Re: NFS - $ in directory names



Well, the information source for the website is created on a Windows
workstation, which stores this information on a Windows server. However,
for security/reliability reasons, my webserver of choice is WASD on a DS10L.
So, the PA is a "hot backup/test environment" and now that I have tested
NFS, I am happy to use that as the information source for both.

In other words, instead of ftping the data to the DS10L and PA, I can now
have the single source of information created and stored on the Windows
server but accessible by the DS10L (primary and live) and the PA (hot
backup/test) without having to move stuff around and without running into
the disk size limitation of the PA. The ability to create/export from the
DS10L is, for me, an unecessary extra step - I can now use the single data
source for everything.


"Wilm Boerhout" <w5OLD.PAINTboerhout@xxxxxxxxx> wrote in message
news:465f0b39$0$10881$ba620dc5@xxxxxxxxxxxxxxxxxxxxxx
on 30-5-2007 18:26 David J Dachtera wrote...
Gremlin wrote:
Hi Paul

Ah, thanks you - here I was thinking that I was so clever (not) because
I
told the Windows side to *not* preserve case, thinking that it would
either
just pass through as is, or at least let VMS make it uppercase - anyway,
time to hit the manual in more detail!!

I need to have it without the $ as I have decided to use a PersonalAlpha
run
as a backup to my webserver, but there is more data than will fit on the
PA
disk because of its "hobbyist" limitations, so NFS is the way to go.

How so? VMS is VMS is VMS is ... There is no "hobbyist version".

...unless the limitations are because you are running an Alpha emulator
and not
a real Alpha. Personal Alpha may have artificial limitations built into
it for
some perverted reason.

What limitation do you find in Personal Alpha? The tools supplied do not
allow you to *create* large disks, but I see no reason why you could not
create an arbitrary large container (on a real Alpha, using LD for
example) I would: create a large container on Alpha, $INIT/ERASE it, then
ZIP it on VMS, ftp it to Windows, unzip it and assign it to Personal
Alpha. 9Gb, 18GB, 36GB, if you have space to create it on your VMS system,
PA will be able to use it (constrained possibly only by the VMS version
you run on the virtual Alpha)

/Wilm


.



Relevant Pages

  • Re: Left in the dust?
    ... You'll find a very affordable Alpha box. ... but they aren't VMS or even VMS-like. ... reason: it was designed to be a command line OS. ... My wife is also blind and I've used Windows telnet with screen reading ...
    (comp.os.vms)
  • Re: Rookie on open VMS operating system
    ... The Alpha is just a microprocessor architecture: ... TRU64 unix and it supports Windows NT4. ... most current drives are supported by VMS. ... VMS also runs on a fourth platform: ...
    (comp.sys.dec)
  • Re: Alternative to FTP
    ... I have a flat text file that gets ftp'd out of our Alpha to a Windows ... Windows and VMS? ...
    (comp.os.vms)
  • Re: OT: Intel quad core X64 benchmarked
    ... VAX ran only VMS and a little Ultrix; Alpha lost Windows ... support, ended up with few Linux users, and Tru64 is going away. ...
    (comp.os.vms)
  • Re: Drag it to the trash...
    ... There might be a piece of software utility out there to help in finding and administering these "roaming profiles" for windows. ... A lot of MSDOS programmers entering into the VMS system schools abhorred vms at first, but later it sank in to just how flexible the system was designed to be. ... the so called installer is basically just a script that has been given priviledges to create files and directories, make changes to the system logical tables, and creating new aliases. ... in hardware to do all that. ...
    (comp.sys.mac.advocacy)