On Tue, 2009-02-10 at 20:08 +0530, Rahul Sundaram wrote: > John Summerfield wrote: > > > The problem, as has already been mentioned and which you seem to have > > overlooked is that when an administrator finds it's locked up, it's too > > late to fix it. > > If it is really locked up, the current change won't affect you. A half > struck system, it is matter of restarting and resetting it. You can > avoid that even, if you read up what has changed as any good > administrator should. Actually, I think the real issue here is that we leaving something the same because a sysadmin (of all people) didn't bother to read the release notes before installing an OS, and then when things go wrong (presumably on a 'production' system) they are going to whine that they didn't know until it was too late. This change hasn't been snuck into fedora without a heads up, and regardless of how you feel about the change, complaining that the administrator was unaware seems a little far fetched. R -- "It's a fine line between denial and faith. It's much better on my side" -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
