Linux s:user-startup

[Fraccy]

The main startup scripts are usually in /etc/init.d

Which scripts are called during startup depends on the runlevel (ie. whether you're starting up with a console or GUI, or some other arrangement). Different distributions often have their own 'user-friendly' methods for adding to the startup scripts, because runlevels can get rather confusing.

It's probably a good idea to use your distro's own method for adding a startup-script; if you try to do it yourself, it might not work (or might go wrong).

A busybox-based system (easily set up from scratch) dispenses with runlevels altogether and has a simple initscript: /etc/init.d/rcS

The Linux/Unix file structure actually makes a lot of sense. Don't forget, it's multi-user - if the Amiga was ever like this, you'd inevitably see something similar.

More details at: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

[Fraccy]

(Just guessing...) the .d extension for init.d indicates that it's a directory containing init scripts.

There are similarly named directories in /etc, such as conf.d and env.d, but I don't think the .d extension is a general rule.

[Fraccy]

Hey, thanks for that! I didn't associate .d and daemons at first, so here's something new I learned today... :-D

[Fraccy]

murple wrote:

I think the main reason for that is that the First Commandment of unix-like OSes is "RTFM!"

And read log files!

I've never EVER had to post on a forum to sort out a problem. Mostly because someone else had had the same problem and there was a solution, or because a comment or observation pointed the way to a solution.

In nearly every case, the answers are already 'out there', or in the manual or a log file.