From: Travis Newman <panickedthumb@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: Xen kernel issue
Date: Sun, 30 Jan 2005 21:05:45 -0500 [thread overview]
Message-ID: <41FD9279.9000605@gmail.com> (raw)
In-Reply-To: <41FD8C08.6070800@gmail.com>
Travis Newman wrote:
> Sorry to keep posting, just wanted to update this on where I am now.
>
>> I've gotten Xen working for dom0, but I haven't gone past that because
>> when using the Xen kernel, there's no support for fat filesystems
...
>> and no support for sound
Sorry to keep replying to my own posts here, but I think I may have
figured out something of interest. For a second I thought everything was
going to work, until I realized I'd left off ARCH=xen this time. make
oldconfig did exactly what I thought it should. It only asked me a very
few questions, which I assumed were from missing entries in the config
file, but that's when I realized I'd left off the ARCH argument. This is
the point in the documentation when it says it should ask you just a few
questions about Xen stuff, to which you should leave the defaults. Well
it did ask those questions, but it also seemed to completely ignore the
.config file altogether. Just thought that may shed some light on the
subject.
Again, thanks for putting up with me ;)
Travis
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-01-31 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 20:43 Xen kernel issue Travis Newman
2005-01-31 1:38 ` Travis Newman
2005-01-31 2:05 ` Travis Newman [this message]
2005-01-31 2:58 ` Robin Green
[not found] ` <f6244b740502011740392349b8@mail.gmail.com>
2005-02-02 2:18 ` Robin Green
2005-01-31 3:03 ` Mark Williamson
2005-01-31 4:57 ` Travis Newman
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=41FD9279.9000605@gmail.com \
--to=panickedthumb@gmail.com \
--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.