bind9 in unstable
All: On Friday, give or take, an updated bind9 package was installed on my DNS server / firewall, which is a Sun Ultra 10 running unstable. The version is: Preparing to replace bind9 1:9.4.2-10 (using .../bind9_1%3a9.5.0.dfsg-1_sparc.deb) ... Unpacking replacement bind9 ... After installation, the daemon tries to start, but prints out: Starting domain name service...: bindnamed: syscall(capset) failed: Invalid argument: please ensure that the capset kernel module is loaded. see insmod(8) There doesn't appear to be a "capset" module. I found a comment from my searching about a "capability" module, but that module does not appear to be available. As part of the installation, a new copy of /etc/apparmor.d/usr.sbin.named was installed. I don't know what, if anything, that has to do with it, although, I see several lines with "capability" in them. Commenting those lines has made no difference. I've been unable to figure out the version string to revert to version 9.4.2-10 to get the previous behavior, although, I'm not sure that was the previous version. Can someone advise about: 1) Is this behavior as expected from the new bind9 on sparc? 2) How do I get the previous behavior back? I've been unable to get the previous version of the package installed. For immediate relief, I'm going back to try djbdns Well, no relief found. I find no coherent instructions for setting up djbdns that seems to work. The dnsqr query always fails with "connection refused". Any help greatly appreciated. Thanks in advance. Cheers, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
enable second interface on hme (netra t1)
Hello everyone. I've been running debian sparc on my netra t1 for so many years I'd practically forgotten all about it. A couple nights ago, we had a very near lightning strike (though not a direct hit). It was quite something, as the charge in the clouds overhead would build up, it would set off one or two of the smoke alarms, then when the lightning discharged, they went off. It was eerie. In any case, this has apparently permanently horked eth0 on my HME card. eth1 still shows link when I plug in an ethernet cable, so I sez "no problem, I'll bring up eth1 and keep rolling" cept I'm really a novice here. ifconfig does not see more than one interface on the HME. I tried playing dumb and just changing "eth0" to "eth1" in /etc/network/interfaces ... this, of course did nothing. Googling for "debian sparc hme configuration" unsurprisingly yeilds pages and pages of mailing list entries about the net-install cd. I would imagine, that I need to configure something with the kernel module for HME? I've tried putting the net-install cd back in the drive and booting in rescue mode, however in both r'escue' mode and 'expert' mode the "network configuration" section does not allow me to select a network interface, just to try dhcp or manually configure the "primary" network interface, meaning my horked eth0. Can anyone help me here? How do I manually bring up eth1? The OS has never thought eth1 existed, though it never bothered me 'till now. I have a strong gut feeling that eth1 would still work if I could find a way to enable it on the OS. thanks in advance for your help everyone, -Andy
Re: Bug#485961: installation-reports: Installer can't locate CD-ROM drive (sparc)
> Hmm. There is also a sun_esp module, which depends on esp_scsi. I wonder > if that's the missing link here. > I've attached that module. It should be compatible with the current > 2.6.24-1 kernel used in the installer. Can you try copying that in place > (/lib/modules/2.6.24-1-sparc64/kernel/drivers/scsi/), run 'depmod -a' > and try to modprobe it? > If you select (in expert mode) openssh-client-udeb as additional > installer component to install, you can just scp the module from another > machine. I'll try this and see what happens. The catch would appear to be that installer components live on the (as yet undetected) CD, so can't be loaded to fetch the module. I've built a modified netinst CD with the module added, which I will try tomorrow when I'm in the same room with the e3500. Maybe I even built it correctly. :) De -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
