mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: <rol@as2917.net>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: Re: Why is /dev on a different filesystem ? [Kernel 2.6.20.3]
Date: Wed, 21 Mar 2007 22:32:45 +0100	[thread overview]
Message-ID: <jeslbyp9j6.fsf@sykes.suse.de> (raw)
In-Reply-To: <04ea01c76bed$11b0d050$4b00a8c0@donald> (Paul Rolland's message of "Wed, 21 Mar 2007 20:13:50 +0100")

"Paul Rolland" <rol@as2917.net> writes:

> and df -a reports :
> [root@host-181 src]# df -a
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hda1              7936256   3105556   4421048  42% /
> proc                         0         0         0   -  /proc
> sysfs                        0         0         0   -  /sys
> devpts                       0         0         0   -  /dev/pts
> tmpfs                   517632         0    517632   0% /dev/shm
> /dev/hda5             61787140    237360  58360480   1% /usr/local/witbe
> /dev/hda2              4956316    142292   4558192   4% /var/log
> none                         0         0         0   -
> /proc/sys/fs/binfmt_misc
>
> So, obviously, /dev is on /, but the stat(2) says no.
> Who is right, and where is the bug ?

Try cat /proc/mounts, apparently when /dev was mounted /etc/mtab wasn't
updated appropriately.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      parent reply	other threads:[~2007-03-21 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 19:13 Paul Rolland
2007-03-21 19:20 ` Valdis.Kletnieks
2007-03-21 19:30   ` Paul Rolland
2007-03-21 19:37 ` Greg KH
2007-03-21 19:59 ` David Schwartz
2007-03-21 20:58 ` Alistair John Strachan
2007-03-21 21:32 ` Andreas Schwab [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=jeslbyp9j6.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rol@as2917.net \
    /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

all inboxes | Powered by JetHome®