vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

add --force into the command chainloader.

Browse source
This commit is contained in:
okuji 2000-01-15 03:20:59 +00:00
parent 7692b3eab6
commit 18c2360755
5 changed files with 51 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/tutorial.texi
View file

@ -367,6 +367,12 @@ grub> chainloader +1
Do not care about what @samp{+1} is. We describe it later in
@ref{Filesystem}. If this succeeds, run the command @command{boot}.
@strong{Caution:} Some boot loaders (such as the one in SCO Unixware
7.1) are defective in the signature, so you will have to specify the
option @option{--force} to @command{chainloader} for them. The option
might seem to solve your problem, but we strongly recommend reporting
the bug to the maintainer.
However, some tricks will be necessary if you have installed DOS or
Windows on a non-first hard disk, because they cannot boot any disks
except for the first one. The solution is to use the command

7
docs/user-ref.texi
View file

@ -758,10 +758,13 @@ grub> cat /etc/fstab
@end example
@end deffn
@deffn Command chainloader file
@deffn Command chainloader [@option{--force}] file
Load @var{file} as a chain-loader. Like any other file loaded by the
filesystem code, it can use the blocklist notation to grab the first
sector of the current partition with @samp{+1}.
sector of the current partition with @samp{+1}. If you specify the
option @option{--force}, then load @var{file} forcibly, whether it has a
correct signature or not. This is required when you want to load a
defective boot loader, such as SCO Unixware 7.1.
@end deffn
@deffn Command configfile @var{file}