piCore 11.0beta1a released

[bmarkus]

First beta of piCore 11 released. Changes:

• glibc updated to 2.30
• gcc updated to 9.2
• uPython updated

[Paul_123]

Nice progress Bela.

Any plans to change change the base from here.   

- OpenSSL 1.1.1
- plus what you have above.

If you would like, I can build the wifi stuff.

[Juanito]

There appears to be a problem with /mnt/mmcblk0p1/11.0beta1av7.gz?

I cannot boot this on an RPi3B.

I can extract 11.0beta1a.gz and 11.0beta1av7l.gz, without problems, but with 11.0beta1av7.gz:

Code: [Select]

$ zcat /tmp/11.0beta1av7.gz | sudo cpio -i -H newc -d
cpio: unsupported cpio format, use newc or crc

[bmarkus]

Interesting, I'm developing on 3+. Will check.

[Twist]

Just to add to Juanito's post, and FWIW, I compiled gnu cpio-2.13 to see if it can extract the pi3 image.

Code: (bash) [Select]

tc@box:/tmp/remaster$ zcat ../11.0beta1av7.gz | sudo /tmp/cpio/usr/local/bin/cpio -i -H newc -d
/tmp/cpio/usr/local/bin/cpio: warning: skipped 8534 bytes of junk
zcat: unexpected end of file
/tmp/cpio/usr/local/bin/cpio: premature end of file

[Twist]

...
If you would like, I can build the wifi stuff.

Done that and have wifi on a pi zero W running 11.0beta1 working.
I've kept everything together (sources, .build and the resulting tczs), so could submit a load of extensions. But since I haven't had feedback on the first couple I sent through, I'm a bit hesitant to send more. (Are my tcz submits not going down some /dev/null somewhere?)
Let me know if I can help.

[Rich]

Hi Twist
Assuming  armv6, if they are listed here:
http://tinycorelinux.net/11.x/armv6/tcz/
then they are in the repository.

[Twist]

Rich, yes that's what I would expect to happen at some point (not yet listed atm).

For me the proces after submitting to picoresubmit _at_ gmail.com is a black hole. All I'm saying is: if it helps, I can sent through a couple more to get the 11x repo built up with some of the basic extensions like wifi and it's deps. Just not sure if my contributions meet the standard, and are received in good order. 

[Rich]

Hi Twist
I'm afraid that's all I know about this. Maybe one of the administrators can provide more insight into this issue.

[Paul_123]

Typically the extension maintainer does the updates, I maintain a lot of the rpi specific packages (wifi, rpi firmware, rpi-vc) I do them for pCP anyway.   But even I have to send everything through Bela to get posted.  He is just very busy.  Wish there was an automated way for distribution.

[Rich]

Hi Twist
Paul_123 brings up a point I forgot to mention. When updating an extension, protocol is to contact the person listed in the
Extension_by  field in the  .info  file to see if they are OK with you updating it.

[Twist]

Ah, wasn’t aware of that ‘protocol’. I happily listed myself in the submitted .info files 
I understand there’s a need to keep in control somehow. And it’s a pity if an individual (bmarkus) is burdened with that task. But I have to agree with Paul_123 that it would be great if there was more direct way to publish extensions. I’m not all that familiar with ‘git’, but surely a similar form of version control system with ‘public’ contributions could be a possibility? ... anyway i’m drifting way off topic here, sorry.

So Paul_123, would you be interested in my extensions to get wireless up op 11.xbeta1?
libnl, wireless_tools, libiw, iw, wpa_supplicant
I can imagine you’d rather stay in control and do them yourself, given pCP.

[Paul_123]

The protocol is there mainly for consistency in packages.   Bela and I were talking last year about a package management system......but that takes alot of time bandwidth to get working that we really didn't have.

As for wifi, crda integration is just as important to the rpi chipsets.   It will need rebuilt against the latest openssl.   I have build scripts for everything.   I was waiting for Bela to comment on the base for piCore11   There are core packages that if changed causes rebuilds of everything.  And then there are Silly things like the location of ssl certs too.

We'll see what happens.

[Twist]

Completely understand your point on time bandwidth.
I have no clue how big the install base is for picore (or tinycore). I guess pCP -being so easy to install- brings a lot of users (but not a lot will have ever heard of an tcz extension).

On wifi: I have(/had) no clue what crda is, so that's probably an indication I shouldn't be trusted to built the 'official' 11x extensions for wifi ;-) Happy I got my pi zero w up though.

Openssl in 11.0beta1a is already on 1.1.1d by the way.

[bmarkus]

11.0beta1a updated on the server. The armv7 initrd file was corrupted, sorry for that. Now it is expected to work, please try. If not, let me know. No other changes made.