Peter,
thanks for the reply. It doesn't really help me solve the problem since I
don't have a copy of 7.2 left to copy the scripts over from but at least I
now know which directory to backup IF i can get this figured out. I may not
fix this problem but at least i have learned something from it. :)
What you mentioned though did bring up another rather drastic idea though
and I want to ask the list for opinions about it before I attempt it.
Should I be able to delete all the scripts in the
/etc/sysconfig/network-scripts directory via rpm -e something and then do an
rpm -i something to reinstall them? Reason I am saying this is drastic is
because I would also lose my eth0 scripts and there is no guarantee that
this would fix my problem. I am also not certain which packages to remove
and reinstall to make sure that i cover everything. Guidance would be
greatly appreciated!
The only other solution that i have at the moment is to format the harddrive
and reinstall which i really do NOT want to have to do.
Thanks again,
Ian K. Harrell
EMail: [EMAIL PROTECTED]
This sort of thing keeps happening to me with Linux-Mandrake 8.0 (reported
as
a bug). I have 7.2 on another partition and I copied
/etc/sysconfig/network-scripts from there to
/etc/sysconfig/network-scripts-from-7.2 on my 8.0 partition. Whenever I
have
a problem with /sbin/ifup ppp0, replacing the contents of
/etc/sysconfig/network-scripts with the 7.2 set _always_ fixes it. Please
don't ask me why - it's a crude and dirty kludge but I have spent hours and
hours trying to identify which file caused the problem (by comparing the
contents) to no avail.
If you don't have such a fallback, I suggest you make a backup of that
folder
as soon as you get it working.
--
Peter Ruskin, Wrexham, Wales.
Registered Linux User No. 219434 ( see http://counter.li.org/ )
Linux Mandrake release 8.0 (Traktopel) for i586
Linux 2.4.3-20mdk-win4lin-pnr, KDE: 2.1.2, Qt: 2.3.1
Uptime 15 hours 40 minutes
