On Wed, Jun 18, 2008 at 01:23:01PM +0200, Carlos E. R. wrote:
The Wednesday 2008-06-18 at 13:01 +0200, Pavol Rusnak wrote:
Carlos E. R. wrote:
Aparently, both serve the same purpose:
No, in fact they are exact opposite:
Yeah, humm, well... small details :-p
/etc/init.d/boot.clock:
# Description: Read hardware clock and set system clock ^^^^^^^^ ^^^^^^
/etc/init.d/boot.getclock:
# Description: Read system clock and set hardware clock
Basically, between both they take care of the clock. Why two scripts, wasn't it possible to make do with one script? Just curious.
Simply because the boot.clock is required to be executed *before*
boot.localfs to have the correct time stamp around during mount.
On the other hand is using an adjust file requires to write the
system clock back *before* unmounting the local file system done
by boot.localfs at shutdown.
In other words, the insserv program is currently not able to create
start and stop links in an asymetric manner. This is what I'm
currently implement for insserv(8) to enable insserv(8) to use not
only Required-Start, Should-Start, and X-Start-Before but also
Required-Stop, Should-Stop, and -Stop-After. Compare with the
manual page insserv(8).
Werner
--
Dr. Werner Fink