Your message dated Sun, 22 Jun 2008 09:18:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line #276500: utimensat added as syscall has caused the Debian Bug report #276500, regarding 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.22-1 There is a new syscall in 2.6.22, utimensat. It gets a "struct timespec" which allows nanosecond resultion. It is currently supported on any arch except hppa. Therefor I believe this as resolved from the kernel side. Bastian -- Actual war is a very messy business. Very, very messy business. -- Kirk, "A Taste of Armageddon", stardate 3193.0
signature.asc
Description: Digital signature
--- End Message ---
