- WLUG - wlug.mailman3.com

RE: [Wlug] Linux top gun

by Brett Russ

> Its a competition > where teams take turns attacking and defending a linux server. This sounds similar to (but not the same as) the Honeynet project challenges: http://project.honeynet.org/misc/chall.html

Dec. 23, 2002

Re: [Wlug] kernel saga continues

by avedis＠rcn.com

Hi Andy, Here's my hardware: 1.2GHz Athlon on a Spacewalker AK12A motherboard ELSA GLoria-L vid card (16MB), which has S3virge chip with Glint 500TX, and uses the 3DLabs driver. At some point last year, I thought I installed XFree 4.1 and got the 3DLabs driver. That's what my notes say. But 3.3.6 was running. If I can install 4.0 from the disks, I'll try it. Every time I've run sax, most of it runs off-screen, and I can't use it. That might be where I screwed up yesterday, by hitting Enter when I shouldn't have. Thanks, Greg On 22 Dec 2002, at 22:34, Andy Stewart wrote: > > HI Greg, > > On SuSE, they supply version 3.3.6 and 4.0.x of XFree86. Most of the time, > you want to run version 4.0, but if you have "vintage" video hardware, you're > better off with version 3.3.6 in my opinion. > > To configure XFree86 on SuSE, you should be running sax (for XFree86 version > 3.3.6) or sax2 (for XFree86 version 4.0). > > If you look at your log (below), you'll note that for some reason, you're > running XFreee86 version 3.3.6. Just what do you have for video hardware? > > I've found on SuSE that you're generally better off if you let YaST do the > "dirty work" for you. > > Later, > > Andy > > > > > On Sunday 22 December 2002 6:36 pm, avedis(a)rcn.com wrote: > > Here's the error message I get when I try to run startx: > > > > XFree86 Version 3.3.6 / X Window System > > (protocol Version 11, revision 0, vendor release 6300) > > Release Date: January 8 2000 > > If the server is older than 6-12 months, or if your card is newer > > than the above date, look for a newer version before reporting > > problems. (see http://www.XFree86.Org/FAQ) > > Operating System: Linux 2.4.4-64GB-SMP i686 [ELF] SuSE > > Configured drivers: > > GLINT: accelerated server for 3DLabs GLINT graphics adapters > > (Patchlevel 0) > > (using VT number 7) > > > > XF86Config: /etc/XF86Config > > (**) stands for supplied, (--) stands for probed/default values > > (--) no ModulePath specified using default: /usr/X11R6/lib/modules > > dbe: Unknown error loading module > > > > Config Error: /etc/XF86Config:48 > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 23, 2002

Re: [Wlug] Linux too much like windows?

by Bill Smith

On Sun, 22 Dec 2002 18:50:09 -0500 Chuck Haines <chaines(a)linux-xtreme.net> wrote: CH> I found this article while reading my daily dose of slashdot. It CH> brings some questions to mind. Is linux becoming too much like CH> windows? in some ways, i agree, but i don't think that it is becoming Bad... Win* operating systems seem to suffer from a disease in which the programs are designed (i use the term loosely. very loosely.) to do as much as possible. Compare this with the *nix approach, where most applications do one thing and do it well. The desktop issue is another problem entirely. I believe that the underlying operating system cannot (nor should it) be blamed for the perception of "Difficult to Use". That responsibility lies with the programmer(s) that writes the applications and the desktop interface. For example, The Gimp seems (to me) very much like Photoshop, which Win* users are familiar with. People that like Photoshop shouldn't have too much trouble with Gimp, but that is not something that one can attribute to the OS. The OS allows stability in the environment... If the interface is well designed, the End User should (theoretically) be able to figure things out for themselves. CH> Does it need to in order to compete in the desktop CH> business? One of my friends was commenting that for servers, linux CH> is the best, however it just loses when it comes to the desktop CH> market. What do you guys think about that? I'm not a gamer and CH> primarily do systems administration work as well as php development CH> and I love my redhat 8.0 with gnome2. What do others out there feel? for some reason, many people think that an OS has to have a lot of games to be a viable desktop system. Linux has a lot of games, but the nature of the OS doesn't lend itself very well (i think) to the variety of systems that Gamers have. Games that are graphic intensive (what isn't these days?!?) like to have the Latest-n-Greatest hardware... 8\ There are all sorts of variables that i don't know anything about, but i think that a lot of lessons can be learned from the way Apple does their interface. whether you like it or not, you can't argue the fact that almost anyone can sit down at a Mac and do things. those same people sit down in front of a system running X and they freak out.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- William Smith wsmith-at-chezsmith-dot-com Fall River, MA http://www.chezsmith.com Random BOFH excuse: We have chosen COBOL as the language of choice. * TAG! v3.1 *

Dec. 23, 2002

Re: [Wlug] kernel saga continues

by Andy Stewart

HI Greg, On SuSE, they supply version 3.3.6 and 4.0.x of XFree86. Most of the time, you want to run version 4.0, but if you have "vintage" video hardware, you're better off with version 3.3.6 in my opinion. To configure XFree86 on SuSE, you should be running sax (for XFree86 version 3.3.6) or sax2 (for XFree86 version 4.0). If you look at your log (below), you'll note that for some reason, you're running XFreee86 version 3.3.6. Just what do you have for video hardware? I've found on SuSE that you're generally better off if you let YaST do the "dirty work" for you. Later, Andy On Sunday 22 December 2002 6:36 pm, avedis(a)rcn.com wrote: > Here's the error message I get when I try to run startx: > > XFree86 Version 3.3.6 / X Window System > (protocol Version 11, revision 0, vendor release 6300) > Release Date: January 8 2000 > If the server is older than 6-12 months, or if your card is newer > than the above date, look for a newer version before reporting > problems. (see http://www.XFree86.Org/FAQ) > Operating System: Linux 2.4.4-64GB-SMP i686 [ELF] SuSE > Configured drivers: > GLINT: accelerated server for 3DLabs GLINT graphics adapters > (Patchlevel 0) > (using VT number 7) > > XF86Config: /etc/XF86Config > (**) stands for supplied, (--) stands for probed/default values > (--) no ModulePath specified using default: /usr/X11R6/lib/modules > dbe: Unknown error loading module > > Config Error: /etc/XF86Config:48 -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Dec. 23, 2002

Linux top gun

by Chuck Haines

I just saw this article and thought to myself, "wouldn't this be something interesting for WLUG and WPILA to put on." Its a competition where teams take turns attacking and defending a linux server. This particular server happens to be running apache, but it could be anything really. I think this would be a neat little event to run. What does everyone else think? The URL for reference is: http://linuxtopgun.org/ -- --------------------------------------------------------- | Chuck Haines | AIM: CyberGrex | | chaines(a)wpi.edu | Yahoo: CyberGrex_27 | | http://www.linux-xtreme.net | ICQ: 3707881 | --------------------------------------------------------- | ECE Sytems Administrator | Box 1531 | | WPILA Lab Manager | 100 Institute Road | | GDC Developer | Worcester, MA 01609 | | Tau Kappa Epsilon Fraternity | | --------------------------------------------------------- GNU Privacy Guard Key Fingerprint E12E 09BE 14B2 4AA4 EA36 27EB 72A4 FDDD 8E3E 741D

Dec. 22, 2002

Linux too much like windows?

by Chuck Haines

I found this article while reading my daily dose of slashdot. It brings some questions to mind. Is linux becoming too much like windows? Does it need to in order to compete in the desktop business? One of my friends was commenting that for servers, linux is the best, however it just loses when it comes to the desktop market. What do you guys think about that? I'm not a gamer and primarily do systems administration work as well as php development and I love my redhat 8.0 with gnome2. What do others out there feel? Just my thoughts, -- --------------------------------------------------------- | Chuck Haines | AIM: CyberGrex | | chaines(a)wpi.edu | Yahoo: CyberGrex_27 | | http://www.linux-xtreme.net | ICQ: 3707881 | --------------------------------------------------------- | ECE Sytems Administrator | Box 1531 | | WPILA Lab Manager | 100 Institute Road | | GDC Developer | Worcester, MA 01609 | | Tau Kappa Epsilon Fraternity | | --------------------------------------------------------- GNU Privacy Guard Key Fingerprint E12E 09BE 14B2 4AA4 EA36 27EB 72A4 FDDD 8E3E 741D

Dec. 22, 2002

Re: [Wlug] kernel saga continues

by avedis＠rcn.com

Here's the error message I get when I try to run startx: XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 8 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.4.4-64GB-SMP i686 [ELF] SuSE Configured drivers: GLINT: accelerated server for 3DLabs GLINT graphics adapters (Patchlevel 0) (using VT number 7) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (--) no ModulePath specified using default: /usr/X11R6/lib/modules dbe: Unknown error loading module Config Error: /etc/XF86Config:48 SubSection "extmod" ^^^^^^^^^^^ Module section keyword expected XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. On 22 Dec 2002, at 12:05, avedis(a)rcn.com wrote: > I managed to get my online connection working again. Just had to > change "ippp0" to "ppp0" in my firewall config file. I was also able > to make a lilo boot floppy from command line, and it worked, exept > for my initial menu. I rebooted back and forth a few times between > the two floppies, and they both seemed to be working, and then > when I went into x-session, I had no mouse. > > WTF??? Why did I lose kernel support for other stuff when all I > messed with was "sound"? > > Then I made the mistake of going into XF86Setup. Now, I can't get > into x at all. > > Questions > 1. Can anyone tell me where the problem is? (other than "user") > > 2. Is there someplace in make xconfig or make menuconfig to > provide support for xfree? At one point, I got an error message > about not being able to load a module when trying to get into x. > > 3. Would it make sense to go back to the distribution disks, > remove and re-insall xfree? > > Thanks. > > Greg > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Dec. 22, 2002

kernel saga continues

by avedis＠rcn.com

I managed to get my online connection working again. Just had to change "ippp0" to "ppp0" in my firewall config file. I was also able to make a lilo boot floppy from command line, and it worked, exept for my initial menu. I rebooted back and forth a few times between the two floppies, and they both seemed to be working, and then when I went into x-session, I had no mouse. WTF??? Why did I lose kernel support for other stuff when all I messed with was "sound"? Then I made the mistake of going into XF86Setup. Now, I can't get into x at all. Questions 1. Can anyone tell me where the problem is? (other than "user") 2. Is there someplace in make xconfig or make menuconfig to provide support for xfree? At one point, I got an error message about not being able to load a module when trying to get into x. 3. Would it make sense to go back to the distribution disks, remove and re-insall xfree? Thanks. Greg

Dec. 22, 2002

kernel - Help!

by avedis＠rcn.com

I'm in windows right now, which is where I automatically boot to if I don't use the floppy. I only get a choice of boots with floppy. Tried recompiling the kernel with sound, added the lbn32(?) line to /etc/lilo and the cylinder error went away, but somehow I lost support for ipchains and lost the suse firewall. Also lost support for vfat. I went back into make xconfig and started messing around with ppp support, vfat and dos support. Got my vfat back ok. Also had to go in and re-edit /etc/rc.config and /etc/rc.config.d/firewall- somethingorother.config. I think I need to review my selections in those files. At first, I could dialup and as soon as it would connect, it would disconnect, and pppd would give error message 4, no support for ppp in kernel. I went back in and selected netfilter with ipchains support, and ppp with async support. Now it will connect and stay connected, but I can't send or receive anything (mail or web). Oh, and I removed the sound support from the kernel, but I'm still getting error messages about trying to load the sound modules. Let me know if I did something obvious. Meanwhile, I'll review what I did. Thanks, Greg

Dec. 22, 2002

Re: [Wlug] "LN" question

by Bill Mills-Curran

On Sat, 21 Dec 2002, Michael LaPointe wrote: > My original site had all of the images in an images directory. To > avoid copying all of the images to each new sub domain/directory I > created an images directory for each sub directory and ran ln *.* > /path/to/sub/images from within the real images directory. > > This worked great but is it only a one shot deal? I.E. if I add > another image to the main directory do I need to run ln again? Michael, What you have created in each directory is an images directory populated with links. As you supposed, each time you add something to the "real" images directory, you have to add links to it everywhere. Here's a more efficient approach. 1) get rid of all these directories of links and 2) in each site directory, make single link to the "real" images directory (not to the images themselves). For example, cd <site_directory> ln -s <path_to_images_directory> images That's it. You won't have to worry about maintaining links to the individual files. Hope this helps. Bill

Dec. 21, 2002