From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: linux-lvm@sistina.com, phoebe-list@redhat.com
Subject: [linux-lvm] [CFT] LVM2 RPM Packages availalble for Red Hat 8
Date: Fri Jan 10 16:17:01 2003 [thread overview]
Message-ID: <20030110171726.E3993@ti19> (raw)
[Cross-posted to Linux LVM and Red Hat 8.1 Beta lists.]
I've packaged up versions of lvm1, lvm2, devmapper, and mkinitrd for use
with Red Hat 8. I'd like to see similar changes rolled into RedHat 8.1,
so that it is 2.6-ready, and would appreciate comments and wider testing.
WARNING: These are *alpha*-quality developer-only packages! Don't entrust
your data to them!
What I've done so far:
- Modified and repackaged LVM1 to create a single /sbin/lvm1 executable, like
LVM2, and use symlinks for the legacy commands. Broke the monolithic
LVM package into sub-packages, so that it can coexist with LVM2.
Provided an /sbin/lvm1.static that is linked against diet libc.
- Packaged devmapper with a tiny statically-linked C program (mkdmctl)
used to create the control file. This is useful in combination with
nash for the RedHat initrd, since nash is not a real shell.
- Packaged LVM2. Provides an /sbin/lvm2.static that is linked against diet libc.
- Modified mkinitrd to take a --lvm-version={1,2} argument to specify
which LVM version to use. With 2.4.20-2.2, my initrds (with aic7xxxx)
are 475287 bytes (LVM1) and 472105 bytes (LVM2), so they fit on a 1722kB
floppy.
- Made the minimal hack to rc.sysinit required to make it boot.
Basically, I just want to use LVM2, but have the box function properly
if for some reason I need to boot a kernel without device mapper.
Do not trust this patch with your
Currently, I have LVM{1,2} installed as /sbin/lvm{1,2}. There are two
"links" packages that Provide (in the RPM sense) "lvm". The lvm1-links
sub-package has symlinks pointing -> lvm1. The lvm2-links sub-package
has links pointing -> lvm, which is a currently a shell script that invokes
one of lvm{1,2}, but could simply be a symlink determined at boot.
I'm currently running root-on-LVM with the RedHat 2.4.20-2.2 kernel.
I managed to destroy my root partition in the process of debugging these
packages. [Fortunately, I saved a copy in a non-LVM partition.] I believe
that the problem is with switching LVM versions when there are stale
/dev/<vg> directories left over if the box is not shutdown cleanly ...
Find the packages here:
ftp://67.83.203.127:/pub/lvm
[Caution: my home cable modem, so upstream bandwidth is quite limited.
I know, I should set up dyndns at a minimum, but another day ...]
Regards,
Bill Rugolsky
reply other threads:[~2003-01-10 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030110171726.E3993@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=linux-lvm@sistina.com \
--cc=phoebe-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.