On Nov 10, 2008, at 5:13 PM, Joseph L. Casale [EMAIL PROTECTED]
wrote:
In the future, when upgrading the kernel, will future initrd's be
built with my current modules or will I have to manually create new
initrd's after each update?
Good question that I would love to know as well. I
Tim Nelson wrote:
If my assumptions are correct, the onboard drives are detected first, then
the arrays assembled, and after the system has passed control from the
initrd to boot, THEN the addon controller is detected and hence the third
drive (sdc). If I am correct, then I need to update my
Hello fellow CentOS'ers-
I've got a system running CentOS 5.0. The motherboard has two onboard SATA
ports with two drives attached. I installed the system on a RAID1 setup.
However, I'd like to add a hotspare disk to the array. Since there are no
additional SATA ports, I've installed an
I wanted to MaKe and INITRD and you sent me to check out MKINITRD. How
thoughtful... :-)
Kidding aside, I appreciate the suggestion. I checked it out and simply ran a
'mkinitrd --with=sata_sil /path/to/newinitrd kernel' and rebooted. When grub
popped up, I edited the initrd line to reflect the
In the future, when upgrading the kernel, will future initrd's be built with
my current modules or will I have to manually create new initrd's after each
update?
Good question that I would love to know as well. I thought
/etc/sysconfig/mkinitrd handled
this, but not ripping apart the srpm of
5 matches
Mail list logo
