Archive:FedoraDocs/ReleaseNotes/Core4Test1/PackageSpecific/Miscellaneous

This section contains information related to packages that do not fit in any of the proceeding categories.

compat-db
C++ and TCL bindings are no longer contained in the  package. Applications requiring these bindings must be ported to the currently-shipping DB library.

nscd
The nscd name service cache daemon may now maintain a persistent cache across restarts or system reboots. Each database (user, group, and host, respectively) can be made selected to be persistent by setting the appropriate line in  to "yes". Entries are not removed from the cache until they are proven to be no longer of interest. All entries whose time-to-live expires but are otherwise interesting are automatically reloaded, which helps in situations where the directory and name services become temporarily unavailable.

The nscd name service daemon is also able to communicate faster with client programs. This feature must be enabled explicitly by setting the "shared" entry for the appropriate database in  to "yes".

udev
Fedora Core 4test1 has switched from a static  directory to one that is dynamically managed via. This allows device nodes to be created on demand as drivers are loaded.

For more information on udev, refer to the udev(8) man page and the following link:

http://people.redhat.com/~harald/udev.html

Additional rules for udev should be placed in a separate file in the  directory.

Additional permission rules for udev should be placed in a separate file in the  directory.

Systems upgraded to Fedora Core 4test1 using Anaconda will automatically be reconfigured to use udev. However (although NOT recommended) it is possible to perform a "live" upgrade to udev using the following steps:

1. Ensure that you are running a 2.6 kernel

2. Ensure that  is mounted

3. Install the  RPM supplied with Fedora Core 4test1

4. Install the new  RPM supplied with Fedora Core 4test1

5. Execute /sbin/start_udev

6. Install the new  RPM supplied with Fedora Core 4test1

7. Perform one of the following steps:


 * Install the new  RPM supplied with Fedora Core 4test1

OR:


 * Re-run mkinitrd for your existing kernel(s)

Warning

Improperly performing these steps can result in a system configuration that will not boot properly.