Ok.....it's been known now for over 2 days that mkinitrd is messed up. Why hasn't there been an update for 10.1? Fred -- MickySoft, the ultimate corporate parasite.
On 19/09/06 20:55, Fred A. Miller wrote:
Ok.....it's been known now for over 2 days that mkinitrd is messed up. Why hasn't there been an update for 10.1? That reminds me of Michelangelo's reply to Pope Julius, who kept asking (about the Sistine Chapel ceiling), "When will you make an end of this?"
The reply, "When I am done."
Darryl Gregorash wrote:
On 19/09/06 20:55, Fred A. Miller wrote:
Ok.....it's been known now for over 2 days that mkinitrd is messed up. Why hasn't there been an update for 10.1?
That reminds me of Michelangelo's reply to Pope Julius, who kept asking (about the Sistine Chapel ceiling), "When will you make an end of this?"
The reply, "When I am done."
IMHO, issues with mkinitrd are very serious, especially with a new kernel being made available via standard YOU. I can see this leading to large numbers of machines becoming ubootable. Yes, the machines can be fixed; yes, the bugs do not cause loss of data; and yes, eventually this will leave a sour taste in people's mouths when thinking of moving to Suse. There is a reason we do not have Michelangelos in our data centers :P -- --Moby
On Tuesday 19 September 2006 11:08 pm, Darryl Gregorash wrote:
On 19/09/06 20:55, Fred A. Miller wrote:
Ok.....it's been known now for over 2 days that mkinitrd is messed up. Why hasn't there been an update for 10.1?
That reminds me of Michelangelo's reply to Pope Julius, who kept asking (about the Sistine Chapel ceiling), "When will you make an end of this?"
The reply, "When I am done."
I don't write code and assumed it was an "easy fix." Fred -- MickySoft, the ultimate corporate parasite.
On 19/09/06 22:12, Fred A. Miller wrote:
On Tuesday 19 September 2006 11:08 pm, Darryl Gregorash wrote:
<snip> The reply, "When I am done."
I don't write code and assumed it was an "easy fix." I have no idea, and won't speculate. Meanwhile, perhaps you can do as suggested, revert to the previous version of mkinitrd, and don't forget to *run* mkinitrd afterwards.
For Moby: I never suggested this wasn't a serious issue, and perhaps the reason a fix hasn't arrived yet is because the SuSE people also regard it as such -- and thus wish to make damn sure it is properly fixed before releasing an upgrade.
On Wednesday 20 September 2006 2:09 am, Darryl Gregorash wrote:
On 19/09/06 22:12, Fred A. Miller wrote:
On Tuesday 19 September 2006 11:08 pm, Darryl Gregorash wrote:
<snip> The reply, "When I am done."
I don't write code and assumed it was an "easy fix."
I have no idea, and won't speculate. Meanwhile, perhaps you can do as suggested, revert to the previous version of mkinitrd, and don't forget to *run* mkinitrd afterwards.
For Moby: I never suggested this wasn't a serious issue, and perhaps the reason a fix hasn't arrived yet is because the SuSE people also regard it as such -- and thus wish to make damn sure it is properly fixed before releasing an upgrade.
Also, there are only some systems that are affected with this new kernel update. Systems I upgraded today don't have the problem with mkinitrd. Fred -- MickySoft, the ultimate corporate parasite.
Darryl Gregorash wrote:
On 20/09/06 14:43, Fred A. Miller wrote:
<snip>
Also, there are only some systems that are affected with this new kernel update. Systems I upgraded today don't have the problem with mkinitrd.
Perhaps the mkinitrd update was released while we all slept.
As stated in the original complaint, issues arise with lvm etc on / - no / on lvm (at least my issues with mkinit which I have since reported in Bugzilla), no issues with the latest mkinit. -- --Moby
On Wednesday 20 September 2006 5:47 pm, Darryl Gregorash wrote:
On 20/09/06 14:43, Fred A. Miller wrote:
<snip>
Also, there are only some systems that are affected with this new kernel update. Systems I upgraded today don't have the problem with mkinitrd.
Perhaps the mkinitrd update was released while we all slept.
Hehehehehe.....could be. I "grabbed" it in the wee hours of the morning "eastern" time. Fred -- MickySoft, the ultimate corporate parasite.
Hi all! Does anyone know how i can add a linux driver module at boot prompt? Well... im a SuSE user but in this case its on redhat :) I dont what to use the linux dd command at boot promt. I would like to add a module (special hardware not supported by the kernel) at boot prompt or in the kickstart script. Im makeing a special version of RedHat ES 4.0 x86_64. I have tried with RedHat without any success so here i am.... begging for help from competent people! :) I have the module compiled for my installation kernel, how can i make it available to the installation ... make it find my driver on my cdrom? Cheers and thanks guys! Regards //Mattias
On Saturday 23 September 2006 13:07, Per Jessen wrote:
LinuxInfo wrote:
Does anyone know how i can add a linux driver module at boot prompt?
Assuming boot prompt = lilo prompt:
insmod=xxxxxx
This is a command interpreted by linuxrc in suse, not by lilo or grub. Does Red Hat use the same linuxrc?
participants (6)
-
Anders Johansson -
Darryl Gregorash -
Fred A. Miller -
LinuxInfo -
Moby -
Per Jessen