The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [pups] 2.11BSD device config trouble
Date: Thu,  1 May 2003 08:49:55 -0500	[thread overview]
Message-ID: <YMWNFzDR0MYr.VjBrnZ0N@128.100.27.218> (raw)

Carl Lowenstein:

  Isn't this really true of Unix systems of any age, when doing fsck
  on a mounted root file system?

Some middle-elderly BSD systems--4.1 and possibly 4.0--
managed the buffer pool in such a way that the super-block
of a mounted file system was kept in the original buffer,
with device and block number correctly stored in the struct
buf header.  Hence if fsck wrote to the block device rather
than the raw one, the super-block came out right even when
checking a mounted file system; in particular there was no
need to reboot.

This convenience was abolished in either 4.2 or 4.3 (I am
travelling right now and cannot check manuals and 
sources).  I never quite understood why, though I never
looked at the source code in the later systems.  The
scheme found in most current systems, in which the
root starts out read-only, is a better idea anyway.

Norman Wilson
Toronto ON (normally)





             reply	other threads:[~2003-05-01 13:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 13:49 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 19:14 Michael Sokolov
2003-05-01  4:04 Steven M. Schultz
2003-05-01  3:30 Carl Lowenstein
2003-05-01  3:48 ` Gregg C Levine
2003-04-30 18:43 Steven M. Schultz
2003-05-01  9:24 ` Jochen Kunz
2003-04-30 16:03 Steven M. Schultz
2003-04-30 15:56 Steven M. Schultz
2003-04-30 16:58 ` Jochen Kunz
2003-04-29 22:48 Steven M. Schultz
2003-04-30  8:24 ` Jochen Kunz
2003-04-30 13:40   ` David Evans
2003-04-30 16:23     ` Jochen Kunz
2003-04-30 16:59       ` David Evans
2003-04-29 21:54 Jochen Kunz

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=YMWNFzDR0MYr.VjBrnZ0N@128.100.27.218 \
    --to=norman@nose.cs.utoronto.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).