Date: Sat, 24 Jul 1999 22:36:30 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Andrzej Bialecki <abial@webgiro.com> Cc: Mark Huizer <freebsd@xaa.iae.nl>, freebsd-current@FreeBSD.ORG Subject: Re: Arg! MFS broken Message-ID: <47364.932848590@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 24 Jul 1999 22:28:09 %2B0200." <Pine.BSF.4.05.9907242226470.43777-100000@freja.webgiro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.05.9907242226470.43777-100000@freja.webgiro.com>, Andrze j Bialecki writes: >On Sat, 24 Jul 1999, Mark Huizer wrote: > >> > >> > > MFS is badly broken when used in a diskless configuration. I am trying >> > > to track it all down but it is very, very frustrating. >> > > >> > > Also BOOTP seems to be broken -- rootdev is not being setup any more >> > > and I can't figure out which commit broke it. >> > >> > I'm sorry, I don't have either in my arsenal currently. >> I found that trying to build a PicoBSD floppy was a sure way of crashing >> my current box :-( Perhaps that is a nice testing environment? > >Then you should investigate this further, because it looks like some bug >in vn(4) code - picobsd build doesn't do anything unusual except that... I built a release (which also uses vn(4)) yesterday, so to some extent of the concept vn(4) works. I'm very interested in a traceback of this panic... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! 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?47364.932848590>