Re: Bug#47896: MS_SYNC Macros Missing from Hurd development environment

2007-06-08 Thread Samuel Thibault
Hi, Aurelien Jarno, le Sat 18 Feb 2006 23:32:50 +0100, a écrit : It seems the msync() function has been implemented on Hurd since the bug has been reported, at least there is now a sysdeps/mach/msync.c file which seems to do something. The macro MS_SYNC has been added and some code has been

Re: Bug#79358: is select still broken on hurd ?

2007-06-08 Thread Samuel Thibault
Hi, (summary for the recall) things like select(1,[0],[],[],[0,0..999]) always return 0 immediately About the 0..999 range, it's just that the timeout value is divided (and rounded down) by 1000. Now, we have a pile of issues: in gnumach's ipc_mqueue_receive(), if time_out is zero, the

Processed: closing 38658

2007-06-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 close 38658 Bug#38658: hurd: keyboard layout configuration 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to [EMAIL

Processed: closing 144545

2007-06-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.4 close 144545 Bug#144545: hurd: init scripts don't fsck extra partitions 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further

libgl1-mesa-glx

2007-06-08 Thread Samuel Thibault
Hi, There is some issues with packages that depend on libgl1-mesa-glx | libgl1: on the Hurd we only build libgl1-mesa-swx11 which provides libgl1, but buildd isn't smart enough to install it. A solution would be to ask maintainers to fix into libgl1-mesa-glx [!hurd-i386] | libgl1-mesa-swx11

Re: Bug#79358: is select still broken on hurd ?

2007-06-08 Thread Neal H. Walfield
At Sat, 9 Jun 2007 01:30:49 +0800, Samuel Thibault [EMAIL PROTECTED] wrote: Actually, on the Hurd, a timeout of 0 probably doesn't make sense (since we at least need to give back cpu to the server). What I'd propose is the attached patch (not tested), that rounds up the timeout value, and in