>
> Try to pull in the commit I just did to syscons, I looks like I messed
> something up somewhere :-(
That seems to have fixed it. I get the startup and shutdown messages. I
didn't make it back to my console soon enough after rebooting to go straight
to singule-user mode, but I was able to s
In message <[EMAIL PROTECTED]>, Jonathan Fosburgh writes:
>On Friday 26 September 2003 01:13 pm, Cameron Murdoch wrote:
>> I have the same here from this morning's -current but I also see this on
>> boot up:
>>
>> *snip*
>> mounting root from ufs:/dev/ad0s2a
>> pid 87 (fsck_ufs), uid 0: exited on s
On Friday 26 September 2003 01:13 pm, Cameron Murdoch wrote:
> I have the same here from this morning's -current but I also see this on
> boot up:
>
> *snip*
> mounting root from ufs:/dev/ad0s2a
> pid 87 (fsck_ufs), uid 0: exited on signal 8
> pid 88 (fsck_ufs), uid 0: exited on signal 8
>
I notic
sages.
Cam
On Fri, 2003-09-26 at 17:16, Jonathan Fosburgh wrote:
> On Friday 26 September 2003 10:32 am, Shin-ichi Yoshimoto wrote:
> > Hi, After new kernel installing, I cannot boot -s.
> > This kernel always runs multiuser mode.
> >
> > What's happen ??
> I
On Friday 26 September 2003 10:32 am, Shin-ichi Yoshimoto wrote:
> Hi, After new kernel installing, I cannot boot -s.
> This kernel always runs multiuser mode.
>
> What's happen ??
I have the same thing from this morning's sources. Also, shutdown -s just
brings me back up
Hi, After new kernel installing, I cannot boot -s.
This kernel always runs multiuser mode.
What's happen ??
--
Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]>
http://diary.waishi.jp/~yosimoto/diary/
___
[EMAIL PROTECTED] mailing list
http://lists.