Comment 4 for bug 28072

Message-ID: <email address hidden>
Date: Tue, 27 Dec 2005 13:08:08 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: hwclockfirst.sh is run too late, after fsck

--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

We're seeing this problem with certian ADS bitsyxb hardware that doesn't ha=
ve
a valid time until hwclock is run. Possible results range from fsck never
running even after the max interval between checks has been reached, to it
running at every single boot.

We've avoided this problem by adding a link to call hwclockfirst.sh
before the fsck.

--=20
see shy jo

--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDsYMHd8HHehbQuO8RAhMaAJsHYYzKKpylwQYk9ufZpHzWh+1MUQCfW9IL
6jH24edjhunStfIvFLzVBgs=
=0NoL
-----END PGP SIGNATURE-----

--SLDf9lqlvOQaIe6s--