Linux OS.: Technical questions Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Linux OS.: Technical questions

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Thomas A Watson who wrote (312)	6/17/2002 10:58:00 AM
From: Thomas A Watson	Read Replies (1) of 484

004 The live tale of a network install of RH 7.3 PART3 DAS_dumbis_redhatums. 4.1 Well this not live recount but a blow by blow of where I am now. 4.2 After returning from the Monroe Strawberry Festival( pbase.com ) I continued. I was still in the middle of an install and the installer indicated that a file was missing. I verified the file was located where it should be but the installer did not see it. It is not fully clear to what if anything the TRANS.TBL might have to do with the installing process. I now believe that it has nothing to do with it in a NFS install like I am doing. 4.3 But as I was not sure I decided that I would copy or cat/append the TRANS.TBL of disc2/RedHat/RPMS to the disc1/RedHat/RPMS. The TRANS.TBL is just a plane ascii file that I believe is a list of DOS names and the linux name of the files. I believe the DOS names are for use when you are in a fat file system. 4.4 Well when I looked at the disc2/RedHat/RPMS/TRANS.TBL I found that there seemed to be binary data at the end. This seemed strange. So I decided to do an md5sum again on the valhalla-i386-disc2.iso image. Well the md5sum was bad. I believe I had checked all the md5sums when I downloaded each image. Well I may have and the file may have been corrupted afterwards. 4.5 It's matters not why, I downloaded another valhalla-i386-disc2.iso image. I then mounted it. I copied the disc2/REDHAT/RPMS/openjade....rpm to ./DISK_1/RedHat/RPMS/ (see #reply-17610234 para 3.3 ) This worked and the installed continued. The install stoped again indicating a bad or missing file and I then copied all of the disc2 RPMS to the mounted point of the DISK_1 RPMS. 4.6 The install continued for several hundred more packages and around package, hmmmm 700 something out of 800 something I got a message the rpm licq-qt-1.1.0-0.cvs20020416.1.i386.rpm was missing. I found that there was no licq-qt...rpm there was a licq....rpm that seemed to match all the letters so I did a cp -a ./disc2/RedHat/RPMS/licq-1* ./DISK_1/RedHat/RPMS/licq-qt-1.1.0-0.cvs20020416.1.i386.rpm 4.7 Well when I clicked to continue the install it indicated it was aborting a the file was bogus. 4.8 So now I guess I will check all the downloads again, rebuild my DISK_1 images from the iso images and try again. 4.9 But I have leaned how the installer mounts file systems and how they are called. During the install (#reply-17610234 paragraph 3.7) By using <ctrl+alt> <F2> get a terminal and doing a df I got a listing of all the mounted file systems. The source of the install is mounted on /mnt/sourceimg The failures I am working around are teaching me more about how they do it. Well this is good but I'd really perfer not to have to learn... argghhh. time to post.. tom watson tosiwmee

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next