tinycore_2.4rc1

[bmarkus]

ALT/ENTER is now minimizing the window again 

[bmarkus]

2.4rc1 downloaded an hour ago, so it is expected the reuploaded release. There are extensions in /tce, started with norestore waitusb=5 option.

Everything works, but during boot these messages displayed:



(Sorry for the poor image quality, recorded in a dark room with a digital photo camera in hand)

[jpeters]

"tce-load -i -r -w xonclock" still changes /usr/local/tce.installed to root:root 1600 Jan  1  1970. 

[meo]

Hi!

I've been trying the new tinycore 2.4rc1 and I like the path of it's development. Very good work! I had some trouble with using both flit and watcher since they overlapped eachother. I had to make some hacks in /home/tc/.xsession to make it work the way I want it. So now it's OK. The only problems I've experienced besides that is thet there has been some troubles mounting (doenloading) extensions. I've received the message that it went well but while rebooting there have been error messages. Thanks for the good work!

Have fun developing tinycore further,
meo

EDIT: Have found some signs of unstability too. Like: when clicking on logout in the menu just produces the logout options without text, just plain grey (might be my own fault somehow but I wanted to mention it).

[roberts]

2.4rc1 downloaded an hour ago, so it is expected the reuploaded release. There are extensions in /tce, started with norestore waitusb=5 option.

Everything works, but during boot these messages displayed:



(Sorry for the poor image quality, recorded in a dark room with a digital photo camera in hand)

Nothing I can do about read errors. Either media is going bad, or bad download.

[roberts]

ALT/ENTER is now minimizing the window again 

Sometimes that happens when two people are working on the same program.

[bmarkus]

Nothing I can do about read errors. Either media is going bad, or bad download.

Possibly. But

• applications are installed and registered in /usr/tce.installed therefore TC found md5 OK
• checked all md5 manually, they are OK
• applications are working correctly
• TC 2.x prior 2.4 using the same media and same extensions do not display such message (first time I see only with 2.4RC1

[Jason W]

I see this same error on a clean reinstall of tce directory with 2.4rc1 during boot with the wxgtk being copied to ram.  I will see what I can find.

[bmarkus]

When downloading dependencies a new wget window opened cursor is moved to the top of this window. This is bit annoying when you are doing something else. Do not know is it 2.4 specific or prior version doing the same, just recognized playing with 2.4rc1

[Jason W]

Those files are getting an I/O error when trying to read them with any app.  They are apparently corrupt files and I will replace them.

[bmarkus]

Those files are getting an I/O error when trying to read them with any app.  They are apparently corrupt files and I will replace them.

Hm... In my case how is it possible that I can verify them and they are getting installed and working?

Will try it with other machines. What is strange that never seen this before 2-4rc1 I know, anything can become faulty any time 

[Jason W]

The use of copy-to-ram exposes corrupt files and other errors that are not caught by mounting a tcz or untarring a tce.  Rox filer for some reason was a similar case for unknown reasons.  The wxgtk extension has been fixed and reposted. 

[bigpcman]

The use of copy-to-ram exposes corrupt files and other errors that are not caught by mounting a tcz or untarring a tce.  Rox filer for some reason was a similar case for unknown reasons.  The wxgtk extension has been fixed and reposted. 

This is a very interesting limitation. I wonder if there is a remedy.

[Jason W]

Not really a limitation as there should be no corrupt files in an extension anyway.  Copy to ram simply exposes them.  The remedy is to have no corrupt files in extensions.  I will post a new extension audit script that will check for corrupted files so they can be caught before submission.

[bigpcman]

Not really a limitation as there should be no corrupt files in an extension anyway.  Copy to ram simply exposes them.  The remedy is to have no corrupt files in extensions.  I will post a new extension audit script that will check for corrupted files so they can be caught before submission.

Not really a limitation as there should be no corrupt files in an extension anyway.  Copy to ram simply exposes them.  The remedy is to have no corrupt files in extensions.  I will post a new extension audit script that will check for corrupted files so they can be caught before submission.

I suppose the more likely problem is going to be that the extensions become corrupt in the /tce directory. Perhaps the extension audit menu tool could also check the "health" of the extensions.