John Totten <john@totten.com> wrote:

...

Anyone interested in Linux telephony?

Absolutly, especailly for Central Office, VoIP/PSTN Integration, and VoIP Virtual PBX. Check out owner-jtapi-interest@capra.Eng.Sun.COM

Of course.....:)

W.D.McKinney (Dee) deem@wdm.com Faith is acting on your passions & beliefs.

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hi, On Thu, 26 Nov 1998, Eric Lee Green wrote: [SNIP]

Part 3: Questions.

1) What about PAM? I tried loading the "ssh" rpm from www.replay.com and it would not work. So I recompiled "ssh" from the tarball. What does SuSE use instead of PAM? Or is PAM (Pluggable Authentication Modules) there, but just not visible?

No, there's no PAM in SuSE Linux. You could have downloaded the right ssh-RPMs from ftp.gwdg.de, for example...

2) How come there's so many boot disks?! Just curious, because Red Hat somehow gets by with only one. Shades of Slackware!

What's wrong with that? You only need one of them. But there are some hardware constellations, which require a special setup, that's the reason for having different disks.

3) How can I make apsfilter quit #$%@#@ duplexing my text?! I can't READ text that tiny! I want my text files to come out looking like normal text, not sideways and in teensy letters.

Have a look in /etc/apsfilterrc about this, the Variable is called "FEATURE".

4) How can I make mail from "eric@england.local.net" be re-written as being mail from "el_green@bellsouth.net"? ("local.net" is my home network and "bellsouth.net" is my ISP).

Not sure about this one, but I think you have to put this in the Variable FROM_HEADER in /etc/rc.config. Bye, LenZ ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Some additional comments: I continue to be impressed by the number of packages shipped with SuSE Linux. There are packages there that I did not know even existed, to solve problems that I had thought required using Windows 95 or Windows 98. My initial impression: SuSE Linux is a good platform for the Linux enthusiast. However, I am seeing a lack of enterprise-ready features, or maybe just not seeing them. For example, PAM is important because it allows using a centralized authentication mechanism such as RADIUS or Kerberos without modifications to end-user programs. Similarly, keeping runlevel configuration scripts in /etc/rc.d rather than in /sbin/init.d helps with setting up a corporate-wide backup policy (yes, they're scripts, but no, they're more configuration files than executables). Similarly, being able to add stuff to the daily crontabs cross-network with no scripting simply by dumping a script into the directory /etc/cron.daily etc. like I did with Red Hat 4.2 across a WAN of 250 machines scattered across a 5000 square mile area is the kind of enterprise-class solution that I need. Don't get me wrong, I'm enjoying SuSE Linux. However, I would not deploy it in my enterprise from what I see so far. More as I keep digging. I am currently downloading the updates from ftp.suse.com. One problem I have is with the way the updates directory is laid out. I cannot just glance at one directory and see if anything new has come in since the last time I looked. Rather, I must dig through a whole heirarchy of directories. In addition, there does not seem to be a common naming scheme. Some rpms have their version number as part of their name, which is nice because I can do a "rpm -q" on my local system and see if I need them. Others do not, and I have no choice but to download them because I don't know if they are a later version than what is on my system. On Thu, 26 Nov 1998, Lenz Grimmer wrote:

No, there's no PAM in SuSE Linux. You could have downloaded the right ssh-RPMs from ftp.gwdg.de, for example...

Is there a security archive for SuSE Linux the way that ftp.replay.com serves as a security archive for Red Hat Linux? -- Eric Lee Green eric@linux-hw.com <A HREF="http://www.linux-hw.com/~eric"><A HREF="http://www.linux-hw.com/~eric</A">http://www.linux-hw.com/~eric</A</A>> "Linux represents a best-of-breed UNIX, that is trusted in mission critical applications..." -- internal Microsoft memo - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Well, 4 days have passed, and here's what the conclusion is: SuSE 5.3 is one heckuva general-purpose workstation. I recommend it unhesitantly to the individual user who wants to use Linux. I still recommend Red Hat for server applications because it's so much easier to install and maintain, but SuSE is definitely superior as a general-purpose workstation. Much of the value is in the 5-CD set -- there is software there to do almost anything that can be done with Linux, all easily accessed via "yast". No more digging through FTP sites all over the world to find that One Perfect Application to do what you need to do -- it's all there, ready and waiting, and "yast" makes it easy to find and install it. Best of all, "yast" even manages the dependencies for you. Shades of "dselect"! (Now all you need to add is the auto-update feature of "dselect", where you can point it at your FTP archive, and it'll automatically flag all the new packages for update for you, for update and installation with a single keystroke). A little more attention to enterprise-scale features, and I'd unhesitantly recommend it for large-scale deployments. Here's some things that need to be considered for enterprise-scale deployments: 1) Routine maintenance tasks need to be distributable across the network without editing script files. Red Hat's /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly are such a means of doing this. I can use "rdist" or equivalent and zap out a script to all of my sites to do a weekly database cleanup or etc. without disturbing any other scheduled events or editing any files. Similarly, /etc/profile.d provides an easy way to drop in a script to be done at login without disturbing the contents of /etc/profile or the contents of any other login script. 2) Same with authentication information. PAM is a must for centralized authentication in the Microsoft-centric environments here in the United States. Recompiling applications every time Microsoft changes their authentication methods is *NOT* an option. When Microsoft added encrypted authentication to their SMB networking protocol, for example, a PAM module was swiftly written to interface with the fix that the Samba team added to their suite. Thus the NT networking and Linux logins can both use the same authentication database, rather than have two different sets of authentication tokens. Not a single end-user application had to be altered to make this change. 3) An effort must be made to segregate configuration and user information from the rest of the system so that a coherent backup strategy can be formulated. For example, under Red Hat Linux I know that if I back up /etc, /usr/local, and /home I can restore my entire system configuration by reinstalling the system, reinstalling my applications such as applix, then restoring the contents of those three directories. There is no configuration information that lives elsewhere on the system. Even the "X" server link is is set in the /etc/X11 directory so that when I restore my /etc directory, it restores ALL of my configuration info, even the configuration info that denotes where my "X" server lives. The fact that some of this configuration info is in the form of shell scripts or links to executables still does not make it belong somewhere else on the filesystem -- for an enterprise-scale deployment, I cannot go hunting down things stashed in odd corners of the system. That way lies lunacy. Lest you think these are just minor quibbles: they are *NOT* minor quibbles when you are trying to maintain 250 systems scattered across a 10,000 square mile area in less than 2 hours a day of available time. I have managed enterprise-scale deployments. "minor" things like this swiftly become major when the number of systems involved passes 100. Many of these features were added to Red Hat 4.0 as the result of feedback from people like me, people who were managing large-scale deployments of Red Hat 3.0.3 and who had to add these kinds of things by hand over time in order to make our jobs reasonable. The time for thinking of Linux as an individual user's platform is over. It is now time to think of wide-spread deployment in the corporate environment. Without attention to enterprise-scale features it does not matter how good a workstation SuSE produces -- it won't be deployed in the numbers that it deserves. I hope that SuSE asks for feedback from others who are involved or who have been involved in the past with corporate-wide deployments of Linux, because I know that you can probably come up with some stuff that'll blow Red Hat in the weeds there. But it won't happen without someone making it their job to make it happen. In the meantime: I am unhesitantly recommending SuSE Linux to our customers who are buying Linux machines for personal use. I'd like to see it get to the point where we could sell a couple hundred copies to someone deploying on a corporate-wide basis too. -- Eric Lee Green eric@linux-hw.com <A HREF="http://www.linux-hw.com/~eric"><A HREF="http://www.linux-hw.com/~eric</A">http://www.linux-hw.com/~eric</A</A>> "Linux represents a best-of-breed UNIX, that is trusted in mission critical applications..." -- internal Microsoft memo - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

On Sun, 29 Nov 1998, Juergen Braukmann wrote:

Eric Lee Green wrote:

...

A little more attention to enterprise-scale features, and I'd unhesitantly recommend it for large-scale deployments. Here's some things that need to be considered for enterprise-scale deployments: 1) Routine maintenance tasks need to be distributable across the network without editing script files. Red Hat's /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly are such a means of doing this. I can use "rdist" or equivalent and zap out

is this a problem?? you *can* alter / create entries in /etc/crontab

Across 1,000 machines, each of which may also have local crontab alterations? As you state, it is not a problem of individual deployments. However, for enterprise-wide deployments, it *IS* a problem. All Red Hat did was add a script that'll execute all the scripts in a directory, add this to /etc/crontab, and voila. Now I can send out something to happen on a daily basis (e.g., I have a particular application where I want the application's password to change on a daily basis, due to security reasons) without bothering the contents of any file on the system. It's like Sys V Init. It allows you to do for cron-scheduled tasks what Sys V Init does for startup tasks -- i.e., change the configuration without messing with any other part of the configuration.

...

3) An effort must be made to segregate configuration and user information from the rest of the system so that a coherent backup strategy can be formulated. For example, under Red Hat Linux I know that if I back up /etc, /usr/local, and /home I can restore my entire system configuration by reinstalling the system, reinstalling my applications such as applix, then restoring the contents of those

As far as I remember, a few things were changed due to "standardisation", like the move from /etc/init.d to /sbin/init.d. So,

I read the LHS different from what SuSE reads it. No matter. /sbin/init.d can live in /sbin, but the configuration information (the links to the individual scripts in /sbin/init.d) needs to live under the /etc directory because /etc is where the LHS says configuration info needs to live. Same thing with the link to the "X" server. That is *CONFIGURATION* information, buster -- and belongs under /etc. When I save and restore /etc, I want *ALL* of my configuration info to be saved and restored, not just the particular configuration info that happens to live under /etc. Again, this is not much of an issue under individual deployments... but for large-scale deployments it is DEFINITELY an issue, because it allows me to have a reasonable backup policy. For example, I developed an automated backup system that backed up /database and /home daily, /etc weekly and /usr/local monthly from all the Linux servers on my WAN to a centralized backup server that had a 40gb DLT on it. This happened at 1am in the morning, every night, as a scheduled task. There is *NO WAY* that I could backup the ENTIRE contents of these servers on a regular basis, even this little bit, being transmitted as a compressed tarball, takes up the entire bandwidth of the WAN for several hours. Not to mention that even a 40gb DLT has a finite capacity! A machine went down, we re-installed Linux on it, we re-installed the database software and /etc and /usr/local and /home and /database, and the machine was back up and running. *THAT* is the kind of reassurance I need -- that I can restore a machine from scratch and know that I'm not going to be bit by some kind of configuration information living somewhere else on the system that I did not have backed up over the WAN. And no, we can *NOT* depend on branch sites performing regular backups! (They were supposed to, but they never did, and unfortunately there's nothing that the IT department can do to force them to do so).

if we are talking about that, we have to keep in mind that there are standards set in unix world that should be reached (by all unices).

I don't care about standards. I care about getting the job done. Standards are supposed to help in that. If parts of a standard hinder that, then it is the standard that is wrong, not me.

...

Lest you think these are just minor quibbles: they are *NOT* minor quibbles when you are trying to maintain 250 systems scattered across a 10,000 square mile area in less than 2 hours a day of available time. I have managed enterprise-scale deployments. "minor" things like this swiftly become major when the number of systems involved passes 100. Many of these features were added to Red Hat 4.0 as the result of feedback from people like me, people who were managing

yes, that's true. try that with the "other" OS. ;-)

You're joking, right? :-).

...

asks for feedback from others who are involved or who have been involved in the past with corporate-wide deployments of Linux, because I know that you can probably come up with some stuff that'll blow Red Hat in the weeds there. But it won't happen without someone making it their

should this *realy* be a prime goal??

Blowing Red Hat into the weeds should not be a prime goal. Improving the product should be. Enterprise-scale managability issues need to be addressed no matter what other Linux distributions do. I mention Red Hat merely because this is one area where they have done their homework (as you would suspect, given that Red Hat's technical lead is an old system administrator, not a hacker). -- Eric Lee Green eric@linux-hw.com <A HREF="http://www.linux-hw.com/~eric"><A HREF="http://www.linux-hw.com/~eric</A">http://www.linux-hw.com/~eric</A</A>> "Linux represents a best-of-breed UNIX, that is trusted in mission critical applications..." -- internal Microsoft memo - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hi: Great message. I hope SuSE listens and takes this to heart. Also, I really enjoyed looking over your "The Computer Builder" site (<A HREF="http://www.linux-hw.com/config/"><A HREF="http://www.linux-hw.com/config/</A">http://www.linux-hw.com/config/</A</A>>) Regards and happy holidays, Bill Parker

-----Original Message----- From: owner-suse-linux-e@suse.com [<A HREF="mailto:owner-suse-linux-e@suse.com]On">mailto:owner-suse-linux-e@suse.com]On</A> Behalf Of Eric Lee Green Sent: Saturday, November 28, 1998 11:57 PM To: suse-linux-e@suse.com Subject: [SuSE Linux] Day 4: Wrapup

Well, 4 days have passed, and here's what the conclusion is:

SuSE 5.3 is one heckuva general-purpose workstation.

I recommend it unhesitantly to the individual user who wants to use Linux. I still recommend Red Hat for server applications because it's so much easier to install and maintain, but SuSE is definitely superior as a general-purpose workstation. Much of the value is in the 5-CD set -- there is software there to do almost anything that can be done with Linux, all easily accessed via "yast". No more digging through FTP sites all over the world to find that One Perfect Application to do what you need to do -- it's all there, ready and waiting, and "yast" makes it easy to find and install it. Best of all, "yast" even manages the dependencies for you. Shades of "dselect"! (Now all you need to add is the auto-update feature of "dselect", where you can point it at your FTP archive, and it'll automatically flag all the new packages for update for you, for update and installation with a single keystroke). A little more attention to enterprise-scale features, and I'd unhesitantly recommend it for large-scale deployments. Here's some things that need to be considered for enterprise-scale deployments: 1) Routine maintenance tasks need to be distributable across the network without editing script files. Red Hat's /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly are such a means of doing this. I can use "rdist" or equivalent and zap out a script to all of my sites to do a weekly database cleanup or etc. without disturbing any other scheduled events or editing any files. Similarly, /etc/profile.d provides an easy way to drop in a script to be done at login without disturbing the contents of /etc/profile or the contents of any other login script. 2) Same with authentication information. PAM is a must for centralized authentication in the Microsoft-centric environments here in the United States. Recompiling applications every time Microsoft changes their authentication methods is *NOT* an option. When Microsoft added encrypted authentication to their SMB networking protocol, for example, a PAM module was swiftly written to interface with the fix that the Samba team added to their suite. Thus the NT networking and Linux logins can both use the same authentication database, rather than have two different sets of authentication tokens. Not a single end-user application had to be altered to make this change. 3) An effort must be made to segregate configuration and user information from the rest of the system so that a coherent backup strategy can be formulated. For example, under Red Hat Linux I know that if I back up /etc, /usr/local, and /home I can restore my entire system configuration by reinstalling the system, reinstalling my applications such as applix, then restoring the contents of those three directories. There is no configuration information that lives elsewhere on the system. Even the "X" server link is is set in the /etc/X11 directory so that when I restore my /etc directory, it restores ALL of my configuration info, even the configuration info that denotes where my "X" server lives. The fact that some of this configuration info is in the form of shell scripts or links to executables still does not make it belong somewhere else on the filesystem -- for an enterprise-scale deployment, I cannot go hunting down things stashed in odd corners of the system. That way lies lunacy.

Lest you think these are just minor quibbles: they are *NOT* minor quibbles when you are trying to maintain 250 systems scattered across a 10,000 square mile area in less than 2 hours a day of available time. I have managed enterprise-scale deployments. "minor" things like this swiftly become major when the number of systems involved passes 100. Many of these features were added to Red Hat 4.0 as the result of feedback from people like me, people who were managing large-scale deployments of Red Hat 3.0.3 and who had to add these kinds of things by hand over time in order to make our jobs reasonable. The time for thinking of Linux as an individual user's platform is over. It is now time to think of wide-spread deployment in the corporate environment. Without attention to enterprise-scale features it does not matter how good a workstation SuSE produces -- it won't be deployed in the numbers that it deserves. I hope that SuSE asks for feedback from others who are involved or who have been involved in the past with corporate-wide deployments of Linux, because I know that you can probably come up with some stuff that'll blow Red Hat in the weeds there. But it won't happen without someone making it their job to make it happen.

In the meantime: I am unhesitantly recommending SuSE Linux to our customers who are buying Linux machines for personal use. I'd like to see it get to the point where we could sell a couple hundred copies to someone deploying on a corporate-wide basis too.

-- Eric Lee Green eric@linux-hw.com <A HREF="http://www.linux-hw.com/~eric"><A HREF="http://www.linux-hw.com/~eric</A">http://www.linux-hw.com/~eric</A</A>> "Linux represents a best-of-breed UNIX, that is trusted in mission critical applications..." -- internal Microsoft memo

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hi, On Thu, Nov 26, 1998 at 01:07 -0500, Eric Lee Green wrote:

4) How can I make mail from "eric@england.local.net" be re-written as being mail from "el_green@bellsouth.net"? ("local.net" is my home network and "bellsouth.net" is my ISP).

Add the following line to /etc/mail/genericstable eric@england.local.net el_green@bellsouth.net and do a /usr/sbin/makemap hash -f genericstable.db < genericstable then restart sendmail with /sbin/init.d/sendmail stop /sbin/init.d/sendmail start Of course this will only work if you're using sendmail. Ciao, Stefan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Thus spake Miguel Rabi IMARPE (mrabi@imarpe.gob.pe):

Dear Susers:

I'm on Suse 5.2 (Kernel 2.0.34) and KDE 1.0, I've installed Zircon an IRC client from the Suse 5.2 and 5.3 rpms cds but when I try to excecute it an tcl/tk label apears indicating that my tcl libraries have not support for networking.

Where is the problem? I have other tcl/tk applications like xftp and others running perfectly on the internet.

I have installed the new tk, tcl and tix...

Do you now some other irc client, especially for KDE, and better if it is a rpm... I will be very thankfull

Thanks

I just compiled kvirc which is pretty cool. I have not been able to compile kirc whatsoever. I still like use tkirc which seems to have all the functionality I could want. Have you checked out cIRCus or whatever? I dont know about rpms but everything for me besides kirc compiled cleanly. I upgraded to the Qlib 1.41 in an attempt to get some programs compiling like korg but I have not been successful. kvirc has a pretty nice interface. I had the same problem with zircon on SuSE 5.2. I also had some general stability problems and had zircon close me out a few times while idling along on undernet. Take care. -- Michael Perry mperry@basin.com ------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

"Christopher A. Martin" wrote:

I recently installed the realvideo/audio 5.0 .rpm using xrpm. Everything seemed to go fine. However, when I try to run "rvplayer" I get "Segmentation fault". What do I do. . .help

I havn't used the rpm version but I did get the version to work that comes off of the Realaudio website. It gives step by step instruction on how to install. I don't even bother with rpm's anymore unless they were made by SuSe. The Redhat rpms just don't work on anything except Redhat. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Miguel Rabi IMARPE wrote:

...

Dear Susers:

I'm on Suse 5.2 (Kernel 2.0.34) and KDE 1.0, I've installed Zircon an IRC client from the Suse 5.2 and 5.3 rpms cds but when I try to excecute it an tcl/tk label apears indicating that my tcl libraries have not support for networking.

Where is the problem? I have other tcl/tk applications like xftp and others running perfectly on the internet.

I have installed the new tk, tcl and tix...

Do you now some other irc client, especially for KDE, and better if it is a rpm... I will be very thankfull

Thanks

Miguel Rabi Lima Peru <A HREF="http://www.imarpe.gob.pe"><A HREF="http://www.imarpe.gob.pe</A">http://www.imarpe.gob.pe</A</A>>

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hello!

I prefer kvirc - you can find it on <A HREF="http://www.kvirc.org"><A HREF="http://www.kvirc.org</A">http://www.kvirc.org</A</A>> - it is a lot better (my opinion) than zircon - couse it supports scripting.

1) I had the same problems with zircon - but never tried to figure it out. 2) I've had great success with tkirc. The fact that it uses TCL scripting is a plus for me since I also do eggdrop scripting. 3) tkirc is not specifically a KDE app - but it works fine with it. Since I don't have a great need to dump text file onto a channel I can't really think of any benefits of being fully KDE integrated. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

I have a friend and his wife who are new to computers and would like to start them on the right path with Linux. Can anybody help? Juanito - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

John Minyard wrote:

I have a friend and his wife who are new to computers and would like to start them on the right path with Linux. Can anybody help?

Juanito

It will be tough to learn computers from scratch starting with Linux. Most Linux users have some dos and windows experience, so they have an idea of what all the commands do, what the parts of the machine are, etc. Even then you get lost, look at all the questions in this mailing list. You could set Linux up for them, so they could get on the internet with Netscape, email, ftp, etc. Many people only need this. Then at least they would have a functioning system. They could learn more as they need. But it is hard to learn software such as Gimp if you don't know the difference between a gif, jpg, or avi. Or what the difference between a file and a directory is. If you do go with linux, be sure to learn Midnight Commander. Just type "mc" at the command line. It allows new leaners to see where the files are, and edit them and view them easily. I hate to say it, but if your friends just want to do things like email, web surfing, and printing out t-shirts on their cheap inkjet printer, then they are probably better off with Windows. At least use NT. ;-) Printing on cheap printers is one area where Windows is better than linux. You should get them an introductory level book such as the "Dr. Bob's No Nonsense Guide to Linux", or "Linux for Dummies". You need books when you learn Windows, and Linux is no different. Go to www.linuxmall.com www.cheapbytes.com and other sites to find cheap books and cdroms. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

zentara wrote:

John Minyard wrote:

...

I have a friend and his wife who are new to computers and would like to start them on the right path with Linux. Can anybody help?

Juanito

It will be tough to learn computers from scratch starting with Linux. Most Linux users have some dos and windows experience, so they have an idea of what all the commands do, what the parts of the machine are, etc. Even then you get lost, look at all the questions in this mailing list.

You could set Linux up for them, so they could get on the internet with Netscape, email, ftp, etc. Many people only need this. Then at least they would have a functioning system. They could learn more as they need. But it is hard to learn software such as Gimp if you don't know the difference between a gif, jpg, or avi. Or what the difference between a file and a directory is. If you do go with linux, be sure to learn Midnight Commander. Just type "mc" at the command line. It allows new leaners to see where the files are, and edit them and view them easily.

I hate to say it, but if your friends just want to do things like email, web surfing, and printing out t-shirts on their cheap inkjet printer, then they are probably better off with Windows. At least use NT. ;-) Printing on cheap printers is one area where Windows is better than linux.

You should get them an introductory level book such as the "Dr. Bob's No Nonsense Guide to Linux", or "Linux for Dummies".

You need books when you learn Windows, and Linux is no different.

Go to www.linuxmall.com www.cheapbytes.com and other sites to find cheap books and cdroms. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

I can agree with you to a certain extent, but I'm in Austin, tx and they are in Norfolk, Va. His wife is the one who wants to start learning about computers and my thought was to find a Lug to get her attached to. This way, she would not be brainwashed by Windoze, even though she will use it. BTW, she is Russian. Juanito - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Just installed zircon myself, same error. Not that much of a biggie though as I tend to use ircii myself, second preference is bitchx, lowest preference is zircon... Weird one though, will have to check it out further as to *WHY* it's complaining too... Anyone have ideas?

Dear Susers:

I'm on Suse 5.2 (Kernel 2.0.34) and KDE 1.0, I've installed Zircon an IRC client from the Suse 5.2 and 5.3 rpms cds but when I try to excecute it an tcl/tk label apears indicating that my tcl libraries have not support for networking.

Where is the problem? I have other tcl/tk applications like xftp and others running perfectly on the internet.

I have installed the new tk, tcl and tix...

Do you now some other irc client, especially for KDE, and better if it is a rpm... I will be very thankfull

Thanks

Miguel Rabi Lima Peru <A HREF="http://www.imarpe.gob.pe"><A HREF="http://www.imarpe.gob.pe</A">http://www.imarpe.gob.pe</A</A>>

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e