[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: state of /etc/profile



Hi Greg,

> The /var/lib/dpkg/info/base-files.postinst script contains code that will

> modify /etc/profile if the first argument is "configure" and the second

> argument isn't the empty string.

>

> I don't know what would cause those particular arguments to be passed to

> that script.

>

> In order for that modification to happen, the existing file's MD5 checksum

> is compared against the one found in /usr/share/base-files/.

>

> So... either your /etc/profile doesn't have the right MD5 checksum, or

> else nothing is calling that postinst script with the correct arguments.

>


so, if that is true, what you say (or if I understood you correctly), then a reinstall or upgrade of the package "base-files" should overwrite /etc/profile if the md5sum is different.


Well, it did not. I tried "apt-get --reinstall install base-files" and nothing changed.


md5sum /etc/profile
40f068da82e55a304d8baf245600b636  /etc/profile

md5sum /usr/share/base-files/profile
48a30a427d1794feb49f102b87ddce2b  /usr/share/base-files/profile

Without md5sum it can also be clearly seen, as both files got different content.


I  believe, it might be more what Dan said: Overwriting some existent special configuration files, might break the system of people. So they are not changed and the user/admin can later decide, if he wants to overwrite these files or not.


Additionally (but can not prove it), it may be, that a missing file will be renewed during upgrade (did not test this!).


Can be I am fully wrong, maybe someone knows more.


Have fun!


Hans 

 

 


Reply to: