public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John P. Looney" <john@antefacto.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux as a minicomputer ?
Date: Thu, 11 Apr 2002 17:49:42 +0000	[thread overview]
Message-ID: <20020411174941.GC17962@antefacto.com> (raw)
In-Reply-To: <20020411154601.GY17962@antefacto.com> <20020411164331.GR612@gallifrey> <20020411184923.A15238@ucw.cz> <20020411170910.GS612@gallifrey> <20020411191339.B15435@ucw.cz>

On Thu, Apr 11, 2002 at 07:13:39PM +0200, Vojtech Pavlik mentioned:
> > I'd presumed this was
> > the whole point of the busid spec in the config file.
> No, it's for running one Xserver on multiple displays at once only.
> Sad, ain't it?

 Very sad. Nice to know it's not really the kernel's fault. 

 Is it possible to say "Any mice plugged in to this port is
/dev/input/mouse3" etc. so that if someone plugged out your mouse, plugged
in another into a different port, and you plugged yours back in, that they
wouldn't renumberate ?

Kate
 
-- 
_______________________________________
John Looney             Chief Scientist
a n t e f a c t o     t: +353 1 8586004
www.antefacto.com     f: +353 1 8586014


  reply	other threads:[~2002-04-11 17:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 15:46 linux as a minicomputer ? John P. Looney
2002-04-11 16:43 ` Dr. David Alan Gilbert
2002-04-11 16:49   ` Vojtech Pavlik
2002-04-11 17:07     ` Ed Sweetman
2002-04-11 17:12       ` Vojtech Pavlik
     [not found]         ` <3CB69032.D332FA51@aitel.hist.no>
2002-04-12  8:08           ` Vojtech Pavlik
2002-04-11 17:09     ` Dr. David Alan Gilbert
2002-04-11 17:13       ` Vojtech Pavlik
2002-04-11 17:49         ` John P. Looney [this message]
2002-04-11 17:59           ` Rene Rebe
2002-04-11 18:46             ` James Simmons
2002-04-11 19:06             ` Vojtech Pavlik
2002-04-12  7:41               ` Helge Hafting
2002-04-12  8:09                 ` Vojtech Pavlik
2002-04-11 18:01           ` James Simmons
2002-04-11 19:07           ` Vojtech Pavlik
2002-04-13 19:03       ` Alan Cox
2002-04-11 19:45 ` H. Peter Anvin
2002-04-11 20:05   ` James Simmons
2002-04-12  7:31     ` Helge Hafting
2002-04-13 18:56   ` Alan Cox
2002-04-13 19:29     ` H. Peter Anvin
2002-04-13 19:37       ` Richard Gooch
2002-04-13 19:40         ` H. Peter Anvin
2002-04-13 19:49           ` Richard Gooch
2002-04-13 22:08             ` J.A. Magallon
2002-04-13 23:46               ` Richard Gooch
2002-04-13 19:51       ` Alan Cox
2002-04-13 19:36         ` H. Peter Anvin
2002-04-14  4:30         ` Bill Davidsen
2002-04-14 13:45           ` Alan Cox
2002-04-14 16:44             ` Sten
2002-04-14 16:50               ` Dr. David Alan Gilbert
2002-04-14 20:20                 ` H. Peter Anvin
2002-04-15 16:05                 ` Thomas Molina
2002-04-15  0:37             ` Rob Landley
2002-04-15  8:46               ` Helge Hafting
2002-04-15  9:10               ` Alan Cox
     [not found]               ` <3CBB522C.8070704@bcgreen.com>
2002-04-15 18:09                 ` Rob Landley
2002-04-14  2:35       ` ux " jw schultz
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11 17:42 linux " Ivan Ivanov

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=20020411174941.GC17962@antefacto.com \
    --to=john@antefacto.com \
    --cc=linux-kernel@vger.kernel.org \
    /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