Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
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?
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.
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.
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?
Bro you either know what the fuck is in that file, or you shouldn’t be renaming it in the first place.
Unnamed(7)FinalFinalThisTimePlease?
Apparently not.
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.
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.