From: Steve Youngs <sryoungs@bigpond.net.au>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Increase recursive symlink limit from 5 to 8
Date: Sun, 11 Jan 2004 17:01:01 +1000 [thread overview]
Message-ID: <microsoft-free.87isjj0y1e.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <2flllofnvp6.fsf@saruman.uio.no> (Petter Reinholdtsen's message of "Sun, 11 Jan 2004 02:03:01 +0100")
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
* Petter Reinholdtsen <pere@hungry.com> writes:
> Linux: Symlink limit seem to be 6 path entities.
> AIX: Symlink limit seem to be 21 path entities.
> HP-UX: Symlink limit seem to be 21 path entities.
> Solaris: Symlink limit seem to be 21 path entities.
> Irix: Symlink limit seem to be 31 path entities.
> Mac OS X: Symlink limit seem to be 33 path entities.
> Tru64 Unix: Symlink limit seem to be 65 path entities.
> I really think this limit should be increased in Linux. Not sure
> how high it should go, but from 5 to somewhere between 20 and 64
> seem like a good idea to me.
6 does seem pretty low. What was the reason for setting it there? Is
there a downside to increasing it?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-11 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 23:12 [PATCH] Increase recursive symlink limit from 5 to 8 Petter Reinholdtsen
2004-01-11 1:03 ` Petter Reinholdtsen
2004-01-11 7:01 ` Steve Youngs [this message]
2004-01-11 9:37 ` Peter Osterlund
2004-01-11 9:49 ` Arjan van de Ven
2004-01-16 0:45 ` GOTO Masanori
2004-01-16 0:56 ` Måns Rullgård
2004-01-16 1:25 ` viro
2004-01-16 15:46 ` Andries Brouwer
2004-01-16 3:08 ` Steve Youngs
2004-01-11 12:10 ` Felipe Alfaro Solana
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=microsoft-free.87isjj0y1e.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox