From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: link() security
Date: Mon, 15 Apr 2002 20:01:43 -0400 [thread overview]
Message-ID: <20020415200143.E431@marta> (raw)
In-Reply-To: <E16xFtQ-0007Gp-00@the-village.bc.nu> <3CBB5ECB.2040002@zytor.com>
Scribbling feverishly on April 15, H. Peter Anvin managed to emit:
[schnip]
> The point was mostly that storing mail in a (basically) unstructured
> flat-file format isn't really consistent with the operations you want to
> perform on it. I didn't mean the directory/file format was necessarily
> the ultimate solution, only that (a) it works better than mbox, (b) it's
> been around for a long time.
[nod]
I suppose it made sense back when we made our 1s and 0s by hand, but
whoever (would dare) take credit for "designing" the UNIX mbox "format"
needs a remedial course if file format design.
K
--
Are you ever going to do the dishes? Or will you change your major to biology?
next prev parent reply other threads:[~2002-04-16 0:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 23:21 link() security xystrus
2002-04-12 1:15 ` Chris Wright
2002-04-13 16:59 ` Alan Cox
2002-04-13 17:02 ` xystrus
2002-04-14 1:49 ` Chris Wright
2002-04-15 14:44 ` Patrick J. LoPresti
2002-04-15 19:25 ` H. Peter Anvin
2002-04-15 22:48 ` Alan Cox
2002-04-15 23:05 ` H. Peter Anvin
2002-04-15 23:28 ` Alan Cox
2002-04-15 23:14 ` H. Peter Anvin
2002-04-16 0:01 ` Kurt Wall [this message]
2002-04-15 21:41 ` xystrus
2002-05-06 5:00 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2002-04-13 17:48 Hank Leininger
2002-04-15 19:36 Chris Adams
2002-04-15 19:55 ` H. Peter Anvin
2002-04-15 20:36 ` Patrick J. LoPresti
2002-04-16 1:37 ` H. Peter Anvin
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=20020415200143.E431@marta \
--to=kwall@kurtwerks.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.