One of the reasons I switched from RH9 back to RH8.0 was the printer sharing. I have oodles of printers on oodles of systems, and I've tried CUPS sharing, Samba sharing, different printer drivers and connections, and bunches of other stuff. I didn't post anything on bugzilla 'cause at the time I was having several other problems and forgot about it until now. Plus, I really couldn't find any reason to the rhyme except that it worked in Psyche and not in Shrike. There have been a number of package updates since my last attempt, but the symptoms you're describing are the same as what I got, so if you have stayed up2date, then I would guess a fix to this probably rare problem hasn't been implemented. RH9 also gave me a problem on my HP LaserJet 4. After a few minutes, the printer would report some error (I think it was an I/O error, but I can't remember). I'm curious, what kind of system are you running? The only similarity among all the systems here which didn't print is that they use Athlon chips and Jetway (VIA chipset) motherboards. One system had an Athlon T-Bird 1.2, ATI AIW 128, Jetway 692(?) mommybored, Turtle Beach Tropez+, and stock Shrike install. The printers used on that system were HP LaserJet 4 and HP DeskJet 842c. Other systems here didn't share any of a good supply of printers, but those two are the ones I tried first on each system. Other systems used a few Athlon XP 1700+ chips on Jetway J867 boards, and one had a 1.0 TBird (which doesn't like RH 9 at all). Sometimes I did "Everything" installs, sometimes I did the default installation, and sometimes I simply added everything (without clicking "Everything"). By the way, when I used RH8.0 to print, it just worked, with CUPS or lpd..or both. I assume Red Hat would not be upset with me mentioning J.A.M.D., since it's really just Red Hat 9 with a few modifications, as opposed to a lot of other RH-based distros who try to reinvent the whole OS a piece at a time. I figure that those who want to know about J.A.M.D. will still buy RHCE classses. :-) (Seems like a good argument for profitable GPL software.) As a Linux junkie, I made my way down the list at DistroWatch and arrived at J.A.M.D. I tried it on my own system, and it didn't get into X. It didn't even timeout, so I couldn't diagnose the problem. (I think it was an attempt to install nVidia drivers.) I figured it was because the OS was still an infant at version 0.0.6, but every other system I tried it on was surprisingly happy. J.A.M.D. is not really a server distribution, but one thing I like about it is that if you have something you want to install from RH9, you just run the RPM from the RH9 CD and everything works. J.A.M.D. is a small distro at only 1 CD. (Wow, by that reasoning, Windows XP is a small distro.) Anyway, J.A.M.D. comes with the same version of Samba that Shrike comes with and I think the same CUPS. In fact, versionwise everything seems to be about the same. However, printer sharing worked, my Belkin USB dongle didn't crash the network configuration tools, Kopete worked right, and programs even started faster. The point is that it's probably something inside RH9, at least when it comes to my own printer sharing problem. It seems to me that the solution must be some simple undocumented package conflict. Is there any chance that it's Shrike's NPTL backport? I'm really quite ignorant on NPTL, but isn't it a patch to the 2.4.20 cleverly made to work? In other words, is it really part of the stock 2.4.20 kernel? Could it have something to do with all the bugs I've experienced or even with the old Athlon chips not working right? By the way, since mailman likes to misplace my messages, won't turn off digests, and sometimes sends digests when they're obsolete, I'm gonna quit hanging around. It's getting hard to follow, and I'm sure it's frustrating to see new top-level messages with "Re:" at the beginning. I hope mailman soon gets replaced with a bulletin board, something UBB-like. Vector's BB is pretty good. I understand they had a catastrophic data loss on their previous BB, so I don't know what they were using before, but now they're using phpBB. One thing I like about it is the semi-transparent email-notices about messages posted. If you stop clicking the link in the email, they stop sending them to you. I understand some people are email-only, but I don't see why mailman can't be expanded a little with a web-based email interface built in. See ya. I can still be reached at benjaminvanderjagt@xxxxxxxxxxxx (one final plug, visit my SourceForge project DLIP! The specs are up to version 0.03. http://sourceforge.net/projects/dlip or http://dlip.sourceforge.net/ for details. You can still find me (vanderjagt) on the Vector and J.A.M.D. BBs.
