[SOLVED] Slackware 14.1 32bit system tarball/stage3 image/chroot image/bootstrap image

vinipsmaker · 05-11-2014, 11:34 AM

I need an image containing a Slackware installation (the root folder that contains the bin, etc, var, usr, ... folders). I've lost some hours on Google and I was unable to find such image.

Where can I find one?

ruario · 05-11-2014, 12:17 PM

Why do you need an image? Just decide which packages you want to install and use installpkg with the --root switch to set to the location of your chroot folder.

vinipsmaker · 05-11-2014, 12:24 PM

Quote:

Originally Posted by ruario

Why do you need an image? Just decide which packages you want to install and use installpkg with the --root switch to set to the location of your chroot folder.

I don't have a Slackware installation. That's why I need an image... to install Slackware... inside a container.

It's the oldest distro still going on. I'm pretty confident this image must exist.

ponce · 05-11-2014, 12:41 PM

sorry, inside which kind of container?

I don't think there are tarballs available with the root filesystem of a full installation for the x86/x86_64 arch (for arm there's the minirootfs)...

if you want to use installpkg on another system, you need just the pkgtools package (it's a tarball, so you can easily extract it).

vinipsmaker · 05-11-2014, 12:42 PM

Quote:

Originally Posted by ponce

sorry, inside which kind of container?

LXC, but I can take care of the configuration myself. I just need the "filesystem tarball".

ponce · 05-11-2014, 01:24 PM

here they are, 32 and 64 bit: I just created them

http://ponce.cc/slackware/lxc/

vinipsmaker · 05-11-2014, 01:27 PM

Quote:

Originally Posted by ponce

here they are, 32 and 64 bit: I just created them

http://ponce.cc/slackware/lxc/

Thank you anon.

ponce · 05-11-2014, 01:34 PM

np.

if you want to assemble them yourself or, for any reason, you need more infos about lxc on Slackware, you can refer to

https://slackware.ponce.cc/blog/2012...lackware-14-0/
https://slackware.ponce.cc/blog/2014...4-14-1current/
http://www.vislab.uq.edu.au/howto/lxc/lxc.html

vinipsmaker · 05-11-2014, 01:51 PM

Quote:

Originally Posted by ponce

here they are, 32 and 64 bit: I just created them

http://ponce.cc/slackware/lxc/

I just noticed you container is minimal, which is fine, but doesn't come with the standard Slackware tools (such as installpkg, removepkg, upgradepkg, makepkg, explodepkg, pkgtool), which makes me doubt if I can refer to this container as a Slackware container.

Anyway, I'll hunt the required packages and extract them. Thanks for the help so far. I think I can manage from here.

ruario · 05-11-2014, 01:52 PM

Quote:

Originally Posted by ponce

if you want to use installpkg on another system, you need just the pkgtools package (it's a tarball, so you can easily extract it).

To expand on that for the benefit of the OP or others reading this, just fetch the installpkg script. Make it executable and use it to install your selected Slackware packages from your host system using an appropriate --root option. You will get a warning about using a non tar version 1.13 version. This is indeed not ideal but it should be good enough for purposes like setting up a chroot/LXC. Non 1.13 tar is more of an issue for removepkg and makepkg.

If you want you could remove the -U and -l options from the tar extraction in installpkg, as their meanings have changed in later versions of tar. Here is a patch:

Code:

--- installpkg.orig
+++ installpkg
@@ -93,22 +93,7 @@
 
 # So that we know what to expect...
 umask 022
-TAR=tar-1.13
-$TAR --help 1> /dev/null 2> /dev/null
-if [ ! $? = 0 ]; then
-  TAR=tar
-fi
-if [ ! "$(LC_MESSAGES=C $TAR --version)" = "tar (GNU tar) 1.13
-
-Copyright (C) 1988, 92,93,94,95,96,97,98, 1999 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.
-
-Written by John Gilmore and Jay Fenlason." ]; then
-  echo "WARNING: pkgtools are unstable with tar > 1.13."
-  echo "         You should provide a \"tar-1.13\" in your \$PATH."
-  sleep 5
-fi
+TAR=tar
 
 usage() {
  cat << EOF
@@ -519,7 +504,7 @@
     cat $DESCRIPTION | grep "^$shortname:" >> $ADM_DIR/packages/$shortname 2> /dev/null
   fi
   echo "FILE LIST:" >> $ADM_DIR/packages/$shortname
-  ( cd $ROOT/ ; $packagecompression -dc | $TAR -xlUpvf - ) < $package >> $TMP/$shortname 2> /dev/null
+  ( cd $ROOT/ ; $packagecompression -dc | $TAR -xpvf - ) < $package >> $TMP/$shortname 2> /dev/null
   if [ "$(cat $TMP/$shortname | grep '^\./' | wc -l | tr -d ' ')" = "1" ]; then
     # Good.  We have a package that meets the Slackware spec.
     cat $TMP/$shortname >> $ADM_DIR/packages/$shortname

Save the above as installpkg.patch in the directory where you saved installpkg and issue the following command:

Code:

patch < installpkg.patch

If you are interested to find out more about why Slackware uses GNU tar 1.13, read this. This more recent post might also be interesting.

ruario · 05-11-2014, 01:55 PM

Quote:

Originally Posted by vinipsmaker

doesn't come with the standard Slackware tools (such as installpkg, removepkg, upgradepkg, makepkg, explodepkg, pkgtool), which makes me doubt if I can refer to this container as a Slackware container.

Anyway, I'll hunt the required packages and extract them. Thanks for the help so far. I think I can manage from here.

You can get these here. Install it with installpkg from your host system, as explained in my previous post, or from within the lxc.

ponce · 05-11-2014, 01:58 PM

Quote:

Originally Posted by vinipsmaker

I just noticed you container is minimal, which is fine, but doesn't come with the standard Slackware tools (such as installpkg, removepkg, upgradepkg, makepkg, explodepkg, pkgtool), which makes me doubt if I can refer to this container as a Slackware container.

Anyway, I'll hunt the required packages and extract them. Thanks for the help so far. I think I can manage from here.

I don't know where you're actually looking for them, but all the commands you cited are in the /sbin directory of the container filesystem.

Code:

$ ls -la /var/lib/lxc/slack32/rootfs/var/log/packages/pkgtools-14.1-noarch-2 
-rw-r--r-- 1 root root 1331 May 11 20:16 /var/lib/lxc/slack32/rootfs/var/log/packages/pkgtools-14.1-noarch-2
$ ls -la /var/lib/lxc/slack32/rootfs/sbin/ | grep pkg 
-rwxr-xr-x  1 root root   3169 May 11  2010 explodepkg
-rwxr-xr-x  1 root root  20490 Apr 22  2011 installpkg
-rwxr-xr-x  1 root root  11315 Jun  2  2009 makepkg
-rwxr-xr-x  1 root root  22670 Oct  3  2013 pkgtool
-rwxr-xr-x  1 root root  14048 Apr 28  2009 removepkg
-rwxr-xr-x  1 root root  12135 May 11  2010 upgradepkg

Didier Spaier · 05-11-2014, 02:03 PM

Quote:

Originally Posted by ruario

If you are interested to find out more about why Slackware uses GNU tar 1.13, read this. This more recent post might also be interesting.

I just noticed that in Slackware-current's installer, two versions of tar are shipped:

Code:

/tmp$ ls -l initrd-Slackware-current/bin/tar*
-rwxr-xr-x 1 didier users 269332 avril 14  2011 initrd-Slackware-current/bin/tar
-rwxr-xr-x 1 didier users 122396 avril 14  2011 initrd-Slackware-current/bin/tar-1.13
lrwxrwxrwx 1 didier users      3 mai   11 11:28 initrd-Slackware-current/bin/tar-1.26 -> tar
/tmp

As a reminder, in Slackware 14.1's installer instead:

Code:

/tmp$ ls -l initrd-Slackware-14.1/bin/tar*
lrwxrwxrwx 1 didier users      8 mai   11 11:28 initrd-Slackware-14.1/bin/tar -> tar-1.13
-rwxr-xr-x 1 didier users 122396 avril 14  2011 initrd-Slackware-14.1/bin/tar-1.13
/tmp$

I don't know why Pat made this change, but he certainly knows

vinipsmaker · 05-11-2014, 02:05 PM

Quote:

Originally Posted by ponce

I don't know where you're actually looking for them, but all the commands you cited are in the /sbin directory of the container filesystem.

Code:

$ ls -la /var/lib/lxc/slack32/rootfs/var/log/packages/pkgtools-14.1-noarch-2 
-rw-r--r-- 1 root root 1331 May 11 20:16 /var/lib/lxc/slack32/rootfs/var/log/packages/pkgtools-14.1-noarch-2
$ ls -la /var/lib/lxc/slack32/rootfs/sbin/ | grep pkg 
-rwxr-xr-x  1 root root   3169 May 11  2010 explodepkg
-rwxr-xr-x  1 root root  20490 Apr 22  2011 installpkg
-rwxr-xr-x  1 root root  11315 Jun  2  2009 makepkg
-rwxr-xr-x  1 root root  22670 Oct  3  2013 pkgtool
-rwxr-xr-x  1 root root  14048 Apr 28  2009 removepkg
-rwxr-xr-x  1 root root  12135 May 11  2010 upgradepkg

I found them.

Looks like it's a problem of lxc-attach vs lxc-console. lxc-attach won't update the PATH env var. I'll use lxc-console from now on.

Thanks again.

ruario · 05-11-2014, 02:08 PM

Quote:

Originally Posted by Didier Spaier

As a reminder, in Slackware 14.1's installer instead:

Code:

/tmp$ ls -l initrd-Slackware-14.1/bin/tar*
lrwxrwxrwx 1 didier users      8 mai   11 11:28 initrd-Slackware-14.1/bin/tar -> tar-1.13
-rwxr-xr-x 1 didier users 122396 avril 14  2011 initrd-Slackware-14.1/bin/tar-1.13
/tmp$

I don't know why Pat made this change, but he certainly knows

Stuart also knows.

Quote:

Originally Posted by drmozes

It appears that it was my idea to wipe out the latest version of tar and symlink tar-1.13 to tar anyway (seemed optimal and efficient 6 years ago! ;-) ). I've added it to my installer to do list - Pat will most likely accept this change as it's non intrusive - although you'll only know if it appears ;-)