From: kihan <kihan@gmx.at>
To: linux-lvm@sistina.com
Subject: [linux-lvm] device mapper startup
Date: Fri May 9 04:27:01 2003 [thread overview]
Message-ID: <3EBB7489.3060600@gmx.at> (raw)
hello,
i have now compiled a kernel with device-mapper support, and the lvm2 tools.
i have my root filesystem on an lvm-jfs drive, so i need a ramdisk. (it
worked for me for 2.4.12)
i don't use "devfs", so therefore i need to start "devmap_mknod.sh" on
each boot, i think after reading the documentation.
so my question is, when do i need to start the script?
1. do i need to run it from the "linuxrc"-script of my ramdisk?
2. do i need to run it again in my "normal" boot scripts?
3. do i need to create any directories, devices etc in "dev" (ramdisk
also?), before the script runs correctly?
at the moment when my system starts up with the device mapper kernel
driver, i get following message, when "vgscan" is run from the
"linuxrc"-script on my ramdisk.
"/dev/mapper/control": no such file or directory
....after that i get a message, which asks, if the kernel has
device-mapper support. and yes i have complied the kernel with the
"0.96.08" release, because current cvs from the device-mapper sources do
not complie, and i'm not he best coder...;-)
thanks for any help again,
manfred
reply other threads:[~2003-05-09 4:27 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=3EBB7489.3060600@gmx.at \
--to=kihan@gmx.at \
--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