makefloppies(8)

💾 makefloppies(8) — the floppy device node maker ✨

okay bestie, welcome to makefloppies, part of the System Manager's Manual gang. This is the page for MAKEFLOPPIES, and yes she's an 8th-section icon because she's touching your device nodes. buckle up 🎀

---

🌸 NAME 🌸

MAKEFLOPPIES — Creates the default floppy device nodes. that's it, that's the whole job. 💅

---

🦋 NOTE 🦋

okay so real talk first, because this is important and I'm not gonna let you get got:

This manpage has been automatically generated from fdutils's texinfo documentation.

and like… the process is only approximative. Some items — cross-references, footnotes and indices — are lost in this translation process. Fr fr, those things have no appropriate representation in the manpage format. Also? Only the items specific to each command got translated, and the general info about fdutils got dropped entirely for the manpage version. So the author strongly advises you to use the original texinfo doc. no cap. 🫶

so here's how you get the good version:

• To generate a printable copy from the texinfo doc, run the following commands:

./configure; make dvi; dvips fdutils.dvi

• To generate a HTML copy, run:

./configure; make html

A pre-made HTML can be found at: http://www.tux.org/pub/knaff/fdutils

• To generate an info copy (browsable using emacs' info mode), run:

./configure; make info

The texinfo doc looks most pretty when printed or as HTML. Indeed, in the info version certain examples are difficult to read due to the quoting conventions used in info. 😭 like the info version is giving "I woke up like this" but the quoting conventions said no. 💀

---

✨ DESCRIPTION ✨

MAKEFLOPPIES [-tlvng] [drives]

The MAKEFLOPPIES shell script creates the new floppy block device node. She's not doing it alone though — she uses the floppycontrol program to translate the minor device numbers into meaningful names 👑. And she also uses those names to decide whether to create a given block device file or not, depending on the type of the physical drive. Like, for instance? For a 3 1/2 drive, the formats corresponding to a 5 1/4 drive are not created. she knows the vibe check and she's not making files that don't belong. 🧚

If you have more than two floppy drives, you need to tell the kernel the CMOS types of those additional drives using the floppy=drive,type,cmos lilo option. bestie the kernel does not read minds. 🫠

If the drives parameter is given, only the device nodes for the listed drives are made. By default, all only the two first drives are tried.

MAKEFLOPPIES does not work if you redefine your default formats.

Caution: MAKEFLOPPIES removes already existing floppy device nodes. 🔥 like she said "makeover" and she MEANT it. existing nodes? gone. be so serious about this one, back stuff up, know what you're doing, periodt.

---

🎀 OPTIONS 🎀

• -t — Use the old naming convention for 3 1/2 devices (e.g. `fd0H720' instead of `fd0u720'). throwback era, vintage core. 💜
• -m — Base the name for the created devices on the type of the media (e.g. `fd0h720' instead of `fd0u720'). it's giving "name her after the media, not the drive" 🌸
• -l — Local. Creates device nodes in the local directory, not /dev. staying home today 🏠
• -v — Verbose. she will talk. 🗣️✨
• -n — Dry run. (just report what would be done, do not do anything). the "tell me your plans but don't touch anything" option, iconic honestly 🙈
• -g — Group. Allow read/write access to floppy devices only for group floppy. 🫶

---

💀 BUGS 💀

The MAKEFLOPPIES script does not work on redefined "default" formats, If you redefine default formats, you need to create the needed device nodes manually. 😭 like girl cannot handle your custom defaults, you're on your own for those, get in there and make them by hand.

---

🌈 SEE ALSO 🌈

Fdutils' texinfo doc — go read it, that's the main character of this whole situation ⭐

---

and that's a wrap on makefloppies(8) from fdutils-5.6, dated 27Jan21 💖 thank you for coming to my TED talk, go forth and make your floppy device nodes responsibly, love u, bye bestie 💅✨🎀