Right problems with Porteus v09

[ahz]

Hallo,

thanks for releasing Porteus v09. When I mount the ISO-Image I see that /boot and /porteus have the following rights:

dr-xr-xr-x 6 root root 4096 2011-01-10 10:08 boot/
dr-xr-xr-x 7 root root 2048 2011-01-10 09:57 porteus/

If you change into /porteus you see

dr-xr-xr-x 2 someone someone 4096 2011-01-10 10:07 base/
-r--r--r-- 1 someone someone 7982 2011-01-10 09:57 cheatcodes.txt
-r--r--r-- 1 someone someone 17993 2011-01-10 09:57 GNU_GPL
-r--r--r-- 1 someone someone 255 2011-01-10 09:57 License.txt
-r-xr-xr-x 1 someone someone 706 2011-01-10 09:57 make_iso.bat*
-r-xr-xr-x 1 someone someone 974 2011-01-10 09:57 make_iso.sh*
dr-xr-xr-x 2 someone someone 4096 2011-01-10 09:57 modules/
dr-xr-xr-x 2 someone someone 4096 2011-01-10 09:57 optional/
-r--r--r-- 1 someone someone 441 2011-01-10 09:57 porteus-v09.sgn
-r--r--r-- 1 someone someone 977 2011-01-10 09:57 requirements.txt
dr-xr-xr-x 2 someone someone 4096 2011-01-10 09:57 rootcopy/
-r--r--r-- 1 someone someone 21606 2011-01-10 09:57 slaxsave.zip
dr-xr-xr-x 3 someone someone 4096 2011-01-10 09:57 tools/

So everywhere the 'w'-flag is missing for user rights, making it impossible to write into e.g. the modules folder with "non-root rights". Has this changed with intend while porting remix to Porteus?

[brokenman]

Thank you. Not sure why those rights might have changes. Certainly not intentional. Will address this in v1.0

[wread]

my pemissions by boot are 777, by porteus 755 -maybe you have a corrupted download?

[ahz]

The download seems to be OK (md5sum is the same as on the download page). Maybe you see this issue only if one mounts the ISO-Image e.g. in order to "remaster" Porteus. Things may be different if you boot the ISO-Image (will have a closer look about this tomorrow). From my few todays experiments I can tell, that a booted plain Porteus behaves like a plain remix.

[brokenman]

When I mount the ISO-Image

I missed the important part of the sentence. Your mounted ISO is of course read only. Extract the iso or mount it and copy the files elsewhere.

[ahz]

That does not solve the problem. I will try to explain it a more detailed:

I downloaded the two ISO-Images porteus-v09-i486.iso and porteus-v09-x86_64.iso. They appear as following in ~/Downloads:

ahz@i750:~/ba/2006/2007/porteus/32bit/v09/porteus/modules$ ls -laF ~/Downloads/porteus-v09*
-rw-r--r-- 1 ahz ahz 245557248 2011-01-11 14:31 /home/ahz/Downloads/porteus-v09-i486.iso
-rw-r--r-- 1 ahz ahz 315287552 2011-01-11 14:27 /home/ahz/Downloads/porteus-v09-x86_64.iso

In order to remaster the first one I did 'sudo mount -o loop ~/Downloads/porteus-v09-i486.iso /mnt'. This leads to

ahz@i750:~/ba/2006/2007/porteus/test$ ls -laF /mnt
total 12
dr-xr-xr-x 4 root root 2048 2011-01-10 09:57 ./
drwxr-xr-x 22 root root 4096 2010-12-21 14:22 ../
dr-xr-xr-x 6 root root 4096 2011-01-10 10:08 boot/
dr-xr-xr-x 7 root root 2048 2011-01-10 09:57 porteus/

Now you can do do a 'cp -a ..." or 'rsync -avH ...' to get a copy of the content of this mount point and you get:

ahz@i750:~/ba/2006/2007/porteus/test$ ls -laF
total 16
drwxr-xr-x 4 ahz ahz 4096 2011-01-17 07:50 ./
drwxr-xr-x 5 ahz ahz 4096 2011-01-17 07:49 ../
dr-xr-xr-x 6 ahz ahz 4096 2011-01-10 10:08 boot/
dr-xr-xr-x 7 ahz ahz 4096 2011-01-10 09:57 porteus/

This is exactly what you see in the mounted ISO-Image.

If you do the same with porteus-v09-x86_64.iso things change:

ahz@i750:~/ba/2006/2007/porteus/test$ sudo umount /mnt
ahz@i750:~/ba/2006/2007/porteus/test$ sudo mount -o loop ~/Downloads/porteus-v09-x86_64.iso /mnt
ahz@i750:~/ba/2006/2007/porteus/test$ ls -laF /mnt
total 12
drwxr-xr-x 4 1001 users 2048 2011-01-09 16:03 ./
drwxr-xr-x 22 root root 4096 2010-12-21 14:22 ../
drwxr-xr-x 6 1001 users 4096 2011-01-10 08:39 boot/
drwxr-xr-x 7 1001 users 2048 2011-01-09 16:04 porteus/

Now compare the status of the w-flag for the folders boot and porteus: While in porteus-v09-i486.iso it is u-w, porteus-v09-x86_64.iso has the value u+w.

The latter one is the one I used to see in all remix versions until now. I agree that this is not a big problem at all (you can change this easily by hand after copying and I have done so) but it is definitively different from the 64 edition and other remixes and it is issued by the way the ISO-Image has been created and/or the source from which the ISO has been created from. I have dowloaded porteus-v09-i486.iso multiple times it is always the same.

[brokenman]

I understand now. No doubt it i caused by the method i use to create the ISO. I'll address this for next release. Thanks for explaining clearly.