dCore-5.13.10.22 released.

[Jason W]

Team Tinycore is pleased to announce the release of dCore-5.13.10.22 after months of development and 4 release candidates.  Below are some highlights and features of dCore-5:

• Base system made from Debian Wheezy compatible libraries.
• importsce command to fetch Debian packages and their dependencies and package them in a single.sce extension.
• Ability to create a list file of favorite Debian packages which can be used to import and create a single sce containing those packages.
• Support for custom TC post install scripts.
• Premade packages available for kernel modules and similar.
• Debian mirror can be specified in /opt/debmirror in the same manner as /opt/tcemirror.
• Downloaded .deb packages are stored for use by later import sessions.  If the package has been updated by Debian, the newer updated version is then fetched and used by importsce.
• Functional toolchain when build-essential and any relevant development packages are installed.

Changes made since dCore 5.0-rc4:

• tc-config: Adjustments to PXE, lvm, and RAID - via Gerald Clark.
• importsce: Renamed import to importsce to avoid collision with import command of ImageMagick.

Files can be found at:

http://www.tinycorelinux.net/5.x/x86/release/

[gerald_clark]

I tried re-importing Xprogs, but the Import icon in wbar still tries to run import instead of importsce.

dCore appears to suffer from the same sync bug as core 5.  The patched kernel from core 5 seems to work.

[roberts]

Thanks for reporting. Xprogs updated to reflect name change of import to importsce. Please re-import.

[roberts]

Heads up. 5.13.10.22 image reposted to correct reported filetool.sh permission error. Please re-download the base image.

Also, as noted, Xprogs must be re-imported to support the name change from import to importsce.

[gerald_clark]

.profile looks for /usr/local/tce.installed/xorg which is not installed if you install something like xorg-intel.
This stops X from starting at login.

[tinypoodle]

Could someone please explain the versioning scheme?

Is this considered a release or a release candidate?

[roberts]

It is a release. Files moved to release area and announcement adjusted.
The version is a date stamp appended to 5 which represents the common kernel with x86 native Core.
Since remaining base of dCore is now quite different than native Core, a timestamp (yymmdd) was chosen to avoid confusion.

[tinypoodle]

Thank you very much for clarification.
Indeed it had occurred to me that version number might be a yymmdd timestamp, but the difference of 3 days between forum post and version had left me in doubt of that.

[hiro]

• tc-config: Adjustments to PXE, lvm, and RAID - via Gerald Clark.

Hey, this is the only google result for "dcore" "lvm" site:tinycorelinux.net
are there any instructions about how to use dcore with lvm, specifically to have the tce dir on a partition served by lvm?

[mocore]

My guess would be use to pretce or what ever the dcore equivalent is.

+I just tryed the searching the  git.source and found
http://git.tinycorelinux.net/index.cgi?url=dCore-scripts.git/log/&qt=grep&q=lvm

Code: [Select]

Preload drivers needed for tce/opt/home on lvm/RAID etc
So looking for PRETCE related stuff should put you on the right path *

*IMHO

[hiro]

well, now what's an easy way to do this on dcore? I obviously can't just use tce-load to download the right packages. Do I have to use debian packages for lvm2 cause there is no lvm2 sce?

[Jason W]

The only sce packages we keep are those like wireless that are necessary to have to be able to setup networking to then enable the ability to import desired packages.  If you would be able to use tce-load in this case to fetch packages on Core, you can also import on dCore.

If we did host a lvm2.sce, it would be made from imported Debian packages and/or our prebulit ones. 

[hiro]

I see, so that means one would run sce-import lvm2 to get the debian part and then sce-import raid-dm-3.16.6-tinycore to get the tc modules prebuilt into sce format. Then you copy these extensions from RAM into your new pre-sce dir (loaded with pretce=sda1/pre-sce) on the boot disk and add to the packages to the bootlist. The rest should happen as we're used to automatically.
Correct me if I'm wrong.