Neil Williams: 2038 overflows
Adrian (also sent by email):Re: 2038 issues on mobile platforms.
It is possible to handle 64bit time on 32bit systems. I got disillusioned with the libglib2.0-0 support (GDate) and I already had a library capable of 64bit mathematics (libqof1) so I wrote QofDate and QofTime that can handle true 64bit date and time calculations, formatting and scanning on 32bit or 64bit installations. I estimate that this gives us enough capacity to handle time for a couple of dozen times the age of the universe to nanosecond precision. The maths can also go backwards as far as it can go forwards so it could handle the date of the Big Bang with nanosecond precision too - if anybody actually works that out.
I'll be using this library in Emdebian to provide support for 64bit maths for gpe-expenses and the pre-alpha gpe-cash (stripped out gnucash for embedded devices) so at least your financial records will be safe.
http://cashutil.sourceforge.net/gpecash.php
http://gpe-expenses.sourceforge.net/
"QofTime is a lot like the unix 'struct timespec' except that it uses a
64-bit signed int to store the seconds. This should adequately cover
dates in the distant future as well as the distant past, as long as
these are not more than a couple of dozen times the age of the
universe. Values of this type can range from -9,223,372,036,854,775,808
to 9,223,372,036,854,775,807."
http://qof.sourceforge.net/doxy/group__QOFTIME.html#gb93e930907d0e2eba07b1fa7496e7822
http://qof.sourceforge.net/doxy/group__QOFTIME.html
QofTime is defined as 64bit on all systems and will not overflow until
the year 292,471,208,679 (not counting leap years). i.e. approx.
9223372036854775808 / (60*60*24*365). This also means that some values
of QofTime cannot be converted to a time_t on systems where time_t is
defined as 32bit.
http://qof.sourceforge.net/doxy/group__Date.html
A QofDate is theoretically able to go forward to the year
292,471,206,707 AD and back to the year 292,471,206,708 BC. Whether
such dates actually exist is outside the scope of this documentation.
http://packages.debian.org/sid/libqof-doc
http://packages.debian.org/sid/libqof1
We're a third of the way through spring, and already we're hitting
temperatures that would be a respectable mid-summer day. Tomorrow has also
been declared a Total Fire Ban day in our area. That's probably nearly
unheard of, especially given the large amount of rain that we've had over
winter.
I think I'm going to be a busy boy this summer. The bush around our town
last had a bushfire through it seven years ago, and there's a regular seven
year cycle of major bushfires. We're due for it. As this is my first
summer as a qualified bush firefighter, I'm a bit twitchy about what the
continued hot, dry weather may bring. Here's hoping it's not too horrific.
The German train drivers are going on strike again on Friday, asking for 30% more money. So far, they've been offered 4% and two extra hours of work per week. At least DB had the decency not to sink millions of Euros into an advertising campaign denouncing the union's demands as unreasonable. Which they aren't.
Looking at the web stats, I noticed, that quite a lot of people find
something relevant to "environmental" on my pages. As I was not aware of
anything related here, I
96.43.01 and 71.86.01 legacy packages have been started but I didn't get them done in time for a weekend release. Sorry about that. The plan is for the next two days.
Phil and I managed to catch up with Linus when he was at the kernel
summit in Cambridge last month. We gave him a Debian T-shirt at the
time, as Phil 
Joey writes about
* One of the best ever event
I had one of
In the last few days we (as in DebConf admins Steve Gran, Mark Hymers
and myself) have been doing some
I spent the better part of the weekend with trying to get an older Athlon XP mainboard to boot grub from an USB stick.
Unfortunately, without success.
Since a few months, my notebook boots Windows XP when it is booted naively. Only if the correct USB stick is plugged in
on boot, the Debian system that I work with comes up. The USB stick has grub, a kernel and an initrd which is used to
boot and unlock the crypto file systems (crypted LVs) on the disk and can be removed once the system has booted.
I wanted to use the same scheme for a “newly built” new desktop from old parts. Unfortunately, this was
much harder than I expected.
Since a few years, I use the USB-ZIP format for USB sticks that need to boot. It has shown that this format has the
best chance to successfully boot. For more information about this format and about how to build it, see
/usr/share/syslinux/README.usbkey on any recent Debian system with syslinux installed.
My grml USB stick that I always have on me is formatted like this, and the “new” desktop boots it just
fine. The boot stick for my notebook is an USB-ZIP as well, only that its primary partition is not FAT, but ext3.
Unfortunately, the BIOS of the “new” desktop seems to refuse booting grub. Neither my notebook’s
stick nor the new stick even come to the “loading stage x” output of grub, let alone to the menu. syslinux
works fine, and both sticks boot just fine on my notebook and on a qemu on the “new” desktop.
Since the grub command line has saved me multiple times in the past, I didn’t really like the idea of having to
use syslinux, and decided to boot the “new” desktop conventionally from hard disk without the use of an USB
boot stick. Until I got this far, the complete saturday and the better part of sunday was wasted. Darn.
This reminds me of a mainboard from 2002 (incidentally from the same vendor), which checked whether the first hard disk
had an active primary partition on it before it even tried to execute the MBR code. If no primary partition was found
(which was common case with the partitioning scheme that I used back then which only had logical drives - this was
before I discovered LVM), the BIOS gave the error message “Not found active primary partition” (sic!) and
refused to boot. Stupid programmers trying to outsmart the sysadmins of their products. But at least, the error message
was reasonably clear back then.