On Tue, Sep 04, 2001 at 11:12:27PM -0400, Jude DaShiell wrote: > What killed me was disk druid and fdisk if that's what it's called. > Ended up having to do some math because fdisk wanted everything in terms While little math won't hurt there is an easier way to do it. fdisk allows you to define partition size in Megabytes, Gigabytes or Kilobytes. You just tell the size with the following format +1500M here is an improvised session with fdisk, first is a Command prompt where I selected n for new partition followed by p for primary partition. I selected 1 for first partition starting with cylinder 1. After that you can define the partition size in megabytes etc. You need to prepend plus sign in front of the number and upper case letter after the number, M for megabytes etc. Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-19, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-19, default 19): Hope it helps, -- Rafael > of cyllinders and messed up the calculations. I have a disk with 2489 > cyllinders on it so it's above standard size. For that reason I restored > the silent workstation installation that had already been on the disk. > At least that way there was a credible set of partitions on the disk. > Not saying they are good, just that they're credible. So I go into the > boot up process and hit control-alt-f1 and type in account and password on > separate lines. How can I get this system talking and what needs to be > done to keep it talking on next boot up? Finally the instructions in > bootltlk.txt distributed with that speakup_.gz file are not making sense > to me over here tonight. At what point in the installation process is it > a good time to stop installation and do the commands in that file? Would > it be useful to just start with the litetalk disk in a: and no cd in the > cdrom so that the install will be forced to a stop when the cd cannot be > found the first time around? Finally, is it control-\ that gets the kind > of stop needed here? review seemed to be present but was shakey inside > those disk partitioning tools. The lilo got skipped again on installation > too. I wonder if red hat made lilo available only once xconfiguration had > been done. Since I had errors in that part of the install I had to skip > out to go on so that would explain why lilo hadn't come up. > > Jude <jdashiel@shellworld.net>