From: David Dillow <dave@thedillows.org>
To: mark.doffman@codethink.co.uk
Cc: ceph-devel@vger.kernel.org, sage@inktank.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, rob.taylor@codethink.co.uk
Subject: Re: [PATCH 0/4] Add ceph root filesystem functionality and documentation.
Date: Thu, 21 Nov 2013 15:19:46 -0500 [thread overview]
Message-ID: <1385065186.18238.0.camel@frustration.ornl.gov> (raw)
In-Reply-To: <1385000024-23463-1-git-send-email-mark.doffman@codethink.co.uk>
On Wed, 2013-11-20 at 20:13 -0600, mark.doffman@codethink.co.uk wrote:
> The following patch series adds the ability to use a ceph distributed
> file system as the root device. The functionality is similar to
> NFS root but for the ceph filesystem.
Why do this in the kernel vs in the initramfs? Dracut would be a more
appropriate place, I think, as it has support for other network root
devices already.
next prev parent reply other threads:[~2013-11-21 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 2:13 mark.doffman
2013-11-21 2:13 ` [PATCH 1/4] init: Add a new root device option, the Ceph file system mark.doffman
2013-12-07 6:10 ` Sage Weil
2013-11-21 2:13 ` [PATCH 2/4] Documentation: Document the cephroot functionality mark.doffman
2013-12-07 5:57 ` Sage Weil
2014-01-15 17:22 ` Mark Doffman
2013-11-21 2:13 ` [PATCH 3/4] cephroot: Add DHCP option 17 configuration to ceph root fs mark.doffman
2013-11-21 2:13 ` [PATCH 4/4] Reuse root_nfs_parse_addr() for NFS and CEPH mark.doffman
2013-11-21 20:19 ` David Dillow [this message]
2013-11-22 16:53 ` [PATCH 0/4] Add ceph root filesystem functionality and documentation Mark Doffman
2014-01-15 17:26 ` [PATCH v2 0/2] " mark.doffman
2014-01-15 17:26 ` [PATCH v2 1/2] init: Add a new root device option, the Ceph file system mark.doffman
2014-01-15 17:26 ` [PATCH v2 2/2] Documentation: Document the cephroot functionality mark.doffman
2014-01-15 18:00 ` Randy Dunlap
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=1385065186.18238.0.camel@frustration.ornl.gov \
--to=dave@thedillows.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mark.doffman@codethink.co.uk \
--cc=netdev@vger.kernel.org \
--cc=rob.taylor@codethink.co.uk \
--cc=sage@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®