You could of course also do something like
"/etc/init.d/console-client stop" in the console client...
You mean, deco stop console-client. :-)
I suppose that could work, sending SIGTERM or some such.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
At Fri, 11 Mar 2005 01:12:00 +0100,
Alfred M Szmidt wrote:
>
>The point is that you actually want to break out of it if you are
>indeed in an infinite loop.
>
> This isn't really related to when console-client starts dieing, and
> you get into a infinite loop, but it would be nice when yo
The point is that you actually want to break out of it if you are
indeed in an infinite loop.
This isn't really related to when console-client starts dieing, and
you get into a infinite loop, but it would be nice when you actually
wish to drop out into the Mach console by force.
What do you
On Thu, Mar 10, 2005 at 02:04:32AM +0100, Marcus Brinkmann wrote:
> This is not the point. The point is that you actually want to break
> out of it if you are indeed in an infinite loop. Because if you are
> in such a loop, then it is a bug that prevents anybody from logging
> in, and it is prefe
I'd like to see the console-client fixed so that it not blank the
screen etc., until there is at least one tty setup.
A better solution is to actually fix console-client to just show what
was on the screen before (and as such, allow for messages from the
Mach console to be shown). But this
- Original Message -
From: "Michael Banck" <[EMAIL PROTECTED]>
To:
Cc: "Robert Millan" <[EMAIL PROTECTED]>
Sent: Thursday, March 10, 2005 10:33 AM
Subject: Re: Bug#298856: RFA: libsem
> On Thu, Mar 10, 2005 at 12:51:03PM +0100, Robert Millan wrote:
> > The GNU/kFreeBSD port no longer de
On Thu, Mar 10, 2005 at 02:05:04PM +0100, Marc Dequenes wrote:
> Is there a special place for glibc stuff ?
bug-hurd or libc-alpha, depending on the problem, I guess. I suggest
trying bug-hurd first.
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mb
On Thu, Mar 10, 2005 at 12:51:03PM +0100, Robert Millan wrote:
> The GNU/kFreeBSD port no longer depends on libsem (as it switched to
> linuxthreads) and I'm told the GNU/Hurd port will soon switch to NPTL,
> so it won't need libsem either.
Who told you that? "Soon" in conjunction with the Hurd is
Michael Banck <[EMAIL PROTECTED]> writes:
> On Wed, Mar 09, 2005 at 05:49:34PM -0700, Duck wrote:
>> Depends on hurd-select problem in glibc being solved.
>
> Can you elaborate on this, please?
I'd rather add a task on alioth for this. Filling the patch tracker was
so long and boring i defered th
Package: wnpp
Severity: normal
Hi!
The GNU/kFreeBSD port no longer depends on libsem (as it switched to
linuxthreads) and I'm told the GNU/Hurd port will soon switch to NPTL, so it
won't need libsem either.
Unless someone who is actualy interested in libsem volunteers to maintain it,
I'll reques
On Wed, Mar 09, 2005 at 05:49:34PM -0700, Duck wrote:
> Depends on hurd-select problem in glibc being solved.
Can you elaborate on this, please?
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html
--
To UNSUBSCRIBE, email to [EMAIL PR
11 matches
Mail list logo
