[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1002170932010.4721@asgard.lang.hm>
Date: Wed, 17 Feb 2010 09:41:53 -0800 (PST)
From: david@...g.hm
To: Kyle Moffett <kyle@...fetthome.net>
cc: 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.
On Wed, 17 Feb 2010, Kyle Moffett wrote:
> On Wed, Feb 17, 2010 at 04:38, Rudy Zijlstra
> <rudy@...mpydevil.homelinux.org> wrote:
>> Kyle Moffett wrote:
>>> On Tue, Feb 16, 2010 at 21:01, Neil Brown <neilb@...e.de> wrote:
>>>> I will not be removing 0.90 or auto-assemble from the kernel in the
>>>> foreseeable future.
>>>> None the less, I recommend weaning yourself from your dependence on it.
>>>> initramfs is the future, embrace it.
>>>>
>>>
>>> What are people's reasons for pushback against initramfs? I've heard
>>> lots of claims that "it's not trustworthy" and "it breaks", but in 7
>>> years of running bootable software RAID boxes on weird architectures
>>> (even running Debian unstable) I have only once or twice had initramfs
>>> problems.
Kyle,
for a distro that is trying to make one kernel image run on every
possible type of hardware features like initramfs (and udev, modeules,
etc) are wonderful.
however for people who run systems that are known ahead of time and
static (and who build their own kernels instead of just relying on the
distro default kernel), all of this is unnessesary complication, which
leaves more room for problems to creep in.
David Lang
Powered by blists - more mailing lists