From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 30 May 2004 01:56:35 +0200 From: Tristan Seligmann To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: Re: [9fans] acme: some thoughts about design Message-ID: <20040529235635.GA20444@mithrandi.za.net> References: <81132473206F3A46A72BD6116E1A06AEAD0457@black.aprote.com> <20040529165834.GA16038@mithrandi.za.net> <018b01c445cf$17086730$347e7d50@SOMA> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <018b01c445cf$17086730$347e7d50@SOMA> User-Agent: Mutt/1.5.6i Topicbox-Message-UUID: 8d6fb9aa-eacd-11e9-9e20-41e7f4b1d025 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 30, 2004 at 00:48:40 +0200, boyd, rounin wrote: > > really has 1 or 2 >=20 > run du -a lately? The problem is, if I want to associate a file with, say, "computers" and "vaccuum cleaners", how do I layout my filesystem? (let's say the file is a write-up about computer-controlled vaccuum cleaners) > > It may be a great low-level implementation, but being > > able to say "find the e-mail I wrote to Timothy last week" is a lot more > > useful to the user. >=20 > really? mbox/Timothy/* or mbox/Timothy/YYYY/MMDD/* Ok, now what about "all work-related e-mail I wrote about cars last month"? All of these queries can be "displayed" via a hierarchical file view, but not simultaneously; you could of course build multiple "views" using symlinks or unions or similar, but that's what I'd consider "higher-level". --=20 mithrandi, i Ainil en-Balandor, a faer Ambar --XsQoSWH+UP9D9v3l Content-Type: multipart/mixed; boundary="upas-gricbbghwoszywnyibdwoecoxa" Content-Disposition: inline This is a multi-part message in MIME format. --upas-gricbbghwoszywnyibdwoecoxa Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@ethel: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline --upas-gricbbghwoszywnyibdwoecoxa Content-Type: application/octet-stream Content-Disposition: attachment; filename="signature.asc.suspect" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAuSMzpNuXDQIV94oRAniKAJ9JFHoi3LyNeERKi08yEEV5zum5AgCeO3cR LQwylAh3aXdh8VPYLIWSfPs= =rUWi -----END PGP SIGNATURE----- --upas-gricbbghwoszywnyibdwoecoxa-- --XsQoSWH+UP9D9v3l--