I agree with your analysis. I think your current behavior is probably best.
This is a general problem with all semantics that entail something active
or synchronized happening on `close', e.g. POSIX.1 file locking has similar
questions (though not quite as bad). As I read the Linux implementati
Thanks for following up. I moved that assert to below the `if' clause that
handles port notifications, and that should fix the problem. Please let me
know if that works.
Thanks,
Roland
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/m
On Thu, Sep 27, 2001 at 06:00:03PM -0700, Thomas Bushnell, BSG wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > the default pager in serverboot (also used by mach-defpager) is still using
> > the legacy interfaces memory_object_set_attributes() and
> > memory_object_data_write() to set
On Sat, 13 Oct 2001, Roland McGrath wrote:
> It's not totally clear to me what all your debug printfs mean. When using
> a modified version of the program, please include your changes so we can
> see exactly what your program was printing. I can't tell whether your
> output includes all the e
On Mon, Oct 15, 2001 at 01:43:52AM +0200, Marcus Brinkmann wrote:
> I checked in a similar implementation that works correctly,
Mmmh. I just read up about SO_LINGER in Stevens, and it seems that the
implementation ismostly bogus. As far as I can see, the sock_release only
ever happens when the
On Thu, Aug 30, 2001 at 07:45:37PM -, kurian kattukaren wrote:
> >> thread_t current = mach_current_thread();
> >> int long schedule_timeout(long int timeout)
> void process_timeout(unsingned long data)
[snipped]
Hi,
I checked in a similar implementation that works correctly, and also use
Roland McGrath <[EMAIL PROTECTED]> writes:
Hello,
>> The first question was: If shadowfs supports having an explicitely
>> specified writable filesystem[0], shadowfs might has to create whole
>> directory hierarchies - how can this be done? (Or should it be done at
>> all?.)
>
> In a shadowfs th
With the new boot code, oskit's environment searched for the root variable.
You have to put a "--" after the "root=", i.e.
kernel /boot/oskit-mach.gz root=part:1:device:hd0 --
If you don't do that, the "root=" variable is in the argc and argv
variables. It's explained in the comments in
oskit/ke
[I redirected the CC to bug-hurd, since this is not Debian-related stuff.]
> I'm also looking for a way to start a translator from gdb or
> at least watch the translator run from the start of main().
Use "settrans -a --pause /node /translator args". It will print out the
translator's pid and w
On Sat, Oct 13, 2001 at 03:58:40PM -0400, Roland McGrath wrote:
> > in oskit-mach, the RSS for the oskit-mach kernel in proc is bogus:
> > 0159744
Damn. I meant to type -159744.
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann
On Sat, Oct 13, 2001 at 03:58:40PM -0400, Roland McGrath wrote:
> > in oskit-mach, the RSS for the oskit-mach kernel in proc is bogus:
> > 0159744
> >
> > The vmem size seems to be okay with 122M. The user time is 0, which also
> > seems to be bogus, while the system time is okay.
>
> Uh, ok.
Thanks, I've put your term change in.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
12 matches
Mail list logo