Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Plethora of New User Space Filesystems For Mac OS X

Posted by CmdrTaco on Wed Dec 17, 2008 11:46 AM
from the because-you-can dept.
DaringDan writes "As part of the recent MacFUSE 2.0 release Amit Singh has added support for an insane number of filesystems on the Mac. This video from Google and this blog post pretty much explain everything in detail but to sum-up Singh has written a new filesystem called AncientFS which lets you mount a ton of UNIX file formats starting from the very first version of UNIX. Even more interesting is that they have also taken Linux kernel implementations of filesystems like ufs, sysv-fs, minix-fs and made them work in user-space on the Mac, which means its now possible to read disks from OSes like FreeBSD, Solaris and NeXT on OS X. ext2/ext3 don't seem to be on the list but apparently the source for everything is provided, so hopefully some enterprising soul can apply the same techniques to ext2. One of their demos even has the old UNIX kernel compiled directly on the Mac through the original PDP C compiler by somehow executing the PDP binaries on OS X!"
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Pope (17780) on Wednesday December 17 2008, @11:52AM (#26147099) Homepage

    I still have the old Intel Rhapsody DR2 disks lying around, and would love to see if this can read the filesystem. It's kind of fun playing around it what was NeXT with a MacOS interface, and at times I almost would rather have it than what OS X became, if only to eliminate the stupid gimmicks.

  • Sounds great. (Score:5, Interesting)

    by solios (53048) on Wednesday December 17 2008, @11:53AM (#26147115) Homepage

    Especially if I ever need to recover one of my linux box's drives from a Mac.

    But really, all I want for christmas is NTFS write support.

    • Re:Sounds great. (Score:5, Informative)

      by DarthStrydre (685032) on Wednesday December 17 2008, @11:57AM (#26147193)

      NTFS-3G which works with MacFUSE has full NTFS write support. It is, however, much slower at reading than the native NTFS read-only driver.

      • Re: (Score:3, Interesting)

        So why can't you use the native NTFS read-only driver for reads and the NTFS-3G driver for writes?

        • Re:Sounds great. (Score:4, Informative)

          by BrentH (1154987) on Wednesday December 17 2008, @02:23PM (#26149461)
          Because he hasnt tried the ublio builds of the nfts-3g plugin: it read and writes with comparable speed to a native filesystems (http://www.csamuel.org/2007/04/25/comparing-ntfs-3g-to-zfs-fuse-for-fuse-performance). I can read/write with 30MB/s on an external USB drive.
            • Re: (Score:3, Informative)

              That hasn't been unstable for a long time. Been using it for over a year now on a regular basis, for backups, and I havn't ever had any problems with it. I also havn't actually heard of reports of breakage for over a year, and many reports of succes. It's what Linux ntfs-3g uses too, and the stability/corruption issues just aren't there.

              NTFS-3g is just as stable and performant as a native fs, on both OSX and Linux. Ubuntu even supports it officially with Wubi now.
        • Well, for the last year or so, I have been using NTFS-3G every single day of the week, using it to running my virtual machines stored on a USB hard disk (performance is excellent, by the way -- with Linux's tendency to cache the VM images, Windows guest performance is easily better than running natively off a physical partition).

          At my college, and at home, there are computers with faulty USB connectors. A few times a week, when running a VM, my USB cable will wriggle loose, and the hard disk will disconne

    • Re: (Score:2, Funny)

      by Anonymous Coward

      But really, all I want for christmas is NTFS write support.

      Santa Jobs says you've been naughty. COAL filesystem support for you this year!

    • Re: (Score:3, Informative)

      Merry Christmas [blogspot.com]. NTFS-3G is more than fast enough to read documents from your Windows partitions. The only time its slower speeds will really be a noticeable problem, in my experience, is if you run OS X applications from your NTFS disk. But why would you keep your OS X applications on an NTFS volume?
      • Or you keep Steam on your windows parition and don't feel like rebooting to get your TF2 fix, so you load it up via crossover. And let me tell you, it is NOT fast enough for that. Load times are considerably longer than in Windows - Garry's Mod is nearly unplayable due to it taking around 30 minutes to load a map.

  • ext3 (Score:5, Insightful)

    by fracai (796392) on Wednesday December 17 2008, @12:04PM (#26147323)

    What is needed is an ext3 implementation. There've been projects to bring ext2/3 to the Mac, but so far they've been incomplete and abandoned.

    I'm actually pretty surprised that this hasn't been properly implemented already.

  • A couple years old, but ext2fsx [sourceforge.net] still works.

    • Re:ext2 on Mac (Score:4, Insightful)

      by mrsteveman1 (1010381) on Wednesday December 17 2008, @12:25PM (#26147705) Homepage

      If by "works" you mean "i have a 10.3 panther PPC machine and need non-journaling access to an ext3 partition", or "i have a tiger/leopard Intel machine and don't care if my machine suddenly panics". Those are the choices at the moment.

      It's curious really, this is a filesystem for which the spec is very well known, implementations are available fully open source, and yet here we are with unmaintained and unstable projects that are alpha quality for both OS X and Windows. The drivers for Windows ext2/3 support cause bluescreens under various conditions, so yea those are alpha too.

  • So it supports and insane number of filesystems just not the two most popular ones?

    Insane's the word...

  • FUSE for Windows (Score:3, Informative)

    by Cyberax (705495) on Wednesday December 17 2008, @12:47PM (#26148067)

    Also, it seems to be a good time to plug Dokan and my FUSE4Win project :)

    There's a wonderful project named "Dokan" (http://dokan-dev.net/en/), it makes posssible to write user-space filesystem in Windows.

    I've adapted FUSE interface for it, so it's possible to use (almost) unmodified FUSE filesystems in Windows: http://hg.sharesource.org/fuse4win [sharesource.org]

    Currently, SSHFS works fine. NTFS3g also works :)

  • A Plethora? (Score:5, Funny)

    by Ignatius D'Lusional (1010911) on Wednesday December 17 2008, @01:11PM (#26148461)
    Jefe: I have put many beautiful new user space filesystems in the Mac OS X, each of them filled with little suprises.
    El Guapo: Many new user space filesystems?
    Jefe: Oh yes, many!
    El Guapo: Would you say I have a plethora of new user space filesystems?
    Jefe: A what?
    El Guapo: A *plethora*.
    Jefe: Oh yes, you have a plethora.
    El Guapo: Jefe, what is a plethora?
    Jefe: Why, El Guapo?
    El Guapo: Well, you told me I have a plethora. And I just would like to know if you know what a plethora is. I would not like to think that a person would tell someone he has a plethora, and then find out that that person has *no idea* what it means to have a plethora.
    Jefe: Forgive me, El Guapo. I know that I, Jefe, do not have your superior intellect and education. But could it be that once again, you are angry at something else, and are looking to take it out on me?
  • FUSE vs. FST (Score:3, Interesting)

    by HTH NE1 (675604) on Wednesday December 17 2008, @01:41PM (#26148877)

    Apple's GS/OS had FSTs (File System Translators) that allowed that operating system to access HFS, ProDOS, DOS 3.3, and FAT volumes. How does FUSE compare in function to GS/OS's FSTs? You know, apart from working with non-obsolete hardware.

    • Re: (Score:3, Informative)

      Apple's GS/OS had FSTs (File System Translators) that allowed that operating system to access HFS, ProDOS, DOS 3.3, and FAT volumes. How does FUSE compare in function to GS/OS's FSTs? You know, apart from working with non-obsolete hardware.

      Fuse is not a file system or even a translation layer per se. It's just a way to let you run a filesystem in userspace, instead of inside the kernel where it would normally reside.

      This is slower, but has many benefits including easy development/debugging, not requiring ac

  • Reiser 4 (Score:3, Interesting)

    by doom (14564) <doom@kzsu.stanford.edu> on Wednesday December 17 2008, @02:55PM (#26149919) Homepage Journal

    Wasn't this sort of thing the idea behind the original "plug-in" mechanism planned for Reiser 4? I remember being intrigued by the idea of writing file-system customizations in perl, and I was looking forward to playing around with it to see what could be done with it.

    Unfortunately, it appears that the kernel devs don't want to hear about any functionality that doesn't fit in the box of their VFS layer.

    • Re:Reiser 4 (Score:4, Informative)

      by SanityInAnarchy (655584) <ninja@slaphack.com> on Wednesday December 17 2008, @08:43PM (#26153817) Journal

      I was semi-involved in this -- basically, Reiser4 wanted to make the filesystem pluggable, but in kernel-mode. The idea was that features would be implemented in the filesystem itself -- crypto, compression, files-of-files (for example, instead of suid utilities like passwd, just let me edit /etc/passwd/sanity), metadata-as-files (Unix permissions are a file, or things like foo.mp3/id3/genre)....

      Lots of cool ideas bouncing around, and most of them might work better as FUSE filesystems -- for example, there's no reason id3lib needs to be in the kernel.

      Some of them, it makes sense -- certainly for spinning disks, even moreso for external media, the media is so much slower than the CPU that compression makes sense, but you want to compress on flush, and not before. The part that was cool about that was, from the benchmarks they were getting, performance was actually better with compression turned on, because of how fast the algorithm is, how fast CPUs are, and how slow spinning disks are.

      But if you break down the "plug-in" concept, it was really horribly mis-named and mis-marketed -- it was just an API, like the pluggable IO schedulers were. It's really something that would probably go in the VFS layer -- something Hans had a really difficult time selling; according to his story, the first time he brought up his ideas, they told him to go put it inside his filesystem, not in the VFS, to try it out without making such drastic changes that would affect other filesystems. When he did that, and came back with the so-called "plugin" architecture, they told him that it should have been in the VFS, so that other filesystems could use it, and they refused to merge it.

      Looking at it now, it looks like most of these ideas, and some filesystems currently in the kernel, are better as FUSE filesystems. Better to keep the kernel smaller and more reliable, especially when the performance advantage is minimal -- FUSE will never be the bottleneck for sshfs, for example. Crypto works well enough at the block level (for full-disk crypto). And 20 years from now, we'll have computers so absurdly fast that no one will care about the performance hit of FUSE -- arguably, we're there already.

      But I do still wish that the compression, at least, would be tried, if those benchmarks have any truth to them.

      Anyway -- more directly, you would never have been able to write file-system customizations in Perl, unless Perl was put in the kernel, which would be an atrocity. However, you can write whole filesystems in Perl, Python, Ruby, or pretty much anything you want -- just use FUSE -- and nothing is stopping you from letting a real filesystem handle 90% of that.

  • by Animats (122034) on Wednesday December 17 2008, @03:00PM (#26149991) Homepage

    These are mostly read-only implementations for dealing with archival data. They're not read/write, which is more work to implement and not that useful.

    QNX has had user-space file systems for decades. (It's a microkernel; almost everything is in user space.) Some users wrote file system implementations for weird file systems, like .zip files. Most of the modern QNX file system action is supporting various flash-based file systems and networked file systems.

  • > "One of their demos even has the old UNIX kernel compiled directly on the Mac
    > through the original PDP C compiler by somehow executing the PDP binaries on OS X!"

    Hmpfh... Circa 1978-79, Forrest Howard and I wrote a PDP-10 simulator that ran on a PDP-11/70 (a 36 bit machine on a 16 bit machine for those not educated in DEC hardware). It was used to recompile the DEC Fortran compiler which was written in Bliss-11. And the Bliss-11 compiler could only be run on a PDP-10. Lacking a PDP-10 (expensive pseudo-mainframe computers in those days) we simply wrote a simulator. It didn't run fast, as I recall the DEC Fortran compiler recompile took several weeks, but it did run.

    Reproducing a PDP-11 sumulator on modern hardware would be relatively trivial, though it would have been much easier on older Macs because it could be argued that the 680X0 architecture was a knockoff of the PDP-11 architecture. Though one could suppose that current era (non-680X0 or non-PowerPC) machines are fast enough that it is a noop. I think the PDP-11 had a 300 ns cycle time and current machines are ~10x faster. Any current machines could easily simulate a '70s era minicomputer (or even most mainframes).

  • by master_p (608214) on Thursday December 18 2008, @07:51AM (#26158631)

    Someone makes a filesystem in the 70s, and then 30 years later is still accessible...I don't think that's gonna be the case with Windows in 30 years in the future!

    • Re: (Score:3, Insightful)

      I searched on that phrase and found a note on Apple's site with a Last Modified date of October 30, 2008: http://support.apple.com/kb/TS1545 [apple.com]

      Heck, here's one that makes reference to Mac OS 9 and OS X 10.2.4: http://support.apple.com/kb/TS1411 [apple.com]

      Doesn't sound like it's even remotely new, yet alone being new news.

    • Yes, I'm sure this is a conspiracy! Everyone gather up your torches and pitchforks so we can go after CmdrTaco!

      I think I actually had the "blue screen" problem that you're referring to. I say "I think" because I'm not sure what you're referring to. The only upgrade problem I've heard about is the one I had, which was very minor and nothing like a "blue screen of death". During the upgrade process, the upgrade stopped working and just sat there. It didn't crash, but it just sat there. If you did a har

    • Re: (Score:2, Insightful)

      Slashdot reports on useful software for OS X: "What the hell? Why aren't you paying attention to $RANDOM_BUG_AFFECTING_1%_OF_MAC_USERS."

      Slashdot reports on a random bug in the Linux kernel: "What the hell? Why aren't you reporting on all the great free software for Linux? Are you trying to give people the wrong idea?"

      • Re:News? (Score:5, Insightful)

        by mrsteveman1 (1010381) on Wednesday December 17 2008, @12:10PM (#26147429) Homepage

        Because slashdot isn't a public service announcement system and macfuse is more interesting?

        • Re:News? (Score:4, Insightful)

          by neokushan (932374) on Wednesday December 17 2008, @12:18PM (#26147587)

          I'd say that what's interesting and what's not interesting is all a matter of opinion, but it stands to reason that if you own a Mac and would be interested in this software, you would also be interested in knowing that a recently released update from Apple is causing major system trouble.

      • Re: (Score:2, Insightful)

        FUSE is interesting and nerdy. Scaremongering about how an operating system update may not work as advertised isn't particularly interesting, even if it is indicative of a QA failure on the part of the vendor.

      • Because... (Score:4, Insightful)

        by mario_grgic (515333) on Wednesday December 17 2008, @12:19PM (#26147625)

        Some users installing third party apps that modify their system files, and then apply updates over them have issues is hardly newsworthy.

        • by pla (258480) on Wednesday December 17 2008, @12:33PM (#26147859) Journal
          Some users installing third party apps that modify their system files, and then apply updates over them have issues is hardly newsworthy.

          Riiiiiight... Because a Linux-heavy audience would never even consider violating the sanctity of those spoooooky "system files" of which you speak...
          • Sure (Score:5, Insightful)

            by mario_grgic (515333) on Wednesday December 17 2008, @12:44PM (#26148007)

            You most certainly can if you want to. But if you have system files A and B and you modify B and later system update modifies A to call something in B that you changed the behavior of, then don't blame the system update.

            That's all I'm saying.

          • Re:Because... (Score:4, Insightful)

            by MightyYar (622222) on Wednesday December 17 2008, @12:56PM (#26148229)

            Try that with Ubuntu, upgrade, and then see what happens... similar :) I know, I've been there...

          • I've seen plenty of stories where Joe hacked this, or John hacked that or Larry came up with this ingenious hack. But since when is slashdot concerned with the details of said hack?

            If your news story is "If you hack your Mac OS X system files and then upgrade, you'll get a blue screen," then that's not news on slashdot. Anyone crowd who is "linux-heavy" should know this and go "duh!", and anyone who is not in that crowd has no idea what that means anyway.

            The news here is not that exists but the details of

          • Re: (Score:3, Insightful)

            In my experience, no, they wouldn't.

            Most linux users -- even talented ones -- rarely do anything to their system files other than apply vendor-created packages. For most people the idea of replacing system libraries with non-standard versions is almost unthinkable; if they wanted some other functionality they'd switch distros, not replace standard system files.

      • I think it's more luck. You can bitch about luck if you want, but there is not much you can do about it. I know I haven't heard anything about the blue screen problem yet. Did you try submitting it? The other thing is that MacFuse is an interesting open source project that makes Linux heads' eyes turn round like plates and mouths start dueling. Given that many times when a linux related article is shown, slashdot usually ends up ending the alticle with a disclaimer stating that they are owned by linux.
      • could potentially affect all Mac users

        Well for one, it's not so you've lost a lot of the shock you're attempting to drum up.

      • Re: (Score:3, Insightful)

        From a geek standpoint, one is a cool project and the other a mundane bit of troubleshooting.

        • Re:News? (Score:5, Funny)

          by rmav (1149097) on Wednesday December 17 2008, @03:29PM (#26150387)

          Macs are gay.

          Yeah. My macs are gay. But I talked to them, I explained I am hetero, and they never molested me - they never did anything to hurt my feelings. I am tolerant, but not interested in gay relationships. My computers understood that.
          Not that I would ever be interested in having sex with a computer anyway...
          Roberto

    • Yes, if you need support for a filesystem, changing the entire operating system around that need makes much more sense.

    • Re:So what? (Score:5, Insightful)

      by inKubus (199753) on Wednesday December 17 2008, @12:32PM (#26147837) Homepage Journal

      External hard drives, for one. I have some external drives I use on Linux boxes for various things. All of these boxes are up in an air conditioned server room. On occasion I need to get one file off onto my workstation, which is a Mac. Currently I have to walk it up to server room, connect it up, go back down, shell into the machine and mount it (if it's not an automounted drive), then somehow get the file out of the linux box to my Mac (scp or something). If I could just mount it on my workstation, it would save a lot of time.

      Additionally, there are occasions where a recovery process needs to be run on a bad drive. The same procedure applies. It's mainly a convenience thing, but it would make the Mac into a much more useful tool for admins. I can definitely see the usefulness for FAT/NTFS in a desktop support environment.

      Naturally you can always comment "Why use a Mac in the first place when you could have a linux desktop?" but I would reply that I don't have a choice, the CEO only buys Macs for workstations. So I have to use what I've got. This would make my life easier.

      • Re:So what? (Score:4, Interesting)

        by againjj (1132651) on Wednesday December 17 2008, @03:02PM (#26150019)

        Naturally you can always comment "Why use a Mac in the first place when you could have a linux desktop?" but I would reply that I don't have a choice, the CEO only buys Macs for workstations. So I have to use what I've got. This would make my life easier.

        And Macs don't run linux?