9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] [Fwd: road sign]
Date: Mon, 10 Oct 2005 22:52:56 -0700	[thread overview]
Message-ID: <3e1162e60510102252y6e10ca4ejb50e6db1897cb697@mail.gmail.com> (raw)
In-Reply-To: <BBFE8564-57E3-40B5-AAE7-574AE8DF8A0B@corpus-callosum.com>

> >
> > 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


  reply	other threads:[~2005-10-11  5:52 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 [this message]
2005-10-11  7:11           ` Chris Collins
2005-10-11  8:05             ` leimy2k
2005-10-11  7:25           ` Uriel
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=3e1162e60510102252y6e10ca4ejb50e6db1897cb697@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --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).