> I think this is not a problem since the user will not make the info
>by himself usually. Info is distributed with the package according to
>GNU Coding Standards.
After checking out grub CVS repository, developer try to configure
then make the grub package. Then it produces many errors. Developer
try to find reason then he found that it is due to the unreleased
version of texinfo command *sigh*. Yes, with Emacs
texinfo-format-buffer may work but current makefile try to make
grub.info with makeinfo. The fact consumes many grub developer's time
meaningless. I believe maitainer shoud rethink about using "@command"
in grub.texi.
BTW, I think it is very inconvenient the nodes don't have any next,
prev, up link.
*** grub/docs/grub.texi Fri May 7 19:16:43 1999
--- grub.texi Wed May 12 00:04:34 1999
***************
*** 68,74 ****
@c The Top node appears only in Info.
@ifinfo
! @node Top
@top GRUB
This file documents GNU GRUB, the Grand Unified Bootloader. This
--- 68,74 ----
@c The Top node appears only in Info.
@ifinfo
! @node Top, Introduction, (dir), (dir)
@top GRUB
This file documents GNU GRUB, the Grand Unified Bootloader. This
***************
*** 99,105 ****
* Automated install:: Installation via @code{install=}.
* Installation under Unix:: Installation by @file{/sbin/grub}.
! Booting your operating systems
* Command-line:: The flexible command-line interface.
* Menu:: The simple menu interface.
--- 99,105 ----
* Automated install:: Installation via @code{install=}.
* Installation under Unix:: Installation by @file{/sbin/grub}.
! Booting your operating system
* Command-line:: The flexible command-line interface.
* Menu:: The simple menu interface.
***************
*** 123,129 ****
@end ifinfo
! @node Introduction
@chapter Introduction
Briefly, a @dfn{bootloader} is the first software program that runs when
--- 123,129 ----
@end ifinfo
! @node Introduction, Installing, Top, Top
@chapter Introduction
Briefly, a @dfn{bootloader} is the first software program that runs when
***************
*** 139,145 ****
@end menu
! @node History
@section History of GRUB
GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU
--- 139,145 ----
@end menu
! @node History, Features, Introduction, Introduction
@section History of GRUB
GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU
***************
*** 162,173 ****
@code{grub}. Just hit return when prompted for a password.}
! @node Features
@section GRUB features
technical.html: why another bootloader?
! @node Role of a bootloader
@section The role of a bootloader
The following is a quotation from Gordon Matzigkeit, a GRUB fanatic:
--- 162,173 ----
@code{grub}. Just hit return when prompted for a password.}
! @node Features, Role of a bootloader, History, Introduction
@section GRUB features
technical.html: why another bootloader?
! @node Role of a bootloader, , Features, Introduction
@section The role of a bootloader
The following is a quotation from Gordon Matzigkeit, a GRUB fanatic:
***************
*** 199,205 ****
did writing it.
! @node Installing
@chapter How to install GRUB on your computer
Due to the nature of a @dfn{bootloader}, you need to install GRUB on
--- 199,205 ----
did writing it.
! @node Installing, Using, Introduction, Top
@chapter How to install GRUB on your computer
Due to the nature of a @dfn{bootloader}, you need to install GRUB on
***************
*** 214,220 ****
@end menu
! @node Boot floppy
@section Creating a GRUB boot floppy
@quotation
--- 214,220 ----
@end menu
! @node Boot floppy, Automated install, Installing, Installing
@section Creating a GRUB boot floppy
@quotation
***************
*** 247,253 ****
come with many GNU and GNU/Linux distributions.
! @node Automated install
@section Installation via the @code{install=} command
@quotation
--- 247,253 ----
come with many GNU and GNU/Linux distributions.
! @node Automated install, Installation under Unix, Boot floppy, Installing
@section Installation via the @code{install=} command
@quotation
***************
*** 343,355 ****
the OS.
! @node Installation under Unix
@section Installation by @file{/sbin/grub}
FIXME
! @node Using
@chapter Booting your operating system
GRUB has both a simple menu interface for choosing preset entries from a
--- 343,355 ----
the OS.
! @node Installation under Unix, , Automated install, Installing
@section Installation by @file{/sbin/grub}
FIXME
! @node Using, Filesystems, Installing, Top
@chapter Booting your operating system
GRUB has both a simple menu interface for choosing preset entries from a
***************
*** 370,376 ****
@end menu
! @node Command-line
@section The flexible command-line interface
The command-line interface provides a prompt and after it an editable
--- 370,376 ----
@end menu
! @node Command-line, Menu, Using, Using
@section The flexible command-line interface
The command-line interface provides a prompt and after it an editable
***************
*** 399,405 ****
@c beautiful.
! @node Menu
@section The simple menu interface
The menu interface is quite easy to use. It's commands are both
--- 399,405 ----
@c beautiful.
! @node Menu, Menu entry editor, Command-line, Using
@section The simple menu interface
The menu interface is quite easy to use. It's commands are both
***************
*** 417,423 ****
respectively by pressing @key{c} or @key{e}.
! @node Menu entry editor
@section Editing a menu entry
This looks much like the main menu interface, but with the lines in the
--- 417,423 ----
respectively by pressing @key{c} or @key{e}.
! @node Menu entry editor, Commands, Menu, Using
@section Editing a menu entry
This looks much like the main menu interface, but with the lines in the
***************
*** 434,440 ****
and in that case the changes are thrown away).
! @node Commands
@section The list of available commands
In this section, we list the available commands, both in the
--- 434,440 ----
and in that case the changes are thrown away).
! @node Commands, , Menu entry editor, Using
@section The list of available commands
In this section, we list the available commands, both in the
***************
*** 661,667 ****
@end table
! @node Filesystems
@chapter Filesystem syntax and semantics
GRUB uses special syntax for specifying disk drives, that can be
--- 661,667 ----
@end table
! @node Filesystems, Troubleshooting, Using, Top
@chapter Filesystem syntax and semantics
GRUB uses special syntax for specifying disk drives, that can be
***************
*** 675,681 ****
@end menu
! @node Device syntax
@section How to specify devices
The device syntax is like this:
--- 675,681 ----
@end menu
! @node Device syntax, Filename syntax, Filesystems, Filesystems
@section How to specify devices
The device syntax is like this:
***************
*** 709,715 ****
@end example
! @node Filename syntax
@section How to specify files
There are two ways to specify files, @dfn{absolute pathname} and
--- 709,715 ----
@end example
! @node Filename syntax, , Device syntax, Filesystems
@section How to specify files
There are two ways to specify files, @dfn{absolute pathname} and
***************
*** 733,739 ****
offset is zero.
! @node Troubleshooting
@chapter Error messages reported by GRUB
This chapter describes the meanings of the error messages reported by
--- 733,739 ----
offset is zero.
! @node Troubleshooting, Multiboot, Filesystems, Top
@chapter Error messages reported by GRUB
This chapter describes the meanings of the error messages reported by
***************
*** 746,752 ****
@end menu
! @node Stage1 errors
@section Errors reported by the Stage 1
The general way that the Stage 1 handles errors is to print an error
--- 746,752 ----
@end menu
! @node Stage1 errors, Stage1.5 errors, Troubleshooting, Troubleshooting
@section Errors reported by the Stage 1
The general way that the Stage 1 handles errors is to print an error
***************
*** 782,788 ****
@end table
! @node Stage1.5 errors
@section Errors reported by the Stage 1.5
The general way that the Stage 1.5 handles errors is to print an error
--- 782,788 ----
@end table
! @node Stage1.5 errors, Stage2 errors, Stage1 errors, Troubleshooting
@section Errors reported by the Stage 1.5
The general way that the Stage 1.5 handles errors is to print an error
***************
*** 793,799 ****
sequence.
! @node Stage2 errors
@section Errors reported by the Stage 2
The general way that the Stage 2 handles errors is to abort the
--- 793,799 ----
sequence.
! @node Stage2 errors, , Stage1.5 errors, Troubleshooting
@section Errors reported by the Stage 2
The general way that the Stage 2 handles errors is to abort the
***************
*** 944,956 ****
@c its own manual, because Multiboot is not only for GRUB. Perhaps we
@c should write the Multiboot manual "multiboot.texinfo", and then
@c include it here. - okuji
! @node Multiboot
@chapter Standard booting interface
boot-proposal.html
! @node Hacking
@chapter Implementation details
technical.html
--- 944,956 ----
@c its own manual, because Multiboot is not only for GRUB. Perhaps we
@c should write the Multiboot manual "multiboot.texinfo", and then
@c include it here. - okuji
! @node Multiboot, Hacking, Troubleshooting, Top
@chapter Standard booting interface
boot-proposal.html
! @node Hacking, Index, Multiboot, Top
@chapter Implementation details
technical.html
***************
*** 958,964 ****
PC_partitioning.txt
! @node Index
@unnumbered Index
@c Currently, we use only the Concept Index.
--- 958,964 ----
PC_partitioning.txt
! @node Index, , Hacking, Top
@unnumbered Index
@c Currently, we use only the Concept Index.
