Tiny Core Linux

Tiny Core Base => TCB News => Final Releases => Topic started by: Juanito on November 28, 2013, 11:09:29 PM

Title: Tiny Core v5.1
Post by: Juanito on November 28, 2013, 11:09:29 PM
Team Tiny Core is pleased to announce the release of Core v5.1:

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

Change log:
* kernel: updated from 3.8.10 to 3.8.13, to correct long sync issues
  (This is a minor update to fix a specific bug. No config changes)
* tce-fetch: updated to support $KERNEL parameter (thanks to maro)
* version: added multi-architecture support
* tc-functions: getbootparam updated to properly match a parameter that is a substring
* tc-functions: getpasswd updated to preserve last character entered in a password

Note that this version is available in three formats:

core: fully 32-bit
core64: 32-bit with 64-bit kernel modules
corepure64: fully 64-bit

The fully 32-bit core is available in three iso files - core*.iso, tinycore*.iso and coreplus*.iso

core, core64 and corepure64 are available from:

http://distro.ibiblio.org/tinycorelinux/5.x/x86/release/distribution_files/

core: rootfs.gz + modules.gz + vmlinuz
core64: rootfs.gz + modules64.gz + vmlinux64
corepure64: rootfs64.gz + modules64.gz + vmlunux64

Update instructions:

1. Copy over new vmlinuz/vmlinuz64
2. Copy over new core.gz or rootfs.gz + modules.gz/modules64.gz or rootfs64.gz + modules64.gz
3. Boot into new system

if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing

or if you only use core or rootfs + modules (no X) or Xorg did not start and only have a system prompt use:

tce-audit builddb
tce-audit fetchmissing

Note:

If using corepure64 alongside core and/or core64, a separate /tce directory is required for the 64-bit extensions and must be specified using "tce=" in the bootloader.
Title: Re: Tiny Core v5.1
Post by: philip on November 29, 2013, 12:49:30 PM
Hooray!

I inserted a line acknowledging this happy event into the table at

http://en.wikipedia.org/wiki/Tiny_Core_Linux#Release_history

... but I was too shy to make any bigger changes. E.g., perhaps the table lines mentioning 5.0.1 and 5.0.2 should now be dropped?
Title: Re: Tiny Core v5.1
Post by: tinypoodle on November 29, 2013, 01:18:31 PM
IMHO yes, more so as at current there are 3 entries "Current Release".

Also, "Latest stable release  5.0.2 ^[^1] / October 18, 2013; 42 days ago (2013-10-18)" (on top of page)  should probably be adapted accordingly.
Title: Re: Tiny Core v5.1
Post by: LinuxUser01 on November 29, 2013, 04:43:51 PM
In which folder would i copy over modules.gz into? Core.gz and vmlinuz usually go into mnt/sdc1/boot, but i can't find modules.gz anywhere. Do i even need modules.gz? Not sure what it is even used for. Thanks.
Title: Re: Tiny Core v5.1
Post by: Juanito on November 29, 2013, 09:35:11 PM
core.gz = rootfs.gz + modules.gz

..so if you have core.gz, then no need for rootfs.gz + modules.gz
Title: Re: Tiny Core v5.1
Post by: Juanito on November 30, 2013, 01:13:29 AM
rootfs64 reposted to correct udev version to be the same as x86 (fixes problems with pulseaudio and Xorg-7.7 evdev/udev)
Title: Re: Tiny Core v5.1
Post by: bmarkus on November 30, 2013, 02:52:37 AM
rootfs64 reposted to correct udev version to be the same as x86 (fixes problems with pulseaudio and Xorg-7.7 evdev/udev)

Which problems fixed?
Title: Re: Tiny Core v5.1
Post by: Juanito on November 30, 2013, 03:15:20 AM
Due to problems with udev, the Xorg-7.7 evdev driver would not automatically find the keyboard, mouse, touchpad, etc, and loading pulseaudio gave udev path_id errors.
Title: Re: Tiny Core v5.1
Post by: netnomad on December 01, 2013, 09:15:50 AM
hi friends,

until 4.7.7. it was possible to correct the password-entry with backspace and cursor-left in the protected mode.
in the last cut the major problems of the protected mode were solved, but it is still not possible to correct a mistyped password :(

thank you for your help and contributions.
Title: Re: Tiny Core v5.1
Post by: Zendrael on December 01, 2013, 01:16:20 PM
Maybe we should add a note that id the user is using just wi-fi, it's better to download the 3.8.13 wireless modules and drivers BEFORE the update, otherwise he will end with a disconnected system or had to boot back to the old version. Also, there are some wireless firmwares that are not ported to the 3.8.13 yet in the repo.

Aside that, everything is working ok!

Thanks Core team!
Title: Re: Tiny Core v5.1
Post by: curaga on December 02, 2013, 06:54:10 AM
@netnomad

The password is read one char at a time, see tc-functions. The code here has not changed since 4.7 (besides the last char bugfix). It's probably a kernel change.


Would you like to try to fix it? You can test it easily from a normal shell, reboots not needed - just call ". /etc/init.d/tc-functions; getpasswd", it will fetch the latest function and start it.
Then you can have tc-functions open in another terminal and edit to fit.


edit: I see it's not possible to have both editing and "password stars" in shell. That it worked before was a bug that's now seemingly fixed.

I'll see about making a C helper for this.
Title: Re: Tiny Core v5.1
Post by: curaga on December 02, 2013, 07:54:34 AM
Actually, I'd rather not reimplement line editing. We can make it a line editing prompt, but without any stars, like the normal busybox login. Would that work for you?
Title: Re: Tiny Core v5.1
Post by: netnomad on December 02, 2013, 10:38:06 AM
hi curaga,

i don't mind.
in my opinion the best solution was line-editing plus stars, although it's caused by a bug, so it's hard to decide.
is there a limit for false inputs? can i try a password again and again?
if yes, it could be a security issue :(
if no, probably line-editing is more secure and convenient.
Title: Re: Tiny Core v5.1
Post by: curaga on December 03, 2013, 06:31:24 AM
Quote
is there a limit for false inputs? can i try a password again and again?
if yes, it could be a security issue
if no, probably line-editing is more secure and convenient.

If the entered password matches (when you enter it again), that's the only try. If the decryption fails you are not asked again.

Ash does not support arrow keys in the "read" builtin, but backspace will work in future versions.
Title: Re: Tiny Core v5.1
Post by: Juanito on December 05, 2013, 11:33:26 PM
The CorePlus-5.1 iso has been reposted.

Problems with the dep tree files in the repo resulted in the wrong versions of the ndiswrapper, wireless and wl kernel module extensions being built into the previous iso.

Note that there are still problems with the dep tree files in the repos and we are working to fix this.
Title: Re: Tiny Core v5.1
Post by: vinnie on December 26, 2013, 06:07:53 AM
In core 5.x the flag copy2fs.flg still works? Yesterday I wanted to try the new core but once the distro was started I could not unmount the sd memory.
Title: Re: Tiny Core v5.1
Post by: Juanito on December 26, 2013, 06:23:24 AM
it worked the last time I tried it, which I believe was with tc-5.1
Title: Re: Tiny Core v5.1
Post by: vinnie on December 28, 2013, 02:09:14 AM
You're right, it works, I must have put the flag in a wrong place.
Today I tried to install Xorg and flwm and the touchpad is not recognized (I can not move the cursor but only press the buttons).

Title: Re: Tiny Core v5.1
Post by: Juanito on December 28, 2013, 03:07:18 AM
if you have the xf86-input-evdev extension loaded it should work, but you could also try the xf86-input-synaptics extension
Title: Re: Tiny Core v5.1
Post by: vinnie on December 28, 2013, 06:39:21 AM
with xf86-input-synaptics touchpad works fine and also touchscreen works out of the box! (but unfortunately it was ruined over time  >:( )

I have two other problems:
1. there is no longer standard terminal included (like xterm or aterm?)
2. I can not install applications from the GUI (in the status bar I get a "Failed packname.tcz") but only by tce tce-load or tce-ab
Title: Re: Tiny Core v5.1
Post by: Juanito on December 28, 2013, 07:04:57 AM
It would be good to read the tc-5.x release notes - aterm is a separate extension and at least one terminal extension needs to be loaded for the fltk gui applets to work.
Title: Re: Tiny Core v5.1
Post by: vinnie on December 28, 2013, 08:07:35 AM
Ok, thanks. you should write in the info file of xprogs.tcz or try to generate an pertinent error.
which terminals you can choose from? apps with urxvt not seem to work.

I noticed that all my packages are missing (except geany), what criteria did you choose to reintegrate or not  the packages?
Title: Re: Tiny Core v5.1
Post by: gerald_clark on December 28, 2013, 08:23:42 AM
Some have to be recompiled, some need to be tested.

http://forum.tinycorelinux.net/index.php/topic,15906.0.html
Title: Re: Tiny Core v5.1
Post by: beerstein on December 28, 2013, 08:26:52 AM
I have the same problem with my piCore 5.1 rc3. It works great so far and seems to be stable also. After the GUI install on the CLI according to the REDME.TXT file and reboot the GUI piCore boots OK. There is no aterm installed and no aterm icon in wbar. So I tried to install aterm from the GUI apps tool. After a while I am getting the error:
"2. I can not install applications from the GUI (in the status bar I get a "Failed packname.tcz") but only by tce tce-load or tce-ab"
This happens for other extensions too.
So I went back to the CLI and see - here I was able to install aterm and some other extensions such as pcmanfm and openssh.
After returning to the GUI things have changed to the better - I now was able to install extensions from the GUI - strange???
Title: Re: Tiny Core v5.1
Post by: vinnie on December 28, 2013, 08:50:50 AM
if you have installed aterm,  apps can work (but I would like to know with such other terminals it work? if it works only with aterm, it would be right to add it as a xprogs dependency)

thanks gerald, i see
Title: Re: Tiny Core v5.1
Post by: bmarkus on December 28, 2013, 08:55:46 AM
if you have installed aterm,  apps can work (but I would like to know with such other terminals it work? if it works only with aterm, it would be right to add it as a xprogs dependency)

lxterminal
Title: Re: Tiny Core v5.1
Post by: bmarkus on December 28, 2013, 08:56:29 AM
I have the same problem with my piCore 5.1 rc3. It works great so far and seems to be stable also. After the GUI install on the CLI according to the REDME.TXT file and reboot the GUI piCore boots OK. There is no aterm installed and no aterm icon in wbar. So I tried to install aterm from the GUI apps tool. After a while I am getting the error:
"2. I can not install applications from the GUI (in the status bar I get a "Failed packname.tcz") but only by tce tce-load or tce-ab"
This happens for other extensions too.
So I went back to the CLI and see - here I was able to install aterm and some other extensions such as pcmanfm and openssh.
After returning to the GUI things have changed to the better - I now was able to install extensions from the GUI - strange???

Will check piCore
Title: Re: Tiny Core v5.1
Post by: Juanito on December 28, 2013, 09:00:59 AM
The idea is that any terminal program could work as long as it provides the appropriate symlink. Lxterminal looks like it would work, but urxvt looks like it needs adjusting
Title: Re: Tiny Core v5.1
Post by: bmarkus on December 31, 2013, 04:47:28 PM
I have the same problem with my piCore 5.1 rc3. It works great so far and seems to be stable also. After the GUI install on the CLI according to the REDME.TXT file and reboot the GUI piCore boots OK. There is no aterm installed and no aterm icon in wbar. So I tried to install aterm from the GUI apps tool. After a while I am getting the error:
"2. I can not install applications from the GUI (in the status bar I get a "Failed packname.tcz") but only by tce tce-load or tce-ab"
This happens for other extensions too.
So I went back to the CLI and see - here I was able to install aterm and some other extensions such as pcmanfm and openssh.
After returning to the GUI things have changed to the better - I now was able to install extensions from the GUI - strange???

Can't reproduce on piCore 5.1.rc3 Running in console

Code: [Select]
tce-load -iw TC.tcz
startx

loads all necessary components correctly and in GUI aterm works as expected.