summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorphk <phk@FreeBSD.org>1999-11-10 10:50:51 +0000
committerphk <phk@FreeBSD.org>1999-11-10 10:50:51 +0000
commit942fabe617ea02690dd3bdbc22959b3ac94a843f (patch)
tree0e9d0cda48b7ef6c4265e5a0499bff5285a9151e
parent802a7ce1af1cbfe9cd7303465dd692b34365ae4c (diff)
downloadFreeBSD-src-942fabe617ea02690dd3bdbc22959b3ac94a843f.zip
FreeBSD-src-942fabe617ea02690dd3bdbc22959b3ac94a843f.tar.gz
Finding root devices is a much more sane thing now.
-rw-r--r--sys/contrib/dev/fla/README15
1 files changed, 8 insertions, 7 deletions
diff --git a/sys/contrib/dev/fla/README b/sys/contrib/dev/fla/README
index 413e97d..78433de 100644
--- a/sys/contrib/dev/fla/README
+++ b/sys/contrib/dev/fla/README
@@ -46,15 +46,16 @@
[6] How to boot from a fla device ?
- The FreeBSD kernel recognizes the root device using various
- hacks. These hacks doesn't recognize the fla device so some
- "real" hacks are needed to boot from your fla device.
+ FreeBSD 4.0 and forward find their root device by reading
+ the /etc/fstab, so the DiskOnChip devices will work just
+ like any other device.
- In 4.0 current the easiest way is to configure your kernel with
- the
- options ROOTDEVNAME=\"fla0\"
+ Earlier FreeBSD kernels recognizes the root device using
+ various hacks. These hacks doesn't recognize the fla device
+ so some "real" hacks are needed to boot from your fla
+ device.
- In older versions, specifying the boot device in the kernel
+ In pre 4.0 versions specifying the boot device in the kernel
config file this way is the easiest way to do it:
config kernel root on major 28 minor 65538
OpenPOWER on IntegriCloud