Custom Query (1145 matches)

Reported by geofft, 15 years ago.

It's generally the case that on clusters, you need to open the full gnome-volume-control (or alsamixer) and figure out which channel is the built-in speaker and mute it, in addition to unmuting and bringing up the volume on the headphones. This is pretty undiscoverable, especially if your headphones are in and you don't notice that the built-in speaker is also making noise.

Is there a way around this? For instance, we could unmute headphones by default (and unmute PCM, and simply mute Master or Master Mono when reactivating).

Reported by geofft, 15 years ago.

As far as I can tell, debathena-dns-config sets up bind to start resolving from the global root servers, not whatever DNS servers are provided via DHCP. This makes you sad when you're on a network that depends on redirecting web requests via DNS to a registration page. (For instance, the Middle East's network, although free, requires you to click okay on a web page on every session.)

I haven't tested this with a MITnet-unregistered machine, but it seems like it would be a problem there, too, e.g., if you just installed debathena-workstation on a new machine from PXE.

There appears to be code in /etc/resolvconf/update.d/bind to configure bind's forwarders to be what the other resolvconf sources say your DNS servers should be, which would be a perfect fix. Is that not getting triggered for some reason?

Reported by geofft, 15 years ago.

On a couple of Debathena machines I use:

sipbadmin@tyger:~$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new

dr-wily:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/openafs/cacheinfo.debathena.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/openafs/cacheinfo.debathena.debathena-orig.dpkg-new
/etc/ssh/sshd_config.debathena.debathena-orig.dpkg-new
/etc/security/access.conf.debathena.dpkg-new

ozok-the-destroyer:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/ldap/ldap.conf.debathena-orig.dpkg-new
/etc/firefox-3.0/pref/ubufox.js.debathena-orig.dpkg-new
/etc/texmf/xdvi/XDvi.debathena-orig.dpkg-new
/etc/texmf/dvips/config/config.ps.debathena-orig.dpkg-new
/etc/texmf/dvipdfm/config/config.debathena-orig.dpkg-new
/etc/texmf/tex/generic/config/pdftexconfig.tex.debathena-orig.dpkg-new
/etc/lprng/lpd.conf.debathena-orig.dpkg-new
/etc/cups/cupsd.conf.debathena-orig.dpkg-new
/etc/fuse.conf.debathena-orig.dpkg-new
/etc/security/access.conf.debathena-orig.dpkg-new
/etc/pam.d/login.debathena-orig.dpkg-new
/etc/pam.d/gdm.debathena-orig.dpkg-new
/etc/pam.d/sshd.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/ssh/ssh_config.debathena-orig.dpkg-new
/etc/gdm/gdm.conf-custom.debathena-orig.dpkg-new
/etc/ntp.conf.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/krb.realms.debathena-orig.dpkg-new
/etc/csh.cshrc.debathena-orig.dpkg-new

kid-icarus:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/csh.cshrc.debathena-orig.dpkg-new
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/cups/cupsd.conf.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/ntp.conf.debathena-orig.dpkg-new
/etc/lprng/lpd.conf.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/apparmor.d/usr.sbin.cupsd.debathena-orig.dpkg-new

Zephyr discussion reminded me that this is due to  a bug in dpkg regarding diverted conffiles that's been fixed in dpkg 1.15. Jaunty and Lenny both still have 1.14, and we more or less still care about them, so we should consider adding code in auto-update to clean these up appropriately.