1 |
On 2020-11-24, antlists <antlists@××××××××××××.uk> wrote: |
2 |
> |
3 |
>> Cool, I'll have to read up on using volumes for that. How far back in |
4 |
>> time can you go before you get to distros that would have problems? |
5 |
> |
6 |
> How old is LVM? It's been around for ages, I think. |
7 |
|
8 |
We regularly run into customers running distros that came out 10 years |
9 |
ago. Not long ago, I was working with a customer who was running RHEL 6 |
10 |
and kernel 2.6.32 on production machines. Yes, RHEL 6 is still |
11 |
supported (though not for long). According to the LVM Wikipedia page, |
12 |
2.6.32 is old enough that journalling filesystems didn't work |
13 |
correctly on top of LVM. That said, it's quite possible RH backported |
14 |
LVM improvements to 2.6.32 so that's not an issue. |
15 |
|
16 |
Right now, I have a small "grub" partition which has menu that allows |
17 |
chainloading any of dozen or so main partitions, each of which has a |
18 |
linux distro installed (with a bootloader installed in that |
19 |
partition). I've been reading up on LVM vs. grub, and all of the |
20 |
examples I find of booting multiple distros on LVM don't seem to be |
21 |
chainloading. Rather they point the "master" grub at the root |
22 |
"partition" and that partition's .cfg file. However, that assumes |
23 |
that the distro uses grub, and that the .cfg file is compatible with |
24 |
the "master" grub executables. I'd rather not rely on that assumption |
25 |
and just do chainloading like I always have. |
26 |
|
27 |
In grub, does chainloading an LVM virtual partition work the same as |
28 |
chainloading a "real" partition? |
29 |
|
30 |
-- |
31 |
Grant |