How come there is two init scripts to deal with the hardware
clock at boot up?
martin f krafft
madduck at debian.org
Mon Jan 30 09:16:52 GMT 2006
First, please do not CC me on mailing lists, as per request in my
signature and the header of any email I send.
also sprach Tobias Hunger <tobias at aquazul.com> [2006.01.30.0947 +0100]:
> S18 is not that early in the boot process.
It is early enough.
> Finally your argument does not hold, since S20checkrootfs.sh does
> *not* mount /usr. This only happens in S35mountall. Is hwclock run
> way too early?
It appears to be. In Debian sarge, hwclock is started at S50, while
hwclockfirst is also started at S18. In Debian sid, it appears to be
at S18/S22 now too. See #342887.
Anyway, the changelog only mentions
* Really move hwclockfirst.sh back to S18 where it belongs.
Put hwclock.sh at S22. See #50572.
Typical example of a bad changelog entry, IMHO.
Sorry for not checking this earlier. I was on a plane when answering
the post and had not 'Net access.
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <madduck at debian.org>
: :' : proud Debian developer and author: http://debiansystem.info
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
"time flies like an arrow. fruit flies like a banana."
-- groucho marx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20060130/0c3afff2/attachment.pgp
More information about the ubuntu-devel