[opensuse-autoinstall] Mount points
Hello, I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;). Regards hmw -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Flood - Your friendly network packet generator http://www.c0t0d0s0.de/flood/flood.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
on Friday 11 November 2011 Michael Welle wrote:
I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;).
you can not configure the mount point. The only chance would be to change the yast code. We have a variable for that directory but there is a good chance that changing that variable will break the installation because "/mnt" is still hardcoded somewhere else. -- ciao, Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Speichel, Laub Und Saitenspiel" by Stillste Stund -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hello,
sorry for the late answer, I had some trouble at a customer site last
week ;).
Uwe Gansert
on Friday 11 November 2011 Michael Welle wrote:
I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;).
you can not configure the mount point. The only chance would be to change the yast code. We have a variable for that directory but there is a good chance that changing that variable will break the installation because "/mnt" is still hardcoded somewhere else. deep in my guts I expected something like that. But hope dies last, so I asked anyways ;).
Thanks hmw -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Flood - Your friendly network packet generator http://www.c0t0d0s0.de/flood/flood.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Fri, Nov 11, 2011 at 12:35:05PM +0100, Michael Welle wrote:
I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;).
If those are rpms doing that and you added them to an add_on repository that's used during install, try the <post-packages> directive and put them there. Then they'll get installed after the first reboot. I dropped in a custom RPM we use to put in some links (to help support older sw we still have to support for our engineers) that would break if not in the post-packages bit because the autoyast resolver would run it and they'd try to link before the files were in place and would fail. Rather then try to hack in dependencies, using <post-packages> was a much easier fix. If they're scripted installations.. why are you running them that early in the install? Put them in the post-install and there shouldn't be any issue. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Your family are the people who cut you the most slack and give you the most chances. I mean, when Richard Dawson says "Name something you find in a refrigerator" and you say "A dictionary" and the rest of America is screaming "You moron!" at their TV sets, who's clapping and saying "Good answer! Good answer!"? Your family, that's who. ==> Dennis Miller on Families. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Fri, Nov 11, 2011 at 12:35:05PM +0100, Michael Welle wrote:
I have a somewhat odd question which arose from merging the autoyast process with some third party tools. During the installation the target filesystem is mounted on /mnt in the ram disk. Can I configure this mount point? The third party tools use this mount point also. Trying to mount or umount something on /mnt while the installer is running leads to some funny effects ;).
If those are rpms doing that and you added them to an add_on repository that's it's by far more complicated than installing packages. I changed the init
Hello,
Mike Marion
fine. Buuuut, some time later the third party binary remembers the mounted filesystem and tries to umount /mnt....dang.
Why not double mount /mnt beforehand. ? So a single umount from the 3rd party would not cause not any harm. Cheers Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hi,
Hans-Joachim Ehlers
fine. Buuuut, some time later the third party binary remembers the mounted filesystem and tries to umount /mnt....dang.
Why not double mount /mnt beforehand. ? So a single umount from the 3rd party would not cause not any harm. might work somehow. But it must be done after autoyast has partitioned and formated the disks.
Regards hmw -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Flood - Your friendly network packet generator http://www.c0t0d0s0.de/flood/flood.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (4)
-
Hans-Joachim Ehlers -
Michael Welle -
Mike Marion -
Uwe Gansert