Igor Kovalenko <firstname.lastname@example.org> wrote in message
There’s more to a usable backup software than just ‘cp’.
Then again, I don’t think it should be the OS vendor supplying the
I did not say that.
Sure you did. You said, “There’s more to a usable backup software that just
‘cp’.” - which implies that you believe we hold cp as some type of backup
system, which it isn’t.
But the OS vendor should be supplying useful interface
to backup devices. And QNX doesn’t. Kevin had to hack CAM layer to make
cdrecord work. My regards to him, but other people are not in the position
to do something like that. And it still is neither complete nor
Yep, I won’t argue that.
Tapes have no way to address them at all (it is funny how your header
define DCMDs for them, yet driver won’t create /dev entries). The whole
scheme of enumerating and addressing devices in QNX is a HORRIBLE MESS (I
fully prepared to elaborate on that).
While the enumeration process isn’t perfect, detecting devices over a wide
breadth of manufactures isn’t straightforward. One probe can have
detrimental effects on a piece of hardware. Not to mention the fact that
some hardware is just broken - but no one seems to complain loudly about
that. Inevitably, some ugly hack is put into a driver/enumeration to ‘play
nice’ and help the hardware recover.
Do you really expect any 3rd party vendor to support an OS like that?
While it’s not always an ideal environment, I don’t think it’s impossible -
‘just work around it’