From owner-freebsd-libh Mon Apr 22 13: 7:32 2002 Delivered-To: freebsd-libh@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 25FFF37B400 for ; Mon, 22 Apr 2002 13:07:30 -0700 (PDT) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.12.2/8.12.2) with ESMTP id g3MGaV7W010096; Mon, 22 Apr 2002 09:36:32 -0700 (PDT) (envelope-from jkh@winston.freebsd.org) To: The Anarcat Cc: libh@FreeBSD.ORG Subject: Re: hfstab and extending getfsent(3) In-Reply-To: Message from The Anarcat of "Mon, 22 Apr 2002 02:55:34 EDT." <20020422065534.GE326@lenny.anarcat.dyndns.org> Date: Mon, 22 Apr 2002 09:36:31 -0700 Message-ID: <10095.1019493391@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It would be interesting to extend getfsent(3) into functions that > would write to fstab too. I don't know if it would be appropriate to > write those functions in C and backport them to the base, but I think > it's worth a shot. sysinstallNG needs to write to /etc/fstab at any rate. If those FreeBSD losers would just adopt Netinfo for all this kind of information, there would already be a central datastore and an API for writing to it! :-) OK, sorry, too much crack this morning. Seriously, this sort of thing would be good - the lack of a programmatic interface for writing fstab entries has been commented on and complained about before. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message