Porteus

Salutations...

I'm interested in using... So at startup I can load my default settings globally...
@ /etc/skel/.config
Instead of using "changes" (~/.config).
Is there a simple convenient way to do this?

Best Regards...

Hi

Please don't delete guest account

when I first came here....I recommended they improve the FAQ as it should say ....have only guest and root
viewtopic.php?f=53&t=5121

2) What is wrong with using a changes cheatcode....that is IMHO exactly what you need....what you want etc

Salutations...

I'm doing this for the custom derivative of Porteus that I've been working on for the last year and a half.
IMHO... for my goals the USM... the "changes" cheatcodes and saved modules... files and folders are counterproductive.
(I only use the USM now to edit modules and resolve dependencies that I later download by tunnel from slakfinder.org)

Like many things Porteus I prefer to go "rogue"... because I have a different vision of the potential of Porteus.
Porteus uses glibc-solibs... I use musl. It uses perl... I use perl w/ libmce-perl (perl JIT?)
Porteus/LXQT uses Openbox... I use PekWM (my derivative tries to avoid Mesa... Qt/Gtk dependencies) and so on.
eg... http://forum.porteus.org/viewtopic.php?f=39&t=5139

I have multiple partitions w/ stable versions of Porteus.
However... this version is my custom spin on it that is fully functional and 95% complete.

In order to use /etc/skel/.config... "userdel -r guest" and "useradd -r guest" must be run @ startup.
I just don't know how to set it up. With a global (default?) configuration my derivative will be complete.

Basically what I'm saying is... I help need to get over the 5 yard line to score the touchdown.

Best Regards...

I would think that since you apparently have an aversion to using Porteus changes along with related files and folders, you might have to hard code your needs in the base and rebuild it.

Or, use some other distro more suited to your purposes.

I think the best place would be inside initrd. Next best perhaps in the startup scripts like /etc/rc.d/rc.S or the last one run /etc/rc.d/rc.local

Salutations...

Thanks... brokenman. it looks like I can finally finish.
(For what it's worth... I prefer to use Porteus rather than build it).

Best Regards...

Salutations...

I haven't applied the startup commands yet... but as a more exotic variation...
would it also be feasable to symlink /root/.config to overwrite /etc/skel/.config?

So I everytime I reconfigure /root/.config and save it to ~/rootcopy/root/.config...
it updates /home/guest/.config. Or... is that too esoteric?

Basically... I want root (admin?) configuration to control guest (user?).

Best Regards...

brokenman wrote:I think the best place would be inside initrd. Next best perhaps in the startup scripts like /etc/rc.d/rc.S or the last one run /etc/rc.d/rc.local

I hadn't realized that files in the initrd would/could be carried over to the main system....I had thought that everything was passed to the system after starting init.....this opens up more possibilities.

Thanks