Is mIRC made for a Linux machine? I have Redhat 8.0 and would like to get mIRC on it. I know that there's an buildin mIRC in the Mozilla browser, but i dont know how to use it, because it dosen't understand the regular commands like /join (/j) #NetGamerZ.dk

Hope to get an answer soon.

LePsycho

from the mirc faq :

6-3 Is there a version for Windows CE, WebTV, Mac or Linux?

No, sorry. mIRC just comes in two tastes for Windows; a 16 bit and a 32 bit one. These issues will work on Windows 3.x, Windows 95, 98, 2000, ME, XP, and NT, but not on Windows CE. mIRC also does not work on the Atari, Commodore, WebTV, Macintosh, UNIX or Linux operating systems. We have no plans to make mIRC versions for these systems in the future either. Sorry....

Some people have reported success running mIRC under vmware or wine.

The program included with Mozilla, is NOT mIRC. It is a chat client called Chatzilla. If you want to use IRC under Linux, I would recommend xchat which you can get at www.xchat.org

Okay, thanks !!

I really hate that system that you are using. Lunix and redhat that is what my school is using and it is one of the thinks i hate the most out of all operating system. Its annoying and not very usefull.
But I think it is only made for windows, but the commands are almost just like shell. I really recomend you to throw out that operating system and use Windows. I am pretty sure you wont regret it.

I know im also a windows lover! But the thing is, that i would like to run a Counter Strike server, and for that system Linux is the most secure and stable operation system! So thats how simple it is

And by the way, IT FREE unlike Windows !!

www.irssi.org

You can run mIRC 16 bit on linux..takes litle work tho but can be done

Well if you are running a server it's stability would be assured if you were only using it for one task, regardless of what OS you use.

Yes, my friend has success running mIRC on Wine.

I had a windows XP uptime (until i lost power--not OS at fault) that far surpassed two friends of mine running mandrake and redhat.. Windows only crashes because the user is unknowledgable, not because the operating system is bad.

Windows XP Pro is what I use. And Windows is buggy now and then, it's not always user ignorance for others. Keyword: always.

The site dosse't work anymore

have you done it?

Im using RedHat 8.0 -> Psycho is this a good server hosting OS?

Thanks that's all i want to know. But is redhat a good OS for the server running?

If you have a high uptime on your linux box, all that means is you have an outdated kernel (and probably one of the ones that mangles filesystems...)

I promised myself that I wouldn't get involved in ye 'ole which OS is better debate, but here goes...



If you have a high uptime in Windows it means you haven't updated anything... I swear it forced me to reboot after Windows Update added an icon to my Start menu. With *nix the one and only time you have to reboot is if you want to load up a different kernel... I can even run off of the old kernel entirely in memory while it has been removed from the HD and replaced with something else. (translation: reboot when I decide)

My POV is that each OS has it's merrits and a user should pick what's best for their situation... Windows makes a great end user graphical OS, and a very awful server, while the reverse is true for *nix.

When I install windows xp I don't have to deal with things like creating ext2, swap,ect.. partitions or with the confusion of deciding whether to put lilo in the first boot sector or the mbr. The windows install is very straightforward and user-friendly. Linux is not!

Linux is not secure it has just as many holes in it as windows does if not more.
Heres a list of some more commonly known linux security holes:

1. The uml_net utility, part of the kernel-utils package in Red Hat Linux 8.0, was shipped with incorrect permissions.

a. Local users could control network interfaces, put interfaces into promiscuous mode, and add and remove arp entries and routes.

2. The "netfilter" firewall subsystem included with Linux kernel versions 2.4.x contains a vulnerability that may allow remote attackers to reach hosts that should be protected.

3. From the HP-UX security bulletins digest (HPSBUX0305-259): A problem has been reported in kermit which could allow access to account bin and group daemon privileges. Until a fix is available we recommend removing suid/sgid permissions from kermit. This will limit the functionality of kermit. Full functionality will be available only to the root user.

4. Buffer overflow vulnerabilities exists in the DNS stub resolver library used by BSD, ISC BIND, and GNU glibc. Other systems that use DNS resolver code derived from ISC BIND may also be affected. An attacker who is able to control DNS responses could exploit arbitrary code or cause a denial of service on vulnerable systems.

a. An attacker who is able to control DNS responses could exploit arbitrary code or cause a denial of service on vulnerable systems. The attacker would need to be able to spoof DNS responses or control a DNS server that provides responses to a vulnerable system. Any code executed by the attacker would run with the privileges of the process that called the vulnerable resolver function, potentially root.

5. There is a remotely exploitable buffer overflow in PopTop. An exploit for this vulnerability exists and is publicly available.

a. A remote attacker may be able to crash the PPTP server or execute arbitrary code with the privileges of the PopTop server.

6. A remotely exploitable denial-of-service vulnerability exists in the Apache HTTP Server. Exploitation of this vulnerability may allow an attacker to consume all available system resources, resulting in a denial-of-service condition.

a. Exploitation of this vulnerability may allow an attacker to consume all available system resources, resulting in a denial-of-service condition.

7. There is a vulnerability in sendmail that may allow remote attackers to gain the privileges of the sendmail daemon, typically root.

a. Successful exploitation of this vulnerability may allow an attacker to gain the privileges of the sendmail daemon, typically root. Even vulnerable sendmail servers on the interior of a given network may be at risk since the vulnerability is triggered from the contents of a malicious email message.

8. Samba contains several buffer overflow vulnerabilitites. At least one of these vulnerabilities could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service.

a. An unauthenticated, remote attacker could execute arbitrary code or cause a denial of service. The Samba daemon (smbd) runs with root privileges, so an attacker could gain complete control of a vulnerable system.

Oh good. Another OS 'war' filled with non-facts and half-truths.

Yep. Sad eh.

I think those Linux people are a joke. Windows will always be king. :tongue:

Obviously Linux is free, the bug fixers aren't getting paid.

As with most things, its a matter of choice. Insulting another's choice and trying to rekindle a flame war is pointless.