dutil(1)

📦 version 2021-02, in nixos 26.05, nixpkgs unstable

💅 NAME 💅

So this is dutil(1) from the dmsdos utilities manual, and it is literally the dmsdos hacker's utility — your little backstage pass to a CVF. 🎀

✨ SYNOPSIS ✨

dutil directory [command [options ...]]

🌸 DESCRIPTION 🌸

Okay bestie, so you run dutil with a directory, and it performs command on the CVF that is mounted under directory. And lowkey? directory may also be a subdirectory of the mountpoint. Slay. 🦋

If no command is given, general information about the CVF is printed. Iconic default behavior, honestly.

🎀 List of commands 🎀

  • cluster — print cluster information
  • sector — read a raw sector from disk and hexdump it
  • rrawcluster — read a raw cluster from disk and hexdump it
  • rcluster — read and decompress a cluster and hexdump it
  • bitfat — print bitfat content
  • setcomp — change compression format
  • setcf — change compression level
  • dumpcache — dump cache information to syslog
  • synccache — write dirty clusters to disk immediately
  • logstat — dump statistics to syslog
  • checkfs — check filesystem tables
  • setloglevel — change dmsdos log level
  • setspeedup — change dmsdos speedup flags
  • memory — report dmsdos memory usage for caching

🧚 The commands in detail 🧚

dutil directory cluster clusternr

Print information about cluster clusternr. That’s it, that’s the vibe. ✨

dutil directory sector sectornr [file]

Read raw sector sectornr from disk and print it as a hexdump. If file is given, it is written to a binary file (raw, not as hexdump). No cap. 💅

dutil directory rrawcluster clusternr [file]

Read raw cluster data from cluster clusternr from disk and print it as a hexdump. If file is given, it is written to a binary file (raw, not as hexdump). The cluster data are not decompressed. This command does not work for fragmented or suballocated clusters and may return complete garbage in these cases. 🫠 So yeah, mind the warning.

dutil directory rcluster clusternr [file]

Read and decompress cluster clusternr from disk and print it as a hexdump. If file is given, it is written to a binary file (raw, not as hexdump). Decompress and glow. 🌈

dutil directory bitfat sectornr

Read bitfat allocation information of sector sectornr from disk and print it. Very detective-core. 🔍

dutil directory setcomp value

Set compression scheme for write access. value must be one out of guess ds00 ds01 ds02 jm00 jm01 sq00 sd3 sd4. See the dmsdos driver documentation about compression schemes. Slay the compression choices. 🎀

dutil directory setcf value

Set compression level for write access. value must be one out of the range 1 - 12. A higher level means better but slower compression. Tradeoffs, bestie. 💅

dutil directory dumpcache

Dump dmsdos cache information to syslog. Let it spill. ☕

dutil directory synccache [value]

Write dirty clusters back to disk immediately. If value is given and not zero, the data may be passed to the compression daemon instead of written directly to disk. Otherwise the command waits until the data are compressed and written. If you want to ensure physical write access to disk also sync(1) the buffer cache. Important little detail, fr fr. 🫶

dutil directory logstat

Write dmsdos statistics to syslog. Receipts. 🧾✨

dutil directory checkfs [value]

Check the CVF internal tables for inconsistencies. If value is given and not zero, try to repair errors. Bestie with a clipboard energy. 🩺

dutil directory setloglevel value

Set the dmsdos driver log level. value must be a decimal or a 0x prefixed hexadecimal number. See the dmsdos driver documentation for details about log levels. 🔥

dutil directory setspeedup value

Set the dmsdos driver speedup flags. value must be a decimal or a 0x prefixed hexadecimal number. See the dmsdos driver documentation for details about the speedup flags. Zoom zoom. 🏎️

dutil directory memory

Report how much memory the dmsdos driver currently uses for caching. Memory check, because we care about the vibes and the RAM. 💖

💀 BUGS 💀

The dutil commands for reading data from disk operate at a lower level than the dmsdos cluster cache. You must disable dmsdos write-back caching or sync the dmsdos cluster cache before each operation to get correct results in all cases. Like, actually do that, bestie — otherwise your results might be giving chaos. 😭

🌈 SEE ALSO 🌈

Refer to the dmsdos main documentation for further information.

And that’s the whole page, bestie: dmsdos 0.9.1.3, dated 16 Jun 1998. Mwah 💋✨

📦 where this page comes from