Target is busy

FOSS developers, especially Linux and especially its kernel developers have become famous for setting false targets. The error message 'Target is busy' must be the epitome of that: wrong priorities everywhere.

Dudes, I will finally break it to you because nobody else did: when I as the owner and administrator of a system order a mounted drive to be unmounted, that is a direct order from the only authority that is in control of the system. I and only I make decisions here, in the form of -f argument by way of which I tell umount that I, root, command it to unmount it regardless of anyone else's considerations. But Linux developers deem themselves above all and refuse.

That is a false target. That is a wrong priority. Their concern that some software that keeps open handles to that mount may become upset is void and nil. By issuing the force command line argument as root I communicate my unconditional order to surrender, an ultimatum that must be followed.

The system is already dead. The mounted volume is already unresponsive. No one guarantees anything. There is no support, no venue for complaints, no contract. I am on my own.

What do you think I am going to do next? Right! The reboot. But it may also fail to commence gracefully because of a dead share/zombie processes.

So? False targets set by Linux developers do not do much.

All hat, no cattle.

Posted by: LinuxLies at 07:28 AM | No Comments | Add Comment
Post contains 247 words, total size 1 kb.