so I think I'm going to move from Debian to Slackware...

rkrishna · 06-08-2010, 08:57 PM

@onbuck,
thanks for the comment and detailed Note, especially the max no of logical partitions on disk
i also wanted to give the same information. i really agree that it was not properly described.

what i usually do is, first primary (say /dev/sda1) for windows and remaining space space will be allotted for the extended partition( /dev/sda2). then, create as many number of logical drives in the extended partition as desired( these numbering will start from /dev/sda5 onwards)

Edit- schematic diagram

Code:

/---------------------------------\
| |-----------------------------| |
| |             /dev/sda1     <-|-|---- primary
| |-----------------------------| |
|---------------------------------|
| |-----------------------------| |
| |           /dev/sda5       <-|-|---- logical drives
| |-----------------------------| |
| |-----------------------------| |
| |        ......               | |
| |                             | |
| |        ......               | |
| |-----------------------------| |
\---------------------------------/

i found that the same old classical way of partitioning ( fdisk ) is the best way. we know what we are doing.

these days i found people got problem in partitioning from ubuntu and various other flavors of linux. they dont know that we can only have max 4 primary partition in a disk. they even make swap as primary and get problem in partitioning.

regards

Richard Cranium · 06-08-2010, 09:56 PM

Quote:

Originally Posted by onebuck

Hi,

I don't use nor care for 'lvm'.

But each to his/her own.

Fair enough. I balked at using lvm for a long time, myself.

Now I just set up various RAID1 partitions and run lvm on top of that. Since I'm using xfs (and some reiserfs), I can always increase the size of a logical volume without having to unmount the filesystem. Very convenient and I no longer worry about how I am going to divide up my hard drive(s).

You can even tell lvm to move data off of a given physical device while the system is running. All in all, pretty nice and actually fairly easy to use.

Your mileage may vary. :-)

rkrishna · 06-09-2010, 06:36 AM

Quote:

Originally Posted by Richard Cranium

Fair enough. I balked at using lvm for a long time, myself.

Now I just set up various RAID1 partitions and run lvm on top of that. Since I'm using xfs (and some reiserfs), I can always increase the size of a logical volume without having to unmount the filesystem. Very convenient and I no longer worry about how I am going to divide up my hard drive(s).

You can even tell lvm to move data off of a given physical device while the system is running. All in all, pretty nice and actually fairly easy to use.

Your mileage may vary. :-)

thanks Richard Cranium for the great info. let me try it next time. so slack 13.1 is going to be on lvm

and it s time for google lvm
regards rkrishna

onebuck · 06-09-2010, 07:17 AM

Hi,

Quote:

Originally Posted by Richard Cranium

Fair enough. I balked at using lvm for a long time, myself.

Now I just set up various RAID1 partitions and run lvm on top of that. Since I'm using xfs (and some reiserfs), I can always increase the size of a logical volume without having to unmount the filesystem. Very convenient and I no longer worry about how I am going to divide up my hard drive(s).

You can even tell lvm to move data off of a given physical device while the system is running. All in all, pretty nice and actually fairly easy to use.

Your mileage may vary. :-)

I'm not balking. Just don't need the hassle of 'lvm'. 'KISS' hasn't failed me yet. No real advantage using 'lvm' for me since my systems are planned for expansion and the convenience is not the driving factor to add to the complexity. 'ext2/3/4' meet the needs of my systems and installs that provide a stable system using Slackware with these filesystem types.

Now video or other similar data types will be addressed when necessary but not for normal system usage.

As I said "Each to his/her own choices'. That's part of the Slackware way.