Re: Moving From ProTools to Linux? Good or bad?



"Randy Yates" wrote...
(Scott Dorsey) writes:
VMS had some good points and some bad points.... the heavyweight
filesystem
was a great thing for commercial applications because the filesystem
itself
did all the database work. On the other hand, it was a pain in the neck
for scientific computing because you would generate a text file and it
would be variable length record or maybe fixed-length-null-padded or
maybe
stream_lf or maybe some other format. And when you FTP'ed it to another
machine it would be a still different format on the other end.

FTP? You didn't need to FTP. VMS had the ability to access files
from other systems with the node::device syntax:

node::device:[root.][directory-name]filename.type;version

Yeah, as long as you were working VAX to VAX. Once you left
DEC-land it wasn't quite so seamless. I had to develop some
rather arcane software to get data from my lab HP network onto
the big ethernet "thick-LAN" and into the VAX where it could
be data-warehoused and analyzed.

Not exactly related anecdote:

When the corp IT organization was just getting started, they didn't
have any servers on our campus to host the cc:Mail databases :-((
So we created some file shares on one of our VAXen to host their
stuff. They played pretty fast and loose in those days (they are a little
better today) and would re-boot a server just to see if it would fix a
problem (who cares if any users have files open, etc.!)

So one day someone from the corp IT help-desk calls me and says
"We're having a problem with the ALCCM03 database. It is hosted
on one of your VAXes, can you reboot it for us?" I responded as
deadpan as I could manage: "The fab-support servers aren't scheduled
for a re-boot until the Christmas warm-down. Would you like to hold?"
(it was mid-May). They choked and said, no, they would think of
some other way to resolve their problem.





.



Relevant Pages

  • Re: Image storage - db vs filesystem (again)
    ... the table, and not make the same change to the filesystem, or vice-versa? ... Remember that even if you store the image in the database, ... that's a massive single backup task. ... servers, you have backup of the actual file data via redundancy (and you can ...
    (microsoft.public.sqlserver.programming)
  • Re: distributed php
    ... Session data is by default kept in a filesystem, not a database. ... servers, sometimes physically distributed around the country. ...
    (comp.lang.php)
  • Re: reiser4 plugins
    ... > an entire new storage array and this wasn't/isn't cheap. ... > following versions of an article; reduced the database by 85%). ... So a filesystem with intelligent ... Any "unnecessary double work" would squarely be within ReiserFS... ...
    (Linux-Kernel)
  • Re: [RFC] Linux Kernel Subversion Howto
    ... - you only have a filesystem that supports 8.3 file names, ... This was the clever trick I alluded to. ... > why aren't you telling Oracle to disclose how Oracle works inside? ... stored in the database for itself, ...
    (Linux-Kernel)
  • Re: [PHP] Re: how to display images stored in DB
    ... To follow up with Ted, nobody said using the filesystem is bad, ... many of us are saying is that the database is not necessarily bad ... Think of the UNIX file systems, ... he argues in favour of the irrefutability of his argument only needs one ...
    (php.general)