NCPFS flags all files executable on NetWare Volumes wit
Quoted 2 lines · Jeff V. Merkey
Here's the complete set of 3.x/4.x/5.x Namespace NCP calls with proper return codes. I'll run down the huge-data info and post a bit later.
Thanks. Main problem with hardlinks is that unlink through NFS namespace kills server (at least up to 5.0, I did not checked it during last few months), and unlink through DOS (or OS2) namespace removes all instances of hardlinked file :-( A bit unfortunate behavior.
Quoted 3 lines
let me know. I have a 600 page document I wrote two years ago that details every single NCP and NDS NCP used,
and can send it to you via UPS in .cz. It's too big to fax, or post.
Not for now.
Quoted 2 lines
2222/6804 Return Bindery Context (you need to implement this one
-- I did not see it in your code)
ncpfs 2.2.0.18 implements this (lib/ds/bindctx.c:NWDSGetBinderyContext), but does not use it itself...
Quoted 2 lines
2222/6805 Monitor NDS Connection (this one will allow you to
intercept NDS replica packets and suck an NDS replica local)
Novell documentation is a bit - hmm - unclear on this one...
Quoted 2 lines
2222/1631 Open Data Stream (this NCP will allow you to open the
MAC namespace data fork and read it remotely for MAC clients)
Userspace ncpfs (specifically ncopy) uses (lib/filemgmt.c:ncp_ns_open_create_entry) NCP 87,30 or 87,33 for this (and NW3.x is out of luck, AFAIK). Kernel code does not support MAC forks (and ACL and extended attributes), as up to now there is no vfs API for this... You have to use ncopy,nwdir/nwrights, nwtrustee,...,nwdir/eaops,nwdir for accessing MAC(&FTAM)/ACL/EAs for now. (for EAs you must have post-August 27 ncpfs, betas are on ftp://platan.vc.cvut.cz/private/ncpfs)
Thanks,
Petr Vandrovec [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Petr Vandrovec
Quoted 2 lines · Jeff V. Merkey
Here's the complete set of 3.x/4.x/5.x Namespace NCP calls with proper return codes. I'll run down the huge-data info and post a bit later.
Thanks. Main problem with hardlinks is that unlink through NFS namespace kills server (at least up to 5.0, I did not checked it during last few months), and unlink through DOS (or OS2) namespace removes all instances of hardlinked file :-( A bit unfortunate behavior.
Where are you doing this in the code? I'll go look at it and attempt a fix. It's killing the server because the linkage fields are probably not getting set. If NFSSERV is loaded, and the
links ever get hosed, you will get an Abend on 3.x and 4.x, and a "process suspended" error on 5.x (which also hangs the server). If the wrong pipe of fifo octals get set in mode,
it will also hang the server. If it is removing the entire namespace with hardlinks, it's
also because these linkage fields are not getting set properly. It does not work this way
with the NetWare NFSSERV.NLM mounted as an NFS client from Linux.
Quoted 9 lines
Quoted 4 lines
let me know. I have a 600 page document I wrote two years ago that details every single NCP and NDS NCP used,
and can send it to you via UPS in .cz. It's too big to fax, or post.Not for now.
Quoted 5 lines
Quoted 2 lines
2222/6804 Return Bindery Context (you need to implement this one
-- I did not see it in your code)ncpfs 2.2.0.18 implements this (lib/ds/bindctx.c:NWDSGetBinderyContext), but does not use it itself...
It should. It will allow you to use NDS with your existing code and NCP suite. I guess
doug's next project at TRG will be to put in NDS support in NCPFS and submit the patches to you.
Quoted 5 lines
Quoted 3 lines
2222/6805 Monitor NDS Connection (this one will allow you to
intercept NDS replica packets and suck an NDS replica local)Novell documentation is a bit - hmm - unclear on this one...
There's some undocumented diagnostic calls in NDS that basically render it totally unsuitable for the internet and make it easy to hack. It's great for LANs in an organization where the
servers can all be locked up, and employees can get fired for hacking. On the internet, it's
a piece of "swiss cheese" and is vulnerable in many respects.
Quoted 4 lines
Quoted 3 lines
2222/1631 Open Data Stream (this NCP will allow you to open the
MAC namespace data fork and read it remotely for MAC clients)
Quoted 8 lines
Userspace ncpfs (specifically ncopy) uses (lib/filemgmt.c:ncp_ns_open_create_entry) NCP 87,30 or 87,33 for this (and NW3.x is out of luck, AFAIK). Kernel code does not support MAC forks (and ACL and extended attributes), as up to now there is no vfs API for this... You have to use ncopy,nwdir/nwrights, nwtrustee,...,nwdir/eaops,nwdir for accessing MAC(&FTAM)/ACL/EAs for now. (for EAs you must have post-August 27 ncpfs, betas are on ftp://platan.vc.cvut.cz/private/ncpfs)
You can expose these as .files the way HFS likes to see them, and MAC clients to a Linux box
will be able to see and store their data in native MAC format -- with finder info.
Jeff
Quoted 7 lines
Thanks,
Petr Vandrovec [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/