Tiny Core Base > Release Candidate Testing

tinycore_2.2rc2

(1/2) > >>

roberts:
The Second Release Candidate of v2.2 (tinycore_2.2rc2.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release/

Change log for v2.2 Release Candidate 2
* Upgraded busybox to support hdparam applet -d option for DMA.
* Upgraded busybox to support chrt applet.
* Upgraded usbinstall to support microcore installations.
* Upgraded upgrade_tce.sh to support microcore's .core. elements.
* Upgraded flpicss to v0.92
* Upgraded wallpaper Fltk/GUI to use generic setbackground.
* Updated tc-config for new boot codes, bkg and thm.
* New setbackground a WM agnostic background setting tool.
* New boot code bkg=image to set background at boot time, use complete file name, e.g., Saturn.jpg from /opt/backgrounds.
* New boot code thm=name_of_theme.thm to set JWM theme at boot time from /opt/jwmthemes via extension or backup.
* Forced unmount of all mounted loop files in rc.shutdown for cleaner shutdown.
* Fixed bug in swapfile Fltk/GUI was using incorrect swap filename.
* Fixed $DISPLAY to test for running instance of X.

Files in your home directory that have changed and need to be updated, check if you have added custom content.

.filetool.lst
.jwmrc
.profile
.xsession


Note: /opt/.backgrounds has been changed to /opt/backgrounds
If you currently have a collection of background be sure to adjust .filetool.lst so that you do not lose your collection.

helander:
Hi Robert,

thank you very much for the chrt applet.

Where can I find more info about the .core. elements. I found some traces of that in tc-config some day ago but did not really understand what it was. Where can I find more info about it?

Kind Regards

Lars

roberts:
Core elelments are squashfs system components to give Micro Core the same capabilities of Tiny Core, but with more flexibility, more choices.

For the time being Core Elements are maintained by Team Tiny Core and will be in the download directory along side the Micro Core iso.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release/core_elements

Xlibs.core.tczl
Xlibs.core.tczl.md5.txt
Xprogs.core.tczl
Xprogs.core.tczl.md5.txt
Xvesa.core.tcz
Xvesa.core.tcz.md5.txt

If you are like me, and want flwm, then be sure to use the latest flwm.tce and add .wmx to your /opt/.xfiletool.lst so that you get an updated flwm menu.

It is quite simple to get Micro Core to  provide a full "Tiny Core" experience.
Just download and place the core elements in any tce enabled directory.

For example, I have a pendrive with a tce directory. This tce directory has:
Xlibs.core.tczl, Xprogs.core.tczl, Xvesa.core.tce,  flwm.tce and mydata.tgz
and, of course, my selection of extensions.

If I boot mircocore with only these options:
microcore waitusb=5 tce=sda1

I basically get "tinycore" full X environment. Of course you could subsitute jwm.tce or hackedbox.tce or any other supported window manager with the same boot options and you will have your X setup. No desktop= needed no restore= needed. And if you are not using a pendrive, no waitusb=5 is needed!

If I boot the same microcore as above but just add the boot option text
microcore waitusb=5 tce=sda1 text

I boot to only the $ prompt
then when I want full X, just type startx, perhaps you might need to do an xsetup.sh before startx/

Tiny Core v2.x is self contained like version 1.x with many many updates.
While Micro Core is a subset of Tiny Core, Micro Core is not just command line interface, or just for servers. It is the most malleable system builder based on Tiny Core Concepts.

For another example you can remaster Micro Core with core elements inside the initramfs by placing them in /opt/tce and have a customized iso that boots using core elements.

You will find that Micro Core you have even more options more choices to have it your way.

helander:
Thank you very much for the elaborate explanation.

It sounds like I should have a deeper look into microcore and its capabilities. It could very well be that it would be a better choice for me than to use TC.

How do you see the way forward for these two distros, will TC just be remastered MC (where the extra TC extensions are
stored under /opt/tce in the tinycore.gz initramfs) ? Or will TC and MC differ in more than the built in extensions, e.g. will they have a different /etc/init.d/tc-config ?

/Lars

roberts:
I see them having the same "roots". All development is from MC. TC is just a "prebuilt"  Quite literally
TC = MC + extracted core elements. It would be nice for me to only have to post MC. But I started with TC and so it remains.

Navigation

[0] Message Index

[#] Next page