Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Dec 2005 17:04:02 -0500
From:      "Matt Emmerton" <matt@gsicomp.on.ca>
To:        "John Baldwin" <jhb@freebsd.org>
Cc:        Scott Long <scottl@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: GENERIC and DEFAULTS
Message-ID:  <001f01c601c3$7ba43f50$1200a8c0@gsicomp.on.ca>
References:  <002d01c601b9$206f9940$1200a8c0@gsicomp.on.ca> <200512151609.58744.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Thursday 15 December 2005 03:49 pm, Matt Emmerton wrote:
> > I know this has been discussed ad nauseum, but here's my $0.02:
> >
> > Why not mark these entries as 'mandatory' in /usr/src/sys/conf/files*
> > instead?
> > This will cause config to error out if they are not specified in the
> > config, and handles the common case (normal users).
> > .
> > For those power users who really want to disable the devices, we should
> > smarten up the nodevice handling in config(8) to that (nodevice &&
> > mandatory) is not an error.
>
> What happens when you mark some of the files for a device mandatory but
not
> others?  How do you make an option that isn't listed in sys/conf/files
> mandatory?  After considering these questions and several others, the
> conclusion was reached that it was a lot simpler and less error prone to
use
> the same format for defaulting options on or devices on that we use to
turn
> them on in the first place: i.e. a config file.  If it really gets peoples
> panties all up in wads we can move the defaults files to /sys/conf (e.g.
> sys/conf/DEFAULTS.i386 or even sys/conf/defaults.i386).

Points taken; moving to private e-mail and/or -current for more in-depth
discussion.

--
Matt Emmerton




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001f01c601c3$7ba43f50$1200a8c0>