When does a shell get executed during the linux startup process
I do not understand when does a shell, lets say bash, get executed, which program runs bash initially first.
startup
Run gui application on startup
I can run a script at boot by adding the following line to my crontab:
How do services in Debian work, and how can I manage them?
In Windows I have the services manager, where I see all system services, that can be started through Windows itself, I set up the user it uses, the rights management is in there, and I can pass variables and some other information to the services, I can name them, and I can create duplicates services of one program and so on. So I have a main management tool in Windows.
Running a script during booting/startup; init.d vs cron @reboot
I am currently trying to understand the difference between init.d and cron @reboot for running a script at startup/booting of the system.
Create and control start up scripts in BusyBox
I have compiled a custom linux kernel in BusyBox. BusyBox init does not support runlevels. When the kernel boots up in BusyBox, it first executes init which looks for the specified runlevel in /etc/inittab. BusyBox init works just fine without /etc/inittab. When no inittab is found it has the following behavior:
systemd: automate modprobe command at boot time
My distribution is Fedora 17 Gnome.
Every time I reboot/restart my computer I need to run this command as root:
One systemctl command to both start and enable
Using one command to both start and enable systemctl managed software would be useful to spare a few lines in a few scripts, making them a bit more aesthetic (not really a problem but a nice thing to have).
How can I run a script that starts before my login screen?
I was calibrating my touch screen, and saw that the best tool around was xinput_calibrator. So I used it. It have two options (one of which did not work), so I am here for the second. It says I should execute this command “in a script that starts with your X session”: