On Sunday, June 17th, 2012, at 13:51:30h +0000, Chris Glurr explained:
> Let me try and help you then.
Thank you; it is greatly appreciated that you take the
time and trouble to do so. Most people just do not bother.
> If you read the OP S.L.O.W.L.Y you'll see that it refers to:
>
> <grub of FC1 installation> <--- FC1 ?!
> was able to boot Debian-lenny <--- Debian ?!
> to access Slackware13 <--- Slackware ?1
Yes that still conveys the same meaning as the original
no matter how S...L...O...W...L...Y I read it.
The problem is with the grub installation of Fedora Core 1
accessing the latest version of a Slackware installation.
The fact that it was able to access Debian-lenny is irrelevant.
The solution to your problem is very simple though --
update to the latest Fedora Core 17, or a still supported
version of Fedora Core viz FC15 or FC16.
And when you boot into Debian-lenny and mount the Slackware
created file systems, what filesystem type does Debian-lenny
claim that they are? Look at the output of the blkid command --
blkid /dev/sdLN
where L is the appropriate letter a,b,c,d etc and N
is the appropriate number 1,2,3 .. 15
Fedora Core 1 became obsolete very many years ago.
It was released on 2003-11-05 and support ended on 2004-09-20,
which is almost eight years ago.
If you wish to do forensics on an ancient FC1 installation
as to why an ancient version of grub 1 does not findthe file
systems of a recent version of Slackware, then may I humbly
suggest a more appropriate news group would be something like
alt.linux.archaelogy or alt.os.linux.ancient or alt.os.linux.unsupported
I suggest that you will find that you will get very few
responses to your question since most people reading the alt.os.linux
and Debian newsgroups are rather more occupied with trying to resolve
the bugs and problems of current GNU/Linux distributions.