Tiny Core Base > Release Candidate Testing
Core v7.0beta3
gerald_clark:
Then you have a program that behaves differently depending on what other programs have been installed.
Support and troubleshooting is hard enough without throwing in random unknown conditions.
Lee:
OSS.tcz is in the 7.x repo but it depends on OSS-modules-KERNEL.tcz which is not present.
Lee
Juanito:
The oss-modules-KERNEL extensions are waiting on a volunteer to compile them and submit an extension.
..so if you're feeling creative...
andyj:
I have a dilemma, and thus a question for the maintainers. The open-vm-tools extension will not work if copied to RAM, it MUST be an extension to work. The short explanation is that the copy process breaks the symlinks that are required for it to work. I don't have any desire to rewrite the source, it's just how it is. The question is: If I were to submit a patch for tce-load to support not copying an extension to ram that otherwise would get copied if copy2fs.flg existed, would it be better to have a file such as xcopy2fs.lst for a copy to ram blacklist, or have some flag file in the extension itself that would indicate to tce-load that the extension is not to be copied to ram?
Misalf:
Do the symlinks point to /tmp/tcloop ? In that case it would be better to fix the extension as relying on the presence of this dir is bad practice for obvious reasons.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version