Tiny Core Base > Release Candidate Testing
Core v4.4rc2
bmarkus:
In current version TC is composed of Core and few extensions. Running from USB stick CDE content is copied to TCE and handled on the same way as user installed extensions. Using the 'base' boot options no any extensions loaded, result is Core instead if TinyCore, therefore you can not start a clean TC system after installing extensions.
Use xbase.lst as a protection list and even when base option used load extensions from xbase.lst and skip all others.
roberts:
--- Quote from: bmarkus on March 05, 2012, 10:04:25 AM ---Search in AppBrowser doesn't work, returns the full extension list instead of only matching names.
--- End quote ---
Working fine here. NMI
mladen:
--- Quote from: bmarkus on March 05, 2012, 10:15:21 AM ---Use xbase.lst as a protection list and even when base option used load extensions from xbase.lst and skip all others.
--- End quote ---
After a base installation to usb, I copied original /cde directory to it and try to play with "clean" CorePlus configuration. Noticed that if I add some extension to the xbase.lst file and use cde and lst=xbase.lst boot options, system boot only tcz extensions from original unmodified version of xbase.lst file !?
roberts:
On a usb install you should be using a normal live tce directory and not cde.
cde is intended for cdrom and isohybrid for delivery of read-only extensions due to the factoring out of X/GUI from the initrd strting with version 4.2
mladen:
Thanks for your explanation Roberts.
Actually I used /cde directory trying to separate working directories for tcz and scm extensions. I entered to the same problem as bmarkus:
--- Quote from: bmarkus on March 02, 2012, 02:04:45 AM ---With AppBrowser / Local I can load extension from anywhere in the file system. It is convenient during testing extensions. With ScmBrowser I can't do that, I have to move it to the production directory /tce/optional and install from there and remove when testing finished.
--- End quote ---
so I experimented using separate directories (not named tce !) for tcz and scm extensions.
Booting CorePlus from /cde directory and using two simple scripts I can easily change /etc/sysconfig/tcedir and alternatively use this two directories for downloading and experimenting with new extensions. In this way I avoid bloating my production /tce directory with things I really don`t need. Using such /cde based configuration, I can also easily use the most recent release candidate without touching my stable usb installation.
I suppose this subject is better to discuss on other place, but I was initiated with quoted bmarkus comment.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version