> Just a guess...but it may be due to byte ordering issues; you did this > on PPC, which is big-endian, and ext2 was originally developed on > Linux/x86, which is little-endian. That could be it, but ext3 works in PPC linux distros.(I have not tested ext2fuse on PPC linux distros though)
> If you care about the filesystem, I wouldn't touch let what you've > compiled write to it. fsck cannot perform miracles, and if your hosed > driver corrupts your filesystem, you may never be able to recover it. You are right, but I did not know how to use ext2fuse as readonly and I don't have any important data on my linux partition.(I'm just testing different linux distros on my PPC mac to see how much it has progressed, I use Leopard for serious works.) > A more correct thing to do would be to remove the declaration from imager.c Thats what I have tried the first time I got the error, but it caused several other errors and after about one day of trial and error I decided to temporarily modify string.h . Then the next error was: ext2fs.c:52: error: 'struct stat' has no member named 'st_atim' ext2fs.c:53: error: 'struct stat' has no member named 'st_mtim' ext2fs.c:54: error: 'struct stat' has no member named 'st_ctim' After googling a bit I preferred to comment those lines of ext2fs.c . The las error was: /usr/local/include/fuse/fuse_lowlevel_compat.h:77:24: error: sys/ statfs.h: No such file or directory I have commented sys/statfs.h from fuse_lowlevel_compat.h too. Then it compiled successfully. On Mar 30, 9:20 pm, "Chris Cleeland" <[EMAIL PROTECTED]> wrote: > On Sun, Mar 30, 2008 at 11:55 AM, ali <[EMAIL PROTECTED]> wrote: > > > I have successfully compiled ext2fuse 0.8 on Mac OS X 10.5.2(PowerPC) > > after modifying some of ext2fuse, macfuse and OS X header and source > > files. I'm not a programmer so it is highly possible that I did > > something wrong. > > When I try to mount my Ext3 partition using this command: > > sudo ext2fuse /dev/disk0s5 /Users/ali/mounts/new > > I get this error: > > fuse-ext2fs: Bad magic number in super-block while trying to open /dev/ > > disk0s5 > > Bus error > > Just a guess...but it may be due to byte ordering issues; you did this > on PPC, which is big-endian, and ext2 was originally developed on > Linux/x86, which is little-endian. > > Of course, there could be many other issues considering the number of > things you changed. Modifying header files--especially those that you > can't authoritatively change--is generally a Bad Idea. > > > I don't know whether it is Ext2FUSE bug, incompatibility with MacFUSE > > or my mistakes when modifying header files. > > I have fsck-ed my linux partition in single user mode and it says my > > root partition is clean, should I add any special option to fsck to > > check super-block too? > > If you care about the filesystem, I wouldn't touch let what you've > compiled write to it. fsck cannot perform miracles, and if your hosed > driver corrupts your filesystem, you may never be able to recover it. > > > BTW, the first and most annoying compile error was: > > imager.c:40: error: conflicting types for 'ssize_t' > > /usr/include/string.h:70: error: previous declaration of 'ssize_t' was > > here > > make[2]: *** [libext2fs_a-imager.o] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > I have fixed it by changing string.h to match imager.c regarding > > 'ssize_t'. > > A more correct thing to do would be to remove the declaration from imager.c --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
