From: Bastien Nocera <hadess@hadess.net>
To: Urban Widmark <urban@teststation.com>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: problems with smbfs on 2.4.18 kernel (ppc)
Date: 03 May 2002 03:06:25 +0100 [thread overview]
Message-ID: <1020391586.13881.12.camel@dozo> (raw)
In-Reply-To: <1020268150.25255.195.camel@dozo>
Dammit,
I feel stupid now. The SAMBA version I grabbed off some MacOS X site
came with a borked smb.conf. There was a rule to veto some files only
used by MacOS X (resource forks). Here was the rule:
veto files = .*/Temporary Items/Desktop
*/TheFindByContentFolder/TheVolumeSettingsFolder/Network */
And the last bit actually vetoed all the directories, beginning with the
one at the bottom of the share. I still don't understand why smbclient
and the smb gnome-vfs method actually worked just fine with this share.
Urban, is this actually a bug ? I'll take this off linuxppc-dev now.
Cheers
On Wed, 2002-05-01 at 16:49, Bastien Nocera wrote:
<snip>
> I'm seeing this in ethereal:
> from laptop to SMB server: Transaction2 Request QUERY_PATH_INFORMATION,
> Path: \
> from SMB server back to laptop: Transaction2 Response
> QUERY_PATH_INFORMATION, Error: Directory not found
>
> However, smbclient seems to find it:
>
> smbclient //kara/backup1 -U hadess
> added interface ip=192.168.1.2 bcast=192.168.1.255 nmask=255.255.255.0
> Password:
> Domain=[IDORU] OS=[Unix] Server=[Samba 2.2.2]
> smb: \> ls
> mp3s D 0 Wed Apr 3 06:38:08
> 2002
--
/Bastien Nocera
http://hadess.net
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-03 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 17:11 problems with smbfs on 2.4.18 kernel (ppc) Bastien Nocera
2002-03-03 17:28 ` Urban Widmark
2002-03-05 1:51 ` Bastien Nocera
2002-03-04 21:03 ` benh
2002-03-05 16:50 ` Derrik Pates
2002-03-05 9:12 ` Urban Widmark
2002-05-01 15:49 ` Bastien Nocera
2002-05-03 2:06 ` Bastien Nocera [this message]
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=1020391586.13881.12.camel@dozo \
--to=hadess@hadess.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--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;
as well as URLs for NNTP newsgroup(s).