Patrick Nelson wrote: ----------------->>>> Patrick Nelson wrote: ----------------->>>> This system current HD configuration is: /dev/hda DOS /dev/hdb Me trusty Linux system I never boot into windows anymore so I want to grab the hdisk space for Linux. The current partition tables for the system are as follows: Device Boot Start End Blocks ID System /dev/hda1 * 1 518 2088544+ 6 FAT16 /dev/hda2 519 874 1435392 1b Hidden Win95 FAT32 Device Boot Start End Blocks ID System /dev/hdb1 1 50 201568+ 83 Linux /dev/hdb2 51 875 3326400 5 Extended /dev/hdb5 51 396 1395040+ 83 Linux /dev/hdb6 397 545 600736+ 83 Linux /dev/hdb7 546 644 399136+ 83 Linux /dev/hdb8 645 743 399136+ 83 Linux /dev/hdb9 744 842 399136+ 83 Linux /dev/hdb10 843 874 128992+ 82 Linux Swap Output of df -h Filesystem Size Used Avail Use% Mounted on /dev/hdb1 191M 99M 86M 55% / /dev/hdb6 568M 131M 408M 24% /home /dev/hdb8 377M 1.2M 357M 0% /tmp /dev/hdb5 1.6G 818M 432M 65% /usr /dev/hdb7 377M 120M 238M 33% /usr/src /dev/hdb9 377M 130M 228M 36% /var So my question is... What would be the best way to convert and utilize the windows hdisk for my Linux system? Opinions appreciated! ----------------->>>> OK I've decided to go with 4 partitions on the 2 drives. /dev/hda1 50M /boot /dev/hda2 3.3G / /dev/hdb1 250M SWAP /hda/hdb2 3.3G /home I deleted the Winbloz partitions on hda created the new partitions, saved partition info to disk, mk2efs both partitions, mounted the partitions, df -h to be sure of sizes and whatnot. Great, but something occurred to me... Will it boot now into Linux with out the winbloz partitions there? Just to be sure I edited lilo.conf and removed the winbloz item and then ran lilo which ran without incident. Being paranoid I ran mkbootdisk --device /dev/fd0 2.2.14-5.0 which gave me an error that vmlinuz-2.2.14-5.0 didn't exists which I had named just vmlinuz, so I cp -p vmlinuz vmlinuz-2.2.14-5.0 and re-ran mkbootdisk --device /dev/fd0 2.2.14-5.0 and this time it completed. Great now I am left to the reboot... Which of course worries me! Anyone care to comment of if I did this right or wrong or anything else you can think of? Oh I have not copied /boot from it's current location to it's new one, so I didn't change lilo.conf except to get rid of the winbloz boot info. Once this reboots then I will do the "edit fstab" then umount then mount thing to lock in the new location(s). ----------------->>>> Oops! I'm doing the same thing on a RH box and mistakenly said the mkbootdisk thing which doesn't exist on SuSE 7.1... Really use Yast to create the boot disk for the system. I guess I just got to many things going a t once.