Recent content by saybur

That looks amazing, what a chonky beast. If you can get the response from an INQUIRY command it should indicate whether it is write-only or not, there is a device type flag in there (assuming it is standards-compliant). SCSI Probe should show that information. There is another classic Mac tool...

I'd assume the SCSI commands are going to be quirky with write-once media, especially during formatting. It may require one of those special backup packages referenced in the other thread.

Neat find! If it's a WORM drive some of the information here might point to useful software. If you want to take some pictures you might be the first person to document it online, I couldn't find hardly anything apart from references to Laserdisk (later "Literal") making the equipment.

Well done work and very nicely documented. Wonder what they were trying to accomplish with... whatever all that was. Just trying to narrow down the GAL failure? Or somehow trying to make it work with some other system?

That makes complete sense, thanks. Are there any plans to change the old-school ea=ad approach? Or is that expected to remain a viable option for the future?

@Fizzbinn that was my first thought too. Would be worth checking the voltage of those batteries in circuit as well to make sure they aren't toast. Second (and IMHO more likely) are the logic board caps. At this point I'd be suspicious of any original-capacitor LC series board that hasn't been...

The writeup assumes you're using the official Debian packages for all the services, though this should work on any distro or BSD assuming similar service versions. The only custom code is the hooks library for Kea (and if you need it, the C program used one time to help prep the images)...

This is great info thank you, I was not understanding this prior to your posts on the subject. If it was in the documentation I definitely missed it, adding that somewhere in the official docs would be useful. I also find this unintuitive, to be honest. I assume there's a technical reason not...

That's neat! Never knew there was any netbooting support for the earlier systems at all. Good read. Another approach these days might be one of the network-attached modern SCSI devices presenting a network file as though it was local storage. Not sure how practical that would be with all the...

Guide updated for Debian trixie and associated package version changes (including Netatalk 4 being much easier to install now its available in official packages, yay!). This also updates the hooks library to address a breaking change made starting in Kea 2.6.3 and includes some more concrete...

Sorry, I should have clarified that all original testing was with ea unset; I was checking extended attributes directly with addump -e (and to a lesser extent getfattr --dump, just to make sure something was present). I went back to ea = ad as a fallback since it was somewhat easier to directly...

Very nice, that's cleaner than the manual bless editing I was doing. This and the set commands gets EAs correctly populated with FinderData and I'm no longer getting AppleDouble errors on dbd scans. Unfortunately this is not bringing over the resource fork from the dot files into the EAs, and...

Appreciate the help, I will try these out via a client later this evening.

Made another attempt, this time within the ~/afp-data directory. This time I got "ad[58969] {unix.c:619} (error:AFPDaemon): initgroups(saybur, 1000): Operation not permitted". Adding sudo to each ad command made them complete without error and I did see a burst of activity in the Netatalk log...

I tried this again and unfortunately ran into the same issue. Commands ran on an empty share with dbd -f /srv/netboot ran on it immediately beforehand (lightly edited for brevity): $:/srv/netboot$ 7z x ~/NetBoot.pax $:/srv/netboot$ chmod +x NetBootInstallation $:/srv/netboot$ cd...