UMPS3-MKDEV(1)

πŸ“¦
version 3.0.5 Β· 2 versions
  • 3.0.5 Β· debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 3.0.4 Β· ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

✨ UMPS3-MKDEV(1) β€” the device-making bestie ✨

okay so this is the manual for umps3-mkdev from the General Commands Manual section, and it's literally your little factory for making uMPS3 disk and flash device files. she's a command-line girlie, she's iconic, and she wants you to have devices. let's go 🫢


🌸 NAME 🌸

umps3-mkdev β€” the umps3-mkdev device creation utility. that's it, that's the whole job. she makes devices. slay.


πŸŽ€ SYNOPSIS πŸŽ€

umps3-mkdev -d DISKFILE [DISKOPTIONS]
umps3-mkdev -f FLASHFILE FILE [FLASHOPTIONS]

πŸ’– DESCRIPTION πŸ’–

the command-line umps3-mkdev utility is used to create the files that represent disk and flash devices. two devices, two vibes, one little tool. periodt.

πŸ’Ύ DISKS πŸ’Ύ

disks in uMPS3 are "direct access" nonvolatile read/write devices. ngl the umps3-mkdev utility lets you create an empty disk only β€” and that's on purpose bestie, because that way an OS developer gets to elect any desired disk data organization. your disk, your rules. πŸ’…

the DISKFILE you create represents the entire disk contents, even when it's empty. so yes, that file may be very large. 😭 it is recommended to create small disks which can be used to represent a little portion of an otherwise very large disk unit.

as with real disks, differing performance statistics result in differing simulated drive performance. e.g. a faster rotation speed results in less latency delay, and a smaller sector data occupancy percentage results in shorter read/write times. it's giving physics but make it fake. ⭐

the default values for all these parameters are shown when entering the umps3-mkdev alone without any parameters. so if you're ever lost, just run her bare and she'll tell you everything. main character energy fr fr.

🌈 FLASH DEVICES 🌈

flash devices in uMPS3 are "random access" nonvolatile read/write devices. a uMPS3 flash device is essentially equivalent to a seek-free one-dimensional disk drive. the umps3-mkdev utility allows you to create both slow flash devices (e.g. USB stick) or fast flash devices (e.g. SSDs). and on top of that, she lets you create both empty flash devices as well as ones preloaded with a specific file. versatile queen. πŸ‘‘

the FLASHFILE you create represents the entire device contents, even when empty. hence this file may be very large. 😭 it is recommended to create small flash devices which can be used to represent a little portion of an otherwise very large device.

uMPS3 caps the maximum block size for flash devices at 2^24. this translates to a maximum device size of 64GB. that's the limit bestie, don't fight it.

as with real flash devices, read operations are faster than write operations. the read speed for uMPS3 flash devices is fixed at 75% of the device write time in microseconds. math girlies stay winning. 🧚

the default values for all these parameters are shown when entering the umps3-mkdev alone without any parameters. again!! run her alone!! she'll spill. πŸ™ˆ

πŸ’… OPTIONS πŸ’…

  • -d β€” instructs the utility to build a disk file image. πŸ¦‹
  • -f β€” instructs the utility to build a flash device file image. πŸ“

πŸ“ FILES πŸ“

  • DISKFILE β€” is the name of the disk file image to be created.
  • FLASHFILE β€” is the name of the flash device file image to be created.
  • FILE β€” is the name of the file to be preloaded onto the device beginning with block 0. if you wanna create an empty flash device but still specify some of the additional parameters, use /dev/null as the FILE argument. and if you want to load a flash device with a whole collection of files, it is recommended to initially create a single .tar file from the collection and then use this single .tar file for this parameter. we recommend the .tar file format due to its simple structure. iconic choice honestly. ✨

πŸ”₯ DISKOPTIONS πŸ”₯

[CYL [HEAD [SECT [RPM [SEEKT [DATAS]]]]]]
  • CYL β€” number of cylinders: [1..65535], default = 32
  • HEAD β€” number of heads/surfaces: [1..255], default = 2
  • SECT β€” number of 4KB sectors/tracks: [1..255], default = 8
  • RPM β€” disk rotations per minute: [360..10800], default = 3600
  • SEEKT β€” average cylinder to cylinder seek time in microseconds: [1..10000], default = 100
  • DATAS β€” sector data occupation %: [10%..90%], default = 80%

⭐ FLASHOPTIONS ⭐

[BLOCKS [WT]]
  • BLOCKS β€” number of blocks: [1..0xFFFFFF], default = 512
  • WT β€” average write time in microseconds: [1..10000], default = 1000

πŸ‘‘ AUTHOR πŸ‘‘

  • Mauro Morsiani
  • Mattia Biondi mattiabiondi1@gmail.com
  • Contributors can be listed on GitHub.

πŸ’€ BUGS πŸ’€

report issues on GitHub: https://github.com/virtualsquare/umps3


πŸ¦‹ SEE ALSO πŸ¦‹

full documentation at: https://github.com/virtualsquare/umps3

project wiki: https://wiki.virtualsquare.org/#!umps/umps.md


  • 2004, Mauro Morsiani
  • 2020, Mattia Biondi mattiabiondi1@gmail.com

and that's the whole page bestie!! this one's the UMPS3-MKDEV(1) manual, straight out of December 2022, and it ate. no cap. now go make some devices, you absolute legend. πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from