Tiny Core Base > Release Candidate Testing
Micro Core & Core Elements
roberts:
I had mentioned that I would be discussing core elements.
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/
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.
Note: Using the old "*.core.*" from RC3 will break things as well as using an old flwm extension. Be advised.
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/
If for some reason, I boot microcore as base norestore nolocal I also get $ prompt but X core elements are not mounted. So, when I want full X, from the $ prompt I run desksetup and answer two questions.
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 ( this is similiar to what TCv2.0rc3 was demonstrating ).
You will find that Micro Core you have even more options more choices to have it your way.
Juanito:
--- Quote from: roberts on June 03, 2009, 12:28:07 AM ---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/
If for some reason, I boot microcore as base norestore nolocal I also get $ prompt but X core elements are not mounted. So, when I want full X, from the $ prompt I run desksetup and answer two questions.
--- End quote ---
I'm booting microcore like this from a usb stick:
--- Code: ---initrd=/boot/microcore.gz quiet vga=773 noswap waitusb=5 noscan text
--- End code ---
The "microcore" in "microcore waitusb=5 tce=sda1 text" doesn't appear to be required - or are you indicating "initrd=/boot/microcore.gz" by "microcore"?
jpeters:
Funny thing...no matter how small the core, the first thing I do is add packages so that my system does all the things I'm already used to. Fast boot times and updated libraries that work with current apps/modules have been extremely useful in adding functionality.
roberts:
--- Quote ---I'm booting microcore like this from a usb stick:
Code:
initrd=/boot/microcore.gz quiet vga=773 noswap waitusb=5 noscan text
The "microcore" in "microcore waitusb=5 tce=sda1 text" doesn't appear to be required - or are you indicating "initrd=/boot/microcore.gz" by "microcore"?
--- End quote ---
I was indicating from a boot prompt.
I believe what you posted in a part of your boot loader's specification, which in that case, you would not repeat microcore, just as you don't repeat tinycore for various boot loaders.
roberts:
--- Quote from: jpeters on June 03, 2009, 03:19:16 AM ---Funny thing...no matter how small the core, the first thing I do is add packages so that my system does all the things I'm already used to. Fast boot times and updated libraries that work with current apps/modules have been extremely useful in adding functionality.
--- End quote ---
Actually, the smaller the core, the less ram demand when using tcz.
Therefore microcore + core elements, mounted from a persistent store, will use less ram than the equivalent tinycore, which has all of the core elements in ram.
Navigation
[0] Message Index
[#] Next page
Go to full version