Devuan considers machine IDs

Re:Devuan considers machine IDs by mirimir on Saturday March 30, 2019 @11:35AM (#19529916)

Because the machine-id by default never changes after OS installation.

[ Parent | on HN ]

Re:Devuan considers machine IDs by swinglock on Saturday March 30, 2019 @11:45AM (#19529973)

Neither does a file Chrome generates. Not even if reinstalled.

[ Parent | on HN ]

Re:Devuan considers machine IDs by mirimir on Saturday March 30, 2019 @11:57AM (#19530038)

Huh?

Even if you do

    $ sudo apt-get -y purge chrome

[or whatever its package name is]?

And if necessary, find and delete everything that it created.

[ Parent | on HN ]

Re:Devuan considers machine IDs by pantalaimon on Saturday March 30, 2019 @12:33PM (#19530273)

apt doesn't know about any file the application might have ever created in your home directory.

[ Parent | on HN ]

Re:Devuan considers machine IDs by ChristianBundy on Saturday March 30, 2019 @12:54PM (#19530424)

> And if necessary, find and delete everything that it created.

[ Parent | on HN ]

Re:Devuan considers machine IDs by mirimir on Saturday March 30, 2019 @01:46PM (#19530714)

Actually, apt does a pretty good job at finding stuff. Sometimes it can't delete, but it warns you about that.

[ Parent | on HN ]

Re:Devuan considers machine IDs by Evidlo on Saturday March 30, 2019 @02:15PM (#19530855)

Apt only knows about the files that are listed in the package.

[ Parent | on HN ]

Re:Devuan considers machine IDs by mirimir on Saturday March 30, 2019 @02:41PM (#19530996)

Sure, but then that means that honest packages should document all files that the software can be configured to created automatically. Or at least, all but user-specified ones.

[ Parent | on HN ]

Re:Devuan considers machine IDs by JohnFen on Sunday March 31, 2019 @06:32PM (#19538864)

In Linux, I can find and nuke everything that Chrome (or any other app) generates.

[ Parent | on HN ]