In article <20060924213728.5d0f37d7.smb@cs.columbia.edu>,
Steven M. Bellovin <smb@cs.columbia.edu> wrote:
>On Sun, 24 Sep 2006 21:29:41 -0400, Michael Lorenz <macallan@netbsd.org>
>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hello,
>> 
>> On Sep 24, 2006, at 20:18, Steven M. Bellovin wrote:
>> 
>> > I received the following messages from init after upgrading to 4.99.3
>> > from this afternoon:
>> >
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for runlevel
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port system 
>> > boot
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port system 
>> > down
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for runlevel
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port console
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE1
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE2
>> > Sep 24 20:09:17 berkshire init: can't add utmpx record for port ttyE3
>> >
>> > Was I supposed to have tweaked something?  I see nothing in UPDATING
>> > saying what to do.
>> 
>> is / still read only for some reason?
>> 
>This was a straight, multi-user boot -- I assume that root was mounted
>read-write before those happened...  (For what it's worth (and for odd
>reasons), I did the upgrade by doing 'build.sh release' and burning a CD,
>so I went through whatever sysinst wanted to do.)

When do you mount /var?

christos