On Fri, Oct 17, 2008 at 12:42 AM, Phil Endecott
[EMAIL PROTECTED] wrote:
Hi everyone,
It's clear that it's possible to save a few seconds of boot time by
using a pre-populated /dev, rather than letting udev populate it
dynamically. This would be simple in a locked down system where
upgrades
Phil Endecott wrote:
Phil Endecott wrote:
- Setting the clock takes up to a second. But I don't think it would
if we didn't have to use --directisa.
It turns out that it still takes up to a second even when hwclock is
reading from /dev/rtc; it still waits for the time to tick over to the
On Mon, Oct 20, 2008 at 1:11 AM, Phil Endecott
[EMAIL PROTECTED] wrote:
Unfortunately we don't know anything about the fractional value from the
hardware.
We may be able to set the software clock to t+0.5 which I think would fix
it, wouldn't it?
I think so; it should also have the side
Phil Endecott wrote:
- Setting the clock takes up to a second. But I don't think it would
if we didn't have to use --directisa.
It turns out that it still takes up to a second even when hwclock is
reading from /dev/rtc; it still waits for the time to tick over to the
next second. Not using
Damyan Ivanov wrote:
I think you can safely ommit the settle call in the network
coldplugging part.
There are scripts for things like ntp that run after this and want the
network to be up.
Also, the initial coldplugging may be split in two
parts - disks and the rest (minus network). The
-=| Phil Endecott, Fri, Oct 17, 2008 at 12:42:52AM +0100 |=-
I haven't used this much yet so if anyone can see any flaws please
let me know.
Not exactly a flaw, but an additional idea:
I think you can safely ommit the settle call in the network
coldplugging part. Also, the initial
