Mailinglist Archive: opensuse (2035 mails)
| < Previous | Next > |
Re: [Fwd: Re: [opensuse] Questions for Partitioning guru's]
- From: Bob S <911@xxxxxxxxxxx>
- Date: Mon, 10 Sep 2007 02:23:35 -0400
- Message-id: <200709100223.35607.911@xxxxxxxxxxx>
On Sunday 09 September 2007 14:30, Peter Sjoberg wrote:
> On Sat, 2007-09-08 at 00:49 -0400, Bob S wrote:
> > Hello SuSE people,
.<snip a bunch>................
> I love lvm since it's so flexible, if you for example run low in space
> in datalv you can just expand it without playing around with disk
> partitions (=much safer) and you can even add a new disk and expand it
> without problem. If I need to replace a disk with a bigger one/remove
> one I can use a single "pvmove /dev/hdb" to move data around and get it
> done without tons of repartition and fs moves.
OK, but I have a question;
When I installed 10.0 I used LVM for everything except /swap and /. When I
went to install 10.2 I was going to use LVM again, but when I looked at the
partitioner it seemed to want put my 10.2 partitions with the old 10.0 stuff
under /system2, That worried me. How could I have a homelv for 10.0 and a
homelv for 10.2? (relying on memory here which isn't as good as it used to
be) How would the 10.0 os and the 10.2 os sort it out. Soooo, I just resorted
to a regular partitioning scheme for 10.2
>
> One thing is that since /boot and /boot/grub/menu.lst is common for all
> installs you need to manually manage that area. I found that each os
> version have there own version numbering like
> vmlinuz-2.6.18.8-0.5-default/initrd-2.6.18.8-0.5-default so there is no
> conflict
Ummm,,, that would be the kernel version, so it wouldn't be right if the
kernel were upgraded, right? When I upgraded the kernel in 10.2 I lost the
ability to boot 10.0. I attributed it to that but I didn't look into it
because 10.2 was working well. Guess I would have to reinstall 10.0 or find
the proper kernel and install it.
> but they normally replace /boot/grub/menu.lst so I make sure I
> have a copy of menu.lst somewhere and then I manually merge the old and
> new menu.lst after each install.
So you must have both kernel versions on your system. I don't like the
automated update of the kernel because it replaces it rather than adding the
new kernel and you end up with only the one kernel. Way back when.... I would
download a kernel and manually install it. That way I would have more than
one kernel to fall back on. I guess I will start keeping a copy of Menu.1st
also.
>
> > Anxiously awaiting the final 10.3 so I can try Compiz-Fusion, Beryl
> > whatever and be able to fall back to 10.2 when I screw it up.
>
> I'm also waiting for 10.3 final but you can do as me and start playing
> with Beta 3 to get a feel for it and report problems (or you may have to
> report same problem on the final because everyone assumed someone else
> already tested and reported it)
Welllll.....I will, as soon as I free up the space on my drive which I screwed
up by improperly partitioning it. Thanks for your input.
Bob S.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
> On Sat, 2007-09-08 at 00:49 -0400, Bob S wrote:
> > Hello SuSE people,
.<snip a bunch>................
> I love lvm since it's so flexible, if you for example run low in space
> in datalv you can just expand it without playing around with disk
> partitions (=much safer) and you can even add a new disk and expand it
> without problem. If I need to replace a disk with a bigger one/remove
> one I can use a single "pvmove /dev/hdb" to move data around and get it
> done without tons of repartition and fs moves.
OK, but I have a question;
When I installed 10.0 I used LVM for everything except /swap and /. When I
went to install 10.2 I was going to use LVM again, but when I looked at the
partitioner it seemed to want put my 10.2 partitions with the old 10.0 stuff
under /system2, That worried me. How could I have a homelv for 10.0 and a
homelv for 10.2? (relying on memory here which isn't as good as it used to
be) How would the 10.0 os and the 10.2 os sort it out. Soooo, I just resorted
to a regular partitioning scheme for 10.2
>
> One thing is that since /boot and /boot/grub/menu.lst is common for all
> installs you need to manually manage that area. I found that each os
> version have there own version numbering like
> vmlinuz-2.6.18.8-0.5-default/initrd-2.6.18.8-0.5-default so there is no
> conflict
Ummm,,, that would be the kernel version, so it wouldn't be right if the
kernel were upgraded, right? When I upgraded the kernel in 10.2 I lost the
ability to boot 10.0. I attributed it to that but I didn't look into it
because 10.2 was working well. Guess I would have to reinstall 10.0 or find
the proper kernel and install it.
> but they normally replace /boot/grub/menu.lst so I make sure I
> have a copy of menu.lst somewhere and then I manually merge the old and
> new menu.lst after each install.
So you must have both kernel versions on your system. I don't like the
automated update of the kernel because it replaces it rather than adding the
new kernel and you end up with only the one kernel. Way back when.... I would
download a kernel and manually install it. That way I would have more than
one kernel to fall back on. I guess I will start keeping a copy of Menu.1st
also.
>
> > Anxiously awaiting the final 10.3 so I can try Compiz-Fusion, Beryl
> > whatever and be able to fall back to 10.2 when I screw it up.
>
> I'm also waiting for 10.3 final but you can do as me and start playing
> with Beta 3 to get a feel for it and report problems (or you may have to
> report same problem on the final because everyone assumed someone else
> already tested and reported it)
Welllll.....I will, as soon as I free up the space on my drive which I screwed
up by improperly partitioning it. Thanks for your input.
Bob S.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |