Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.development
Subject: Re: any chance of...
Date: 31 Mar 93 22:19:07
Organization: Kernel Hackers 'r' Us
Lines: 26
Message-ID: <CGD.93Mar31221907@eden.CS.Berkeley.EDU>
References: <1993Mar30.163132.6284@cs.wisc.edu> <1pacj7INNqid@fstgds01.tu-graz.ac.at>
<1pdm8n$3la@mudos.ann-arbor.mi.us>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: mju@mudos.ann-arbor.mi.us's message of 31 Mar 1993 22:07:03 -0500
In article <1pdm8n$3la@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
> (This could actually be an advantage, if the driver was
>written such that it could be used as a tmpfs driver in a production
>kernel. Two birds with one stone...)
there already is MFS.
however, the problem here is not mounting the MFS, even as root,
the problem is getting the MFS created *before* the kernel
is booted.
the kernel is responsible for mounting root, and it's irrational
to put the mfs-creation and setup code in the kernel...
what we need is a standalone MFS creator, and a way to pass
a pointer to this MFS to the kernel...
chris
who would work on such a beast, but knows little about 386 low-level stuff,
and who realizes he wants to learn less and less the more and more he learns.
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass