From: Matthias Bruestle <m@mbsks.franken.de>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Why is it always "fast boot" in 2.11BSD?
Date: Sat, 28 May 2022 15:14:55 +0200 [thread overview]
Message-ID: <YpIgT+YLJ/+/ulGq@mbsks.franken.de> (raw)
In-Reply-To: <YpIJ171xybiS0uy2@grumpf.hope-2000.org>
On Sat, May 28, 2022 at 01:39:03PM +0200, Hans Rosenfeld wrote:
> 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.
I use a quite basic simh.ini without fancy memory manipulations.
At the moment the behaviour is:
1) First boot => enter unix at : prompt => no fsck => root shell
2) ^D => "fast boot" => no fsck => multiuser
3) login + reboot => passed : prompt => no "fast boot" => fsck => multiuser
That is with the RA92 image provided with simh for the ESP32,
which contains a command to setup WiFi.
I found at minnie.tuhs.org/Distributions/Boot_Images/2.11_on_Simh
a version where Andru Luvisi has configured a 1MB RAM disk mounted
to /tmp for the temp file required by fsck. Needed to compile a new
kernel, but with the RAM disk fsck runs nicely. I put a # in front of
rwhod in /etc/rc to prevent it beeing started, but then it never went
into multisuser. No idea why.
> 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
Seems to be related to bootdev here:
73Boot from ra(0,0,0) at 0172150
: unix
Boot: bootdev=02400 bootcsr=0172150
But it looks always like this, with and without fastboot.
Thanks
Matthias
--
When You Find Out Your Normal Daily Lifestyle Is Called Quarantine
next prev parent reply other threads:[~2022-05-28 13:20 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 ` [TUHS] " Hans Rosenfeld
2022-05-28 13:14 ` Matthias Bruestle [this message]
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=YpIgT+YLJ/+/ulGq@mbsks.franken.de \
--to=m@mbsks.franken.de \
--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).