Fedora Telnet install (Part 2 Of 2)

Janina Sajka janina at rednote.net
Tue Aug 9 22:09:13 EDT 2005


[Continued from a previous post]

How To Do A Telnet INstall Of FC4 -- Part 2 Of 2

4.)	Once you make a telnet connection, the installation will proceed
precisely as described in the HOWTO. However, there is one important
difference that must be considered. You will not be able to switch
consoles when performing a telnet installation, so you will need a
different strategy for dealing with the inaccessible firstboot
application that Fedora will launch when you reboot after a successful
install.

Without a strategy for what to do about first boot, you'll find yourself
wondering what happened. You'll think you've done an installation
without error, and rebooted just as instructed, and you'll be correct.
Firstboot doesn't talk, and there's no way to escape out of it once it's
running. Without sighted assistance, you can only force a reboot--not a
pretty scenario.

Fortunately, there are good ways to handle firstboot. One of these is
described in the HOWTO. It involves going to single user mode when you
boot your completed Fedora installation for the first time.
Fortunately, there's an easy way to insure that your system will go
directly to single user mode when you reboot following your telnet
installation. Here's how to make that happen:

IMPORTANT: When you get the installation screen that asks you if you
want to pass any options to the grub boot loader, put a single char in
the provided field:

s

That's all. One letter, 's' which stands for "single user mode."

NOTE: You can, of course, get to single mode directly from the grub
prompt as described in the HOWTO. The advantage of adding this argument
is that you avoid the rather inaccessible grub prompt. The disadvantage
is that you must then remove this char (see #6 below) to enable standard
booting.

5.)	Once you've completed your installation and rebooted to single
user mode, follow the steps to remove firstboot as described in the
HOWTO.

NOTE: Since you've rebooted, there's no need to do a "cd /mnt/sysimage'
or 'chroot .' command. These are no longer pertinent--because you have
passed that point by virtue of having rebooted.

6.)	Lastly, you must now remove that letter s from the line that
begins with the word "kernel" near the bottom of your /boot/grub.conf
file. Use any text editor to do this.

PS: This message would be half this long except for the inaccessible
firstboot application. May I suggest complaints to Redhat are in order?
I find it outrageous that there is no way to just tell the computer to
"skip this firstboot thing." There certainly could be and should be such
an option.

_______________________________________________
Blinux-list mailing list
Blinux-list at redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list




More information about the Speakup mailing list