Date: Sun, 9 Jul 2000 21:56:27 -0500 (EST) From: Jonathan Smith <jonsmith@dragonstar.dhs.org> To: "Dan O'Connor" <dan@mostgraveconcern.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Previous Message on /etc/defaults Message-ID: <Pine.BSF.4.21.0007092148560.95124-100000@dragonstar.dhs.org> In-Reply-To: <036c01bfea19$417daae0$0200000a@danco>
next in thread | previous in thread | raw e-mail | index | archive | help
> My $0.02: I thinks it's a good idea for /etc/defaults/whatever to set the > defaults and then load any customizations for /etc/whatever. Personally, I > *like* having small /etc/whatever files with just my entries to worry about. > And if we call defaults from the /etc copy, you have to first have an /etc > version, or else the defaults don't get loaded at all... *grins* That's your choice, I'm not saying to take it away from you. We already have to have an etc version, either that or sysinstall generates it. Either way, it gets created. <history> I started with slackware almost 4 years ago.... I personally had a nightmare getting things done in the sysv way of things, all the various config files just get the system started. Then, one of the local 'experts' had me try FreeBSD. (This was in the 2.2.x days ;) I had one main config file that I had to edit that listed nearly [if not] all of the main options to get my machine up. I think that was the first (and one of the biggest) reasons I stayed with FreeBSD. </history> Since then, I've been frustrated by the defaults directory; however, I do realise it's value in large networks. I don't want that removed, but I think it'd be nice to be able to remove it more easily. As I said, my suggestion also makes it quite obvious that the defaults are just that. j. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007092148560.95124-100000>