dCore 5.0-rc1 released

[roberts]

On x86 dCore tcWbar incudes the wbar binary. So no need for the extra import.

[uggla]

Load the wireless mega extension you made and do this command if the name of the sce is "wireless":

find /tmp/tcloop/wireless > /home/tc/filelist


Then attach that filelist file with your next post.

Also, what is the output of the "version" command?  Just to be sure.

Here's the filelist. Version shows 5.0-rc1

[uggla]

On x86 dCore tcWbar incudes the wbar binary. So no need for the extra import.

So what is included in tcWbar that isn't in wbar? I've been using dcore with xorg and wbar and not tcWbar, it seems to work fine.

[beroje]

[Jason W]

uggla, I see it is simple with the firmware-iwlwifi package, it is not in main but in non-free, so it does not exist as a package and is not imported.

[Jason W]

beroje, sceupdatecheck will be deprecated as premade packages are going to be imported like the others.

But there is an importupdatecheck that can be imported the will check sce's that were imported with the "import -s" option.  It simply tells a user which packages inside an sce have available updates whether they are Debian packages or custom Tinycore ones.

Import a package:

import -s firefox

Then at a later time, check it with:

importupdatecheck firefox

It will tell you of any packages contained in it that have newer versions.  The sce does not have to be mounted, it will work either way.

[beroje]

thanks
Gracias

[uggla]

beroje, sceupdatecheck will be deprecated as premade packages are going to be imported like the others.

But there is an importupdatecheck that can be imported the will check sce's that were imported with the "import -s" option.  It simply tells a user which packages inside an sce have available updates whether they are Debian packages or custom Tinycore ones.

Import a package:

import -s firefox

Then at a later time, check it with:

importupdatecheck firefox

It will tell you of any packages contained in it that have newer versions.  The sce does not have to be mounted, it will work either way.

Why isn't the -s option used as default? What is the drawbacks using the -s option?

[uggla]

uggla, I see it is simple with the firmware-iwlwifi package, it is not in main but in non-free, so it does not exist as a package and is not imported.

But how am I supposed to download firmware-iwlwifi if it can't be imported?

[Jason W]

The -s option is used as it causes a list of md5sums to be created that not everyone will use, so for the sake of efficiency it is an option to create it.

As for the firmware, we are in the process of making a prebuilt wireless sce that can be downloaded so folks with wireless only have to download vmlinuz, dCore.gz, and the wireless sce.  I hope to get it up shortly.

[uggla]

As for the firmware, we are in the process of making a prebuilt wireless sce that can be downloaded so folks with wireless only have to download vmlinuz, dCore.gz, and the wireless sce.  I hope to get it up shortly.

I was thinking of having a system with only one (mega-) sce. Together with vmlinuz and dCore.gz it would make the whole system. But now there is going to be wireless.sce too 

[Jason W]

I am in the process of making individual firmware packages that can be imported, which along with the wireless stuff can be either made modular/mega via import, or to be downloaded as a single sce for those who want to download one wireless.sce and be ready to go.

Be patient.  :-)

The individual packages are there now, I will make the premade wireless sce soon that will have all one needs to connect with wireless when loaded.

[Jason W]

wireless.sce uploaded.  This is intended for those who desire a single file download to get connected on any wireless hardware without having to determine exactly what drivers or packages are needed.  It includes wpasupplicant, b43-fwcutter, all available wireless firmware, wireless-tools, and relevant kernel modules.  Once connected, one can use import to fetch just the needed packages for one's hardware requirements.  Available at the below link:

http://tinycorelinux.net/5.x/x86/sce/wireless.sce
http://tinycorelinux.net/5.x/x86/sce/wireless.sce.md5.txt

The same package can be obtained by import with the below command:

import wireless

[uggla]

I've now tried to put everything I need in one mega-sce. Dcore boots up fine with both wireless and xorg working. Some application icons show up in wbar but Applications menu are totally empty. I've included alsa-modules-3.8.10-tinycore and alsa-base but I don't know how to get sound working.

[Jason W]

alsa-base does not appear to have alsa-utils as a dependency according to it's web page.  I use alsa-utils plus alsa-modules-3.8.10-tinycore for sound, with alsa-utils you should have working sound without much if any manual intervention.

What window manager or desktop are you using?