Re: some oddities with fsck and boot -s

[Bill Hacker <wbh@xxxxxxxxxxxxx>]

Matthew Dillon wrote:

> :
> :hi folks,
> :
> :I have some questions, first when I do
> :
> :$ fsck -y
> :** /dev/da0s1a (NO WRITE)
> :** Last Mounted On
> :                   ^^^^^^^^^^
> :** Phase 1 - Check Blocks and Sizes
> :[...]
> :
> :** /dev/da0s1e (NO WRITE)
> :** Last Mounted On
> :                   ^^^^^^^^^^
> :** Phase 1 - Check Blocks and Sizes
> :[...]
> :
> :Last Mounted On is always empty
>
>     I've noticed this too.  The last mounted on information is stored in
>     the superblock.  I think I did something to it a while ago (like a year)
>     that stopped it from doing the writeback.  I'll take a look at it but
>     I don't consider it a critical issue.
>
> :another thing is sh's default PATH (just /bin and /usr/bin) after
> :booting to single user mode via boot -s; can we add /sbin and /usr/sbin?
>
>     I'll fix the /bin/sh path problem right now.  That's always bothered 
>     me.
>
> 					-Matt
> 					Matthew Dillon 
> 					<dillon@xxxxxxxxxxxxx>

/usr/sbin (where /usr is generally not yet mounted) may be problematic.

One might mkdir /usr/sbin directly onto the root mount-point, and 
populate it,
as it will be overlaid when the 'real' /usr mount is fscked and mounted.

But whatever lives there would have to be static compiled, IIRC.

(Sez  he who has been known to make copies of such needful things into 
/ubin, /ulbin, /usbin, /ulsbin).

YMMV,

Bill Hacker