Linux LVM users
 help / color / mirror / Atom feed
From: Xavier Brouckaert <xbr@info.ucl.ac.be>
To: linux-lvm@sistina.com
Subject: [linux-lvm] 2.4 LVM1 devfs  -> 2.6.0 LVM2 udev
Date: Fri Dec 19 06:34:01 2003	[thread overview]
Message-ID: <1071837164.7460.37.camel@Chimay.bugfactory.org> (raw)

Hi,

As the 2.6.0 is out, it's time for me to see if I can switch to it.
What is the procedure and the things to know to switch from a 2.4 LVM1
devfs to a 2.6 LVM2 udev ?  I'm using a debian/unstable.  I've seen that
there was a package lvm2 (2.00.08-3) but the comment contains at the end
"requires Linux kernel 2.4.". Does this mean that this package really
cannot handle 2.6 kernels ?

I've also seen that devfs has been obsoleted by udev. However, I didn't
find a udev package for sid nor a kernel option for it (but I've read
that it is only in userspace).  The udev FAQ
(http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ) does not
mention if I need to install hotplug to have udev working.

Do I have to change something in /etc/lvmtab.d and /etc/lvmconf ?

It seems that a thing called "device-mapper" is needed, but I couldn't
find it in the kernel. Is it CONFIG_DM_IOCTL_V4 ? The "DM" substring
makes me think it's that but the comment in "make menuconfig" doesn't
say that it's for LVM nor that it's a device mapper.

Thanks !
Xavier

             reply	other threads:[~2003-12-19  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19  6:34 Xavier Brouckaert [this message]
2003-12-19  7:26 ` [linux-lvm] 2.4 LVM1 devfs -> 2.6.0 LVM2 udev Patrick Caulfield
2003-12-20  4:11   ` [linux-lvm] 2.4 LVM1 devfs -> 2.6.0 LVM2 devfs Francis SOUYRI
2003-12-20  9:58     ` Patrick Caulfield
2003-12-22  0:20       ` Francis SOUYRI
2003-12-22  2:09         ` Patrick Caulfield

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=1071837164.7460.37.camel@Chimay.bugfactory.org \
    --to=xbr@info.ucl.ac.be \
    --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