17
JFK422
14d

Why cant I name a folder 'con' on Windows?!

Comments
  • 22
    Stay positive. Try pro
  • 17
    Legacy dos named pipe. Lpt and com1 should also be illegal for example
  • 9
    Because it's a special name, along with NUL, LPT, COM, and a few others, for old DOS special devices.
  • 50
    You're messing with ancient powers you don't understand. Yield now, or be forever Untitled.
  • 9
    jUsT uSe LiNuX dUdE
  • 12
    It's a reserved word for legacy dos, these are all reserved and windows will prevent a file or folder being named

    CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9
  • 6
    @jespersh Here be dragons
  • 13
    @Stuxnet dOn’T yOu MeAn GnU/LiNuX
  • 3
    @devTea those are the worst people tbh.

    Everyone knows what's being implied. Get off your high horse and stfu ffs
  • 3
    quick, someone boot up a Win9x machine and try to access C:\NUL\NUL
  • 6
    @Stuxnet R Stallman probably salty because most of the people mention linus but not him for linux
  • 1
    @devTea yeah because Linus did most of the work. He just used his license
  • 4
    Linux and unix have all their special files stored in virtual filesystems: /proc, /dev, /sys, etc.

    Windows [I think this started on dos] on the other hand tried to create something similar, except this was happening a long, long time ago, when computers stpred very little data and there was no need for a concept of directories. So MS reserved a set of filenames for special cases [mostly stuff you have in /dev in linux]. These filenames are in global namespace, so it doesn't matter which directory you're in. The filter applies everywhere :)

    that's a bug Windows has for decades now :)
  • 2
    @jespersh Almost died laughing
  • 2
    @netikras Story of how an ignored

    // TODO

    eventually changes to

    // DON'T FUCKING CHANGE THIS
Your Job Suck?
Get a Better Job
Add Comment