linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Gene Czarcinski <gene@czarc.net>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: /boot as a btrfs subvolume
Date: Mon, 07 Jan 2013 18:48:21 +0100	[thread overview]
Message-ID: <50EB0A65.4090009@petaramesh.org> (raw)
In-Reply-To: <50E9D909.1020207@czarc.net>

Le 06/01/2013 21:05, Gene Czarcinski a écrit :
> I assume you have a "grub partition" (or its equivalent) with a
> grub.cfg file having menuentry definitions [pointing to the different
> grub.cfg file for each system ... that seems to work well (at least
> for me).  Currently, os-prober does not support btrfs. 

I don't have any specific "grub" partition, every Linux install has its
own grub install in its own /boot BTRFS subvolume.

But I of course have only one grub actually installed in the disk MBR,
the one that corresponds to the distro I use most (and for which I redid
« grub-install /dev/sda » last).

As this grub doesn't auto-detect the other distros, I simply chain from
there the other distro's grub.cfg, by having crafted once for all a :


"/etc/grub.d/40_custom" that contains, i.e. :


#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply
type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.

menuentry "DebMint Loader (Chained)" {
    configfile (hd0,2)/LMDE/@boot/grub/grub.cfg
}

menuentry "Mint 13 Loader (Chained)" {
    configfile (hd0,2)/MINT/@boot/grub/grub.cfg
}

menuentry "Bodhi Loader (Chained)" {
    configfile (hd0,2)/BODHI/@boot/grub/grub.cfg
}


That's all folks ;-))

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.


  parent reply	other threads:[~2013-01-07 17:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 21:17 /boot as a btrfs subvolume Gene Czarcinski
2013-01-05 21:27 ` Chris Murphy
2013-01-06 14:44   ` Gene Czarcinski
2013-01-06 19:11     ` Chris Murphy
2013-01-06 19:17       ` Swâmi Petaramesh
2013-01-06 20:05         ` Gene Czarcinski
2013-01-07  2:00           ` Chris Murphy
2013-01-07 15:42             ` Gene Czarcinski
2013-01-07 18:42               ` Chris Murphy
2013-01-07 21:41                 ` Gene Czarcinski
2013-01-07 22:04                   ` Chris Murphy
2013-01-07 17:48           ` Swâmi Petaramesh [this message]
2013-01-07 19:28             ` Chris Murphy
2013-01-05 21:32 ` Chris Murphy
2013-01-06 14:37   ` Gene Czarcinski

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=50EB0A65.4090009@petaramesh.org \
    --to=swami@petaramesh.org \
    --cc=gene@czarc.net \
    --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).