public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where did lvm installation guide go?
Date: Thu, 29 Aug 2013 19:30:54 -0500	[thread overview]
Message-ID: <CADPrc83_WQ7nv2OsOju7QH-HyftSJTGk_2K5menHM39KC7CM5A@mail.gmail.com> (raw)
In-Reply-To: <87sixschz7.fsf@nyu.edu>

On Thu, Aug 29, 2013 at 4:19 PM,  <gottlieb@nyu.edu> wrote:
> On Thu, Aug 29 2013, Canek Peláez Valdés wrote:
>
>> As James said, the docs are being reorganized. However, I did a
>> systemd+LVM installation (just because I was getting tired of not
>> knowing what the fuss was all about), and (in my experience) there are
>> almost no changes from the regular installation in the handbook.
>>
>> I put everything in LVM (/, /boot, everything).
>
> I am not so ambitious.  /+/boot+/usr one ext4 partition not on lvm
>
>> From my notes, the only changes are:
>>
>>>From the livecd:
>> 1. Use partitions, not whole disks (GRUB2 got confused when I tried to
>> use whole disks).
>> 2. Set the partition type as LVM (8e in fdisk).
>> 3. Create the Physical Volume, the Volume Group, and the Logical
>> Volumes as desired.
>> 4. Continue the normal installation, just using /dev/vg0/lvolX (or
>> whatever names you choose).
>
> There is a little more (activating or something the LVs) especially if
> you shutdown in the middle of the installation and resume it later.
>
>> After the chroot and emerging the kernel package:
>> 1. Se the LVM options in the kernel. Compile, install it.
>> 2. Emerge systemd.
>> 3. Emerge dracut (USE="device-mapper", DRACUT_MODULES="systemd lvm", at least).
>> 4. Set add_dracutmodules="systemd" in /etc/dracut.conf.
>> 5. Weirdly, set lvmconf="no" in /etc/dracut.conf. I didn't even
>> touched /etc/lvm/lvm.conf, so I think leaving it out makes dracut to
>> autoconfigure it. If I put lvmconf="yes", the boot hangs. Didn't
>> investigated why.
>> 6. Emerge GRUB2 (USE="device-mapper mount"); I don't know if GRUB
>> works with LVM, but GRUB2 does, so I used that.
>> 7. Set GRUB_PRELOAD_MODULES="lvm",
>> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd", in
>> /etc/default/grub.
>> 8. Generate initramfs, generate /boot/grub2/grub.cfg, install GRUB2
>> with grub2-install.
>> 9. Reboot. Everything works.
>>
>> GRUB2 handles LVM just fine, I believe, but my LVM setup was dead
>> simple (the VG was just the only partition of all my disks).
>> dracut+systemd takes care of everything else; I didn't even had to do
>> something special in fstab, since I used labels.
>>
>> To extend/reduce your Logical Volumes you will need a livecd, or a
>> more complex initramfs, though.
>>
>> Regards.
>
> I have experience with LVM, but not systemd or dracut or initramfs
>
> * both grub and grub2 support lvm

Does GRUB legacy handles /boot in LVM? I haven't tried that yet.

> * Never did 2,3,4,5,7, or the initramfs part of 8
>
> My goal is to have this system (an older laptop) setup like my current
> laptop (grub2, openrc, root+/usr, etc).  Then I will convert OLD to
> systemd.  Once I have done this and moved my work from CURRENT to OLD, I
> will convert CURRENT to systemd and move back.

That sounds complex.

> thanks to you and james for your helpful comments.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


  reply	other threads:[~2013-08-30  0:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 15:47 [gentoo-user] where did lvm installation guide go? gottlieb
2013-08-29 16:56 ` [gentoo-user] " James
2013-08-29 21:02   ` gottlieb
2013-08-29 17:29 ` [gentoo-user] " Canek Peláez Valdés
2013-08-29 21:19   ` gottlieb
2013-08-30  0:30     ` Canek Peláez Valdés [this message]
2013-08-30  1:45       ` gottlieb
2013-08-30  2:29         ` Canek Peláez Valdés
2013-08-30  5:21         ` J. Roeleveld
2013-08-30  5:36           ` Canek Peláez Valdés
2013-08-30  6:10             ` Alan McKinnon
2013-08-30  7:16               ` Dale
2013-08-30 14:05                 ` Tanstaafl
2013-08-30 14:28                   ` Canek Peláez Valdés
2013-08-30 14:37                     ` Tanstaafl
2013-08-30 14:38                       ` Alan McKinnon
2013-08-30 14:59                         ` Tanstaafl
2013-08-30 14:56                       ` Canek Peláez Valdés
2013-08-31 11:31                       ` [gentoo-user] " Nicolas Sebrecht
2013-08-30 14:13               ` [gentoo-user] " Canek Peláez Valdés
2013-08-30  5:47         ` Alan McKinnon
2013-08-30  7:17           ` Dale
2013-08-30  5:21   ` J. Roeleveld
2013-08-30  6:13     ` Alan McKinnon
2013-08-30  5:21   ` J. Roeleveld
2013-08-30  5:20 ` J. Roeleveld
2013-08-30 15:18   ` gottlieb
2013-08-30 16:48     ` joost
2013-08-30 19:18     ` Alan McKinnon
2013-08-31 14:18       ` gottlieb

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=CADPrc83_WQ7nv2OsOju7QH-HyftSJTGk_2K5menHM39KC7CM5A@mail.gmail.com \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.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