Specifying a custom user with boot codes requires that you chmod the tce folder

[baz]

If you install a fresh TC using a custom user bootcode (i.e. user=baz) you will not be able to install apps until you "chmod g+w tce". I am using a persistent opt, tce and home on 2.7.

Clearly, users should be able to immediately install apps after specifying a custom user.

Cheers,
Baz

[baz]

Should the tce folder even be owned by "tc", or would it make more sense as "root", or even my user "baz"?

[roberts]

Simple enough. Group write enabled. Done.

[baz]

Is there a reason to have the user "TC" in the system if you specify a custom user?

In opt,

"baz" owns: .appbrowser, .tcrc
"tc" owns: .filetool.lst, .xfiletool.lst, .tce_dir
and "root" owns the rest.

Wouldn't it be more dependable and prettier if "baz" completely replaced "tc" throughout the system and "tc" didn't exist?

[roberts]

Not necessary. Adding users has been supported therefore group write had to have been enabled for such. Likely a process or extension changed the permission on the persistent store. As part of the boot up I will ensure such group write is enabled.

[baz]

Is the change in the current 2.7 or is it reserved for 2.8?

[roberts]

It is in 2.8.