From: Blair Zajac <blair@orcaware.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "Daniel Kozák" <kozzi11@gmail.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Running Apache Derby on 3.8 and BTRFS cause kernel oops
Date: Thu, 28 Feb 2013 12:28:23 -0800 [thread overview]
Message-ID: <512FBDE7.5000906@orcaware.com> (raw)
In-Reply-To: <20130228200503.GL19641@localhost.localdomain>
On 02/28/2013 12:05 PM, Josef Bacik wrote:
>
> Ok so now that I have it reproducing, how do I go about getting a custom kernel
> on there? I'm used to libvirt where all the networking stuff is done for me,
> this doesn't seem to connect to the network at all and it also doesn't seem to
> have mount.nfs so I can't do what I normally do and mount my local drive as nfs
> and install the new kernel. What is the best way to go about doing this?
I run these images in OpenStack or with kvm. Its a very bare OS, so
you'll need to install NFS and anything else you need on it.
Did it not come up with networking? I was able to do an 'apt-get
update' on it. It needs to boot with the seed.iso for it to get proper
networking, as it uses the cloud-init package to configure itself (it's
meant to be deployed into EC2 or OpenStack).
Blair
next prev parent reply other threads:[~2013-02-28 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 13:20 Running Apache Derby on 3.8 and BTRFS cause kernel oops Daniel Kozák
2013-02-27 13:25 ` Josef Bacik
2013-02-27 18:19 ` Daniel Kozák
2013-02-27 22:08 ` Josef Bacik
2013-02-27 22:59 ` Blair Zajac
2013-02-28 15:47 ` Josef Bacik
2013-02-28 18:31 ` Daniel Kozák
2013-02-28 18:35 ` Josef Bacik
2013-02-28 18:41 ` Blair Zajac
2013-02-28 20:05 ` Josef Bacik
2013-02-28 20:28 ` Blair Zajac [this message]
2013-02-28 21:21 ` Tomasz Torcz
2013-02-28 22:00 ` Josef Bacik
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=512FBDE7.5000906@orcaware.com \
--to=blair@orcaware.com \
--cc=jbacik@fusionio.com \
--cc=josef@toxicpanda.com \
--cc=kozzi11@gmail.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).