ISO Loopback install with Slackware 10.1?
 

I have two harddrives, one has Debian (the one I'm running right now; hda1) and the other has a blank partition of 10GB (the one I want to install Slackware on; hdb1). I have both Slackware install disks and I mounted those disks on:
/cdrom (disk 1)
/cdrom2 (disk 2)
Using a loopback.

I have hdb1 (where I'm going to install slackware) mounted on:
/mnt/slackware

I've tried to install by running all of the install-packages shell scripts on disk 1 and disk 2, while having this global variable:
$ROOT = /mnt/slackware
But nothing seemed to be on hdb1 (mnt/slackware) after all of the installations. I know hdb1 is writable because I can copy and paste files in there. Does anyone have any ideas on how to install slackware on this hdb1 the quickest/easiest way with Slackware 10.1?

Thank you for your time!

I'm not sure if the floppy boot kernel supports loopback, but basically, the only way to run the setup in your situation that I *know* works would be to create the boot floppy, boot from it, mount the slackware CD's/install files, and choose to install from a previously mounted directory.

Or, you know, you could actually burn the CD's. Use CDRW's if you don't want to waste a disc.

Alright I just created a kernel boot disk, and I'm going to try it out! Wish me luck :D

You could just copy the kernels/bare.i/bzImage and isolinux/initrd.img to the harddrive or wherever (CD, network) ... then boot the kernel and slack image with grub. Hit c for command line at a grub interface and then boot that baby up using /dev/ram as the root device.

:scratch: AAAHH!!! Well I'm going to forget Slackware for a few days and then try again. I'm working with kernel upgrades right now for Debian, I was working with Slackware but I moved that to priority 2. I have this page on Bookmarks so I'll update this post a little later as far as troubleshooting. Though I want to say that I've never used grub before, and I've never used /dev/ram. I probably should update /etc/fstab to automount /dev/hdb1 on bootup to start up those image/kernel files.....