Re: sleep in microsecond or nanosecond

Special casing is what I had in mind, but it's very tricky. The normal wakeup-queue method is simply not adequate. On Thu, Aug 12, 2010 at 11:42 PM, wrote: > Hi, > > On Wed, Aug 11, 2010 at 10:03:31AM -0700, Thomas Bushnell, BSG wrote: > > > The current technique is to use a blocking mach_msg wh

Re: [PATCH 0/8] Bring console-driver-xkb up to date

Hi, 2010/8/13 : > > > Not sure what you are saying here. Do you mean that the xkb driver > misses some functionality the ordinary pc_kbd driver has? > At some point in it's history pc_kbd introduced support for GNU Mach v2, which is the oskit based kernel AFAIK. For that reason, pc_kbd now has t

Re: [PATCH 1/2] Fix /proc/*/cmdline.

Hi, thanks for your comments. On Fri, Aug 13, 2010 at 05:13:20PM +0200, olafbuddenha...@gmx.net wrote: > [You should split] Sorry for inadvertently fixing some bugs :-P The procfs code is in a rather bad shape, I guess I should just take an afternoon to read through the whole thing and fix/refac

[PATCH 3/4] Set an appropriate st_mode on symlinks.

--- procfs_pid_files.c | 11 ++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/procfs_pid_files.c b/procfs_pid_files.c index 3008145..548497c 100644 --- a/procfs_pid_files.c +++ b/procfs_pid_files.c @@ -49,7 +49,16 @@ update_pid_entries (struct procfs_dir *dir, const ch

[PATCH 4/4] Implement /proc/cmdline and /proc/mounts as symlinks.

* /proc/cmdline -> /proc/2/cmdline (process 2 is usually gnumach) This is not perfect, as the format of /proc/cmdline and /proc/*/cmdline are different on Linux. Namely, the latter includes NUL bytes to separate subsequent arguments, while the former contains only spaces and a trailing ne

[PATCH 2/4] update_pid_entries(): fix awkwardly indented uninitialized memory leak

--- procfs_pid_files.c | 10 -- 1 files changed, 4 insertions(+), 6 deletions(-) diff --git a/procfs_pid_files.c b/procfs_pid_files.c index 9dbe3eb..3008145 100644 --- a/procfs_pid_files.c +++ b/procfs_pid_files.c @@ -46,14 +46,12 @@ update_pid_entries (struct procfs_dir *dir, const cha

[PATCH 1/4] Fix /proc/*/cmdline.

On Linux, /proc//cmdline is a NUL-separated list of arguments. We used to truncate after the first one and add some whitespace. --- procfs_pid_files.c | 14 +++--- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/procfs_pid_files.c b/procfs_pid_files.c index 4686153..9d

Re: What do you need from the Hurd for your day-to-day tasks?

On Thursday 12 August 2010 08:10:43 olafbuddenha...@gmx.net wrote: > However, I still refuse to run a graphics-centric environment, just to > do my text-centric work on top of it. It makes no sense. I want a > text-centric environment, with graphics capabilities as on optional > addition; not the o

Re: [PATCH 1/2] Fix /proc/*/cmdline.

Hi, On Fri, Aug 13, 2010 at 06:06:41AM +0200, Jeremie Koenig wrote: > On Linux, the per-process cmdline files should include the whole command line, > with subsequent arguments separated by NUL bytes. However, for some reason we > used to truncate it after the first one and append " \n". Hm... A

Re: [PATCH 0/8] Bring console-driver-xkb up to date

Hi, On Wed, Aug 11, 2010 at 06:55:25PM -0300, Diego Nieto Cid wrote: > 2010/8/9 : > > I'm not really familiar with the situation; but it sounds like xkb > > never should have been an extra driver, but rather just an update > > (perhaps on a development branch) of the normal pc_kbd driver -- > >

Re: [PATCH 2/8] Avoid hashing garbage for short keynames.

Hi, On Wed, Aug 11, 2010 at 07:04:17PM -0300, Diego Nieto Cid wrote: > 2010/8/9 : > > Hm, why tmp[5]? The way I read the code, only 4 entries are used... > > Well it's the null that terminates the string. But you specified "4" in the strncpy()... AFAIK it will omit the \0 if there are 4 non-\0

Re: [PATCH] Add support to send file descriptors over Unix sockets

Hi, On Wed, Aug 11, 2010 at 07:02:12PM +0200, Emilio Pozuelo Monfort wrote: > On 01/08/10 21:02, Carl Fredrik Hammar wrote: > > Another thing that crossed my mind is what'll happen if SCM_CREDS is > > also sent in the future? Because it also involves port, your code will > > fail because of the

Re: sleep in microsecond or nanosecond

Hi, On Wed, Aug 11, 2010 at 10:03:31AM -0700, Thomas Bushnell, BSG wrote: > The current technique is to use a blocking mach_msg which will never > complete, and with a timeout. The reason that nanosleep and usleep > don't work is because 10ms is the granularity of the Mach clock. Yeah, we figure

Re: [PATCH 2/2] Implement some (global) symlinks.

Hi, On Fri, Aug 13, 2010 at 06:06:42AM +0200, Jeremie Koenig wrote: > * /proc/cmdline -> /proc/2/cmdline (pid 2 is usually gnumach) > This is not perfect, as the format of /proc/cmdline and /proc/*/cmdline are > different on Linux. Namely, the latter includes NUL bytes to separate > subseq

Re: What do you need from the Hurd for your day-to-day tasks?

olafbuddenha...@gmx.net, le Wed 04 Aug 2010 19:37:18 +0200, a écrit : > On Wed, Jul 28, 2010 at 02:36:49PM +0200, Samuel Thibault wrote: > > olafbuddenha...@gmx.net, le Sat 24 Jul 2010 04:08:51 +0200, a écrit : > > > > - A full-featured high-resolution console (probably > > > framebuffer-based) >

Re: [PATCH 6/8] Add missing functions to input_driver_test.

olafbuddenha...@gmx.net, le Wed 11 Aug 2010 07:59:13 +0200, a écrit : > On Wed, Aug 04, 2010 at 04:20:04AM -0300, Diego Nieto Cid wrote: > > > +void console_switch_back(void) > > +{ > > + puts("Switch back\n"); > > Hm... I'm slightly ambivalent about the use of puts(). It make a lot of > sense t

Re: sleep in microsecond or nanosecond

Thomas Bushnell, BSG, le Wed 11 Aug 2010 10:03:31 -0700, a écrit : > The current technique is to use a blocking mach_msg which will never complete, > and with a timeout. The reason that nanosleep and usleep don't work is because > 10ms is the granularity of the Mach clock.  Changing the interface h

Re: preliminary patch for initrd support in Mach

olafbuddenha...@gmx.net, le Mon 09 Aug 2010 22:57:32 +0200, a écrit : > > If I remember correctly they're actually kindof related, because I needed > > those > > for the ramdisk message to be displayed correctly. > > In that case, you should make an extra patch, and make it part of a > patch seri

Re: GPL code reuse questions

olafbuddenha...@gmx.net, le Wed 04 Aug 2010 20:59:50 +0200, a écrit : > On Wed, Jul 21, 2010 at 12:08:45AM +0200, Samuel Thibault wrote: > > > No need to care about license stuff: fold that into a separate > > process, and voilà :) > > It's not that simple. What constitutes a derived work cannot

Re: [PATCH 2/2] Implement some (global) symlinks.

On Fri, Aug 13, 2010 at 06:06:42AM +0200, Jeremie Koenig wrote: > + stat.st_size = symlink_target ? strlen (symlink_target) : 0; > + stat.st_mode = symlink_target ? S_IFLNK : S_IFREG; > + stat.st_mode |= S_IRUSR | S_IRGRP | S_IROTH; Hmm, those symlinks should be mode 0777, shouldn't they? (also

A bash busy-loop, and -- more important -- about other TODOs / open issues: now on the web pages

Hello! | I've first seen this problem after having had the following command line run | for a week, or two, or three: | | Start `screen`. Find PID of pfinet. | | $ while sleep 66; do echo "$(date)" " $(ps --no-header --fo