![]() |
repartitioning hard drive on Slackware 11- distributing free space, need an advice
Hello!
I've recently removed Window(r) system from my machine and now I want to redistribute free space between partitions in "more optimized" way. I'm just not quite sure what should I take in account before repartitioning, abd which filesystem should I use for which partitions, which folders should be placed on a separate partition, etc. But I'm quite sure that current partition scheme isn't good. So I need and advice, or a good link to read.. :) Current situation: Slackware 11 System with 512mb ram and single 40Gb hard drive with following partition scheme: 1)/dev/hdc1 - primary 7.2G ext3 (former windows' system partition), mounted as /mnt/win_c, almost empty (129Mb used by system)/ 2)extended partition which contains: 2.1) /dev/hdc5 - 21G ext3 (former windows "data" partition0, mounted as /mnt/win_d, almost empty (129Mb used by system) 2.2) /dev/hdc6 - 512mb swap partition. Mostly isn't used, swap usage at most time is about 0..4mb. 3) /dev/hdc3 - 6,7GB ext3, mounted as / 5,8 Gb used. The space distribution is so strange because there was windows XP on same machine. With current partition scheme I'm running out of space in / when compiling something "heavy" (two parallel "wine" compilations will be enough) in ~ directory, and it looks like contents of / doesn't change often (except for /tmp and /home) - changes occur only when installing new software. It looks like having 1GB swap partition instead of 512mb would be good. Also, some articles suggest splitting system into 6 or 7 partitions, each with different filesystem and different flags. (even for a /boot directory) is this necessary? So, what's the best way to redistribute free space for my Slackware Linux system? thanks. |
I don't think it matters, except esthetically. If you tend to run out of room in /tmp or /var/tmp, maybe you should mount those on a tempfs file system -- essentially a ram disk. If you used LVM, you could later change your mind about the partitioning, but I don't think that's worth the trouble.
|
Quote:
Quote:
|
What's on /dev/hdc3?
You've got 5.8GB of something on it. Is this valuable data? If it is not, and you want to wipe out the entire dissk and start from scratch, I've got a scheme for you.
|
Hi,
Quote:
Disk partitioning is a personal taste issue! If you have a general desktop then you can get away with just '/' & 'swap'. If you want to understand partitioning in general then look at this link. If you want to use a system as a server then that is where the partition scheme can be interesting. Below is an example of a server on my lan; Code:
amos:~# fdisk -lCheck my sig for some good references. The 'Slackware LQ Suggestions!' has a lot of material. Some people are now including the 'Slackware LQ Suggestions!' link in their sig. |
Just mount /home on /dev/hdc5
I am no expert but I think the simplest short-term solution would be to mount /home on /dev/hdc5, which should leave plenty of space on /dev/hdc3 for the system files in / and involve no need to repartition anything. You can then take your time investigating what can be a complex issue.
Meantime /dev/hdc1 could be used for backup or installing a dual-boot secondary linux system for testing. Both systems can then access /home. This will require careful investigation into the correct lilo.conf setup. I ran this type of setup for a while before settling on Slackware and found it very useful. Whatever happens with the trial system it should not affect /home or the running system, which you can always fall back on. The booting setup is, however, critical, so do get advice from someone knowledgeable. |
Quote:
Quote:
Quote:
Quote:
Problem solved, thanks for the help. |
| All times are GMT -5. The time now is 04:18 AM. |