On Thu, 24 Feb 2000 12:18:33 +0000, [EMAIL PROTECTED] wrote:
> Willi Geffers wrote:
> >
> > Hi!
> >
> > I've installed the GNUstep core system (version 0.6.5) on a Intel P-II
> > running SuSE Linux 6.2 with egcs 2.91.66 as well as gcc 2.95.1. I'd no
> > problems to configure, install and setup GNUstep according to the
> > information in GNUstep-howto. I did it as root, so /etc/services has
> > been edited automatically and gdomap (owned by root) has the suid flag
> > set.
> >
> > But when I start an application it does not find a GDNC server, no matter
> > whether GDNC is already running or implicitly started by the application.
> > Afterwards (one more) GDNC is running.
> >
> > Did I miss to configure something or do I have to install some patches?
> >
> > Thanx and best regards
> > Willi
> >
> > --
> > RWTH Aachen <mailto:[EMAIL PROTECTED]
> > Lehrstuhl fuer Prozesstechnik <http://www.lfpt.rwth-aachen.de/~wge
> > Turmstrasse 46 Phone: +49 241 80 7716
> > 52064 Aachen, Germany FAX: +49 241 8888 326
>
> It sounds like you hit upon the same problem I had, which Richard F-M
> helped me to track down. It seems that there is a problem with the
> default kernel build distributed with Suse 6.2 which means that the
> socket binding used by gdnc doesn't work.
>
> If you recompile the kernel then it starts working! I'm not sure if
> there's a particular build option that triggers it, but I do know that
> the original kernel failed every time on a diverse set of hardware,
> while a recompiled kernel worked every time.
>
> I did report it to Suse, but I've heard nothing back from them about it.
Thanks - I'd forgotten about that kernel bug. I guess I had assumed that you
were working with a custom built kernel version - I didn't realise that a
major GNU/Linux distribution had been released with such a severe bug in it.
