Datasheet
“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 170 — #196
i
i
i
i
i
i
i
i
Notes regarding the kernel and linuxthreads with floating stacks: Appli-
cations using errno, h_errno, and _res must include the header files
(errno.h, netdb.h, and resolv.h) with #include. For C++ programs
with multithread support that use thread cancellation, the environment vari-
able LD_ASSUME_KERNEL=2.4.1 must be used to prompt the use of the
linuxthreads library.
Adaptions for Native POSIX Thread Library
NPTL (Native POSIX Thread Library) is included as the thread package. NPTL
is binary-compatible with the older linuxthreads library. However, areas
in which linuxthreads violates the POSIX standard require NPTL adap-
tions. This includes the following: signal handling, getpid returns the
same value in all threads, and thread handlers registered with pthread_-
atfork do not work if vfork is used.
Network Interface Configuration
The configuration of the network interface has changed. Formerly, the
hardware was initialized following the configuration of a nonexistent in-
terface. Now, the system searches for new hardware and initializes it imme-
diately, enabling the configuration of the new network interface.
New names have been introduced for the configuration files. As the name
of a network interface is generated dynamically and the use of hotplug
devices is increasing steadily, a name like ethhXi is no longer suitable for
configuration purposes. For this reason, unique designations, like the MAC
address or the PCI slot, are now used for naming interface configurations.
Of course, you can use interface names as soon as they appear. Commands
like ifup eth0 or ifdown eth0 are still possible.
The device configurations are located in /etc/sysconfig/hardware.
The interfaces provided by these devices are usually located in /etc/
sysconfig/network (with different names). See the detailed description
in /usr/share/doc/packages/sysconfig/README.
Top-Level Domain .local as link-local Domain
The resolver library treats the top-level domain .local as “link-local”
domain and sends multicast DNS queries to the multicast address
224.0.0.251, port 5353, instead of normal DNS queries. This is an in-
compatible change. If the domain .local is already used in the name
server configuration, use a different domain name. For more information
about multicast DNS, see http://www.multicastdns.org.
170 5.2. Software Changes from Version to Version