[Solved] why does boot process change /opt ownership to root?

[curaga]

I think the change is fine, added to git. Any fresh opt is still root:staff, only a customized one stays with its own ownership.

[jazzbiker]

Hi, Core people!

Gazing over owners, permissions and dirs I was surprised by

Code: [Select]

tc@box:~$ ls -ld /
drwxr-xr-x   17 tc       staff          380 Jul  4 15:55 //

Is it ok to own / not by root? Or I am doing something wrong?

[jazzbiker]

As an exercise I've booted with "base" bootcode and

Code: [Select]

cd /
rm -r home

without sudo and any problems.

[GNUser]

I think the change is fine, added to git.

Yay!

curaga, I realized later that we can accomplish the same result with one line instead of two, like this:

Code: [Select]

    yes n | cp -ai /opt/* /opt/.[!.]* "$MOUNTPOINT"/opt/ 2>/dev/null
This is a more elegant change (more efficient, keeps line count the same). I've tested it in my remastered TCL and it works exactly as intended.

[curaga]

User tc has sudo access without a password, so access to the root dir doesn't really harm anything.