Date: Sun, 19 Apr 1998 21:39:09 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: rotel@indigo.ie Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Discussion : Using DHCP to obtain configuration Message-ID: <199804192139.OAA14350@usr08.primenet.com> In-Reply-To: <199804191102.MAA00294@indigo.ie> from "Niall Smart" at Apr 19, 98 12:02:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Oh.. and while I'm dreaming, how about using portalfs or similar as > > > > such: mount /etc with portalfs and have a translator present all of > > > > the data from the database in traditional format. > > > > > > This is a *terrifically* cool idea! > > Would this be read-only or read-write? > > Read-write sounds tough. It is harder, but not significantly difficult. The problems lie mostly in comment fields in files like /etc/protocols; if you want to maintain them, you will need to modify the getprotoent(3) function to allow them to be returned. I view the need to provide this as a need to support statically linked programs that are linked against a legacy libc. This is mostly a problem for BSD code alone, though a much smaller subset of the databases are accessed by Linux and other emulated platforms. Most of this code is not read/write code, since there is not a libc(3) mechanism for writing password entries, /etc/services or similar files, etc.. The databases are themselves predominantly read-only, and tend to change infrequently (with the exception of the accounts database, which is already using this model and importing/exporting; that code would be easy to roll in). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804192139.OAA14350>