also sprach dean gaudet [EMAIL PROTECTED] [2007.09.28.2256 +0100]:
i did search but obviously didn't search for the right things, alas.
Did you get a chance to test 2.6.3-1 now?
i think i might make some @reboot cron job which saves away a copy
of /boot/initrd-`uname -r` after a successful
forcemerge 439334 444364
thanks
also sprach dean gaudet [EMAIL PROTECTED] [2007.09.28.0230 +0100]:
it is EXEPTIONALLY DANGEROUS to replace EVERY SINGLE initrd when mdadm is
installed/upgraded.
Please STOP SCREAMING and look at the existing bugs before you reply
new ones. 2.6.3-1 will not do
On Fri, 28 Sep 2007, martin f krafft wrote:
also sprach dean gaudet [EMAIL PROTECTED] [2007.09.28.0230 +0100]:
it is EXEPTIONALLY DANGEROUS to replace EVERY SINGLE initrd when mdadm is
installed/upgraded.
Please STOP SCREAMING and look at the existing bugs before you reply
new ones.
Package: mdadm
Version: 2.6.2-2
it is EXEPTIONALLY DANGEROUS to replace EVERY SINGLE initrd when mdadm is
installed/upgraded.
you pretty much guarantee that any problem will produce an unbootable
system -- especially if root is on md.
as has just occured to me.
in the past in this situation
4 matches
Mail list logo