|
 |
f96e0b |
From 8d7ed36e113b21de18a1b4a2bf81d218d79114d2 Mon Sep 17 00:00:00 2001
|
|
|
f96e0b |
From: =?UTF-8?q?Gr=C3=A9goire=20Sutre?= <gregoire.sutre@gmail.com>
|
|
|
f96e0b |
Date: Wed, 1 Aug 2012 00:18:57 +0200
|
|
|
f96e0b |
Subject: [PATCH 018/482] Update manual NetBSD-wise.
|
|
|
f96e0b |
|
|
|
f96e0b |
---
|
|
|
f96e0b |
ChangeLog | 5 +++++
|
|
|
f96e0b |
docs/grub.texi | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--
|
|
|
f96e0b |
2 files changed, 67 insertions(+), 2 deletions(-)
|
|
|
f96e0b |
|
|
|
f96e0b |
diff --git a/ChangeLog b/ChangeLog
|
|
|
f96e0b |
index 01d4f92..b246d4e 100644
|
|
|
f96e0b |
--- a/ChangeLog
|
|
|
f96e0b |
+++ b/ChangeLog
|
|
|
f96e0b |
@@ -1,3 +1,8 @@
|
|
|
f96e0b |
+2012-07-31 Grégoire Sutre <gregoire.sutre@gmail.com>
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+ * docs/grub.texi: Note that NetBSD/i386 is Multiboot-compliant.
|
|
|
f96e0b |
+ (NetBSD): New subsection.
|
|
|
f96e0b |
+
|
|
|
f96e0b |
2012-07-22 Ales Nesrsta <starous@volny.cz>
|
|
|
f96e0b |
|
|
|
f96e0b |
* grub-core/bus/usb/ehci.c: PCI iter. - added PCI bus master setting.
|
|
|
f96e0b |
diff --git a/docs/grub.texi b/docs/grub.texi
|
|
|
f96e0b |
index b5954da..b0e7f59 100644
|
|
|
f96e0b |
--- a/docs/grub.texi
|
|
|
f96e0b |
+++ b/docs/grub.texi
|
|
|
f96e0b |
@@ -311,8 +311,10 @@ tables are also loaded.
|
|
|
f96e0b |
|
|
|
f96e0b |
@item Support non-Multiboot kernels
|
|
|
f96e0b |
Support many of the various free 32-bit kernels that lack Multiboot
|
|
|
f96e0b |
-compliance (primarily FreeBSD, NetBSD, OpenBSD, and
|
|
|
f96e0b |
-Linux). Chain-loading of other boot loaders is also supported.
|
|
|
f96e0b |
+compliance (primarily FreeBSD, NetBSD@footnote{The NetBSD/i386 kernel
|
|
|
f96e0b |
+is Multiboot-compliant, but lacks support for Multiboot modules.},
|
|
|
f96e0b |
+OpenBSD, and Linux). Chain-loading of other boot loaders is also
|
|
|
f96e0b |
+supported.
|
|
|
f96e0b |
|
|
|
f96e0b |
@item Load multiples modules
|
|
|
f96e0b |
Fully support the Multiboot feature of loading multiple modules.
|
|
|
f96e0b |
@@ -897,6 +899,7 @@ Here, we describe some caveats on several operating systems.
|
|
|
f96e0b |
@menu
|
|
|
f96e0b |
* GNU/Hurd::
|
|
|
f96e0b |
* GNU/Linux::
|
|
|
f96e0b |
+* NetBSD::
|
|
|
f96e0b |
* DOS/Windows::
|
|
|
f96e0b |
@end menu
|
|
|
f96e0b |
|
|
|
f96e0b |
@@ -997,6 +1000,63 @@ the size, run the command @command{uppermem} @emph{before} loading the
|
|
|
f96e0b |
kernel. @xref{uppermem}, for more information.
|
|
|
f96e0b |
|
|
|
f96e0b |
|
|
|
f96e0b |
+@node NetBSD
|
|
|
f96e0b |
+@subsection NetBSD
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+Booting a NetBSD kernel from GRUB is also relatively easy: first set
|
|
|
f96e0b |
+GRUB's root device, then load the kernel and the modules, and finally
|
|
|
f96e0b |
+run @command{boot}.
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@enumerate
|
|
|
f96e0b |
+@item
|
|
|
f96e0b |
+Set GRUB's root device to the partition holding the NetBSD root file
|
|
|
f96e0b |
+system. For a disk with a NetBSD disk label, this is usually the first
|
|
|
f96e0b |
+partition (a:). In that case, and assuming that the partition is on the
|
|
|
f96e0b |
+first hard disk, set GRUB's root device as follows:
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@example
|
|
|
f96e0b |
+grub> @kbd{insmod part_bsd}
|
|
|
f96e0b |
+grub> @kbd{set root=(hd0,netbsd1)}
|
|
|
f96e0b |
+@end example
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+For a disk with a GUID Partition Table (GPT), and assuming that the
|
|
|
f96e0b |
+NetBSD root partition is the third GPT partition, do this:
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@example
|
|
|
f96e0b |
+grub> @kbd{insmod part_gpt}
|
|
|
f96e0b |
+grub> @kbd{set root=(hd0,gpt3)}
|
|
|
f96e0b |
+@end example
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@item
|
|
|
f96e0b |
+Load the kernel using the command @command{knetbsd}:
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@example
|
|
|
f96e0b |
+grub> @kbd{knetbsd /netbsd}
|
|
|
f96e0b |
+@end example
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+Various options may be given to @command{knetbsd}. These options are,
|
|
|
f96e0b |
+for the most part, the same as in the NetBSD boot loader. For instance,
|
|
|
f96e0b |
+to boot the system in single-user mode and with verbose messages, do
|
|
|
f96e0b |
+this:
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@example
|
|
|
f96e0b |
+grub> @kbd{knetbsd /netbsd -s -v}
|
|
|
f96e0b |
+@end example
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@item
|
|
|
f96e0b |
+If needed, load kernel modules with the command
|
|
|
f96e0b |
+@command{knetbsd_module_elf}. A typical example is the module for the
|
|
|
f96e0b |
+root file system:
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@example
|
|
|
f96e0b |
+grub> @kbd{knetbsd_module_elf /stand/amd64/6.0/modules/ffs/ffs.kmod}
|
|
|
f96e0b |
+@end example
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+@item
|
|
|
f96e0b |
+Finally, run the command @command{boot} (@pxref{boot}).
|
|
|
f96e0b |
+@end enumerate
|
|
|
f96e0b |
+
|
|
|
f96e0b |
+
|
|
|
f96e0b |
@node DOS/Windows
|
|
|
f96e0b |
@subsection DOS/Windows
|
|
|
f96e0b |
|
|
|
f96e0b |
--
|
|
|
f96e0b |
1.8.2.1
|
|
|
f96e0b |
|