From: Joe Thornber <thornber@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Patch for Miguel Cabe?a's lvm2create_initrd script
Date: Wed Mar 10 08:25:00 2004 [thread overview]
Message-ID: <20040310132858.GD643@reti> (raw)
In-Reply-To: <1078884314.2919.16.camel@localhost>
On Tue, Mar 09, 2004 at 09:05:14PM -0500, Jeff Layton wrote:
> The second one is an ugly hack, and I'm definitely open to better ways
> of handling it. After my kernel upgrade (from 2.6.1 to 2.6.4-rc2), the
> major number of the device mapper devices on my system changed. So, I
> added a hack to copy the contents of the ramdisk /dev/mapper directory
> to the /dev/mapper directory on the lvm2 root filesystem, prior to the
> pivot_root. It works for me, but I'd love to hear about better ways of
> handling this.
Mount tmpfs on /dev/mapper, and then run 'dmsetup mknods' ?
- Joe
next prev parent reply other threads:[~2004-03-10 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 19:06 [linux-lvm] Another lvm2create_initrd for having a root filesystem on LVM2 Miguel Cabeça
2004-02-26 22:49 ` Kevin P. Fleming
2004-03-09 21:03 ` [linux-lvm] Patch for Miguel Cabeça's lvm2create_initrd script Jeff Layton
2004-03-10 8:25 ` Joe Thornber [this message]
2004-03-10 11:36 ` [linux-lvm] Patch for Miguel Cabe?a's " Jeffrey Layton
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=20040310132858.GD643@reti \
--to=thornber@redhat.com \
--cc=linux-lvm@redhat.com \
/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