On Sun, 7 Feb 1999, Karl F. Larsen wrote:
> } Karl. It would help if you read and tried to understand the messages
> } posted here. As already said here your problem is most probably lack of
> } support for Unix domain sockets.
> }
> What is a Unix domain socket?
It would be helpful if you would read the documents too, especially if
you plan on trying to help someone else. Starting with the Changes
document, and while configuring the kernel, the help items in the
configuration.
If you would have taken time to press 'H' before DISABLING the support
for "Unix domain sockets" in the Networking section (it is ENABLED by
default because most users need it), you would have seen the following
description (pay attention to the last paragraph - it appears in many of
the help texts):
CONFIG_UNIX:
This includes Unix domain sockets, the standard Unix mechanism for
establishing and accessing network connections. Many commonly used
programs such as the X Window system and syslog use these sockets
even if your machine is not connected to any network. Unless you are
working on an embedded system or something similar, you therefore
definitely want to say Y here.
The socket support is also available as a module ( = code which can
be inserted in and removed from the running kernel whenever you
want). The module will be called unix.o. If you want to compile it
as a module, say M here and read Documentation/modules.txt. If you
try building this as a module and you have said Y to "Kernel module
loader support" above, be sure to add 'alias net-pf-1 unix' to your
/etc/conf.modules file.
If unsure, say Y.
(If you'd read some more of the help texts, you'd also learn that the
NLS character set support in the kernel has absolutely nothing to do with
character set conversion in packet terminal programs.)
- Hessu (also using 2.2.1 on RH5.2 with X and AX.25 with 0 problems left)
