- WLUG - wlug.mailman3.com

delurking to grovel

by Mike Peckar

Hello all, I've been lurking for quite some time now, though i'd pipe up. I've been hosting several very low volume domains through a dedicated dialup starting oh, sheesh, like six years ago via iii.net and using slackware 0.0.9 (am i old or what?). When iii bellied up, I switched to tiac, which was gobbled by psi - now in bankrupcy. suffice it to say that I've seen service levels as low as 95% (two weeks down per year). O.k., sure, I made some sucky choices on my ISP's but what is a guy to do if he's got like four domain names - pay $16.95 per month per domain for hosting? That just bites dead donkey dicks in hell - especially when all the sites combined push less than 1m/day Any suggestions for hosting on the cheap would be greatly appreciated - no dialup required. I have skills I can trade for hosting priviledges - I specialize in enterprise network and systems management (HP OpenView, micromuse, openNMS, UCD SNMP, MRTG, etc). co-location may be even easier - I could just pop my server onto your high-speed acess LAN, reconfig IP addresses, and make it even easier for you - charge me something, but I want to pay for what I serve - not my idiot factor... Peace, Mike the groveler

May 4, 2001

Re: Fwd: Re: [Wlug] Lp0 issues

by Wesley Allen

Go up to 7.2, it's x-configuration has been painless for me on: An HP Pavillion 4450 A Compaq Deskpro 3 old Pentium NOTEBOOKS (All compaq) 1 Custom-built web server 1 HP NetServer (I forget the model) 1 Dell 4800 notebook As you can see, there is great x-support in 7.2, it was really mature, 8.0 is even nicer, but if you're on older hardware don't bother becasue you'll take a HUGE performance hit (KDE 2.1 and Nautilus are memory suckers, maybe with a lightweight window manager you'll be ok though..) Wes ---------- Original Message ---------------------------------- From: gwlt(a)ma.ultranet.com Reply-To: wlug(a)mail.wlug.org Date: Thu, 03 May 2001 15:22:12 GMT >All right, > > Thank you for the assistance all. It has been helpful. > I took Andy & Jeff's lead to check the Kernel and sure enough there is >no such device. >Is my best bet to try to load a newer version? I am less afraid of this >prospect after fighting my way through X problems in 6.0 before going to >7.1. > Any words to the wise before embarking on this adventure? Up until now I >have used off the shelf disks to get the job done. How much more >treacherous is trying to grab stuff on-line? > >COLIN > >> Basic stuff: if you cannot cat a file to /dev/lp0, then you probably >have >> a kernel related problem. That will need to be fixed first. Jeff's >> earlier e-mail explains in brief how to do this. > >> Try something like this: > >> cat/.cshrc > /dev/lp0 > >> OK, once that works, you know that the kernel is OK. > > >_______________________________________________ >Wlug mailing list >Wlug(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug >

May 3, 2001

Fwd: Re: [Wlug] Lp0 issues

by gwlt＠ma.ultranet.com

All right, Thank you for the assistance all. It has been helpful. I took Andy & Jeff's lead to check the Kernel and sure enough there is no such device. Is my best bet to try to load a newer version? I am less afraid of this prospect after fighting my way through X problems in 6.0 before going to 7.1. Any words to the wise before embarking on this adventure? Up until now I have used off the shelf disks to get the job done. How much more treacherous is trying to grab stuff on-line? COLIN > Basic stuff: if you cannot cat a file to /dev/lp0, then you probably have > a kernel related problem. That will need to be fixed first. Jeff's > earlier e-mail explains in brief how to do this. > Try something like this: > cat/.cshrc > /dev/lp0 > OK, once that works, you know that the kernel is OK.

May 3, 2001

Re: [Wlug] Lp0 issues

by Andy Stewart

I have an Epson Stylus Color 870 which works great under Linux, so let me take a stab at helping out here. Basic stuff: if you cannot cat a file to /dev/lp0, then you probably have a kernel related problem. That will need to be fixed first. Jeff's earlier e-mail explains in brief how to do this. Try something like this: cat/.cshrc > /dev/lp0 OK, once that works, you know that the kernel is OK. Now, for the fun part! There are a ton of *great* Epson printer drivers as part of Robert Krawitz's gimp-print package (I know Robert professionally). When tied into the CUPS printing system, you can print anything using those drivers as well as print directly from the GIMP. These drivers are of high quality, although a tad slow occasionally at the higher resolutions. These drivers can be tied into ghostscript, but it is not a task for the faint of heart. I double checked, and Robert's driver code definitely supports the Epson stylus color 660 printer. A previous reply mentioned the Epson 640, which is also supported. FYI, this code also supports printers from Canon, Compaq, HP, Lexmark, and Okidata. To find this software, go to: http://www.sourceforge.net/projects/gimp-print http://www.cups.org I personally like CUPS a whole lot better than lpr or lprng. The web interface alone makes it worthwhile to me. My 2 cents worth, devalued for inflation..... Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org On Wednesday 02 May 2001 10:49, you wrote: > I have been making myself at home in KDE 1.1.2 under Linux 2.2.15-4mdk > and have managed to slowly get most functionality off of the old Windows > half of the dual boot drive. There is one major impediment to moving > over entirely: > I cannot print. > I have an Epson Stylus Color 660, and can not make it work, reconfigure > and test as I try. > If I am not mistaken the system is using a ghostwriter filter that > generically addresses Epson Stylus Color printers (I have tried all > sorts of earlier drivers and generic options within this.) > > When you go to the setup and configuration there is no auto detect of > the printer and type, > You must manually chose it, and when you try any form of a test print > you get: > "Waiting for lp0 to become ready (offline?)" > If you try to test print from RHLinux Print System Manager ASCII > directly you get: > "Couldn't write file "dev/lp0": no such device" > When I try to print from an app. I get: > "lpr: lp: lp: unknown printer" > > If you can spare a few seconds I would be thoroughly grateful for your > thoughts. ---------------------------------------- Content-Type: application/rtf; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: base64 Content-Description: filename="text1.rtf" ----------------------------------------

May 2, 2001

Re: [Wlug] Lp0 issues

by Wesley T Allen

If I remember correctly, I had a problem printing on my Epson 640 on my origional Linux distro (Caldera 2.2). Finally, I went to the caldera help database and they had a printcap file you could manually type in and then my printing worked. For all I know, it may still be there on their database (search for "epson" under their 2.2 version). After I put manually created printcap filter in, it printed fine. You'll get a ton of these, but you may want to switch to a newer distro. If you've got slow hardware, Mandrake 7.0 found my epson right away, and 7.2 has specific drivers for the 6x0 series. YOu may like what you've got, but it's just a thought. Wes On 02 May 2001 14:49:41 +0000, gwlt(a)ma.ultranet.com wrote: > I have been making myself at home in KDE 1.1.2 under Linux 2.2.15-4mdk > and have managed to slowly get most functionality off of the old Windows > half of the dual boot drive. There is one major impediment to moving over > entirely: > I cannot print. > I have an Epson Stylus Color 660, and can not make it work, reconfigure > and test as I try. > If I am not mistaken the system is using a ghostwriter filter that > generically addresses Epson Stylus Color printers (I have tried all sorts > of earlier drivers and generic options within this.) > > When you go to the setup and configuration there is no auto detect of the > printer and type, > You must manually chose it, and when you try any form of a test print you > get: > "Waiting for lp0 to become ready (offline?)" > If you try to test print from RHLinux Print System Manager ASCII directly > you get: > "Couldn't write file "dev/lp0": no such device" > When I try to print from an app. I get: > "lpr: lp: lp: unknown printer" > > If you can spare a few seconds I would be thoroughly grateful for your

May 2, 2001

Re: [Wlug] Lp0 issues

by Jeff Moyer

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ==> Regarding [Wlug] Lp0 issues; gwlt(a)ma.ultranet.com adds: gwlt> I have been making myself at home in KDE 1.1.2 under Linux gwlt> 2.2.15-4mdk and have managed to slowly get most functionality off of gwlt> the old Windows half of the dual boot drive. There is one major gwlt> impediment to moving over entirely: gwlt> I cannot print. I have an Epson Stylus Color 660, and can not make gwlt> it work, reconfigure and test as I try. If I am not mistaken the gwlt> system is using a ghostwriter filter that generically addresses Epson gwlt> Stylus Color printers (I have tried all sorts of earlier drivers and gwlt> generic options within this.) gwlt> When you go to the setup and configuration there is no auto detect of gwlt> the printer and type, You must manually chose it, and when you try gwlt> any form of a test print you get> gwlt> "Waiting for lp0 to become ready (offline?)" If you try to test gwlt> print from RHLinux Print System Manager ASCII directly you get: gwlt> "Couldn't write file "dev/lp0": no such device" When I try to print gwlt> from an app. I get: "lpr: lp: lp: unknown printer" Hmm, perhaps you didn't compile parallel printer support into your kernel? It's listed in make [,menu,x]config under: Character Devices->Parallel printer support Also, you'll probably want to check off Parallel Port support under General Setup. Hope this helps. - -Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/> iEYEARECAAYFAjrwI38ACgkQH/inyh944bQ0iACeJpSgItxSXuqAyNpBNMqDxLXH s04An1yXs/oQ/S6ChOJGGx8pn+NhbGbg =SrTe -----END PGP SIGNATURE-----

May 2, 2001

Lp0 issues

by gwlt＠ma.ultranet.com

I have been making myself at home in KDE 1.1.2 under Linux 2.2.15-4mdk and have managed to slowly get most functionality off of the old Windows half of the dual boot drive. There is one major impediment to moving over entirely: I cannot print. I have an Epson Stylus Color 660, and can not make it work, reconfigure and test as I try. If I am not mistaken the system is using a ghostwriter filter that generically addresses Epson Stylus Color printers (I have tried all sorts of earlier drivers and generic options within this.) When you go to the setup and configuration there is no auto detect of the printer and type, You must manually chose it, and when you try any form of a test print you get: "Waiting for lp0 to become ready (offline?)" If you try to test print from RHLinux Print System Manager ASCII directly you get: "Couldn't write file "dev/lp0": no such device" When I try to print from an app. I get: "lpr: lp: lp: unknown printer" If you can spare a few seconds I would be thoroughly grateful for your thoughts.

May 2, 2001

RE: [Wlug] SCSI HD Boot Failure! BLA!

by Keller, Tim

That'll probably be really tough, since it won't even boot for the first time... What you could try is using a boot diskette to get the machine up and running, then compile a custom kernel that has support for the scsi card compiled in (not as a module) The kernel that the installer uses has -everything- compiled in so it'll work on a maximum number of systems, however, the kernel it installs on your machine does not. Hope that helps! Tim Keller -----Original Message----- From: Ben Dow [mailto:bdow@WPI.EDU] Sent: Saturday, April 28, 2001 5:30 AM To: wlug(a)mail.wlug.org Subject: Re: [Wlug] SCSI HD Boot Failure! BLA! Try compiling scsi support into your kernel, or using a different precompiled kernel if you're not into compiling your own. You probably had scsi support in the installation kernel but not the one it installs to boot from by default. On Sat, 28 Apr 2001, Sands Fish wrote: > Hello again all, > I've just recently started putting together a Mandrake 8.0 box. (About > 3 hours ago, yes in the middle of the night.) For a hard drive, I have an > IBM SCSI Drive on an Adaptec 2940-U2 card. When I ran the install, it found > the card and the drive automagically. I was impressed and happy. Went > through the installation fine, copied all the files. But as soon as I > rebooted to run it for the first time, I get the LILO graphical screen, I > choose one of the options (any), and get the following error... > > request_module[block-major-8]: Root fs not mounted > VFS: Cannot open root device "801" or 08:01 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 08:01 > > Just some more information. The HD is on SCSI ID #6. The controller is on > #7. The SCSI BIOS sees the drive because I can see it report it on boot. > When I watch the boot messages fly by for Linux, I see no reference to any > sd# devices at all. > > I'm really completely lost here. Would changing the SCSI ID # help? That > doesn't seem to be likely. Any suggestions would be greatly appreciated. > Thanx a lot guys/grrls!! > > - - s a n d s - - > SandsFish(a)ArtKillsYuppieBabies.com > _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

April 30, 2001

Re: [Wlug] ipchains flush

by Jeff Wiedemeier

> Rusty's Three-Line Guide to Masquerading (IPCHAINS How-To) , each > modified to start with "ipchains -F" which should flush all existing > rules, that the flush isn't happening. You need to flush each chain separately. So.. ipchains -F input ipchains -F output ipchains -F forward will do what you want. /jeff

April 28, 2001

Re: [Wlug] Ximian Gnome on Debian

by Aaron Haviland

Something I forgot to mention... I haven't actually tested these. I will by tomorrow, though. I've elected to download to a machine elsewhere and burn to a CD instead of waiting for my 56k modem to crunch through them. However, I'm fairly sure I've fixed most of the dependancy problems that I noticed. gnucash from debian proper and gnome-games conflict because of differences in libguile out of all those packages installed, none depend on libgdk-pixbuf-gnome2, yet gnome-session should. Others probably should as well, but I hadn't gotten that far. I don't know if ximian plans a fix for gnucash. Terry Yelmene said: > Thanks Orion... This is the configuration I wanted to upgrade to. This > helps! > tyelmene > tyelmene(a)3c3art.com > > ----- Original Message ----- > From: "Orion" <orion(a)tribble.dyndns.org> > To: "WLUG" <wlug(a)mail.wlug.org> > Sent: Saturday, April 28, 2001 5:03 PM > Subject: [Wlug] Ximian Gnome on Debian > > > > Just in case anyone here uses Debian and is thinking of installing > > Ximian1.4, the directions that say to apt-get install task-helix-gnome > > are wrong. I've gone and made some task packages based on what > > helix/ximian used to have for its previous release. Just add this to > > your sources.list and you can use them: > > > > deb http://zork.net/~orion potato main > > > > (or s/potato/unstable/ of you prefer) > > > > also, if you need a deb-src line for ximian, until they fix it (IF they > > fix it) you need to use this instead of what they say: > > > > deb-src http://red-carpet.ximian.com/debian/ dists/potato/main/sources/ > > > > (again, s/potato/woody/ if you wish) -- Orion orion [at] tribble [dot] dyndns [dot] org "You build a time machine that automatically, when it's about to be destroyed, etc, goes back and makes sure that absolutely everything that happened ever did actually happen that way." - Colin

April 28, 2001