Hey everyone, I'm running Slackware 14.0 and I'm trying to set up a console login for my Arch chroot. My intention is to have a "clean" login environment for the chroot. If I run chroot normally while logged in as root...
# chroot /mnt/chroot/arch /bin/bash
... it copies over my environment variables from Slackware's root login. Arch uses some different environment variables than Slackware, which is why it's very important that I don't pass any through the host environment to the chroot, and instead login in a way that will run the chroot's own /etc/profile and so forth. This would additionally give non-root users a way to login to Arch without needing to have root privileges to chroot first.
Here's where I'm stuck:
After installing Arch in a chroot and making sure to bind-mount all the necessary directories, I took a hint from this guide
(as well as some other guides I found related to creating Gentoo chroots in Slackware that suggested the same thing), and added the following to my /etc/inittab:
c7:12345:respawn:/usr/bin/chroot /mnt/chroot/arch /sbin/agetty 38400 tty8 linux
I ran 'init q', hit Ctrl+F8 and sure enough there was a fresh new console login with "Arch Linux" instead of the usual "Welcome to Linux" at the top. However, when I tried logging in, I just got hit with "Login incorrect" every single time.
I was trying to login as root and I know I got my password right, after typing it several times, very slowly and deliberately, looking at the keys and everything to be sure. I even ran passwd in the chroot, set the password again, and tried again in the console login. Login incorrect. I can still login on my Slackware tty's, but this new one just doesn't seem to be taking correctly.
Do I not have the inittab configured correctly? Is there something else I need to do? I realize that guide I'm referencing is from back in 2007, so I don't know how much may have changed since then.
I'd really like to be able to benefit from Arch's selection of packages, while still having peace of mind knowing it's safely cradled under a stable Slackware installation in case anything goes horribly wrong. Any help and advice is appreciated. Oh, and before anyone suggests virtualization as an alternative, that just isn't an option -- my computer is simply too old to do that efficiently.