public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NCPFS flags all files executable on NetWare Volumes wit
Date: Fri, 27 Oct 2000 16:31:56 -0600	[thread overview]
Message-ID: <39FA025C.673118C8@timpanogas.org> (raw)
In-Reply-To: <B2D168F210B@vcnet.vc.cvut.cz>



Petr Vandrovec wrote:
> 
>
> 
> In kernel fs/ncpfs/ncplib_kernel.c, there is function named
> ncp_del_file_or_subdir() which does:
> 
> #ifdef CONFIG_NCPFS_NFS_NS
>   if (server->name_space[volnum] == NW_NS_NFS)
>   {
>     int result;
> 
>     result = ncp_obtain_DOS_dir_base(server, volnum, dirent, name, &dirent);
>     if (result) return result;
>     return ncp_DeleteNSEntry(server, 1, volnum, dirent, NULL, NW_NS_DOS,
>        htons(0x0680));

What wrong here is you have to read in each NS record (and the records
for the parent
file) and modify them.  You are just doing one and expecting the server
to do the work
of unlinking just the one.  You have to do each link yourself.  I will
fix.


>   }
>   else
> #endif
>     return ncp_DeleteNSEntry(server, 1, volnum, dirent, name,
>        server->name_space[volnum], htons(0x0680));
> 
> If you'll remove #ifdef-ed part, and you'll try to unlink some file
> using NFS namespace, server dies (on traditional filesystem, NSS works)
> with some internal inconsistency found error. Depending on search
> attributes (0x8006) passed to function, it either works only for directories
> (and abend for files), or works only for dirs (and refuses files), or
> does not work at all.
> 
>
> > 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.
> 
> It is possible when using DOS or OS/2 namespace. But as NFS namespace
> allows all byte sequences up to 255 chars for filename (excluding chars
> 0, '/' and names "." and "..")...

I have code that translates MAC to DOS, DOS to NFS, NFS to MAC, etc.  
You have to convert the
names using the tables in NWFS, file NWCREATE.C.  There are tables I use
to generate the 
MAC names from an NFS name using these tables of valid and invalid
characters for each
namespace.  I have to do it for all the server Namespaces, since Netware
can cross mount 
NWFS volumes created under Linux.

Jeff

>                                             Best regards,
>                                                 Petr Vandrovec
>                                                 vandrove@vc.cvut.cz
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-27 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 23:54 NCPFS flags all files executable on NetWare Volumes wit Petr Vandrovec
2000-10-27 22:31 ` Jeff V. Merkey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-27 22:18 Petr Vandrovec
2000-10-27 21:14 ` Jeff V. Merkey
2000-10-27 15:00 Petr Vandrovec
2000-10-27 16:57 ` Jeff V. Merkey
2000-10-27 17:11   ` Jeff V. Merkey
2000-10-27 19:46     ` Jeff V. Merkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39FA025C.673118C8@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox