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

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
aus9

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

Post#1 by aus9 » 30 Oct 2015, 10:05

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
Last edited by aus9 on 01 Nov 2015, 00:36, edited 1 time in total.

aus9

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

Post#2 by aus9 » 31 Oct 2015, 13:13

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

User avatar
Ed_P
Contributor
Contributor
Posts: 3328
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

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

Post#3 by Ed_P » 31 Oct 2015, 15:02

These threads may shed some light on those files for you.

viewtopic.php?f=117&t=3205&start=90#p26644
viewtopic.php?f=81&t=3501&p=25182#p25178
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5575
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

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

Post#4 by brokenman » 31 Oct 2015, 19:56

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.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply