WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core v11.0  (Read 8359 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11913
Re: Tiny Core v11.0
« Reply #45 on: March 26, 2020, 10:42:41 PM »
findutils reposted

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11913
Re: Tiny Core v11.0
« Reply #46 on: March 26, 2020, 11:56:42 PM »
hplip and ghostscript posted to tc-11.x x86 repo - things had also been broken by a net-snmp update

Offline rhermsen

  • Newbie
  • *
  • Posts: 37
Re: Tiny Core v11.0
« Reply #47 on: April 04, 2020, 07:05:00 AM »
GNU wget gives: Disabling SSL due to encountered errors.
Looks due to openssl 1.1.1 (see e.g. https://github.com/ContinuumIO/anaconda-issues/issues/10709)

wget
Code: [Select]
BusyBox v1.31.1 (2019-12-17 16:10:37 UTC) multi-call binary.

cd /tmp
wget https://github.com/FRRouting/frr/archive/frr-6.0.2.tar.gz
Code: [Select]
Connecting to github.com (140.82.118.4:443)
sudo rm frr-6.0.2.tar.gzConnecting to codeload.github.com (140.82.114.9:443)
saving to 'frr-6.0.2.tar.gz'
frr-6.0.2.tar.gz     100% |*****************************************************************| 4371k  0:00:00 ETA
'frr-6.0.2.tar.gz' saved

tce-load -wi wget.tcz
#reboot
wget --version
Code: [Select]
NU Wget 1.20.3 built on linux-gnu.
cd /tmp
wget https://github.com/FRRouting/frr/archive/frr-6.0.2.tar.gz
Code: [Select]
--2020-04-04 13:54:17--  https://github.com/FRRouting/frr/archive/frr-6.0.2.tar.gz
Disabling SSL due to encountered errors.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10207
Re: Tiny Core v11.0
« Reply #48 on: April 04, 2020, 09:59:20 AM »
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11913
Re: Tiny Core v11.0
« Reply #49 on: April 04, 2020, 11:55:18 PM »
I've compiled openssl-1.1.1f, which seems to fix the problem - I'll post after some more testing.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11913
Re: Tiny Core v11.0
« Reply #50 on: April 05, 2020, 05:16:23 AM »
updated openssl-1.1.1 posted

Offline rhermsen

  • Newbie
  • *
  • Posts: 37
Re: Tiny Core v11.0
« Reply #51 on: April 06, 2020, 03:13:22 PM »
GNU wget is working fine with openssl-1.1.1f.
Thanks!

Offline aus9

  • Jr. Member
  • **
  • Posts: 86
Re: Tiny Core v11.0
« Reply #52 on: April 16, 2020, 04:12:20 AM »
SNIP
Code: [Select]
/etc/os-release
/usr/share/doc/tc/release.txt
SNIP

I wonder, is it possible for someone to accidently download the 32 variants....boot up on a 64 bit CPU and be none the wiser?

on my 64 bit I have
Code: [Select]
cat /etc/os-release
NAME=TinyCore
VERSION="11.1"
ID=tinycore
VERSION_ID=11.1
PRETTY_NAME="TinyCoreLinux 11.1"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:tinycore:tinycore_linux:11.1"
HOME_URL="http://tinycorelinux.net/"
SUPPORT_URL="http://forum.tinycorelinux.net/"
BUG_REPORT_URL="http://forum.tinycorelinux.net/"
tc@box:~$ cat /usr/share/doc/tc/release.txt
11.1

If its just a string.....maybe add x64_64 to it?

I am aware I am on the correct variant as "uname -r" tells me so.
I do not want to waste internet bandwith in these troubling times by downloading   32 bit variants to peek into  their text files

thanks for reading






Online Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 7673
Re: Tiny Core v11.0
« Reply #53 on: April 16, 2020, 05:33:03 AM »
Hi aus9
... I wonder, is it possible for someone to accidently download the 32 variants....
Certainly, if they manually download extensions instead of using the intended tools (apps  or  tce-load).

Quote
... boot up on a 64 bit CPU and be none the wiser? ...
Since Tinycore does not support mixed 32/64 bit libraries (and extensions), no.
If you are running Corepure64 (64 bit kernel, 64 bit apps) a 32 bit program will fail to run.
If you are running Core64 (64 bit kernel, 32 bit apps), you can only run 32 bit programs.
If you are running Core (32 bit kernel, 32 bit apps), you can only run 32 bit programs.

Quote
I am aware I am on the correct variant as "uname -r" tells me so.
That only tells you if you are running a 32 or 64 bit kernel.

The  getBuild()  function defined in  /etc/init.d/tc-functions  is used to determine whether you need 32 or 64 bit extensions:
Code: [Select]
tc@E310:~$ . /etc/init.d/tc-functions && getBuild
x86
tc@E310:~$