All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Katz <katzj@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: RE: Building domains as a lesser user (was Re: [Xen-devel] bootloaders for domain != 0)
Date: Fri, 04 Feb 2005 08:20:53 -0500	[thread overview]
Message-ID: <1107523253.7797.7.camel@bree.local.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1236FE@liverpoolst.ad.cl.cam.ac.uk>

On Fri, 2005-02-04 at 09:38 +0000, Ian Pratt wrote:
> > On Fri, 2005-02-04 at 02:30 +0000, Ian Pratt wrote:
> > Especially as you start thinking about things like modular fs's, etc,
> > it's going to be much less clean of a solution and be a significant
> > slowdown on your guest boot time.
> 
> A few seconds slow down -- nothing compared to what a BIOS normally
> adds.
> 
> I don't see why the filesystems would particularly need to be modular,
> though you might do so for convenience. 

Because if the kernel is _different_ than every other kernel being
shipped by a distribution, then it's a major pain.  It also ends up
giving people a lot less flexibility (because if I were to do that, for
example, it would only have ext[23] support leaving users of
reiserfs/xfs/jfs/foofs out in the cold whereas with a modular solution,
they can at least add the support for what they want).

> > And then, it's yet another kernel to keep updated, etc.
> 
> I don't see any reason to keep it up to date. Its running in a protected
> environemnt and doesn't have any extra access that the kernel about to
> be booted is going to get.

Users don't tend to take that answer very well ;)  The protected
environment means you can have a little bit longer to fix it, but they
have things like audit requirements, etc.  And just because it's running
in a protected environment doesn't mean it's bug-free.  Or that it's
going to be able to stand still as filesystem features are added, etc.
This ends up being less of a concern with minimalistic implementations
for reading filesystems like grub's and libext2fs.

Jeremy



-------------------------------------------------------
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

  parent reply	other threads:[~2005-02-04 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04  9:38 Building domains as a lesser user (was Re: bootloaders for domain != 0) Ian Pratt
2005-02-04 10:23 ` Andy Whitcroft
2005-02-04 13:21   ` Building domains as a lesser user (was Re: [Xen-devel] " Jeremy Katz
2005-02-04 17:36     ` Andy Whitcroft
2005-02-04 13:20 ` Jeremy Katz [this message]
2005-02-04 13:27   ` Mark Williamson
2005-02-04 13:47     ` Jeremy Katz
  -- strict thread matches above, loose matches on Subject: below --
2005-02-04 13:44 Building domains as a lesser user (was Re: [Xen-devel]bootloaders " Ian Pratt

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=1107523253.7797.7.camel@bree.local.net \
    --to=katzj@redhat.com \
    --cc=m+Ian.Pratt@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.