F10 beta: No xorg.conf, where to tweak Synaptics pad?

[Scott Robbins]

On Sat, Oct 11, 2008 at 03:31:58AM +0530, Rahul Sundaram wrote:
> Scott Robbins wrote:
>> So, that's my suggestion.  Include an UPDATING that gets updated when
>> various changes that might surprise people are made.  What might
>> surprise people is of course, subjective, but....
>
> Why do you think that a complete new file like this would be read by  
> more people than the better known release notes which already has a  
> section specific to upgrades?

I guess it's a habit from FreeBSD.  Everyone knew that it should be read
before updating.  (FreeBSD has a more distinct separation between system
and 3rd party programs as well, so there is also a /usr/ports/UPDATING.)

Also, I think that if it were publicized, for example, if something is
mentioned there, and then someone posts, for example, on Fedora forums
about it, someone else will post back, Didn't you read UPDATING?  

Lastly, the idea (again it's certainly easier said than done) is that
this would cover major, perhaps system breaking changes.   For example,
to make one up...

Changelog

programX updated 2.1.1.2
programY updated 2.1.1.4
Majorchange in NetworkManager--if you don't follow steps X, Y, and Z it
won't work).

Then in UPDATING

<date whatever> NetworkManager has been changed. You must now do X, Y,
and Z before it will run properly. 

So, I think that if it were done like that, and confined to major
changes (again subjective--for example, for me, tying sound to
ConsoleKit was major, for Gnome users it probably wasn't), people would
begin to read it. 


-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Willow: I just talked to Buffy, and yeah, I think she's feeling a
little... insane. No, not bitchy crazy, more like homicidal 
maniac crazy. So I told her to come see you, 'kay?