November 2011 - luv-main

Re: [luv-main] Handling Ubuntu updates [Was: ubuntu hang after upgrade natty to oniric]
by Andrew 06 Nov '11

06 Nov '11

On 30/10/2011 6:29 PM, Erik Christiansen wrote: >> By the way, if you have numerous Debian machines needing package >> updates, you do _not_ have them all fetch those in parallel. What you >> do is have each host's apt subsystem use a shared local Squid cache you >> establish for that purpose. That way, duplicate downloads are >> eliminated automatically. > That does sound easier than doing an "apt-get --download-only", sharing > the archive via NFS (or sneakernet), and doing a "dpkg -i", but we often > just end up doing what we remember how to do. In a default configuration, Squid's ideas about what is fresh are less than ideal. There are a variety of apt specific caching programs out there, or you can give squid some rules to limit how long it will consider files to be fresh. There's two problem areas with squid. Firstly, resources can be cached for too long, so you miss critical updates. Secondly, the various files in your cache are frequently out of sync with each other. Andrew

1 0

[luv-main] Luv list and DKIM
by Jason White 03 Nov '11

03 Nov '11

Oct 9 12:29:12 jdc postfix/cleanup[3374]: 50CC118074A6F: milter-reject: END-OF-MESSAGE from lists2.luv.asn.au[202.158.218.239]: 5.7.1 rejected due to DKIM ADSP evaluation; from=<luv-main-bounces(a)lists.luv.asn.au> to=<jason(a)jasonjgw.net> proto=ESMTP helo=<tainted.luv.asn.au> Oct 11 10:23:02 jdc postfix/cleanup[19312]: 23E771805C2E5: milter-reject: END-OF-MESSAGE from lists2.luv.asn.au[202.158.218.239]: 5.7.1 rejected due to DKIM ADSP evaluation; from=<luv-talk-bounces(a)lists.luv.asn.au> to=<jason(a)jasonjgw.net> proto=ESMTP helo=<tainted.luv.asn.au> Oct 11 11:23:10 jdc postfix/cleanup[20280]: 49D9118046E51: milter-reject: END-OF-MESSAGE from lists2.luv.asn.au[202.158.218.239]: 5.7.1 rejected due to DKIM ADSP evaluation; from=<luv-talk-bounces(a)lists.luv.asn.au> to=<jason(a)jasonjgw.net> proto=ESMTP helo=<tainted.luv.asn.au> Oct 12 14:20:49 jdc postfix/cleanup[9322]: 96D1B180C50B5: milter-reject: END-OF-MESSAGE from lists2.luv.asn.au[202.158.218.239]: 5.7.1 rejected due to DKIM ADSP evaluation; from=<luv-talk-bounces(a)lists.luv.asn.au> to=<jason(a)jasonjgw.net> proto=ESMTP helo=<tainted.luv.asn.au> The only other error in the logs in these instances is "rejected per sender domain policy". I'm running OpenDKIM here and I haven't touched the configuration of OpenDKIM, Postfix, Bind (or anything else). The problem appears to be gone now anyway. It resulted in temporary suspension from luv-talk.

5 11

[luv-main] ABC RN: Future Tense: Communication, access and equality (Dili Village Telco & Serval)
by rdbrown＠pacific.net.au 03 Nov '11

03 Nov '11

http://www.abc.net.au/rn/futuretense/stories/2011/3353120.htm We look at a number of projects aiming to improve access to communication - be it the use of telephones in East Timor or Internet access in the remote interior of Australia. ... I don't think Linux was explicitly mentioned though

2 1

Re: [luv-main] [luv-announce] LUV-Main Meeting Reminder, LUV Shepparton
by Russell Coker 02 Nov '11

02 Nov '11

On Mon, 31 Oct 2011, lev(a)levlafayette.com wrote: > the event. With a good turnout, LUV now has its third chapter established > (Ballarat, Geelong, Shepparton) in addition to the Melbourne city group. It would be good to have monthly status updates on what the other chapers are doing. Also how are they going for talks? Presumably they find it more difficult to get speakers than we do. What size of audience do they get? I would consider travelling to those places to give a talk if the audience is big enough... -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

3 2

[luv-main] Sound Issue With Gigabyte Motherboard
by David Zuccaro 02 Nov '11

02 Nov '11

Hi, I've noticed that I get much higher volume sound output in MS windows than in Debian. Obviously I want better volume output. I've checked the volume control and PCM isn't turned down. Is there something else I could check to increase the volume output? This is the output of lspci if that's any help. dz2@Palatinus:~$ lspci 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 01:05.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) dz2@Palatinus:~$ uname -a Linux Palatinus 2.6.26-2-686 #1 SMP Wed Sep 21 04:35:47 UTC 2011 i686 GNU/Linux Thanks, David

2 2

[luv-main] Stumped - memory compatibility issue?
by Toby Corkindale 02 Nov '11

02 Nov '11

hey all, I have an issue with some memory that has me stumped. Due to an upgrade, I had 4x1GB sticks of RAM spare, so I figured I'd put these into another machine of mine that currently only has 1 GB total. (It's a little ITX board for media playback) However, after putting the new RAM in, the machine won't boot Ubuntu reliably, and memtest+ on the Ubuntu install disc shows up lots of memory errors. The memory was also *extremely* hot when I removed it from the machine. I tried the memory in pairs of two matched sticks at a time. Returning the memory to original machine, it runs memtest+ with no errors. Is there some kind of memory incompatibility that I'm unaware of going on here? The specs: Machine A, working combination: Motherboard: Intel P35 chipset RAM: 4x 1GB of DDR2-800 Machine B, working combination: Motherboard: Zotac nForce 630i RAM: 2x 512MB of DDR2-667 The latter motherboard says it supports DDR2-800 memory. I moved the CPU over from machine A to B, but that didn't help. I was especially bothered by the RAM getting very hot - I'm pretty sure that's not normal - although that machine is in a very small case without brilliant ventilation. But it was hot after just a few minutes of run time. I wondered if you had any thoughts? Thanks, Toby

7 7