Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Better Filesystems selection in OS X

4 posts in this topic

Recommended Posts

Hm. For fun I am dorking with porting FreeBSD filesystems to XNU. While it's certainly not a walk in the park so far, it looks very doable.



So if there is interest in the subject, I will update results of this R&D..

Quite tired now, laters all :)

What FS do you want to port?

Share this post

Link to post
Share on other sites

What FS do you want to port?

I am thinking of Ext2 (and UFS is gone from XNU now too :(  ) would be really useful for starters. Then who knows.


I am thinking of proper, native filesystems here. The VFS layer is a bit weird as they removed access to the structures and everything is "opaque".

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By jcrcarmo
      Hello everyone,
        Greetings from Brazil!  I'm getting a kernel panic at the macOS High Sierra install process.  Any ideas on what could be happening?  Please refer to attached pictures.  Thank you very much for your time and help.  I really appreciate it.   Motherboard Gigabyte G41MT-S2P F3 CPU Intel Core 2 Duo 2.6 GHz 8 Gb of RAM Video Zotac GeForce 9500GT 1 Gb     jcrcarmo        
    • By PsychoKoopa
      I recently got an Asus X55U laptop with the following specs:
      AMD Brazos C-60 1Ghz CPU
      4GB DDR3
      120GB HDD
      AMD HD 6290 Graphics.
      I am trying to use the Sierra 10.12.5 raw file from the Olarila forum. I understand that I need to change the kernel on the installer USB to one that supports AMD processors, but I am not sure which kernel to use or how to replace it. If anyone can help me with this I would appreciate it.
      EDIT: Also when I try to use the Sierra Zone distro with the included AMD kernel, I get Error loading kernel cache (0x9) when trying to boot into the installer.
      EDIT 2: Nevermind this post. I just read that your CPU needs SSE4.1 to run Sierra and the C-60 only had SSE4A. I'll try an older version and make a new post if necessary.
    • By pjhartin
      I've recently acquired a kernel that Bronya has been developing and I had wished to test it out on my system.
      I assumed the process of updating the kernel would follow the steps outlined here
      So I booted via USB into my macOS, deleted the existing kernel at 
      macOS/System/Library/Kernels and replaced with the new kernel file, then deleted the existing PrelinkedKernels file too. 
      Next I ran Kext Utility, and when it finished I rebooted.
      Upon booting into macOS again via clover on the drive, I ran Kext Utility again, just to be safe.
      Now, however, I no longer have any sound devices once booted and I am experiencing very long boot times, noting "kextd wait appleacpicpu" at the end of boot (see attached screenshot)
      Did I actually update the kernel correctly? Did I miss a step, or screw something up along the way?
    • By Egonaut
      Alright, so my first attempt at helping people that isn’t in a private discord. Hope this goes well.
      No one has posted this as a direct solution to someone asking for help with this error, so I thought I’d be the one to share it.

      I encountered this problem when I rebooted after making some minor changes and discovered I couldn’t boot back into the disk. All over the web, people keep suggesting clover-side tweaks and replacing kexts, and while they may solve the problem for some, absolutely nothing was working for me (and a few others), even when booting with no kernel cache at all.
      No boot flags worked, no .efi files would solve it. 

Holding spacebar in clover, no change.
      So, the solution ended up being system side, and not clover related. You needed to delete your prelinked kernel from the HDD and rebuild it. 

To do this, you just have to be able to get to your recovery drive or use an install USB that’ll give you access to the disk. Clover got me into my recovery drive just fine, another hint that it wasn’t related to clover - but regardless, whatever works for you.

      After you’re in a terminal, type the following commands.

      Df -h This will list all of your volumes, make sure you’re targeting your installation drive.

      If your volume has a space in the name, such as "Mac OS HS", you'll need to format it as such: "Mac\ OS\ HS" - This is simply how the command line associates spaces.
      touch /Volumes/[NAME HERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE]

 In my case, I replaced [NAME HERE] with my installation drive - "macOS\ 10.13".
      Chances are, this command will give you the error "Child process [directory] has exited due to signal 10"
      The line immediately after that will give you another bit of extremely important information that you need to take note of.
      "Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel"
      That directory is what we're going to be targeting to fix our system.

      So, time to nuke it.
      rm -rf [location to /prelinkedkernel/prelinkedkernel] MAKE SURE YOU DOUBLE CHECK IT IS EXACTLY WHAT WAS OUTPUT WHEN YOU TRIED THE COMMAND ABOVE.

      I've done this on multiple machines and it really is hit or miss whether or not this will appear. Regardless, the solution is simple. The following code tag only applies to if you encounter this issue.
      Fsck mount -uw / RE-ENTER THE FOLLOWING COMMAND! You need a more specific location now. rm -rf /Volumes/[NAME]/System/Library/PrelinkedKernels/prelinkedkernel touch /Volumes/[NAME]/System/Library/Extensions && kextcache -u /Volumes/[Name] Now you should be receiving "/Volumes/[NAME] locked; waiting for lock." This is a good thing. Wait a few seconds, you'll receive "Lock acquired; proceeding." After that, you'll be back at -bash-3.2#, and it will appear as if nothing happened. Again, this is expected. For people who didn't have to use the Fsck command, simply type the following and receive the usual "Waiting for lock; Lock received" response.
      touch /Volumes/[NAMEHERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE] Now, use your up arrow on the keyboard to re-enter this command. If nothing happens, you're golden. If it detects kexts with invalid signatures, that's still okay - but for future reference, don't go the ##### approach/philosophy of installing kexts to your system drive. Take this as a warning.
      Go ahead and reboot, and start your installation just like normal. You'll now get past the 0x1 error. Congratulations!
      If you get hung up anywhere, go back to clover and add “-f” to the boot flags, then boot again.
      You should make it back to your desktop with no damage whatsoever.

 Like nothing ever happened!

      Now, as for what causes this, I honestly have no idea. All I know is when you have a working system, make some kind of modication/tweak/installation that HS doesn't agree with, you can possibly get this error on some systems. It's rare, but exists, and unfortunately this is the only way I've been able to get past it. It's not too much work, so don't be too intimidated. You'll have your system back in no time.
      If you'd like some personalized 1-on-1 support, read my signature and contact me that way. I'm more than happy to help, or at the very least take some time out of my day to analyze your issue and give my thoughts.  Thanks for reading my first guide, I'm hoping to publish some more fixes to make High Sierra as painless as possible for every user.
    • By ticobfr
      Hello everyone,
      I've been trying to install sierra in my new external HD and I'm stuck with this screen. 
      I read here a guy change from -v to -x and worked, so I did it and I got the apple. Before changing it I was stuck with the same result but without the apple.

      Thanks in advance!