> On Sun, 24 Jan 1999, Christopher Masto wrote:
>
> > The old "unable to mount /, specified device does not match root
> > device" on booting. My /etc/fstab had (working with -current from
> > just a few weeks ago):
> >
> > /dev/wd0s1a / ufs rw 1
On Sun, 24 Jan 1999, Christopher Masto wrote:
> The old "unable to mount /, specified device does not match root
> device" on booting. My /etc/fstab had (working with -current from
> just a few weeks ago):
>
> /dev/wd0s1a / ufs rw 1 1
>
> I thoug
On Sun, Jan 24, 1999 at 03:46:53AM -0500, Christopher Masto wrote:
> That's all that I noticed. I will try another update to get Matt's vm
> fix.. if it still panics, I'll get a proper backtrace. And yes, I'm
> using INVARIANTS.
Well, I resupped and rebuilt, and did the thing that crashed it
bef
Christopher Masto wrote:
> After fixing that, I ran into problems with libcrypt. Specifically,
> everything seems to be linked against libcrypt.so.3
This has been fixed. Please resup.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majord...@freeb
I just finished a make world and kernel build from sourced cvsuped at
around Jan 23, 21:00 EST. There were no build problems, and I saw the
crypt backout was in, so I installed it. System seems to be working
so far, but with the following suprises:
The old "unable to mount /, specified device do
