summaryrefslogtreecommitdiff
path: root/Hurd/InstallNotes.mdwn
diff options
context:
space:
mode:
authorJoachim Nilsson <joachim@gnufans.org>2003-04-02 22:00:34 +0000
committerJoachim Nilsson <joachim@gnufans.org>2003-04-02 22:00:34 +0000
commite30059168a2ff8190513a392c334d01f0882628b (patch)
tree33820b2c524e1780a5e156bf2fa2d901fd504d06 /Hurd/InstallNotes.mdwn
parent454b94d4bafa2c6d7192ceb7ace4d75d420ad48a (diff)
none
Diffstat (limited to 'Hurd/InstallNotes.mdwn')
-rw-r--r--Hurd/InstallNotes.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/Hurd/InstallNotes.mdwn b/Hurd/InstallNotes.mdwn
index 2bfd6944..d183f824 100644
--- a/Hurd/InstallNotes.mdwn
+++ b/Hurd/InstallNotes.mdwn
@@ -57,11 +57,11 @@ The tarball is setup to extract everything into the current directory. After mou
# cd /gnu
# tar --same-owner -xvzpf ~/gnu-latest.tar.gz
-NOTE: This should NOT be confused with the deprecated `cross-install` script method.
+**_NOTE:_** This should NOT be confused with the `cross-install` script method. It is only used by maintainers when creating a new tarball.
## <a name="5_Booting_GNU"> </a> 5. Booting GNU
-All is now in readiness to boot GNU for the first time. After verifying that the GRUB boot disk is in the drive, reboot. If all goes well, a GRUB menu will be displayed. Hit c for the GRUB command line.
+Now things are setup to boot GNU for the first time. Verify that the GRUB boot disk is in the drive and reboot. If all goes well, a GRUB menu will be displayed. Hit c for the GRUB command line.
First, the root file system needs to be set. GRUB uses a partition nomenclature that is a bit different from either GNU or GNU/Linux: both IDE and SCSI drives are named `(hdN)`. `N` is the drive number (zero based) as reported by the BIOS. That is, GRUB makes no distinction between IDE and SCSI disks. The partitions, like the disks, are also indexed numerically from zero: `(hdN,M)`. If this sounds bad, relax: GRUB is also helpful.
@@ -83,7 +83,7 @@ Since the Hurd has not yet been configured, it must be run in single user mode.
Thus, continuing with the above example and assuming that the first drive in the master on the secondary controller, we would have:
- grub> kernel /boot/gnumach.gz -s root=device:hd2s1
+ grub> kernel /boot/gnumach.gz root=device:hd2s1 -s
[Multiboot-elf, ...]
Next, the root file system server and the exec server must be loaded. This is done using GRUB's boot module capability. The parameters are the semantics by which the kernel passes some important values to the servers.
@@ -98,7 +98,7 @@ Next, the root file system server and the exec server must be loaded. This is do
grub> module /lib/ld.so.1 /hurd/exec $(exec-task=task-create)
[Multiboot-module 0x494000, 0x27afe bytes]
-It is important that each module string is only a single separate line, or by escaping the EOL (end of line) with a back slash. Remember though to make sure there are **_no trailing spaces!_** Adding this to GRUB's `menu.lst` file as soon as possible is advised.
+**_Important:_** each module string should be asingle separate line _or_ line wrapped with a backslash at the end of each line. Remember to make sure there are **_no trailing spaces!_** Adding this to GRUB's `menu.lst` file as soon as possible is advised.
Finally, GNU can be booted: