Re: [Mailman-Developers] Re: i18n support for Archiver
On Mon, 26 Aug 2002 23:58:26 -0400 bob <Puff@NLE" bob@nleaudio.com> wrote:
A note / plea for those working on Pipermail archives. It would be really nice if Mailman would store the archives in a 8.3 dos-compatible filename. This makes the storing of archives on CDROM much easier, and cross-platform friendly.
Easier to use one of the extended CDROM formats which supports long filenames.
---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
Easier to use one of the extended CDROM formats which supports long filenames
A few months ago I went through this with a customer who wanted a copy of the archives on CDROM from their list. The extended filenames work fine under Windows, but not under the MacOS. They have a different format for their extended filenames. The only common denominator I found was the 8.3 dos filenames.
Bob
Bob Puff bob@nleaudio.com wrote:
A few months ago I went through this with a customer who wanted a copy of the archives on CDROM from their list. The extended filenames work fine under Windows, but not under the MacOS. They have a different format for their extended filenames. The only common denominator I found was the 8.3 dos filenames.
Ouch!
Do you know whether 11-character directory names (which do not contain any dots) will work portably?
Greetings, Norbert.
"B" == Bob bob@nleaudio.com writes:
>> Easier to use one of the extended CDROM formats which supports
>> long filenames
B> A few months ago I went through this with a customer who wanted
B> a copy of the archives on CDROM from their list. The extended
B> filenames work fine under Windows, but not under the MacOS.
B> They have a different format for their extended filenames. The
B> only common denominator I found was the 8.3 dos filenames.
That must have been an old version of MacOS. I just tested a CD I burned w/Toast using (IIRC) Mac+PC Hybrid, which is probably ISO 9660 with some fairly universal extensions (Rockridge, but not Joliet????).
In any event the long file names were easily readable under MacOS 9.2.2 and OSX 10.1.5. Python finally abandoned 8.3 names at least a few years ago, and I think we shouldn't go there either.
-Barry
Barry A. Warsaw wrote:
"B" == Bob bob@nleaudio.com writes:
>> Easier to use one of the extended CDROM formats which supports >> long filenames B> A few months ago I went through this with a customer who wanted B> a copy of the archives on CDROM from their list. The extended B> filenames work fine under Windows, but not under the MacOS. B> They have a different format for their extended filenames. The B> only common denominator I found was the 8.3 dos filenames.That must have been an old version of MacOS. I just tested a CD I burned w/Toast using (IIRC) Mac+PC Hybrid, which is probably ISO 9660 with some fairly universal extensions (Rockridge, but not Joliet????).
"Hybrid" probably means "HFS *and* Joliet on the same disc". It's completely sad, the state of CD filesystems. Sigh.
- On 2002.08.27, in 3D6B9EAB.B8F33FAE@nleaudio.com,
- "Bob Puff@NLE" bob@nleaudio.com wrote:
Easier to use one of the extended CDROM formats which supports long filenames
A few months ago I went through this with a customer who wanted a copy of the archives on CDROM from their list. The extended filenames work fine under Windows, but not under the MacOS. They have a different format for their extended filenames. The only common denominator I found was the 8.3 dos filenames.
For UNIX, you want Rock Ridge extensions. For MS, you want Joliet. For MacOS, you want HFS. Combinations of these are commonly called "hybrid". I haven't used Toast on the Mac, but I'd wager that it'll take care of this. So does mkisofs (formerly mkhybrid) from the cdrtools software (formerly cdrecord).
Mkisofs runs on most UNIXes, and will create a single-file hybrid ISO-9660+extensions CD-ROM image track suitable for burning to disc with any CD-R[W] software. Sincec cdrecord is included with it, you might find it easiest to use; maybe not.
Search for "cdrecord schily -psychopath" in Google. It's a first hit, so it's okay to feel lucky.
At one time not so long ago, VMS and HP-UX still required 8.3 filenaming, but I suspect they've both gone RR by now.
Solaris 9 now ships with mkisofs and Sun's own cd-recording program, cdrw. I'd recommend something like:
shell$ cd /path/to/image/root
shell$ mkisofs -o /tmp/image.iso -V "Name of CD-ROM" -J -r -h .
-J adds Joliet records. -r uses "rationalized" Rock Ridge extensions (uids are mapped to 0, permissions normalized). -h adds HFS extensions
Mkisofs also lets you emplace El Torito, Sparc, and Apple boot images, if that's important, and hide certain files from Joliet users or HFS users exclusively.
So, anyway, with tools like that I don't see the added value of switching to 8.3 filenames. :)
- On 2002.09.03, in 3D750235.6080904@sun.com,
- "Dan Mick" Dan.Mick@sun.com wrote:
Oh, that's brilliant! Thank you David; I love Joerg's software, but that just hit home...
I rely on his CD software, and for the most part it's quite good, but it was just too funny to let lie when I found him claiming that under some circumstances you need his make clone to compile cdrecord, and his tar clone to unpack his make source.
You just have to wonder why -- until you realize you'd probably regret finding out.
participants (6)
-
barry＠python.org -
Bob Puff＠NLE -
Dan Mick -
David Champion -
J C Lawrence -
Norbert Bollow