custom installation failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
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>





[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]