I have noticed that when you boot from the DVD that if you don't do anything it acts like you hit enter.
How hard would it be to change that to do the following.
Check to see if the system has a keyboard. If not look for a floppy with ks.cfg on it. If it finds it act like the user typed: linux ks=floppy
If no floppy, look for usb device and do the same. Linux ks=usb/ks.cfg kind of thing.
If no usb start network with dhcp and look for Web server linux ks=http://fedora7.<domain from dhcp>/ks.cfg Or maybe linux ks=http://fedora7.<domain from dhcp>/<mac address>.cfg
If no web server then run: Linux vnc vncpassword=Fedora7
If it has a keyboard just do the normal thing.
This would make it so you don't really have to change the dhcp server. Maybe add an alias for a web server. Then the install would happen and when completed would eject DVD. Take out the DVD and power cycle the box and be done.
On Monday 15 January 2007 09:58pm, Jerry Williams wrote:
I have noticed that when you boot from the DVD that if you don't do anything it acts like you hit enter.
How hard would it be to change that to do the following.
Check to see if the system has a keyboard. If not look for a floppy with ks.cfg on it. If it finds it act like the user typed: linux ks=floppy
If no floppy, look for usb device and do the same. Linux ks=usb/ks.cfg kind of thing.
If no usb start network with dhcp and look for Web server linux ks=http://fedora7.<domain from dhcp>/ks.cfg Or maybe linux ks=http://fedora7.<domain from dhcp>/<mac address>.cfg
Why? Why not just use DHCP "nextserver" and "filename" options to get the kickstart file via NFS?
If no web server then run: Linux vnc vncpassword=Fedora7
If it has a keyboard just do the normal thing.
This would make it so you don't really have to change the dhcp server.
What's the advantage of that? Adding "nextserver" and "kickstart" lines is easy. They can even be placed within VCI conditionals or with "static" IP assignments if you need different kickstart files for different boxes.
Maybe add an alias for a web server. Then the install would happen and when completed would eject DVD. Take out the DVD and power cycle the box and be done.
I would be interested in seeing anaconda present some kind of selection "menu" of available kickstart files if "linux ks=whatever:/some/dir/" were specified (or via DHCP "filename"), pointing to a directory with several kickstart files in it.
-----Original Message----- From: fedora-devel-list-bounces@redhat.com [mailto:fedora-devel-list- bounces@redhat.com] On Behalf Of Lamont Peterson Sent: Tuesday, January 16, 2007 9:22 AM To: fedora-devel-list@redhat.com Subject: Re: Smarter install - Headless
On Monday 15 January 2007 09:58pm, Jerry Williams wrote:
I have noticed that when you boot from the DVD that if you don't do anything it acts like you hit enter.
How hard would it be to change that to do the following.
Check to see if the system has a keyboard. If not look for a floppy with ks.cfg on it. If it finds it act like the user typed: linux ks=floppy
If no floppy, look for usb device and do the same. Linux ks=usb/ks.cfg kind of thing.
If no usb start network with dhcp and look for Web server linux ks=http://fedora7.<domain from dhcp>/ks.cfg Or maybe linux ks=http://fedora7.<domain from dhcp>/<mac address>.cfg
Why? Why not just use DHCP "nextserver" and "filename" options to get the kickstart file via NFS?
That is easy at home, not so easy at work and they try really hard not to use nfs if possible.
If no web server then run: Linux vnc vncpassword=Fedora7
If it has a keyboard just do the normal thing.
This would make it so you don't really have to change the dhcp server.
What's the advantage of that? Adding "nextserver" and "kickstart" lines is easy. They can even be placed within VCI conditionals or with "static" IP assignments if you need different kickstart files for different boxes.
Maybe add an alias for a web server. Then the install would happen and when completed would eject DVD. Take out the DVD and power cycle the box and be done.
I would be interested in seeing anaconda present some kind of selection "menu" of available kickstart files if "linux ks=whatever:/some/dir/" were specified (or via DHCP "filename"), pointing to a directory with several kickstart files in it. -- Lamont Peterson lamont@gurulabs.com Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ]
NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's.
On Tuesday 16 January 2007 09:38am, Jerry Williams wrote: [snip]
If no usb start network with dhcp and look for Web server linux ks=http://fedora7.<domain from dhcp>/ks.cfg Or maybe linux ks=http://fedora7.<domain from dhcp>/<mac address>.cfg
Why? Why not just use DHCP "nextserver" and "filename" options to get the kickstart file via NFS?
OK. I guess I'm confused by these:
That is easy at home, not so easy at work
Why is it so hard to add two little line to a DHCP server at work yet so easy at home? I would have to guess that you have a lot of red tape to deal with or something like that.
and they try really hard not to use nfs if possible.
Why? What's wrong with NFS?
Network installs via either HTTP or FTP take longer (i.e. are slower) than via NFS.
On Tue, 2007-01-16 at 09:59 -0700, Lamont Peterson wrote:
On Tuesday 16 January 2007 09:38am, Jerry Williams wrote:
and they try really hard not to use nfs if possible.
Why? What's wrong with NFS?
Network installs via either HTTP or FTP take longer (i.e. are slower) than via NFS.
Although IIRC, NFS over TCP is a must.
On Tuesday 16 January 2007 07:47pm, Paul W. Frields wrote:
On Tue, 2007-01-16 at 09:59 -0700, Lamont Peterson wrote:
On Tuesday 16 January 2007 09:38am, Jerry Williams wrote:
and they try really hard not to use nfs if possible.
Why? What's wrong with NFS?
Network installs via either HTTP or FTP take longer (i.e. are slower) than via NFS.
Although IIRC, NFS over TCP is a must.
Yeah, I would like to see anaconda do that. On occasion, the NFS over UDP with anaconda does cause problems.
On Tue, 2007-01-16 at 09:22 -0700, Lamont Peterson wrote:
Why? Why not just use DHCP "nextserver" and "filename" options to get the kickstart file via NFS?
Surely those are already pointed to the TFTP server which carries images/netboot/ppc{32,64}.img (or whatever the equivalent is for IA32 or AMD64). I don't think it's a good idea to abuse them for kickstart.
You _could_ potentially have vendor-specific DHCP options though.