installpkg errors
 

I've downloaded the install discs 3 different times and checked them from bittorrent buit when i go to install i get these installpkg errors:

installpkg error #1

there was a fatal error attempting to install
/var/log/mount/slackware/ap/bc-1.06-i386-2.tgz. The package may be corrupt, the installation media may be bad. or something else
has cause the package to be unable to be read without error. you
may hit enter to continue if you wish, but if this is an important
required package then your installation may not work as is.

i'm keeping a list of all the corrupt packages... i was hoping to find out if i could install these packages later somehow.. or after the install is complete can i just reinstall completely over it? and how can this be done... i am rather new to it all. is there somewhere else i should be downloading the iso's?

Did you check the md5sums? When this happened to me I realised my download or burn was less than perfect. Check the md5sum and try burning at 4x (assuming the checksum comes back ok).

im going to redownload and check them. when trying to install a second time i dont even get the same errors! is there some where else i should download them from? well here goes another try.

http://iso.linuxquestions.org/ for all your iso needs :)

are you using a somewhat " older " cd drive for this ? ( say 5 or 6 years ).
that drive might not be able to read self-made disks correct and that would explain why you
get different errors on a second try.

egag

I've ran into this several times... In my case it has nothing to do with a bad ISO/CD.... The / filesystem is either not supported by the kernel you chose to boot up with or you made a new filesystem thru cfdisk and it didn't get initialized properly (eg. didn't reboot when it said to).... Seriously... ;) I can reproduce the error consistently... Run cfdisk from the Slack disk and delete then make a new / partition. Assign it type '83' Then reboot back into the Slack disk and let Slack format it. If you mkreiserfs on your own (or whatever filesystem your using), make sure you reboot the computer after you do so. If your using an XFS filesystem, obviously, you need to choose xfs.s or whatever the Slack kernel is called for XFS...

I'm sure you get the jist of what I'm saying... Just keep playing with it. The install can be finiky in that regard.

i have brand new drives so i know that's not it.

i think you're right though jong... i followed this installation guide: http://www.bitbenderforums.com/vb22/...?postid=311808

using the ext2 filesystem, without journaling. i used the sata.i kernel to boot and i used fdisk to make my partitions.

what do you mean exactly by cfdisk from slackware, delete then make a new partition? just delete the entire primary partition and recreate all the ones the installation guide says to make (i.e. /use, /opt, and /home)

my partition table looks like this:

/dev/sda1 / ext2
/dev/sda5 /usr ext2
/dev/sda6 /opt ext2
/dev/sda7 /home ext2

yeah, after i posted i read your sig. :)

but i think it's strange you don't get the same errors every time.
are you using those rewritable cd's to burn the images to ?
( just a thought, they gave me some prob.'s in the past )

egag

not rewritables. but im trying again after repartitioning with fdisk all over again and mnting my partitions.. and im getting the same exact errors as the first time. im writing them down in hopes that i can just install this stuff later. the only important one i think is from the kernel source.. what a pain! i've had this happen before and gave up but not this time, not this computer! anyone have a suggestion for an iso burner other than iso recorder? (for my windows xp back up system to burn the cd for me)

The trial version of Nero is pretty good and does what you need it to do.

...and if you can't solve it, there's a simple workaround
because you were able to install all of the /a dir.
if you want to try it, i'll explain...

egag

please do! as long as i can "patch up" the rest of the install some later time i'll be happy!

well...if you have all of the /a dir. installed you have nearly a working system.
all it further needs is an "fstab" file ( it's created by the installer ) and a kernel + modules.
then install lilo.
( btw.: i guess you have a win. partition wich contains the iso's on that same pc )

if thats ok, then you should be able to reboot and get to the commandline of Slack.
then login as root and do the following:

-make a mountpoint for the windows partition
#mkdir /win
-if that win. partition is ntfs then
#modprobe ntfs

-mount the partition
#mount -t ntfs /dev/hdXX /win

( XX =fill in the part. name )
( if it's a fat part., then use "vfat" instead of "ntfs" )

-copy the images somewhere to your linux part.
#cp /win/path-to-iso/slackware-----.iso / ( root partition is ok )

-make a mountpoint for the image
#mkdir /slack1

cd to where the iso-images are
#cd /

-mount the image
#mount -o loop slackware----.iso /slack1

( you can repeat the last three steps for the other image with /slack2 as mountpoint )

then cd into the disk image..
#cd /slack1/slackware

inthere are the dir.'s /a /ap etc...
just cd to them ( skip /a , that one is installed ) and use installpkg

example:
#cd ap
#installpkg *.tgz

when you've installed all of the first cd, you can cd to the second
and install kde or gnome ( or both... )

i hope it's a bit clear.
just post any Q.'s

egag

oh no i dont have a windows partition at all.. i did... but i completely zero wrote the drive and im only installing slackware.

what may have confused you is that im burning the iso's on my back up computer which IS running windows xp. so basically what you're trying to get me to do is take the iso's off the cd and put them onto my SW box's hd and then install from there? or do i need to burn the iso to the cd first and then put it onto the hd and install from there?

yeah...i described how to use the iso images on the harddisk instead of the cd.'s
( by mounting them on a loop device )

but now one way is to use the cd.'s and mount the cd instead of the iso
cd to there and use installpkg.
but maybe you'll get the same errors on some packages.

...or you can get your hd out of the win. box and plug it into the linux pc,
and try as described above.
( incase you do that, mind the jumper setting for master/slave )

egag