Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
> > >
> > > We are trying to integrate OS X into a Linux back end and having
> > > problems.
> > >
> > > When copying files to or from the Linux server with either SMB or AFP
> > > at some point doing the copy process there will be an error -50. This
> > > is a consistent problem. The files that are copied before the error
> > > occurs will typically be corrupt, have a zero K file size or lose
> > > their format, i.e. a jpg will look like a text file.
> > >
> > > Files copied from the OS 9 to Linux are not all visible to the OS X
> > > computer. For example if you copy a "folder" that contains files from
> > > OS 9 to Linux, at times several of those files will be missing. If
> > > you remove and recopy the folder different files will be missing from
> > > the folder.
> > >
> > > Apple's technical support will not acknowledge this problem. Their
> > > solution is to purchase an OS X server.
> > >
> > > Based on Goggle search returns, I have tried changing the Linux file
> > > system from ext3 to ext2. That did not resolve the problem.
> > >
> > > Connecting workstations to the Linux server via NFS does work without
> > > error but I would prefer not to do this as this would require server
> > > level administration / configurations on each workstation. I thought
> > > it might be better to use a OS X "server" to connect to the Linux
> > > server via NFS.
> > >
> > > Due in part to this problem, I am trying to move away from AFP and
> > > solely to SMB. My goal here is to use an OS X computer to "share"
> > > Linux NFS mounted volumes to other OS X computers via Samba. I am
> > > having one problem with the OS X Samba server, the SMB client is able
> > > to create directories on a Samba share but unable to create or copy
> > > files. When attempting to copy file "foo" to the share the error code
> > > is, "The operation cannot be completed because you do not have
> > > sufficient privileges for "foo". When trying to copy a directory that
> > > contains files to the share the error code is, "The operation cannot
> > > be completed because you do not have sufficient privileges for
> > > ".DS_Store".
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
Whoever is doing this is, pardon me, insane. If you want to share files between UNIX machines, you should be using NFS. The excuse of:
Quote:
> > > Connecting workstations to the Linux server via NFS does work without
> > > error but I would prefer not to do this as this would require server
> > > level administration / configurations on each workstation. I thought
> > > it might be better to use a OS X "server" to connect to the Linux
> > > server via NFS.
is silly. You need to have permissions to do the same thing with other file "sharing" techniques like samba. Just set up an exportfs from the Linux server, and tell all the OS X machines to mount the filesystem via NFS. It's not difficult, and it's a hell of a lot more robust than the SMB garbage being used by samba (remember, samba is designed to interface UNIX and windows because windows doesn't know how to deal with a real network filesystem).
You already have a solution that, "works without error". Use it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.