- wlug - University of Waikato Mail Lists

Re: [wlug] wlug Digest, Vol 235, Issue 2
by noel villamor 05 Jan '11

05 Jan '11

How old is this Sony Viao laptop? Some parts may be salvaged if we have model info.

2 1

Re: [wlug] Laptop
by Sam Lin 04 Jan '11

04 Jan '11

Or leave the laptop until eDay2011? Regards, Sam > Message: 1 > Date: Mon, 03 Jan 2011 14:13:15 +1300 > From: John <jaytee(a)clear.net.nz> > To: Waikato Users Group <wlug(a)list.waikato.ac.nz> > Subject: [wlug] Laptop > > Hi All, > I have a Sony Viao laptop with a dead main board no h/d. The screen, > CPU, or sundry ports may be required by someone before it is deposed of. > Please contact me if interested. > Regards John

4 3

Laptop
by John 03 Jan '11

03 Jan '11

Hi All, I have a Sony Viao laptop with a dead main board no h/d. The screen, CPU, or sundry ports may be required by someone before it is deposed of. Please contact me if interested. Regards John

1 0

Fwd: help please
by Bruce Kingsbury 23 Dec '10

23 Dec '10

---------- Forwarded message ---------- From: John Torrance <jtorrance(a)slingshot.co.nz> Date: 27 November 2010 23:49 Subject: help please To: wlug-owner(a)list.waikato.ac.nz I sent this request for help but it was bounced for some reason. I have been unable to update my ubuntu - when using the command line, I get the following errors. Could someone help me please Cheers John warning, in file '/var/lib/dpkg/available' near line 61945 package 'flyback': error in Version string '0.6.1_r111-1': invalid character in version number Setting up python-wxgtk2.8 (2.8.11.0-0ubuntu4) ... Compiling /usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_controls.py ... SyntaxError: ("keyword can't be an expression", ('/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_controls.py', 5089, None, 'Data = property(GetData,SetData<doc="See `GetData` and `SetData`") \n')) pycentral: pycentral pkginstall: error byte-compiling files (429) pycentral pkginstall: error byte-compiling files (429) dpkg: error processing python-wxgtk2.8 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python-wxversion: python-wxversion depends on python-wxgtk2.8 (>= 2.8.6.1-0ubuntu2) | python-wxgtk2.6 (>= 2.6.3.2.2-1ubuntu2); however: Package python-wxgtk2.8 is not configured yet. Package python-wxgtk2.6 is not installed. dpkg: error processing python-wxversion (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of python-wxtools: python-wxtools depends on python-wxgtk2.8; however: Package python-wxgtk2.8 is not configured yet. dpkg: error processing python-wxtools (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of python-wxgtk2.8-dbg: python-wxgtk2.8-dbg depends on python-wxgtk2.8 (= 2.8.11.0-0ubuntu4); however: Package python-wxgtk2.8 is not configured yet. dpkg: error processing python-wxgtk2.8-dbg (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Errors were encountered while processing: python-wxgtk2.8 python-wxversion python-wxtools python-wxgtk2.8-dbg E: Sub-process /usr/bin/dpkg returned an error code (1) -- Disclaimer: By sending an email to any of my addresses you are agreeing that: 1. I am by definition, "the intended recipient" 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. 3. I may take the contents as representing the views of your company. 4. This overrides any disclaimer or statement of confidentiality that may be included on your message.

3 2

iSCSI as common storage
by Gregory Machin 12 Dec '10

12 Dec '10

Hi. I would like to avoid setting up a file server as back-end to my web server cluster, as this would give a single point of failure. Give we are running a iSCSI array of 8 nodes with redundancy and replication etc, I would like to take advantage of this. It's the first time I'll be working with iSCSI from within Linux. A) is it possible and b) if it is, how do I best configure multiple machine to use the same iSCSI LUN / data store, as a "common share " . I assume I need a more advance file system that ext3. Is there a howto on this ? I have found anything on google yet .. still digging.... Thanks -- - TLA - three letter acronym ... - We are loosing the art of communication through progress.. Proverbs 27:17 (New International Version) 17 As iron sharpens iron, so one man sharpens another.

3 3

Free to Good Home:
by Wayne Grimsey 06 Dec '10

06 Dec '10

Hi WLUGers My wife has an old PC circa 2000. It's still in working order. included are a monitor, cables, box (holding hard disc, CD-ROM and floppy disk), keyboard and mouse. OS may be Windows 98 and also may be loaded with Office 2000. Haven't booted it for a while. This machine is free to a good home. For anyone who may want to play around with an old PC Let me know if you're interested or have any questions. Wayne

3 2

Waikato ICT Christmas Curry
by David Hallett 05 Dec '10

05 Dec '10

Waikato ICT Christmas Curry Wednesday 15 December 2010: 6:30 pm - 10:00 pm Little India 4 Alexandra Street Cnr Alexandra & Hood Streets Hamilton Kick-start the summer heat with a delicious curry dinner held for the Hamilton ICT industry. NZCS is holding a curry banquet at Little India with festive company and the opportunity to chat and network with others. As well as the opportunity for informal discussion, Waikato/BOP NZCS Councillor, David Hallett is available to discuss the IT industry and profession in New Zealand, opportunities, and the big picture of where we're heading and why. Registration Details It is essential to book for this event - no door registrations can be accepted! https://www.nzcs.org.nz/events/waikato_bop/261-Waikato_ICT_Christmas_Curry Cash Bar Operating NB: The event includes wine provided by NZCS, however additional drinks are at bar costs, payable to the wait staff.

1 0

CentOS release 5.4 (Final) + Nic Bonding + machine goes out of network randomly + 2.6.18-164.6.1.el5 #1 SMP kernel
by Narender 24 Nov '10

24 Nov '10

Hi We are facing a strange problem from past few days. Below are the logs attached for ref. We are using nic bonding to our dell server. It has centos 5.4 installed with 4 nic cards. This machine was working good from past few months. But from previous 2-3 days it went out of network by itself. Any pointer or help would be much appreciated. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ cat /proc/cpuinfo processor : 15 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5530 @ 2.40GHz stepping : 5 ============================================================================================== [root@S log]# uname -a Linux ABC.NETXXXXXX 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:12:36 EST 2009 x86_64 x86_64 x86_64 GNU/Linux ============================================================================================ [root@S log]# cat /etc/redhat-release CentOS release 5.4 (Final) [root@SJC-SRCH-03-R ~]# dmesg |grep eth | more eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 90, node addr 00219b8fd3bc eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 98, node addr 00219b8fd3be eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem da000000, IRQ 106, node addr 00219b8fd3c0 eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem dc000000, IRQ 114, node addr 00219b8fd3c2 cnic: Added CNIC device: eth0 cnic: Added CNIC device: eth1 cnic: Added CNIC device: eth2 cnic: Added CNIC device: eth3 bonding: bond0: Adding slave eth0. bnx2: eth0: using MSIX bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: enslaving eth0 as a backup interface with a down link. bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: Adding slave eth1. bnx2: eth1: using MSIX bnx2i: iSCSI not supported, dev=eth1 bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: enslaving eth1 as a backup interface with a down link. bnx2i: iSCSI not supported, dev=eth1 bonding: bond0: link status definitely up for interface eth0. bonding: bond0: making interface eth0 the new active one. bonding: bond0: link status definitely up for interface eth1. bonding: bond0: link status definitely down for interface eth1, disabling it bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: link status definitely up for interface eth1. bonding: bond0: making interface eth1 the new active one. bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2i: iSCSI not supported, dev=eth2 bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2i: iSCSI not supported, dev=eth2 bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2i: iSCSI not supported, dev=eth3 bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2i: iSCSI not supported, dev=eth3 bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2i: iSCSI not supported, dev=eth2 bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2i: iSCSI not supported, dev=eth3 bonding: bond0: Removing slave eth1 bonding: bond0: releasing active interface eth1 bonding: bond0: making interface eth0 the new active one.ease 5.4 (Final) bonding: bond0: Removing slave eth0 bonding: bond0: releasing active interface eth0 bonding: unable to remove non-existent slave eth1 for bond bond0. bonding: bond0: Adding slave eth0. bnx2: eth0: using MSIX bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: enslaving eth0 as a backup interface with a down link. bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: Adding slave eth1. bnx2: eth1: using MSIX bnx2i: iSCSI not supported, dev=eth1 bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: enslaving eth1 as a backup interface with a down link. bonding: bond0: link status definitely up for interface eth0. bonding: bond0: making interface eth0 the new active one. bonding: bond0: link status definitely up for interface eth1. bnx2i: iSCSI not supported, dev=eth1 bonding: bond0: link status definitely down for interface eth1, disabling it bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: link status definitely up for interface eth1. bonding: bond0: making interface eth1 the new active one. bonding: bond0: Removing slave eth0 bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:21:9B:8F:D3:BC - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. bonding: bond0: releasing backup interface eth0 bonding: bond0: Removing slave eth1 bonding: bond0: releasing active interface eth1 bonding: bond0: Adding slave eth0. bnx2: eth0: using MSIX bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: enslaving eth0 as a backup interface with a down link. bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: Adding slave eth1. bnx2: eth1: using MSIX bnx2i: iSCSI not supported, dev=eth1 bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: enslaving eth1 as a backup interface with a down link. bonding: bond0: link status definitely up for interface eth0. bonding: bond0: making interface eth0 the new active one. bonding: bond0: link status definitely up for interface eth1. bnx2i: iSCSI not supported, dev=eth1 bonding: bond0: link status definitely down for interface eth1, disabling it bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON bonding: bond0: link status definitely up for interface eth1. bonding: bond0: making interface eth1 the new active one. =========================================================================================================================================== ============================================================================================ [root@S ~]# modinfo e1000 | more filename: /lib/modules/2.6.18-164.6.1.el5/kernel/drivers/net/e1000/e1000.ko version: 7.3.20-k2-NAPI license: GPL description: Intel(R) PRO/1000 Network Driver author: Intel Corporation, <linux.nics(a)intel.com> srcversion: 26DD82C709EB760C93D4103 alias: pci:v00008086d00001000sv*sd*bc*sc*i* depends: vermagic: 2.6.18-164.6.1.el5 SMP mod_unload gcc-4.1 parm: TxDescriptors:Number of transmit descriptors (array of int) parm: TxDescPower:Binary exponential size (2^X) of each transmit descriptor (array of int) parm: RxDescriptors:Number of receive descriptors (array of int) parm: Speed:Speed setting (array of int) parm: Duplex:Duplex setting (array of int) parm: AutoNeg:Advertised auto-negotiation setting (array of int) parm: FlowControl:Flow Control setting (array of int) parm: XsumRX:Disable or enable Receive Checksum offload (array of int) parm: TxIntDelay:Transmit Interrupt Delay (array of int) parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int) parm: RxIntDelay:Receive Interrupt Delay (array of int) parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int) parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int) parm: SmartPowerDownEnable:Enable PHY smart power down (array of int) parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int) parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint) parm: debug:Debug level (0=none,...,16=all) (int) ================================================================================================= [root@ ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d ============================================= root@S ~]# ethtool -i eth0 driver: bnx2 version: 1.9.3 firmware-version: 4.6.4 NCSI 1.0.6 bus-info: 0000:01:00.0 [========================= [root@ ~]# ethtool -i eth1 driver: bnx2 version: 1.9.3 firmware-version: 4.6.4 NCSI 1.0.6 bus-info: 0000:01:00.1 ================================ [root@S ~]# ethtool -i bond0 driver: bonding version: 3.4.0 firmware-version: 2 bus-info: ===================================

1 1

Re: [wlug] Wake-up call. Where to next for WLUG
by Sam Lin 21 Nov '10

21 Nov '10

Hi Rod and WLUG fellows - I am a PCBSD (or FreeBSD) user and have attended couples of WLUG activities recently including Monday meetings, Saturday workshops, SFD2008@Waikato University, SFD2010@Central Plaza and eDay2010. I have for the last few years been using and contributing to FLOSS both on *BSD and Windows, and have also been spreading the word of FLOSS whenever there is "appropriate" chance. For a long time I have usually, if not always, felt that *BSD, Linux or even FLOSS is still giving the general public a wrong impression that these are for geeks but not for the them to use. One example is that all books regarding Linux are titled something like "Building a Linux server system", "Linux systems", "xxx Programming Language Bible" etc whereas undeniably these would scare most general users away. While more general books and online tutorials for general users are coming out nowadays, these are still far less than those technical stuff. Another example is that the term Linux refers not to a OS but to a kernel, whereas general users just don't realise the difference between them nor do they care what they exactly are; all they care is - how to use those common/useful software in their daily lives. This is what the public is interested in as well as in need of the most. Linux? System administrating? Programming? These are definitely useful for techies but sorry most people just don't intend to bother them. As a side note, in NZ there used to be a user group called NZFUG (New Zealand FreeBSD User Group) but apparently they have disbanded years ago, which I believe is due to fail to draw the public's interest mainly for the similar reason. Sadly enough, all official FreeBSD webpage/ftp mirror sites in NZ were also discontinued due to the lack of maintainers for ages. I see WLUG is unfortunately following the same path. WLUG has been holding several interesting talks in the meetings as well as valuable activities, I felt WLUG (and probably other FLOSS-related user groups too) needs to focus more on the general user base. An introduction to Inkscape given by Stephen last month is a good start. I think similar tutorials/seminars about other FLOSS e.g. GIMP, Scribus etc would be helpful for both the user group and the public. While technical skills is an important part of WLUG, I think expanding and promoting FLOSS to a wider audience urgently need to be prioritised - if the user group is still to be continued. I also think that the user group had better not claim something like FLOSS/Linux but instead use the term FOSS as this otherwise would give the public an impression that all these was only for Linux, whereas in fact FLOSS exist on *BSD, Windows and other platforms. That said, by using the term "FLOSS" instead of "FLOSS/Linux" it would be less likely to limit ourselves from the otherwise potential yet wide user base. I was even dreaming that, if I were to lead the WLUG, I would rename the user group to say WFUG (Waikato FLOSS User Group) and merge those FLOSS users at the Waikato or even in NZ from other platforms - regardless of *BSD, Linux, Mac or Windows. Perhaps it is only by combining these sparse forces that could increase the odds to sustain the FLOSS community at Waikato or in NZ in the long run. Regarding the finances, I felt some expenses had not been necessary nor worth the outcomes. Software Freedom Day this year was actually not really successful as people really do not want to be disturbed in the middle of their shopping by someone proposing FLOSS. As for the Internet usage/cost, I think Internet is also not necessary in the Saturday workshops as the workshop shouldn't be a free Internet cafe (another reason is that downloading in NZ is by nature not favourable due to the restriction in the monthly Internet usage policy in NZ). To help visitors install FLOSS/ISOs these could have been prepared on disks in advance rather than repeatedly downloaded during the workshop. Another thing I felt WLUG needs to improve is communication within the user group member as well as with the public. Take eDay2010 for example, some people was told by the user group that he would be assigned the time and tasks by email before eDay whereas ultimately he didn't get any contact from the user group. Communication within the user group needs to be organised and improved. As for the communication with the public, this has largely to do with advertisement. Not many people know about WLUG and the activities the user group has been holding. There are actually many low-cost or even free yet more effective ways to advertise WLUG activities... for instance Facebook, Tweet, or "chain-email" through friends of friends etc. Just my two cents. Regards, Sam > From:?Roderick Aldridge <rod-aldridge(a)xnet.co.nz> > To:?Waikato Linux Users Group <wlug(a)list.waikato.ac.nz> > Date:?Wed, 10 Nov 2010 08:24:12 +1300 > Subject:?Wake-up call. Where to next for WLUG? > > Hi WLUG members > > Most members of the committee are retiring or leaving. Nobody has > definitely indicated they are willing to stand again... > What do you want WLUG to do in the future? > What activities should we focus on? What else should we be doing? What > will get your support and continued membership? > Should we concentrate mainly on technical skills, or promoting > FOSS/Linux to a wider audience, or both? > The membership has dwindled somewhat, as have our finances, due to > reduced membership and to Software Freedom Day expenses being higher > than planned (liability insurance etc). > Should we continue as an incorporated society or become an informal > group with shared interests or disband altogether? Unless we get > enough people coming forward to hold? office and continue membership > we will have no choice but to disband. > For a quorum we need 50% of the membership or 15 members to attend, so > come to the AGM which will decide these matters. Let us know what you > what you want WLUG to do and what you can do to contribute to the > future of WLUG. > Roderick Aldridge > > > ------------------------------

4 3

REMINDER: WLUG meeting tonight!
by Meeting Reminder Bot 21 Nov '10

21 Nov '10

There's a WLUG meeting tonight: ---------------------------------------------------------------------- !!! WLUG AGM ANNOUNCEMENT: Annual General Meeting, 22nd November In accordance with Rule 6 of the charter, I would like to announce to all members that the Waikato Linux Users Group (Incorporated) will be holding its Annual General Meeting on Monday, 22 November, 2010, at 7pm, at the regular meeting location of Room MS4.G.02 (http://www.waikato.ac.nz/contacts/map?MS4) Several officers and committee members will be stepping down this year. Society membership has also gone down recently. Present and past members interested in seeing WLUG continue as an IncorporatedSociety are encouraged to attend this years AGM to meet quorum requirements and stand for election. If a quorum is established and new officers step forward, a bylaw change is proposed to be voted on. Please see the WlugCharterDiscussion for more details. Note: To be eligible to vote at the meeting you must have previously been a financial member (although not necessarily for the 2010 year) and pay your membership for 2011 at or before the AGM. To be eligible to vote or stand for office at the AGM members must have paid a subscription for the 2010 year before the AGM. If you'd like to stand for committee and have not paid for membership this year, please do this at the October Meeting or November SaturdayWorkshop. An amendment about who can vote at the meeting was passed in 2008. "That the WLUG charter be amended to allow former paid members of the WLUG of good standing, whose membership has lapsed, to vote at an AGM of the WLUG with the proviso that they rejoin the WLUG and pay a new subscription at or before the AGM."

1 0