Bill Sommerfeld wrote: > On Mon, 2007-08-06 at 20:35 -0700, Jan Setje-Eilers wrote: > >>> I think this addresses my fears in the short term, though we do need to >>> see a revised spec which nails down specifics of how files may be >>> excluded from the archive. >>> >> I suspect it should be all editable files as well as all driver.conf >> files (editable or not) in the archive. I'll gather some data on this >> and will update the spec accordingly. >> > > You mentioned in a side conversation that you had heard that there was a > good reason why we packaged many driver.conf files as non-editable but > still occasionally told people to edit them anyway. > > If at all possible it would be very helpful to chase down the origin of > that folklore, as what I'm hearing about likely changes coming in the > packaging/patching/upgrade space suggests that the ground underneath > that folklore is about to shift fairly dramatically. > > - Bill > Oh boy, did you just turn over a slimy rock.
The reason that driver.conf files were separated out was so they could be edited. Otherwise we could just hardwire the information in the driver itself. However, there was a *big* discussion about where they should be. One side was that they should be in the same filesystem as the driver (root vs. usr). The other side (mine) was that they should all be in /root so they could be editted. I recall this was a bigger issue than one might think. Of course, the real issue is "editable or not", rather than "where". The real question should be "if they aren't editable, why do we have them"? - jek3
