All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: dima <dolenin@parallels.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: What is best practice when partitioning a device that holds one or more btr-filesystems
Date: Thu, 15 Dec 2011 09:55:30 +0100	[thread overview]
Message-ID: <20111215085530.GA31915@attic.humilis.net> (raw)
In-Reply-To: <4EE9AFD8.1010306@parallels.com>

dima wrote (ao):
> >>format the device to
> >>btrfs and use subvolumes instead of your usual partitions (some
> >>/boot restrictions apply). You won't be able to use grub2 though,
> >>but syslinux will work.
> >
> >Grub2 has btrfs support for quite some time now, which you are aware of
> >I assume. Grub2 can't cope with / in a subvolume or something?
> 
> No, btrfs has nothing to do with this. It is just that grub2 cannot
> be installed to a partition-less drive (at least 1 partition is
> needed), while syslinux can.

Ah, wasn't aware of that. Thanks for the info!

	Sander
 
-- 
Humilis IT Services and Solutions
http://www.humilis.net

      reply	other threads:[~2011-12-15  8:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 13:00 What is best practice when partitioning a device that holds one or more btr-filesystems Wilfred van Velzen
2011-12-14 13:17 ` Helmut Hullen
2011-12-14 16:43 ` Peeters Simon
     [not found] ` <CAKcLGm-LZmyOKm4gegZDRYaq-DO-KW+5CCb_E7n8WvF0fEFCeQ@mail.gmail.com>
2011-12-14 18:51   ` Wilfred van Velzen
     [not found]     ` <CA+WRLO98Je2J1SMZv0zVi1r1AfGFcnUCHKU=sJAsYDuUssqx8w@mail.gmail.com>
2011-12-14 21:42       ` Wilfred van Velzen
2011-12-14 22:46         ` Fajar A. Nugraha
2011-12-15  0:42         ` Kok, Auke-jan H
2011-12-15  1:09     ` dima
2011-12-15  8:25       ` Sander
2011-12-15  8:29         ` dima
2011-12-15  8:55           ` Sander [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=20111215085530.GA31915@attic.humilis.net \
    --to=sander@humilis.net \
    --cc=dolenin@parallels.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 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.