srmbootfat.sgml 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. <!DOCTYPE RefEntry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
  2. <refentry id="srmbootfat">
  3. <refmeta>
  4. <refentrytitle>srmbootfat</refentrytitle>
  5. <manvolnum>1</manvolnum>
  6. <refmiscinfo>srmbootfat</refmiscinfo>
  7. </refmeta>
  8. <refnamediv>
  9. <refname>srmbootfat</refname>
  10. <refpurpose>
  11. Linux/Alpha SRM boot block composer
  12. </refpurpose>
  13. </refnamediv>
  14. <refsynopsisdiv>
  15. <cmdsynopsis>
  16. <command>srmbootfat</command>
  17. <arg choice="plain">filesystem_image</arg>
  18. <arg choice="plain">boot_file</arg>
  19. </cmdsynopsis>
  20. </refsynopsisdiv>
  21. <!-- <refsect1><title>COPYRIGHT</title>
  22. <para>
  23. </para>
  24. </refsect1> -->
  25. <refsect1><title>DESCRIPTIONS</title>
  26. <para>
  27. <indexterm><primary>srmbootfat</primary></indexterm>
  28. This tool is a quick hack and is not supposed to exist in its present
  29. state for long.
  30. </para>
  31. <para>
  32. <application>Srmbootfat</application> finds <filename>boot_file</filename>
  33. in the root directory of the <acronym>FAT</acronym> file system stored in file
  34. <filename>filesystem_image</filename>
  35. and makes it bootable by writing the appropriate SRM boot block into the
  36. file system image file. This will work only on unpartitioned disks (such as
  37. floppies), because otherwise the boot block would need to be written into the
  38. partition table, which is outside the file system. However, a hard drive
  39. containing a FAT file system would most probably be partitioned using the PC
  40. partition table, which SRM cannot boot from anyway.
  41. </para>
  42. <para>
  43. The bootloader (<filename>boot_file</filename>)
  44. must be contiguous, i.e. occupy consecutive blocks.
  45. </para>
  46. </refsect1>
  47. <refsect1><title>ARGUMENTS</title>
  48. <para>
  49. <variablelist>
  50. <varlistentry><term><filename>filesystem_image</filename></term>
  51. <listitem><para>
  52. The name of the file containing a FAT file system image, e.g.
  53. <filename>/dev/fd0</filename>.
  54. </para></listitem></varlistentry>
  55. <varlistentry><term><filename>boot_file</filename></term>
  56. <listitem><para>
  57. The file name of the bootloader.
  58. </para></listitem></varlistentry>
  59. </variablelist>
  60. </refsect1>
  61. <!-- <refsect1><title>BUGS</title>
  62. <para>
  63. </para>
  64. </refsect1> -->
  65. <refsect1><title>AUTHOR</title>
  66. <para>
  67. Nikita Schmidt <email>cetus@snowball.ucd.ie</email>
  68. </para>
  69. </refsect1>
  70. <refsect1><title>SEE ALSO</title>
  71. <para>
  72. <application>aboot</application>(8), <application>mke2fs</application>(8), <application>e2writeboot</application>(8)
  73. </para>
  74. </refsect1>
  75. </refentry>