>the previous default of "no" is now changed to "yes".

But why exactly has the default been changed to a value that's obviously wrong 
for the majority of Linux systems in existence? Perhaps instead the tiny 
minority of systems that are used in a workstation-like fashion, where this 
behavior might *arguably* make some kind of sense, could set the option to 
yes, and all other systems could benefit from a sensible default that doesn't 
break things for dubious reasons? Just a thought.

Reply via email to