On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > On Friday 05 July 2019 08:41:47 Greg Wooledge wrote: > > On Fri, Jul 05, 2019 at 06:35:53AM -0400, Gene Heskett wrote: > > > yup, and if the repos were open... They are not as I've previously > > > posted. I can report that apt --purge does not, I still see > > > an /etc/nsswitch.conf, even though ts been purged. > > > > ... what. > > > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. It's part > > of the core installation. It is absolutely fundamental to the > > operation of basically every single piece of the operating system > > above the boot loader, the kernel, the ld.so shared library loader, > > and libc. > > IOW, the image I have in my pocket probably don't work until I locate a > copy and put it back in. But just for grins, check the buster its > running: yes, its still there and I think intact: > gene@shop:~$ cat /etc/nsswitch.conf > # /etc/nsswitch.conf > # > # Example configuration of GNU Name Service Switch functionality. > # If you have the `glibc-doc-reference' and `info' packages installed, > try: > # `info libc "Name Service Switch"' for information about this file. > > passwd: compat > group: compat > shadow: compat > > hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 > networks: files > > protocols: db files > services: db files > ethers: db files > rpc: db files > > netgroup: nis > > But that begs another question Greg. If it hasn't anything to do with > avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch > package with it? > > > If you remove /etc/nsswitch.conf, you won't be able to look up user > > names, or service port names, or host names, or basically *any* kind > > of names of anything at all. (Or, at best, you'll get some sort of > > default behavior compiled into the C library routines, if any.) > > > > wooledg:~$ dpkg -S /etc/nsswitch.conf > > dpkg-query: no path found matching pattern /etc/nsswitch.conf > > > > Since nsswitch.conf isn't part of a package, there is absolutely no > > reason you should think that purging ANY package would remove it. And > > there is absolutely no reason you should *want* to remove it. > > The only reason I removed it, was to complete the libnsswitch removal > that removing avahi-daemon took out. Somehow I am missing an actual > dependency of one on the other. Call me puzzled.
I'm puzzled too. Can you tell us which package you're talking about as I can only find: Package lib32nss-mdns Package libnss3 Package libnss3-1d Package libnss3-dbg Package libnss3-dbgsym Package libnss3-dev Package libnss3-tools Package libnss3-tools-dbgsym Package libnss-cache Package libnss-cache-dbgsym Package libnss-db Package libnss-db-dbgsym Package libnss-dns-udeb Package libnss-docker Package libnss-docker-dbgsym Package libnss-extrausers Package libnss-extrausers-dbgsym Package libnss-files-udeb Package libnss-gw-name Package libnss-gw-name-dbgsym Package libnss-ldap Package libnss-ldapd Package libnss-ldap-dbgsym Package libnss-ldapd-dbgsym Package libnss-libvirt Package libnss-libvirt-dbgsym Package libnss-lwres Package libnss-lwres-dbgsym Package libnss-mdns Package libnss-mdns-dbgsym Package libnss-mdns-i386 Package libnss-myhostname Package libnss-myhostname-dbgsym Package libnss-mymachines Package libnss-mymachines-dbgsym Package libnss-mysql-bg Package libnss-pgsql2 Package libnss-pgsql2-dbgsym Package libnss-rainbow2 Package libnss-rainbow2-dbgsym Package libnss-resolve Package libnss-resolve-dbgsym Package libnss-securepass Package libnss-securepass-dbgsym Package libnss-sss Package libnss-sss-dbgsym Package libnss-systemd Package libnss-systemd-dbgsym Package libnss-unknown Package libnss-unknown-dbgsym Package libnss-winbind Package libnss-winbind-dbgsym Package libnss-wrapper Package libnss-wrapper-dbgsym Package libpam-ccreds Package libpam-ldap Package nslcd Package nsscache Package nss-passwords Package nss-updatedb Package pynslcd Package winbind Cheers, David.