Linux LVM users
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Migrating to an LVM system (boot/root) disk
Date: Mon, 4 Jun 2001 17:15:12 -0500	[thread overview]
Message-ID: <20010604171512.A348@sistina.com> (raw)
In-Reply-To: <200106041734.f54HYLbh020302@webber.adilger.int>; from adilger@turbolinux.com on Mon, Jun 04, 2001 at 11:34:21AM -0600

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

On Mon, Jun 04, 2001 at 11:34:21AM -0600, Andreas Dilger wrote:
> Yes, you are correct that you know in advance which IOP version you need.
> However, it is much easier for lvmcreate_initrd to just copy all of the
> programs (including the wrapper) to the initrd, instead of trying to find
> which ones are needed and which are not needed.  In the end, the wrapper
> is one disk block + a few directory entries (no more space needed).
> 
> The problem is that "sed" is used in the wrapper script.  AFAIK, I do not
> have "sed" in my wrapper script, so I don't know where it came from.  Can
> you tell me where the wrapper script comes from that you are using and/or
> post a copy to this list so it can be fixed?

Hmm...I put 'sed' in the debian package wrapper scripts since Debian put's
basename in /usr/bin and if you don't use an initrd script and you have your
/usr partition on LVM, you can't use the wrapper...

Is there an easy way we can work around this?  Maybe hack up the
create_initrd script a bit more?  I can just adjust it in the debian
packages too i guess.

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing...
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-06-04 22:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03  2:16 [linux-lvm] Migrating to an LVM system (boot/root) disk Brian J. Murrell
2001-06-03  5:02 ` Steve Wray
2001-06-03 10:22   ` Brian J. Murrell
2001-06-03 10:59     ` Steve Wray
2001-06-03 18:27       ` Michael Tokarev
2001-06-03 21:12         ` Steve Wray
2001-06-03 23:11           ` Michael Tokarev
2001-06-04 17:34             ` Andreas Dilger
2001-06-04 18:59               ` Michael Tokarev
2001-06-04 21:03                 ` Steve Wray
2001-06-04 22:15               ` AJ Lewis [this message]
2001-06-04 23:15                 ` Michael Tokarev
2001-06-04 23:28                   ` Luca Berra
2001-06-05 16:57                     ` AJ Lewis
2001-06-05 17:55                   ` Andreas Dilger
2001-06-05 18:08                     ` Luca Berra
2001-06-04  3:40 ` Andreas Dilger
2001-06-04  6:04   ` Brian J. Murrell
2001-06-04 17:37     ` Andreas Dilger

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=20010604171512.A348@sistina.com \
    --to=lewis@sistina.com \
    --cc=linux-lvm@sistina.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