I've just been considering one of the security flaws that Windows has, and wondering how Linux contends with the same issue: On Windows, it was always a problem that you might install something (intentionally or not) that would replace a system file that it shouldn't be able to. On Linux, if you were to try and install a file that wanted to replace some system file, or some file belonging to another package that may be just as important, can you *expect* the install process to remove the original owner package? Or is it possible to stuff up some file belonging to another package, silently? e.g. If I was to install silly-game.rpm and I saw comments about removing kernel(something) in the list of things to do during the intall, I'd abort. (Not that that'd help those who routinely do "yum -y install" without due care.) I think the case that installing a package that generates a file during installation, can leave a file that's not owned by the package (as far as YUM and RPM databases are concerned). -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
