> > This is actually more a question of where to store the flag than
> > anything else.
>
> /boot/loader.conf perhaps, but how does the loader know that the previous boot
> failed so that it knows to fall back? This is much harder, as a failed kernel
> boot usually results in a hang or an instant CPU reset.
I had always planned to write a fixed-size file to disk (probably 512
bytes) and then implement "overwrite only" write support in the various
filesystems to allow us to use it as a "persistent" environment store,
eg. have a 'save <foo>' keyword which would update the persistent store
with the '<foo>' variable. This would avoid the bloat that block
allocation, directory creation etc. would entail with "real" write
support, whilst allowing us most of the desirable features.
All of the primary boot filesystems (ffs, nfs, tftp, fat, ext2) could
handle this with trivial modifications.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
