linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re[4]: fsck root fs: fsck, devfs, /proc/mounts miscooperate.
Date: Wed, 29 Aug 2001 22:21:54 +0300	[thread overview]
Message-ID: <19318081209.20010829222154@port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <200108291427.f7TERJj07458@vindaloo.ras.ucalgary.ca>
In-Reply-To: <22075604.20010829095413@port.imtp.ilyichevsk.odessa.ua> <20010829021304.D24270@turbolinux.com> <6410958637.20010829151417@port.imtp.ilyichevsk.odessa.ua> <200108291427.f7TERJj07458@vindaloo.ras.ucalgary.ca>

Hello Richard,

Wednesday, August 29, 2001, 5:27:19 PM, you wrote:
RG> You say you are running devfs. Well, if that's the case, you can
RG> simply do:
RG> # fsck /dev/root

RG> because devfs makes /dev/root a symbolic link to the root FS device.
RG> Magic.

Thanks! It works!
However, I still think "fsck /" behavior isn't right - people who don't use
devfs won't be able to check root fs without fstab entry for it.
This seems fixable - "mount -o remount,rw /" works without /dev/root
trick, right?

Best regards,
VDA
--
mailto:VDA@port.imtp.ilyichevsk.odessa.ua
http://port.imtp.ilyichevsk.odessa.ua/vda/



  parent reply	other threads:[~2001-08-29 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  6:54 fsck root fs: fsck, devfs, /proc/mounts miscooperate VDA
2001-08-29  8:13 ` Andreas Dilger
2001-08-29 14:27   ` Re[2]: " Richard Gooch
2001-08-29 12:14 ` VDA
2001-08-29 18:17   ` Andreas Dilger
2001-08-29 19:03   ` Richard Gooch
2001-08-29 19:21   ` VDA [this message]
2001-08-30 19:39   ` Re[2]: " Theodore Tso
2001-08-31 10:58   ` Re[4]: " VDA

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=19318081209.20010829222154@port.imtp.ilyichevsk.odessa.ua \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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).