Ram-Disk on VxWorks
Danny Cohen
I created a RamDisk with dosFs it is called "E:".
I verify that it is created with the "devs" command.
-> devs
drv name
0 /null
1 /tyCo/0
1 /tyCo/1
5 diags:
7 /vio
3 E:
When I FTP the device, i reach the "diags" device which is the host-name.
How can i change the shell and FTP server to point to the target device?
1. how can i access "E:" device via FTP?
2. how can i access "E:" device via shell ("cwd", "ls"....)?
--
Regards.
Cohen Danny. dan...@harmonic.co.il
Harmonic Lightwaves
Tel: +972-4-6230150 ext 112
Mobile: +972-51-563413
Michael Lawnick
in ftp:
cd e:
on shell:
cd "e:"
HTH
Michael
"Danny Cohen" <dan...@harmonic.co.il> schrieb im Newsbeitrag
news:afa29t$kq0$1...@news.att.net.il...
Bill Pringlemeir
Danny> Hello all. I created a RamDisk with dosFs it is called "E:".
Danny> I verify that it is created with the "devs" command.
[snip]
Danny> When I FTP the device, i reach the "diags" device which is the
Danny> host-name. How can i change the shell and FTP server to point
Danny> to the target device? 1. how can i access "E:" device via
Danny> FTP? 2. how can i access "E:" device via shell ("cwd",
Danny> "ls"....)?
Why would you call it "E:"? [*] Why not call it something like
"/ramDisk1". I bet you use C++.
The main problem is the inability of the FTP server (and clients) to
handle the colon. I guess that some where along the line, some one
decided that any file with spaces, question mark, colon, or other
seemingly random data should be ignored. Also it is difficult to have
a file system when user pick weird device names.
I would suggest for your sanity that you call the ramdisk "/ramDisk"
or something like that. This is not an excuse for the FTP code... but
why do people insist on using `drive letters'.
Also look at the function ioLib and the function "ioDefPathSet". This
might help you as some FTP clients (ie, your PC) will have trouble
using drive letters.
You should be able to access the drive if you have an I/O system.
Type "ioHelp" from the shell prompt. Be very sure that you are
executing on the target. You might wish to prefix all shell commands
by `@' if you don't know what this means. Ie,
-> @ioHelp
hth,
Bill Pringlemeir.
[*] I suppose some people like to kiss for Bill Gate's colon.
--
You are not incomprehensible, because life is fair.
vxWorks FAQ, "http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html"
David Laight
> I would suggest for your sanity that you call the ramdisk "/ramDisk"
Or better "/ramdisk/" unless you want "/ramdiskefile" to be equivalent
to "/ramdisk/file".
Unfortunately that shows up a 'feature' [1] of the NFS server code
whereby if removes a trailing '/' from the wrong name.
So if you export "/fred/" you can mount "/fred//" but not "/fred/"
or "/fred" (but not from M$ - it will only issue a request for a
directory on the export list !)
David
[1] Not a bug because it is documented!