From owner-freebsd-current Sat Jul 24 13:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id C960714DB2 for ; Sat, 24 Jul 1999 13:46:11 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 11C951913; Sat, 24 Jul 1999 22:45:04 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 0EA2D49DF; Sat, 24 Jul 1999 22:45:04 +0200 (CEST) Date: Sat, 24 Jul 1999 22:45:04 +0200 (CEST) From: Andrzej Bialecki To: Poul-Henning Kamp Cc: Mark Huizer , freebsd-current@FreeBSD.ORG Subject: Re: Arg! MFS broken In-Reply-To: <47364.932848590@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Poul-Henning Kamp wrote: > 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... If interrupted at (in)appropriate place, picobsd build process can leave vn(4) configured but left without underlying file. I shoudl probably test various scenarios here, like: * vn configured, remove file, unconfig vn * vn configured, mounted, unconfigure vn etc, etc.. vn(4) should be foolproof , at least it shouldn't panic the system. But you're right, we need a trace first... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message