Mailinglist Archive: opensuse (2876 mails)
| < Previous | Next > |
Re: [opensuse] system does not boot
- From: Reinhard Gimbel <opensuse@xxxxxxxxxxxxx>
- Date: Mon, 28 May 2007 12:25:02 +0200
- Message-id: <465AADFE.30400@xxxxxxxxxxxxx>
Hello Amr, hello community !
Amr M. Salah wrote / schrieb:
> I’m a newbie with Linux systems , so I hope if any on can help me , I’m in a big trouble ☹
[...]
> My question is, can I do something to remove GBLIC 2.4 so I can every thing back (using the rescue system for example)
Actually you will need to replace GLIBC 2.4 by the original version (2.3).
Using the rescue system is one path to go.
The other one would be to try a repair installation out of the
installation system. But depending on which modification you did after
the inital installation that might bring other minor trouble.
So the path to go might be the rescue system.
Any idea of the layout of the partitions in use ?
--
Never give up !
Best regards / Gruß, Reinhard.
"Software is like a parachute. It doesn't work if it is not open."
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Amr M. Salah wrote / schrieb:
> I’m a newbie with Linux systems , so I hope if any on can help me , I’m in a big trouble ☹
[...]
> My question is, can I do something to remove GBLIC 2.4 so I can every thing back (using the rescue system for example)
Actually you will need to replace GLIBC 2.4 by the original version (2.3).
Using the rescue system is one path to go.
The other one would be to try a repair installation out of the
installation system. But depending on which modification you did after
the inital installation that might bring other minor trouble.
So the path to go might be the rescue system.
Any idea of the layout of the partitions in use ?
--
Never give up !
Best regards / Gruß, Reinhard.
"Software is like a parachute. It doesn't work if it is not open."
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |