Tiny Core Base > Release Candidate Testing
Core v7.0beta3
curaga:
--- Quote from: andyj on January 23, 2016, 09:34:32 AM ---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?
--- End quote ---
It's the first time, and probably one-off. 4.3 is (was) too new, and Canonical happened to declare they'd supply further stable patches for 4.2, so why not apply them?
--- Quote ---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.
--- End quote ---
Please report this to busybox.
gerald_clark:
filetool.sh is a core component and cannot depend on an extension.
andyj:
So because it's "core" it has to use hard paths and not be able to use a program in an extension even if one is available?
gerald_clark:
It can't use an extension that may not be installed.
andyj:
That still doesn't explain why the path to tar has to be hard coded. If it's just "tar" instead of "/bin/tar" and tar.tcz is not loaded, then /bin/tar will be executed. if tar.tcz is loaded, then /usr/local/bin/tar will be executed. If you're worried about a broken search path, then do something like "if [ -x /usr/local/bin/tar ] then /usr/local/bin/tar else /bin/tar fi". Would this be so bad?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version