SuSE 9.1 - какой скрипт стартует последним ?

/etc/rc.d/boot.local (во всех версиях SuSE)

в том то и прикол, что нет !!!
после бут.локал дох#я еще стартует всего. А мне нужен /последний/
скрипт.
Блин, зачем нужно было отходить от редхатовского стиля???
Ну нахера, блин!? Лиш бы по-своему? немцы как хохлы, блин.

SuSe Help-Center -> 13.4. Init Scripts Читаем документацию к системе.

boot

Executed while starting the system directly using init. It is independent of the chosen runlevel and is only executed once. Here, the proc and pts file systems are mounted and the blogd (boot logging daemon) is activated. If the system is booted for the first time after an update or an installation, the initial system configuration is started.

The blogd daemon is a service started by the boot and by the rc scripts before any other one. It is stopped after the actions triggered by the above scripts (running a number of subscripts, for example) are completed. The blogd daemon writes any screen output to the log file /var/log/boot.msg — but only if and when /var is mounted read-write. Otherwise, blogd buffers all screen data until /var becomes available. Further information about blogd can be obtained with man blogd.

The script boot is also responsible for starting all the scripts in /etc/init.d/boot.d with a name that starts with S. There, the file systems are checked and loop devices are configured if needed. The system time is also set. If an error occurs while automatically checking and repairing the file system, the system administrator can intervene after first entering the root password. Last executed is the script boot.local.

boot.local

Here, enter additional commands to execute at boot before changing into a runlevel. It can be compared to AUTOEXEC.BAT on DOS systems.

boot.setup

This script is executed when changing from single user mode to any other runlevel and is responsible for a number of basic settings, namely for the keyboard layout and for initializing the virtual consoles.

Отсюда делаем вывод, что последовательность такая, сначала init запускает boot, boot.local, boot.setup, а потом уж проход по rc.d скриптам в зависимости от выбранного runlevel'а...

Соответственно стартанет последним тот скрипт из /etc/init.d/script, на который симлинк в /etc/rc.d/rcX.d/SYYscript имеет наибольший номер YY.

Поправьте, если я не прав...