Crashdamage

Just go here: http://easyurpmi.zarb.org/ And all will become clear to you...

In a terminal, type "rpm -ql j2re" (no qoutes). If it really is installed, that will list all the files the Java package installed and their locations.

Java 1.2? That's pretty old. What are you using - Mandrake 7? Anyway...go to: https://jsecom16.sun.com/ECom/EComActionSer...35383A99D0FED5B Middle of the page "Linux Platform" click on download "RPM in self-extracting file (j2re-1_4_2_06-linux-i586-rpm.bin". Note where you save the rpm. Then go to: http://java.sun.com/j2se/1.4.2/jre/install-linux.html and follow the directions. It's pretty easy. Java 1.5 is out now, but there are rumblings of problems with compatibility problems with some apps. This stuff has been covered in previous posts on this board. Do a search if you want to check out those posts.

Just a reminder for any n00bs reading this - logging in to a GUI (desktop) as root is a Very Bad Idea. It should *not* be done, nor should it *ever* be necessary. Coming from the WinWorld, it took me a while working with Linux to get used to that concept. Resist the urge, learn how to use 'su' properly from a terminal.

Oops...my bad...

Can't help you with the old info by Tom Berger. But really this thread should have enough info to get you started. Install fetchmail, procmail, spamassassin and a virus checker (if you want it) on your server. Then read through this thread again, look at the sample .fetchmail and .procmailrc code I posted, and of course check out 'man fetchmail' and 'man procmail'. Take a little time to grok the basics of setting up your ~./spamassasin/user_prefs. For your purposes I'd probably just let fetchmail run in daemon mode and auto-fetch every few minutes. And like I said before, you'll need to add some entries in .procmailrc to specify delivery to your particular mailboxes. If you want to have procmail deposit mail in mailboxes on the local workstations, of course you will need to allow the server access to those and the workstations have to be running. I'd probably have procmail leave mail in mboxes on the server and have the mail clients access those - directly, not with pop3 - but however you want to do it, depending on your needs. Losta possibilties. Paul or someone else can probably help you more with setup of virus checking. I don't bother with it on incoming mail with Linux. Linux is immune, ya know. Virus checking at the mail server is mostly for corporate stuff. As for outgoing, I doubt I'd ever send a virus on outgoing mail, and as far as I'm concerned Winidiots are on their own anyway. My Win boxes have virus software on 'em to do virus protection locally 'cause after all, email isn't the only way to get infected. None of this is really all that hard, ya just gotta go for it. If I-who-knows-nothing can do it, you certainly can. The link I gave for Prof Timo's Procmail Tips & Recipies is very good. Here it is again, and some other links I like for this stuff: http://www.uwasa.fi/~ts/info/proctips.html http://userpages.umbc.edu/~ian/procmail.html http://linux.cudeso.be/linuxdoc/fetchmail.php http://www.troubleshooters.com/lpm/200402/200402.htm Google will find a *lot* more stuff for you.

Kaffeine is not a really player plugin, it's a replacement for (alternative to) Java. It's alright, but not the best, and may not work with Mozilla/Firefox at all, I never tried. You need to install genuine Java, enable Mozilla/Firefox to use it and go from there. If you need help with that there's plenty in the forum archives about it, or check the Sun and Firefox websites for downloads and instructions.

Yeah, I know, it was a joke...kinda...like the name of the site is a joke...kinda...

In the same article, he also says: 'Nuff said there. MS has worked long and hard to get that well-deserved reputation. But like tymark says, what's his references? Who and what are "some reports"? And who funded those reports? The guy is writing for www.fool.com. We would be fools to take him seriously.

Weird. Almost amazing. I've never had this problem. It must be because I didn't install the mc.rpm included with 10.1. I installed a 'generic' mc-4.6.rpm I got somewhere and have used for years 'cause it works with transparency. I've never had a problem with it.

Check the permissions on the rpm and contents. You probably need to be root to modify them. Doubtful there's anything wrong with your Mandrake install.

It's like this... There's MTAs (mail transfer agents), and MSAs (mail storage agents) and MUAs (mail user agents). MTAs get and send email over the internet. Fetchmail is an MTA that is specialized for getting mail. Postfix, sendmail, qmail, etc are also MTAs, specialized for sending mail. Procmail is a MSA. It takes the retrieved mail, sends it off for further processing (spamassassin, virus checker, etc.) then takes the output, sorts and stores it on the system in the designated place(s). MUAs are your email reader/composer - sylpheed, mutt, kmail, whatever. These functions sometimes overlap - like a MTA may have some MSA functionality, or as you know, most (but not all, such as mutt, pine, etc.) email clients nowadays have built-in retrieve and send capabilities and so can deal with mail over the internet directly. They really are a MTA+MSA+MUA all-in-one. But often the all-in-one approach isn't the best answer. Like Mr. Natural says, "Always use the right tool for the job." A building-block-of-apps approach, using tools specialized for each task, can give far, far better flexibilty. On most company email systems these days, the mail server's MTA fetches the mail from the internet, then the MSA sends it for processing and then stashes the output on the server, where the worker's MUA retrieves it via pop3 or imap. Outgoing mail may (or may not) be sent back to the server for virus checking, etc before going out on the 'Net. But that's usually for mid-to-large size companies where without using pop3/imap retrieval by the workers' email clients, the poor IT guy would have to set up sorting incoming mail to dozens, maybe hundreds, of mailboxes, keep track of all the name changes, etc, etc. Uuugghh. For your purposes you won't need to sort to hundreds of mailboxes, so I don't see much point in having the workstations' mail clients retrieve mail from your server via pop3. For incoming mail you can just let fetchmail get the mail (either running as a daemon auto-fetching every X-minutes, or called manually by the email client) have procmail send it for processing and then sort and deliver the filtered mail directly to the client mailbox(s) wherever they are, and skip setting up pop or imap retrieval on the client side. When you open your mail client the new mail will just be in there. For outgoing, if you use a mail client with built-in send capability outgoing mail can go out directly from the workstation. I have sendmail setup on my box, but that's 'cause the lovable mutt doesn't have a built-in send capability (though mutt will do pop3/imap retrieval and a whole lot more). So you won't need sendmail or postfix on the workstations unless you use a mail client like mutt that needs it. And you won't need to setup sendmail or postfix on your server *unless* you want send outgoing mail back to the server to run an anti-virus check or do other processing before it hits the 'Net. If so, you might want to get Paul more involved in this. Hope that clears things up a little...

I don't think the licensing terms are a problem, the terms MS has used have always stated one license for one computer. It's XPee's product activation thing that could cause trouble, but they don't seem too worried about it so they must have a handle on it. Of course bootleg XP copies less the activation scheme will no doubt be as popular with Win4lin as they are in general. For now, Netraverse is focusing on Win2k because since XP is to Win2k kinda like WinME is to 98SE, i.e. the same basic OS but all f*scked up, they figure most users will want to opt for Win2k. I've got both Win2k Pro and XP Pro and I know which I'll be installing. XP support will come a little later, for those unfortunate enough to have a copy of XP but no Win2k. It would be a good guess to say that Netraverse would just as soon not have to fool with XP at all, but they realize a lot of people are stuck with it. They had the same problem with 98SE/ME. They didn't want to put valuable development time into ME support but too many potential users were stuck with ME-only. At any rate, the no-kernel-mods thing is certainly great news and should make installing so easy any click-click MS refugee can install Win4lin and go. That should in turn really help the popularity of Win4Lin and, hopefully, Linux in general. Hey, maybe the new version will even include things like full DirectX and and USB support so I'll finally be able to start switching over all my office workstations to Linux. Or maybe I'm being a little TOO optimistic...

***Update*** Anyone interested in new Win4Lin developments might want to check the last message in this thread from time to time. I'll post anything significant happening there. For those who might want to know...word from the Netraverse developers is that volunteer outside beta testers for the new Win4Lin/Win2k will soon be recruited, with testing to start in early to mid Janurary. But maybe the best thing is, not only is Win2k support (and soon after that WinXP) getting close, but the new version will no longer require Win4Lin-patched kernels. Should just install and run on stock kernels. Who-hoo!!

This looks like a cool idea. I like the choice of oggs or FLAC downloads and the overall philosophy. They gotta make a major increase in choices though, so I can rock properly...

Hmmm...apache might deliver mail, but I never heard of anyone using it for that. But procmail is bound to be easier to setup and more flexible, since that's what it's intended to do. I don't know if you really need any of this, but here's a little stuff that might help you get fetchmail and procmail going. Fetchmail is very simple. I call fetchmail with: "!fetchmail -as\n". See 'man fetchmail' for details about the '-a' and '-s' options. Some basics for a .fetchmailrc: # This option tells fetchmail to run in the background as a daemon and # automatically check specified mail server(s). This example sets a # pass every 600 seconds (10 min). Comment out to NOT run fetchmail in # daemon mode. # set daemon 600 set postmaster "joe" # Name of the last-resort mail repcient. # set bouncemail # Directs error mail to sender. # set no spambounce # Sends spambounces. set properties "" # String value is ignored by fetchmail. set logfile "~/.fetchmail.log" # Set the pop username and password. Leave the password # parameter out to enter the password manually at login. # Basic format is: # poll SERVERNAME protocol PROTOCOL username NAME password PASSWORD # Example: # poll pop.gmx.net protocol pop3 username "joeblow" password "PASSWD" poll pop-server.kc.rr.com protocol pop3 no dns username "joeblow" # Tell fetchmail to send downloaded mail to procmail for further # processing. Comment out this line if not using procmail. mda "/usr/bin/procmail -d %T" A .procmailrc can be very simple or it can get pretty complicated, depending on what chores you want procmail to do. Some basics for a simple .procmailrc: # Preliminaries and File Locations: DEFAULT=$HOME/mail/spool # Often set to /var/spool/mail/joeblow MAILDIR=$HOME/mail SPAM=$HOME/mail/in/SPAM FORMAIL=/usr/bin/formail PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin/:/usr/games:/usr/lib/jre-1.4.2_05/bin SHELL=/bin/sh # For other shells, this might need adjustment - check your path! LOGFILE=$HOME/.procmail.log # This can be set globally in /etc/procmailrc. # LOGFILE=/dev/null # Do not generate a logfile. VERBOSE=OFF # OFF gives simple log entries. Set to ON for details for troubleshooting. # Some basic usage recipes: # 1st, we nuke duplicates using formail: :0 Whc: .msgid.lock | $FORMAIL -D 16384 .msgid.cache # 2nd, send messages smaller than 250kb to spamassassin for checking: :0fw: spamassassin.lock * < 256000 | spamassassin # 3rd, send messages flagged as spam to their own special place. :0: * ^X-Spam-Flag: Yes $HOME/mail/in/SPAM # 4th,sort email from certain people: :0 * ^From.*jblow@earthlink\.net $HOME/mail/in/joe Obviously, I didn't write those for a mailserver, but they should give you the idea. You'll need to add stuff for sending email trough a virus checker, to all your mailboxes, etc. There's an awful lot procmail can do. Check out Prof Timo's Procmail Tips & Recipes for much more great info. http://www.uwasa.fi/~ts/info/proctips.html

Thanks. That's the answer I expected, just wanted a second opinion before I did it 'cause I really have almost no experience fooling with KDE. Done, and it did fix the themes problem, but init.kde still hangs and has to be killed manually, Konqueror still refuses to open, etc. KDE is still in intensive care. Any Ideas where to go from here?

Sounds like what you want is to have the server get the mail via fetchmail, send it to procmail, which then sends it to spamasassin for checking, then procmail takes the results and sorts and delivers the mail (all this would be done on the server). No problem. And procmail can deliver it either to mboxes on the server for the workstations to access there, or send it to mboxes on the workstations themselves. You've got it basically right, the workstations wouldn't fetch mail themselves at all, fetchmail running on the server would handle that and the workstations' email clients would just look in the mailboxes. Likely you'd want filtered spam to stay in a mbox on the server. Unless you want to do some processing of outgoing mail, you wouldn't need to setup sending mail via the server, outgoing email can be sent directly from the workstations' email clients with their built-in send capability or with sendmail, postfix, qmail, whatever you like to handle outgoing mail. I use the lovable Mutt for email, which does not have send capability built-in, with sendmail. I can probably help you with some (most?) of setup if you want, but I'm no guru at this.

I'm not famailiar with this app but it's possible that "ksmoothdoc" may not be the proper command. Check "man ksmoothdoc" for info, if there is one. If not, try typing this in a terminal: rpm -ql ksmoothdoc That will list all the files installed from the package and their locations. Check the name of the executable and type the command exactly as it is named. If that fails, look for any "ReadMe" or ther docs that were installed that may help. Also might want to check permissions on the executable and see if only root is allowed to start it.

Why not put 2 nics (or 3) in the Linux box, connect the Linux box to the cable modem and connect the Win boxes to the Linux box (with either a switch or by using 3 nics) so the Linux box can be the firewall/router for the Win boxes? You could assign static IPs for the Win boxes and skip running a DHCP server on the Linux box. Draco Araurlis is probably right about the DNS thing. Just because ping works doesn't mean you have no problems on the network. We all wish it were so simple....

Here's what I have: $ df -H Filesystem Size Used Avail Use% Mounted on /dev/hda5 818M 123M 654M 16% / /dev/hdb1 99G 49G 45G 53% /data1 /dev/hdd5 56G 23G 31G 43% /data2 /dev/hda9 11G 4.2G 5.5G 44% /home /dev/hda1 2.0G 899M 1.1G 46% /mnt/win_c /dev/hdd2 5.0G 147M 4.9G 3% /mnt/win_c2 /dev/hda7 4.2G 2.8G 1.2G 72% /usr /dev/hda8 2.1G 820M 1.2G 43% /var /dev/sda1 32M 17M 16M 53% /mnt/sda1 I've used this setup for a long time. The 'hdb' and 'hdd' drives are for data storage only. The main 20G 'hda' system drive is split into: /mnt/win_c / /var /usr /home The reasons being: The /mnt/win_c is a minimal Win98 install, never used and only for *extreme* emergencies. I always make /var seperate just in case it gets filled by a runaway process or something. Otherwise, /var is put under /, and very bad things can happen then. I consider a seperate /var a must. I do back up whole partitions, and a /usr partition is kinda handy. Everyone who's used Linux for long knows a seperate /home is a Good Thing. Mine is fairly large becaus it also holds a complete Win4Lin/Win98 installation, a lot of data used by it, and it needs plenty of extra space to use for shuffling around large files. Otherwise I would make it smaller and the extra space would become another /data partition. I know that with seperate /var and /usr partitons / could be smaller, but I was too lazy to change it during the last install. And I figure plenty of extra space there is never a Bad Thing anyway. A pretty good case can be made for having /etc on a seperate partition also. Of course these partition sizes could be shrunk some if a more minimalist installation is done. I've got a lot loaded on this box.

Since upgrading from 8.2 to 10.1 KDE just isn't right. This is a fresh install, including formatting all partitions except /home, which was left untouched. Using the 'standard' KDE 3.2 that came with the 10.1 Power Pack, no changes whatever. A few of the problems I've found: 1. Biggest problem is after logging out, KDE process hangs and eats about 98% CPU. Have to kill this manually. 2. Desktops don't fully load, icons are missing. A refresh does get 'em to pop up though. 3. Can't change the theme. Still stuck with whatever was being used under KDE 2.2 at the time of the upgrade. 4. Konqueror will not open in KDE, though it will if logged in with Fluxbox or other WM. 5. Etc, etc. Basically, KDE is functional but very sick. To be honest, I couldn't care less myself - everything works great with Fluxbox or Ratpoison. But the other users on this box are starting to get upset so I gotta try to figure this out. So what would be the best way to go about straightening this mess out? I've never fooled with KDE much, it's just too Windows-like for me, so I'm not up to speed much about KDE illnesses and how to fix them. Thanks for any help.

I don't want to get into an arguement here, but I don't want Opera to get an undeserved bad rap (or Firefox for that matter)... Well, yeah, as far as that goes, but the menu is less intuitvley named (in mho) than Opera's and missing some stuff. Where's setup for lotsa simple things like default email program, java path, etc? And you still have to configure the extensions seperately, in a different menu under 'Tools', which then takes you to seperate menus for each extension. All this stuff should be in one place. ??? Tools>Preferences - it's all there, except for the stuff under 'View', which is just like Firefox. What could be simpler? That's cool. But it shouldn't matter what distro or OS you run, installation should just go bang-bang. It's a friggin' web browser, any numbskull should be able to install it without knowing anything. With Opera, it's either download with Java or thanks, I have it already so just give me the program, (or I don't know anything, whether I have Java or not or how to set it up if I do so just give it all to me to be sure) then install and go. Anyone who can install anything can install Opera with everything they need included. Firefox seems better suited to more computer-literate types. I put Firefox on for my Dad and my son, both Opera users and at least as savvy as an average point-and-click user, (well, my son is better than that!) to let them try it out. Both had a few questions for me about setup and use where with Opera they really didn't ask anything. They like it now that they've got the extensions they like, etc. But hey, Firefox has just had their first stable release while Opera's had years of developement. Firefox is really good now and will get better. It's already impressive overall, enough to break my years-long Opera habit. The speed and stabiity is great - it hasn't crashed yet. But I still use Links... :lol:

I think I can speak from some experience about this. I've been using Opera/Win for years, since version 4, and Opera/Linux since right about when version 6 was introduced. I have both Windoze and Linux version licenses. I've only been using Firefox for about a month, since the last beta release, but I'm gettin' a handle on it. I really, really like Opera. It's a lean, mean, web-grazin' machine. Easily configured almost any way you want it. Java is included if you want, and a snap for even a n00b to setup if you already have it installed. Opera has just about everything you might want or need already built-in and is still small and quick. The Opera guys obviously know what they're doing, but they gotta be paid to use it unencumbered. With Firefox, configuration is less intuitive and it's not as flexible. Java is not included, goofy to setup and would frustrate a raw n00b from the Windoze world who didn't understand command lines and creating symlinks. Lotsa stuff included in Opera has to be installed and configured seperately as extensions. The Firefox guys need to re-think some of this stuff and probably will, but they work for free. That said, I've still converted to using Firefox when I need a Java-enabled Linux browser. Why? Well, 'cause Firefox is also a lean, mean, web-grazin' machine. But the biggest reason is Firefox plays nice with several websites Opera struggled with or outright refused to, so I don't have to start Win4Lin to run IE for those sites - nice. I can only guess this is because more webmasters are testing with Firefox now because of all the press and newfound popularity. If so, I expect that trend to continue, but for testing against Opera to continue to be ignored by webmasters. Speed is basically a toss-up, but I give a slight edge to Firefox for stability, it really is a rock. I've found differences between them in how a few sites are rendered, but either one might be better, just depends on the site. No particular advantage either way there I can tell. I don't need the mail client in Opera, which I always stripped out after installing anyway. Notice I said I use Firefox for a Linux broswer...at this point I'm still using Opera for Windoze. Firefox/Linux is a keeper, but Firefox/Win has been a mess. Completely fouled up importing Opera's bookmarks, I can't get Java to work, some extensions I like aren't available for the Win version, etc, etc. Opera for Win still drills & thrills Firefox for Windoze. Makes me wonder why Firefox has gotten so much press as an IE replacement when Opera's been a better alternative than either one all along. I can't think of any reason to use Mozilla over Firefox, especially with Thunderbird available now for those who want a GUI mail client.

What's cool about Opera that I miss with Firefox is Opera zooms *everything*, text, graphics, photos - whatever, and with a single key (+ or -) no 'ctrl' needed. On the other hand, Opera won't zoom just the text, at least not that I know of. Overall, I'd rather set the font like I want in preferences and have 'total' zoom like Opera. I've used both the Linux and Windoze versions of Opera for years. Even so, now I've pretty much committed to using Firefox instead, mainly because it works on some websites I frequent that Opera struggled with. I guess more website coders are testing against Firefox because of all the publicity and popularity lately. Seems like Firefox might be a shade quicker than Opera and maybe even a bit more stable too. Both Firefox and Opera are pretty good. But actually, I still do most of my web grazing with Links.