SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
chmod: cannot access '/mnt/chroot//var': No such file or directory
chmod: cannot access '/mnt/chroot//usr': No such file or directory
chmod: cannot access '/mnt/chroot//tmp': No such file or directory
I created those directories manually, when I issued the command again nothing happened?
I was thinking this would bring up Dialog to let me choose which packages I wanted to install in the chroot directory. Or am I doing something wrong?
I believe it would just be /mnt since that is the mountpoint of / when using the install disk. In other words no /chroot. I honestly can't say for sure since I usually only have a few packages to install from /extra after a full install or I just use slackpkg with a local mirror for updates. From a working system to install a whole series I just mount the slackware disk and cd to the slackware directory and use something like
@damgar, my idea was to use pkgtool dialog for selecting which packages to install in /chroot without using upgradepkg or installpkg commands. Basically like the dialog when you're selecting which packages you want on a fresh install.
Disclaimer: I don't really know what I'm talking about.
Just a thought....
Is your intention to do this to a mounted partition with nothing on it yet? If so, I wonder if perhaps before you use pkgtool you need to use installpkg to install aaa_base. I believe aaa_base is what sets up the root directory tree, so it kind of stands to reason that if that is not installed, other things may have a hard time doing what they are supposed to.
you can try changing two lines of /sbin/pkgtool, like below
--- pkgtool.orig 2012-08-09 20:38:10.000000000 +0200
+++ pkgtool 2012-10-22 15:47:03.360638344 +0200
@@ -94,8 +94,8 @@
if [ ! -d $TMP ]; then
mkdir -p $TMP
this way it should honor the $ROOT environment variable (like installpkg already does) and you can use it to install in the chroot, exporting first ROOT=/chroot (no need for --target_dir, that seems used only in the O.S. install phase).
Maybe slackpkg is a better choice for this kind of tasks, it even supports templates: that's what I use to create my lxc containers.
I had to modify it just a little too to let it honor the $ROOT environment variable and to have the possibility of specifying an alternate configuration folder (in alternative to /etc/slackpkg) with a $CONF variable, to not being tied to the contents of that folder and choose to install, for example, 32bit packages in the container from a slackware64 host, use a custom blacklist and so on.
If you want to try it, it's here