All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: andrew.warfield@cl.cam.ac.uk, xen-devel@lists.sourceforge.net
Subject: Re: x2d2
Date: Wed, 19 Jan 2005 14:19:37 -0500	[thread overview]
Message-ID: <200501191919.AFJ00168@ms13.netsolmail.com> (raw)

---- Original message ----
>From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>  
>
>We thought about the pty approach, but resisted it because we
>thought that in most setups there'd need to be a daemon running
>in user-space to export the console (typically over the network),
>and hence it wasn't worth the effort of turning it into a pty in
>the kernel. 

The daemon we wrote does the pty stuff in user space.  It's particularly
useful in unix becase pty's can be connected to all sorts of interesting
things like remote Xterms and ssh sessions.

One particularly useful feature of pty's is delegation.  Since you can
set pty's with standard unix file permissions (maybe even posix acls?)
you can delegate console access in a pretty sophisticated way.

You cannot easily do that with normal sockets.

>The current approach also minimizes the amount of OS-specific Xen
>privileged interface code, which keeps the people interested in
>using OSes other than Linux in domain 0 happy.

I agree here.  pts's are part of Posix though.  Of course more esoteric
OSes that don't have Posix support will need another mechanism but
they'll probably need a lot of work anyway to be used in dom0.

>I could be persuaded, though...

That's always a good sign :-)

Regards,

>Ian


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

             reply	other threads:[~2005-01-19 19:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 19:19 Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-19 20:43 x2d2 Ian Pratt
2005-01-19 21:03 ` x2d2 Derrik Pates
2005-01-19 21:17   ` x2d2 Ronald G. Minnich
2005-01-19 20:37 x2d2 Ian Pratt
2005-01-19 20:38 ` x2d2 Ronald G. Minnich
2005-01-19 21:23 ` x2d2 Anthony Liguori
2005-01-19  2:19 x2d2 Jacob Gorm Hansen
2005-01-19  4:20 ` x2d2 Ronald G. Minnich
2005-01-19  6:32 ` x2d2 Anthony Liguori
2005-01-19  9:58   ` x2d2 Jacob Gorm Hansen
2005-01-19 10:12     ` x2d2 Andrew Warfield
2005-01-19 14:11       ` x2d2 Anthony Liguori
2005-01-19 16:36         ` x2d2 Ian Pratt
2005-01-19 16:44           ` x2d2 Andrew Warfield
2005-01-19 20:12           ` x2d2 Ronald G. Minnich
2005-01-21  0:22       ` x2d2 Michael Hohnbaum
2005-01-21  0:35         ` x2d2 Andrew Warfield
2005-01-19 15:47   ` x2d2 Ronald G. Minnich
2005-01-19 19:01     ` x2d2 Anthony Liguori
2005-01-19 18:55       ` x2d2 Ronald G. Minnich
2005-01-20 14:08         ` x2d2 Rik van Riel
2005-01-20 18:36       ` x2d2 Rik van Riel
2005-01-20 22:45         ` x2d2 Felipe Alfaro Solana
2005-01-19 23:24   ` x2d2 Adam Sulmicki
2005-01-19 12:00 ` x2d2 Grzegorz Milos

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=200501191919.AFJ00168@ms13.netsolmail.com \
    --to=anthony@codemonkey.ws \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=andrew.warfield@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.