> This seems to be related to the change to UUID's... which are about the only sensible way to enumerate disks on large systems, especially when you are arranging arrays with multiple paths.
mdadm and dm-multipath *need* to give a disk some sort of id to be able to cope with not trashing your large multi terabyte tunes collection:-)
I ran across this problem last year when speccing up for marine software. All the nautical ones (for non SOLAS anyway) were windows based, Sure if you have a nice integrated bridge system it'll be some flavour of *NIX, but not joe average.
One of the hassles (certainly for UK) is that ARCS (the admiralty raster charts) are _very_ expensive. oh, and dongle protected...
Slashdot Mirror
And he had the cheek to move the PHP script that controlled his X10 lighting (cron is a wonderful annoyance tool...)
> This seems to be related to the change to UUID's ... which are about the only sensible way to enumerate disks on large systems, especially when you are arranging arrays with multiple paths.
:-)
mdadm and dm-multipath *need* to give a disk some sort of id to be able to cope with not trashing your large multi terabyte tunes collection
The IBM RPM's for TSM work fine under debian
.debs and did a dpkg -i ...
/home from a debian stable system seems fine
I used "alien" to convert to
Admittedly our TSM server is a large AIX box, but backing up
Buffer overflow anybody?
I ran across this problem last year when speccing up for marine software. All the nautical ones (for non SOLAS anyway) were windows based, Sure if you have a nice integrated bridge system it'll be some flavour of *NIX, but not joe average.
One of the hassles (certainly for UK) is that ARCS (the admiralty raster charts) are _very_ expensive. oh, and dongle protected...