[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CFD: XMLification of NOTES
- Subject: CFD: XMLification of NOTES
- From: kris at obsecurity.org (Kris Kennaway)
- Date: Tue Mar 30 21:44:45 2004
On Wed, Mar 31, 2004 at 07:27:48AM +0200, Alex Keahan wrote:
> On Wednesday 31 Mar 2004 1:54 am, Dag-Erling Sm?rgrav wrote:
> > Alexey Zelkin <phantom_(_at_)_FreeBSD_(_dot_)_org> writes:
> > > On Tue, Mar 30, 2004 at 05:05:24PM +0200, Dag-Erling Sm?rgrav wrote:
> > > > NOTES is not intended as a list of supported device and options. We
> > > > have src/sys/conf/files* and src/sys/conf/options* for that.
> > >
> > > Strange. IMO LINT was existed for exactly this reason
> > Your opinion does not matter. The purpose of LINT is to cover as much
> > code as possible. Why do you think it's called LINT?
> Why doesn't his opinion matter?
> Perhaps my opinion does not matter either, but as a developer and
> long-time FreeBSD user, I don't think that XMLification of NOTES is
> such a bad idea.
> Having said that, I can also see why some developers would be opposed
> to the idea. Apart from neophobia and an obligation to fight to keep
> Unix pure, simple and free from modern-day buzzword nonsense, the main
> reason for the hostility and ridicule with which Alexey's idea was treated is
> the simple fact that an XML kernel configuration tool would likely shift the
> blame for misconfigured kernels from the end-user to the developer.
What an odd comment. You sound pretty sure of yourself, though...on
what basis do you make this assertion?
> Whereas previously a developer could add a new option or remove an
> existing one without having to think twice about it, a strict XML schema
> would force the developer to adhere to higher standards, explicitly evaluate
> and list the dependencies and possible incompatibilities and reconcile the
> new options with the multitude of the existing configuration possibilities.
> A good thing for the end-user? Certainly. At the moment, a user who has
> the misfortune of breaking his system by adding an "option FOO" to his
> kernel without the required corresponding magical "option BAR" will be
> told to "go read the mailing list archives", "go read UPDATING" or simply
> "go away".
> With an XML-based dependency system in place, the blame would be
> entirely on the developer who had forgotten to update the NOTES file or
> had done so incorrectly.
> An XML-based list of supported devices and options would also allow the
> creation of a kernel configuration tool, similar to what Linux has had for as
> long as I can remember. Again, a good thing for the end user.
Don't change the topic. XML is not required for any of that, and
someone could just as easily write those tools without it. Similarly,
it's just as wrong to assume that changing to XML will magically cause
all these tools to appear.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20040330/c07b0745/attachment.bin