The "disk images" it's referring to here are not the ISOs, but ratherQuote:> According to
> the RedHat docs, I should be able to do a hard drive install by putting the
> ISOs on the machine and pointing to it. Whenever I try this, it claims that
> the directory specified does not contain disk images.
Unsure. I tried burning some 7.2 ISOs a few weeks ago, and AFAIK theyQuote:> Additionally, I tried burning the images to CD, but it did not recognize the
> CDs and valid install media. I haven't changed my method for burning them
> over any of the other versions that I'd installed. Is there something
> unique about 7.2?
Providing online networks of Australian lawyers (http://www.ilaw.com.au)
and Linux experts (http://www.linuxconsultants.com.au) for instant help!
Disclaimer: http://www.terminus.net.au/disclaimer.html. GCS L+++ P++ t++
I tried both methods, pointing to the ISOs, and also pointing to an expandedQuote:> > According to
> > the RedHat docs, I should be able to do a hard drive install by putting
> > ISOs on the machine and pointing to it. Whenever I try this, it claims
> > the directory specified does not contain disk images.
> The "disk images" it's referring to here are not the ISOs, but rather
> the floppy images (boot.img, pcmcia.img, etc) in the images/ directory
> on the CD. If you simply copy the entire CD contents to a directory on
> the disk and point to the images/ subdirectory within that, it should
> work AFAIK.
I just tried to reburn the CDs, and this time it worked. Odd. I searchedQuote:> > Additionally, I tried burning the images to CD, but it did not recognize
> > CDs and valid install media. I haven't changed my method for burning
> > over any of the other versions that I'd installed. Is there something
> > unique about 7.2?
> Unsure. I tried burning some 7.2 ISOs a few weeks ago, and AFAIK they
> burned correctly, but the install process seemed to think the CD was
> invalid. On the other hand I burned another set to different CDs several
> weeks prior to that, and the install (well, upgrade) went fine. Weird...
mount -r -t iso9660 -o loop /path/to/ISO/blah.iso /mnt/ISO
When you change to the /mnt/ISO directory, you will see the contents of the
file as if it were a mounted CD. It's a great time saver if you don't feel
like writing the ISO to a CD.
Thanks for the reply,
Quote:> I seem to remember when I read that info that there was a utility
> you had to run to "mount" the image files as a volume.
i'm installing RH 7.2 to dual boot with Win98. I created a new
partition at cylinder 1012; my Win partition has about 7.9 gigs, my
linux partition about 5. yet when i get to disk druid or fdisk, i get
"The partition table on /tmp/hda is inconsistent [...] detected the
BIOS geometry incorrectly. However, this does not appear to be the
here[...]safe to ignore[...]may cause (fixable) problems with some
when using fdisk, the first thing it tells me is that my partition is
1664 cylinders. What? I installed RH 6 before (and have since deleted
it) and placed the partition in about the same location (just below
1024) and didn't have this problem. What's strange is that the
language of this message implies that it's the SIZE of the partition
that matters ("this partition is 1664 cylinders. there's nothing wrong
with that, but it's greater than 1024..."), instead of its starting
point, which I thought was critical for the boot partition. Either
way, neither the starting point nor the total size of this partition
are anywhere near 1664. Any suggestions?
you can reply by email at msb13 at duke dot edu.
thank you very much,
8. C shell