Re: [DCP-o-matic] DCP for Linux

A bit of context wrt inode size of 128 bytes; these couple of paragraphs were written in runes in the year of 2013: /// The default inode size for EXT2/3 filesystems changed years ago (from 128 to 256 bytes). The motivation was to be able to store extended attributes. In Digital Cinema context noone should care, really, but there's a catch: Systems with 2.4 series linux kernels won't be able to mount filesystems with inode sizes > 128 bytes at all. In linux history terms the 2.4 series is the middle ages. Noone sane should be running kernels that old. Fact is there are some systems out there which do. These are abandoned legacy systems. Their vendors don't care to upgrade them. Their users are not eager to spend a couple of K's again. So if you don't want to run into issues you'll want to use 128 bytes for inode size, period. Yes, this is 2013. Most userland FS tools won't even let you tweak the setting. Its relevance died that far back. mkfs.ext2 and mkfs.ext3 - here we come! One thing these vendors are rather tight-lipped about: Linux 2.4 series kernels carry a long list of vulnerabilities. These systems are not at all safe or able to withstand even half-serious snooping since a long time. If I were Fox or Warner or Sony I'd make sure these boxes either get updated or blacklisted fast. /// My theory and hope, or rather, game plan at the time was that userland would increasingly ignore a setting from the stone ages and force those systems out of the market. I don’t have any numbers to check how that worked out. Got a feeling, though, it just didn’t and the affected systems are still out there somewhere. Waiting. Slowly filling their caves with bones of the newborns they get fed with every now and then. Patiently preparing to grab you by the throat :) Wolfgang _______________________________________________ DCPomatic mailing list DCPomatic(a)carlh.net http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic