Simon, the forked project is Baltra. It changes the scheme that
Netatalk uses to store files on the server to use Apple's standards
(utf-8, ._filename style AppleDouble forks, etc.) instead of Netatalk's
ancient arbitrary schemes.
For more info:
http://www.baltra.org/
Phil
Simon Hobson
? and /) to the server. Make
sure you have people use some sane naming on their files or else they
may get some error when trying to name or copy files on the server.
My Samba, btw, is running tandom with Netatalk-1.6.4-Baltra.
Good luck!
Phil
Deim Agoston wrote:
Philip Edelbrock [EMAIL PROTECTED
That could be true. If you veto 'dot' files in smb.conf, then you would
get strange permission errors from OS-X clients. OS-X wants to put
._filename files (AppleDouble versions of the resource forks) and
.DS_Store files (containing some file metadata like Finder comments) on
the server.
If
I've played a little bit with smart cards and tokens. They are a bit
messy to implement. I didn't like the idea of special software/hardware
installed on the client to get such a system in place. There are some
other ways to do the same thing, though, that may solve a lot of the
issues you may
OS-X wants Samba 3.0. It fixes a lot of issues that OS-X has with SMB.
Another issue you may be hitting is large file support. You might do
some searches in the list to see if there are discussions related to
that which you may be experiencing.
BTW- OS-X in general seems to have flakey
Take a look at Baltra:
http://www.baltra.org/
The idea behind Baltra is to patch up Netatalk so that it accesses and
stores files on the server in the standard Apple OS-X way instead of the
funky old Netatalk method (e.g. .AppleDouble directories). Baltra
doesn't change the way Netatalk
Yes, Apple has. ;') Try taking a look at the changes they made to Samba:
http://www.opensource.apple.com/darwinsource/index.html
Last I looked, most of the additions is Kerberos stuff (which your error
output seems to imply is where your build is failing).
You might try downloading Apple's,
Most of the support for SMB in OS-X is centered around the Samba 3.0x
tree, not 2.x.
FYI- Here the relevent section of my smb.conf for OS-X clients:
# OS-X Additions
; UTF-8 encoding to match Baltra patched Netatalk (OS-9 clients)
unix charset = UTF8
unicode = yes
; dumb down that charset to
Sorry, let me back up a little: I may have not answered your original
question.
The file sizes shown in OS-X are guessed 'physical' sizes. If you 'get
info' (command-i) on a file, it will show you the actual file size in
parentheses. The size in parentheses is what counts for most uses (like
I think it already comes with a flavor of Samba 3.0x. You just need to
start it as a service. The SMB client in OS-X is written by Apple and
is in kernel space (hense the complete machine crashes when OS-X runs
into a file sharing bug ;')
Also, see this site for some related info regarding
(Last comment on the spam issue)
Here's some info on SourceForge for adding some restrictions (other than
closing the list) to filter some spam:
http://sourceforge.net/docman/display_doc.php?docid=9484group_id=1#antispamtools
Phil
--
To unsubscribe from this list go to the following URL and
I was forced to put a filter (spambayes) on my list (Lm_sensors) to keep
out most of the garbage. It's really helped a ton, and I can scan the
'spam' to make sure nothing real got blocked from the rest of the
recipients of the list.
It's pretty easy (I used procmail, spambayes, and a large
Hi, I think OS-X was primarily written w/ Samba3.0 in mind. I've tested
2.x and 3.0 (alphas) and 3.0 solved a lot of problems for me.
BTW- Check out this site for more info on using OS-X with Samba and a
special patched version of Netatalk specificly for networks which
include OS-X clients:
Incidently, I've founded a project a few weeks ago to tweak Netatalk to
work specificly with OS-X and Samba 3.0 to ease the problems of a
MacOS-9 and MacOS-X mixed environment. Preserving resource-forks across
file servers is a problem. Products like DAVE don't address this unless
every Mac
(This is a brief announcement of a focused development/refinement of the
Netatalk project.)
The primary goal of Baltra is to provide a Mac OS X compatible AFP file
sharing service with Samba 3.0 compatibility. We are hoping to have an
AFP file sharing daemon which can run in parallel with
Command-K in the 'finder' (aka the desktop) or Go-Connect to Server
menu and then smb://servername will let you browse and connect. Or, for
unix-terminal freaks, you can use mount_smbfs (there is a man page for
it for usage details). Mounted shares will show up as an icon on the
desktop as
I'm having a problem with some client machines connecting to Samba using
'bad' chars. Actually, the chars are legal but the clients get confused
seeing them come back after putting them there (this is Mac-OS-X, btw).
For example, the 'florin' char (script small latin F with hook [unicode
17 matches
Mail list logo
