If you ever tried listing a directory with a lot (10,000+) of files in it, I’m sure you know how annoyingly slow ‘ls’ can be. Turns out there is a simple way to make it better. Have a look at the “When setting an environment variable gives you a 40x speedup” blog post.
Or just do the following:
This will disable colors on the executable files, setuid/setgid bits, and capabilities.
“Files Are Hard” is one of those articles that show how complex even the simplest of things are. How complex is writing to a file? Well, quite. Especially if you want to make sure there’s no corruption in case of a crash. It goes both over the theory and practice, looking at different file systems.
This was only a matter of time … gitfs – version controlled file system:
gitfs was designed to bring the full powers of git to everyone, no matter how little they know about versioning. A user can mount any repository and all the his changes will be automatically converted into commits. gitfs will also expose the history of the branch you’re currently working on by simulating snapshots of every commit.
Here is a brief feature list:
- Automatically commits changes: create, delete, update files and their metadata
- Browse through working index and commit history
- Merges with upstream by automatically accepting local changes
- Caching commits reduces the memory footprint and speeds up navigation
- Reduces the number of pushes by batching commits
πfs – the data-free filesystem!
πfs is a revolutionary new file system that, instead of wasting space storing your data on your hard drive, stores your data in π! You’ll never run out of space again – π holds every file that could possibly exist! They said 100% compression was impossible? You’re looking at it!
Linux Weekly News notifies:
At the June 8 meeting of the Fedora engineering steering committee (FESCo), the group decided that Fedora 16 will ship with Btrfs as its default filesystem. Btrfs is a relatively new copy-on-write filesystem with many interesting features such as read-only and writeable snapshots, multiple device support for RAID, online filesystem defragmentation, and more, though it is still marked as experimental in the kernel. “AGREED: Feature is approved. Will add some base critera to the page to be met by feature freeze. This is just a swap of ext4 to btrfs for default, not change of lvm or other parts of default.“
As noted in the comments, Btrfs is marked as an experimental feature in the kernel. As also noted in the comments, many other features which were marked as experimental were brought into production and that seemed to work fine.
While I personally have no knowledge of Btrfs stability or readiness for production, I am slightly worried by that move. First of all, ext4 – current default filesystem – works fine for me and for everyone I know. Why fixing something that works? It seems that Btrfs is a better choice for server platforms. And while Fedora is mostly used on the desktop, it is still a testing platform for Red Hat distribution which is, in fact, a server-oriented line of products.
On another note, Fedora 15 upgrade was a bumpy ride. Again, not just for me, but for everyone I know. Switch to Gnome3, sysctl, and other changes didn’t quite work out of the box for many people. Btrfs might do the same. I think it’s better to push such a change at least to Fedora 17. Let people recover slightly. Focus instead on fixing things which are broken. Let people regain confidence in Fedora distribution and its upgrade paths. Please.