>tfw you can't put a dot in the end of a folder name on Windows
>tfw "prn" is still a reserved file name
but you can
>>47080263
you can't
>>47080275
use powershell or cmd
>socialist pro-Russia nutcase
>"intellectual"
I hope you realize her party is basically using her as cheap eyecandy in hopes of getting some votes.
>>47080234
no, I'm sorry
you aren't allowed to have a president who is That hot
>>47080287
>use powershell or cmd
no
>create directory called BANK:PASSWORDS on NTFS partition mounted under Linux
>watch skiddies go nuts trying to open it.
>tfw linux retards decided to use part of the filename/foldername as attribute indicator for hidden
>The dot first retardation
>>47080319
oh snap
fel when can't name a file "con" on windows.
ITT: Baby's first wikipedia article about reserved names
>2020
>can't have colons, slashes and backslashes in file names
thanks human civilization
>>47080343
>linux retards decided
Do you even history of computing? That rule came from a historical implementation detail from the original unix "ls" command and has been a widely accepted standard for hiding files since then.
>>47080573
>1391898926012.jpg
http://niceme.me/
>>47080573
and?
>oh, there this thing that does not show stuff?
>Lets not fix it, lets just use it as standard to have part of the fucking filename decide file attributes
>and I also have this great idea, lets just then dump all of the shit in to home folder, just hide it with the dot
>now lets wait 20 years for someone to come up with .config
>>47080573
>Helping NASA deploy rovers
that would be Ganoo/Loonix
>>47080669
The good part about the dot notation is that it actually works among different file systems.
>Have a working standard for hiding files that everyone follows
>Be Microsoft
>Do things different without any reasons
>Clone software repository on Windows
>Download any software tarball
>Hidden files of repository aren't actually hidden and visible fucking everywhere
>Bravo Microsoft.
Good thing I don't have to use that crap.
>>47080937
>Have a working standard for separating file paths into directories
>Be Microsoft
>Do things different without any reasons
>Quote a filepath on Windows
>"C:\\Program Files\\Foo\\Bar\\foobar.exe"
>Bravo Microsoft.
Good thing I don't have to use that crap.
>>47080253
So is
>con
I wanted to put my devious plan in there.
>tfw putting a dot at the beginning of a directory makes it hidden
>>47080573
K
>>47081135
Those Thinkpads are all running Debian Squeeze LTS now.
>Windows and GNU/Linux are suitable for running systems that human lives directly depend upon
>OS X isn't
>>47081135
macbooks would overheat and brick in space
airflow is weird in 0G
>>47080573
Maybe nasa would get their budget back if they'd stop blowing it on shitbooks
>>47080287
I can't believe how shitty cmd is compared to any nix terminal.
>>47080234
You can but explorer tells you it's a fucking stupid idea.
>>47080275
Hipster.
>>47080319
>>47081275
List one feature it doesn't have compared to bash or csh (if you use any others you might as well kill yourself).
You can't.
I can.
>>47081152
>running systems that human lives directly depend upon
No they aren't holy shit. All of the life support systems are either mechanical or running a RTOS.
>>47081166
wouldn't the New Macbook be best then? It doesn't require airflow. And if you get hit in the head with it in 0g, it won't hurt as bad because it's so light.
>>47081315
>>List one feature it doesn't have compared to bash or csh (if you use any others you might as well kill yourself).
If we're comparing terminals, resizing windows terminal emulator is a huge hassle and there is no support for utf8 (there is, but it's so broken you can's use it).
If we're talking about shells, the list is infinite. But if you want me to list one thing, no regular expressions.
>>47081356
Which most of them are unix compliant
>>47081275
>I can't believe how shitty cmd is compared to any nix terminal.
Reminder that windows users also think OS X is less functional than Windows.
>>47081275
>I can't believe how shitty cmd is compared to any nix terminal.
That's why powershell has been around since 2006.
>>47081388
And so is Mac OS :^)
>>47081275
That's why powershell exists. Microsoft doesn't change cmd to keep backwards compatibility or some shit
>>47081135
Imagine how ISS would have looked like if Apple built it. No wires anywhere, everything smooth and aluhhminuhm and glowing apples everywhere, astronauts in tite latex suits, 27" iMacs floating around in 0G. And of course dongles shipped from earth for $79 + $127,899 shipping, $174,999 overnight. I wish someone would shoop it.
>>47081315
dd?
>>47081315
every terminal based app, wget, ls, lolcat
>>47080669
>and?
Linux developers obviously got nothing to do with that decision.
$$>>47081603
ssh
>>47081574
Untill something breaks and they have to take the whole fucking station to the applestore.
No thanks.
>>47081574
>>47080306
What has this world come to
She didn't even say she supports Putin
All she said was that she would speak with him as president and try to improve relations
>>47080306
>socialist pro-Russia
That's an oxymoron, blud.
>>47081704
But they would give you a new ISS, anon.
>>47081711
kek, not far from truth probably
>>47080234
nor the start
but it's an explorer limitation, not a windows or ntfs one
it counts "file." as a file with an empty extension (unsupported), and ".file" as a file with no name (only an extension, also unsupported)
>>47081782
i'd argue it's a pleonasm
>>47080234
Try making a folder with the following name :GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
>>47081336
Cool, but can you make a folder named "con" ?
>>47080234
>Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not. However, it is acceptable to specify a period as the first character of a name. For example, ".temp".
https://msdn.microsoft.com/en-us/library/Aa365247#paths
CAPTCHA: ubutu
>>47082481
>>47081087
what happens if i copy this dirs and also create dir prn and put them on flash drive?
>>47080287
>being forced to use CMD prompt to create a folder with a . at the end
literally worse than loonix
>>47080275
>>47080234
What now?
>>47081135
Those two pipes going up his shorts, astronauts water cool their balls. Fucking next level.
>>47082507
yes.
>>47081166
macbooks overheat under normal conditions
>>47082841
how ?
shoop? custom explorer? hacked fonts?
>>47082932
This is true.
It just werks.
>>47081166
Airflow isnt weird at 0Gs
Its weird at vacuum
>>47083368
manually change the MFT record of that file
>can't put : and / in the filename
>can use the Japanese characters for it
>>47083368
>>47083511
None of the above. The trick is to put an alt+255 character after the . at the end. The blank file is just an alt+255 alone. Disallowed-name dirs were created like mkdir \\.\C:\HAXX0R\CON -- using \\.\ paths allows use of those names.
>>47083599
Putting the alt+255 defeats the object of trying creating a folder called con. By doing that the folder is displayed as "con", but is in fact "con ", thus meaning that the folder isnt called "con" (if that makes sense).
Will have to try the MFT entry edit sometime.
>1436 AH
>Using NTFS
كافر
>>47083711
No, my CON is actually named CON. I didn't binary hack my MFT either.
Do this:
mkdir \\.\C:\Users\anon\Desktop\con
No alt-255 trickery, just bypassing Win32 legacy name checking by using an NT path.
>>47081553
>Mac OS
>RTOS
pick one
