August 2001 - WLUG - wlug.mailman3.com

Re: [Wlug] gettin' the Sparc Classic on the network...

by john＠stoffel.org

Sands> Settin' up the box I won at the last WLUG meeting. I wanna Sands> get it on the network here at work. When I watch the boot Sands> messages, I see "eth0 LANCE <mac address>" and "eth0 using Sands> auto-carrier-detection", but i don't see an entry for /dev/eth0 Sands> when i look there. I can ping the local loopback, but when I Sands> try to use DHCP in linuxconf to let it grab an address, but in Sands> ifconfig, i still only see the entry for the local loopback. Sands> Is there a different location for the eth0 device? Any hints? Sands> Anything would be appreciated. Thanx everyone. The box should already be semi setup to use an address between 192.168.1.101-105, or something like that. I don't remember exactly what I used and I'm not at home to check. The LANCE part is the ethernet chip, eth0 is the interface you need to use to access the net. Do you have any errors in the log file when you run dhcpd on the box? It might need to have some stuff put into /etc/dhcpd.conf to get it working right. I can check this at home if need be. And if need be, I can rip a copy of RH 6.1 for Sparc and bring it to the next meeting for those who'd like to get packages for it. John

Aug. 22, 2001

Re: [Wlug] gettin' the Sparc Classic on the network...

by Chuck Homic

On Wed, Aug 22, 2001 at 05:04:44PM -0400, Ben Dow wrote: > Well, I might be a little out of touch with my old-fashioned Slackware > ways, but I don't think there's supposed to be a /dev/eth0. DHCP must not > be working if it's not showing up in ifconfig, but try ifconfig eth0 to > see if the interface exists. You can always try running dhcpcd manually, > too. Right. eth0 is a network interface, not a device, so there is no /dev/ entry. If you're just trying to test the interface, you can also just assign it an IP by hand by doing "ifconfig eth0 192.168.blah.blah". You might also need some -netmask goodness, but I'm not sure. "man ifconfig" has the goods. Then once that works, I'd start getting into DHCP. I'm a little paranoid with DHCP... at work I use dhcpcd because pump doesn't work. At home (with road-runner), I use pump because dhcpcd doesn't work. Am I on crack? -Chuck

Aug. 22, 2001

Re: [Wlug] gettin' the Sparc Classic on the network...

by Ben Dow

Well, I might be a little out of touch with my old-fashioned Slackware ways, but I don't think there's supposed to be a /dev/eth0. DHCP must not be working if it's not showing up in ifconfig, but try ifconfig eth0 to see if the interface exists. You can always try running dhcpcd manually, too. On Wed, 22 Aug 2001, Sands Fish wrote: > Hello all, > Settin' up the box I won at the last WLUG meeting. I wanna get it on > the network here at work. When I watch the boot messages, I see "eth0 LANCE > <mac address>" and "eth0 using auto-carrier-detection", but i don't see an > entry for /dev/eth0 when i look there. I can ping the local loopback, but > when I try to use DHCP in linuxconf to let it grab an address, but in > ifconfig, i still only see the entry for the local loopback. Is there a > different location for the eth0 device? Any hints? Anything would be > appreciated. Thanx everyone. > > - Sands Fish > - eCommerce > - telecomNOW > - sands(a)telecomnow.com >

Aug. 22, 2001

gettin' the Sparc Classic on the network...

by Sands Fish

Hello all, Settin' up the box I won at the last WLUG meeting. I wanna get it on the network here at work. When I watch the boot messages, I see "eth0 LANCE <mac address>" and "eth0 using auto-carrier-detection", but i don't see an entry for /dev/eth0 when i look there. I can ping the local loopback, but when I try to use DHCP in linuxconf to let it grab an address, but in ifconfig, i still only see the entry for the local loopback. Is there a different location for the eth0 device? Any hints? Anything would be appreciated. Thanx everyone. - Sands Fish - eCommerce - telecomNOW - sands(a)telecomnow.com

Aug. 22, 2001

Re: [Wlug] REPLY TO FROM (!!!)

by Andy Stewart

HI all, Nothing is perfect in this world, especially computers, no matter how much we all choose to deny it! :-) With that said, please use care when replying, and make sure that your favorite mailing tool sends your reply wherever you desire it to go, be it the list or the original sender. Have a sense of humor when somebody obviously makes the inevitable mistake. I think this is the best we can do until somebody invents the DWIM button on e-mail GUIs (do what I mean). :-) Later, Andy -- Andy Stewart Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org

Aug. 20, 2001

Re: [Wlug] REPLY TO FROM (!!!)

by Chuck Homic

I'd just like to say this is my favorite thread in the world! :) You guys are all nuts... and I realize that having pedants like you is the reason everything works so well. I've never had that kind of energy, but from a spectator's point of view this is just awesome. God bless WLUG! (BTW, I'm with Theo... I just check my headers, dude! :) ) -Chuck

Aug. 20, 2001

Re: [Wlug] REPLY TO FROM (!!!)

by Josh Huber

Aaron Haviland <orion(a)tribble.dyndns.org> writes: > i'm more familiar with this setup myself. mutt works nicely with > mailing lists. i have "bind pager l list-reply" and "lists `cd > ~/inboxes && echo *`" in my muttrc, and on most mailman mailing > lists, i can just hit 'l' to reply to the list. if i hit 'r', it > prompts me to reply to the list or the sender. I'd like to point out that the whole purpose of list-reply in mutt is to reply to the list, and to have reply ("r") go to the author. Why bother having it prompt you if you can have "l" send a message to the list, and "r" send a message to the author? Having Reply-to point back at the mailing list is designed to compensate for other MUA's inability to distiguish between a reply and a followup. (*cough* Outlook *cough* pine *cough*) :) ttyl, -- Josh Huber

Aug. 20, 2001

Re: [Wlug] REPLY TO FROM (!!!)

by Aaron Haviland

Doug Chamberlin said: > At 8/20/2001 11:53 AM (Monday), ccb(a)acm.org wrote: > > > - Some people expect that a reply will goto the group. > > > > > > However, this causes a number of people to respond to the group > > > when they mean the response to goto the sender only. > > > >Of the 40 or so mailing lists that I'm regularly a participant on, the > >wlug list is the only one exhibiting this behavior. It's generally > >consider an anachronism, dating to the days when we all had "!" in our > >email addresses. > > Of the 15 or so mailing lists that I'm regularly a participant on, there > are NO lists which are setup so replies go directly to senders instead of > the list as a whole. Replying by default only to senders hinders one of the > primary benefits of participation - that of sharing info. It is generally > considered "the way to go" to have replies default to the whole list with > strong objections made every time it is suggested that it be changed. i'm more familiar with this setup myself. mutt works nicely with mailing lists. i have "bind pager l list-reply" and "lists `cd ~/inboxes && echo *`" in my muttrc, and on most mailman mailing lists, i can just hit 'l' to reply to the list. if i hit 'r', it prompts me to reply to the list or the sender. just sharing :) -- Aaron Haviland orion [at] tribble [dot] dyndns [dot] org orion [at] parsed [dot] net Random #afda Quote #1: "Cool - my random quote is '"random quotes" is great'" - Tag

Aug. 20, 2001

stat syscall in RH7.1

by Brad Noyes

Hi Fellas I'm trying to get a shared library to work with my red hat 7.1 system. The problem is; when the library makes a system call to stat() i get "<./myprog> error while loading shared libraries: <mylib.so>: undefined symbol: stat". I have tried this on other distro's (debian, namely), and it was able to make the syscall just fine. Any ideas? Here's some info that you may find helpful: i compile with these lines: gcc -g -fPIC -c -g <mylib>.c -o <mylib>.o ld -shared -soname <mylib>.so.0 -o <mylib>.so.0.0.0 -lc <mylib>.o gcc -g <myprog>.o -o <myprog> -L. -l<mylib> ldd <myprog> <mylib>.so.0 => ./<mylib>.so.0 (0x40018000) libc.so.6 => /lib/i686/libc.so.6 (0x4002d000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) gcc --version 2.96 Thanks for any sugesstions, --Brad

Aug. 20, 2001

Re: [Wlug] REPLY TO FROM (!!!)

by Doug Chamberlin

I sent my reply, not because I care strongly one way or the other, but because I didn't want the subject to be too one-sided (since the original message was so strong). There are two very legitimate sides to the debate. I once participated in a list which banned any form of quoting. They had a well considered rationale which included: 1) Replies would be more considered when the writer had to restate the item being replied to. 2) Elimintated over-quoting and other lazy, off-hand replies. 3) Slows the pace of exchange just enough for reasonable reflection, retarding the heated build up of flames. Worked quite well. Would not be popular today.

Aug. 20, 2001