Installing the NT version of SOSS should consist of merely going into the
exe directory and executing runsoss.bat.  The list of exported filesystems
is contained in the export.us file.  If you look at runsoss.bat, it sets
the TZ (timezone) variable, which you will want to adjust for your location.
You'll also see that it sets the NFSDEBUG value, which enables some
error messages.  Setting NFSDEBUG to "all" will enable lots of output,
very useful for debugging.

When you mount something from unix, BE SURE to limit the read and
write requests to 1024, with a command (under System V) like:

   mount -f NFS,intr,rsize=1024,wsize=1024 ntmachine:/c /usr/ntmachine_c

You can put the rsize=1024,wsize=124 options in /etc/fstab under SunOS.

The inode.dmp file (in the exe directory, or wherever you run soss from)
contains the list of inodes, which can sometimes get corrupted.
To get a clean start, make sure the filesystem is unmounted
on the UNIX side, then remove the inode.dmp file, and then start soss.

This program assumes that you've got TCP/IP working,
and that you have the host names properly entered in
winnt\system\drivers\etc\hosts, and that the UNIX side has the
proper stuff in its hosts and fstab file.



--------------------

New stuff. see src dir for more.

The software I build has the following specs.:
    Based on SOSSNT
Plus
    NTFS filename support, up to 256 bytes, case insensitive,
    but with case preservation.

    NTFS security mapping, 
        Owner -> Unix User id
        Group -> Unix group id, first matching group out of
            "group" file
        Group -> Unix world, first matching group out of
            "world" file, ie "Everyone"
    
    The matching works as follows:
        The permissions on a file/dir are checked against the
        groups in the group/world file, the first match get's 
        mapped.
        A file should only have one mapped group-> unix group
        and one mapped group to unix world.
 
    The admin must provide for files:
        export.us for export directories and hosts
        user      NT user name -> unix id mapping
        group     NT group name -> unix id
        world     NT group name -> unix world access

Restrictions:
1. Security validations is partly left to the client NFS module, works with our
    SUn network.
2. Chgrp will not work if there is no mapped group already in the permissions
          of the file/dir
3. Owner/Group/Access rights and all map-files are cached.
    If you change them, ie access rights for mapped groups on a file which
    has been accessed by the NFS client, these changes won't take effect
    until the file is not cached any more, or the NFS server has been
     restarted.
4. The source code for the NTFS security will not be provided, they are
    propriatry.


Every user who is satisfied, might wish to donate to a charity organisation
of his choice, not to myself.
This is on voluntary basis and will not be controlled.
I offer to publish donations in appropiate user groups.

Ralf

