| To: | darren.miller@xxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS v1.1 and Linux |
| From: | Ian Cumming <ian@xxxxxxxxxx> |
| Date: | Thu, 16 May 2002 05:00:41 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <OF41E2D436.A3E59BF8-ON80256BBA.004A8AA0@xxxxxxxxxxxxxxxxxxx> |
| References: | <OF41E2D436.A3E59BF8-ON80256BBA.004A8AA0@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
Hi, Couldn't you use XFS file attributes to store these longs strings for each file name? Just a thought. Ian. On Wed, May 15, 2002 at 02:37:09PM +0100, darren.miller@xxxxxxxxxxx wrote: > Now, the requirement comes in, due to a rank amateur creating a computer > generated system > which creates files in excess of 400 characters in filename length. -- Ian Cumming, ian@xxxxxxxxxxxxxx "The number of Unix installations has grown to 10, with more expected." -- The Unix Programmer's Manual, 2nd Edition, June, 1972 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Are these errors bad? xfs_repair finding errors., Quentin Arce |
|---|---|
| Next by Date: | Re: xfs_ncheck shows only one filename per inode, Steve Lord |
| Previous by Thread: | Re: XFS v1.1 and Linux, Ragnar Kjørstad |
| Next by Thread: | Re: XFS v1.1 and Linux, David Lloyd |
| Indexes: | [Date] [Thread] [Top] [All Lists] |