minix/drivers/memory/ramdisk
Thomas Veerman b47483433c Added a hack to start binaries from the boot image only. In particular, setting
bin_img=1 in the boot monitor will make sure that during the boot procedure the
mfs binary that is part of the boot image is the only binary that is used to
mount partitions. This is useful when for some reason the mfs binary on disk 
malfunctions, rendering Minix unable to boot. By setting bin_img=1, the binary
on disk is ignored and the binary in the boot image is used instead.

- 'service' now accepts an additional flag -r. -r implies -c. -r instructs RS
  to first look in memory if the binary has already been copied to memory and
  execute that version, instead of loading the binary from disk. For example,
  the first time a MFS is being started it is copied (-c) to memory and
  executed from there. The second time MFS is being started this way, RS will
  look in memory for a previously copied MFS binary and reuse it if it exists.
- The mount and newroot commands now accept an additional flag -i, which
  instructs them to set the MS_REUSE flag in the mount flags.
- The mount system call now supports the MS_REUSE flag and invokes 'service'
  with the -r flag when MS_REUSE is set.
- /etc/rc and the rc script that's included in the boot image check for the
  existence of the bin_img flag in the boot monitor, and invoke mount and 
  newroot with the -i flag accordingly.
2009-08-18 11:36:01 +00:00
..
bintoc.c Initial root filesystem is now on a ramdisk that is part of the image. 2006-02-15 11:18:21 +00:00
Makefile don't call mkdep with an absolute path 2007-02-08 16:26:20 +00:00
mtab Initial root filesystem is now on a ramdisk that is part of the image. 2006-02-15 11:18:21 +00:00
proto bigger ramdisk for bigger binaries 2009-01-09 17:47:18 +00:00
proto.sh Merge of VFS by Balasz Gerofi with Minix trunk. 2006-10-25 13:40:36 +00:00
rc Added a hack to start binaries from the boot image only. In particular, setting 2009-08-18 11:36:01 +00:00