From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [Fwd: road sign]
Date: Tue, 11 Oct 2005 08:25:51 +0100 [thread overview]
Message-ID: <20051011072551.GH8153@server4.lensbuddy.com> (raw)
In-Reply-To: <3e1162e60510102252y6e10ca4ejb50e6db1897cb697@mail.gmail.com>
when I hear about resource forks or extended attributes I reach for my
MP5.
apple latest "innovation" is to fuck up tar, zip, and I think even cp
and mv to pass around their wonderful crap.
a file I got from a graphic design company we work with:
; ls
Linsbilder_JPG.zip
; file Linsbilder_JPG.zip
Linsbilder JPG.zip: Zip archive data, at least v2.0 to extract
; unzip Linsbilder_JPG.zip >/dev/null
$ ls -l
drwxr-xr-x 2 uriel uriel 4096 2005-10-04 10:15 Linsbilder JPG
-rw-r--r-- 1 uriel uriel 5801742 2005-10-11 08:56 Linsbilder_JPG.zip
drwxr-xr-x 3 uriel uriel 4096 2005-10-11 09:01 __MACOSX
; ls -l __MACOSX
total 4
drwxr-xr-x 2 uriel uriel 4096 2005-10-11 09:01 Linsbilder JPG
; ls -l '__MACOSX/Linsbilder JPG/'
[nothing!]
; ls -la '__MACOSX/Linsbilder JPG/'
total 1156
drwxr-xr-x 2 uriel uriel 4096 2005-10-11 09:01 .
drwxr-xr-x 3 uriel uriel 4096 2005-10-11 09:01 ..
-rw-r--r-- 1 uriel uriel 37848 2005-10-04 10:15 ._01.jpg
-rw-r--r-- 1 uriel uriel 37929 2005-10-04 10:14 ._02.jpg
-rw-r--r-- 1 uriel uriel 37837 2005-10-04 10:15 ._03.jpg
[...]
-rw-r--r-- 1 uriel uriel 70 2005-10-04 10:07 ._.DS_Store
; file '__MACOSX/Linsbilder JPG/._01.jpg'
__MACOSX/Linsbilder JPG/._01.jpg: AppleDouble encoded Macintosh file
20h, get those physics packages ready, we have some fireworks to make
around Cupertino.
unix has become so disgusting that people covers it's crap with a tick
layer of sparkling sugar, but in the end maybe it will be the sugar that
kills you.
the new holy trinity: MacOS X, Google, and Firefox.
doing a boyd maybe, but someone had to do it.
uriel
P.S.: Oh, and don't you love their new XML based init system[0]?! "The unix
of the 21th century" indeed.
[0] http://developer.apple.com/macosx/launchd.html
On Mon, Oct 10, 2005 at 10:52:56PM -0700, David Leimbach wrote:
> > >
> > > No, but the RFCs never really covered correct handling of 'forked'
> > > binary files (such as those found on Macs).
> >
> > Thankfully, even Apple on OS X has slowly gone away from the blasted
> > Resource Forks. Sure, you can still use them (if you're Adobe), but
> > none of the Cocoa or CoreFoundation APIs go out and encourage to
> > resource forks any more.
>
> No but the whole OS pretty much relies on storing things in extended
> attributes now. Even the resource forks can be found there now. [I
> believe this is also where ACLs are stored but don't quote me on this]
>
> Why does a file need to be like a directory? Isn't that what
> directories are for? :)
>
> Dave
next prev parent reply other threads:[~2005-10-11 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 3:57 Ronald G Minnich
2005-10-10 19:52 ` Russ Cox
2005-10-11 1:56 ` erik quanstrom
2005-10-11 2:34 ` erik quanstrom
2005-10-11 2:49 ` Chris Collins
2005-10-11 3:05 ` Jeff Sickel
2005-10-11 5:52 ` David Leimbach
2005-10-11 7:11 ` Chris Collins
2005-10-11 8:05 ` leimy2k
2005-10-11 7:25 ` Uriel [this message]
2005-10-11 10:05 ` erik quanstrom
2005-10-13 2:09 ` Jeff Sickel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051011072551.GH8153@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).