All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murillo Bernardes <mfb@br.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, Sean Dague <japh@us.ibm.com>
Subject: Re: [PATCH] build in SATA drivers to the -xen kernel forx86_64
Date: Thu, 30 Mar 2006 12:01:47 -0300	[thread overview]
Message-ID: <200603301201.48060.mfb@br.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA001@liverpoolst.ad.cl.cam.ac.uk>

On Wednesday 29 March 2006 17:40, Ian Pratt wrote:
> > This patch adds in the SATA drivers that are supported in the
> > -xen0 kernel.
> > Because the default behavior of xen is to reboot on a dom0
> > crash (i.e. not finding root filesystem), and the xen0 kernel
> > supported SATA directly, a number of people (including
> > myself) got caught by the switch over.
> >
myself also

> > Long term, we probably want to modularize more of the kernel,
> > and make initrd building more of the default, however this
> > should ease people's transition from the -xen0 => -xen kernel
> > for testing on x86_64.
>
> Is it even possible to boot a modern distro without an initrd? Most
> require an initrd for udev/console stuff.
>
Surely it's possible. I have debian and gentoo running without a initrd.

> I'd certainly like to see a patch (and clear documentation) that helps
> users with building an appropriate initrd.
>
It would be good, but be able to boot without an initrd too is really better.

> [I'd wouldn't mind seeing a couple of common SATA controllers included
> in the -xen config anyhow.]

-- 
Murillo Fernandes Bernardes
IBM Linux Technology Center

      parent reply	other threads:[~2006-03-30 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 20:40 [PATCH] build in SATA drivers to the -xen kernel forx86_64 Ian Pratt
2006-03-29 20:59 ` Sean Dague
2006-03-30  9:56   ` Harry Butterworth
2006-03-30  0:11 ` Adam Heath
2006-03-30 15:01 ` Murillo Bernardes [this message]

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=200603301201.48060.mfb@br.ibm.com \
    --to=mfb@br.ibm.com \
    --cc=japh@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.