]] Ludovic Rousseau | The /etc/reader.conf contains a "warning": | # Do NOT edit this file directly but use update-reader.conf(8) instead. | | update-reader.conf(8) checks that the /etc/reader.conf contains the line: | ### This file is automatically generated by update-reader.conf | So a config file written by hand from scratch is _not_ overwritten.
Sure, but that's not the wording in policy, it is that you must preserve user changes. :-) | What should the update-reader.conf if the file have been manually | modified? | | Do you have an example of an update-foo command that does what you | request for? Either aborting if the file is modified (with a sensible error message) or not keeping reader.conf in /etc would both be acceptable solutions. update-rc.d and update-passwd handle in-/etc updates. As an example of something storing the result in /var, take a look at update-updmap for instance. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
