public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Christian Schmidt <lkml@digadd.de>,
	Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Help needed: Partitioned software raid > 2TB
Date: Sat, 16 Jun 2007 11:38:15 +0600	[thread overview]
Message-ID: <46737747.1050608@ums.usu.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0706151824240.32724@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Jun 15 2007 16:03, Christian Schmidt wrote:

>> Thanks for the clarification. I didn't use LVM on the device on purpose,
>> as root on LVM requires initrd (which I strongly dislike as
>> yet-another-point-of-failure). As LVM is on the large partition anyway
>> I'll just add the second partition for now, and change the system setup
>> with the next drive migration. Maybe linux even supports root-on-lvm
>> natively until then ;)
> 
> Uh, it does. By means of initrd/ramfs image. Blame your distro if it still
> can't do root-on-LVM, there is at least one who can.

AFAIK, root-on-LVM on the whole disk (BTW, I use such setup myself) requires 
LILO, doesn't it? Could you please list a few distributions with an easy 
method to install LILO (and, of course, root and /boot on LVM on whole disk) 
from their default installation media? So far, I only know that Debian can 
do it if you run debootstrap by hand, although they say that such setup is a 
bug (http://bugs.debian.org/401393).

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-06-16  5:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15 11:56 Help needed: Partitioned software raid > 2TB Christian Schmidt
2007-06-15 14:37 ` Andi Kleen
2007-06-15 14:03   ` Christian Schmidt
2007-06-15 16:25     ` Jan Engelhardt
2007-06-16  5:38       ` Alexander E. Patrakov [this message]
2007-06-16  6:46         ` Jan Engelhardt
2007-06-16  7:55           ` Alexander E. Patrakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46737747.1050608@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=andi@firstfloor.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@digadd.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox