Tiny Core Base > Release Candidate Testing

tinycore_v3.8rc2

<< < (7/9) > >>

roberts:
Would need more specific information that could be reproduced. If not a local extension permission problem then possibly a low(er) memory system resulting in running out of inodes.

bmarkus:
/tce directory is stored on HDD's /sda1 partition ext4 formatted. System is booting from USB stick. There is 2GB RAM, an Intel Core2 dual core CPU. No tricks, it's an ordinary rc2, no extension loaded to RAM. From one boot to another same happenes, it is not random. First loaded extensions work as expected, failing ones are at the end of onboot list. There are not too many extensions, thes setup is used to compile simple extensions. If you need I can provide the onboot list. It happened with intltool.tcz first but it's not significant I'm sure. Changing onboot to ondemand it works fine.

gerald_clark:
Sounds to me like a depfile error.
Programs may run or not run depending on the order they are loaded.


I would identify the first that fails, remove it and all that follow from onboot.lst.
Then reboot and tce-load -i each in turn and look for errors.

roberts:
A depfile error should be found by using appsaudit. Order should not be a factor as dependencies are loaded prior to any parent extension.

There was a known issue with coreutils "overlaying" via path some busybox commands that are used to load the system. That issue was addressed in rc2

* Updated tce-setup & tce-load to ensure busybox calls thus avoiding conflicts with gnu utilities.

Sharing your onboot.lst would be helpful.

gerald_clark:
AppsAudit will only find a missing dependency listed in a dep file, not one that is missing from a  dep file.

I have found several dep files that were in error this way.

Navigation

[0] Message Index

[#] Next page

[*] Previous page