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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4877c76c1002190104x3c801023x3ba2e3c7a11fcdf7@mail.gmail.com>
Date:	Fri, 19 Feb 2010 01:04:02 -0800
From:	Michael Evans <mjevans1983@...il.com>
To:	Goswin von Brederlow <goswin-v-b@....de>, david@...g.hm,
	Kyle Moffett <kyle@...fetthome.net>,
	Rudy Zijlstra <rudy@...mpydevil.homelinux.org>,
	Neil Brown <neilb@...e.de>,
	"Mr. James W. Laferriere" <babydr@...y-dragons.com>,
	Bill Davidsen <davidsen@....com>,
	Volker Armin Hemmann <volkerarmin@...glemail.com>,
	Michael Evans <mjevans1983@...il.com>,
	linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org
Subject: Re: Linux mdadm superblock question.

I actually much prefer building my own kernel for servers and
higher-end workstations.  I like having all the core drivers needed to
'get running' in there; even if the more delicate but static logic of
how to track down and assemble/unlock the drives is in the initramfs
image.

The only really annoying issue I've had with my custom initramfs
creator is getting it 'chained' by various distros auto-initramfs
update triggers so that it can grab the version of modules that match
a given kernel.  I have several ways in mind to work around that issue
at various steps, but no known userbase to support besides my self and
thus less motivation to work on that task.

Everything else of course works exactly the same as long as the
configuration hasn't changed on the host system.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ