Can the NFS media location be passed to anaconda as a kernel arg?

[Kyle McDonald]

On 4/29/2010 8:59 AM, Chris Lumens wrote:
>> I want to setup PXE network installs that are interactive, but I'd like
>> to limit the amount of questions the user has to enter for each one. The
>> PXE boot already passes some kernel args to configure the serial
>> console, and force a vnc install. I'm wondering if I can also supply the
>> NFS location for the media as a kernel arg so that users don't need to
>> type it in everytime (It's always the same, and it's long.)
>>     
> Sure, method= (or stage2=/repo= if you're using F13 or RHEL6 beta).
>
> You'd do something like method=nfs:your.server.here:/mnt/wherever
>
>   
Cool. Thanks!
> Keep in mind if your path plus other parameters is too long, you're
> going to run up against a size limit and arguments will start getting
> trimmed or dropped.  So if you start to see pretty weird behavior, it
> might be time to switch to a kickstart file.
>   
I'm aware of that with SLES, but luckily I haven't hit that problem yet.
>> Also I know when doing KickStart installs, you can use ks-device=eth1 to
>> avoid being prompted for the network device when there is more than one.
>> Can I use this same option so that the interactive user doesn't have to
>> know which eth to pick?
>>
>> On a related note, is there a way to have anaconda figure out which
>> interface the PXE boot booted the machine on and just go with that one?
>> Right now I need to make 2 different PXE boot config files for the 2
>> types of machines I have because one boots on eth0 and the other on eth1.
>>     
> ksdevice=bootif
>
>   
That's cool too. What release did that appear in?

Now if GRUB or PXElinux could only read the serial console redirection
settings from the BIOS, and pass them to the kernel, I could cut the
number of PXE config files I have in half (half ttyS0 at 115200, the others
at ttyS1 at 19200 - Ugh!)

  -Kyle


> - Chris
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>