summaryrefslogtreecommitdiff
path: root/microkernel
diff options
context:
space:
mode:
authorAndrew Engelbrecht <sudoman@ninthfloor.org>2011-08-04 21:56:40 -0400
committerAndrew Engelbrecht <sudoman@ninthfloor.org>2011-08-04 21:56:40 -0400
commit6ac278617dd6e5801577dc35cd9738579ecce8cb (patch)
tree82a8bf8f4ccfde7caeca5bdcea3790807d3d3963 /microkernel
parentef0baf74357b7db4c094c5103e3d17599f46b6d1 (diff)
gnumach/build: expanded backup and install
Diffstat (limited to 'microkernel')
-rw-r--r--microkernel/mach/gnumach/building.mdwn15
1 files changed, 11 insertions, 4 deletions
diff --git a/microkernel/mach/gnumach/building.mdwn b/microkernel/mach/gnumach/building.mdwn
index ecaae7f8..24a73608 100644
--- a/microkernel/mach/gnumach/building.mdwn
+++ b/microkernel/mach/gnumach/building.mdwn
@@ -95,7 +95,14 @@ Optionally run the (tiny) test suite:
$ make check
-The resulting kernel binary can now be moved into place (just copy
-`gnumach.gz`, typically to `/boot/gnumach.gz`), so you can boot your system
-with the new kernel. It is a good idea to make a backup of the previously
-installed binary, in case you need to recover.
+It's a good idea to make a backup of the previously installed kernel, in case
+you can't boot using the new one. That way, you can restore it after booting
+from a rescue media (or mounting the disk image used by your vm).
+
+ # cp /boot/gnumach.gz /boot/gnumach.gz.bak
+
+GNU Mach can now be moved into place, typically `/boot/gnumach.gz`, so that you
+can boot your system with the new kernel.
+
+ # cp gnumach.gz /boot
+