- WLUG - wlug.mailman3.com

Re: [mwblug] one last (maling list) hurrah for USA

by rek2

YAP! On Sunday 16 September 2001 11:33, Jeff Reed wrote: <><>i would personally like to thank the JINX hackwear company <><>for sincerely expressing exactly how i feel on their front <><>page... <><> <><>check it out... <><> <><>http://www.jinxhackwear.com/ <><> -- --------------------------------------------------------------------------------------------------------------------------------------- http://www.tuxedo.org/~esr/jargon/jargon.html#cyberpunk Since 1990 or so, popular culture has included a movement or fashion trend that calls itself `cyberpunk', associated especially with the rave/techno subculture. Hackers have mixed feelings about this. On the one hand, self-described cyberpunks too often seem to be shallow trendoids in black leather who have substituted enthusiastic blathering about technology for actually learning and doing it. Attitude is no substitute for competence. On the other hand, at least cyberpunks are excited about the right things and properly respectful of hacking talent in those who have it. The general consensus is to tolerate them politely in hopes that they'll attract people who grow into being true hackers. --------------------------------------------------------------------------------------------------------------------------------------------- Hacker /n./1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary. 2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than ust theorizing about programming. 3. A person capable of appreciating hack value. 4. A person who is good at programming quickly. 5. An expert at a particular program, or one who frequently does work using it or on it; as in `a Unix hacker'. (Definitions 1 through 5 are correlated, and people who fit them congregate.) 6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example. 7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations.

Sept. 16, 2001

one last (maling list) hurrah for USA

by Jeff Reed

i would personally like to thank the JINX hackwear company for sincerely expressing exactly how i feel on their front page... check it out... http://www.jinxhackwear.com/ -- //-- Jeff Reed //-- Co-founder / Odd (Job) Guy //-- Metro West Boston Linux User Group //-- jreed(a)linuxbusca.com

Sept. 16, 2001

Re: Laptop recommendations

by Robert L Krawitz

I found an HP Pavilion 5470 for $1500 at Circuit City. It was a return. It's only 1024x768, which is less than I want (although it is a 15" display), but with 256 MB, the price, and the combo CDRW/DVD drive, it looked awfully appealing. I have 14 days to decide whether to keep it (there's no restocking fee, since it was an open box). It has a non-Lucent lusemodem. The processor is an Athlon 4/1GHz, for what little that's worth; it's way, way cheaper than anything similar on Pricewatch. According to http://www.deater.net/john/PavilionN5430.html, it's possible to run Linux on it, albeit it uses a not very well supported Trident chipset, among other things. Is anyone familiar with this laptop? Comments? -- Robert Krawitz <rlk(a)alum.mit.edu> http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail lpf(a)uunet.uu.net Project lead for Gimp Print/stp -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton

Sept. 13, 2001

Re: [Wlug] Unable to obtain an IP

by Mike Frysinger

i thought the fact that my 3com nic [a 3c905] was odd in the fact it was using the module 3c59* until i looked for the driver via google and looked at the doc's on it in the kernel help page ... the module that is called 3c59* supports all of these nics: x "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) x "Boomerang" (EtherLink XL 3c900 or 3c905) x "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) x "Tornado" (3c905) x "Hurricane" (3c555/3cSOHO) ... the original driver was meant for the 3c59* nic's, but the original coder found that other, similar 3com nic's had no linux support, so he added in a bunch of 3c90* nic's to his module, but retained the original name. thus, keep the 3c59* module and dont change it, when i forced usage of 3c90*, it broke my nic [i.e. it didnt work], but the 3c59* worked fine -mike ----- Original Message ----- From: "Eric Frederick" <efreder1(a)hotmail.com> To: <wlug(a)mail.wlug.org> Sent: Thursday, September 13, 2001 02:55 AM Subject: Re: [Wlug] Unable to obtain an IP > > EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to > > EF>connect to the internet. I have only been using Linux for about 7-8 > > EF>months and I am still a novice. When I was using Redhat 7.1 last > > EF>spring, it worked fine. > > > > WS>what happened between then and now? new hard drive? (just curious; > i'm > > WS>of the If-it-ain't-broke-don't-fix-it school... <g>) > > I updated the system using Redhat's upgrade system and I recieved errors > messages > and things stopped working. Since I had no clue how to fix it, I > said forget it. > > > EF>I am using a 3com Etherlink card (the driver > > EF>is 3c905c-tx in windows) and my computer seems to detect it correctly. > > > > WS>you know this from the boot up screen? > > I got the information about the NIC by using the command "ifconfig eth0." > The command displays the driver installed for the device. > > > EF>However, it is using the 3com59* driver. I tried to switch to the > > EF>driver to 3com90*, but my computer stopped recognizing the card so I > > EF>doubt it is a driver problem. (Plus, it was using the same driver last > > EF>spring.) > > > > WS>how were you doing this? usually, all you should need to do is > re-compile > > WS>the kernel if support for your Network Interface Card (NIC) isn't there > > WS>already. > > Since I have no clue about recompiling the kernel, I made the changes using > linuxconf. It is a GUI program that is supposed to reconfigure things for > you. > > > EF>I also tried pump -i eth0 and it failed. > > > > WS>i'm not familiar with "pump"... does it have something to do with > DHCP? > > >From what I understand, pump a the program that works with DHCP to get IP > addresses. I am using the DHCP client rather than BOOTP (something like > that.) > since that is what I am supposed to use. > > > EF>Also, I entered an IP hoping that it would pick something up but that > > EF>does not work either. > > > > WS>generally, you can't just "assign" an IP address, unless it's for your > own > > WS>LAN. if you're connecting that system to a LAN AND a dial-up, then you > > WS>need to be careful that your network address isn't something that > > WS>technically belongs to someone else. (for example, it might be nice to > > WS>have a LAN at home with 18.100.x.x, but i'll bet MIT would have > something > > WS>to say to you if you tried to connect that to the 'Net...) > > WS>for private networks, there are a few generally accepted networks that > > WS>work out, since they are Officially Unassigned. try something in the > > WS>192.168.x.x range. if the LAN and the Dial Up are on the same machine, > > WS>there might be a routing issue on the local box. > > The IP address was for my LAN at school. The network officials recommended > that I take this action to resolve the problem. Also, they told me that > they know hardly anything about Linux so I am not about to ask them for more > help. > > > EF>Does anyone know what could be done to resolve the problem or > > EF>at least direct me somewhere. > > > > WS>worst-case, you could always try checking the wire to make sure that > it's > > WS>connected securely. you'd be surprised how many times i've found that > to > > WS>be a problem. <sigh> ;) > > The NIC works on my DOS drive so I doubt that it is a problem. :) However, > could this problem occur if I let the Redhat install program reformat the > drive for me? Should I format the drive myself and then reinstall and see > if the problem is resolved? > > > WS>hope this helps... > > Thank you very much for the advice. I know I should learn to fix the system > rather than format it, but it is hard for me to do that while I am at > school. I have very little time to learn Linux, but I like Linux much > better than Windows and I am trying to convert. I have learned not to > upgrade until I know more about the OS and how to fix it. :-) > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Sept. 13, 2001

Re: [Wlug] Unable to obtain an IP

by Eric Frederick

> EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to > EF>connect to the internet. I have only been using Linux for about 7-8 > EF>months and I am still a novice. When I was using Redhat 7.1 last > EF>spring, it worked fine. > > WS>what happened between then and now? new hard drive? (just curious; i'm > WS>of the If-it-ain't-broke-don't-fix-it school... <g>) I updated the system using Redhat's upgrade system and I recieved errors messages > and things stopped working. Since I had no clue how to fix it, I said forget it. > EF>I am using a 3com Etherlink card (the driver > EF>is 3c905c-tx in windows) and my computer seems to detect it correctly. > > WS>you know this from the boot up screen? I got the information about the NIC by using the command "ifconfig eth0." The command displays the driver installed for the device. > EF>However, it is using the 3com59* driver. I tried to switch to the > EF>driver to 3com90*, but my computer stopped recognizing the card so I > EF>doubt it is a driver problem. (Plus, it was using the same driver last > EF>spring.) > > WS>how were you doing this? usually, all you should need to do is re-compile > WS>the kernel if support for your Network Interface Card (NIC) isn't there > WS>already. Since I have no clue about recompiling the kernel, I made the changes using linuxconf. It is a GUI program that is supposed to reconfigure things for you. > EF>I also tried pump -i eth0 and it failed. > > WS>i'm not familiar with "pump"... does it have something to do with DHCP?

Sept. 13, 2001

Re: [Wlug] Unable to obtain an IP

by William Smith

On Mon, 10 Sep 2001, Eric Frederick wrote: EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to EF>connect to the internet. I have only been using Linux for about 7-8 EF>months and I am still a novice. When I was using Redhat 7.1 last EF>spring, it worked fine. what happened between then and now? new hard drive? (just curious; i'm of the If-it-ain't-broke-don't-fix-it school... <g>) EF>I am using a 3com Etherlink card (the driver EF>is 3c905c-tx in windows) and my computer seems to detect it correctly. you know this from the boot up screen? EF>However, it is using the 3com59* driver. I tried to switch to the EF>driver to 3com90*, but my computer stopped recognizing the card so I EF>doubt it is a driver problem. (Plus, it was using the same driver last EF>spring.) how were you doing this? usually, all you should need to do is re-compile the kernel if support for your Network Interface Card (NIC) isn't there already. EF>I also tried pump -i eth0 and it failed. i'm not familiar with "pump"... does it have something to do with DHCP? EF>Also, I entered an IP hoping that it would pick something up but that EF>does not work either. generally, you can't just "assign" an IP address, unless it's for your own LAN. if you're connecting that system to a LAN AND a dial-up, then you need to be careful that your network address isn't something that technically belongs to someone else. (for example, it might be nice to have a LAN at home with 18.100.x.x, but i'll bet MIT would have something to say to you if you tried to connect that to the 'Net...) for private networks, there are a few generally accepted networks that work out, since they are Officially Unassigned. try something in the 192.168.x.x range. if the LAN and the Dial Up are on the same machine, there might be a routing issue on the local box. EF>Does anyone know what could be done to resolve the problem or EF>at least direct me somewhere. worst-case, you could always try checking the wire to make sure that it's connected securely. you'd be surprised how many times i've found that to be a problem. <sigh> ;) hope this helps... -- William Smith wsmith(a)chezsmith.com Fall River, MA http://www.chezsmith.com

Sept. 13, 2001

Re: [Wlug] lost in kernel

by Aaron Haviland

Brad Noyes said: > Hi all, > Has anyone else had trouble finding an option in the kerel config? I was > looking for support for /dev/imon (for libfam), but i just can't find it in > the kernel config. The kernel has become huge, and hard to find things in. > anyone have an easy way of looking for an option in the kernel, or does anyone > where this /dev/imon option is in the kernel? > > Thanks, > --Brad Unless I'm mistaken, there doesn't exist anything in the official kernel for libfam or imon. At least nothing turned up on a full grep of the 2.4.9 sources. You might need to apply the kernel patches from http://oss.sgi.com/projects/fam/ -- Aaron Haviland orion [at] tribble [dot] dyndns [dot] org orion [at] parsed [dot] net No hish were farmed in frosting to this poup.

Sept. 12, 2001

lost in kernel

by Brad Noyes

Hi all, Has anyone else had trouble finding an option in the kerel config? I was looking for support for /dev/imon (for libfam), but i just can't find it in the kernel config. The kernel has become huge, and hard to find things in. anyone have an easy way of looking for an option in the kernel, or does anyone where this /dev/imon option is in the kernel? Thanks, --Brad

Sept. 12, 2001

Unable to obtain an IP

by Eric Frederick

I reinstalled Redhat 7.1 on my computer at school and I am unable to connect to the internet. I have only been using Linux for about 7-8 months and I am still a novice. When I was using Redhat 7.1 last spring, it worked fine. I am using a 3com Etherlink card (the driver is 3c905c-tx in windows) and my computer seems to detect it correctly. However, it is using the 3com59* driver. I tried to switch to the driver to 3com90*, but my computer stopped recognizing the card so I doubt it is a driver problem. (Plus, it was using the same driver last spring.) I also tried pump -i eth0 and it failed. Also, I entered an IP hoping that it would pick something up but that does not work either. Does anyone know what could be done to resolve the problem or at least direct me somewhere. Thanks, Eric

Sept. 10, 2001

Re: [Wlug] boot images -- safe to delete?

by Ben Dow

Ok, first off, repartitioning isn't really all that bad, at least in my experience... you just get a partition magic 4.0 or higher (for ext2, at least... I doubt even the latest version has support for the more esoteric filesystems... but you probably don't have to worry about that) boot disk, boot off of that, tell it to resize the partition, go out, see a movie with friends, and by the time you get back, hopefully it's done... I haven't tried any of the open-source Linux tools for that, but that doesn't mean they won't work just as well. As for the kernel images, well, I'm a fan of compiling your own kernel so you don't need any of them, but that isn't for everybody, I know, so yes, you can safely delete the uncompressed versions. And unless you have a multiprocessor machine, the smp kernels aren't doing you any good either. If you delete anything referred to in lilo.conf, make sure to re-run lilo (preferably taking that part out or pointing it somewhere else), or else you probably won't be able to boot. Beyond that, I'm not familiar with Redhat and their packaging system to say what kind of stuff you'd be able to safely delete without interfering with the upgrade process... intuitively, I'd say something non-essential that you're sure is going to be replaced anyway (kde and gnome come to mind), but again, don't listen to me; I don't know what I'm talking about. On Sun, 9 Sep 2001, Bill Mills-Curran wrote: > I tried to upgrade to RedHat 7.1 tonight, and I found that I do not have > enough disk space on /. So I have 3 options: > > 1. Fresh install > 2. Repartition > 3. Clean up > > As much as I'd like to repartition, I'm not sure enough of myself to plow > into that, although I'd like to hear what tricks there might be that would > make it easy (easier?) to do. > > One thing I've noticed is that I seem to have extra kernels around, but I > thought I'd see if there is any reason I need to keep them before I whack > them. Here's what I have: > > ls -l vm* > -rwxr-xr-x 1 root root 1621659 Aug 22 2000 vmlinux-2.2.16-22 > -rwxr-xr-x 1 root root 1739279 Aug 22 2000 vmlinux-2.2.16-22smp > lrwxrwxrwx 1 root root 20 Apr 16 22:51 vmlinuz ->vmlinuz-2.2.16-22smp > -rw-r--r-- 1 root root 627379 Aug 22 2000 vmlinuz-2.2.16-22 > -rw-r--r-- 1 root root 654459 Aug 22 2000 vmlinuz-2.2.16-22smp > > My lilo has: > > cat /etc/lilo.conf > boot=/dev/sda > map=/boot/map > install=/boot/boot.b > prompt > timeout=50 > default=linux > message=/boot/message > linear > > image=/boot/vmlinuz-2.2.16-22smp > label=linux > initrd=/boot/initrd-2.2.16-22smp.img > read-only > root=/dev/sda1 > > image=/boot/vmlinuz-2.2.16-22 > label=linux-up > initrd=/boot/initrd-2.2.16-22.img > read-only > root=/dev/sda1 > > > So, I can get of the uncompressed kernel images, right? > > BTW, when considering my options for repartitioning, I do have a DAT drive > for backup/restore ops. > > Thanks, > Bill > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Sept. 10, 2001