CertForums.com IT Certification Forum Homepage
Results 1 to 3 of 3

Linux Filesystems vs Windows Filesystems by Nigel McFarlane

You are viewing a topic in the Linux / Unix Discussion forum part of the Computing Support Forums category.

  • Share:
  1. #1
    Bit Poster
    Posts
    30
    Join Date
    17 Nov 2005
    Liked
    0 times
    Rep Power
    7

    Arrow Linux Filesystems vs Windows Filesystems by Nigel McFarlane

    Hello all,
    Here is an article comparing Windows and Linux File systems. I hope you'll enjoy this.

    Both Windows and Linux organize disk-based files into a hierarchy of directories. Such directories are usually called "folders" when viewed in a GUI. One whole hierarchy is called a "file system" on both platforms. The architecture of Windows and Linux file systems is similar in some points, but diverges greatly when tools are considered. Here's a quick comparison.

    On hardware derived from Intel or IBM PCs, both Windows and Linux use the Master Block Record/ Master Boot Record (MBR). That is the bit of disk used to boot the operating system and to state whether the disk is partitioned or not. On both Windows and Linux, it is common to have at most one file system per partition. That is about the end of the similarity.

    Each Windows file system gets a drive letter, like "C:". OnLinux, each file system gets a device, like /dev/hda1 ("hard disk A part 1"), which is represented as a file. Such a file is a device file (since a disk is a device), hence the "dev" part of the path name. Also, the device file is not an ordinary text file, it is a "special file." Since disks are block devices (unlike a serial mouse), such a file is fully described as a "block special device file." The numbered part of the path can be a little weird to get right; it's best to be guided by documentation there or extract the right name from a report.

    On Windows, file systems can be FAT16, FAT32 or NTFS, to name a few. Recall FAT16 is the ancient standard responsible for Windows file names with the "8.3" file name length restriction. On Linux, filesystems can be "minix," "ext," or "ext2," to name a few. Also, "minix" is an example of the ancient standard responsible for UNIX file names once being limited to 14 characters. Linux also has "msdos" and "vfat" file systems for compatibility with Windows and DOS, plus more.

    Windows uses FORMAT.EXE to format a disk. Linux uses "mkfs" ("make file system") in various specialist forms.

    Each Windows file system has a File Allocation Table (FAT, VFAT, or similar) that states which disk blocks hold the topmost directory. On Linux, the equivalent on most filesystems is the superblock. A Linux file system has multiple copies of the superblock physically saved on the disk. This provides redundancy in case of a partial disk corruption. The superblock is just about always in memory on Linux; that is not the case for ancient DOS-like file systems. There are no special restrictions on files placed in the topmost directory on Linux, either.

    On Windows, there is one drive letter per mounted file system: for example, C: for C: and D: for D:. On Linux there are no drive letters, so one file system is mounted on "/" and all other file systems are mounted on subdirectories of "/." This arrangement is like the little-used MS-DOS command SUBST, or the NET USE command that supports Novell's NetWare. The equivalent Linux command is "mount."

    You can see all this at work on Linux, but for some of it you need to be logged in as root. Type "cat /etc/fstab" to see all the mountable devices, including floppy disks and CD players. Type "df" to see the devices currently mounted, and their free space. In the usual case you can even see the superblock: try "/sbin/dumpe2fs /dev/hda1" where hda1 comes from the output of "df." The name "dumpe2fs" is a casualty of history; it replaces the older "dumpfs." The information produced is really just for diagnostic purposes.

    Mostly file systems work for you silently. If you want to dig into Linux further, then there are plenty of tools that can be used as inspection points.

    About the author
    Nigel McFarlane is an open source software analyst and technologist with a broad background in technology and software engineering. He has an extensive programming background and degrees in computer science and physics. His latest book is "Rapid Application Development with Mozilla" from Prentice Hall PTR.

    Source:
    http://searchopensource.techtarget.c...990200,00.html

  2. Posts
    666
    Join Date
    6 June 2003
    Location
    Somewhere in Germany
     

  3. #2
    Yottabyte Poster tripwire45's Avatar
    Posts
    14,265
    Join Date
    29 Jun 2003
    Location
    Boise, ID, USA
    Country
    United States Country Flag
    Liked
    6 times
    Rep Power
    100
    Thanks, techguy. Just one question...is that an original article? That is, did you write it yourself? If you did, that's wonderful and you should take credit for it. If not, please post the link to the original source. Thanks.

  4. #3
    Terabyte Poster moominboy's Avatar
    Posts
    1,130
    Join Date
    24 Aug 2005
    Location
    Wiltshire, England
    Age
    32
    Liked
    0 times
    Rep Power
    12
    thanks for that techguy, handy to have a reference to compare different terms on both os's.

Similar Threads

  1. Manage Linux servers from Windows
    By tripwire45 in forum News
    Replies: 3
    Last Post: 11-Nov-2005, 07:52 AM
  2. How responsive is your Linux machine compared to your Windows machines?
    By ffreeloader in forum Linux / Unix Discussion
    Replies: 10
    Last Post: 09-Nov-2005, 01:09 AM
  3. Linux on Windows with CoLinux
    By tripwire45 in forum News
    Replies: 2
    Last Post: 26-Sep-2005, 03:46 PM
  4. Linux security in a Windows World (article)
    By tripwire45 in forum Linux / Unix Discussion
    Replies: 0
    Last Post: 09-Aug-2004, 06:24 PM