From: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Why is it always "fast boot" in 2.11BSD?
Date: Sat, 28 May 2022 13:39:03 +0200 [thread overview]
Message-ID: <YpIJ171xybiS0uy2@grumpf.hope-2000.org> (raw)
In-Reply-To: <Yo9nacaVxsHjs2v3@mbsks.franken.de>
On Thu, May 26, 2022 at 01:41:29PM +0200, Matthias Bruestle wrote:
> I have noticed, that 2.11BSD is in all cases where I looked set
> to "fast boot", which AFAIK means no fsck of at least /. I found
> nobody talking about this or providing information about how to
> change it to "slow boot" with a proper check, which is now normal.
>
> Is there a reason why it is not possible to deactivate fast boot?
> Or is it just that nobody bothered to do it?
Interesting. When I played with 2.11BSD a few years ago I found that it
only did a "fast" boot if rebooted with "shutdown -rf". A cold boot
would always drop into single user and allow running fsck manually.
IIRC /boot or even one of the earlier bootstrap stages would check a
certain memory location for certain values, which the kernel(?) would
place there in the reboot syscall. As I wanted to always force a fast
boot, I had this in my simh.ini to force a fast boot:
d 157772 177777
d 157774 002400
d 157776 000000
If you're using a simulator I wouldn't be suprised if it does that
automatically nowadays, of perhaps 2.11BSD was patched a while back to
reverse that behaviour.
I don't remember what these values do, though. And you want to do the
opposite anyway. But perhaps this helps you find out more.
Hans
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
next prev parent reply other threads:[~2022-05-28 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:41 [TUHS] " Matthias Bruestle
2022-05-28 11:39 ` Hans Rosenfeld [this message]
2022-05-28 13:14 ` [TUHS] " Matthias Bruestle
2022-05-28 22:35 ` Matthias Bruestle
2022-05-29 12:12 ` Matthias Bruestle
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=YpIJ171xybiS0uy2@grumpf.hope-2000.org \
--to=rosenfeld@grumpf.hope-2000.org \
--cc=tuhs@tuhs.org \
/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).