us malware" into
the firmware of the USB stick that accepts data, returns "written"
to the writer, but doesn't actually write anything to its storage,
because... we need to protect the users! :-)
Rule:
If it stops you to do stupid things, it also stops you to d
not write a MBR from a file but I can from a md0?
To dd, a virtual node shouldn't be needed to operate on MBRs.
The if= and of= parameters will (should!) accept plain files
just like real devices.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mous
er, larger USB port. But
that doesn't mean you have to discard all your old
peripherals.
Source:
https://www.howtogeek.com/211843/usb-type-c-explained-what-it-is-and-why-youll-want-it/
I'm not sure I'll it... ;-)
--
Polytropon
Ma
n (or require
a run of fsck, or in case of "Windows", a kind of "repair" that
often leads to data loss and corrupted files).
Examining the USB traffic and checking for the CAM packets exchanged
between the device and the OS could help you find a way to implement
the impossibl
e: Something is still mounted, but it doesn't
exist anymore. Okay, umount -f, no damage done. But with read-write
media such as USB direct access storage... well... that looks much
more complicated.
That's why you alway unmount first, then wait, then disconnect.
Sorry I couldn't provide
