Updating my persistent liveslak modified my actual hard drive and OS
by afsouni from LinuxQuestions.org on (#5RVNV)
Hi everybody,
So I've been playing around with liveslak on a persistent USB for a week now, to get more familiar with it before actually installing it on my laptop. couple of hours ago I booted it up and as I usually do, did a quick update following these commands:
Code:slackpkg update gpg
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-systemAnd when I was done and booted in my actual OS which is fedora, I saw that it's hostname was changed to darkstar :) and there is probably more.
I know the problem should have arisen from one of the installation scripts from the update, but wanted to ask how did it get to my actual hard drive :)?
Aren't those scripts limited to their own root?
Appreciate any answer.
So I've been playing around with liveslak on a persistent USB for a week now, to get more familiar with it before actually installing it on my laptop. couple of hours ago I booted it up and as I usually do, did a quick update following these commands:
Code:slackpkg update gpg
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-systemAnd when I was done and booted in my actual OS which is fedora, I saw that it's hostname was changed to darkstar :) and there is probably more.
I know the problem should have arisen from one of the installation scripts from the update, but wanted to ask how did it get to my actual hard drive :)?
Aren't those scripts limited to their own root?
Appreciate any answer.