Tiny Core v11.1

[Juanito]

Team Tiny Core is proud to announce the release of Core v11.1
http://www.tinycorelinux.net/11.x/x86/release
http://www.tinycorelinux.net/11.x/x86_64/release

Changelog for 11.1
* tce-size changes from Rich
* busybox-1.31.1-vi.backward_search.patch from Jazzbiker
* removed /usr/bin/uuid
* ldconfig update (x86_64 only) to fix occasional libraries not found error

[xor]

works well

For the first time, the screen came without entering these commands for "pavucontrol"!

Code: [Select]

$ sudo /usr/local/etc/init.d/dbus start

[marcelocripe]

Hi Juanito and colleagues,

I congratulate the team for updating Tiny Core to version 11.1.

More tests for me to do and learn from the new version.

Lo link: http://www.tinycorelinux.net/11.x/x86_64/release

There is no 64-bit version of Core Plus 11.1, the team does not offer the 64-bit version of Tiny Core Plus 11.1?

In Tiny Core version 11.0 of 32 bits there was no tc-install.

Is there already a tutorial on how to install Tiny Core without the tc-install extension?

Thank you for always answering my questions.

thankful
marcelocripe

Original text in Portuguese, translated into English by Google Translate

----------------------------

Olá Juanito e colegas,

Parabenizo a equipe por atualizar o Tiny Core para a versão 11.1.

Mais testes para eu fazer e aprender com a nova versão.

Lo link: http://www.tinycorelinux.net/11.x/x86_64/release

Não tem versão do Core Plus 11.1 64 bits, a equipe não disponibiliza a versão em 64 bits do Tiny Core Plus 11.1?

No Tiny Core versão 11.0 de 32 bits não havia o  tc-install.

Já existe um tutorial de como instalar o Tiny Core sem a extensão tc-install?

Agradeço por sempre responder as minhas dúvidas.

Grato
marcelocripe

Texto original em português, traduzido para inglês por Google Tradutor

[Juanito]

You are correct, there is no 64-bit version of CorePlus.

Are you saying that there is no tc-install in TinyCore? CorePlus contains both tc-install and tc-install-GUI

If you want to upgrade from 11.0 to 11.1, you can replace the existing core.gz with the new version for 32-bit and with corepure64.gz for 64-bit. These files are available here:

http://www.tinycorelinux.net/11.x/x86/release/distribution_files/
http://www.tinycorelinux.net/11.x/x86_64/release/distribution_files/

[u54749]

The new ldconfig has introduced a problem.

I have some 32-bit libraries in /l32 to run 32-bit wine with 32-bit Windows applications.  After an ldconfig run wine can't find the 32 bit libraries anymore.  After a run of the previous ldconfig version the 32-bit libraries are found and wine initializes correctly.  In both cases the 32-bit libraries seem to be correctly recorded in ld.so.cache.

Code: [Select]

~$ cat /etc/ld.so.conf
/usr/local/lib
/l32
~$ sudo ldconfig
~$ wine
wine: error while loading shared libraries: libpthread.so.0: wrong ELF class: ELFCLASS64
~$ ldconfig -p | grep libpthread
        libpthread.so.0 (libc6) => /lib/libpthread.so.0
        libpthread.so.0 (libc6) => /l32/libpthread.so.0
        libpthread-2.30.so (libc6) => /lib/libpthread-2.30.so
        libpthread-2.20.so (libc6) => /l32/libpthread-2.20.so
~$ sudo ./previous_ldconfig
~$ wine
Usage: wine PROGRAM [ARGUMENTS...]   Run the specified program
       wine --help                   Display this help and exit
       wine --version                Output version information and exit
~$ ./previous_ldconfig -p | grep libpthread
        libpthread.so.0 (libc6) => /lib/libpthread.so.0
        libpthread.so.0 (libc6) => /l32/libpthread.so.0
        libpthread-2.30.so (libc6) => /lib/libpthread-2.30.so
        libpthread-2.20.so (libc6) => /l32/libpthread-2.20.so
~$ sudo ldconfig
~$ wine
wine: error while loading shared libraries: libpthread.so.0: wrong ELF class: ELFCLASS64


[Juanito]

Are you using 32-bit Core or 64-bit CorePure64?

ldconfig was only updated in CorePure64.

[u54749]

I use 64-bit but I use the 32-bit version of wine (because the Windows app I use are 32-bit) and so needs some 32-bit libraries to run.   In previous tinycore versions this worked flawlessly but not anymore since the new ldconfig.

[Juanito]

What happens with the glibc ldconfig in the glibc_apps extension?

[u54749]

wine works

Code: [Select]

~$ sudo /tmp/glibc_apps/sbin/ldconfig
~$ wine
Usage: wine PROGRAM [ARGUMENTS...]   Run the specified program
       wine --help                   Display this help and exit
       wine --version                Output version information and exit
~$ /tmp/glibc_apps/sbin/ldconfig -p | grep libpthread
        libpthread.so.0 (libc6,x86-64, OS ABI: Linux 4.19.10) => /lib/libpthread.so.0
        libpthread.so.0 (libc6, OS ABI: Linux 3.8.13) => /l32/libpthread.so.0
        libpthread.so (libc6,x86-64, OS ABI: Linux 4.19.10) => /usr/lib/libpthread.so


[Juanito]

As loading 32-bit libs wasn't an anticipated use of CorePure64, I'd suggest using ldconfig from glibc_apps then..

[aus9]

I have some strangeness with my dot local bin. I hopefully set up a test others could duplicate?
On  64 bit

Code: [Select]

echo $PATH
/home/tc/.local/bin:/usr/local/sbin:/usr/local/bin:/apps/bin:/usr/sbin:/usr/bin:/sbin:/bin:/etc/sysconfig/tcedir/ondemand

tc@box:~$ ls -al $HOME/.local/bin/test
-rwxr-xr-x    1 tc       staff           25 Apr 16 11:48 /home/tc/.local/bin/test

tc@box:~$ .local/bin/test
line 1

tc@box:~$ test

tc@box:~$ cat $HOME/.local/bin/test
#!/bin/sh
echo 'line 1'

tc@box:~$
I was expecting "test" to work at the command line without the full pathway?

any clues?

[Rich]

Hi aus9

... any clues?

Yes. Since no error message was displayed, there's another  test  program being found. You have  coreutils.tcz  installed and
are executing  /usr/local/bin/test.

[andyj]

There is also a test in busybox:

Code: [Select]

~$ ls -al $(which test)
lrwxrwxrwx    1 root     root            17 Jan 20  2019 /usr/bin/test -> ../../bin/busybox


[Rich]

Hi andyj

There is also a test in busybox:

Did not realize that.

In that case, I have  coreutils.tcz  installed :

Code: [Select]

tc@E310:~$ ls -l `which test`
lrwxrwxrwx 1 root root 40 Apr  2 17:03 /usr/local/bin/test -> /tmp/tcloop/coreutils/usr/local/bin/test
tc@E310:~$

[curaga]

It's a shell builtin. Those take predecence over PATH apps.