On Thu, Mar 18, 1999 at 01:44:47PM -0800, Tony Schlemmer wrote:
>
> Cons:
>
> Any custom stuff I had linked against libc5 no longer worked. I had to
> recompile all of my custom stuff to use libc6 instead. All went smooth
> here as I simply recompiled and reinstalled all of my custom stuff.
> (Note that I did expect this to happen since I knew SuSE 6.0 was based
> on glibc. This may be a con for some people that are unaware of this
> change).
>
> IP_FORWARD is set to "no" in the /etc/rc.config file and so this broke
> IP Masquerading on my server.
>
> It seems like the gcc packages were broken up or something as I
> discovered that "gcc" no longer existed on my system after the upgrade.
> I had to install a "gccfront" package to get "gcc" back on my systems so
> I could do kernal compiles.
>
You didn't have to recompile. You could have simply installed the shlibs5
package and had the best of both worlds. It's a compatibility thaaang
The IP_FORWARD item was explained. It's a security thaaang.
Yup. gccfront, just like the book/list/suse community says. It's a
flexibility thaaang.
Other than those expected scenarios (which means nothing's broken), how'd
ti go?
--
Brad Shelton [EMAIL PROTECTED]
On Line Exchange http://ole.net
Detroit News http://detnews.com
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
