Re: vendor class identifier and kickstart

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

 



On 26 Jun 2003, Eric Doutreleau wrote:

> Le jeu 26/06/2003 à 16:29, John a écrit :
> > On 26 Jun 2003, Eric Doutreleau wrote:
> > 
> > > 
> > > Hi
> > > 
> > > I'm wondering if it s possible when doing a network base kickstart
> > > installation ( throug dhcp ) to set up the vendor class identifier in
> > > the dhcp request in order to get different parameter.
> > > 
> > > We have multi boot system here and we install all of our machine
> > > through network.
> > > Therefore there s some kind of competition among diffrent os for the
> > > value of
> > > next server
> > > boot_filename 
> > > in the dhcpd.conf.
> > > 
> > > if we could set up the vci to a particuliar value for kickstart we would
> > > solved our problem at least for kickstart.
> > > 
> > > Thanks in advance for any help
> > 
> > Can't you each have your own LAN segment for installation purposes?
> > That's what I prefer
> 
> Well i just can't
> and even if i could i would prefer not to :)

Trust me. life is easier if you own the LAN!
> > .
> > 
> > If not, it shouldn't be hard to modify pump in the installer to add
> > additional information... AHhhhhhhhhh
> 
> Hmm
> It s what i would like to do
> do you have any information about doing that?
> > 
> > This is before the installer?
> 
> Well i really don't know.

Think... You turn on the machine, the BOOT ROM in the NIC talks to your
DHCP server and fetches the file the server says from the server it
says.

Then Anaconda starts, if you were lucky enough to get _your_ reply.

> 
> > 
> > You can probably use etherboot (www.etherboot.org) to load and run the
> > installer: it doesn't do PXE, but it shouldn't be hard to make NBI
> > images, and from then on it's all the same.
> > 
> > It means you either burn your own ROMs, or boot the "ROM" from floppy -
> > intended for testing, but handy when your NIC doesn't have ROM.
> > 
> > 
> > Here's my etherboot segment from dhcpd.conf:
> > # Filched from http://clic.mandrakesoft.com/documentation/pxe/ch04.html
> >       class "Etherboot"
> >   {
> >      match if substring (option vendor-class-identifier, 0, 13) = "Etherboot-5.0";
> >      option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
> >      option vendor-class-identifier "Etherboot-5.0";
> >      vendor-option-space PXE;
> >      option PXE.mtftp-ip 0.0.0.0;
> >      filename "/tftpboot.ser";
> >   }
> > 
> >  
> > 
> > Presumably you can change the Etherboot string in the ROM and config
> > file to something else if several of you want to do it on the same LAN.
> >  
> I would prefer not to use etherboot as i have a lot of different
> hardware.
> with kickstart i boot with only one CD for all my machine.
> i would love not lose this fact.

So what filename do you need from the DHCP server? If you're booting
from CD then you don't need boot info from the DHCP server because
you've already booted.




> 
> Nevertheless thanks for your answer.
> 
> 
> 

-- 
Please, reply only to the list.

Join the "Linux Support by Small Businesses" list at
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux