|
CRIP EATIN BREAD posted:im afraid of all the bad software thats going to break when they move to a case sensitive file system HFS+ can be formatted in case sensitive mode. everything is hilariously broken if you try to use it for anything non-unixy. this has to be a beta limitation, no way in hell they can ship a case sensitive FS now. I'm not sure why you would even want to.
|
#
¿
Jun 16, 2016 22:50
|
|
|
|
| # ¿ May 10, 2024 05:12 |
|
|
Pardot posted:in the docs, every time cow is mentioned but once it goes out of the way to qualify it with 'cow metadata', and the other spot is for the file/dir clone feature. it makes me think it's not cow all the time like zfs or bttrfs, just when you use the clone thing and the metadata. metadata is always cow. data is when it's needed, like when there's a snapshot retaining a copy of the original. also unlike zfs the snapshots seem to be read only, there is only one writable version. seems good enough for a file system for phones and laptops.
|
|
#
¿
Jun 16, 2016 22:54
|
|
|
Powercrazy posted:Case Sensitive File Systems are dogshit garbage. symbolic names for files are dogshit garbage for dumb humans. we should just use inode numbers for everything.
|
|
#
¿
Jun 17, 2016 02:14
|
|
|
CRIP EATIN BREAD posted:case insensitive poo poo is dumb why?
|
|
#
¿
Jun 17, 2016 02:17
|
|
|
my use case requires I have both file.txt and File.txt in the same directory!
|
|
#
¿
Jun 17, 2016 02:20
|
|
|
apparently lots of nerds are angry about case sensitivity. both Mac OS and windows have been running on case insensitive file systems since the 80s and users don't seem to have problems with it. obviously when Linux finally conquers the desktop it will show them what they've been missing all these years
|
|
#
¿
Jun 17, 2016 13:43
|
|
|
using anything oracle is asking to get sued once they sense there's enough money to be made.
|
|
#
¿
Jun 17, 2016 14:58
|
|
|
some idiots using zfs on Linux in a major deployment will get their rear end sued for using oracle patents, and their blubbering about open source is not going to help them.
|
|
#
¿
Jun 17, 2016 15:10
|
|
|
Larry Parrish posted:I know you're not that bright but Explorer features aren't part of the NTFS spec. nope Microsoft posted:NTFS supports two slightly different modes of operation that can be selected by the subsystem of the application interacting with NTFS. The first is fully case sensitive and demands that file names supplied by the application match the names stored on disk including case if the file on disk is to be selected. The second mode of operation is case preserving but not case sensitive. This means that applications can select files on the disk even if the supplied name differs in case from the name stored on the disk. Note that both modes preserve the case used to create the files. The difference in behavior noted here applies only when an application needs to locate an existing file. POSIX takes advantage of the full case sensitive mode, while MS-DOS, WOW, and Win32 subsystems use the case insensitive mode. I.e. the file system supports a fully case-insensitive use mode. it's not in the applications.
|
|
#
¿
Jun 17, 2016 18:03
|
|
|
lol drive letters.
|
|
#
¿
Jun 17, 2016 23:28
|
|
|
zfs takes massive amounts of memory
|
|
#
¿
Jun 18, 2016 00:16
|
|
|
mishaq posted:apfs is the most advanced file system ever created this is not true mishaq posted:and the best probably the best tool for the job, yes.
|
|
#
¿
Jun 19, 2016 06:39
|
|
|
BiohazrD posted:*limits entire file path to 256 characters* this is an idiocy of the Windows layer, ntfs doesn't have this limit. you can make long paths and then Windows programs will barf when they try to access it. edit: gently caress
|
|
#
¿
Jun 19, 2016 20:10
|
|
|
many years ago when I was bored at work I wrote a tool that creates an encrypted disk image in ntfs secondary resource forks. it turns out that the way ntfs permissions apply to resource forks is not exactly obvious, so I exploited a hole in the permissions of our corporate IT server to make a volume in the resource fork of some directory and hide all of my mp3s there.
|
|
#
¿
Jun 19, 2016 20:26
|
|
|
it's been a long time but I think the parent directory counted it but if you checked properties on that directory it wouldn't show it. there was no way to tell where that space was going. most tools were not able to account for it because basically nothing on Windows actually knows about the secondary resource forks.
|
|
#
¿
Jun 19, 2016 21:12
|
|
|
'streams' is what ntfs calls them, but nothing in Windows really uses them. IIS had an exploit for years that allowed you to fetch the source for any file if you specified the main data stream in the URL https://www.exploit-db.com/exploits/19118/
|
|
#
¿
Jun 19, 2016 21:17
|
|
|
if it had live metadata like beos that would be amazing.
|
|
#
¿
Jun 20, 2016 14:47
|
|
|
|
| # ¿ May 10, 2024 05:12 |
|
|
BangersInMyKnickers posted:who cares if you tack a few ms on to the front of a file access request for a file server? the overhead is imperceptible to the user. I wouldn't advocate it as the default filesystem mode, but it would be useful for file server volumes when your users try to concurrently access files and your server can't handle a fraction of the load it previously could because of the compounded overhead they will care and so will your boss, and eventually you, too.
|
|
#
¿
Jun 24, 2016 19:33
|
|