befs.txt 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117
  1. BeOS filesystem for Linux
  2. Document last updated: Dec 6, 2001
  3. WARNING
  4. =======
  5. Make sure you understand that this is alpha software. This means that the
  6. implementation is neither complete nor well-tested.
  7. I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
  8. LICENSE
  9. =====
  10. This software is covered by the GNU General Public License.
  11. See the file COPYING for the complete text of the license.
  12. Or the GNU website: <http://www.gnu.org/licenses/licenses.html>
  13. AUTHOR
  14. =====
  15. The largest part of the code written by Will Dyson <will_dyson@pobox.com>
  16. He has been working on the code since Aug 13, 2001. See the changelog for
  17. details.
  18. Original Author: Makoto Kato <m_kato@ga2.so-net.ne.jp>
  19. His original code can still be found at:
  20. <http://hp.vector.co.jp/authors/VA008030/bfs/>
  21. Does anyone know of a more current email address for Makoto? He doesn't
  22. respond to the address given above...
  23. This filesystem doesn't have a maintainer.
  24. WHAT IS THIS DRIVER?
  25. ==================
  26. This module implements the native filesystem of BeOS http://www.beincorporated.com/
  27. for the linux 2.4.1 and later kernels. Currently it is a read-only
  28. implementation.
  29. Which is it, BFS or BEFS?
  30. ================
  31. Be, Inc said, "BeOS Filesystem is officially called BFS, not BeFS".
  32. But Unixware Boot Filesystem is called bfs, too. And they are already in
  33. the kernel. Because of this naming conflict, on Linux the BeOS
  34. filesystem is called befs.
  35. HOW TO INSTALL
  36. ==============
  37. step 1. Install the BeFS patch into the source code tree of linux.
  38. Apply the patchfile to your kernel source tree.
  39. Assuming that your kernel source is in /foo/bar/linux and the patchfile
  40. is called patch-befs-xxx, you would do the following:
  41. cd /foo/bar/linux
  42. patch -p1 < /path/to/patch-befs-xxx
  43. if the patching step fails (i.e. there are rejected hunks), you can try to
  44. figure it out yourself (it shouldn't be hard), or mail the maintainer
  45. (Will Dyson <will_dyson@pobox.com>) for help.
  46. step 2. Configuration & make kernel
  47. The linux kernel has many compile-time options. Most of them are beyond the
  48. scope of this document. I suggest the Kernel-HOWTO document as a good general
  49. reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
  50. However, to use the BeFS module, you must enable it at configure time.
  51. cd /foo/bar/linux
  52. make menuconfig (or xconfig)
  53. The BeFS module is not a standard part of the linux kernel, so you must first
  54. enable support for experimental code under the "Code maturity level" menu.
  55. Then, under the "Filesystems" menu will be an option called "BeFS
  56. filesystem (experimental)", or something like that. Enable that option
  57. (it is fine to make it a module).
  58. Save your kernel configuration and then build your kernel.
  59. step 3. Install
  60. See the kernel howto <http://www.linux.com/howto/Kernel-HOWTO.html> for
  61. instructions on this critical step.
  62. USING BFS
  63. =========
  64. To use the BeOS filesystem, use filesystem type 'befs'.
  65. ex)
  66. mount -t befs /dev/fd0 /beos
  67. MOUNT OPTIONS
  68. =============
  69. uid=nnn All files in the partition will be owned by user id nnn.
  70. gid=nnn All files in the partition will be in group nnn.
  71. iocharset=xxx Use xxx as the name of the NLS translation table.
  72. debug The driver will output debugging information to the syslog.
  73. HOW TO GET LASTEST VERSION
  74. ==========================
  75. The latest version is currently available at:
  76. <http://befs-driver.sourceforge.net/>
  77. ANY KNOWN BUGS?
  78. ===========
  79. As of Jan 20, 2002:
  80. None
  81. SPECIAL THANKS
  82. ==============
  83. Dominic Giampalo ... Writing "Practical file system design with Be filesystem"
  84. Hiroyuki Yamada ... Testing LinuxPPC.