aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorhpa <hpa>2004-12-21 22:36:29 +0000
committerhpa <hpa>2004-12-21 22:36:29 +0000
commit8db502c28e8d3d076c834762b95c62ec501574fc (patch)
tree72bbdcfc0cf80a292d00f2184d2b7d7551cfd853
parent6eb3c5e7ade4e74c5446d1a0776c0f49c7072d07 (diff)
downloadsyslinux-8db502c28e8d3d076c834762b95c62ec501574fc.tar.gz
syslinux-8db502c28e8d3d076c834762b95c62ec501574fc.tar.xz
syslinux-8db502c28e8d3d076c834762b95c62ec501574fc.zip
Document the need/lack thereof to run the installer.
-rw-r--r--extlinux.doc11
1 files changed, 11 insertions, 0 deletions
diff --git a/extlinux.doc b/extlinux.doc
index 54e649d1..502cfc0c 100644
--- a/extlinux.doc
+++ b/extlinux.doc
@@ -54,3 +54,14 @@ preferred way to boot is:
- Run "extlinux /boot" to install extlinux. This will install it on
all the drives in the RAID-1 set, which means you can boot any
combination of drives in any order.
+
+
+
+It is not required to re-run the extlinux installer after installing
+new kernels. If you are using ext3 journalling, however, it might be
+desirable to do so, since running the extlinux installer will flush
+the log. Otherwise a dirty shutdown could cause some of the new
+kernel image to still be in the log. This is a general problem for
+boot loaders on journalling filesystems; it is not specific to
+extlinux. The "sync" command does not flush the log on the ext3
+filesystem.