From owner-freebsd-current Sat Jul 24 13:39: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A589114CE2 for ; Sat, 24 Jul 1999 13:38:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA47366; Sat, 24 Jul 1999 22:36:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Andrzej Bialecki Cc: Mark Huizer , freebsd-current@FreeBSD.ORG Subject: Re: Arg! MFS broken In-reply-to: Your message of "Sat, 24 Jul 1999 22:28:09 +0200." Date: Sat, 24 Jul 1999 22:36:30 +0200 Message-ID: <47364.932848590@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , 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