Re: Clarification about section 3.1 (The Root Filesystem, Purpose)

2002-10-13 Thread Richard Kreuter
On Sat, Oct 12, 2002 at 12:00:16PM -0500, Richard Kreuter wrote: > On Sat, Oct 12, 2002 at 05:18:45PM +0200, Alfred M. Szmidt wrote: > > Richard Kreuter <[EMAIL PROTECTED]> writes: > > > I've got a slightly newer draft, nearly properly groff formatted, > > > but I've no place to post it online r

Re: fork() loses when thread self port's refcount is max'ed out

2002-10-13 Thread Roland McGrath
> * You can call mach_task_self() anytime you like. Never deallocate it. That's right. Using the macro that is really just a variable and doesn't diddle refs is not a very clear API, but we inherited it from CMU. > * You should never call mach_thread_self(). If you need to call it, > don't

more info (was:Re: glibc 2.3 broken

2002-10-13 Thread Marcus Brinkmann
On Sun, Oct 13, 2002 at 06:06:14PM +0200, Marcus Brinkmann wrote: > (to Jeff) You are right, glibc 2.3 is quite broken for us. > > I don't even come to a login prompt. postinst segfaults, runsystem > segfaults, and the system soon crashes. ok, I found out a bit more. I could reproduce this in

Re: core dumps (was: Re: glibc 2.3 broken

2002-10-13 Thread Marcus Brinkmann
On Sun, Oct 13, 2002 at 06:35:30PM +0200, Marcus Brinkmann wrote: > On Sun, Oct 13, 2002 at 06:06:14PM +0200, Marcus Brinkmann wrote: > > I don't even come to a login prompt. postinst segfaults, runsystem > > segfaults, and the system soon crashes. jojo reported a 'panic: ipc ports > > exhausted'

core dumps (was: Re: glibc 2.3 broken

2002-10-13 Thread Marcus Brinkmann
On Sun, Oct 13, 2002 at 06:06:14PM +0200, Marcus Brinkmann wrote: > I don't even come to a login prompt. postinst segfaults, runsystem > segfaults, and the system soon crashes. jojo reported a 'panic: ipc ports > exhausted'. The kernel panic problem etc could actually be related to the core dump

glibc 2.3 broken

2002-10-13 Thread Marcus Brinkmann
Hi, (to Jeff) You are right, glibc 2.3 is quite broken for us. I don't even come to a login prompt. postinst segfaults, runsystem segfaults, and the system soon crashes. jojo reported a 'panic: ipc ports exhausted'. I definitely won't be able to look at this before november. Packages are at

Re: fork() loses when thread self port's refcount is max'ed out

2002-10-13 Thread Marcus Brinkmann
On Sat, Oct 12, 2002 at 10:37:52PM -0400, Roland McGrath wrote: > Generally speaking, leaking send rights should be considered like leaking > memory and programs that leak any send rights are buggy. This goes for the > thread and task send rights just like any other. The mach_task_self macro > us