public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Scott A. Sibert" <kernel@hollins.edu>
To: Urban Widmark <urban@teststation.com>
Cc: linux-kernel@vger.kernel.org, vt <vt@vt.fermentas.lt>,
	vda@port.imtp.ilyichevsk.odessa.ua
Subject: Re: 2.5.11 and smbfs
Date: Fri, 03 May 2002 10:39:06 -0400	[thread overview]
Message-ID: <3CD2A10A.2010306@hollins.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0205011842001.1885-100000@cola.enlightnet.local>

Hi all.

Kernel 2.4.18 smbfs worked, 2.4.19-pre8 smbfs worked (although 
fs/ufs/super.c had some missing commas), 2.5.11 smbfs didn't work.  The 
RedHat 7.2 had samba-2.2.1a-4 so I pulled down samba-2.2.3a-4 from the 
skipjack beta and compiled it under kernel 2.5.11 and it mounts windows 
shares correctly.  I'm in the process of going to 2.5.13 but I'm going 
to stick with the 2.2.3a-4 samba.

Thanks for all of your help.

--Scott

Urban Widmark wrote:

>On Tue, 30 Apr 2002, Scott A. Sibert wrote:
>
>>I can mount other samba shares fine (ie. Samba-2.2.2 from OSX 10.1.4 and 
>>Samba-2.2.2 from Tru64 5.1) and the directories look fine.  When I mount 
>>a share from a Windows 2000 server I only get the first letter of the 
>>entry in the shared folder which, of course, makes no sense and 
>>generates errors when just trying to get an "ls" of the share.  The 
>>Win2K servers are both regular server and Adv Server, both with SP2 and 
>>the latest patches.  The linux machine is running RedHat 7.2 with almost 
>>all of the latest updates and 2.5.11 compiled.
>>
>
>The server is returning unicode filenames but smbfs isn't expecting them.
>
>You don't say which samba version your smbmount is from, but I'm guessing
>2.2.1/2.2.2. They always negotiate unicode support without knowing if
>smbfs supports it or not, which is a bug.
>
>With smbfs unicode support in 2.5 this started to matter for various
>reasons. I have thought about "autodetection" and maybe that will be
>necessary anyway.
>
>For now, upgrading samba to 2.2.3a should fix this. Let me know if it
>doesn't.
>
>/Urban
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>



  reply	other threads:[~2002-05-03 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 19:40 2.5.11 and smbfs Scott A. Sibert
2002-05-01 17:44 ` Urban Widmark
2002-05-03 14:39   ` Scott A. Sibert [this message]
2002-05-01 19:08 ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01  7:52 vt

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=3CD2A10A.2010306@hollins.edu \
    --to=kernel@hollins.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=urban@teststation.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=vt@vt.fermentas.lt \
    /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