>Current state of Windows

current state of NTFS*

File: linux.png (299B, 129x103px) Image search: [Google]

299B, 129x103px

>Current state of Linux

>>59225711
BTFO

>>59225711
I see no problems :^)

>>59225711
Cool, a blank slate! I can add anything I want!

File: 2017-03-03 17_39_02-_g_ - Technology - 4chan.png (16KB, 425x221px) Image search: [Google]

16KB, 425x221px

congratulations, you can successfully use colons in filenames if you use linux.
good job.

>>59225760
You could, but you won't because you don't know how to fix it when your ``custom'' work starts to burn.

>>59225706

>filesystems aren't virtual

>>59225789
at least I'm ABLE to fix it

File: 1485691279065.webm (3MB, 1280x720px) Image search: [Google]

3MB, 1280x720px

>>59225692
>>59225711
>t. mactoddler

>>59225692
worse, if you somehow manage to get a file with those characters in its name, windows won't let you touch it, even to rename it.

>>59225890
Literally bullshit. If you attempt to download such a file, Windows will just omit the illegal characters.

>>59225973
I have an external hard drive with some music files copied from a linux computer. Windows can't open or do anything on those files if they had unsupported characters.

>>59225782
linux is a kernel, not a filesystem

>>59226057
windows doesn't touch the files because linux is leprosy

>>59226057
linux is a kernel, not a computer

>>59225706
/thread

>>59226101
Windows is a filesystem, not a character.

>>59226057
>an OS can't access files on an unsupported filesystem

Really gets those neurons firing.

>>59226057
>Windows can't use an unsupported file system
Really activates your almonds

>>59226057
it can't force rename them in any way, shape or form either.
cant be done via cmd or powershell, or directly, the fs won't even touch it

>>59226191
>>59226214
you can do this just by mounting an NTFS windows drive and copying a file with colons or question marks into it. the files will show up in explorer but you won't be able to touch it. the underscore replacement is done by windows, not the file system.

>>59226107
>linux is leprosy
Windows is aids.

>>59225973
I once accidentally renamed a folder "res" on Windows and had to reinstall the OS to delete it.

>>59227865
Why?

File: smug_sanae.png (176KB, 393x393px) Image search: [Google]

176KB, 393x393px

>>59225782
>he doesnt know about \ or ""
obviously your too retarded to use GNU+Linux

File: lookimbeingproductive.png (3KB, 129x103px) Image search: [Google]

3KB, 129x103px

>>59225711
[every desktop environment]

>>59225711
>what happens when you fuck up your xorg config after you try to rice your DE

>>59225873
What movie

>>59228876
the tv comedy show Silicon Valley. it's at the end of some episode
you should watch it

>>59228969Thats not silicon valley i have seen the whole thing

>>59229039
do you not see the pied piper logo on the background screens? it's at the end of some episode so it's probably past the ending credits too

>>59229057
Oh

>>59229085
s03e09 btw

File: IMG_9134.jpg (51KB, 1200x630px) Image search: [Google]

51KB, 1200x630px

>>59225692
Basically Windows has always blown ass and as the poo coders make up more of the team it will go further down the shitter.

There is no stopping this.

>>59225706

I have plenty of files with those forbidden characters in their names in two NTFS volumes I use with GNU/Linux, so you're basically retarded.

>>59229604
The problem comes when you try to rename them anon. It's Windows that's retarded.

>>59225692
Meanwhile one of my programs wasn't working on Linux and produced files with non-displayable characters.... And they're still valid.

What happens if you make a file with a : on Linux and send it to a windows computer?

>>59226230
What if you read the file allocation table, determined all sectors containing the file, read those sectors into memory directly bypassing the file system, wrote them into another file in the correct order, and applied the correct file extension and permissions.

Could you reconstruct the file in a way Windows could then interact with it?

>>59225782
>mkdir/touch "\filename(). []"

>>59229915
Windows barfs and refuses to open, rename, delete, or do anything at all to the file.

I found out about that years ago when my laptop was dual-boot with a shared partition and I took a screenshot in Linux and saved it there, not noticing that the default filename includes colons.

>>59229133
kek i have'nt seen s3 yet

>>59225692
>>59225706
I got a question,


How will wincucks ever recover?

>>59228715
>Not using wayland

>>59225782
you can use any character except forward slash and the null byte. obviously they need to be escaped in shell commands.

>>59225692
Better than current state of Linux:
>make capitalization and special characters work in filenames
>be too pussy to ever use capitalized letters or special characters (like spaces) in filenames

>>59231820
>except forward slash
But you can use the forward slash in Linux filenames. As well as the backslash.

>>59228442
You can always tell the scrubs by those who don't know the difference between console, terminal, and shell.

>>59232052
linux is a kernel; it doesn't care about filenames, the filesystem cares

get outta here, tech illiterate

>>59232072
doesn't it fuck with stuff because of directories?

>>59232090
Hey there, Autist. Commonly, when we refer to 'Linux', we don't actually mean the Linux kernel itself. We mean Linux-based operating systems for which 'Linux' is just a shorthand.
Hope it helped and prevents you from creating embarrassing posts like that in the future. No need to thank me, I am here to help :)

>>59232100
I think I've seen someone on /g/ use it. (For folders called '/g/', 'a', etc.). After a quick search I am not so sure any more. But it shouldn't matter any more than space or other special characters.

Actually Windows is the problem. NTFS can handle it just fine. Try making a program that always prefixes "\\?\" to paths. It makes Windows pass the path to the filesystem driver instead of trying to parse it like a retard.

Windows tools like msys2 have no trouble with paths with, say, ? in them. I dug deep into the msys2 codebase and found it uses the prefix like I described.

I actually managed to submit this as a bug report to the GitHub for Windows team. Their tool can't display full Unix paths which are ubiquitous for obvious reasons. They emailed me back and said they'd take a look... and didn't.

>>59232989
>For file I/O, the "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system.


neat

>>59229586
Yes

>>59229586
That error screen makes my blood pressure rise