Re: Whether /mnt/source should be visible chroot'd or not

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



John Summerfied wrote:
Philip Prindeville wrote:

which I didn't understand, and seemed to be counter to most expectations.

So I wanted to ask, am I really alone here in left field?  Because at
least one other posting (earlier today) on Kickstart-list seemed to
imply that this is a fairly common expectation/misunderstanding.

Anyone else have feelings on this issue either way?

What am I missing?

Where would you expect the install source to be mounted if you're installing via http or ftp?

Well, obviously network based (or specifically .iso image based)
installs have some variation.  I pointed this out in the fact that
doing a DVD-based (or CD-based) install doesn't enable networking
(though it wouldn't do any harm to do so).



I suggest you learn what environment variables are set (there are some) and where the ks file is, and how to extract the info you want from those sources.

Ok.  I'll look into it.  Too bad this isn't pointed out anywhere obvious
in the Kickstart documentation.  Perhaps it's a future addition...  Is
there something besides ANACONDAARGS I should be looking at?

As for the ks file... Yeah, that could be more clear also.  If one
specifies "ks=cdrom", it isn't clear where on the cdrom it's
expected to live from the docs... I.e. is it in the root, or the
isolinux/ directory, or even in the initrd.img file...  People trying
to build installers shouldn't have to sift through the internals of
how Anaconda works in order to figure that stuff out, IMO.


You can, if you choose, have several %post scripts, and the first of those could do the discovery and write the results to the target system in a convenient location.

Actually, I currently do that now in a %pre script, since the
mount point of the DVD gets clobbered in the FC5 version
(and will do so until bugid 191381 gets into the distribution).

The first cut would simply be like this:
%post
set >somepath/somefile
ls -l /tmp >somepath/anotherfile
cp /tmp/*ks somepath/

Actually, I currently do:

cp /mnt/source/ks.cfg ...

from a non-chrooted %post script...  Is there any difference between
that one and the one that gets copied into /tmp?

-Philip


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux