Your message dated Fri, 20 Jun 2008 17:14:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Kernel from Debian 3.1 no longer supported
has caused the Debian Bug report #276500,
regarding kernel-image-2.6.8-1-k7: system call need nanosecond resolution
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
276500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276500
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-3
Severity: normal
$ touch -r a b
$ stat -c %y a b
2004-10-13 11:36:18.169474381 +0800
2004-10-13 11:36:18.169474000 +0800
the difference messes up test -nt, make, cp -u, etc. etc.
From: Paul Eggert <[EMAIL PROTECTED]>
Subject: Re: cp -up forever
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
"touch" operates by means of system calls. If the system calls
mishandle submicrosecond time stamps, "touch" will as well. So you'll
have to direct your bug reports to the kernel people who have
misdesigned their system calls.
The basic problem is that utimes() has only microsecond resolution;
the kernel need to add a system call ("utimens()", say?) that supports
nanosecond resolution.
--- End Message ---
--- Begin Message ---
Version: 2.6.8-99+rm
You reported a bug against the Linux kernel (version 2.6.8) that was
shipped with Debian 3.1 (sarge). Since Debian 3.1 is no longer
supported and the kernel has changed so much that it would be very
difficult to verify every outstanding bug from 2.6.8, I'm hereby
closing your bug report.
If you still see this issue with the kernel from the upcoming release
of Debian (lenny, version 5.0), then please me know and I'll be happy
to reopen this bug report.
Thanks.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---