Date: Mon, 25 Jan 1999 09:23:30 +1000 From: "Harry Starr" <starr3@gccs.com.au> To: "Mike Smith" <mike@smith.net.au> Cc: "Daniel C. Sobral" <dcs@newsguy.com>, "current" <freebsd-current@FreeBSD.ORG> Subject: Re: Problem booting using /boot/loader Message-ID: <002b01be47f0$8dea2c90$0a9811cb@gccs.com.au>
next in thread | raw e-mail | index | archive | help
Just to let you know that re-cvsup'ing and building /boot has FIXED the problem. Thanks, Mike. Harry. ----- Original Message ----- From: Mike Smith <mike@smith.net.au> To: Harry Starr <starr3@gccs.com.au> Cc: Daniel C. Sobral <dcs@newsguy.com>; current <freebsd-current@FreeBSD.ORG> Sent: Monday, January 25, 1999 3:23 AM Subject: Re: Problem booting using /boot/loader >> Yep! >> >> /boot/loader.old works OK! (dated Jan 11) >> >> /boot/loader (Jan 24) fails. >> >> And yes, the kernel was recompiled from the same cvsup sources. >> >> Definitely looks like something broke in the current loader. > >There was a window of a few hours where the 4-current loader was broken >due to a typo on my part. I forgot to merge the fix back into 3-stable >(which I've just now done). > >Please resup/rebuild/reinstall the loader. Also note that for those of >you that had to change your /etc/fstab - you'll have to change it right >back. 8) > >If you have to push through a loader that has this bug, >'set root_disk_unit=0' for eg. a system with root on wd0 or da0 will >avoid the broken code. > >-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002b01be47f0$8dea2c90$0a9811cb>