From: Andreas Schwab <schwab@suse.de>
To: "Miquel van Smoorenburg" <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OLS and console rearchitecture
Date: Mon, 02 Aug 2004 18:21:04 +0200 [thread overview]
Message-ID: <je3c35qznz.fsf@sykes.suse.de> (raw)
In-Reply-To: <celori$joe$1@news.cistron.nl> (Miquel van Smoorenburg's message of "Mon, 2 Aug 2004 16:07:14 +0000 (UTC)")
"Miquel van Smoorenburg" <miquels@cistron.nl> writes:
> In article <410E55AA.8030709@ums.usu.ru>,
> Alexander E. Patrakov <patrakov@ums.usu.ru> wrote:
>>Jon Smirl wrote:
>>> 15) Over time user space console will be moved to a model where VT's
>>> are implemented in user space. This allows user space console access to
>>> fully accelerated drawing libraries. This might allow removal of all of
>>> the tty/vc layer code avoiding the need to fix it for SMP.
>>
>>One more minor problem. We need to ensure somehow that the "killall5"
>>program from the sysvinit package will not kill our userspace console
>>daemon at shutdown (got this when I tried to put fbiterm into
>>initramfs). What is the best way to achieve that?
>
> A configuration file for killall5 in which services/daemons get
> defined that should not be signalled ?
IMHO a better solution would be some kind of process flag that can be
interrogated by killall5.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-08-02 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:24 Jon Smirl
2004-08-02 14:54 ` Alexander E. Patrakov
2004-08-02 16:07 ` Miquel van Smoorenburg
2004-08-02 16:21 ` Andreas Schwab [this message]
2004-08-02 17:40 ` Alan Cox
2004-08-03 8:44 ` Andreas Schwab
2004-08-02 16:16 ` Jon Smirl
2004-08-05 11:08 ` Martin Waitz
2004-08-02 18:33 ` Jesse Barnes
2004-08-03 0:01 ` Benjamin Herrenschmidt
2004-08-05 8:56 ` Helge Hafting
2004-08-05 20:32 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=je3c35qznz.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®