| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 7 Dec 2007 09:36:18 +0100 (CET) From: Jan Engelhardt <jengelh@...putergmbh.de> To: Nix <nix@...eri.org.uk> cc: Justin Piszcz <jpiszcz@...idpixels.com>, linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org, apiszcz@...arrain.com Subject: Re: Kernel 2.6.23.9 + mdadm 2.6.2-2 + Auto rebuild RAID1? On Dec 7 2007 07:30, Nix wrote: >On 6 Dec 2007, Jan Engelhardt verbalised: >> On Dec 5 2007 19:29, Nix wrote: >>>> On Dec 1 2007 06:19, Justin Piszcz wrote: >>>> >>>>> RAID1, 0.90.03 superblocks (in order to be compatible with LILO, if >>>>> you use 1.x superblocks with LILO you can't boot) >>>> >>>> Says who? (Don't use LILO ;-) >>> >>>Well, your kernels must be on a 0.90-superblocked RAID-0 or RAID-1 >>>device. It can't handle booting off 1.x superblocks nor RAID-[56] >>>(not that I could really hope for the latter). >> >> If the superblock is at the end (which is the case for 0.90 and 1.0), >> then the offsets for a specific block on /dev/mdX match the ones for /dev/sda, >> so it should be "easy" to use lilo on 1.0 too, no? > >Sure, but you may have to hack /sbin/lilo to convince it to create the >superblock there at all. It's likely to recognise that this is an md >device without a v0.90 superblock and refuse to continue. (But I haven't >tested it.) > In that case, see above - move to a different bootloader. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists