From: Daniel Savard <dsavard@cids.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3
Date: Thu May 30 19:37:02 2002 [thread overview]
Message-ID: <1022805422.19446.41.camel@dirac.cids.ca> (raw)
In-Reply-To: <E17DTyw-0008Hp-00@hermes.sistina.com>
le jeu 30-05-2002 à 13:44, James B. Byrne a écrit :
>
> The kmod error is reputedly caused by the ramdisk image file
> (created by lvmcreate_initrd) not containing a /sbin/modprobe
> command. How can I verify if this is so? I note that redhat has
> /sbin/modprobe as a logical link to insmod. Could this be confusing
> lvmcreate_initrd?
The symlink won't cause lvmcreate_initrd to create a ramdisk image with
the missing executable.
To check, just copy your initrd image somewhere, say /tmp, uncompress it
(gunzip) there and mount it on a mount point as a loop device:
Given an initrd uncompressed file name: my_image
Given a mount point named: /tmp/my_mount_point
Just type: mount -o loop /tmp/my_image /tmp/my_mount_point
After that, you can cd to /tmp/my_mount_point and look at the files and
executables there.
Regards,
>
> Regards,
> Jim
>
> --- e-mail is NOT a secure channel
> James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
> Harte & Lyne Limited http://www.harte-lyne.ca
> 9 Brockley Drive vox: +1 905 561 1241
> Hamilton, Ontario fax: +1 905 561 0757
> Canada L8E 3C3
>
--
=======================================
Daniel Savard
Consultation Informatique Daniel Savard
551, boul. Sir-Wilfrid-Laurier
suite 105
Beloeil, (Québec)
Canada J3G 4J1
Tél: (450) 467-8014
Internet: dsavard@cids.ca
=======================================
next parent reply other threads:[~2002-05-30 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17DTyw-0008Hp-00@hermes.sistina.com>
2002-05-30 19:37 ` Daniel Savard [this message]
[not found] <E17DJKw-0006ou-00@hermes.sistina.com>
2002-05-30 12:42 ` [linux-lvm] Re: LVM 1.03 root file system on Redhat 7.3 James B. Byrne
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=1022805422.19446.41.camel@dirac.cids.ca \
--to=dsavard@cids.ca \
--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 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.