Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Final Releases => Topic started by: Juanito on June 07, 2020, 02:07:52 AM
-
Team Tiny Core is pleased to announce the release of piCore-11.0:
Thanks to @Paul_123 for his help with this
* kernel 4.19.81
* glibc 2.30
* gcc 9.2.0
* e2fsprogs 1.45.4
* util-linux 2.34
* BusyBox 1.28.4
Other changes:
* initrd split into 11.0.gz (rootfs) and 4.19.81-piCore{,_v7,_v7l}.gz
* X libs and server updated - full kms supported on RPi3, fake kms supported on RPi4
* wayland added with weston compositor
Download locations:
http://tinycorelinux.net/11.x/armv6/releases/RPi/
http://tinycorelinux.net/11.x/armv7/releases/RPi/
http://tinycorelinux.net/11.x/armv7l/releases/RPi/
There is only one SD card image, it supports all RPi boards, including RPi3+ and RPi4.
Please read README and don't forget to expand the mmcblk0p2 partition according to your needs to make room for persistent data and installed applications.
For support visit http://forum.tinycorelinux.net/index.php/board,57.0.html
-
Awesome!
Thanks to all who contributed.
-
Good stuff first, I have 11.0 armv7 running on a Pi 3 B+, with X and the touch screen also working.
I have found a couple of minor problems.
--I tried to load lftp from the repository. It lists libidn as a dependency. The repository has libibn2, but not libibn so the load of lftp fails.
--the udpsvd link to busybox is missing in /sbin
-
Hi MrPorcine
According to the .info files lftp .tcz was compiled after libibn2.tcz so it's quite possible that's what it was built against. Change
the .dep file to say libibn2.tcz and see if it works.
-
lftp does indeed depend on libidn2 - dep file adjusted.
-
--the udpsvd link to busybox is missing in /sbin
It's at /usr/bin/udpsvd - it's also there in x86/x86_64, so I guess that's where busybox installs it to?
-
The busybox tftpd is started as a service in /etc/init.d/services/tftpd. This script has the path to udpsvd as "/sbin/updsvd". You are right, the link is already installed a /usr/bin/udpsvd, it's only that this script doesn't find it.
-
I need busybox-httpd.tcz and inetutils-servers.tcz. They both exist in the 9.0.3 repository. Pardon the newbie question, but do I just request them here? Can I help? Perhaps the procedure is documented somewhere?
More generally, I'm looking for light weight http and ftp servers. lftp is a little too light. The two tczs above work well for me in 9.0.3.
-
The first thing to try would be to see if those extensions work in piCore-11.x.
If not, the second thing to do would be to pm the maintainers and request an update.
If neither of the above works then any extension submissions would be gratefully received - see here: http://wiki.tinycorelinux.net/doku.php?id=wiki:creating_extensions.
Extension compilation notes and scripts can be found here: http://tinycorelinux.net/11.x/armv7/tcz/src
-
I need busybox-httpd.tcz and inetutils-servers.tcz. They both exist in the 9.0.3 repository. Pardon the newbie question, but do I just request them here? Can I help? Perhaps the procedure is documented somewhere?
More generally, I'm looking for light weight http and ftp servers. lftp is a little too light. The two tczs above work well for me in 9.0.3.
Busybox httpd works pretty well. The extension in 9.x, should work in 11.x Not much has changed in newer versions of busybox. But if not, I can make a more current version.
-
The busybox tftpd is started as a service in /etc/init.d/services/tftpd. This script has the path to udpsvd as "/sbin/updsvd". You are right, the link is already installed a /usr/bin/udpsvd, it's only that this script doesn't find it.
The script is correct in x86/x86_64 - I'll make a note to correct it in the next piCore release.
-
update - both inetutils-servers and busybox-httpd tczs from the 9.0.3 repository work with piCore11. So far so good, I have both http and ftp servers working.
-
busybox-httpd copied to the piCore-11.x repo.
Neither inetutils nor inetutils-servers can be copied over as one or more of their utilities depends on an old version of ncurses and thus will need recompiling against the 11.x version of ncurses.
-
Another mystery. All I did was copy the tczs from my working 9.0.3 setup to the 11.0 setup that I'm working on, then updated onboot.lst by hand. When I run ldd on the two executibles they don't mention ncurses (below). It's true that 9.0.3 has ncurses 5.9 and 11.0 has ncurses 6.1. Both the http and the ftp server are working on the 11.0 setup.
Thank you for all the pointers you've given to me. I know I wouldn't have gotten this far without your help.
I ran ldd on all the utilities in inetutils-servers, it's only telnetd that has the ncurses dependency. This won't affect what I'm doing.
tc@box:/mnt/mmcblk0p2/tce$ ldd `which ftpd`
linux-vdso.so.1 (0x7ec1c000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x76efe000)
libc.so.6 => /lib/libc.so.6 (0x76dbc000)
/lib/ld-linux-armhf.so.3 (0x76f3d000)
tc@box:/mnt/mmcblk0p2/tce$ ldd `which busybox-httpd`
linux-vdso.so.1 (0x7ec63000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x76ea8000)
libc.so.6 => /lib/libc.so.6 (0x76d66000)
/lib/ld-linux-armhf.so.3 (0x76ee7000)
tc@box:/mnt/mmcblk0p2/tce$
-
I believe that I have inetutils-servers compiled against piCore11. How do I find the package maintainer?
-
Hi MrPorcine
According to the .info file:
http://tinycorelinux.net/9.x/armv6/tcz/inetutils-servers.tcz.info
the current maintainer is bmarkus.
-
Bela has been mia for a while. The biggest thing when building extensions is to follow the standard build criteria. Unfortunately, it looks like the wiki is down. To link.
You may be able to find the compile info in the package source.
http://distro.ibiblio.org/tinycorelinux/8.x/armv7/tcz/src/inetutils-servers/
-
Yes, there is a build script associated with the sources, thanks for point this out. Which bring up another question :(. All the build scripts that I have found in the 10.x/armv7 tcz source tree have compiler flags set for a v6 build. Is this on purpose or just an historical artifact?
-
On purpose. That way it runs on all boards. I've done many side by side tests, there is not much to be gained in board specific optimizations.(And many times the maintenance headaches)
-
I ran the build script run against inetutils-1.9.4.tar.xz. I compiled on a RPi Model 3 B+ using a virgin piCore 10.0 installation. The resulting files are too large to attach even after compressing with bzip2 (322K).
All I've tested is inetd and ftpd - both work.
Interestingly, when I run ldd against the list of executables, ncursors is not in the list.
-
Hi MrPorcine
... The resulting files are too large to attach even after compressing with bzip2 (322K). ...
You are not allowed to attach extensions to your posts. See the section on submitting extensions in the Wiki:
http://wiki.tinycorelinux.net/doku.php?id=wiki:creating_extensions#submitting
-
Interestingly, when I run ldd against the list of executables, ncursors is not in the list.
Did you load the readline-dev and/or ncurses-dev extensions before compiling?
-
Hi there,
This is my first time posting/replying here, but I've been using piCore 9.x for a little while to run a minimal appliance-style app on an RPi Zero W, and am delighted that there's a new piCore release.
I've had a look in the RPi boards and don't see any threads mentioning this, but it looks like some wifi packages aren't in the 11.x repo yet, which makes it tricky to get started. It wasn't clear whether I should make a new thread for this, or PM a maintainer (no idea which one, though).
To wit, I'm looking in http://repo.tinycorelinux.net/11.x/armv6/tcz/ and:
* libnl is missing
* wifi is missing
* wireless_tools is missing, and the version in the 10.x repo incorrectly lists libiw as a dependency
After manually pulling those into my local tce/optional/ directory I was able to tce-load them as normal and everything is good. As best I can tell these extensions worked properly as-is, so I think it'd be fine to just copy them forwards into the 11.x repo tree, though I did have a go at building a newer version of libnl just for the exercise.
Thanks, hope this is clear and descriptive enough.
-
Missing extensions copied to piCore-11.x armv6 repo - thanks for reporting this.
-
Hello,
I am looking for all of the packages associated with usbip and hamlib. I have found indications that they are available in piCore 9.0, although I have not been able to find any actual archive of the tgz files. Help would be appreciated.
Thanks,
Mac
-
Hi mcody
They are located here:
http://tinycorelinux.net/9.x/armv6/tcz/info.lst
-
I am looking for all of the packages associated with usbip and hamlib
Do you mean the dep list? Thanks to Rich they might be
http://tinycorelinux.net/9.x/armv6/tcz/usbip.tcz.dep
http://tinycorelinux.net/9.x/armv6/tcz/hamlib.tcz.dep
infos says compiled for 8 so
http://tinycorelinux.net/8.x/armv6/tcz/src/usbip/usbip.build
http://tinycorelinux.net/8.x/armv6/tcz/src/hamlib/hamlib.build
tgz .....if you mean TCZ then click these, in your web browser to download them
tinycorelinux.net/9.x/armv6/tcz/usbip.tcz
tinycorelinux.net/9.x/armv6/tcz/hamlib.tcz
-
Sorry if I was not sufficiently clear and also for the typos in my original message (yes, I meant tcz).
I'm looking for the .tcz packages for usbip and hamlib for piCore 11.0. I notice that there are multiple files associated with each package (.tcz, .tcz.info, .tcz.list, .tcz.md5.txt, .tcz.zsync).
I'm confused by the links in the URL 'tinycorelinux.net/9.x/armv6/tcz/'. When the link is sourced directly, there is a webpage listing all of the available Tiny Core extensions. If I add the name of the extension (e.g. 'tinycorelinux.net/9.x/armv6/tcz/hamlib.tcz'), I can download the file. Is that file actually the extension file?
Will the hamlib and usbip .tcz packages found in piCore 9.0 work with piCore 11.0? If so, I will download and use them.
Thanks,
Mac
-
You can download the extensions like this:
$ wget http://tinycorelinux.net/9.x/armv6/tcz/usbip.tcz
$ wget http://tinycorelinux.net/9.x/armv6/tcz/hamlib.tcz..where you also need the *.dep and *.md5.txt files
Once you have the six files, copy them into /mnt/mmcblk0p2/tce/optional
You'll need to try them in piCore-11.x to know if they work or not
-
Thanks, everyone, for your suggestions. I decided it would be easier to switch to piCore 9.0, given that the needed packages are already in place. I'll take a look at piCore 11 at a later date to see if these packages become available.
Regards,
Mac
-
They are less likely to become available if you can't confirm they work..
-
The only thing I see about the firmware from x86_64 is that they include way more than would ever be available on a rpi. Rpi is only USB, so all of the pci based firmware is not needed.
-
Hi all people,
Thanks a lot for such contribution and effort!!!
Keep tinycorelinux going,
Regards,