Tiny Core Base > Release Candidate Testing
tinycore_v2.8rc4
roberts:
meo, Since you mention
--- Quote ---... since no applications are loaded ...
--- End quote ---
, they should be loaded.
If you still have symlinks from rc3 then you need to convert them into a simple text file onboot.txt
One way to convert is as user tc from you tce directory containing those symlinks:
ls -1 *.tcz > onboot.lst
roberts:
After heavy testing, I have found a couple anomalies, ok bugs.
One having to do with some dependencies getting listed in onboot.lst
The second having to do with existing dependencies in optional, but currently not used (loaded), not loading when a new extension is downloaded in install mode that requires such.
Both have been addressed in tinycore_2.8rc4a.iso now posted!
The distribution file tinycore.gz has also been posted.
thane:
To meo, in current TCL (haven't tried 2.8) I had to put a sleep command in my bootlocal.sh file when I was getting a very fast boot with a small number of extensions, without it my soundcard commands didn't execute.
meo:
Hi again!
Thanks for helping me to get things straight. Now when I have followed your advice, Robert, everything works fine and the soundmodule and the right kmap loads just as expected. Still it boots very fast but a little slower than when the extensions that should be loaded didn't load. I changed the tinycore,gz also and will try it out a little more before posting anything more about it. It seems though that Tinycore 2.8rc4 is stable and works fine. With rc3 I had some problems with permissions using emelfm but I haven't had time to try it out properly after changing to the most recent rc4. Thanks a lot to all that are working to make tinycore progress!
Have fun and keep up the good work,
meo
bmarkus:
There is an empty /etc/dropbear directory. It can be removed as dropbear is moved to an extension.
/etc/resolv.conf is missing by default and created only when dhcp daemon creates it. When it missing, WICD can't start as first it tries to create a backup which fails. There are to options:
- Change WICD startup
- Add a blank /etc/resolv.conf to TC.
For me both is OK. Why I mention it maybe lack of the file can cause issue for other applications even if I do not know any other.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version