Yeah if that triggers a bug then the kernel or drive is barely functioning, neither of the two should care what data you write and it’s getting tested all the time as compressed data is indistinguishable from random data.
You could certainly confuse something in /dev that takes actual commands, but say spinning fans randomly won’t do much, and neither crashing the fan controller the firmware will still shut the system down before it melts itself.
But if you have, dunno, an old plotter hooked up to /dev/lp0 and it’s directly interpreting every random number on there as a movement command you might overheat the mechanism and set it on fire.
Yeah if that triggers a bug then the kernel or drive is barely functioning, neither of the two should care what data you write and it’s getting tested all the time as compressed data is indistinguishable from random data.
You could certainly confuse something in /dev that takes actual commands, but say spinning fans randomly won’t do much, and neither crashing the fan controller the firmware will still shut the system down before it melts itself.
But if you have, dunno, an old plotter hooked up to /dev/lp0 and it’s directly interpreting every random number on there as a movement command you might overheat the mechanism and set it on fire.