The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Pavel Machek <pavel@suse.cz>, Rakesh Kumar Banka <Rakesh@asu.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Monolithic Vs. Microkernel
Date: 05 Mar 2002 22:17:11 +0100	[thread overview]
Message-ID: <1015363031.9958.3.camel@bip> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203051803120.1413-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.44L.0203051803120.1413-100000@duckman.distro.conectiva>

le mar 05-03-2002 à 22:04, Rik van Riel a écrit :
> On Mon, 4 Mar 2002, Pavel Machek wrote:
> 
> > > This means we can have all the advantages of modularity at the
> >
> > Not *all* of them. On vsta, you could do
> >
> > ( killall keyboard; sleep 1; keyboard ) &
> 
> How is that different from the following ?
> 
> (rmmod keyboard ; sleep 1 ; modprobe keyboard)
> 
> [no, no need to talk about hardware access ... vsta's keyboard
> driver also has hardware access]

killall works when keyboard is deadlocked, I suppose.



  reply	other threads:[~2002-03-05 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26  6:11 Monolithic Vs. Microkernel Rakesh Kumar Banka
2002-02-26  6:17 ` Larry McVoy
2002-02-26  9:49   ` Alan Cox
2002-02-26  6:17 ` David Lang
2002-02-26  6:23 ` Eric Krout
2002-02-26 11:45 ` Rik van Riel
2002-03-04 14:49   ` Pavel Machek
2002-03-05 20:34     ` Alexander Viro
2002-03-05 20:47       ` Pavel Machek
2002-03-05 21:04     ` Rik van Riel
2002-03-05 21:17       ` Xavier Bestel [this message]
2002-03-06 11:22       ` Pavel Machek
2002-03-05 21:32     ` Bernd Eckenfels
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 10:34 Hans Adams

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=1015363031.9958.3.camel@bip \
    --to=xavier.bestel@free.fr \
    --cc=Rakesh@asu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=riel@conectiva.com.br \
    /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