RE: how it works: hurd users

2001-07-12 Thread Jim Franklin
I think new developers would find it useful as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Farid Hajji Sent: Thursday, July 12, 2001 6:13 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: how it works: hurd users > here is something

Re: how it works: hurd users

2001-07-12 Thread Farid Hajji
> here is something that hopefully helps people to understand how the Hurd > user model works. It is of course far from perfect, not complete, etc etc, > and it is certainly not supposed to be a replacement for proper > documentation (in fact, I don't even think it is adequate as a base for it).

Re: sending ports in reply msg

2001-07-12 Thread Roland McGrath
proc_getexecdata and proc_setexecdata both seem to be totally broken. It seems like they have never actually been called. proc_setexecdata never deallocates the old port rights. proc_getexecdata never sets its *portspoly out parameter, so garbage goes into the reply message. I think the only co

sending ports in reply msg

2001-07-12 Thread Marcus Brinkmann
Hi, this is not so easy to see, esp with all the libports mayhem. proc_getexecdata just memcpy()s the port array, and then returns. Will this do the right thing? proc is essentially single threaded, by taking a lock in message_demuxer. But as it seems to me, the message has not yet actually b

Bug#102437: dealloc analysis for each server function, more bugs!

2001-07-12 Thread Marcus Brinkmann
On Thu, Jul 12, 2001 at 04:34:45PM -0400, Roland McGrath wrote: > I didn't look closely, but now I am thinking twice. If the data is small > enough to fit inline, and you use a separate reply stub, then you can send > it without copying. That ought to be the common case. This would be what you

Bug#102437: dealloc analysis for each server function, more bugs!

2001-07-12 Thread Marcus Brinkmann
On Thu, Jul 12, 2001 at 04:34:45PM -0400, Roland McGrath wrote: > > On Wed, Jul 11, 2001 at 04:49:17PM -0400, Roland McGrath wrote: > > > That's fine by me if it's tested. BTW add -p to your diff switches. > > > > Actually, I goofed up. The arguments to the reply stub have not been > > changed

Bug#102437: dealloc analysis for each server function, more bugs!

2001-07-12 Thread Roland McGrath
> On Wed, Jul 11, 2001 at 04:49:17PM -0400, Roland McGrath wrote: > > That's fine by me if it's tested. BTW add -p to your diff switches. > > Actually, I goofed up. The arguments to the reply stub have not been > changed by my patch. In fact, as we now copy the user data all the time, a > sepe

Assertion failure in ext2fs.static

2001-07-12 Thread Jeff Bailey
I got a different Hurd crash than normal. I don't have any more information than this, sorry. This occured when I was doing an autobuilder run: extfs.static: thread-cancel.c:55: hurd_thread_cancel: Assertion `! __spin_lock_locked (&ss->critical_section_lock)' failed. The crash is unusual in t

Bug#102437: dealloc analysis for each server function, more bugs!

2001-07-12 Thread Marcus Brinkmann
On Thu, Jul 12, 2001 at 09:06:12PM +0200, Marcus Brinkmann wrote: > On Wed, Jul 11, 2001 at 04:49:17PM -0400, Roland McGrath wrote: > > That's fine by me if it's tested. BTW add -p to your diff switches. > > Actually, I goofed up. The arguments to the reply stub have not been > changed by my pa

Bug#102437: dealloc analysis for each server function, more bugs!

2001-07-12 Thread Marcus Brinkmann
On Wed, Jul 11, 2001 at 04:49:17PM -0400, Roland McGrath wrote: > That's fine by me if it's tested. BTW add -p to your diff switches. Actually, I goofed up. The arguments to the reply stub have not been changed by my patch. In fact, as we now copy the user data all the time, a seperate reply s

how it works: hurd users

2001-07-12 Thread Marcus Brinkmann
Hi, here is something that hopefully helps people to understand how the Hurd user model works. It is of course far from perfect, not complete, etc etc, and it is certainly not supposed to be a replacement for proper documentation (in fact, I don't even think it is adequate as a base for it). I h

Re: Content of my talk available online

2001-07-12 Thread Marcus Brinkmann
Cutting the CC line. On Thu, Jul 12, 2001 at 09:55:17AM -0700, Jim Franklin wrote: > Hi Marcus, > If you need a permanent home for your talk, let's put at hurd.gnu.org . I > think it is quite informative and would be of wonderful benefit to the > hurd.gnu.org web site. Works for me. If you nee

RE: Content of my talk available online

2001-07-12 Thread Jim Franklin
Hi Marcus, If you need a permanent home for your talk, let's put at hurd.gnu.org . I think it is quite informative and would be of wonderful benefit to the hurd.gnu.org web site. Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marcus Brinkmann Sent:

Re: Content of my talk available online

2001-07-12 Thread Thierry Laronde
On Thu, Jul 12, 2001 at 04:00:38PM +0200, Marcus Brinkmann wrote: > Hi, Hello Marcus, > > I put the content of my talk about the Hurd online. > > It is currently available from > > http://www.marcus-brinkmann.de/talks.en.html Thanks ! -- Thierry LARONDE, Centre de Ressources Informatiques, A

Content of my talk available online

2001-07-12 Thread Marcus Brinkmann
Hi, I put the content of my talk about the Hurd online. It is currently available from http://www.marcus-brinkmann.de/talks.en.html Please follow the link "talk about the Hurd". This will bring you to people.debian.org. Please don't link to people.debian.org only, as this is most likely not

Call for Projects

2001-07-12 Thread Patrick Strasser
Hello! I plan to set up and publish every month a list of Hurd projects. I'd like to include active and not active or abandoned projects. The list intended to give an overview about work around the Hurd and a starting point for people willing to join. Pease give following information: A short na