Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 May 2003 18:55:06 +0200
From:      Jalle <defacto@home.se>
To:        kmidtset@c2i.net, Robert Storey <y2kbug@ms25.hinet.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: shutdown -p now
Message-ID:  <5.2.1.1.0.20030521184414.00b41110@archimedes.rsn.bth.se>
In-Reply-To: <20030521131047.GA243@tina.la3sg.net>
References:  <20030521201502.0f00f07b.y2kbug@ms25.hinet.net> <20030521092225.5a6a4442.y2kbug@ms25.hinet.net> <3.0.5.32.20030520204643.01366cc0@sage-one.net> <20030521201502.0f00f07b.y2kbug@ms25.hinet.net>

next in thread | previous in thread | raw e-mail | index | archive | help
<snip>
> >  root@sonic:/sys/i386/conf> /usr/sbin/config CUSTOM2
> >  config: CUSTOM2:156: devices with zero units are not likely to be correct
</snip>

Ah! I got these errors too some time ago. Apparently, I had been a little 
careless while cvsup:ing at that time.
I'm on a 4.8-STABLE system, and I accidentally cvsup:ed with the wrong 
cvsup file, ending up with -CURRENT
code all over the place. No good! So, if you've accidentally fetched some 
-CURRENT code to your -STABLE
system, that might be it. Try cvsup to your current system and try again...

<snip>
> >
>Further, "shutdown -p now" does not work yet on r5.0
>IE: stay with r4.8 if you want shutdown -p now to work.
>regards
>Kjell
</snip>

Doesn't it? I think it does, I tried it some time ago, but i've been wrong 
before! =o)

<snip>
> > I decided to stop there rather than compile a possibly flakey kernel. Is
> > this error message anything to worry about, or am I doing something wrong?
</snip>

Good choice... in the long run. But keep in mind that FreeBSD is made for 
Tinkering(TM).
You could (should) always back up a functional kernel before installing new 
ones. That way,
you don't have to worry about screwing up. You could always go back and 
undo/redo.

Don't know if any of this helps, but anyways...

/Jalle 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.1.1.0.20030521184414.00b41110>