On Tue, 2006-01-10 at 19:55 +0100, ezra resnedan wrote: > I would try to place a chroot to the new / and grub -install in the > post-install script... >
I just create a grub.conf put that in the overrides then indeed run something similar to mount devfs /dev/ -t devfs cp /usr/share/grub/i386-redhat/* /boot/grub/ echo "root (hd0,0) setup (hd0)"| grub umount /dev/ Watch out when running in a chroot with no devfs. You might still fail to find your disks. greetz Kris > > 2006/1/10, Charles Galpin <[EMAIL PROTECTED]>: > > Hi Steve > > > > On Jan 9, 2006, at 10:20 PM, Kan Tok wrote: > > > > > The machine does indeed have 2 nics. I have the BIOS set to only > > > enable PXE boot on planar ethernet 2. And like I said it seems to > > > grab the first set of dhcp offers just fine (I get past the point > > > where you see the message.txt menu screen and the initrd and kernel > > > load). But, you're saying there might be a problem after that with > > > some sort of NIC confusion? Would ethereal be able to detect this > > > sort of problem, would the confused nic send out its mac address to > > > view in its response? I'll take a look at the BIOS and see if it's > > > possible to disable the first NIC, but I don't remember there being an > > > option to explicitly shutdown one of the nics (only enabling or > > > disabling PXE booting for each card, would enabling both of them do > > > anything?). Is there some other way to achieve this effect for > > > purposes of having only one nic (in my case the second nic) enabled > > > to ensure it's the only one alive? > > > > What I am saying is the BIOS sees them in one order - for arguments > > sake lets say first and second, and lets say you have your ethernet > > cable connected to the first, and it PXE boots fine. Now when the > > kernel is loaded, it scans the PCI bus in the opposite order and so > > sends it's dhcp request out the second nic (whether you have an > > ethernet cable connected or not) and thats why it fails. You see this > > on some hardware when switching from a 2.4 to a 2.6 kernel btw. > > > > It's easy to test. Just plug both ethernets into your network and the > > first dhcp request should have a different mac address than the second, > > but the process should work. > > > > If you find this is the case, try 3.6.3 which has a 2.6 kernel, and it > > may just see the nics in the same order as the bios. > > > > hth > > charles > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_idv37&alloc_id865&opclick > > _______________________________________________ > > Sisuite-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Sisuite-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > -- Kris Buytaert <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
