>le last word face >255 characters max for a filename >even

>>59925978
why the fuck would you ever give a file name longer than 50 characters?
it's just not practical

>>59925978
why the fuck would you ever give a file name longer than 50 characters?
it's just not practical

>>59925978 (OP)
why the fuck would you ever give a file name longer than 50 characters?
it's just not practical

>>59926037
>>59926054
>posters: 3
Fuck you that's why. This is supposed to be the "last word in filesystems," the be all end all filesystem and it has such a shitty filename limit.
>move files from MurderFS
>can't because lol filename limit

>>59926054
You didn't think about long paths, did you?

>>59926113
You didn't think those are completely unrelated, did you?

>reiserFS
XD

>>59926108
well its actually supposed to end retards like you from using absurdly long file names

>>59926356
>arbitrary limitations are good!
GNU in a gnutshell. Good thing we use 1 fucking byte for the file name, I'd hate to lose A BYTE on all my files in a filesystem designed to let you create massive volumes.

So if it's a filesystem to end all filesystems, how come it still clings onto the hierarchical paradigm of the 60s lol? How about a proper tagging system.

>>59926054
node.js and npm dependencies need that. You couldn't code a static website on zfs, because npm could not download the dependencies.

I'd rather it keep my flies safe than support a thousand character filenames

>>59926575
Neither can NTFS, so what are you gonna use? Ext fucking 3?

Fuck off pajeet

Not only Linux, OP.

Almost everywhere the limit is 255 chars.

Educate yourself.

https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits

>>59926529
Tagging is cancerous you idiot.

>>59926670
NTFS can do 30k~ characters, the Windows API can't do more than 255 though
BTRFS and Ext3/4 can do a lot too

>>59926753
Wiki articles (the same source OP used) on both NTFS and ext4 list max. filename length as 255 bytes

>>59926753
>Windows API can't do more than 255 though
What in the fuck

>>59926788
So much legacy code dating back to DOS is still in modern windows.

File: reisurmug.jpg (37KB, 435x580px) Image search: [Google]

37KB, 435x580px

>>59926670
Murder4fs supports filenames up to 3976 bytes long.

>>59926378
Give me 1(one) practical usecase of a filename needing to be greater than 255 characters.

>>59926749
Objectively more flexible than hierarchical.

>>59926817
>greater than 255 characters
Even less for unicode characters broham.

>>59926804
MurderFS is only good for /var

>>59926846
I use it for portage, faster than ext4 for that gorillion of small files (reiserfs' were designed for that).

>>59926868
>gorillion of small files
That's why I said it's good for /var

You OUGHT to have self imposed an eight character limit. If you need more than 8 characters for YOUR OWN files then you're too scatterbrained to be doing anything serious on a computer anyway.

>>59925978
Is ZFS ok for desktop?

>>59926939
Not for your boot drive, no.
For any kind of storage it's the best.

>>59925978
What is even your point? You know this is referring to the actual file name, not the absolute path? Even FAT32 and NTFS are barely better, they're limited to 255 UTF-16 code units, so their only advantage over the Unix file systems is that they can better handle non-ASCII characters - however, they end up using twice as much space for ASCII, which is what most files are going to use anyway.

Besides, there really is no reason for filenames to be anywhere near 256 or even 128 characters. Path length is far more relevant because you can have potentially indefinitely nested directories - if you need to use 128+ characters to make an unambiguous file name, it's probably time to make a subdirectory.

>>59926113
As mentioned above, this is about filenames, not paths.

>>59926753
>NTFS can do 30k~ characters
That's absolute path, not filename length.

>>59926788
Windows API also has "long pointers" and the WinMain() function has parameters that are guaranteed to always be null. Don't be surprised that it's brain-damaged.

>>59926829
Give me 1 (one) practical use case of a file name needing to be greater than 128 UTF-16 characters.

>>59926897
Is this really true? I tried to do impose that on myself for DOS compatibility, but I found it awkward, especially when naming images that I wanted to give some context to without having to create a separate text file.

>>59927051
>Give me 1 (one) practical use case of a file name needing to be greater than 128 UTF-16 characters.

Ever seen a Japanese Light Novel title?

>>59927165
>Japanese
muh compooter 4 da wite man

>>59927165
Can't say I have, but even so, surely there's an abbreviated form that could fit in 128 UTF-16 characters?

>>59927206
There is, but it's a joke about how the LN titles are more like a story synopsis than a title.

>>59927165
>>59927206
That, or some books with many authors with their name in the filename. If you start taking that away, you need some janky fuck bullshit with author names in tags and shit, and at that point you're just adding more size to every file than you would have had and you also make it a pain in the dick for people to write filesystem searching tools if they have to integrate tag shit into it.

>>59927238
Anthologies are a pretty common thing though, even outside of Japan

>>59927051
>Give me 1 (one) practical use case of a file name needing to be greater than 128 UTF-16 characters.
It's not like there's any practical use case of needing to store anywhere close to 0.01% of 256 quadrillion zebibytes of data either

>>59927267
Unless you're the NSA.

>>59927051
>is this true (... 8 limit)
No, it's just my opinion. I don't believe excessive details are necessary. If you named the file yourself they're very easy to parse.

>my 12th picture of a penguin at the zoo
>pz12.jpg
>wojak eating a hamburger
>wjbg.jpg
>a c program that draws my mother onto the screen using the framefuffer
>momfb.c

It's not easy for guests to read. But why would you want them to?

>>59927347
>>my 12th picture of a penguin at the zoo
>>pz12.jpg
>>wojak eating a hamburger
>>wjbg.jpg
>>a c program that draws my mother onto the screen using the framefuffer
>>momfb.c
Fuck you. This is why dumb faggots have shit like 2 letter variable names everywhere.

>>59927165
>japanese books invalidate the use of enterprise grade filesystems
Pinnacle of 4chan thought

>>59925978
Why the fuck does any filename need to be as long as a twitter post?

>>59927415
Damn fucking right you nigger.
Once ZFS can't fit the full title of my Angolian Finger reading intellectual erotica, I'm dumping my FreeNAS

File: 1471305346697.jpg (76KB, 480x454px) Image search: [Google]

76KB, 480x454px

>>59927347
>find an image wojack playing baldur's gate

>>59927411
Your code is not a filename. Notice that in your verbosity and carelessness you have expanded my implications into something they're not.

>>59927347
I like to use filenames to provide extra context to an image. For example if I have a picture of a warship from WWII and want to remember what ship it is, I can call it CHICAGO.JPG for the USS Chicago. But then I might also want to remember the year, so I can call is CHICAG43.JPG. But if I want to add where the picture was taken, there's really no room left. So for a lot of these I end up doing something like "USS Chicago in Brazil 1943.jpg" But something like that can't really be compressed into 8 characters.

>>59927530
>pz12
>wjbg
>momfb.c
No, it's exactly the same because you treat it the same like a retard.

>>59927530
Short identifiers are more acceptable though, since there's usually much more context. For example I commonly use something like

ParserOutput *po

for local-scope variables, and there really isn't much need to worry about remembering what "po" stands for, as long as there aren't too many other variables in the function and the function isn't too long.

>>59927533
>that can't really be compressed into 8 characters.
It can if you keep a codebook.

>>59927589
>taking work that should be done by a computer and making the human have to do it
Ah yes, Linux.

>>59927554
Are you presupposing i follow some doctrine on usage that you read somewhere?

>>59927533
CH43BZ(.JPG)
C43Z.JPG

>>59927626
>CH43BZ(.JPG)
>C43Z.JPG
Now this is autism.

>>59925978
WTF?

Why are you freaks arguing about filesystems when we don't even have good plugins for existing filesystems. You should all be out there programming application layers so that we can interface with the wide variety of filesystems in existence.

FAT32 is still in use you retards.

>>59926529

Tagging is the only sensible way to organize images. But that's the only type of file that really benefits from it.

>>59927670
>plugins for filesystems
What the fuck am I reading?

>>59926749
Objectively the best comment in this thread.

8/10

I think you guys have such an issue with an 8 character limit because nobody's forced you to trust yourselves to memorize anything in your life.

An autistic response would more likely be confusion and a desire to add copious details to their filenames, if they even had an opinion on this. Please add "ridiculous" or "overly complicated" to your vocabulary.

>>59927687
Do you not English you fucking retard. Install the plugin into your brain that enables your mind to comprehend the English language. You need to either install or develop a custom implementation of a communication layer that allows a interface between your mind and English text.

>>59927801
>Do you not
Stopped reading there.

>>59927750
8 chars is a bit low for a filename.

256 is reasonable, however it would be no more space-efficient than using a 0x00 indicator for end of filename.

The problem is that reading files is a common system operation and having a byte represent the length of the filename enables the system to simply match the specified length as opposed to having to count up to the 0x00 indicator.

I mirror the annons question: Give me 1 (one) practical use case of a file name needing to be greater than 255 characters.

>>59926753
>Windows API can't do more than 255 though

Except that wrong, you fucking mong.

>>59927833
>Stopped reading there.
Because you don't English, you fool.

>>59927869
>being this new

>>59927860
>Except that wrong
Please either install or develop an interpretation layer into your brain that enables your mind to coherently communicate Englishtically.

>>59927847
/thread

OPs argument is objectively invalid due to its impracticality as it would impose unnecessarily burdensome inefficiencies.

>>59927801
>>59927869
>>59927906
fuck off linguisto-imperialist scum

>>59927347
>>59927554
Your shitty ad-hoc hash will have lots of collisions.

>>59927677
>But that's the only type of file that really benefits from it.
Pdfs?

>>59927971
file tagging is Ballmer tier. He literally wanted to replace folder-based digital filing systems with a database.

255 characters is more than enough for any file.

E.g.
Longest word in a major dictionary
Pneumonoultramicroscopicsilicovolcanoconiosis
Length: 45

Movie-meme-word
Supercalifragilisticexpialidocious
Length: 34

Longest word Shakespeare made up
Honorificabilitudinitatibus
Length: 27

Please demonstrate a single use-case where a filename greater than 255 characters would be necessary.

>>59927988
I'm just saying it could be useful for papers and stuff.
If there was some easy to use file tagging with good performance I'd use it.

>>59927051
>>Give me 1 (one) practical use case of a file name needing to be greater than 128 UTF-16 characters.
What kind of brain-damaged shithead (other than Microsoft) uses UTF-16?

>>59928108
Sure but its not really appropriate for use as design component of a filing system due to its limited use-case. You could build your own filing system that does it, or utilize existing systems like databases to do it without having to affect normal file-systems.

>>59928186
I have the same question but for UTF-8.
The problem is that using the spec is unavoidable as most current systems force it on you.

>>59925978
>ZFS
>available on Linux
kek

fghjkl.bmp is the name of all my files

>>59928200
UTF-8 at least has good points. It's identical to ASCII for the low 127 ASCII characters, so it improves space efficiency in the common case at the expense of having variable-length code points. UTF-16 doesn't have that, but if you're going to burn space to guarantee each code point is a constant number of bytes, UTF-16 can't do that for you, you need to go to UTF-32 anyway. UTF-16 is just the worst of both worlds, less space-efficient and variable length.

>>59925978
>>59926108
>>59926037
I have an idea, can anyone tell me if this would work

you have a file system that randomly hashes filenames out with legacy support for programs that don't support it, then allow the files to have a metadata that is embedded into the file.

so lets say you have 5 files in a folder
they would be named

asdkjhfg
erjkht
sdkjfhg
sdlkjrht
lsekjfdhg

but the momeny you open it you are shown their file names

This is anime
This is not porn
This is porn
This is porn
This is trap porn

that way 2 files can have the same name that is visible they will get sorted some other way, and you never have file conflicts

a program at startup that supports this would crawl its files on initial launch and tell itself what everything is is called.

>>59928259
lets say you have 5 files in a folder
they would be named
asdkjhfg (anime)
erjkht (not porn)
sdkjfhg (porn)
sdlkjrht (porn)
lsekjfdhg (trap porn)

wtf bro.

>>59928285
examples, I can't think of file names off the top of my head that need to be longer then 20 characters, but if I think of video,

(group) name of thing - season - episode - sometimes episode title

there have been a few cases where if I didnt save it to the root directories the file could not even be downloaded because of that bullshit.

then you have images saved from websites, some of those could be 200~ characters long on their own, so moving them at all is a nightmare

What I am thinking is just a way to get small file names, and use metadata embedded to get a file name so there is no issue with names are to long. use to have this problem a lot back when I was burning discs more often where I couldn't have more then 20 characters so I had to scrub the name and all the data the name gave just to get shit to burn.

>>59928344
>there have been a few cases where if I didnt save it to the root directories the file could not even be downloaded because of that bullshit.

Windows only allows a maximum file-name + file-path of 1024 characters.

This problem does not occur in Unix based systems (Linux, Mac OS).

>>59927238
>I have to use everyone's full name in the file name instead of initials because i'm a fucking moron

>>59928344
You could also try modifying your Windows registry to allow up to 32,768 characters in the file access path.
Modify

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment:Path

Beware that not all software will be able to read and handle files correctly if their path is too long.

>>59926817
well lets see here, I can give you an example for windows
I have a drive, its called
G:\
I store porn in the porn folder
G:\porn\
I decided to sort my porn
G:\porn\Torrented\
G:\porn\Downloaded\
G:\porn\Real\
G:\porn\Drawn\

Now I save my porn I get online to torrented, and its a rar
So

G:\porn\Torrented\
we are at 18 characters
G:\porn\Torrented\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood
we are now at 129 characters
I want to extract it
G:\porn\Torrented\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood\
we are now at 240, and shit head decided to name the files something stupid too, so the first file is
G:\porn\Torrented\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood\IamtheoneandonlyfileyouwilleverneedIamajealousandangryfile - 1
we are now at 302 characters and the file decided nope, we are failing extraction, fuck you

shit happens all the time where the rar is named retardedly, the file is named retardedly, and because of the two I have to fucking manually unfuck the thing if I want it extracted.

>>59928429
>crippling your search because your filesystem is made by retards

>>59928453
0/10 troll harder

>>59928201
But it is?
https://github.com/zfsonlinux/zfs/releases

>>59928453
>G:\porn\Torrented\Fuckofflongfilenamethatistogoddamnlongtoliveholyshitwhointheirrightmotherfuckingmindthoughtthisfilenamewasgood
Do you really think that using that file name will prevent your parents from finding your trap porn?

Not a valid use-case.
I can't believe you actually tried to use porn as any kind of argument in favor of any kind of change that would benefit you.

>>59928457
Its not hard to make your own file system. How about instead of complaining on here like you think we will do something about it, you do it yourself?

>>59928517
>Its not hard to make your own file system.
It's hard to make ZFS with the current ZFS stability though.

>>59928517
They can find out when I am dead and gone for all I care, point is retarded name shit like retards, and I gave case examples where retards named shit in unreasonable ways along with websites apparently loving to use 200+ long characters for images.

as much as you want to say you don't have porn, you have porn, we are on 4chan, and we are anonymous, you grandma isn't in the corner watching what you post and you ain't picking up anyone from this site to fuck either so why pretend?

File: What the fuck did you just fucking say about me, you little bitch I’ll have you know I graduated top of my class in the Navy Seals, and I’ve been involved in numerous secret raids on Al-Quaeda, and I have over 300 confi.png (327KB, 2029x1145px) Image search: [Google]

327KB, 2029x1145px

ya nfts is so much better. And if you count the characters like I did you'll find you only come out to 220.

255 is the max in macos, although if I remember correctly you can use ascii characters, which I dont really get why windows doesnt allow

File: What the fuck did you just fucking say about me, you little bitch? I’ll have you know I graduated top of my class in the Navy Seals, and I’ve been involved in numerous secret raids on Al-Quaeda, and I have over 300 confirmed kills. I am trained in gor.png (1MB, 1459x1080px) Image search: [Google]

1MB, 1459x1080px

>>59928577
>windows doesn't allow ascii characters

elaborate troll detected

Encfs encrypts filenames in such a way that causes their unencrypted length to be limited to ~190 bytes.

Also on *nix utf-8 encoding is typically used which can reduce the length to 63 if you exclusively use exotic characters.