From: Francis SOUYRI <francis.souyri@wanadoo.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM rootfs and cramfs as ramdisk
Date: Tue Feb 4 00:02:02 2003 [thread overview]
Message-ID: <3E3F56CD.2000100@wanadoo.fr> (raw)
In-Reply-To: <002901c2ca3a$03c98e90$240b892c@pe1mhp.ampr.org>
Hi Jan,
On my system lvm driver is in the kernel (no module).
/#!/bin/sh
I mount /etc with a tmpfs to have /etc in rw (I do not need the
"/etc/fstab").
mount -t tmpfs none /etc
Now I mount /proc because "vgscan" need to access "/proc/partitions" (I
do not need the "/etc/fstab").
mount -t proc none /proc
Finaly I can scan for the volume groups and activate these volume groups.
echo "Scanning for Volume Groups..."
/sbin/vgscan
echo "Activating Volume Groups"
/sbin/vgchange -a y
I umount /proc and /etc because, I do not need now the "/etc" (you need
to do a vgscan in the startup script of your system to update the
"/etc/lvm*" files in the real "/etc"), and the kernel after the mount of
the real / mount the /proc.
umount /proc
umount /etc
I do not need any files in the "/etc" I only need to create temporaries
files with vgscan.
Best regards.
Francis
Jan H. van Gils wrote:
>>Hi Jan,
>>
>>
>
>Hi Francis,
>
>
>
>>You need "/etc" in rw for this you can mount "/etc" in the "linuxrc"
>>script using a tmpfs filesystem like this:
>>
>>
>>
>
>Thanks for the information.
>I was already wondering if I was the only one with this problem.
>
>But what about the init files that are normaly in "/etc" ?
>I can imagion that a tmpfs is an empty filesystem.
>Or do I not fully understand what you mount option does ?
>
>
>
>>/#!/bin/sh
>>...
>>mount -t tmpfs none /etc
>>mount -t proc none /proc
>>echo "Scanning for Volume Groups..."
>>/sbin/vgscan
>>echo "Activating Volume Groups"
>>/sbin/vgchange -a y
>>...
>>umount /proc
>>umount /etc
>>/
>>I used "romfs" for the "initrd" ramdisk.
>>
>>Best regards.
>>
>>Francis
>>
>>
>>
>
>With regards Jan
>
>
>----
>With regards Jan H. van Gils
>Internet web-page http://www.Knoware.NL/users/janvg/
>Internet e-mail address JanVG@Knoware.NL
>RIPE Whois JHG5-RIPE, 6BONE Whois JHG1-6BONE
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>
prev parent reply other threads:[~2003-02-04 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 15:21 [linux-lvm] LVM rootfs and cramfs as ramdisk Jan H. van Gils
2003-01-30 18:01 ` Francis SOUYRI
2003-02-01 15:37 ` Jan H. van Gils
2003-02-04 0:02 ` Francis SOUYRI [this message]
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=3E3F56CD.2000100@wanadoo.fr \
--to=francis.souyri@wanadoo.fr \
--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.