Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
Mogens Kjaer
mk at crc.dkThu Jun 14 04:49:20 UTC 2007
- Previous message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Next message: [CentOS] zenity question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robinson Tiemuqinke wrote: ... > This doesn't work, I think. the 'ksdevice=eth1' or > 'ksdevide=link' ways don't work well, because the > kickstart process will write MAC addresses to > ifcfg-eth* files, and that will just leave headaches > to local disk boot. I don't understand this. > > Another problem with this method is: you have to > predict which eth? the pxe-booted NIC will be detected > as. If there are more than several types of mixed NIC > boxes, then this method becomes too cubersome and not > applicable. Cumbersome, maybe, but making a custom kernel for each different installation would be worse. Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk
- Previous message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Next message: [CentOS] zenity question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list