Porteus

When one wants a command or a script to be included in the bootup process, there seems to be different ways of meeting that goal:
~/.bashrc
/root/.config/autostart-scripts/ #kde desktop

What are the other strategies?

As an example, personally I would like to start the CUPS server with the cupsd command.

Notes:
Services and runlevels:
https://www.linux.com/news/introduction ... cd-scripts
https://www.linux.com/news/introduction ... cd-scripts

How run levels start are configured in /etc/inittab:
example for openrc:

Perhaps?

hi francois in the pkgtool: setup, services,rc.cups and you can choose it at boot,slackware system

Beny, its good to see you on the forum.

Finally, I was happy to dig with these methods. And both of you gave me interesting insights in the linux system: /etc/rc.d. rc.1. rc.2 ... and pkgtools which are available in usm.

But also tied to pkgtools, I got to http://www.porteus.org/component/conten ... udies.html

It was about time that I read that FAQ must read for porteus understanding.

I am working on the CUPS or print module, and the solution is here:
http://alien.slackbook.org/dokuwiki/dok ... kware:cups This will get cupsd command initiated at bootup for the cups package.

So no need for autostart strategies, though it will be of some use later.

Thanks bogomips and beny.

Updated the link in first post.

Gives a 503 error now.

Curious not for me.