From: C Anthony Risinger <anthony@extof.me>
To: Evert Vorster <evorster@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: quick question...
Date: Sun, 8 Aug 2010 21:13:32 -0500 [thread overview]
Message-ID: <AANLkTinc_9RoGnt9OPrVLBGuGfEvQrTiM1s2ui3tZDp1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimTTr0pFw5Y_O7nNUjH4z1UCRUsfYpe+NYtc7wZ@mail.gmail.com>
i'm not an expert, but ill do my best to answer. replies interspersed below.
On Sun, Aug 8, 2010 at 8:57 PM, Evert Vorster <evorster@gmail.com> wrote:
> Hi there.
>
> Has anybody got a btrfs root filesystem that is running on a bare
> block device? Would lilo be able to boot an initramfs that is living
> on such a filesystem?
i haven't [ever] used lilo, but AFIAK no bootloader, with the
exception of maybe syslinux (extlinux), can boot from a btrfs device;
you won't have to worry about the initramfs, because the loader won't
even be able to find the kernel. you'll need a boot partition with a
filesystem supported by the loader.
> What I intend to do is to erase all the partitions off my system, make
> a btrfs volume on /dev/sda, and then just use subvolumes in stead of
> partitions.
>
> Is this folly?
not at all. this is what many of us would like to do, but we run into
the bootloader issues above.
> Would having an initramfs be a boon or a bane in this endeavour?
a non-issue, as the bootloader cannot even get the kernel (unless your
booting the kernel/initramfs from a different device...)
> Would lilo writing to the mbr of a device that is claimed by btrfs
> break the file system?
i don't think so, but i'm not sure.
> Do you need to have a partition table to have an MBR?
i just read about this recently. IIRC, the partition table is within
the 512 byte MBR; it's a 64 byte section starting at byte 446. so...
no :-)
C Anthony
prev parent reply other threads:[~2010-08-09 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 1:57 quick question Evert Vorster
2010-08-09 2:13 ` C Anthony Risinger [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=AANLkTinc_9RoGnt9OPrVLBGuGfEvQrTiM1s2ui3tZDp1@mail.gmail.com \
--to=anthony@extof.me \
--cc=evorster@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).