Re: NCPFS, anyone?
On Fri, 6 Sep 2002, Petr Vandrovec wrote:
> It should work, but only if you are using sparc binary on sparc kernel,
> or sparc64 binary on sparc64 kernel, otherwise sizeof(int), sizeof(long),
> sizeof(__kernel_uid_t) and other may differ between kernel and user. I have
> patch to ncpfs & kernel (2.5.x) to pass mount options through ASCII string,
> if you are interested.
bse:~/tmp> uname -a
Linux bse 2.4.19-pre9 #1 SMP Mon Jun 3 11:47:28 CEST 2002 sparc64 unknown
I have no idea how to specify the right user client on my Debian/Woody
system. Any idea?
> But before you'll try that, try first
> "ncpmount -S server -U rcb -A server -3 /mnt" and
bse:~/tmp> ncpmount -S WRS1 -U TilleA.USER.WR.RKI -A 10.15.140.41 -3 mnt
Logging into WRS1 as TILLEA.USER.WR.RKI
Password:
ncpmount: Invalid argument in mount(2)
> "ncpmount -S server -U rcb -A server -4 /mnt".
bse:~/tmp> ncpmount -S WRS1 -U TilleA.USER.WR.RKI -A 10.15.140.41 -4 mnt
Logging into WRS1 as TILLEA.USER.WR.RKI
Password:
ncpmount: Invalid argument in mount(2)
I'm not sure about the use of -A option because I never needed this on i386
hardware
> 2.4.x kernels should use mount version 4 (which allows for 32bit uid/gid),
> but if you'll look at arch/sparc64/kernel/sys_sparc32.c,
> do_ncp_super_data_conv, you'll find that this function (1) does not check
> version at all, (2) works only with -3 version, and (3) I do not see where
> this function actually copies unchanged members: version, ncp_fd, time_out,
> retry_count and flags... But if you'll rebuild ncpmount as a 64bit binary,
> problems should disappear without need to fix kernel.
Might be I'll do that. But I doubt that it will help much for my special
case because the machine in question will leave the Novell environment
to fullfill a different job. So it would just for academic reason ...
Kind regards
Andreas.
Reply to: