monline

Since this is invoked by one of the startup scripts of your OS, the exact behaviour might be a bit different depending on the implementation of your OS (and the specific OS version, eg. Ubuntu had this feature in /etc/init.d/checkfs.sh for quite a long time, then moved it somewhere else). The point is that at some step of your boot process the fsck tool is started with a set of commandline parameters. Eg. Ubuntu Hardy executes something like this:

One comment on the article: in Ubuntu Precise Pangolin (v12.04) the libmtp is already the latest (v1.1.3) and Nexus works with it (ie. you can write to the device too) out of the box.

The linked page describes it pretty well. However in case of ICS the /dev filesystem has changed a bit. The boot and recovery images are not available as /dev/mtd/mtd1 (etc.) anymore. You've to look for them here: /dev/block/platform/omap/omap_hsmmc.0/by-name/boot.

The respective Wikipedia article lists most of these already:

• Ext2 Installable File System For Windows: for Windows NT4.0/2000/XP/2003/Vista/2008, read+write access to Ext2/3/4 (the latter two only without journal!), drive mapping supported
• DiskInternal's Linux Reader: for Windows 95, 98, ME, NT, 2000, XP, 2003 Server, Vista, read-only, no drive mapping (a filebrowser UI is available)
• Ext2Fsd: for Windows 2k, XP, Vista and Win7, read+write for Ext2/3/4, journals supported, drive mapping supported
• Explore2fs: for various Windows versions, read-only access to Ext2/3 (probably Ext4 wo journal), no drive mapping (filebrowser UI)
• Paragon ExtBrowser: for Windows XP and Vista, read+write to Ext2/3 (probably 4 wo journal), no drive mapping (access through a special folder in Windows Explorer via Windows Name Space Shell Extension)
• Ext2Read: for various Windows versions, read-only access to Ext2/3 (probably Ext4 wo journal), no drive mapping (filebrowser UI)

The post describes techniques useful if you try to mount a filesystem that has serious errors. In the blog (and referenced older posts) Ext3 and Ext4 are both covered.

"GlusterFS is a scale-out NAS file system developed by Gluster. It aggregates various storage servers over Ethernet or Infiniband RDMA interconnect into one large parallel network file system. GlusterFS is based on a stackable user space design without compromising performance. It has found a variety of applications including cloud computing, biomedical sciences and archival storage. GlusterFS is free software, licensed under GNU AGPL v3 license."

Sounds quite impressive.
Here're a few more links:
http://www.gluster.org/about/
http://www.gluster.com/products/glusterfs/

It remains to be seen whether the recent acquisition of Gluster Inc. (by Red Hat) interferes with the open-source product's development/availability or not.

Running fsck.ext3 with the -c checks the filesystem for read errors and creates a (new) bad block list. However what if you want to revert this operation, because you want to access files that occupied these bad blocks? Here's the answer: fsck.ext3 -L /dev/null [device]

"Double Commander is a cross platform open source file manager with two panels side by side. It is inspired by Total Commander and features some new ideas."

Up to date this commander seems to be the best Total Commander clone for linux.

"Imagine you have made a world tour in August 2009 (summer time!) and you have used your digital photo camera to create pictures, videos and voice recordings.

In this guide I will not refer to these items by their specific characteristics (photo, video, audio), but simply regard all of them as "files." Secondly, we assume that the files are saved on a storage medium, which is very likely formatted as FAT (as specified in the DCIM standard for digital cameras).

You have created three files in America/Los Angeles (UTC-0700), three files in your hometown Europe/Vienna (UTC+0200) and three files in Asia/Bangkok (UTC+0700), and at the end of the summer, you return to your hometown Europe/Vienna.

This guide shows you how to correctly bring your files' timestamps from a local time zone-based file system (such as your external flash drive, formatted as FAT32) to a file system using coordinated universal time (UTC) (such as your internal hard disk, formatted as HFS+) using the Finder on MacOS X."

Actually this guide is relevant not only for Mac OS X users, but everybody involved with files that have dates from a number of timezones. The same steps should be followed by Windows (etc.) users as well.

The "original" program was KDirStat and clones for Windows (WinDirStat) and Mac OS X (Disk Inventory X) were made later on.

They are all disk usage utilities and show the sizes of files and folders in a special graphical way called "treemaps".