Evolution -2.8.0 upgrade hosed Mandriva 2006
dnoyeB
to upgrade evolution to 2.8 since there have been some lingering bugs.
Well this upgrade went poorly. For whatever reason Mandriva did not
install the proper glib and mandriva would not start. Now I installed
glib2 and it does start, but it complains that it cant make an SSL
connection. I am not asking it to make an SSL connection...
I am worried that my whole install may be hosed now due to a poor
dependencies configuration of evolution.
Any tips here? is this a known problem? Can I maybe upgrade to 2007 to
avoid this? Or am I looking at a fresh install any way you cut it?
Thanks,
dnoyeB
Bit Twister
> Any tips here? Can I maybe upgrade to 2007 to
I recommend a clean install, non gui startup, su - root, set your
mirrors, then
urpmi rpm --auto
urpmi urpmi --auto
urpmi rpmdrake --auto
urpmi --auto-select --auto
Then start doing your configuration changes. No idea if errata matches
a fully patched install. Here is just one item about your home direcory.
Watch out for the long url
dnoyeB
I always do clean installs. but they require more knowledge. I was
hoping not to this time. I don't know what urpmi is or how to 'set my
mirrors' . how would i start this computer to do this su - root if its a
clean install?
Perhaps you can tell me which directories to delete for a clean install?
I do have some other directories that are not OS related I would like to
keep like my music files and CVS repository etc.
Thanks!
Bit Twister
>
> I always do clean installs. but they require more knowledge.
Ah, but you can put your commands in an admin diary and just cut/paste
them into a root terminal.
Use http://groups.google.com/advanced_group_search for
admin +diary +snippet in the first box for examples
Bit Twister in the Author box
> I was hoping not to this time. I don't know what urpmi is
The Mandriva Control Center is a gui frontend for urpm* commands.
More info for the urpm* commands can be found with
man -k urpm
> or how to
> 'set my mirrors' . how would i start this computer to do this su -
> root if its a clean install?
>
> Perhaps you can tell me which directories to delete for a clean install?
> I do have some other directories that are not OS related I would like to
> keep like my music files and CVS repository etc.
Hmmm, two for one here.
I have several 6 to 10 gig partitions. I use one of them for new
installs. Another one is is a copy of the "Production install" I use
for hot backup/recovery
That allows a multi-boot for booting the old install as fallback if
new install goes bad. Once the new install becomes the "Production
copy" the old partition can be used for testing something like your
Evolution activity. :)
I keep all my stuff on other partitions. One is where I keep my admin
diary and scripts I create to help me go faster.
One of the scripts is the one to set the mirrors.
What you can do is goto http://easyurpmi.zarb.org/ and set it for all
the 2007 mirrors you want and paste the commands into a script, say
set_mirrors. Then do a chmod +x set_mirrors.
Now, during install you mark your other partitions for mounting and
you can access the script/diary from your login. Example:
/mystuff/set_mirrors would set your mirrors from the root prompt.
You also create a mount point for the old release so you can look at
old config files when needed. Example: /2006, /md10_2, /2006_rc2
For /home I have an /accounts partition.
Common stuff in /home/bittwister is linked into /accounts/bittwister
That allows me to have different /home/bittwister for each install
but share common files/directories between installs. Examples:
.bash_logout -> /accounts/bittwister/.bash_logout
.bash_profile -> /accounts/bittwister/.bash_profile
.bashrc -> /accounts/bittwister/.bashrc
bin -> /accounts/bittwister/bin/
comp -> /accounts/bittwister/comp/
.cron -> /accounts/bittwister/.cron
.signature -> /accounts/bittwister/.signature
.Skype -> /accounts/bittwister/.Skype
.slrnrc -> /accounts/bittwister/.slrnrc
.thunderbird -> /accounts/bittwister/.thunderbird/
.emacs -> /accounts/bittwister/.xemacs
During new installs, I just cut the link commands from my admin diary
and paste after a cd ~bittwister.
dnoyeB
windows boxes. I never got that far on linux but I think I will do that
from my next install forward.
I Right now I think I have some logical partions
from df I get this
[carl@erasmus ~]$ df
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 39G 3.8G 33G 11% /
/dev/mapper/VolumeOne-home
20G 855M 19G 5% /home
/dev/mapper/VolumeOne-shared
89G 8.7G 75G 11% /shared
I assume I can divide / into 3 partitions? I will only do this during
reinstall because I know I am goign to hose something when I start messing
with the partitions. I am using 3ware IDE raid as well. but that should
be transparent here.
shared is most of my data, but I noticed that I have a few
directories mounted on /. I think I will move them into /shared and link
back to /.
anyway, how big should I make my OS install partitions? I know that
choice is up to me, but I have no idea really.
Ill do a bit to learn urpmi as well. I do use rpm from the command line,
and I used to use redhats update tool when I was on redhat, so I may as
well learn mandriva's tool and whats going on behind that GUI...
how do you achieve backup with that linking?
Bit Twister
> Wow, those are some really great ideas. I been doing that stuff on my
> windows boxes. I never got that far on linux but I think I will do that
> from my next install forward.
>
> I Right now I think I have some logical partions
> from df I get this
>
> [carl@erasmus ~]$ df
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 39G 3.8G 33G 11% /
> /dev/mapper/VolumeOne-home
> 20G 855M 19G 5% /home
> /dev/mapper/VolumeOne-shared
> 89G 8.7G 75G 11% /shared
Yep, here is mine
$ df
Filesystem Size Used Avail Use% Mounted on
/dev/sda11 6.5G 4.7G 1.5G 77% /
/dev/sda7 1.1G 40M 974M 4% /site
/dev/sda8 6.6G 1.6G 4.7G 26% /accounts
/dev/sda10 22G 13G 8.2G 60% /local
/dev/sda1 30G 11G 20G 35% /mnt/win_c
/dev/sda5 1.9G 416K 1.9G 1% /mnt/win_d
/dev/sda2 8.5G 8.0G 464M 95% /mnt/win_e
> I assume I can divide / into 3 partitions?
You can divide it as much as you like, but my method is everything
about an install is in / including /home.
Example 2006 /home files are NOT UTF-8 and 2007 are UTF-8 which can
give desktop apps problems. Newer releases of the desktop managers may
dinkup older config files in /home. So the old release desktop may
have problems. At one time I had to recreate all my shortcuts because
kde had a new format.
Remember I have common files in other partitions. For kde, I have
/home/bittwister/.kde/Autostart/startup -> /home/bittwister/bin/startup
and
/home/bittwister/bin -> /accounts/bittwister/bin/
After install I copy /accounts/bittwister/Desktop/x* to
/home/bittwister/Desktop for all my KDE desktop shortcuts because I name
all my shortcuts xSomething to make that easy.
> I will only do this during reinstall because I know I am goign to
> hose something when I start messing with the partitions.
Yes, I recommend the new install goes into new partitions, create your
/shared and whatnot somewhere else. Then copy from VolumeOne to new
partitions. Then sda1 can become the new install hot backup when you are up
and running on the new install.
> shared is most of my data, but I noticed that I have a few
> directories mounted on /. I think I will move them into /shared and link
> back to /.
Hmmm, I guess it would depend on what they are. Example instead of a
common /opt I have the /local mount point and put my /opt stuff there.
$ ls /local/opt
firefox-2.0.0.2 info2html-1.4 named thunderbird-1.5.0.9
I used to have a common /opt but had a supprise when I loaded other
distributions which use /opt. Suse did me up just fine. :(
$ ls /suse/opt
gnome kde3 mozilla MozillaFirefox novell
Now different distributions have their own /opt in / and all I need to
do is create /local mountpoint during install.
> anyway, how big should I make my OS install partitions?
How big does a piece of string need to be. :)
It is going to depend on what you are going to install. I install all
package groups except LSB and I pick kde and gnome in the Desktop group.
So looking at my 2007 instal, we see
/dev/sda11 6.5G 4.7G 1.5G 77% /
which leaves me only 1.5 gig for downloading rpms for update and
kernel updates.
$ df /2006oe
Filesystem Size Used Avail Use% Mounted on
/dev/hdb6 6.3G 5.3G 709M 89% /2006oe
It used more because of all the kernel updates.
For the general question, I would not recommend smaller than 6 gig for /
Looking back at 2006 install, I guess I need to start recommending 8 to 10 gig.
For suse I have
$ df /suse
Filesystem Size Used Avail Use% Mounted on
/dev/hdb14 8.8G 5.5G 2.9G 66% /suse
and it almost went full with just updates because I did not know to
uncheck Save Source box. Now I have breathing room again.
> I know that choice is up to me, but I have no idea really.
When I am in unknown territory, I use the unformated/free space I keep
on the end of my drive. I'll do an install there and see the space
used up. I'll add about 2 gig for update space and create a partition
for it and copy there. Then delete the original install partition to
get the free/unformated space back.
> how do you achieve backup with that linking?
That becomes simple for me. I just backup /accounts and /site
I do not worry about / because I just reinstall from cds.
/home/bittister links are recreated from a cut/paste from my admin diary.
Downside is I have to remember to update the admin diary when I create
new subdirectories.
I have had supprises on new installs. I would play a game and find out
I was back at level 1. The good news is I just mount the old install,
copy the game's directory/.rc file to /accounts/bittwister and put in
the links in /home/bittwister and update the diary.
That reminds me, after install, I go and set the old install partition
mount points to noauto and mountable by users. That way, those files do
not show up in the _locate_ database.
Oh yeah, you might want to consider what happens when the UID/GID change.
(Hint man chown)
I have seen them change between releases. :-(
Want to see my solution, goto
http://groups.google.com/advanced_group_search
/etc/group_1500 in the first box
bit twister in the autor box
Comes in handy if you want to have a multi-boot setup for playing with
other distributions.
David W. Hodgins
> I Right now I think I have some logical partions
> from df I get this
> [carl@erasmus ~]$ df
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 39G 3.8G 33G 11% /
> /dev/mapper/VolumeOne-home
> 20G 855M 19G 5% /home
> /dev/mapper/VolumeOne-shared
> 89G 8.7G 75G 11% /shared
>
> I assume I can divide / into 3 partitions? I will only do this during
> reinstall because I know I am goign to hose something when I start messing
> with the partitions. I am using 3ware IDE raid as well. but that should
> be transparent here.
Note that logical volumes are not the same as logical partitions.
The above shows that you have two physical partitions. /dev/sda1 which you
have mounted as /.
/dev/sda2 is either the primary partition containing the LVM physical volume, or
it's an extended partition, in which case /dev/sda5 would be a logical partition
containing the one LVM physical volume. The one LVM physicall volume contains
the two logical volumes, that you have mounted as /home and /shared.
If, during the reinstall, you wipe partition /dev/sda2 (or sda5) containing the
LVM physical volume, you will lose both logical volumes, VolumeOne-home and
VolumeOne-shared. Be very carefull to select the logical volumes, not the
logical parition, when wiping.
I'm also using LVM. I'm appending my current df and mount output, with
everything mounted 98, XP Pro, Linux, Linux Backup, and some partitions
I only use for testing stuff. I'm also appending sfdisk -l, as that
help make the physical partition structure much clearer.
Note that I have a minimum amount on /, to minimize the risk of
being unable to boot, due to the / filesystem being full (Once
was enough<G>).
The other thing that isn't obvious from the below, is that when
I login as root, /home/dave is a directory in the logical volume
mounted as /home. When I login as dave, an encrypted reiserfs
filesystem, stored in a logical volume, gets mounted via loopback
as /home/dave. The only place you see the existence of the encrypted
logical volumes, is in an lvscan (also appended), or similar.
Also, I've deleted /mnt, and use /var/mnt, which is in it's own
logical volume. That way, copying an iso to a filesystem that
hasn't been mounted, doesn't fill up the / filesystem (again,
once was enough<G>).
There's lots of ways to handle partitioning your disk space. Just
be carefull not to mix up what's where, especially, when wiping<G>.
The order of fstab entries is important too, when you have mountpoints
in filesystems other then /.
Regards, Dave Hodgins
[dave@hodgins ~]$ df
Filesystem Size Used Avail Use% Mounted on
/dev/hda15 377M 311M 66M 83% /
/dev/hda14 61M 15M 44M 25% /boot
/dev/mapper/LV2-home 64M 33M 32M 51% /home
/dev/mapper/LV2-opt 512M 33M 480M 7% /opt
/dev/mapper/LV2-tmp 4.0G 38M 4.0G 1% /tmp
/dev/mapper/LV2-usr 9.0G 7.2G 1.9G 80% /usr
/dev/mapper/LV2-var 6.0G 3.7G 2.4G 62% /var
/dev/hda16 126M 46M 80M 37% /var/log
/dev/mapper/LV2-mnt 3.9M 41K 3.7M 2% /var/mnt
/dev/hda10 259M 194M 66M 75% /var/mnt/backup
/dev/hda8 63M 37M 27M 58% /var/mnt/backup/boot
/dev/mapper/LV5-home 64M 33M 32M 51% /var/mnt/backup/home
/dev/mapper/LV5-opt 384M 33M 352M 9% /var/mnt/backup/opt
/dev/mapper/LV5-usr 5.0G 4.1G 985M 81% /var/mnt/backup/usr
/dev/mapper/LV5-var 3.0G 240M 2.8G 8% /var/mnt/backup/var
/dev/hda11 63M 38M 26M 60% /var/mnt/backup/var/log
/dev/hdb7 16G 272K 16G 1% /var/mnt/xfstest
/dev/loop7 13G 11G 2.1G 85% /home/dave
/dev/hda1 2.0G 1.7G 358M 83% /var/mnt/hda1
/dev/hda13 18G 12G 6.2G 67% /var/mnt/hda13
/dev/hda5 1.1G 823M 204M 81% /var/mnt/hda5
/dev/hda6 2.0G 1.9G 123M 95% /var/mnt/hda6
/dev/hda7 517M 384M 134M 75% /var/mnt/hda7
/dev/hdb6 32G 2.1G 30G 7% /var/mnt/hdb6
/dev/hdb5 9.8G 33M 9.8G 1% /var/mnt/hdb5
[dave@hodgins ~]$ mount
/dev/hda15 on / type reiserfs (rw,notail)
none on /proc type proc (rw)
/dev/hda14 on /boot type ext2 (rw)
/dev/mapper/LV2-home on /home type reiserfs (rw,notail)
/dev/mapper/LV2-opt on /opt type reiserfs (rw,notail)
/dev/mapper/LV2-tmp on /tmp type reiserfs (rw,notail)
/dev/mapper/LV2-usr on /usr type reiserfs (rw,notail)
/dev/mapper/LV2-var on /var type reiserfs (rw,notail)
/dev/hda16 on /var/log type reiserfs (rw,notail)
/dev/mapper/LV2-mnt on /var/mnt type ext2 (rw)
/dev/hda10 on /var/mnt/backup type reiserfs (rw,notail)
/dev/hda8 on /var/mnt/backup/boot type reiserfs (rw,notail)
/dev/mapper/LV5-home on /var/mnt/backup/home type reiserfs (rw,notail)
/dev/mapper/LV5-opt on /var/mnt/backup/opt type reiserfs (rw,notail)
/dev/mapper/LV5-usr on /var/mnt/backup/usr type reiserfs (rw,notail)
/dev/mapper/LV5-var on /var/mnt/backup/var type reiserfs (rw,notail)
/dev/hda11 on /var/mnt/backup/var/log type reiserfs (rw,notail)
/dev/hdb7 on /var/mnt/xfstest type xfs (rw)
/dev/loop7 on /home/dave type reiserfs (rw,notail)
/dev/hda1 on /var/mnt/hda1 type vfat (rw,noexec,nosuid,nodev,users,umask=0,iocharset=iso8859-15,codepage=850)
/dev/hda13 on /var/mnt/hda13 type fuse (rw,nosuid,nodev,default_permissions,allow_other)
/dev/hda5 on /var/mnt/hda5 type vfat (rw,noexec,nosuid,nodev,users,umask=0,iocharset=iso8859-15,codepage=850)
/dev/hda6 on /var/mnt/hda6 type vfat (rw,noexec,nosuid,nodev,users,umask=0,iocharset=iso8859-15,codepage=850)
/dev/hda7 on /var/mnt/hda7 type vfat (rw,noexec,nosuid,nodev,users,umask=0,iocharset=iso8859-15,codepage=850)
/dev/hdb6 on /var/mnt/hdb6 type vfat (rw,noexec,nosuid,nodev,users,umask=0,iocharset=iso8859-14,codepage=850)
/dev/hdb5 on /var/mnt/hdb5 type reiserfs (rw)
[dave@hodgins ~]$ sudo sfdisk -l
Disk /dev/hda: 9729 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 260 261- 2096451 b W95 FAT32
/dev/hda2 261 9728 9468 76051710 5 Extended
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
/dev/hda5 261+ 391 131- 1052226 b W95 FAT32
/dev/hda6 392+ 652 261- 2096451 b W95 FAT32
/dev/hda7 653+ 718 66- 530113+ b W95 FAT32
/dev/hda8 719+ 726 8- 64228+ 83 Linux
/dev/hda9 727+ 987 261- 2096451 82 Linux swap / Solaris
/dev/hda10 988+ 1020 33- 265041 83 Linux
/dev/hda11 1021+ 1028 8- 64228+ 83 Linux
/dev/hda12 1029+ 2284 1256- 10088788+ 8e Linux LVM
/dev/hda13 2285+ 5432 3148- 25286278+ 7 HPFS/NTFS
/dev/hda14 5433+ 5440 8- 64228+ 83 Linux
/dev/hda15 5441+ 5488 48- 385528+ 83 Linux
/dev/hda16 5489+ 5504 16- 128488+ 83 Linux
/dev/hda17 5505+ 9728 4224- 33929248+ 8e Linux LVM
Disk /dev/hdb: 9729 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hdb1 * 0+ 7538 7539- 60556986 5 Extended
/dev/hdb2 0 - 0 0 0 Empty
/dev/hdb3 0 - 0 0 0 Empty
/dev/hdb4 0 - 0 0 0 Empty
/dev/hdb5 0+ 1273 1274- 10233342 83 Linux
/dev/hdb6 1274+ 5450 4177- 33551721 b W95 FAT32
/dev/hdb7 5451+ 7538 2088- 16771828+ 83 Linux
[dave@hodgins ~]$ sudo lvscan
ACTIVE '/dev/LV2/opt' [512.00 MB] inherit
ACTIVE '/dev/LV2/usr' [9.00 GB] inherit
ACTIVE '/dev/LV2/var' [6.00 GB] inherit
ACTIVE '/dev/LV2/tmp' [4.00 GB] inherit
ACTIVE '/dev/LV2/enc' [12.79 GB] inherit
ACTIVE '/dev/LV2/home' [64.00 MB] inherit
ACTIVE '/dev/LV2/mnt' [4.00 MB] inherit
ACTIVE '/dev/LV5/opt' [384.00 MB] inherit
ACTIVE '/dev/LV5/usr' [5.00 GB] inherit
ACTIVE '/dev/LV5/var' [3.00 GB] inherit
ACTIVE '/dev/LV5/home' [64.00 MB] inherit
ACTIVE '/dev/LV5/enc' [1.18 GB] inherit
--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
dnoyeB
> On Wed, 28 Feb 2007 09:49:29 -0500, dnoyeB <as...@fake.net> wrote:
>
>> I Right now I think I have some logical partions from df I get this
>> [carl@erasmus ~]$ df
>> Filesystem Size Used Avail Use% Mounted on /dev/sda1
>> 39G 3.8G 33G 11% / /dev/mapper/VolumeOne-home
>> 20G 855M 19G 5% /home
>> /dev/mapper/VolumeOne-shared
>> 89G 8.7G 75G 11% /shared
>>
>> I assume I can divide / into 3 partitions? I will only do this during
>> reinstall because I know I am goign to hose something when I start
>> messing with the partitions. I am using 3ware IDE raid as well. but
>> that should be transparent here.
>
> Note that logical volumes are not the same as logical partitions.
>
> The above shows that you have two physical partitions. /dev/sda1 which you
> have mounted as /.
>
> /dev/sda2 is either the primary partition containing the LVM physical
> volume, or it's an extended partition, in which case /dev/sda5 would be a
> logical partition containing the one LVM physical volume. The one LVM
> physicall volume contains the two logical volumes, that you have mounted
> as /home and /shared.
Ahh, I never fully understood that. You are correct
[root@erasmus ~]# sfdisk -l
Disk /dev/sda: 152626 cylinders, 64 heads, 32 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Warning: The partition table looks like it was made
for C/H/S=*/255/63 (instead of 152626/64/32).
For this listing I'll assume that geometry.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 5098 5099- 40957686 83 Linux
/dev/sda2 5099 19457- 14359- 115332162+ 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 5099+ 5226 128- 1028128+ 82 Linux swap / Solaris
/dev/sda6 5227+ 19457- 14231- 114303971 8e Linux LVM
[root@erasmus ~]#
its excended partition because its broken into 2 logical partitions. one
for the swap partition and one for the logical volume partition..
>
> If, during the reinstall, you wipe partition /dev/sda2 (or sda5)
> containing the LVM physical volume, you will lose both logical volumes,
> VolumeOne-home and VolumeOne-shared. Be very carefull to select the
> logical volumes, not the logical parition, when wiping.
>
Thanks, no telling what I would have concocted without that knowledge.
What I see here is 2 drives. hda and hdb. hda has a primary partition at
hda1, and a logical partitions starting at hda5. Since I see only 1
primary partition, I assume all these logical partitions are within hda1
primary partition?
Further I assume that the logical partition hda5 is broken up into logical
volumes based on the mapper's volume name. well i dont know because you
have a lv2 also but I see no hda2!? i know there is no relation between
the naming.
Is this correct?
If so thanks for the pointer because I was missing that there was logical
partitions and logical volumes which are different.
I think I was reading the df before as if it was the partition table...
hda1 is primary and has FAT32 on it for masochistic purposes I assume :P
hda2 is extended because it has to be in order to be broken into logical
partitions. Which are many and start with hda5. including 2 logical
volumes.
>
> Disk /dev/hdb: 9729 cylinders, 255 heads, 63 sectors/track Warning:
> extended partition does not start at a cylinder boundary. DOS and Linux
> will interpret the contents differently. Units = cylinders of 8225280
> bytes, blocks of 1024 bytes, counting from 0
>
> Device Boot Start End #cyls #blocks Id System
> /dev/hdb1 * 0+ 7538 7539- 60556986 5 Extended /dev/hdb2
> 0 - 0 0 0 Empty /dev/hdb3 0
> - 0 0 0 Empty /dev/hdb4 0 - 0
> 0 0 Empty /dev/hdb5 0+ 1273 1274- 10233342 83
> Linux /dev/hdb6 1274+ 5450 4177- 33551721 b W95 FAT32
> /dev/hdb7 5451+ 7538 2088- 16771828+ 83 Linux
>
> [dave@hodgins ~]$ sudo lvscan
> ACTIVE '/dev/LV2/opt' [512.00 MB] inherit ACTIVE
> '/dev/LV2/usr' [9.00 GB] inherit ACTIVE '/dev/LV2/var'
> [6.00 GB] inherit ACTIVE '/dev/LV2/tmp' [4.00 GB] inherit
> ACTIVE
> '/dev/LV2/enc' [12.79 GB] inherit ACTIVE
> '/dev/LV2/home' [64.00 MB] inherit ACTIVE '/dev/LV2/mnt'
> [4.00 MB] inherit ACTIVE '/dev/LV5/opt' [384.00 MB]
> inherit ACTIVE '/dev/LV5/usr' [5.00 GB] inherit ACTIVE
> '/dev/LV5/var' [3.00 GB] inherit ACTIVE '/dev/LV5/home'
> [64.00 MB] inherit ACTIVE '/dev/LV5/enc' [1.18 GB] inherit
So my last question is, since my objective will be to have seperate
bootable linux installs, I need to have seperate primary partitions
because only primary partitions are bootable??
Thanks for the help.
Bit Twister
> So my last question is, since my objective will be to have seperate
> bootable linux installs, I need to have seperate primary partitions
> because only primary partitions are bootable??
No, they do not have to be Primary partitions.
If lilo/grub can get to it, it is bootable.
I have all my linux partitions in an Extented partition.
Bit Twister
Dang, that should be
> I have all my linux partitions in an Extented partition.
I have all my linux partitions in an Extended partition.
David W. Hodgins
> Ahh, I never fully understood that. You are correct
> its excended partition because its broken into 2 logical partitions. one
> for the swap partition and one for the logical volume partition..
Time to learn about partition tables<G>. This is a topic that is
very important to be clear on, before deleting anything.
You can find details in a google search on "master boot record", but
I'll give a quick summary here.
Each hard drive is divided into sectors of 512 bytes each. The first
sector contains the master boot record (MBR). The MBR contains
a table with room to describe four partitions. Each of those table
entries contain the partiton type, the starting sector number, and the
number of sectors that the partition occupies. There's also the starting
cylinder, track, and head, but those numbers are no longer used with
logical block addressing, so just ignore them.
The partition types you will usually see are Empty, W95 FAT32, NTFS,
Linux, Linux swap, linux LVM and Extended. By definition, any partition
described in the master boot record is a primary partition. Excluding
Extended, each of the partitions described in the MBR is independant,
and except for not being allowed to overlap, the partitions can be
anywhere on the hard drive. The physical order does not have to be
the same as the order in the partition table.
Linux calls the partitions listed in the partiton table of the master
boot record hda1 through hda4 for ide drives, or sda1 through sda4 for scsi hard drives.
The extended partition isn't really a partition. It's really only used
to contain the sector number where another partition table can be found.
The size of the extended partition (number of sectors) may or may not
be accurate. It doesn't matter, as it's not used.
That second partition table also has room for four entries, but in
reality, only two (at most) are used. The first will contain the
type, starting sector, size etc. for one partition, that can be any
of the types used for a primary partition, except extended. Any
parition described in this table entry will, by definition, be called
a logical partition, also called logical drive. The second entry
will either be of a type empty (if this is the last logical drive),
or it will be marked as an extended partition, and contain the sector
number of another partition table. It's by chaining these extended
partiton tables together, that all of the partitions are found.
Except for the extended partition in the MBR, none of the other
extended partitons are assigned a name. Only the logical drives
(first entry in each of the extended partitions tables), are
assigned names. Since there are four entries in the MBR, the
first logical drive will always be HDA5 (or SDA5).
Let's go through the part of the output of "sfdisk -l -uS"
(the -uS tells sfdisk to show the numbers in sectors (as they
are stored on the hard drives), instead of in blocks.
Device Boot Start End #sectors Id System
/dev/hda1 * 63 4192964 4192902 b W95 FAT32
/dev/hda2 4192965 156296384 152103420 5 Extended
/dev/hda3 0 - 0 0 Empty
/dev/hda4 0 - 0 0 Empty
The above four partition table entries are stored in the MBR,
which is in sector 0 (the first sector) of the hard drive.
/dev/hda5 4193028 6297479 2104452 b W95 FAT32
The above partition is the first entry in the partition
table stored in sector number 4192965, which was found by
reading the starting sector of the Extended partition described
as hda2.
Although not shown by sfdisk, the partition table in sector 4192965
has a second entry, with the type extended, and the starting sector
of 6297479.
/dev/hda6 6297543 10490444 4192902 b W95 FAT32
In sector 6297479 there is another partition table. The first
entry describes hda6. The second entry points to the next
partition table.
In linux, the next partition table may physically be before
the current table. Dos doesn't like that, and its version of fdisk
will mess things up, if you let it write to the hard drive. I
strongly encourage anyone who has a copy of fdisk from win98 or
earlier, to delete it.
A linux LVM partition contains one LVM physical volume. Each LVM
physical volume is assigned to a volume group, The volume group
can have more than one physical volumes, which can be on separate
hard drives
If I create a LVM partition on my second hard drive, and assign it
to the same volume group that the LVM partition on my first drive
is assigned to, I can then extend any of the logical volumes in
the volume group, so that they use the space on the second hard drive.
For example, I have the filesystem for /usr in a logical volume
called usr, in the volume group called LV2. If I create a LVM
partition on hdb2, and assign it to the volume group LV2, I can
then extend the logical volume called usr, to make it bigger,
without having to move any of the existing data.
I think that's enough for now. Hope this helps.
Regards, Dave Hodgins