It’s been a very long time since I used bashburn.
There are two reasons for that. First, because my initial work with bashburn was less than successful. That was about seven years ago though, so that criticism doesn’t really hold much water now.
The other reason is my slow and eventual drift away from CDs. That’s not a personal transformation, just a tendency to rely more and more on USB drives over optical media.
Where I used to burn CDs as backups, I now just use leftover hard drives and drive enclosures. And where I used to burn CDs to install distros, I now just inject ISOs onto flash drives with unetbootin.
Now, to add insult to injury, I don’t even have an optical drive on this machine. I could buy one I suppose, but I rarely use CDs any more.
And so we come full circle.
Regardless, bashburn is one of a handful of CD/DVD writing options at the console. For some reason, it seems the majority of burning tools come in graphical form.
Of course, as you probably know, 99 percent of those GUIs are just sending instructions to the command line. But we’ve probably talked about that before. …
If this works for you, leave a note. I’d be curious to get your impression of it.
Inconsolation 
I’m rather surprised that a CLI junkie like yourself uses something like unetbootin. I just manually create multi-iso USB flash drives, as the configuration for syslinux’s memdisk feature is pretty trivial (just set the kernel as memdisk, and the iso as the initrd). Even using grub2’s loopback to boot an iso directly is pretty easy.
Anyway, just make sure you don’t use unetbootin to create an Arch Linux live USB, as it apparently destroys the syslinux.cfg, sending hordes of potential users flocking to the IRC and forums.
Pingback: cdtool: More than just a tool, really | Inconsolation
Pingback: cdw: A proper console application | Inconsolation
Pingback: mybashburn: Much the same animal | Inconsolation