Date: Sun, 15 Feb 1998 15:11:41 +1100 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, toor@dyson.iquest.net Cc: committers@FreeBSD.ORG, dyson@FreeBSD.ORG, eivind@yes.no, wollman@khavrinen.lcs.mit.edu Subject: Re: devfs persistence Message-ID: <199802150411.PAA16481@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> Use mfs. >> >That is a non-starter, and only adds yet another layer of complexity. Devfs >is a good idea for certain applications. (Have *you* actually used MFS in >an embedded application, with heterogeneous products, mostly (only) to support >device nodes?, answer: it is a kludge.) No. When I last worked on an embedded system, a minimal mfs image (about 32K) would have been several times larger than the code :-). What practical disadvantages does it have besides ones shared by specfs, lack of persistence, and possibly slightly larger bloat than for devfs? If the system is an nfs client, then you can use /dev/vn to mount ffs images kept on the server to get persistence and avoid mfs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802150411.PAA16481>