SliTaz Forum
You are not logged in.
This is the list of installed packages in a Slitaz flavor I created selecting only the base system packages. It should include the dependencies.
List of all installed packages
================================================================================
acl 2.2.53 system-tools
acl-dev 2.2.53 development
attr 2.4.48 system-tools
attr-dev 2.4.48 development
busybox 1.31.1 base-system
bzlib 1.0.8 utilities
cdrkit 1.1.11 utilities
cookutils 887 base-system
dialog 1.3_20190211 base-system
e2fsprogs 1.45.5 base-system
elfutils 0.161 development
gcc-lib-base 4.6.3 development
gdbm 1.18.1 misc
gettext 0.19.8.1 development
gettext-base 0.19.8.1 base-system
gettext-tools 0.19.8.1 libs
glib 2.43.3 x-window
glib-dev 2.43.3 development
glibc 2.14.1 meta
glibc-base 2.14.1 base-system
glibc-dev 2.14.1 development
glibc-locale 2.14.1 system-tools
kbd 2.2.0 system-tools
kbd-base 2.2.0 base-system
kmod 23 base-system
libcap 2.33 system-tools
libcomerr 1.45.5 base-system
libcroco 0.6.13 system-tools
libcroco-dev 0.6.13 development
libcrypto 1.0.2u security
libdb 6.2.23 misc
libffi 3.3 development
libffi-dev 3.3 development
libgio 2.43.3 x-window
libgio-dev 2.43.3 development
libgomp 4.6.3 development
liblzma 5.2.5 misc
libsqlite 3.32.1 office
libssl 1.0.2u security
libtic 6.2 development
libtinfo 6.2 development
libxml2 2.9.10 system-tools
libxml2-dev 2.9.10 development
libxml2-tools 2.9.10 system-tools
linux 3.16.55 base-system
linux64 3.16.55 base-system
linux64-agp 3.16.55 base-system
linux64-crypto 3.16.55 base-system
linux64-hfsplus 3.16.55 base-system
linux64-wireless 3.16.55 base-system
lzlib 4.57 base-system
lzma 4.57 base-system
m4 1.4.18 development
memtest 5.01 base-system
ncurses 6.2 base-system
ncurses-common 6.2 base-system
ncursesw 6.2 base-system
openssl 1.0.2u security
pciids 20200329 misc
pcre 8.44 system-tools
pcre-dev 8.44 development
perl 5.14.1 development
pkg-config 0.29.2 development
plop 5.0.15 base-system
python 2.7.17 development
readline 8.0 system-tools
sdft 170314 development
slitaz-base-files 343 base-system
slitaz-boot-scripts 466 base-system
slitaz-configs-base 317 base-system
slitaz-tools 1036 system-tools
sqlite 3.32.1 office
tazlito 529 base-system
tazpkg 944 base-system
udev 182 base-system
usbids 20191031 misc
util-linux-blkid 2.35.1 base-system
util-linux-mount 2.35.1 base-system
util-linux-smartcols 2.35.1 system-tools
util-linux-uuid 2.35.1 base-system
wireless_tools 29 system-tools
zlib 1.2.11 base-system
It should provide a good starting base. Probably some packages might be excluded or other added.
Offline
So, doing a bit of comparison, these are the packages from the base flavor list that are missing in the system I created from 210227_rootfs.gz.
Those marked
F- are present in Filou's website, so I can download, install, and test them.
Those marked
-- I might try to cook later from the LFS wok (which I am downloading now).
F-gdbm 1.18.1 misc
F-gettext-tools 0.19.8.1 libs
F-glib 2.43.3 x-window
F-glibc 2.14.1 meta
F-glibc-locale 2.14.1 system-tools
F-kbd 2.2.0 system-tools
F-libcroco 0.6.13 system-tools
F-libcrypto 1.0.2u security
F-libdb 6.2.23 misc
F-libgio 2.43.3 x-window
F-libsqlite 3.32.1 office
--libssl 1.0.2u security
F-libxml2 2.9.10 system-tools
F-libxml2-tools 2.9.10 system-tools
--linux 3.16.55 base-system
--linux64 3.16.55 base-system
--linux64-agp 3.16.55 base-system
--linux64-crypto 3.16.55 base-system
--linux64-hfsplus 3.16.55 base-system
--linux64-wireless 3.16.55 base-system
--memtest 5.01 base-system
F-ncurses 6.2 base-system
F-openssl 1.0.2u security
F-pcre 8.44 system-tools
--plop 5.0.15 base-system
F-readline 8.0 system-tools
F-sqlite 3.32.1 office
--wireless_tools 29 system-tools
Offline
I have installed all the packages on the list from Filou's website.
I have rebooted into the system and everything seems okay, although I haven't had the chance to do much.
I couldn't attach a file with the dmesg output but you can see it here:
https://pastebin.com/Gwxuj889
This is the new list of installed packages:
List of all installed packages
================================================================================
acl 2.2.53 system-tools
attr 2.4.48 system-tools
busybox 1.31.1 base-system
bzlib 1.0.8 utilities
cdrkit 1.1.11 utilities
cookutils 887 base-system
dialog 1.3_20190211 base-system
dropbear 2020.81 security
e2fsprogs 1.45.5 base-system
efibootmgr 16 system-tools
efivar 37 system-tools
fuse 2.9.9 system-tools
gcc-lib-base 10.2.0 development
gdbm 1.18.1 misc
get-anydesk 1.00 non-free
gettext 0.19.8.1 development
gettext-base 0.19.8.1 base-system
gettext-tools 0.19.8.1 libs
glib 2.64.4 x-window
glibc 2.32 meta
glibc-base 2.32 base-system
glibc-locale 2.32 system-tools
grub4dos-linux 0.4.4 system-tools
ipxe 1.20.1 system-tools
isapnptools 1.27 system-tools
kbd 2.2.0 system-tools
kbd-base 2.2.0 base-system
kmod 23 base-system
libcap 2.33 system-tools
libcomerr 1.45.5 base-system
libcroco 0.6.13 system-tools
libcrypto 1.0.2u security
libdaemon-dev 0.14 development
libdb 6.2.23 misc
libgio 2.64.4 x-window
liblzma 5.2.5 misc
libsqlite 3.32.1 office
libxml2 2.9.10 system-tools
libxml2-tools 2.9.10 system-tools
linux 4.17.7 base-system
lzlib 4.57 base-system
lzma 4.57 base-system
ncurses 6.2 base-system
ncurses-common 6.2 base-system
ncursesw 6.2 base-system
openssl 1.0.2u security
parted 3.2 system-tools
pciids 20200329 misc
pcmciautils 018 system-tools
pcre 8.44 system-tools
popt 1.18 system-tools
posixovl 1.3 system-tools
ppp 2.4.7 network
readline-dev 8.0 development
rp-pppoe 3.13 network
sdft 170314 development
slitaz-base-files 343 base-system
slitaz-boot-scripts 466 base-system
slitaz-configs-base 317 base-system
slitaz-tools 1036 system-tools
sqlite 3.32.1 office
sysfsutils 2.1.0 system-tools
syslinux 4.06 base-system
syslinux-extra 4.06 system-tools
tazinst 108 base-system
tazirc 22 network
tazlito 529 base-system
tazpkg 944 base-system
tazusb 209 base-system
terminus-font-base 4.40 system-tools
udev 182 base-system
usbids 20191031 misc
util-linux-blkid 2.35.1 base-system
util-linux-mount 2.35.1 base-system
util-linux-smartcols 2.35.1 system-tools
util-linux-uuid 2.35.1 base-system
zlib 1.2.11 base-system
================================================================================
77 packages installed.
Offline
Hi,
alanyih, i update slitaz.conf to right arch 'x86_64', i also update mirror for tazpkg to point on my repo, and also add aufs module 5.4.3.
slitaz-basevm.iso as updated.
Need to rebuild packages to fix deps (git repo is uptodate).
Offline
Now i have sanity env with tazdev.
[c]Generating new chroot in: /home/slitaz/unstable/chroot
================================================================================
Mirror URL: people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/[ Done ]
Installing: slitaz-base-files [ Done ]
Installing: busybox
[ Done ]
Installing: cookutils [ Done ]
Installing: tazpkg [ Done ]
Installing: lzma [ Done ]
Creating resolv.conf...[ Done ]
Creating TZ...[ Done ]
Restoring host packages list...[ Done ]
================================================================================
Ready to chroot with: tazdev -c unstable[/c]
Need fix about /lib symlink to /lib64
[c]root@slitaz:~# tazdev -c unstable
Mounting virtual filesystems...[ Done ]
Chrooting to: /home/slitaz/unstable/chroot
root@slitaz:/# tazpkg list
List of all installed packages
================================================================================
busybox 1.31.1 base-system
cookutils 3.1.7 base-system
gcc-lib-base 9.2.0 development
gettext-base 0.19.8.1 base-system
glibc-base 2.31 base-system
lzlib 4.57 base-system
lzma 4.57 base-system
ncurses-common 6.2 base-system
slitaz-base-files 309 base-system
tazpkg 5.3.3 base-system
zlib 1.2.11 base-system
================================================================================
11 packages installed.[/c]
Offline
@shann
Thanks.
slitaz-basevm.iso 2021-Mar-04 09:12:16 10.5M
root@slitaz:~# slitaz
SliTaz GNU/Linux
================================================================================
Release : cooking
Architecture : x86_64
Kernel : 5.4.101-vm
Machine type : x86_64
Home path : /home/slitaz
Configs : /etc/slitaz
Main config : /etc/slitaz/slitaz.conf
Log files : /var/log/slitaz
Packages DB : /var/lib/tazpkg
Installed : 22 packages
Mirror : http://people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/
System date : Fri Mar 5 05:21:52 UTC 2021
--------------
Boot options : initrd=/boot/rootfs.gz rw root=/dev/null BOOT_IMAGE=/boot/bzImage
================================================================================
Offline
I'm curious.
Filou and shann seem to be doing a great job, but on separate ways.
1) are the packages from
https://c.web.de/@337942326598965997/QhaNFMiJQhuEqY3q66F8Xg
and
http://people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/
compatible? (Filou mentioned in a previous post that they were built using different libraries).
2) are you guys somehow coordinating your efforts toward the creation of a single, base x86_64 Slitaz version?
Offline
@shann
tazdev gen-chroot {name_env} --mirror="http://people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/"
Ref:
82 check_mirror() {
http://hg.slitaz.org/slitaz-dev-tools/file/3a966a7b4ac9/tazdev/tazdev#l82
20 # Main mirror to push and download (ISO, rootfs. etc).
21 MIRROR="mirror.slitaz.org"
22 MIRROR_PKGS="/var/www/slitaz/mirror/packages"
23 MIRROR_SOURCES="/var/www/slitaz/mirror/sources"
http://hg.slitaz.org/slitaz-dev-tools/file/3a966a7b4ac9/tazdev/tazdev.conf#l20
Offline
@sofia-m:
Your curiosity is perfectly right. shann and I had a couple of contacts through this forum a couple of weeks ago and I learned, that his first steps, on the basis of alanyih's previous work, went into the same direction, using LFS as a basis for further development.
As I have to admit, I didn't understand (and up to now don't) where any x86_64 version of SliTaz was / is developed, I started over with the latest LFS version in order to build a wok up to what you can download from my webspace (and I still to improve).
My intent was, when switching over to 64bit with what our / my very positive experience with Slitaz32 were, why change anything but the packages themselves, when we can keep all the principles and scripts? So I try to stick as close to Slitaz32, build the 64bit packages and slowly replacing the 32bit ones one by one, maybe patching some of the scripts, to achieve a working Slitaz64.
I also see that shann and alanyih proceed in parallel, but don't understand how to switch over to support their work and judging if I'd better put my efforts in their work or proceeding with mine.
@shann/alanyih: I see your conversation but lack the basis to understand it. Do you work on any already working 64bit basis? Should I / we cease to work on the "latest LFS wok / packages" and support you or should be proceed and later join the packages and experiences?
Offline
@Filou
Thanks a lot for your explanation. I think your your initiative is admirable.
Beside its practical value, it must have a great learning experience.
I was able to install many packages from your website, and they seem to work well.
On the other hand, I imagine that creating a distribution and, above all, maintain it up to date, requires so much work that coordinated help is always welcome.
I assume is just a matter of communication.
The next64 repo, for instance, is quite complete but a bit outdated. Also, as shann explained in a previous reply: "used 'old' toolchain GCC8, kernel 4.*."
It makes sense to have an x64 Slitaz built on up-to-date libs in a standardized way.
shann seems to have taken steps to create a x64 repo at: http://people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/
so, perhaps, that could be the place were to add newly created packages.
@shann
I didn't really understand this part:
"slitaz_x64 tarball doesn't have kernel because goal to can be used as this on any distribution."
Shouldn't a slitaz64 kernel be the base of the whole distro?
Offline
@shann
Okay, I think I got it now. You meant the slitaz_x64 tarball is meant to be used in a chroot from another Linux distribution.
I tried to install the slitaz-basevm.iso on the hard disk using the slitaz installer 'install iso' moede from a live system.
It worked well, apparently, but when I rebooted I discovered that it had installed basevm but with the live systems' kernel, which of course made the system unbootable. Weird.
Offline
@shann
I made a test, tried to install python3 from your repo on basevm
It worked well, you can see the output at:
https://pastebin.com/TF6zmgSk
Offline
Hi sofia-m,
Sorry for inconvenient, infact kernel i build is custom for vm, slitaz-basevm.iso goal to used as vm not on hardware and rootfs for chroot.
I check history of forum for curiosity, not parsed all topics 
, but begin of work of x86_64 isn't new it's few 8 years ago, i find this topic "https://forum.slitaz.org/topic/64-bit-version"
~2013 pankso begin work on cross tools for ARM / x86_64 support, first step as build x86_64 kernel and continue use 32bits userland.
Of course, we need coordonate.
I suggest this guidelines :
- define toolchain used, need fixed and also improved.
- works on same wok, also synchronize with hg.slitaz.org/wok or wok-next
- use same dev env and slitaz tools (tazdev, cooker, ...)
- have cooker env (https://cook.slitaz.org)
- define milestones to split work, "base bootable" (aka slitaz base cli), justx, ...
In my case my wok use receipt v1, and not follow SliTaz 5.0 base files, based on slitaz 4.0/cooking.
I go to rework them with 5.0 and receipt v2.
I am open to all suggestions so that we define and build a common guideline.
@Filou, @alanyih, any member who wants to get involved.
Offline
@shann
Thanks for your answer, it's much clearer now. I didn't catch the 'vm' significance in the ISO's name
I think your guidelines make sense. Well defined goals and unified tools would speed up progress and optimize the effort.
As Filou pointed out in previous posts, Slitaz is a well thought-out distro, there is little need to change its structure, except for bringing it up to date and make it full x64.
Offline
Short update: just reached >900 x86_64 packages in my webspace, proceeded alphabetically up to py, will push on.
After the first iteration through to z, I'll concentrate on the necessary packages to finish a working wok, after that I'll try to further contribute the up to now failing packages...
Offline
@Filou
Congratulations!
980 of 980 Download
Offline
@Filou
980 of 980 Download
please check pkgdb
bandle.tar.lzma 03/08/21 92.3kb
packages.info 02/13/21 41.3kb
packages.list 02/13/21 0 Byte
packages.md5 02/13/21 0 Byte
$ tar tvf bundle.tar.lzma
-rw-r--r-- root/root 783 2021-02-09 17:53 mirrors
-rw-r--r-- root/root 4860 2021-02-09 17:53 extra.list
-rw-r--r-- root/root 32 2021-02-09 17:53 files-list.md5
-rw-r--r-- root/root 1892 2021-02-09 17:53 packages.info
-rw-r--r-- root/root 286552 2021-02-09 17:53 descriptions.txt
-rw-r--r-- root/root 1646 2021-02-09 17:53 packages.desc
-rw-r--r-- root/root 0 2021-02-09 17:53 packages.md5
-rw-r--r-- root/root 1076 2021-02-09 17:53 packages.txt
-rw-r--r-- root/root 0 2021-02-09 17:53 packages.list
-rw-r--r-- root/root 0 2021-02-09 17:53 packages.equiv
$ cat packages.info | wc -l
14
$ tar tvf bundle-0213.tar.lzma
-rw-r--r-- root/root 783 2021-02-13 21:27 mirrors
-rw-r--r-- root/root 4860 2021-02-13 21:28 extra.list
-rw-r--r-- root/root 32 2021-02-13 21:27 files-list.md5
-rw-r--r-- root/root 42338 2021-02-13 21:27 packages.info
-rw-r--r-- root/root 286552 2021-02-13 21:27 descriptions.txt
-rw-r--r-- root/root 35148 2021-02-13 21:27 packages.desc
-rw-r--r-- root/root 0 2021-02-13 21:27 packages.md5
-rw-r--r-- root/root 25359 2021-02-13 21:27 packages.txt
-rw-r--r-- root/root 0 2021-02-13 21:27 packages.list
-rw-r--r-- root/root 228 2021-02-13 21:27 packages.equiv
Offline
@alanyih:
You're right, I always only upload the packages and don't update the absolutely old pkgdb (it's because I treat the webspace as a package collection rather than a repository...).
I'll try to update these files during the next update, too...
Thank you for the hint!
Offline
Perl and Python subpackages lead to a quick and big leap ahead!
The 1.000 packages sonic wall has fallen...
1.100+ packages in my webspace. (I updated the pkgdb too, but am not sure, if all went well here; the packages.list and packages.md5 are still empty, but the rest are updated...).
Python subpackages are still to be completed.
@sofia-m:
This might be a good opportunity to test the environment and the perl packages. If you could test perl with some simpler and maybe later perl projects, we could find out if the system is on the right trail...?!?
Will proceed....
Cheers!
Offline
@Filou
I have copied the rootfs64 from your website onto a partition and installed a 64 kernel.
It boots fine, but this is the output I get:
#slitaz
SliTaz GNU/Linux
====================================================================================
Release : 5.0
Architecture : i486
Kernel : 3.16.55-slitaz64
Machine type : x86_64
Home path : /home/slitaz
Configs : /etc/slitaz
Main config : /etc/slitaz/slitaz.conf
Log files : /var/log/slitaz
Packages DB : /var/lib/tazpkg
Installed : 55 packages
Mirror : http://mirror1.slitaz.org/packages/cooking/
System date : Mon Mar 15 18:18:16 America 2021
--------------
Boot options : BOOT_IMAGE=/boot/vmlinuz-3.16.55-slitaz64 root=/dev/sda11
=========================================================================
As you can see, Release is 5.0, Architecture is i486, and Mirror still points to http://mirror1.slitaz.org/packages/cooking/.
Those values should be different in order to use your website as a repo.
Also, even after coping the running resolv.conf to /etc in the chroot env, I cannot connect to the web.
I can download the packages and install them, of course, but it would be interesting to test if your website can be used as a repo.
Offline
@Filou
210227_rootfs64.gz
/usr/bin/lzma-alone: line 1: syntax error: unexpected "("
ping: bad address 'www.slitaz.org'
nslookup: write to '127.0.0.1': Connection refused
;; connection timed out; no servers could be reached
ls: /lib/libns*: No such file or directory
glibc-base: missing libraries and link error
1.
root@slitaz:/opt/rootfs64# lzma d /opt/210227_rootfs64.gz -so | cpio -idm
55985 blocks
root@slitaz:/opt/rootfs64# tazdev -c /opt/rootfs64
Mounting virtual filesystems... [ Done ]
Chrooting to: /opt/rootfs64
root@slitaz:/# /lib/libc.so.6
GNU C Library (GNU libc) release release version 2.32.
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 10.2.0.
libc ABIs: UNIQUE IFUNC ABSOLUTE
For bug reporting instructions, please see:
<https://www.gnu.org/software/libc/bugs.html>.
root@slitaz:/# ldd /lib/libc.so.6
/lib/libc.so.6:
/lib/ld-linux-x86-64.so.2 (0x00007f3f073bb000)
linux-vdso.so.1 (0x00007fffc6b2d000)
2.
root@slitaz:/# grep ARCH /etc/slitaz/slitaz.conf
SLITAZ_ARCH="i486"
root@slitaz:/# cat /var/lib/tazpkg/mirror
http://mirror1.slitaz.org/packages/cooking/
3.
root@slitaz:/# busybox | head -1
BusyBox v1.31.1 (2021-01-28 19:51:59 CET) multi-call binary.
root@slitaz:/# blkid -version
blkid from util-linux 2.36 (libblkid 2.36.0, 23-Jul-2020)
root@slitaz:/# dropbear -V
Dropbear v2020.81
root@slitaz:/# lzma --help
/usr/bin/lzma-alone: line 1: syntax error: unexpected "("
root@slitaz:/# parted --help
/usr/sbin/parted: line 1: syntax error: unexpected "("
root@slitaz:/# grub --help
/usr/sbin/grub: line 1: syntax error: unexpected "("
4.
root@slitaz:/# tazpkg -i libmagic-5.38-x86_64.tazpkg file-5.38-x86_64.tazpkg
root@slitaz:/# file /lib/libc.so.6
/lib/libc.so.6: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped
root@slitaz:/# file /bin/busybox
/bin/busybox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped
root@slitaz:/# file /usr/bin/lzma-alone
/usr/bin/lzma-alone: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.30, stripped
root@slitaz:/# file /usr/sbin/grub
/usr/sbin/grub: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.30, stripped
root@slitaz:/# file /usr/sbin/parted
/usr/sbin/parted: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.30, stripped
root@slitaz:/# file /lib/liblz.so.1.0.0
/lib/liblz.so.1.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), statically linked, stripped
root@slitaz:/# file usr/lib/libefivar.so.1.37
usr/lib/libefivar.so.1.37: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), statically linked, BuildID[sha1]=ad2926f231f798092c41d6dedd7bb87243d80686, stripped
root@slitaz:/# head -34 /var/lib/tazpkg/installed.md5
db805c755030485e1e4c69376208070c busybox-1.31.1.tazpkg
c334e8b3f34f1db84c424e15ac47f841 cdrkit-1.1.11.tazpkg
c7d530c834b6dd72d25273969c151f71 cookutils-887.tazpkg
766b9b0dba7622a4d907e4a4e4b7627e util-linux-blkid-2.35.1.tazpkg
d1262d5c293fa6e88d93d1c82811df35 util-linux-mount-2.35.1.tazpkg
0b9cbc238eb786cec9dc9b4e15b7531c util-linux-smartcols-2.35.1.tazpkg
dfa7ad54d6250eea2957b899adb8f960 util-linux-uuid-2.35.1.tazpkg
e7b538706e3d04acad479f83801d0f6f grub4dos-linux-0.4.4.tazpkg
02eecc43b9d5362fa4144bcf0bcb17fb ipxe-1.20.1.tazpkg
dff993ca5d80cf550ecacaa0ea119e18 isapnptools-1.27.tazpkg
59ff501aba17d0e54132aa68ff0d4124 lzma-4.57.tazpkg
c94a60a44e12402dca75b334072c34af lzlib-4.57.tazpkg
21203046fa30682c3cc11d6c71a622e1 pcmciautils-018.tazpkg
6dea5f833c9d894f6b4a94ce76380752 ppp-2.4.7.tazpkg
82849fc74b7dc9bef38d02dfbf5fb15e rp-pppoe-3.13.tazpkg
cfe777464737c203ea6f8f68de327acb slitaz-base-files-343.tazpkg
ad80aa99169bb31d2403a31785252d5d slitaz-boot-scripts-466.tazpkg
67ec3083c3eba6942e7752a60994b523 slitaz-configs-base-317.tazpkg
83ae237d5d5e1248bed68a2ac2b9014f slitaz-tools-1036.tazpkg
010251971d3215a8bf505d35ba28ba2b syslinux-4.06.tazpkg
32971a7fa793e5d1d97a47b73dca085b syslinux-extra-4.06.tazpkg
8a453ce04d021194a3acb77de573b4a0 tazinst-108.tazpkg
9fa605197d071f3de113a8b6499c055c parted-3.2.tazpkg
6bd5914ab97189e78f4158c7e6685924 efibootmgr-16.tazpkg
f1a79076e9d96def430793ef79cd1c60 efivar-37.tazpkg
761083b6e6eddc41c624d4966fe0a256 tazlito-529.tazpkg
a8341b913745dfd3bca527645a41a015 tazpkg-944.tazpkg
249a5908f2baf65fcd7b437b786b395e tazusb-209.tazpkg
97a1b95be6b0839d89c09efcc1e46f0e tazirc-22.tazpkg
8922a3550aa075627dfce125d47ea591 udev-182.tazpkg
ab02e544ba3e51470e52b5ed24b38e2e terminus-font-base-4.40.tazpkg
fb8a37a677b35c8b75e21c886b0b550e acl-2.2.53-x86_64.tazpkg
8367787ae24613257fcd0898e404e60b attr-2.4.48-x86_64.tazpkg
575c7c7845c96a61cc9843cb0f88f912 bzlib-1.0.8-x86_64.tazpkg
root@slitaz:/#
5.
root@slitaz:/# ping -c4 www.slitaz.org
ping: bad address 'www.slitaz.org'
root@slitaz:/# nslookup www.slitaz.org
nslookup: write to '127.0.0.1': Connection refused
;; connection timed out; no servers could be reached
root@slitaz:/# cat /etc/resolv.conf
root@slitaz:/# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 0 Feb 27 15:44 /etc/resolv.conf
root@slitaz:/# ls -l /lib64
total 0
lrwxrwxrwx 1 root root 27 Mar 8 02:00 ld-linux-x86-64.so.2 -> ../lib/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 27 Mar 8 02:00 ld-lsb-x86-64.so.3 -> ../lib/ld-linux-x86-64.so.2
root@slitaz:/# ls -l /lib/libns*
ls: /lib/libns*: No such file or directory
root@slitaz:/# tazpkg -lf glibc-base | grep libns
Recharging repository "Main"
================================================================================
Checking... [ Failed ]
Creating backup of the last packages list... [ Done ]
Getting "bundle.tar.lzma"... [ Failed ]
Restoring database files... [ Done ]
================================================================================
Recharging failed
/lib64/libnsl-2.32.so
/lib64/libnsl.so.1
/lib64/libnss_compat-2.32.so
/lib64/libnss_compat.so.2
/lib64/libnss_dns-2.32.so
/lib64/libnss_dns.so.2
/lib64/libnss_files-2.32.so
/lib64/libnss_files.so.2
/usr/lib64/libnsl.so
/usr/lib64/libnss_compat.so
/usr/lib64/libnss_dns.so
/usr/lib64/libnss_files.so
root@slitaz:/# ls -l /usr/lib64
total 12
drwxr-xr-x 2 root root 4096 Mar 8 02:00 gconv
lrwxrwxrwx 1 root root 23 Mar 8 02:00 libanl.so -> ../../lib64/libanl.so.1
lrwxrwxrwx 1 root root 25 Mar 8 02:00 libcrypt.so -> ../../lib64/libcrypt.so.1
lrwxrwxrwx 1 root root 22 Mar 8 02:00 libdl.so -> ../../lib64/libdl.so.2
-rw-r--r-- 1 root root 110 Feb 27 15:44 libm.so
lrwxrwxrwx 1 root root 23 Mar 8 02:00 libnsl.so -> ../../lib64/libnsl.so.1
lrwxrwxrwx 1 root root 30 Mar 8 02:00 libnss_compat.so -> ../../lib64/libnss_compat.so.2
lrwxrwxrwx 1 root root 27 Mar 8 02:00 libnss_dns.so -> ../../lib64/libnss_dns.so.2
lrwxrwxrwx 1 root root 29 Mar 8 02:00 libnss_files.so -> ../../lib64/libnss_files.so.2
lrwxrwxrwx 1 root root 26 Mar 8 02:00 libresolv.so -> ../../lib64/libresolv.so.2
lrwxrwxrwx 1 root root 22 Mar 8 02:00 librt.so -> ../../lib64/librt.so.1
lrwxrwxrwx 1 root root 29 Mar 8 02:00 libthread_db.so -> ../../lib64/libthread_db.so.1
lrwxrwxrwx 1 root root 24 Mar 8 02:00 libutil.so -> ../../lib64/libutil.so.1
drwxr-xr-x 2 root root 4096 Feb 27 15:44 locale
root@slitaz:/#
[attachment=49897,3070]
Offline
Thank you for the tests, the support and the feedback!
In fact my routine for repacking the rootfs after a change missed out the /lib64 path, breaking many functions.
As I described earlier, I used a x486 Slitaz as the base for the further steps. Therefore, some residuals still existed in the package.
So now I
- corrected the ARCH information in /etc/slitaz/slitaz.conf
- reinstalled glibc-base
- repacked everything INCLUDING /lib64 ;-)
- deleted 32bit packages parted and grub, which I was not able to cook in 64bit yet
- deleted 32bit version of lzma-alone, which did not cook in 64bit when derived from p7zip. LFS produces lzma from the xz package, which has some differing command line parameters (which was why I had to patch /usr/libexec/cookutils/* in the wok). For the time being, I linked lzma back to busybox
- pointed /var/lib/tazpkg/mirror to my webspace, which does not lead to a working repository yet. I will still have to build the correct database files there for that to function...
[EDIT]: I was able to build the database files but tazpkg produces an error when accessing the webspace directly due to the html headers... will have to look for another solution...
Maybe we have a place on the slitaz mirrors where we can put the repository?!?!
I uploaded an updated version of the minimal rootfs to my webspace...
[attachment=49903,3073] [attachment=49903,3075]
[EDIT]:
I had to realize that the latest rootfs is broken... :-(
In the previous version I still had some 32bit residuals as explained, udev being one of them.
By correcting the missing glibc files, udev ceases to work.
I first did not catch this while working in the unpacked image on a chroot basis (which seems to be triggered by the native udev events), but when booting directly, I could log in and got eudev and the system running starting [c]/etc/init.d/rcS start[/c] but a couple of features did not work (like network for example)...
Since the latest udev version is from 2012 and uses code that is deprecated or even discarded in recent glibc versions, I am afraid we will have to switch to other tools. LFS chooses eudev, which is why I will try to follow this path.
As there are a good amount of dependencies on udev, this will be a tougher one...
Offline
Playing around some more, I could find out that gibor's advice concerning eudev and the naming of network devices fooled me here, too...
So adding another (empty) "rule" to rules.d dir brought back the network.
What I am experiencing now is that during boot and shutdown, missing libraries are reported and the system seems to stagger:
- libblkid.so.1
- libmount.so.1
- libncursesw.so.6
although those are installed in /lib/ (now even recompiled and reinstalled) and seem to be working...:
when I log in as root and set up again by invoking /etc/init.d/rcS start, the system shows a nearly fine "bootup"; calling blkid or lsblk output is fine and even invoking by udevadm works.
During poweroff/reboot another error message about missing libncursesw.so.6 is reported...
Does anybody have an idea or hint concerning the bootup/shutdown process here?
Offline
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.68 MiB (Peak: 1.77 MiB) ]
