Page 1 of 1

[SOLVED] porteus/changes/var/log/scripts question

Posted: 30 Oct 2015, 10:05
by aus9
Hi

I tend to use changes bootcode. in <partition-mount-point>porteus/changes//var/log/scripts

There are lots of .scriptname
The contents are empty for each file.

eg
.wh.youtube-dl-2015.10.09-x86_64-1_slack
is one of my modules from my modules folder (directory)
But I can't see any base modules in above folder

question 1. Are these important?
b) What happens if I was to accidently delete one or more?

question 2. Should only active scripts-names appear here. That is, are they supposed to match the output of

Code: Select all

ls /mnt/live/memory/images
thanks for reading

Re: porteus/changes/var/log/scripts question

Posted: 31 Oct 2015, 13:13
by aus9
OK I am thinking....wh stands IMHO to whitelist meaning to ignore.

I delete a file with root powers then looked into my porteus/changes/pathway2dir
there was the deleted file showing as

(dot).wh.deleted-filename

thanks for reading.

so if I am right, the original post shows one of my modules was not activated.

I have done a rebuild so far, no whitelisting of modules is showing up in my changes so it looks OK
but looking for verification please

Re: porteus/changes/var/log/scripts question

Posted: 31 Oct 2015, 15:02
by Ed_P

Re: porteus/changes/var/log/scripts question

Posted: 31 Oct 2015, 19:56
by brokenman
Porteus is based on aufs (another union file system) which you can thin of as an onion. It has layers. If a module is on a bottom layer and you load an identical file over it on an uppermost layer (say the rootcopy directory) then the uppermost layer is visible. If you delete a file from the bottom layer then it is not actually deleted but instead a whiteout file (.wh) is placed on the upper layer telling the system to think of it as invisible. Whited out.

Don't touch these .wh files. The system will take care of them, and in deed needs to keep track of them.