John Aldrich wrote:
> On Fri, 14 Apr 2000, you wrote:
> >
> > I don't think we're using the same hd.img file, because the only hdd
> > partitions available with the hd.img I'm using are those on hda. This might
> > only be a discrepancy created by the people at Planete Linux mag., because the
> > cdrom I have was obtained with their mag, in a cellophane enclosed package
> > (not from a Mandrake boxed set); and, if not by them, then by who ever created
> > the cdrom for them.
> >
> Mike:
> You might wanna just break down and get a "Cheapbytes" CD
> of Mandrake. It almost costs more to SHIP the blasted thing
> than it does for the CD itself! :-)
> Joh
Extremely tight budget at the moment and for a while to come, otherwise, I'ld just
go to a local store and purchase the package. I merely purchased the mag to get
the cdrom, to take a look at Mdk (still want to upgrade my RH config, at least to
explore or investigate it), but tight budget and have RH 5.1,upgraded to 5.2.
Now, I'm working on the upgrade to 6.0, after which 6.1 and possibly 6.2 shouldn't
take long to do. Currently blocked at start of 6.0, though, because of some
incompatibilities related to libc.so.6(GLIBC_2.0 and GLIBC_2.1),
libstdc++-libc6.1-1.so.2, and it doesn't look like I'll have an answer quickly.
RedHat doesn't have mailing lists like this. They have a bug reporting tool, but
this isn't a bug.
I've been hoping for someone to know how to get around this hd.img problem not
being able to see the second hdd. I don't want to switch the drives around, to
avoid hassles that'll cause, but if I want to check out this version of Mandrake,
then it's looking like this is what I'll need to do. I also don't have a backup
system; therefore, turf's a little trickier.
On the other hand, the maker of that cdrom (it's not from Mandrake from what I can
tell, because it's labeled "Planete Linux, CD1, Avril 2000, No 6") could modify the
hd.img file to allow access of the second hdd, send an email message saying where
to download the hd.img file, and then I'ld grab it there. I don't need another
cdrom; even if one way to resolve the problem, it's not necessary. All I need is
an hd.img which will allow using the second hdd.
This didn't strike me as a major item, if the maker could just make a corrected
hd.img available for download.
I don't know what goes into creating the hd.img file and don't have the sources for
it, as far as I know.
I looked at the lilo man pages, hoping to find something that'ld explain "oh ya,
got a work around for ya, ...", but didn't find anything in the documentation
related to such a work around. I was hoping someone here would know if this could
be done by simply configuring a lilo for the boot floppy, to allow visibility of
the second hdd for the installation program to see and provide access to.
On the other hand, even if this could be done or attempted with lilo, perhaps the
installation program portion on the boot floppy is hardcoded to only use hda.
Shouldn't be, but could be. Based on that, I don't see how lilo could help with
this problem.
Anyway, the distribution is a single cdrom, doesn't look like it was created by
Mandrake, and this stupid hd.img problem is a pain in the backside. And, I have no
idea why someone would want to create a hd.img which refuses to see other local
HDDs; unless an hd.img can't be made to allow use of more than one hdd.
Input on these types of topics might be helpful here. Even if it doesn't help
resolve my particular hd.img problem, the knowledge would be interesting.
mike
