From: Dominick L. <do...@al...> - 2006-08-24 06:04:35
|
I notice that the latest version(s) of FUSE state that they are compatible with Linux "kernels 2.4.21 and later". I'm attempting to build a FUSE module that will insert into a 2.4.20 kernel. (On a Broadcom BCM4780 embedded device.) So it appears that I'm out of luck. Looks like my options are: 1. Find an older version of FUSE that *will* work with 2.4.20. Can anyone tell me what is the most recent FUSE revision that would be compatible? 2. Patch the 2.4.20 kernel to provide whatever capability from 2.4.21 that FUSE needs. Here, I'd need to know what is missing from 2.4.20. 3. Try to figure out how to shoehorn a completely new kernel onto the embedded device. I doubt anyone here can help me with #3 (time to head off and search all the WRT54G hacking sites), but if anyone can supply answers to Q1 and Q2, I'd be very grateful. Thanks, -- Dominick |
From: Miklos S. <mi...@sz...> - 2006-08-24 08:26:55
|
> I notice that the latest version(s) of FUSE state that they are compatible with > Linux "kernels 2.4.21 and later". > > I'm attempting to build a FUSE module that will insert into a 2.4.20 kernel. > (On a Broadcom BCM4780 embedded device.) So it appears that I'm out of luck. > > > Looks like my options are: > > 1. Find an older version of FUSE that *will* work with 2.4.20. Can > anyone tell me what is the most recent FUSE revision that would be > compatible? I think 1.9 should work, and 1.4 is almost sure to work on most 2.4 kernels. The problem with this could be that most new filesystems won't compile with the old FUSE API. > 2. Patch the 2.4.20 kernel to provide whatever capability from > 2.4.21 that FUSE needs. Here, I'd need to know what is missing from > 2.4.20. The alloc_inode and destroy_inode members of super_operations structure. I know some vendor kernels < 2.4.21 do contains this, so you might like to go fishing in RedHat/etc kernel patches. Miklos |