[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: NetworkManager ( & bind)



Will Backman wrote:

Any idea why NetworkManager requires bind?

It uses bind in a caching-nameserver functionality and named should _not_ be turned on my default in this configuration. Use of bind as a caching nameserver was done to work around deficiencies of nscd and glibc and should allow user applications to be aware of changes to /etc/resolv.conf faster, since the applications actually just talk to 127.0.0.1 for the nameserver, and its the caching-nameserver that actually does the heavy lifting when /etc/resolv.conf changes since glibc isn't up to the task.

Dan



So my FC3 machine tells me that there is an unresolvable chain of
dependencies and doesn't install the updates.

I have a standard workstation install.

Actually, my FC3 machine does install the updates, and installs bind /and/ the caching-nameserver to resolve the dependencies.


Here is my up2date sources file:

---BEGIN FILE---
### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.


### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.

### The default RHN (using "default" as the url means use the one in the
### up2date config file).
#up2date default

### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.

### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type  channel-label      service:server         path        repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel

### Note: for apt repos, there can be multiple repo names specified (space
### seperated).

### A yum style repo. The format is:
### type  channel-label     url

### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/

# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.

#
# base
# Fedora Core 3 - i386 - Base
#
apt base http://ayo.freshrpms.net fedora/linux/3/i386 core

#
# updates-released
# Fedora Core 3 - i386 - Released Updates
#
apt updates-released http://ayo.freshrpms.net fedora/linux/3/i386 updates

#
# updates-testing
# Fedora Core 3 - i386 - Unreleased Updates
#
# apt updates-testing http://ayo.freshrpms.net fedora/linux/3/i386 tupdates

#
# fedoralegacyupdates
# Fedora Core 3 - i386 - Released Updates by FedoraLegacy
#
# apt fedoralegacyupdates http://download.fedoralegacy.org/apt fedora/3/i386 updates


#
# atrpms
# Fedora Core 3 - i386 - ATrpms
# alternatives to stable: testing and bleeding
#
apt atrpms http://apt.atrpms.net fedora/3/en/i386 at-stable

yum fedora-core-3 http://download.fedora.redhat.com/pub/fedora/linux/core/3/$ARCH/os/
yum updates-released-fc3 http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/$ARCH/


yum-mirror fedora-core-3 http://fedora.redhat.com/download/up2date-mirrors/fedora-core-3
yum-mirror updates-released-fc3 http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc3


yum dag http://apt.sw.be/fedora/3/en/$ARCH/dag
---END OF FILE---

As you can see, I use freshrpms, at-stable, and dag, in addition to the traditional fedora-core-3 and updates-released-fc3 repositories. (I edited my up2date file to skip the "libhowl" packages from at-stable; they force too many removals.)

Temlakos


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]