mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Debuggers, KDB or KGDB?
Date: Wed, 2 May 2001 16:44:51 +0200	[thread overview]
Message-ID: <20010502164451.L706@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010501113758.D3305@nightmaster.csn.tu-chemnitz.de> <200105011522.KAA01925@ccure.karaya.com>
In-Reply-To: <200105011522.KAA01925@ccure.karaya.com>; from jdike@karaya.com on Tue, May 01, 2001 at 10:22:14AM -0500

On Tue, May 01, 2001 at 10:22:14AM -0500, Jeff Dike wrote:
> ingo.oeser@informatik.tu-chemnitz.de said:
> > Basically you could add support for ALL generic subsystems, that
> > support dummy hardware, like SCSI and ISDN for example.
> > Is that planned or do I suggest sth. stupid here? ;-) 
> 
> Neither.  I know squat about hardware, so I had no idea that SCSI and ISDN 
> would be easy to do from UML.
> 
> If the SCSI and ISDN people want to produce appropriate UML drivers, I take 
> patches :-)

Everything is there. SCSI and ISDN have the equivalent devices of the
"lo" driver for the networking layer. Or the equivalent of
tun/tap devices for the ethernet layer.

It just have to be an config.in option in UML and every other
adapters switched off.

The problem is: I still do not really get how UML really works.
Many of the mapping rules (Kernel machanism on normal arch ->
UML) are not quite clear to me.

Is there a paper or sth. like that describing the design a bit
more in detail? I only found usage papers on the user-mode-linux
home page.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<     been there and had much fun   >>>>>>>>>>>>

  reply	other threads:[~2001-05-02 14:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 21:17 Paul J Albrecht
2001-05-01  0:11 ` Jeff Dike
2001-05-01  9:37   ` Ingo Oeser
2001-05-01 15:22     ` Jeff Dike
2001-05-02 14:44       ` Ingo Oeser [this message]
2001-05-02 17:54         ` Jeff Dike
2001-05-02 16:55           ` Alan Cox
2001-05-02 19:06             ` Jeff Dike
2001-05-02 18:54               ` Bill Nottingham
2001-05-01  1:16 ` Keith Owens
2001-05-01 10:59   ` Amit S. Kale
2001-05-02 14:58   ` Andi Kleen
2001-05-02 21:06   ` Paul J Albrecht
2001-05-02 23:03     ` Keith Owens
2001-05-03 14:46       ` Amit S. Kale
     [not found] <linux.kernel.18223.988679810@kao2.melbourne.sgi.com>
2001-05-01  7:13 ` Aaron Passey

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=20010502164451.L706@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=jdike@karaya.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

all inboxes | Powered by JetHome®