public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Der Herr Hofrat <der.herr@mail.hofr.at>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MAX_NAME in jffs2
Date: Tue, 30 Jul 2002 23:37:34 +0100	[thread overview]
Message-ID: <14897.1028068654@redhat.com> (raw)
In-Reply-To: <200207251914.g6PJEbs25931@hofr.at>

der.herr@mail.hofr.at said:
> 
>  is there a particular reson for jffs and jffs2 to have a 254
> character filename limit and ext2/ext3/reiserfs 255 (probably others to -
> excluding minix/msdos/M$) ?? There probably is hardly a case where this
> will realy hurt, but a test bit it so I wondered what the reson for this
>  254 is... 

ISTR there may have been a reason in JFFS, but I can't remember it. JFFS2 
just inherited it -- one of the few things that hasn't actually changed. We 
want to keep file names relatively short because dirent nodes can't be 
split across eraseblock boundaries.


--
dwmw2

      reply	other threads:[~2002-07-30 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 19:14 MAX_NAME in jffs2 Der Herr Hofrat
2002-07-30 22:37 ` David Woodhouse [this message]

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=14897.1028068654@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=der.herr@mail.hofr.at \
    --cc=linux-mtd@lists.infradead.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