Where were you when linux was kill?
>>59126768
>not using ext4
>being retarded
>can't even use an OS
>literally automatic install option on the most used distros would prevent this
Its de OSes foolt, guyes, belibe meh! Looonicks is kill!
>>59126768
NTFS has the exact same issue, faggot.
Windows XP will let you copy that file.
You will not be able to move or delete the file.
Reading the file could be tricky.
>>59126890
Not on Windows 10 it doesn't.
>>59126883
I used the default configuration for encrypted ubuntu, you fucking faggot
>dat filename
ALWAYS
UNIQUE
TOTALLY
INTERESTING
SOMETIMES
MYSTERIOUS
>>59126957
It's tied to the filesystem, a different OS won't change that fact. The Win10 option makes it so only that OS ignores the issue, accessing it from another computer that has NTFS support, like when trying to rescue a failing hard drive or when someone with this option enabled putting a file with it's pathname too long on a USB will result in the files being unable to be overwritten, moved, etc.
>>59126957
Windows 10 uses NTFS you dumbfuck.
>>59127106
And Windows 10 doesn't have this limit.
God damn lintards are retarded.
>>59127125
It does have it
>>59127125
Pls read >>59127101
>>59126969
Lol, fag
>>59127159
So basically Windows 10 aliases the filename with a shorter filename in the filesystem?
>>59127157
Win32 does, not NTFS itself.
http://msdn.microsoft.com/en-us/library/aa365247.aspx
I was at home using freebsd when Theo rang
'Linux is kill'
no
>>59127157
>Starting in Windows 10, version 1607,MAX_PATHlimitations have been removed from common Win32 file and directory functions. However, you must opt-in to the new behavior.
All modern filesystems have a filename limit of either 255 bytes or 255 characters.
>Veracrypt
>>59127232
op's filename isn't anywhere close to 255 characters.
>>59127226
>>59127185
>A long file name is considered to be any file name that exceeds the short MS-DOS (also called 8.3) style naming convention. Typically, Windows stores long file names on disk as special directory entries, which can be disabled systemwide for performance reasons depending on the particular file system. When you create a long file name, Windows may also create a short 8.3 form of the name, called the 8.3 alias, and store it on disk also. This 8.3 aliasing can be disabled for a specified volume.
NTFS still does, it just creates an alias with that win10 option enabled. NTFS is still garbage.
>>59127255
I don't see the full filename, in the picture.
>>59127255
That includes the full path.
>>59126768
using linux
>>59127257
Do you know what the MS-DOS 8.3 naming convention even is?
>>59127274
>filename includes the path
oh man.
Encfs severely reduces the amount of characters you can use in a filename. Also will be even worse if you use Unicode characters, since they could take up to 4 bytes each.
>>59127237
What is wrong with it?
>>59127079
It's just a taglist you fucking retard.
>>59127294
Would using dm-crypt with luks help?
>>59126768
You can't kill something that was already dead.
give me that cute wallpaper
>>59129820
Yes
Apple Macbook doesn't have this problem
>>59126768
different filesystems have different restrictions on filename length, news at 11
>>59130886
Go to wallhaven. I got mine from there and you might find more wallpapers like this if you input the correct tag to search.
Why is there a limit for the file path? I've never understood that. Why the fuck hasn't someone increased it to about 32k characters or something?
I always wondered why Linux users were so obsessed with Windows path length and now I know why, just like everything else they lie about is because they are mad that they can not do it as good as Windows can.
>>59126768
Maybe you shouldn't label your shitty chinese porno images with an epic monologue instead of a much simpler file name.
>>59133712
The website automatically tags them faggot. Also it doesn't excuse the encfs to pull bullshit like this
>>59126768
LINUX IS COMMUNISM YOU RETARD NIGGER!
>>59126768
Konachan.com - 218369 2girls blonde_hair dacchi green_eyes long_hair purple_eyes purple_hair seifuku tsurumaki_maki vocaloid voiceroid yuzuki_yukari.jpg
Not even long. This error have to do something with the veracrypt or something, anyway how could you keep it in /home in the first place...
> linux was kill
Linux survived. As usual.
>>59126768
>he used his phone to take a picture of his computer screen
Where were you when OP was a faggot?
>>59135792
I also thought it had something to do with veracrypt so I packed the containers contents into a .tar.gz file and tried to unpack it in the same directory, only to receive the same error.
>>59126768
Linux was never alive to begin with. Meme OS.
>>59134797
>I'm too much of a dipshit to keep my file names at a reasonable length
>a bloo bloo
>bloo
whree was you when windows is kill
>/g/ is NOT your personal tech support team or personal consumer review site.
>be OP
>be retarded and not understand how filesystems work
>make a tech support thread on /g/
>insult guhnoo + linux
>everyone immediately responds with advice
>>59135973
>I am too much of a lifeless dipshit that I take my time to edit thousands of file names.
Wew how's the neet life treatin' you?
>>59136005
I have a job therefore don't spend all day downloading shitty anime pictures, and have the good sense to not save anything with file names longer than my arm you dingus.
>But I can't do X!
>Some reply saying you don't need it
Everytime.