Welcome to the Jupiter rescue CD rom.
This is the README file.
It is located in /usr/doc/cdrom-README (on the CD rom).
It will give you an idea of where things are and how to get started.
Let's take things in chronological order.


**If you have an older PC, with both floppy and a CDROM drive, you
will want to be sure that the BIOS is set to boot fromt the CDROM, or
skip to the instructions for booting from a floppy.

When you boot from this CD, the boot sector turns control over to lilo.
Lilo will launch Linux on whatever drive you specify.
You can use it to jump right into your Linux partition on drive 1 or
drive 2, assuming that partition is compatible with kernel 2.4.18-14,
and assuming it has the necessary speech adapters.
Or you can use it with a second initrd floppy.
But most of the time you will send Linux to your CD rom,
i.e. the talking rescue CD.

The CD runs the Jupiter speech system,
and includes a fully functional mini-distribution of linux that is
capable of accessing files on your computer, or websites on the internet.
so - you will probably tell lilo to use the CD rom.

Here is the screen, as it appears when lilo runs.

SCREEN 1
------------------------------------------------------------
This is a general purpose boot disk - please forgive all the options.
a1 = primary partition on the first disk
a = first disk, as an ide device
as = first disk, as an scsi device
b1 b bs ... second disk, the slave
c1 c cs ... third disk, master on controller 2
d1 d ds ... fourth disk, slave on controller 2
If you are using this as a rescue floppy, with a second floppy acting
as initrd, type r.   (for rescue)
The default is c, as in /dev/hdc.  This is usually right.
This is usually where your CD is located.
If unsure, sit back and wait 5 seconds, and we'll give hdc a shot.
------------------------------------------------------------
END OF SCREEN 1

The intro message also contains two control G bells.
The computer should beep twice, although this does not work on every
machine.
When you hear the two bells, or when you think the time is right,
enter the appropriate code, or sit back and do nothing,
and we'll come up on /dev/hdc, which is (probably) your CD rom.

If your machine cannot boot from a CD,
and there are a few that cannot,
copy the image /boot/floppy.img onto a floppy and boot from that.

From within linux, you would type:
dd if=/mounted-cd/boot/floppy.img of=/dev/fd0 bs=4k

I'll assume, from here on in,
that you brought Linux up on my rescue CD.

When it wakes up, Linux runs the startup program /sbin/init.
I don't use the standard init(8) program that comes with Linux.
Instead I wrote my own init program that executes
the startup script /root/.bash_rescue.
If you have the CD rom, you can read the script directly.
It's pretty well commented.
But not everybody likes reading shell, so I'll describe it here.

The first thing we want to do is load Jupiter so the system can talk.
The script asks you for the synthesizer and port.
Here is the screen, as it appears at this point.

SCREEN 2
------------------------------------------------------------
I'm ready to load the Jupiter speech adapter, but I need to know
the synthesizer and port. Enter synthesizer, port, and keyboard layout,
space separated, on one line.
Synthesizer codes are: dti (DecTalk internal), dte (DecTalk external),
dbe (DoubleTalk external), epc (Echo PC), bns (Braille N speak),
g (generic), and 0 (no synthesizer).
The port is a number from 0 to 3. If you are new to linux, 0 = COM1
and 1 = Com2, etc.
Include this number even if the synthesizer is internal; it selects
an io base address.
Finally, enter k for Karl's keyboard or s for the Speakup layout.
Example: dbe 0 s
would access a DoubleTalk external on port 0 with a Speakup keyboard.
------------------------------------------------------------
END OF SCREEN 2

Once again there are two control G's in this message,
so you should hear two beeps.
Remember, two bells at the lilo prompt and two bells at the synthesizer
prompt.
bear in mind, your computer may not sound the first bells -
it may not even sound the second bells -
it may not have a toggle speaker at all!
But I hope it does, because I go *NUTS* without the constant audio
feedback provided by that little toggle speaker.

Type in the three codes: synthesizer port keyboard
If all goes well you will hear the words "Jupiter ready."
If not, you are scrod!

Next, the script tries to make /tmp a writable directory.
(Write enabled)
Remember, everything in your CD is readOnly.
You cannot change it, and you cannot add to it.
However, I can create a dynamic ramdisk and mount it on /tmp.
That makes /tmp writable. (write enabled)
I also create a ramdisk for /etc, and copy files into it.
There are a lot of programs that change data in /etc,
and you are going to want to run these programs.

You'll notice that /root is actually a symbolic link to /etc/root.
And since /etc is now contained in a ramdisk,
your home directory, /root, is now writable.
Create files if you like, even download packages from the internet.
But remember, your root directory lives in ram.
It will all go away when you turn off the computer,
unless you copy it to disk.

At this point your rescue CD is mounted on /,
dynamic ramdisks are mounted on /tmp and /etc,
(To make these areas writable),
/proc is mounted, and so is /dev/pts.
Type `mount' and you'll see all these mounted file systems.

If you have 144mb of ram or more, there is an alternative.
The startup script asks if you want to pull the entire disk into memory.
(Obviously this makes everything write enabled.)
The disk is only 80mb, so there's still plenty of ram for other tasks.
You'll probably want to say yes.
Now the disk doesn't have to spin up every time you execute a new program.
Furthermore, you can remove the rescue disk and put in another one.
This may be necessary, if you want to reinstall some software from an
installation disk.

Next, the script turns control over to you by spawning an interactive shell.
Actually there are six shells, on six virtual consoles.
You can switch between them via alt-F1 through alt-F6.

Now - suppose you want to fix some corrupt files on your computer.
It won't boot and you don't know why.
Or maybe you do know why. Maybe you forgot to run lilo. Whatever.

There are a number of predefined mount points under /mnt.
List the directory and you'll see what I mean.
These are pretty self-explanatory.
Type `mount /mnt/a1' to mount the first partition of drive 1
on /mnt/a1.
Mount /mnt/b3 for the third partition of drive 2, and so on.
Use /mnt/r1 through /mnt/r4 for the first 4 raid devices.
/mnt/fd is the floppy drive, and /mnt/cd is the CD rom.
You don't have to specify the file system type; we figure it out
automatically.  You can look at Linux files, NT, Windows, or DOS.

You must unmount these file systems when your done, or they may be
corrupt.  Type `mount' to see what is mounted.

If you have mounted a working Linux partition, you can chroot into that
partition and go to work, as though you had booted straight in.
If /mnt/a1 is a working Linux partition, type `chroot /mnt/a1',
do your work, then exit, and you'll be return to the rescue CD.
Note, you will not be able to mount /proc inside your Linux partition,
and lots of programs, like ps, won't work without /proc.
If you are going to be working inside a partition for a while,
and you want access to all your favorite utilities,
you should probably unmount /proc and /dev/pts first,
then chroot to your partition, then remount them there.
But you have to keep track.
You have to unmount these virtual file systems before you
exit back to your rescue CD.

This disk contains all the tools you need to access the Internet,
but that doesn't mean it's going to be easy.
If you are lucky, you are connected via ethernet to an ISP
that supports dhcp, such as a cable modem.
Actually, you might be such a person; it's not unusual.
If this is the case, you only need type `internet module',
and you should be connected to the internet.
Here module is the name of the module that manages your ethernet card.
If you are not sure what this is, check your /etc/modules.conf file
and look for the line that says "alias eth0".
The word after eth0 is the module that drives your primary ethernet card.
So if the line looks like "alias eth0 foo",
you want to type `internet foo' to conect to the internet.

I have loaded most of the ethernet modules,
but there are a lot of different cards out there.
If I don't have the module you need to connect to the internet,
please let me know.
Send mail to karl@eklhad.net and maybe we can figure it out.

Dial-up through ppp is also supported.
Use ppp as the module name, then specify the modem, protocol,
phone number, login, and password.
Here is an example.

internet ppp ttyS1 pap 5551234 joesmith joes_password

Type ppp-off to disconnect.
Subsequent sessions can be managed via ppp-on and ppp-off.

Once you are connected,
the standard text-based internet programs are all here.
telnet, ftp, ssh, lynx.
You also have edbrowse, which is a combination editor,
browser, and mail client.
This can be accessed by the alias e.
e filename
edits a file, and
e www.google.com
accesses the google search engine.
Learn more about edbrowse at www.eklhad.net/linux/app/

The local timezone is set to eastern standard, because that's where I live.
You can change it, since /etc is remounted on a ram disk,
but the next time you boot from this CD rom you'll be back in est again.
If you are in some other timezone, well, you'll just have to apply
a mental fudge factor whenever you ask the computer for the time of day.

When you are done, unmount all the file systems you have mounted,
then turn off the computer.
If you prefer a soft reboot, push the reset button,
then push the eject button to remove your disk.
When the computer comes back around it should boot from your hard drive,
as you have directed.

If your computer contains raid arrays with autodetect, take special note.
(If you don't know what raid is, skip this paragraph.)
Your raid arrays will come up running.
Check the contents of /proc/mdstat to see which raid arrays are active.
It doesn't matter whether you mount the filesystems associated with these
arrays or not; the raid arrays are active nonetheless.
They must be stopped before you power down the computer.
Use `raidstop' to turn off each of the raid arrays.

The Jupiter modules, config files, patches, documentation,
and supporting utilities can be found in /usr/lib/jupiter.

Enjoy,
Karl Dahlke
karl@eklhad.net