From tilleja at gmail.com Mon Oct 20 11:08:17 2014 From: tilleja at gmail.com (Jose Castilleja) Date: Mon, 20 Oct 2014 11:08:17 -0600 Subject: [lug] For Sale: Intel Core i7 processor Message-ID: All, apologies in advance for submitting this here. A young man, high school student, who is very smart, and loves the IT/software world wants to sell this processor. It was the wrong processor. He is kicking himself for not paying closer attention. It's the Intel i7-3770 LGA1155 Anyway, the young man paid $300.00 and is asking $275.00 for this processor. Serious inquiries can contact me directly at tilleja at gmail dot com Thanks. -- Jose -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.haemer at gmail.com Wed Oct 22 05:35:06 2014 From: jeffrey.haemer at gmail.com (Jeffrey S. Haemer) Date: Wed, 22 Oct 2014 05:35:06 -0600 Subject: [lug] Opportunity knocks Message-ID: Ladies and Gentlemen, Kevin Fenzi tells me that the BLUG Web page and mailing list are hosted on a box at Tummy.com (thanks, Tummy!) that's soon to be retired. They just need to be moved to a new box. He could do it himself, in his sleep, but he wouldn't learn anything. If you would, it's an opportunity. If you'd like to learn how to do this, email Kevin. (His address is in the Cc list.) -- Jeffrey Haemer 720-837-8908 [cell], http://seejeffrun.blogspot.com [blog], http://www.youtube.com/user/goyishekop [vlog] *????????? ??? ??? ????? ????? ??????. * -------------- next part -------------- An HTML attachment was scrubbed... URL: From alanr at unix.sh Thu Oct 23 07:22:06 2014 From: alanr at unix.sh (Alan Robertson) Date: Thu, 23 Oct 2014 07:22:06 -0600 Subject: [lug] Buffer Bloat article Message-ID: <544900FE.7060907@unix.sh> When I presented at BLUG earlier in the month, there was a small discussion about buffer bloat, and I couldn't remember all the details. You can read more about it here: http://lwn.net/Articles/616241/ -- Alan Robertson alanr at unix.sh From robert.racansky at gmail.com Thu Oct 23 08:35:16 2014 From: robert.racansky at gmail.com (Robert Racansky) Date: Thu, 23 Oct 2014 08:35:16 -0600 Subject: [lug] Opportunity knocks In-Reply-To: References: Message-ID: On Wed, Oct 22, 2014 at 5:35 AM, Jeffrey S. Haemer wrote: > Ladies and Gentlemen, > > Kevin Fenzi tells me that the BLUG Web page and mailing list are hosted on a > box at Tummy.com (thanks, Tummy!) that's soon to be retired. They just need > to be moved to a new box. > > He could do it himself, in his sleep, but he wouldn't learn anything. If you > would, it's an opportunity. > > If you'd like to learn how to do this, email Kevin. (His address is in the > Cc list.) > When and where is he planning to do this? From jeffrey.haemer at gmail.com Thu Oct 23 08:53:16 2014 From: jeffrey.haemer at gmail.com (Jeffrey S. Haemer) Date: Thu, 23 Oct 2014 08:53:16 -0600 Subject: [lug] Opportunity knocks In-Reply-To: References: Message-ID: On Thu, Oct 23, 2014 at 8:35 AM, Robert Racansky wrote: > On Wed, Oct 22, 2014 at 5:35 AM, Jeffrey S. Haemer > wrote: > > Ladies and Gentlemen, > > > > Kevin Fenzi tells me that the BLUG Web page and mailing list are hosted > on a > > box at Tummy.com (thanks, Tummy!) that's soon to be retired. They just > need > > to be moved to a new box. > > > > He could do it himself, in his sleep, but he wouldn't learn anything. If > you > > would, it's an opportunity. > > > > If you'd like to learn how to do this, email Kevin. (His address is in > the > > Cc list.) > > > > > When and where is he planning to do this? > If you'd like to learn how to do this, email Kevin. (His address is in the > Cc list.) -- Jeffrey Haemer 720-837-8908 [cell], http://seejeffrun.blogspot.com [blog], http://www.youtube.com/user/goyishekop [vlog] *????????? ??? ??? ????? ????? ??????.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjhammel at graphics-muse.org Fri Oct 24 11:58:42 2014 From: mjhammel at graphics-muse.org (Michael J. Hammel) Date: Fri, 24 Oct 2014 11:58:42 -0600 Subject: [lug] need routing help with kvm Message-ID: <1414173522.23529.19.camel@feynman.cei.com> I'm trying to setup routing for a vm on a host that is on a subnet that is on our corp net. I want the VM to be able to reach the corp net. The VM is a KVM guest running CentOS. The VM host is also running CentOS. The default NAT on the vm (via virt-manager) sets up the VMs subnet as 192.168.122.x. This VM guest is 192.168.122.26. The vm host is 192.168.2.129 and 192.168.122.1. The .2 gateway to the .1 network is 192.168.2.65. A host on the corp net is 192.168.1.63. The VM can ping .122 hosts (including the vm host). It can also ping anything on the .2 network (of which the vm host is a member). It cannot reach anything on the .1 network (or anything in the outside world, which is on the other side of the .1 network, but I just need access to .1 for now). The VM host can access the VM guests, the .2 network and hosts on .1. The VM guest's route table is: 192.168.122.0 * 255.255.255.0 U 1 0 0 eth1 default 192.168.122.1 0.0.0.0 UG 0 0 0 eth1 The VM host routes are: 192.168.100.0 * 255.255.255.0 U 0 0 0 virbr2 192.168.2.0 * 255.255.255.0 U 0 0 0 br0 192.168.109.0 * 255.255.255.0 U 0 0 0 virbr1 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 link-local * 255.255.0.0 U 1003 0 0 br0 default 169.254.0.0 0.0.0.0 UG 0 0 0 br0 default 192.168.2.65 0.0.0.0 UG 0 0 0 br0 br0 is a bridge to the physical interface on the vm host. virbr? are bridges created via the virt-manager interface. I've tried all kinds of route changes to the VM and the vm host. It seems the vm host will not route through the 2.65 gateway for the VM guest. I'm not certain at this point if the routing is a problem with the route tables in the VM guest and/or VM host or a configuration problem with libvirt's network configuration for default.xml. I've tried creating new networks via virt-manager but that didn't do much different than what was in default.xml. Any pointers? -- Michael J. Hammel Principal Software Engineer mjhammel at graphics-muse.org http://graphics-muse.org ------------------------------------------------------------------------------ Everything should be made as simple as possible. But not simpler. -- Albert Einstein. From jph at jph.net Fri Oct 24 22:56:11 2014 From: jph at jph.net (John Hernandez) Date: Fri, 24 Oct 2014 22:56:11 -0600 Subject: [lug] need routing help with kvm In-Reply-To: <1414173522.23529.19.camel@feynman.cei.com> References: <1414173522.23529.19.camel@feynman.cei.com> Message-ID: Maybe the packet is making it to corp host, but corp host has no route back to your VM because the echo request has a .122.x source address (NAT fubar'd?) Easy way to figure this out would be to get a pcap (wireshark) on corp host. On Fri, Oct 24, 2014 at 11:58 AM, Michael J. Hammel wrote: > I'm trying to setup routing for a vm on a host that is on a subnet that > is on our corp net. I want the VM to be able to reach the corp net. > The VM is a KVM guest running CentOS. The VM host is also running > CentOS. > > The default NAT on the vm (via virt-manager) sets up the VMs subnet as > 192.168.122.x. This VM guest is 192.168.122.26. The vm host is > 192.168.2.129 and 192.168.122.1. The .2 gateway to the .1 network is > 192.168.2.65. A host on the corp net is 192.168.1.63. > > The VM can ping .122 hosts (including the vm host). It can also ping > anything on the .2 network (of which the vm host is a member). It > cannot reach anything on the .1 network (or anything in the outside > world, which is on the other side of the .1 network, but I just need > access to .1 for now). > > The VM host can access the VM guests, the .2 network and hosts on .1. > > The VM guest's route table is: > 192.168.122.0 * 255.255.255.0 U 1 0 0 eth1 > default 192.168.122.1 0.0.0.0 UG 0 0 0 eth1 > > The VM host routes are: > 192.168.100.0 * 255.255.255.0 U 0 0 0 virbr2 > 192.168.2.0 * 255.255.255.0 U 0 0 0 br0 > 192.168.109.0 * 255.255.255.0 U 0 0 0 virbr1 > 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 > link-local * 255.255.0.0 U 1003 0 0 br0 > default 169.254.0.0 0.0.0.0 UG 0 0 0 br0 > default 192.168.2.65 0.0.0.0 UG 0 0 0 br0 > > br0 is a bridge to the physical interface on the vm host. virbr? are > bridges created via the virt-manager interface. > > I've tried all kinds of route changes to the VM and the vm host. It > seems the vm host will not route through the 2.65 gateway for the VM > guest. I'm not certain at this point if the routing is a problem with > the route tables in the VM guest and/or VM host or a configuration > problem with libvirt's network configuration for default.xml. I've > tried creating new networks via virt-manager but that didn't do much > different than what was in default.xml. > > Any pointers? > -- > Michael J. Hammel Principal Software Engineer > mjhammel at graphics-muse.org http://graphics-muse.org > ------------------------------------------------------------------------------ > Everything should be made as simple as possible. > But not simpler. -- Albert Einstein. > > _______________________________________________ > Web Page: http://lug.boulder.co.us > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug > Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety From jeffrey.haemer at gmail.com Sat Oct 25 17:11:08 2014 From: jeffrey.haemer at gmail.com (Jeffrey S. Haemer) Date: Sat, 25 Oct 2014 17:11:08 -0600 Subject: [lug] Fwd: funny In-Reply-To: <20141025230202.M14829@pedant.com> References: <20141025230202.M14829@pedant.com> Message-ID: ---------- Forwarded message ---------- From: Peter H Salus Date: Sat, Oct 25, 2014 at 5:02 PM Subject: funny To: "Jeffrey S. Haemer" http://bitly.com/12zxDhD ------------------------------------------------------------ Peter H. Salus, Ph.D. 211 St. Patrick St., #1001 Toronto, ON M5T 2Y9 CANADA peter at pedant.com +1 416 408-1728 -- Jeffrey Haemer 720-837-8908 [cell], http://seejeffrun.blogspot.com [blog], http://www.youtube.com/user/goyishekop [vlog] *????????? ??? ??? ????? ????? ??????.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From stimits at comcast.net Sun Oct 26 17:37:12 2014 From: stimits at comcast.net (stimits at comcast.net) Date: Sun, 26 Oct 2014 23:37:12 +0000 (UTC) Subject: [lug] Ubuntu 14.04 LTS syslog/rsyslog Stopped Logging kern.log Message-ID: <994269248.18387137.1414366632554.JavaMail.root@comcast.net> Hi, In the past few days I did an apt-get upgrade on an Ubuntu 14.04 LTS system which I'm trying to work on kernel modules for. Logging of all kernel messages suddenly ceased, and kern.log is now empty. If I use a printk with KERN_INFO, I can still get the output via dmesg, but am scratching my head as to where the actual log file is...I've grepped and gunzip'd and done all I can in /var/log/, and never figured out where the KERN_INFO actually goes. tail -f can no longer be used, as not even the /var/log/dmesg file contains these messages...somehow the dmesg binary command magically pulls KERN_INFO out of the air even when its specific log file does not have this information. So what could have happened with this apt-get upgrade? I've seen some past reports (without solution for the current situation) on syslog or rsyslog stopping logging to /var/log/kern.log, but these do not seem to be current information and have not given clues as to how configuration changed. Anyone here have ideas on what to check for current Ubuntu no longer logging to kern.log, yet showing up in dmesg program but not showing up in dmesg log files? Other than this the system seems to work fine...but it makes it a pain to work on kernel modules (FYI, there are no current changes to any modules or kernel on this system, so module development can't be a cause). Thanks! PS: I've looked at everything I can in /etc related to syslog and rsyslog but found nothing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blug-mail at duboulder.com Sun Oct 26 21:38:08 2014 From: blug-mail at duboulder.com (Lee Woodworth) Date: Sun, 26 Oct 2014 21:38:08 -0600 Subject: [lug] Ubuntu 14.04 LTS syslog/rsyslog Stopped Logging kern.log In-Reply-To: <994269248.18387137.1414366632554.JavaMail.root@comcast.net> References: <994269248.18387137.1414366632554.JavaMail.root@comcast.net> Message-ID: <544DBE20.7030409@duboulder.com> On 10/26/2014 05:37 PM, stimits at comcast.net wrote: > Hi, > > In the past few days I did an apt-get upgrade on an Ubuntu 14.04 LTS system which I'm trying to work on kernel modules for. Logging of all kernel messages suddenly ceased, and kern.log is now empty. If I use a printk with KERN_INFO, I can still get the output via dmesg, but am scratching my head as to where the actual log file is...I've grepped and gunzip'd and done all I can in /var/log/, and never figured out where the KERN_INFO actually goes. tail -f can no longer be used, as not even the /var/log/dmesg file contains these messages...somehow the dmesg binary command magically pulls KERN_INFO out of the air even when its specific log file does not have this information. I suppose you have checked to see if the *syslog* dameon is running. Did something like systemd get pulled in that wasn't there before? A reboot might also give you more information. Does the /dev/log socket exist and is at least world readable? It is strange that a find /etc -iname '*syslog*' wouldn't find anything. There are other loggers, e.g. metalog. Maybe the logging system was changed or deselected during the upgrade -- you don't actually have to have a logging service/daemon running for a system to run. IIRC, the kernel has an in-memory message buffer (the size is set in the kernel config somewhere). I suspect dmesg could read from that when the /var/log/dmesg data file doesn't exist. HTH > > So what could have happened with this apt-get upgrade? I've seen some past reports (without solution for the current situation) on syslog or rsyslog stopping logging to /var/log/kern.log, but these do not seem to be current information and have not given clues as to how configuration changed. Anyone here have ideas on what to check for current Ubuntu no longer logging to kern.log, yet showing up in dmesg program but not showing up in dmesg log files? Other than this the system seems to work fine...but it makes it a pain to work on kernel modules (FYI, there are no current changes to any modules or kernel on this system, so module development can't be a cause). > > Thanks! > > PS: I've looked at everything I can in /etc related to syslog and rsyslog but found nothing. > > > > _______________________________________________ > Web Page: http://lug.boulder.co.us > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug > Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety >