How To Burn Disk From Command Line

Can't test this as I only have one device, but according to the manpage for hdiutil:
hdiutil burn -list
will get you a list of devices with paths suitable for passing to the device option:
hdiutil burn -device <path to device>

- cfr

I can confirm that what Clea suggests works. Jun T. demonstrated how to use my external firewire burner using the openfirmware path provided by hdiutil burn -list. You might try editing the following to find your target drive (first try hdiutil burn -list to find a unique string to match):
<pre style="padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 80ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">hdiutil burn your.dmg -device `hdiutil burn -list | sed -ne '/ via FireWire / {n; p;}'`
</pre>
--
Cole

I think that you would set up the hdiutil burn command as you usually would and then add "-device /AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PATA@1F,1/AppleIntelPIIXATARoot/PR ID@0/AppleIntelPIIXPATA/ATADeviceNub@1/IOATAPIProtocolTransport/IOSCSIPeripheral DeviceNub/IOSCSIPeripheralDeviceType05/IODVDServices" as an(other) option to the burn command.

I haven't done this, mind you. But I think that path is supposed to be such that you feed it straight to the device option. It says it is an "open firmware path" in the manpage. I know virtually nothing about open firmware but I suspect that is why the path looks strange - it is a path at a very low level. It is not a path at the file-system level at all. I don't know if that is true. I don't know if it makes sense, but that's my guess.

Maybe somebody else can confirm. Otherwise, I would probably just try it - maybe as a standard user, though I don't think you are likely to harm anything (open firmware just makes me nervous). I think it just might not work.

- cfr

{quote:title=Rob Frei wrote:}Thanks again for your help. Maybe someone will happen by who has actually done this ... apparently most aren't 😉
{quote}

I use the hdiutil -device option in my production work flow to create masters of our educational software. I can tell you with a high degree of confidence that this does work. 🙂

Each entry is two lines. The first line contains the name of the device followed by another very long line with the OF path to the device. In my case I'm looking for the device whose name contains 'firewire' then printing the following line. But you're looking for a string in the actual path so it becomes simpler.

The path to my internal burner contains ATADeviceNub@0 and this works for me:
<pre style="padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 80ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">hdiutil burn your.dmg -device `hdiutil burn -list | fgrep 'ATADeviceNub@0'`</pre>
--
Cole

Aha - so the IOService: is part of the path? I wondered about that...

- cfr

{quote:title=Clea Rees wrote:}
Aha - so the IOService: is part of the path? I wondered about that...
{quote}

Yes. It's natural to assume the path begins with the forward slash. I wrestled with that for awhile until Jun T. helped out. It's an ugly long string which is why I like to extract it with a separate command.

Actually drutil has a nice rich set of drive selection methods, but surprisingly lacks the ability specify burn speed (at least in my version). This was a show stopper for me, since our replicator prefers masters be burned at 4x.

--
Cole