Another tax on the server? Eek...
on
IRC Improvements
·
· Score: 2
From knowing people who've passed this knowledge down, either efnet/DALnet/ircnet server administrators or operators... IRC servers as much as anything else is huge on resources and bandwidth. It pretty common for an ircd to eat up more than 40MB of RAM in no time flat, not counting resources covering for buffered streams of data. Why do you think a lot of the major networks have tweaked their I:lines out so that clients can hardly even do so much as a/list so as to keep the server load down?
There's little hope of this ever being implemented as a patch on any of the large existing networks if it's anywhere near as processor intensive as I'd guess this would be. Benchmarks, anyone?
Perhaps for small corporate networks, but forget mainstream. And isn't that where we need it?
For those wanting to use linux on their system at home or at work where they (think) they don't have to worry about software licences, use redhat or corel linux. For anybody who wants to learn linux, they start with slackware. Read manpages, join irc channels and ask questions, avoid the installpkg command whenever possible... compile everything yourself. Don't know how? Read the manpages.
Rules to Live By:
Have an hour free? rm -rf/* as root to see what it does.
Oops, did that hurt the system? Go through the installation again. Familliarize yourself with the purpose of all the packages.
If it can be done in windows, it can be done better in linux. Do it. Prove to the world there is hope after microsoft.
freshmeat.net is your friend
It dosen't matter if you need to or not, just do it. It's perfectly normal to have several unfinished projects going at any given time.
Compile it your own damn self.
Good things come with time. I installed slackware using floppy disks made on a windows system with a 28.8 modem.
The real benefit of running a slackware system is that the system you are running is yours. There is no generic install, you can take pride in your accomplishments. One thing that slackware has accidentally taught me over the years is how to solve problems as they arise... a real life skill. Cheers to Patrick for keeping slackware the distro it was meant to be. =)
Though the whole furby trend is sort of passé, a much better resource that keeps up to date on the global furby reverse-engineering project can be found here. The section devoted to the infared commands they've been able to replicate was what really caught my eye. Have a gander, move along. Careful with the flames that you send tim's way:P
I don't doubt the practicality of the bacteria, nor the safety of the ones already in use. Though keeping a "scientists will do their job, never you worry" attitude could lead to a `laissez-faire' attitude about genetic engineering. Letting some Joe Average try and develop a cheaper alternative in his basement could be a mistake we end up paying dearly for. Then again, I'll probably just be called paranoid up until the day something goes wrong. =P
US Microbiotics [http://www.bugsatwork.com/], creators of the bacteria used to clean up oil spills have a few other nifty products on the market. Kinda cool to read, but you wonder, though the bacteria are engineered to be short-lived, what if something goes wrong?
It's great to see the demand for technology creating new products like these, however when will companies stop creating gadgets with "another new feature!" instead of creating something practical? I guess having something that'll support more then one TCP/IP application is way out of consumer price range right now. More "a-la pentium" step-by-step upgrades.
Slashdot Mirror
From knowing people who've passed this knowledge down, either efnet/DALnet/ircnet server administrators or operators... IRC servers as much as anything else is huge on resources and bandwidth. It pretty common for an ircd to eat up more than 40MB of RAM in no time flat, not counting resources covering for buffered streams of data. Why do you think a lot of the major networks have tweaked their I:lines out so that clients can hardly even do so much as a /list so as to keep the server load down?
There's little hope of this ever being implemented as a patch on any of the large existing networks if it's anywhere near as processor intensive as I'd guess this would be. Benchmarks, anyone?
Perhaps for small corporate networks, but forget mainstream. And isn't that where we need it?
Rules to Live By:
- Have an hour free? rm -rf
/* as root to see what it does. - Oops, did that hurt the system? Go through the installation again. Familliarize yourself with the purpose of all the packages.
- If it can be done in windows, it can be done better in linux. Do it. Prove to the world there is hope after microsoft.
- freshmeat.net is your friend
- It dosen't matter if you need to or not, just do it. It's perfectly normal to have several unfinished projects going at any given time.
- Compile it your own damn self.
- Good things come with time. I installed slackware using floppy disks made on a windows system with a 28.8 modem.
The real benefit of running a slackware system is that the system you are running is yours. There is no generic install, you can take pride in your accomplishments. One thing that slackware has accidentally taught me over the years is how to solve problems as they arise... a real life skill. Cheers to Patrick for keeping slackware the distro it was meant to be. =)Though the whole furby trend is sort of passé, a much better resource that keeps up to date on the global furby reverse-engineering project can be found here. The section devoted to the infared commands they've been able to replicate was what really caught my eye. Have a gander, move along. Careful with the flames that you send tim's way :P
I don't doubt the practicality of the bacteria, nor the safety of the ones already in use. Though keeping a "scientists will do their job, never you worry" attitude could lead to a `laissez-faire' attitude about genetic engineering. Letting some Joe Average try and develop a cheaper alternative in his basement could be a mistake we end up paying dearly for. Then again, I'll probably just be called paranoid up until the day something goes wrong. =P
US Microbiotics [http://www.bugsatwork.com/], creators of the bacteria used to clean up oil spills have a few other nifty products on the market. Kinda cool to read, but you wonder, though the bacteria are engineered to be short-lived, what if something goes wrong?
It's great to see the demand for technology creating new products like these, however when will companies stop creating gadgets with "another new feature!" instead of creating something practical? I guess having something that'll support more then one TCP/IP application is way out of consumer price range right now. More "a-la pentium" step-by-step upgrades.