![]() ![]() When the "Start" button is clicked, SheepShaver saves the configuration out to a dotted (hidden) text file called ".sheepshaver_prefs" in the home directory, i.e. SheepShaver Mac OS 9 JIT Compiler configuration I used a port on a VDE (Virtual Distributed Ethernet) switch already configured and used by my DECnet nodes SheepShaver Mac OS 9 Serial Ports and Network Adapter configuration SheepShaver Mac OS 9 Keyboard and Mouse configuration SheepShaver Mac OS 9 Graphics and Sound configuration ![]() SheepShaver Mac OS 9 Disk Volume and Shared Directory configuration Here is a series of pictures of the options I configured in each tab: It simplifies transfer of files between Ubuntu host and Mac OS 9 virtual machines guest anything copied into "shared" shows up in the "Unix" drive on Mac OS desktop though they cannot be executed directly from there, requiring me to copy executable installers from "Unix" to a local place on Mac OS first.įinally I fired up SheepShaver, added the boot disk image, created two disk drives of 250 MB each, disabled sound (I do not want audio!), set the network interface and launched the emulated PowerMac G4. This directory is configured to be the "Unix Root" on SheepShaver and shows up as the drive "Unix" on the virtual Mac desktop. I created a subdirectory called "shared" to share files between the Ubuntu host and SheepShaver's Mac desktop. I placed both these items in the same directory as the SheepShaver binary. There are pointers to where they can be obtained from at " Setting up SheepShaver for Mac OS X". I then looked around the internet to locate a "New World" ROM ( newworld86.rom) and a Mac OS 9 bootable installer image ( Mac OS 9.toast). I created a directory ~/n/ and copied over the SheepShaver binary from the build location ( ~/sheepshaver.build/macemu/SheepShaver/src/Unix/SheepShaver). The following script installs the sheep_net.ko kernel module and creates the /dev/sheep_net network device with the right ownership: Once the main SheepShaver program has been built, the following script builds the sheep_net.ko kernel module. Bring in more Ubuntu Linux boxes supporting AppleTalk to the happy AppleTalk island.Have the Mac OS virtual machine access files on Ubuntu host machine via AppleTalk.Add AppleTalk support to Ubuntu Linux host machine.Configure Mac OS and the virtual machine to support AppleTalk networking.Bring up a classic Macintosh virtual machine running Mac OS with Ubuntu Linux as host.0x809b is EtherTalk, " an Apple AppleTalk networking protocol that enables AppleTalk to communicate over Ethernet cabling."ĮtherTalk (ethertype 0x809b) frames captured by iptraf-ng on Ubuntu LinuxĪfter reading around a bit, and not being a AppleTalk expert, I set myself the simplest of objectives of this experiment: And Cisco's Protocol Filter appendix is handy in deciphering stuff like 0x809b ether-type packets that suddenly pop up in packet dumps once AppleTalk kicks in. The Netatalk 2.0 documentation is fabulous. " Inside Macintosh: Networking" is a great book. Fortunately, there is still enough reading material out on the 'net to get a feel for it. I had zero experience with AppleTalk networking. However, my objective here was to stay away from IP completely, and focus on pure AppleTalk. Interoperability with TCP/IP was introduced as far back as 1988 with MacTCP and later MacIP ( Wikipedia) which basically piggybacked IP over AppleTalk. Trashes files will show up in samba shares (you can easily filter them out on the clients, though).Despite phenomenal rise of the Internet Protocol (TCP/IP), AppleTalk was supported all the way to the 2009 release of Mac OS X Snow Leopard. I have no issues with running netatalk/afp alongside samba on the same server, other than that. In smb.conf to solve some issues with file permissions. You should definitely not forget to use unix extensions = no You can't use server hosted homedir's though with samba. ![]() Older clients will experience random hickups, including (severe) permission problems. Using samba server-side is pretty stable with (Snow) Leopard clients. Adobe Flash (MX and others) don't like this, they'll crash randomly. Netatalk/afp (still) has issues with file locking. Moreover, you will experience random freezes on workstations when the server is not available. Apple Mail will in time complete mess up its mail database on the workstation, forcing to recreate all the mail accounts on workstations. It is possible, but some applications (Adobe InDesign, Illustrator, Apple Mail etc.) don't like this. It's a disaster :įirst of all, don't use home directories on the server with NFS. I've used 25 mac's on an ubuntu server using netatalk and NFS. ![]()
0 Comments
Leave a Reply. |