Uninstall the DisplayLink drivers and restart the system. Right after restarting the system, reinstall the drivers. Don't restart again yet. Open System Preferences - Security and Privacy.
- The install onto my Linux box file server was quite painless and I was instantly able to mount all my Linux volumes on my OS X desktop (works equally well on OS 9). Among other things, Netatalk allows OS X to keep the proper file types (with the ability to define custom file types) and I do not have to deal with invisible files from other file.
- Out of Control Regular Macromedia Fontographer 4. 1 Out of Control Out of Control Macromedia Fontographer 4. 1 8/3/2001 OutofControl JupiterImages http://jupiterimages.
| Click here to return to the 'Access Linux volumes with Netatalk' hint |
You can also use nfs to share your linux files to to a OS X box. Since Linux and OS X are unix based OS's nfs might even be faster/better. You can even get the permissions and users/groups to match up..but you may have to edit the user/group ID's on one of the machines...
I have no problems nfs mounting an exported dir from a solaris box on MacOS X, but I have not been able to get such to work mounting an exported dir from a Linux host. I've tired kernels 2.2.14 and 2.4.17 and both seem to work on the mac side in that the mount does not return an error. But the mount also does not actually work, the mounted-on dir ends up in a funny state where any access ges an 'operation not permited' error and df does not list the mount.
any ideas?
I've used a couple of versions of netatalk (including the current v1.5.2) on Redhat v7.1 and Mac OS X 10.1.x will never connect properly. i get to the point where I select the volume I want and a message 'The file server connection has unexpectedly closed down'. Any ideas?
This same server works just fine when connecting under Mac OS 9.
The fix for this is actually pretty dumb. Add a login message to the server in the netatalk.conf (I think). It will only show the first word and it's kind of annoying every time you log into a server but it gets you there.
Could you please tell me how to add a 'server message' to the netatalk.conf file? I did a 'man netatalk.conf' and couldn't find any references to that.
From OS9 I can mount volumes from my YellowDog Linux server. From OSX I get:
'The file server 'localhost' connection has unexpectedly closed down.'
Regards,
Gustavo
I was having the same problem...
I added the following to the afpd.conf file.
- -loginmesg 'welcome'
(thats two '-' at the begin)
so thanks JessamyG4 for the tip
The current release seems to be quite stable, so far.
After doing some snooping through the Netatalk 1.5.2 make file and the man pages I figured it out.
The previous install was v1.5.0pre6, was installed using the RPM at sourceforge. Because it was a Redhat-specific install everything went in a Redhat-specific place (I really hate that). Unfortunately, The RPM puts things in different places than 'make install' does when compiling from the source code. A quick look at /var/log/messages showed that even with v1.5.2 installed v1.5.0pre6 was still starting up.
So basically, I had to remap a couple things on my Linux box:
1. Modify the /etc/rc.d/init.d/atalk script to point to /usr/local/sbin instead of /usr/bin
2. Create a link from /etc/atalk (the existing netatalk config files) to /usr/local/etc/netatalk (where the v1.5.2 install expects to find them).
I figured this was easier than trying to figure out how to properly remap paths in the make file to match up with where the rpm install put everything.
Everything's good now, and iTunes can finally get to my mp3 stash. Hurray!
Use Adrian Sun's version of netatalk. It works flawlessly. It will say +asun in the package name
As a previous poster said, both linux and OS X support NFS. Another option is to install samba on the linux box and use OS X's smb capability.
- Avi
dont know if this has changed -- but the last time I tried doing something like this I found out that only HFS is supported, not HFS+!
This hint does not discuss mounting linux volumes as local volumes on a OS X machine, or vice versa. It is discussing the mounting of linux volumes over a network. The local filesystem in use by either linux or OS X is completely irrelevant.
- Avi
Hello!!
I've used both. NFS and Netatalk.
And what I've seen, is that Netatalk is faster then NFS(UDP), but NFS is way more stable. Netatalk quits and gives error's, NFS doesn't do that.
Now if your running just OS 9, use Netatalk. NFS support on OS 9, sucks!!
If your running OS X, use NFS!!!!!
Plus the Appledouble problem doesn't happen with NFS.
My people haven't *itched about the connection closing on me, anymore!!!
And oh yeah the Box is a G3 233mhz with 80GB, running LinuxPPC using the 2.4.18 kernel.
CS
We have had no problems here with Netatalk 1.5pre8 on a Linux Mandrake box.
I mount a Netatalk volume to listen to about 20GB of music every day / all day.
No problems at all.
dd
Am i missing something here, but I thought Netatalk was to enable a nix like os to provide Appletalk filesharing?
I upgraded from Mac OS X 10.10 Yosemite to macOS 10.12 Sierra. After that, any MacPorts command I ran returned the following error:
Error: If you upgraded your OS, please follow the migration instructions: https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
'mportinit ui_options global_options global_variations'
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
The problem is that MacPorts is specific to a Mac OS X platform. The best way to fix this problem is to follow the Migrating a MacPorts installation guide.
Totally Clean Slate
MacPorts migration provides a 'restore_ports.tcl' script to restore all the ports (a.k.a. packages) once you have upgraded MacPorts. However, I decided to start from a clean slate and only install ports as I needed them.
port -qv installed > ~/ports_installed.txt
# Save list of ports you manually installed (exclude dependency ports)
port installed requested > ~/ports_requested.txt
# Uninstall all installed ports
sudo port -f uninstall installed
# Clean any partially-completed builds
# Remove leftover build files (this should be done automatically already)
sudorm-rf/opt/local/var/macports/build/*
# Remove download files
sudorm-rf/opt/local/var/macports/distfiles/*
Note: I noticed that executables like svn (from subversion port) were left behind in /usr/bin and could still be used.
Partially Clean Slate
If you decide to keep your existing ports and to use the 'restore_ports.tcl' script, you might consider cleaning out inactive packages:
# Alternative command: port echo inactive
port installed inactive
# Remove all of the inactive ports
sudo port uninstall inactive
Install macOS-specific MacPorts
Install the latest MacPorts for your macOS version:
The fix for this is actually pretty dumb. Add a login message to the server in the netatalk.conf (I think). It will only show the first word and it's kind of annoying every time you log into a server but it gets you there.
Could you please tell me how to add a 'server message' to the netatalk.conf file? I did a 'man netatalk.conf' and couldn't find any references to that.
From OS9 I can mount volumes from my YellowDog Linux server. From OSX I get:
'The file server 'localhost' connection has unexpectedly closed down.'
Regards,
Gustavo
I was having the same problem...
I added the following to the afpd.conf file.
- -loginmesg 'welcome'
(thats two '-' at the begin)
so thanks JessamyG4 for the tip
The current release seems to be quite stable, so far.
After doing some snooping through the Netatalk 1.5.2 make file and the man pages I figured it out.
The previous install was v1.5.0pre6, was installed using the RPM at sourceforge. Because it was a Redhat-specific install everything went in a Redhat-specific place (I really hate that). Unfortunately, The RPM puts things in different places than 'make install' does when compiling from the source code. A quick look at /var/log/messages showed that even with v1.5.2 installed v1.5.0pre6 was still starting up.
So basically, I had to remap a couple things on my Linux box:
1. Modify the /etc/rc.d/init.d/atalk script to point to /usr/local/sbin instead of /usr/bin
2. Create a link from /etc/atalk (the existing netatalk config files) to /usr/local/etc/netatalk (where the v1.5.2 install expects to find them).
I figured this was easier than trying to figure out how to properly remap paths in the make file to match up with where the rpm install put everything.
Everything's good now, and iTunes can finally get to my mp3 stash. Hurray!
Use Adrian Sun's version of netatalk. It works flawlessly. It will say +asun in the package name
As a previous poster said, both linux and OS X support NFS. Another option is to install samba on the linux box and use OS X's smb capability.
- Avi
dont know if this has changed -- but the last time I tried doing something like this I found out that only HFS is supported, not HFS+!
This hint does not discuss mounting linux volumes as local volumes on a OS X machine, or vice versa. It is discussing the mounting of linux volumes over a network. The local filesystem in use by either linux or OS X is completely irrelevant.
- Avi
Hello!!
I've used both. NFS and Netatalk.
And what I've seen, is that Netatalk is faster then NFS(UDP), but NFS is way more stable. Netatalk quits and gives error's, NFS doesn't do that.
Now if your running just OS 9, use Netatalk. NFS support on OS 9, sucks!!
If your running OS X, use NFS!!!!!
Plus the Appledouble problem doesn't happen with NFS.
My people haven't *itched about the connection closing on me, anymore!!!
And oh yeah the Box is a G3 233mhz with 80GB, running LinuxPPC using the 2.4.18 kernel.
CS
We have had no problems here with Netatalk 1.5pre8 on a Linux Mandrake box.
I mount a Netatalk volume to listen to about 20GB of music every day / all day.
No problems at all.
dd
Am i missing something here, but I thought Netatalk was to enable a nix like os to provide Appletalk filesharing?
I upgraded from Mac OS X 10.10 Yosemite to macOS 10.12 Sierra. After that, any MacPorts command I ran returned the following error:
Error: If you upgraded your OS, please follow the migration instructions: https://trac.macports.org/wiki/Migration
OS platform mismatch
while executing
'mportinit ui_options global_options global_variations'
Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform mismatch
The problem is that MacPorts is specific to a Mac OS X platform. The best way to fix this problem is to follow the Migrating a MacPorts installation guide.
Totally Clean Slate
MacPorts migration provides a 'restore_ports.tcl' script to restore all the ports (a.k.a. packages) once you have upgraded MacPorts. However, I decided to start from a clean slate and only install ports as I needed them.
port -qv installed > ~/ports_installed.txt
# Save list of ports you manually installed (exclude dependency ports)
port installed requested > ~/ports_requested.txt
# Uninstall all installed ports
sudo port -f uninstall installed
# Clean any partially-completed builds
# Remove leftover build files (this should be done automatically already)
sudorm-rf/opt/local/var/macports/build/*
# Remove download files
sudorm-rf/opt/local/var/macports/distfiles/*
Note: I noticed that executables like svn (from subversion port) were left behind in /usr/bin and could still be used.
Partially Clean Slate
If you decide to keep your existing ports and to use the 'restore_ports.tcl' script, you might consider cleaning out inactive packages:
# Alternative command: port echo inactive
port installed inactive
# Remove all of the inactive ports
sudo port uninstall inactive
Install macOS-specific MacPorts
Install the latest MacPorts for your macOS version:
- Install or upgrade to the latest version of Xcode Developer Tools (free from the Mac's App Store) and run it once.
- Install the latest Command Line Developer Tools by running this command in the Terminal app:
- Download and install the MacPorts package matching your Mac OS X version. It will overwrite the existing MacPorts installation.
Update MacPorts Configuration
The new MacPorts installer won't modify the existing configuration file so you will need to update it manually. The updated configuration file 'macports.conf.default' is located in the '/opt/local/etc/macports' directory. The old configuration file 'macports.conf' is also in the same location.
Before overwriting the old file with the new, I recommend doing a file comparison:
diff macports.conf macports.conf.default
Out Of Control (greydavenport) Mac Os Catalina
Note: If you prefer a nice graphical user interface, you can use the FileMerge application which comes with Xcode. Just run FileMerge and input the paths to the two files to compare them.
There wasn't any significant difference between the two files (beyond comments), but I went ahead and overwrote the old one with the new.
sudocp macports.conf.default macports.conf
Note: There are two other MacPorts configuration files, 'variants.conf' and 'sources.conf', which the migration guide doesn't mention. I compared them anyways and the only significant difference I found was in the 'sources.conf' where the 'rsync' value was different. I overwrote the 'sources.conf' with the latest to ensure that everything is updated.
If you didn't do a totally clean slate, you will want to follow the migration instructions on how to run the 'restore_ports.tcl' script.
Out Of Control (greydavenport) Mac Os Download
Some info above derived from:
