lkml.org 
[lkml]   [1997]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectsome improvements for ncpfs on 2.0.33
Hi there,

being annoyed by some properties of the current ncpfs code, especially
that you cannot see whether a file is read-only or the inability to
rename read-only files, I decided to try to fix that.

This produced the following patch (for 2.0.33, some earlier kernels
should work, too) which:
a, displays the setting of a file's R-bit (read-only) as
inverse w protection bit, i.e. R-bit set -> w-bit not set,
R-bit not set -> w-bit set.
b, lets you change the R-bit with chmod
c, read-only files (R-bit set) can be renamed
d, read-only files can be deleted
e, fixes an off-by-1 bug in ncp_open_create_file_or_subdir
function (inside ncpfs).

Since c, and d, are rather dangerous (but more Unix-like :-) ), they
are enabled via a mount option. For this, ncpmount (from ncpfs-2.0.11
tools) was modified to provide that mount flag to the kernel.
If you specify "-s" when ncpmounting a file system, options c, and d,
are enabled.

So, ncpfs users, please try this out and give comments/suggestions.
If there is enough response I'll try to port it over to the 2.1.x line.

BTW, the last time I checked ncpfs on the 2.1.x (x around 63), ncpfs
didn't work for me. Has this changed already?

regards,
chris

[unhandled content-type:application/octet-stream]
[unhandled content-type:application/octet-stream]
\
 
 \ /
  Last update: 2005-03-22 13:40    [W:0.033 / U:0.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site