public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Urban Widmark <urban@teststation.com>
Cc: <davem@redhat.com>, <jj@sunsite.ms.mff.cuni.cz>,
	<davidm@hpl.hp.com>, <schwidefsky@de.ibm.com>,
	<engebret@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] 64bit archs doing incorrect magic for smbfs?
Date: Mon, 22 Apr 2002 15:31:47 +0200	[thread overview]
Message-ID: <3187FEB377F@vcnet.vc.cvut.cz> (raw)

On 21 Apr 02 at 12:37, Urban Widmark wrote:
> 
> For smbfs the data part is now often sent as a normal ascii string (when
> using samba 2.2.0+) and should then not be modified at all. ncpfs defines
> two different formats (v3 and v4), don't know if both are used.

If you have recent (2.2.0.18/2.2.0.19) ncpfs, format v4 is used (it allows
for 32bit uid/gid). I have no non-ia32 test environment, so if anybody finds 
that ncpfs does not work on any platform, feel free to send patches either 
to me or to arch maintainers...
 
> Untested patch vs 2.4.19-pre7-ac2 below adds version number checks for the
> smbfs case (yes, it handles the ascii format too). Similar changes are
> needed in 2.5.

I plan using ASCII format too, but it is not high enough on my TODO list.
If it will make life for Al or other architectures easier, I'll do it
sooner...
                                            Petr Vandrovec
                                            vandrove@vc.cvut.cz

             reply	other threads:[~2002-04-22 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 13:31 Petr Vandrovec [this message]
2002-04-22 19:50 ` [patch] 64bit archs doing incorrect magic for smbfs? Urban Widmark
  -- strict thread matches above, loose matches on Subject: below --
2002-04-21 10:37 Urban Widmark
2002-04-21 10:31 ` David S. Miller

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=3187FEB377F@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=engebret@us.ibm.com \
    --cc=jj@sunsite.ms.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=urban@teststation.com \
    /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