Here are some beta test notes so far. . .
I setup the image on a 16gb SD card running on a Pi 3b+.
It goes through the booting process with everything loading and scrolling by and ends by stopping at last line:
[OK] Started Raised Network Interfaces
There is no login prompt, no CLI—which maybe I should assume is normal/expected since these will probably be headless gateway systems. No need for a display at all—you can SSH in—is that the idea?
SO, I don’t have my localtalk wired up yet as I am awaiting hardware delivery, but I did SSH into it as macipgw user. Tried to expand the partition using:
sudo /usr/bin/raspi-config —expand-rootfs
but this fails. In fact, I cannot run raspi-config because I am not in the sudoers list. Can’t edit /etc/sudoers either. . . so, I logged out and back in as pi (same password) and I was able to run raspi-config.
Maybe I missed it but logging in as pi to expand the partition is worth updating in the docs, or add macipgw to the sudoers.
I know the cool part is seeing this from a vintage mac through the local talk bridge, but from a more recent mac Mini running High Sierra, I see
three versions of the file share:
MACIPPI
which has a mountable ‘MacIPpi-Samba’ folder,
macippi MACOS
which has a mountable ‘MacIPpi DISK’ folder,
and
macippi WINDOWS which has a mountable ‘MacIPpi-Samba’ folder
I was able to mount all three and place a file into the SHARED_DISK folder which is showing over 11 GB available. Of course, this file is visible in all three mounted shares.
I assume the different “servers” that are showing up on my network are simply a result of my modern machine’s ability to see all three running the various protocols. The common mapping is as much as anyone needing to transfer files around would need. Nicely done!
I might try setting up a VM either on another Pi or on my mac running MacOS 7 if I can make it work to see if a virtual mac can see this in lieu of my SE/30 which has no connectivity as of yet.
Also, I tested the Web Rendering Proxy, albeit from a modern system. It works a treat! Performance is what it is, but that is a nice addition.
This is a very capable little network solution. I wonder if it can run alongside CUPS with Airprint? I have that running on another Pi (also running PiHole on that one). Do we know if a CUPS printer setup is visible to the old macs this way?
I setup the image on a 16gb SD card running on a Pi 3b+.
It goes through the booting process with everything loading and scrolling by and ends by stopping at last line:
[OK] Started Raised Network Interfaces
There is no login prompt, no CLI—which maybe I should assume is normal/expected since these will probably be headless gateway systems. No need for a display at all—you can SSH in—is that the idea?
SO, I don’t have my localtalk wired up yet as I am awaiting hardware delivery, but I did SSH into it as macipgw user. Tried to expand the partition using:
sudo /usr/bin/raspi-config —expand-rootfs
but this fails. In fact, I cannot run raspi-config because I am not in the sudoers list. Can’t edit /etc/sudoers either. . . so, I logged out and back in as pi (same password) and I was able to run raspi-config.
Maybe I missed it but logging in as pi to expand the partition is worth updating in the docs, or add macipgw to the sudoers.
I know the cool part is seeing this from a vintage mac through the local talk bridge, but from a more recent mac Mini running High Sierra, I see
three versions of the file share:
MACIPPI
which has a mountable ‘MacIPpi-Samba’ folder,
macippi MACOS
which has a mountable ‘MacIPpi DISK’ folder,
and
macippi WINDOWS which has a mountable ‘MacIPpi-Samba’ folder
I was able to mount all three and place a file into the SHARED_DISK folder which is showing over 11 GB available. Of course, this file is visible in all three mounted shares.
I assume the different “servers” that are showing up on my network are simply a result of my modern machine’s ability to see all three running the various protocols. The common mapping is as much as anyone needing to transfer files around would need. Nicely done!
I might try setting up a VM either on another Pi or on my mac running MacOS 7 if I can make it work to see if a virtual mac can see this in lieu of my SE/30 which has no connectivity as of yet.
Also, I tested the Web Rendering Proxy, albeit from a modern system. It works a treat! Performance is what it is, but that is a nice addition.
This is a very capable little network solution. I wonder if it can run alongside CUPS with Airprint? I have that running on another Pi (also running PiHole on that one). Do we know if a CUPS printer setup is visible to the old macs this way?