On Wed, Jan 1, 2014, at 06:17 PM, Theo de Raadt wrote: > I think dmassage being unmaintained for 12 years, and this issue just > coming up now, probably says a lot about that "type" of person. It's > a type of person who can't fix dmassage, and then, sends us a mail. > Sorry, but it's the truth.
Very little, if anything, has changed in either the kernel configuration procedure or the format of a kernel's dmesg in the last 12 years. So this is more a case of "if it ain't broke, don't fix it." If anything has changed, it's what device drivers you can rip out and still get the kernel to compile. I will admit most of the reasons for doing so today are a lot less compelling in years past, when every byte of RAM counted for something (best example being a couple of non-PCI 486 systems when you could cut the kernel size almost in half by not putting in all those useless PCI drivers). Today, you have to try to find something with less than 128MiB of RAM in it, and the odds are in your favor of having more even if it's a dumpster rescue. The only use I can think of might be security (it's much harder to use an external USB storage device if the kernel is compiled not to look for them) but I'm sure there are "better ways" to do even this. -- Shawn K. Quinn skqu...@rushpost.com
