Lists all of the journal entries for the day.
Mon, 20 Mar 2006
6:13 PM - bored
I'm quite bored at the moment. I've about had it with coding for today. On to another activity i suppose. On the up side, I may consider this client to be beta quality and release it. It will be considered 1.4. It certainly looks better than the last version.
5:41 PM - Jury duty
I get to do jury duty tomorrow, how exciting. There goes my day... and I miss a presentation as well.
What to do though...
5:36 PM - JJ fun.
Hmm.. not a lot of luck with this jj win client today.
5:04 PM - Testing new JJ client
I'm working on the new Just Journal windows client. Its been about a month since I released a new version and there are certainly a number of bugs in the last version. Mostly this will be an interface improvement/bugfix release. Lets see what happens.
This article has a somewhat fair comparison, but of course the guy ignores a lot of other unix desktop replacements. Plus, OS X can replace UNIX in many cases since it is UNIX. :)
11:31 AM - More linux
11:19 AM - back to the future GNU
Author: Paul Mackerras <email@example.com>
Date: Wed Mar 15 13:47:15 2006 +1100
powerpc: Fix problem with time going backwards
The recent changes to keep gettimeofday in sync with xtime had the side
effect that it was occasionally possible for the time reported by
gettimeofday to go back by a microsecond. There were two reasons:
(1) when we recalculated the offsets used by gettimeofday every 2^31
timebase ticks, we lost an accumulated fractional microsecond, and
(2) because the update is done some time after the notional start of
jiffy, if ntp is slowing the clock, it is possible to see time go backwards
when the timebase factor gets reduced.
This fixes it by (a) slowing the gettimeofday clock by about 1us in
2^31 timebase ticks (a factor of less than 1 in 3.7 million), and (b)
adjusting the timebase offsets in the rare case that the gettimeofday
result could possibly go backwards (i.e. when ntp is slowing the clock
and the timer interrupt is late). In this case the adjustment will
reduce to zero eventually because of (a).
Signed-off-by: Paul Mackerras <firstname.lastname@example.org>
11:14 AM - ROFL... linux bug in 2.6.15 and lower
Author: Srivatsa Vaddagiri <email@example.com>
Date: Thu Mar 16 23:04:06 2006 -0800
[PATCH] x86: check for online cpus before bringing them up
Bryce reported a bug wherein offlining CPU0 (on x86 box) and then
subsequently onlining it resulted in a lockup.
On x86, CPU0 is never offlined. The subsequent attempt to online CPU0
doesn't take that into account. It actually tries to bootup the already
booted CPU. Following patch fixes the problem (as acknowledged by Bryce).
Please consider for inclusion in 2.6.16.
Check if cpu is already online.
Signed-off-by: Srivatsa Vaddagiri <firstname.lastname@example.org>
Signed-off-by: Andrew Morton <email@example.com>
Signed-off-by: Linus Torvalds <firstname.lastname@example.org>