From f72ab14e4a57b823b0d4dfefa78a33477ab05b66 Mon Sep 17 00:00:00 2001
From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
Date: Thu, 10 Oct 2013 09:44:19 +0200
Subject: [PATCH] 	* docs/grub.texi: Document disk names used on Windows
 and AROS.

---
 ChangeLog      |  4 +++
 docs/grub.texi | 74 +++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 77 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index f64132d44..6254963e7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2013-10-10  Vladimir Serbinenko  <phcoder@gmail.com>
+
+	* docs/grub.texi: Document disk names used on Windows and AROS.
+
 2013-10-10  Vladimir Serbinenko  <phcoder@gmail.com>
 
 	* grub-core/osdep/aros/getroot.c: Change to //: prefix as discussed
diff --git a/docs/grub.texi b/docs/grub.texi
index a97ede329..fe577aabc 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -81,6 +81,9 @@ This edition documents version @value{VERSION}.
 @menu
 * Introduction::                Capturing the spirit of GRUB
 * Naming convention::           Names of your drives in GRUB
+* OS-specific notes about grub tools:: 
+                                Some notes about OS-specific behaviour of GRUB
+                                tools
 * Installation::                Installing GRUB on your drive
 * Booting::                     How to boot different operating systems
 * Configuration::               Writing your own configuration file
@@ -538,6 +541,75 @@ completion works with file names, too.
 That was easy, admit it. Now read the next chapter, to find out how to
 actually install GRUB on your drive.
 
+@node OS-specific notes about grub tools
+@chapter OS-specific notes about grub tools
+
+On OS which have device nodes similar to Unix-like OS GRUB tools use the
+OS name. E.g. for GNU/Linux:
+
+@example
+# @kbd{grub-install /dev/sda}
+@end example
+
+On AROS we use another syntax. For volumes:
+
+@example
+//:<volume name>
+@end example
+
+E.g.
+
+@example
+//:DH0
+@end example
+
+For disks we use syntax:
+@example
+//:<driver name>/unit/flags
+@end example
+
+E.g.
+
+@example
+# @kbd{grub-install //:ata.device/0/0}
+@end example
+
+On Windows we use UNC path. For volumes it's typically
+
+@example
+\\?\Volume{<GUID>}
+\\?\<drive letter>:
+@end example
+
+E.g.
+
+@example
+\\?\Volume{17f34d50-cf64-4b02-800e-51d79c3aa2ff}
+\\?\C:
+@end example
+
+
+For disks it's
+
+@example
+\\?\PhysicalDrive<number>
+@end example
+
+E.g.
+
+@example
+# @kbd{grub-install \\?\PhysicalDrive0}
+@end example
+
+Beware that you may need to further escape the backslashes depending on your
+shell.
+
+When compiled with cygwin support then cygwin drive names are automatically
+when needed. E.g.
+
+@example
+# @kbd{grub-install /dev/sda}
+@end example
 
 @node Installation
 @chapter Installation
@@ -584,7 +656,7 @@ For example, under Linux the following will install GRUB into the MBR
 of the first IDE disk:
 
 @example
-# @kbd{grub-install /dev/hda}
+# @kbd{grub-install /dev/sda}
 @end example
 
 Likewise, under GNU/Hurd, this has the same effect: