linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: ardy@rdb.linux-help.org
To: linux-lvm@sistina.com
Subject: [linux-lvm] FYI Functioning Slackware init
Date: Mon, 26 Feb 2001 19:14:17 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.20.0102261859050.29765-100000@rdb.linux-help.org> (raw)
In-Reply-To: <200102261729.f1QHTAZ10614@webber.adilger.net>

Ok, with the help of list members I was able to resolve the vgscan 
problems I was experiencing booting Slackware. I'm going to share my 
setup.

In /etc/rc.d/rc.S:

 # Remount the root filesystem in read-write mode
 echo "Remounting root device with read-write enabled."
 /sbin/mount -w -v -n -o remount /
 
 # This was an addition, limits vgscan to /proc thus
 # speeding up the scan immensely.
 /sbin/mount /proc 
 
# Initialize Logical Volume Manager
 /sbin/vgscan
 /sbin/vgchange -ay

 .....

 # mount file systems in fstab (and create an entry for /)
 # but not NFS because TCP/IP is not yet configured
 /sbin/mount -a -v -t nonfs,proc

As I had detailed in a previous posting, I had to alias off a bunch
of devices I don't have, in modules.conf. I no longer require those
aliases, and the loop module no longer loads since loop devices are no
longer scanned either.

Again, my thanks to the list, and I hope this can help other Slackware
users.

P.S. Perhaps this can be added to the HOWTO for Slackware init?

  reply	other threads:[~2001-02-27  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-25 18:33 [linux-lvm] Slackware init ardy
2001-02-25 23:52 ` AJ Lewis
2001-02-26 12:08   ` ardy
2001-02-26 14:27     ` AJ Lewis
2001-02-26 17:29       ` Andreas Dilger
2001-02-27  0:14         ` ardy [this message]
2001-02-26 21:39       ` ardy
2001-02-26 22:15         ` Andreas Dilger
2001-02-26 23:21           ` ardy

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=Pine.LNX.4.20.0102261859050.29765-100000@rdb.linux-help.org \
    --to=ardy@rdb.linux-help.org \
    --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;
as well as URLs for NNTP newsgroup(s).