From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: link() security
Date: 15 Apr 2002 12:55:11 -0700 [thread overview]
Message-ID: <a9fb6v$d2f$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020415143641.A46232@hiwaay.net>
Followup to: <20020415143641.A46232@hiwaay.net>
By author: Chris Adams <cmadams@hiwaay.net>
In newsgroup: linux.dev.kernel
>
> Once upon a time, H. Peter Anvin <hpa@zytor.com> said:
> >Not to mention the fact that the single file mailbox design is itself
> >flawed. Mailboxes are fundamentally directories, which news server
> >authors quickly realized.
>
> Funny that news server authors realized that storing messages in files
> by themselves is a bad idea, while at the same time mail server authors
> realized that storing messages together in a single file is a bad idea.
> Which one is right? Both? Neither?
>
It depends on your access patterns. Newer news server use what I
would classify as custom filesystems (which is what binary databases
are, by and large) rather than "single files."
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-04-15 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 19:36 link() security Chris Adams
2002-04-15 19:55 ` H. Peter Anvin [this message]
2002-04-15 20:36 ` Patrick J. LoPresti
2002-04-16 1:37 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-04-13 17:48 Hank Leininger
2002-04-11 23:21 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
2002-04-15 21:41 ` xystrus
2002-05-06 5:00 ` Albert D. Cahalan
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='a9fb6v$d2f$1@cesium.transmeta.com' \
--to=hpa@zytor.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.