3c501 device eth0 does not seem to be present....
On Mon, 2007-01-08 at 21:31 -0500, Ben Scott wrote: On 1/8/07, mike miller [EMAIL PROTECTED] wrote: the next line is bringing up interface eth0; 3c501 device eth0 does not seem to be present delaying installation (failed). 3C501 would be, if I remember correctly, 3Com's first PC Ethernet card, circa 1985. I'd say something is being improperly identified. Even Fedora really does think you have a 3C501 when you don't, or Fedora thinks you have something else, but is loading the wrong driver. Interesting. This: http://www.fedoraforum.org/forum/showthread.php?t=60870 suggests that it's a bad diagnostic; the system is trying to tell you it could not load the driver for *your* NIC, but incorrectly reports it could not load the 3C501 driver. You might try running system-config-network to see what the system thinks you have. According to http://www.abit-usa.com/products/mb/drivers.php?categories=1model=311 your motherboard has a Realtek 8118B Gigabit network controller. I'm not having much luck finding info on that. Is it perhaps a very new or unusual chip? The one interesting find I made was http://www.fedoraforum.org/forum/archive/index.php/t-108031.html My year old laptop has a realtek 8169 which is supported. The driver was simply part of the kernel package. I think that's good news in that realtek is getting supported in the core packages. I do not have any other r drivers, so it looks like support for your controller has not yet arrived in fedora. That might be an argument for switching to ubuntu. The bug report https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215243 says that the controller is supported in the next (2.6.19) kernel release. which suggests building the driver from source -- yuck. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ -- Lloyd Kvam Venix Corp. 1 Court Street, Suite 378 Lebanon, NH 03766-1358 voice: 603-653-8139 fax:320-210-3409 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: $_
On Tuesday, Jan 9th 2007 at 00:03 -0500, quoth [EMAIL PROTECTED]: = =Yeah, I know, it's a great subject line. :) = =But $_ is just SO handy! = =$ play voicemail1234.wav =$ rm $_ =$ cp myfile1 /some/path =$ less $_/myfile2 = =At the command line, $_ expands to the last argument to the previous =command. And, with tab completion, you can even see and edit it! = =If y'all haven't tried $_ yet, you should definitely give it a spin! In terms of good practices, (assuming you're using bash) I prefer using !$ !$ is the last argument of the last command. It's from the csh history functionality that is part of bash. See the bash man page under HISTORY EXPANSION. Things like !-2, !!, $-2:$, etc are all together more flexible. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Monadlug January Meeting
The January meeting of the Monadnock chapter of GNHLUG will meet Thursday, Jan. 11, at 7:00 PM. The meeting will be held as usual at the SAU 1 offices, 106 Hancock Road, Peterborough. This months program: Building a WRT54G Firewall -- Lloyd Kvam -- MonadLUG, 11 January 2006 What do you do if one of your clients has a Microsoft Windows server, directly connected to the Internet, it gets infected, and the client is so dependent on the thing that it cannot be taken off line for a fix? You use Linux, of course. If you're Lloyd Kvam, you use Linux on a flash-based appliance box -- say the popular Linksys WRT54G. Lloyd will describe how to use a WRT54G to act as a Linux firewall, demonstrate the tools, and describe the VLAN topology he used to rescue a poor, broken Windows system. Under fire! Lloyd Kvam is proprietor of Venix Corporation, a charter member of GNHLUG's Dartmouth/Lake Sunapee chapter, and a founding member of GNHLUG's Python SIG. -- Charles Farinella Appropriate Solutions, Inc. (www.AppropriateSolutions.com) [EMAIL PROTECTED] voice: 603.924.6079 fax: 603.924.8668 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: $_
Date: Tue, 9 Jan 2007 09:43:27 -0500 (EST) From: Steven W. Orr [EMAIL PROTECTED] =If y'all haven't tried $_ yet, you should definitely give it a spin! In terms of good practices, (assuming you're using bash) I prefer using !$ !$ is the last argument of the last command. It's from the csh history Using !$ has the advantage that bash shows you the expanded version of the command you are executing. But !$ doesn't interact with tab completion like $_ does. Try this: $ ls -al /etc/sysctl.conf $ less $_/TAB ...turns magically into... $ less /etc/sysctl.conf ...and you can hit backspace... $ less /etc/ ...and fill in something eles $ less /etc/asound.conf In my commands, I've historically (ha ha) avoided ! like the plague because - for me - it has more often than not lead to unexpected results. Of course, taking the time to learn all the ! forms would probably help with this! The idea of being able to access parameters other than the last *does* appeal to me. It sure would be nice if ! forms could be expanded in-place and edited before the command was issued. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
NH Seacoast Ruby/Rails *meeting location CHANGED*
Hi GNHLUGers, I'm happy to report that interest in the new NH Seacoast Ruby/Rails user group has far surpassed my expectations. Apparently there is a lot of interest from people involved with the Greater NH Linux Users Group (GNHLUG), the Boston Ruby mailing list, and Meetup.com. With over a dozen RSVPs, there was no way I could host the meeting in one of the UNH Library study rooms, which can hold 4-6 people, max. For that reason, I have secured a much larger meeting room in Morse Hall at UNH, thanks to the help of Rob Anderson, who runs the Seacoast Linux User Group meetings (thanks Rob!). WHEN: Tuesday, January 16, 2007, from 7-9 PM (same time) WHERE: Morse Hall, Room 301, UNH Campus. Durham, NH (new location, but still at UNH) WHAT: Scott Garman will be sharing some of his favorite resources for developing with Ruby/Rails and following the community. We'll also engage in such exciting activities as creating a regular meeting location and schedule, setting up a mailing list, and coming up with an organization name that makes a cool acronym! I will send out detailed directions and maps sometime on Friday to everyone who has contacted me with interest in attending. If you're not on my announcement list already, please drop me a line ASAP. Regards, Scott Garman -- Scott Garman sgarman at zenlinux dot com ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[GNHLUG] Comet McNaught
You may have heard that January 2007 has presented us with a surprise, an exceptionally bright comet, discovered only in August 2006. Called 2006 P1, or Comet McNaught, it's now visible to the naked eye. It was tonight, anyway! Here's some stuff: http://skytonight.com/observing/home/5133461.html http://antwrp.gsfc.nasa.gov/apod/ap070109.html Janet and I went out to Curtis Hill in Lyndeborough, and from there the period of visibility was from 5:00PM to 5:15PM local time (EST). I'd concur that the directions in the skytonight.com reference would get you there, although we spotted it first by eye. Venus appears solidly (perhaps 10 minutes before the comet) and is a good visual anchor point. (The pictures show Venus just a little higher than 10 degrees, which is accurate, but the picture makes it LOOK higher. 10 degrees is low -- and the comet is lower still.) It IS imperative that your view to the southwest be unobstructed, right down to the horizon, and that the weather be clear. (Can't be sure about the latter - tomorrow's forecast includes chance of snow showers, and the weather around sunset scattered at 4500. My personal forecast is that it'll be dead clear (and blustery COLD), and that the scattered deck will permit a view underneath. Anyway, tonight was, and tomorrow will be, the best chances, with Thursday a runner-up. If you're one of our geek friends, or one of our amateur radio friends, or one of our pilot friends... well, good luck -- and try to stay warm! -Bill and Janet ___ gnhlug-announce mailing list gnhlug-announce@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-announce/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: linux newbie
On Jan 8, 2007, at 21:31, Ben Scott wrote: which suggests building the driver from source -- yuck. I seem to recall running across a server recently with this chip, but I can't seem to figure out which one it was at the moment to pull the config off of it. But building the source wasn't a big deal. Making sure gcc and friends and the kernel source tree are installed are likely to be bigger challenges, but perhaps more documented ones. driver: ftp://210.51.181.211/cn/nic/r1000_v1.05.tgz from README: Requirements - kernel source tree (supported versions 2.4.x or 2.6.x) - compiler/binutils for kernel compilation Quick install with proper kernel settings Unpack the tarball : tar vzxf r1000_vX.YZ.tgz Change to the directory: cd r1000_vX.YZ If you are running the target kernel, then you should be able to do : make clean modules (as root or with sudo) make install depmod -a -Bill - Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 [EMAIL PROTECTED] Cell: 603.252.2606 http://www.bfccomputing.com/Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
