home *** CD-ROM | disk | FTP | other *** search
Wrap
Received: from pht.com (exodus.pht.com [198.60.59.99]) by nacm.com (8.6.10/8.6.9) with SMTP id JAA18454 for <executor@nacm.com>; Thu, 19 Oct 1995 09:10:26 -0700 Received: by pht.com id AA14700 (5.67b/IDA-1.5 for executor@nacm.com); Thu, 19 Oct 1995 08:21:02 -0600 Date: Thu, 19 Oct 1995 08:20:58 -0600 (MDT) From: Brad Midgley <brad@pht.com> To: executor@nacm.com Subject: bad2good.pl: executor->netatalk resource forks Message-Id: <Pine.LNX.3.91.951019081140.14621A-100000@exodus.pht.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-paper@nacm.com Precedence: bulk hi, sorry about the commentary in the name :) (it's preliminary) I wrote a little perl script which converts one-way to netatalk format. It does make softlinks in the form %name->.AppleDouble/name so it will take a netatalk hierarchy and at least make it usable with executor. Can you executor guys give me an idea of how well the softlinks will work in practice? (ie executor won't get upset in any strange cases because it's a softlink, not a real file?) Should I use a hard link instead maybe? I still have more error checking to implement before I release the script, but just to let you know it's there and works. one thing I'm still thinking about though... what do I do if there are differing %name and .AppleDouble/%name? go with the newer one and back up the old one somewhere?? are you sure you guys don't want to offer a command-line switch to tell executor to use the netatalk format? :) brad@pht.com