All of lore.kernel.org
 help / color / mirror / Atom feed
From: Levi Khatskevitch <LKhatskevitch@cachier.com>
To: Tripp Lilley <tlilley@perspex.com>
Cc: mtd@infradead.org, linuxbios@lanl.gov
Subject: Re: nftl/DoC Mill. root fs question
Date: Wed, 6 Dec 2000 02:33:00 -0500	[thread overview]
Message-ID: <00120602385104.02531@mrserver> (raw)
In-Reply-To: <Pine.LNX.3.96.1001206074454.1800T-100000@mail.perspex.com>

On Wed, 06 Dec 2000, Tripp Lilley wrote:
> While researching this whole /etc/mtab vs. /proc/mounts issue, I came
> across the following post:
> 
> 	http://www.uwsg.iu.edu/hypermail/linux/kernel/0010.3/0243.html
> 
> which points out some of the "dangers" in using /proc/mounts, and
> specifically mentions the /dev/root issue. Not sure if it's 100%
> applicable, but it might be a good starting point :)
> 
> 
> On Mon, 4 Dec 2000 tyson@rwii.com wrote:
> 

Thanks,
I'm not yet sure how applicable this is because I'm using busybox mount that as
I have discovered recently doesn't keep mtab at all. It always looks into
/proc/mounts. Since proce/mounts reports /dev/root mounteds on / too I'm
confused, mounting root fs rw doesn't change anything but if I'm using /dev/ram0
as root /proc/mounts and mount both report it correctly. At this point I'm at
loss to explain this.

- Levi

-- 
Levi Khatskevitch
CTO
Cachier, Corp.
575 Grand St., Suite E306
New York, NY 10002


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

       reply	other threads:[~2000-12-06  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1001206074454.1800T-100000@mail.perspex.com>
2000-12-06  7:33 ` Levi Khatskevitch [this message]
2000-12-04 19:52 nftl/DoC Mill. root fs question Levi Khatskevitch
2000-12-04 21:36 ` Ronald G Minnich
2000-12-04 21:40   ` tyson
2000-12-04 22:05     ` Levi Khatskevitch
2000-12-04 21:51   ` Jan Danielsson
2000-12-04 22:08     ` Levi Khatskevitch

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=00120602385104.02531@mrserver \
    --to=lkhatskevitch@cachier.com \
    --cc=linuxbios@lanl.gov \
    --cc=mtd@infradead.org \
    --cc=tlilley@perspex.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.