add user-ref.texi.

This commit is contained in:
okuji 1999-10-21 17:38:49 +00:00
parent 42afef19eb
commit c14ac03919
7 changed files with 1203 additions and 11 deletions

View file

@ -1,3 +1,8 @@
1999-10-22 OKUJI Yoshinori <okuji@kuicr.kyoto-u.ac.jp>
* docs/user-ref.texi: New file.
* docs/Makefile.am (UNFINISHED_MANUALS): Added user-red.texi.
1999-10-21 OKUJI Yoshinori <okuji@kuicr.kyoto-u.ac.jp>
Add BIOS drive remapping support for chain-loading some foolish

View file

@ -7,7 +7,7 @@ SRC2TEXI = src2texi
noinst_SCRIPTS = $(HELP2MAN) $(SRC2TEXI)
# The unfinished manuals.
UNFINISHED_MANUALS = new-grub.texi tutorial.texi
UNFINISHED_MANUALS = new-grub.texi tutorial.texi user-ref.texi
EXTRA_DIST = menu.lst $(man_MANS) $(noinst_SCRIPTS) \
$(EXAMPLES) $(multiboot_TEXINFOS) $(UNFINISHED_MANUALS)

View file

@ -91,7 +91,7 @@ SRC2TEXI = src2texi
noinst_SCRIPTS = $(HELP2MAN) $(SRC2TEXI)
# The unfinished manuals.
UNFINISHED_MANUALS = new-grub.texi tutorial.texi
UNFINISHED_MANUALS = new-grub.texi tutorial.texi user-ref.texi
EXTRA_DIST = menu.lst $(man_MANS) $(noinst_SCRIPTS) \
$(EXAMPLES) $(multiboot_TEXINFOS) $(UNFINISHED_MANUALS)

View file

@ -149,7 +149,7 @@ desirable. However, if you don't want to reboot your computer, run the
program @file{/sbin/grub}.
In both, GRUB will show the command-line interface. First, set the
GRUB's @dfn{root partition}@footnote{Note that GRUB's root partition is
GRUB's @dfn{root device}@footnote{Note that GRUB's root device is
not your OS's root partition; if you need to specify a root partition
for your OS, add the argument into the command @command{kernel}.} to the
partition which has your GRUB images, like this:
@ -168,7 +168,7 @@ grub> find /boot/grub/stage1
This will search for the filename @file{/boot/grub/stage1} and show the
device which contains the images.
If you set the root partition correctly, run the command
If you set the root device correctly, run the command
@command{setup}:
@example
@ -217,7 +217,7 @@ steps:
@enumerate
@item
Set GRUB's root partition to the drive where the OS images is stored by
Set GRUB's root device to the drive where the OS images is stored by
the command @command{root}.
@item
@ -239,7 +239,7 @@ Since GNU/Hurd is Multiboot-compliant, it is easy to boot it; there is
nothing special. But do not forget that you specify a root partition to
the kernel.
First, set GRUB's root partition to the same drive as
First, set GRUB's root device to the same drive as
GNU/Hurd's. Probably @code{find /boot/gnumach} or such will help
you.
@ -259,7 +259,7 @@ And, finally, run the command @command{boot}.
It is relatively easy to boot GNU/Linux from GRUB, because booting
GNU/Linux somewhat resembles booting a Multiboot-compliant OS.
First, set GRUB's root partition to the same drive as
First, set GRUB's root device to the same drive as
GNU/Linux's. Probably @code{find /vmlinuz} or such will help
you.
@ -316,7 +316,7 @@ chain-load the boot loader for the operating system. Normally, the boot
loader is embedded in the @dfn{boot sector} of the partition on which
the operating system is installed.
First, set GRUB's root partition to the partition by the command
First, set GRUB's root device to the partition by the command
@command{rootnoverify}:
@example

1187
docs/user-ref.texi Normal file

File diff suppressed because it is too large Load diff

View file

@ -373,7 +373,7 @@ general_error:
/* go here when you need to stop the machine hard after an error condition */
stop: jmp stop
notification_string: .string "stage1"
notification_string: .string "stage1 "
geometry_error_string: .string "Geom"
hd_probe_error_string: .string "Hard Disk"
read_error_string: .string "Read"

View file

@ -340,9 +340,9 @@ general_error:
stop: jmp stop
#ifdef STAGE1_5
notification_string: .string " stage1.5"
notification_string: .string "stage1.5 "
#else
notification_string: .string " stage2"
notification_string: .string "stage2 "
#endif
geometry_error_string: .string "Geom"