Tiny Core Base > Release Candidate Testing
Core v7.0beta3
Rich:
Hi andyj
I didn't realize the kernel source was from Ubuntu either. I always though it came from kernel.org. Regardless, you got
your answer.
Juanito:
@curaga/andyj - if you could confirm the rules change required to the fuse extension, I'll make the changes.
curaga:
I've updated fuse.tcz in x86 and x86_64.
When adding udev rules, udev has to be told to reload them. Then a trigger should be done, in case another extension did a trigger before fuse, and no extension would do one after it.
curaga:
--- Quote from: andyj on January 22, 2016, 08:47:51 PM ---I guess I didn't catch that the first time. Still, TC as an Ubuntu fork, I didn't see that coming... Being a slacker for over two decades I must just be a purist at heart. It just feels wrong. ;D
--- End quote ---
I did go over the patches included just in case ;) They were competent stable patches.
It is not an Ubuntu kernel in the sense of foo-ubuntu7, ie no Ubuntu-specific patches.
andyj:
The updated fuse.tcz seems to be working, in the sense that I don't have to set any permissions now. I haven't really tried to break it but I'm sure if there's a problem I'll find out at an appropriately bad time.
Regarding the ubuntu kernel, is this a new direction, an old direction that some of us are just now learning about (or maybe just me), or a one off for some reason?
And now for a new problem. Busybox tar is broken. surprise. /opt/.xfiletool.lst is supposed to exclude files and directories, but if the user mounts the shared folder on say /home/tc/hgfs and I add home/tc/hgfs backup fails. If I load tar.tcz and fix the hard coded paths in filetool.sh for /bin/tar to /usr/local/bin/tar, it works as expected. So, one of two solutions exists. Fix busybox tar (unlikely, as this is a known problem), or fix filetool.sh to find the right tar and use it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version