From: <ardy@rdb.linux-help.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Slackware init
Date: Mon, 26 Feb 2001 18:21:11 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.20.0102261819100.27432-100000@rdb.linux-help.org> (raw)
In-Reply-To: <200102262215.f1QMF4W11409@webber.adilger.net>
On Mon, 26 Feb 2001, Andreas Dilger wrote:
> In my Turbolinux init (I haven't used Slackware for many years), there is
> an explicit mount of /proc in rc.sysinit. Later, when it is mounting the
> rest of the filesystems, it uses "mount -a -t nonfs,proc", to avoid any
> error messages.
Oh, this is excellent, I never thought of adding proc to that mount
command, how thoughtless of me.
That ought to about fix me up then, thank you very much!
prev parent reply other threads:[~2001-02-26 23:21 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 ` [linux-lvm] FYI Functioning " ardy
2001-02-26 21:39 ` [linux-lvm] " ardy
2001-02-26 22:15 ` Andreas Dilger
2001-02-26 23:21 ` ardy [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=Pine.LNX.4.20.0102261819100.27432-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).