Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[torvan]

Just a note for future reference.

If you have a machine running El Capitan, you will notice under System Preferences:Sharing that FTP is no longer an option.  That might lead you to think it was removed--but a simple trip to Terminal will turn FTP back on:

Launch Terminal and type in the following and enter your password:

Code: [Select]

sudo -s launchctl load -w /System/Library/LaunchDaemons/ftp.plist
That is it!

Now to turn it back off again, you Unload it:

Code: [Select]

sudo -s launchctl unload -w /System/Library/LaunchDaemons/ftp.plist

Now fire up Fetch (I use 4.0.3 on my iMac) and begin a new connection.

The Host is the IP Address of the El Capitan machine. (Get that from System Preferences: Network).

The User ID is the account on the El Capitan machine you want to use.

The Password is the password on that same account.

That is it! Get and Put to your heart's desire.

[geforceg4]

did u ever try doing it the other way around?
sharing writable file location FROM the mac os 9 machine?
i think i did this last year and i was shocked that it actually worked

[maduro]

You need Rumpus 2.0.....msg me.

[maduro]

Ok, I've uploaded Rumpus Pro 2.0 to macgarden...be sure to look at the config screen snap.  This app works great on OS 9.2.2.

http://macintoshgarden.org/apps/rumpus-20-ftp-server

[Metrophage]

This works, but requires caution to do! I was trying to get FTP running in El Capitan about a month ago and was thrown off by the font spacing on a website, which inspired me to try "...launchctl load -w /System/Library/LaunchDaemons/ ftp.plist" - with a space between the directory and ftp.plist. This caused errors, because my system saw the / and tried loading all of the launch daemons in that directory. In trying to fix it, I accidentally blacklisted ALL of my launch daemons, rendering my system non-bootable. And it's a hackintosh, which makes fixing things a headache. I was able to fix it by taking some time to learn more about the OS X boot process than I wanted to know, but it took a few days.

Moral of the story: pay close attention, and don't try risky terminal jiggerypokery when you've been up all night and are too tired to think it through clearly.