SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the md5sum is: 9a0e09366da25e55fdba3fe1bed76a23 slackware-10.1-install-d2.iso
That's the same as the file I downloaded via Bittorrent.
Either both are compromised or you have a bad md5 file. No way for me to know which is the case. I don't have anti-virus on my Slack box (for obvious reasons). There is a high probability that you have a false positive from your AV program. I'm sure a lot of code that KDE uses might look like a Windows virus according to heuristics.
A couple of things (from being an unofficial mirror of slackware):
Where did you download the .torrent files from?
Did you use the format `md5sum -c slackware-10.1-install-d1.iso.md5` (et. al for the other iso's)?, if not, please do, and make sure you get an "OK" output. Just to double check, you may want to download the .md5 files from a trusted source. slackware.com/osuosl/tds/vtu (myself, although I'm rather low on the bandwidth meter).
Who did you "email at slackware"?
Silly rumors start from posts like this, so please be wary of what you say, people may actually believe it without any proof.
If you can post your answers to the questions above that would be great, hopefully you don't feel offended that I might be asking silly questions, but it would be good to know where the source of the problems are.
Well I emailed the antivurs yesterday about it and they said it's common and it is a false positive and it happens because some of the coding in kde sets off the antivurs and there is nothing really they can do about it because if they take that virus definition out, some virus's will be able to pass the antivirus.
Originally posted by cereal83 Well I emailed the antivurs yesterday about it and they said it's common and it is a false positive and it happens because some of the coding in kde sets off the antivurs and there is nothing really they can do about it because if they take that virus definition out, some virus's will be able to pass the antivirus.
Originally posted by cereal83 I won't but a windows antivurs caught this virus, not a linux one. Windows virus's don't do anything to linux.
"Windows" antivirus, as in Microsoft? I'm surprised it didn't say the whole ISO was one big virus.
Glad everything is working alright. Me, I just updated the image on my NFS server and did a reinstall (from scratch) on my laptop. Didn't like the drive configuration anyway, and figured it was as good a time as any to fix it. The only weird thing I'm getting is on first boot, insmod complaining about a whole bunch of files with improper configuration. probably not something I really need to worry about, and I'm not in front of the laptop to fix it anyway.