> From: Michael Hennebry [mailto:hennebry@xxxxxxxxxxxxxxxxxxxxx] > Sent: 25 January 2012 04:20 > > I've encountered two problems: > How to specify the kickstart file. > How, in the kickstart file does one affect /etc/login.defs . > According to fedora, a kickstart file is the right way to do what I > want. > There is no specific command to affect /etc/login.defs . > >From what I have read, %post runs too late: > Fake users have already been assigned in the range 500..999 . > It seems to me that %pre runs too soon, before partitions are even > assigned. > The %pre example has me really confused. > http://docs.fedoraproject.org/en- > US/Fedora/16/html/Installation_Guide/s1-kic > kstart2-preinstallconfig.html > The example writes out a partioning scheme, > but to work / , /bin and /tmp must already exist. > What is going on? > > How do I specify the kickstart file? > I plan to use a minimal bootable CD and a DVD image on a hard drive. > One technique mentioned was to put ks.cfg in a > correct directory and let anaconda find it. > That technique would seem to require inserting it into an iso file. > I must be missing something. > The other technique involves editing a boot command. > I've seen two syntaxes: > linux ks=hd:/device/dir/ks.cfg > linux ks=hd:partition/path/ks.cfg > If I do it that way, which boot sequence do I interrupt? > As I understand it, two boot sequences, > one to the CD and the other to the DVD iso file. > Is that correct? When you boot the installer, it creates a running system with / and /tmp directories in a RAM-disk. That's a part of memory that has been configured to look like a disk with filesystems. That is what the %pre example you quoted is using. Your real disk partitions have not been created yet. The usual use of %pre is to work out how the real disk should be partitioned. After the installer creates the real partitions, it mounts them under /mnt/sysimage from its RAM-disk, in order to write files to them. When the system boots the new operating system, the real disk partitions get mounted in their proper places and the RAM-disk contents are lost. "Two boot sequences" doesn't look right - although I've never tried what you're describing. I would imagine that it _boots_ from the minimal bootable CD and then loads stuff from the DVD image. In that case, where you would just press <ENTER> or type linux text <ENTER> to start the installer, you would type linux ks= with whatever the path to your kickstart file is. If you have a floppy disk, that's still the easiest way to specify a kickstart file; a USB floppy is the next easiest. I'm sure there has been advice on working out the correct device path for USB kickstart on on this list before - have a look through the archives. An ordinary USB stick is possible, but you do need to be careful that it doesn't get incorporated into the filesystems for the installed system and reformatted. Let's step back a bit, though. What do you need to change in login.defs, and what "fake users" are being assigned? There may be a better way to fix this. Moray. "To err is human; to purr, feline." _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
