Re: settrans: (os/kern) invalid right

2021-05-08 Thread Samuel Thibault
Sergey Bugaev, le sam. 08 mai 2021 14:51:22 +0300, a ecrit: > if we failed to set the translator (either > because of this issue, or for any other reason), let's shut the > translator back down instead of leaving it in limbo. We'd rather do that indeed, thanks! Samuel

Re: settrans: (os/kern) invalid right

2021-05-08 Thread Samuel Thibault
Sergey Bugaev, le sam. 08 mai 2021 14:51:22 +0300, a ecrit: > P.S. There must be something wrong with your mailserver. I only > received a bunch of replies form you just a few minutes ago, and > seemingly so did the archive [0], but your citation indicates that you > have sent the reply promptly af

Re: settrans: (os/kern) invalid right

2021-05-08 Thread Sergey Bugaev
On Sat, May 8, 2021 at 2:39 PM Samuel Thibault wrote: > I pushed the revert, thanks! Thank you! I'm attaching another patch that tries to make settrans handle this case a tiny bit better: if we failed to set the translator (either because of this issue, or for any other reason), let's shut the t

Re: settrans: (os/kern) invalid right

2021-05-08 Thread Samuel Thibault
Hello, Sergey Bugaev, le ven. 07 mai 2021 15:41:17 +0300, a ecrit: > I don't think I understand the reasoning behind [1]. Perhaps I'm > missing something? I don't see either why not deallocating it. Event if it's a dead name, we want to deallocate it, so as to free the port name. Samuel

Re: settrans: (os/kern) invalid right

2021-05-08 Thread Samuel Thibault
Samuel Thibault, le ven. 07 mai 2021 15:29:49 +0200, a ecrit: > Sergey Bugaev, le ven. 07 mai 2021 15:41:17 +0300, a ecrit: > > I don't think I understand the reasoning behind [1]. Perhaps I'm > > missing something? > > I don't see either why not deallocating it. Event if it's a dead name, > we wa

Re: settrans --chroot

2002-05-27 Thread Roland McGrath
> On Sat, May 04, 2002 at 06:58:59PM -0400, Roland McGrath wrote: > > I suspect that presently if you use this (assuming settrans works right), > > that the filesystem process will stick around after the command finishes > > and you might have to kill it. > > Indeed, this is what happens. > > >

Re: settrans --chroot

2002-05-26 Thread Marcus Brinkmann
On Sat, May 04, 2002 at 06:58:59PM -0400, Roland McGrath wrote: > I suspect that presently if you use this (assuming settrans works right), > that the filesystem process will stick around after the command finishes > and you might have to kill it. Indeed, this is what happens. > If that happens,

Re: settrans

2001-01-24 Thread Roland McGrath
> Sorry, I assumed that it was a mistake was in my code; Should I report > it to the gdb people? Well, the "gdb people" for the Hurd is Mark. > Here is what gdb said: > (gdb) p _hurd_init > _hurd_init _hurd_init_dtable _hurd_init_dtablesize See, I told you I got the name wrong.

Re: settrans

2001-01-24 Thread Neal H Walfield
On Wed, Jan 24, 2001 at 02:33:53AM -0500, Roland McGrath wrote: > > > First, please check whether the scenario you are trying does or doesn't > > > exhibit the same bug in a vanilla system without your changes. > > > > The exact same error. > > Well, you certainly could have saved some wild goo

Re: settrans

2001-01-23 Thread Roland McGrath
> > First, please check whether the scenario you are trying does or doesn't > > exhibit the same bug in a vanilla system without your changes. > > The exact same error. Well, you certainly could have saved some wild goose chases by making that clear in the first place. > It is blocked in the c

Re: settrans

2001-01-23 Thread Neal H Walfield
On Sat, Jan 20, 2001 at 05:44:13PM -0500, Roland McGrath wrote: > This is pretty confusing to me, but it's hard to see much without being > able to debug it myself. > > First, please check whether the scenario you are trying does or doesn't > exhibit the same bug in a vanilla system without your

Re: settrans

2001-01-20 Thread Roland McGrath
This is pretty confusing to me, but it's hard to see much without being able to debug it myself. First, please check whether the scenario you are trying does or doesn't exhibit the same bug in a vanilla system without your changes. Next, here are some things to try. When you attach gdb, look a

Re: settrans

2001-01-17 Thread Neal H Walfield
On Wed, Jan 17, 2001 at 10:00:43PM -0500, Neal H Walfield wrote: > On Wed, Jan 17, 2001 at 06:21:40PM -0500, Roland McGrath wrote: > > I don't see anything obviously wrong (other than your spelling of "semantics"). > > Do you think it might be an error elsewhere, e.g. in gdb or the proc > server?

Re: settrans

2001-01-17 Thread Neal H Walfield
On Wed, Jan 17, 2001 at 06:21:40PM -0500, Roland McGrath wrote: > I don't see anything obviously wrong (other than your spelling of "semantics"). Do you think it might be an error elsewhere, e.g. in gdb or the proc server? PGP signature

Re: settrans

2001-01-17 Thread Roland McGrath
I don't see anything obviously wrong (other than your spelling of "semantics"). ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Re: settrans

2001-01-17 Thread Neal H Walfield
Here are all the changes: diff -rNu --exclude libtrivfs hurd-2115/daemons/ChangeLog hurd/daemons/ChangeLog --- hurd-2115/daemons/ChangeLog Tue Sep 28 09:17:24 1999 +++ hurd/daemons/ChangeLog Wed Jan 17 01:47:53 2001 @@ -1,3 +1,8 @@ +2001-01-17 Neal H Walfield <[EMAIL PROTECTE