• TheTechnician27@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        arrow-down
        1
        ·
        1 month ago

        NTFS in general has a bunch of ridiculous, archaic restrictions that a more modern-ish one like ext4 doesn’t. Does NTFS still not allow you to use a question mark in your filename?

            • Bizzle@lemmy.world
              link
              fedilink
              English
              arrow-up
              6
              ·
              1 month ago

              Well if you put it in like that it would give an error. But if you used the right slash you can kiss your home folder goodbye probably. Maybe rm ./~ would work

              • Peruvian_Skies
                link
                fedilink
                arrow-up
                9
                ·
                edit-2
                1 month ago

                ~ resolves to your home folder only if it’s at the beginning of a path. /~ isn’t the same as ~. Go ahead and test it with something other than rm if you don’t believe me (this is the Internet, I could be lying).

        • pyre@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          the question mark is a wildcard, so is asterisk. slashes are used in paths. characters you can’t use usually have implications for the OS. otherwise you can name your file pretty much anything.

          • mke@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 month ago

            Yeah, I think it’s just funny comparing it with the usual situation on Linux, where there’s even less restrictions. I believe you can actually put a newline in a file name, for example, though I’ll need to check and come back later.

            I’d need to rename a massive amount of files if I ever wanted to go back to Windows.

            P.S. yup. Generally, just avoid /, null, and you’re good to go.