You can do this by adjusting the output voltage of the flyback transformer (the 220 V -> 35 KV transformer!). Your local TV repair shop can probably do it for you.
I'd LOVE to see a Linux distribution based entirely on an OpenLDAP infrastructure. Most of the technoligy is already there, it just has to be pieced together in a nice ready-to-go package.
Here's what we already have:
OpenLDAP server. Nice and solid, but too hard to administer.
PAM. My workstation had been running for months without a/etc/passwd file. No problem whatsoever. Simply use pam_ldap and nss_ldap and you're set
Samba. Intergrates nicely with LDAP. When running as a PDC, Samba will change your unix password when your change your windows pass, and you can have linux to change your windows pass when you change your unix pass. This gives nice and transparent intergration without the user ever knowing that his password is stored in no less than three different hashes.
LDAP admin frontend. This is where the trouble starts. Mosts frontends are generic and therefore complex. Most admins simply want to store user accounts into a LDAP database, including telephone numbers, home address, etc. No really good interface which makes this task an easy one yet exists, AFAIK. A lot of bad ones do, however.
YaST however does already have a simply LDAP tool to create users. YaST also makes setting up a LDAP client a breeze. Combined with Novell's knowledge on directories this could lead to an interesting development.
There are plenty of companies paying programmers good money to write free software. They want the software, and they believe that the quality of the software will increase by releasing the source. Or they believe they will sell more hardware when the software running on it is free. Or they sell support on the software they release.
Nobody asks a programmer to work for free. The author of the letter thinks that releasing code for free equals not getting paid for writing it. Think again.
I don't know much about Gnome, but KDE is certainly not dominated by traditional Unix hackers. The KDE developers do care about usability by normal users. With every release they improve.
They're not there yet, but it's certainly not hopeless.
As someone who doesn't know much about Gnome, I'm under the impression that Gnome is more traditional than KDE. They do have solid standards for usability, but these standards seem to be written in the mid nineties and never updated.
Assembly programming is almost hardware programming. If you want to learn about programming real computer programs, you'll have to learn about algorithms. And algorithms are best implemented in higher level languages. Assembly is only used when all other options fail.
I do not know the interface of the iPod -- never seen such a thing. But: less buttons does not imply that the user interface is better. A lot of modern electronics have buttons which have two or more functions. That actually confuses users.
My monitor for example, has three buttons to navigatie through the OSD. But I have to press two simultaniously to exit the menu. Friendly? No.
The three buttons are: menu, -, +
When you press - or + in normal operation, you set the contrast. To set the brightness, set the contrast and press menu within the OSD timeout. Then press - or +. Argh!
Yes, I can figure it out. No problem. But is my granddad able to figure it out? Don't think so...
Spews is not a list for blocking spam. Spews is a boycot against spam supporting providers. Spews wants the listed providers to clean up their act.
Note that a spam supporting provider is not by definition a large source of spam. They could be, but they meight as well be the hoster of spamvertized websites. And as long as providers are willing to (continue to) host spamvertized sites, spammers will continue to spam.
I see lots of comments in the forum like 'spews blocked my server'. Spews did no such thing. Spews is listing their provider. That's what spews does. They list providers. Spam friendly providers.
When your provider is listed by spews, it's time to move away. You are supporting your provider, which is supporting spammers.
When legitimate customers move away, providers will feel that supporting spam costs them real money. They will figure it out sooner or later: the community hates spam. Really, really hates it. And the community will hate you for not hating spam.
Why do rewrites happen? Quite simple. The world is changing, and it's changing in an incredible pace. We live in a world where processors double their speed roughly every 18 months. RAM gets bigger and cheaper.
What worked three years ago could be messy and clumbsy by today's standards.
The problem is: computers are getting more powerful. So the computers can do more. And computers should do more. That's why we make them in the first place. To make the life of the user easier.
Easy-of-use almost always implies complex software. It may well turn out that you can't add the required level of complexity to version N of your software, so you write version N+1.
Why IPv6? Because IPv4 isn't up to its task anymore. If you don't believe me, just ask your ISP for a/28 because your want to have all your machines online. Guys, this is a common situation and IPv4 can't deal with it! We have to use a dirty hack called NAT in order to keep things a little manageable.
Why Mozilla? Netscape 4 is slow, unstable, underfeatured. It won't meet the demands of the modern web by a long shot. It's got a poor CSS implementation, the HTML implementation is not standards compliant, XML? Nah...
In short: change is inherent to the modern (IT) world. Deal with it. If you really think netscape 4 is a good browser, it's getting time to look for a new field of interest. Seriously.
If KDE or GNOME start to bloat or stagnate or become unsuitable, then I'm sure the three window managers I just mentioned might just see an increase in users.
Not going to happen. Old style window managers only attracts geeks and nerds, not regular users. On the end user desktop the traditional window manager is dead and buried.
But just FYI: the upcoming KDE 3.2 is WAY faster than KDE 3.1.
MSIE is very much intergrated with the operating system. And that intergration is good. From a technical point of view anyway. Not from a competative point of view:-)
Anyway, MSIE consists of a great number of libraries which are used by many applications, including msie-the-app.
msie-the-lib consists of an http library, an html rendering engine, mime handlers, etc, etc. That library is being used by Outlook (Express) for example. Also the reason why that app is so very insecure.
I don't know the exact state of intergration of msie-the-lib into the core ms windows application, but I can imagine is extensive.
In KDE the intergration is a little more visible. Konqueror is little more than a framework in which kparts can run. One of these kparts is khtml, the html renderer. khtml is to kde what msie-the-lib is to windows.
When you'd attempt to remove msie from windows, you'd probably could uninstall msie-the-app with little trouble.
On a large scale the spammer will just send a few 'test' messages through your system and move on to the next. With a million spamholes, a spammer can send a million mails at the least. Great.
Also, you'll get yourself blocklisted by every major DNSBL very soon. They scan for open relays too...
The server can simply store the information in the video RAM, where it belongs. As long as the data fits in video mem, it won't cost you any main memory.
Think about it: most spam comes from cable and adsl connected machines. dynablock.easynet.nl is trying to block each and every dynamic IP on earth, effectively making it a whitelist of static and therefore blockable IP's.
One could even take this one step further: blacklist the entire internet and whitelist known mailservers. Getting out of that should be easy, but no so easy that a spammer could do it automatically. And when you're spamming from a whitelisted IP, the IP is blacklisted again for, say, 1 week. Then it can be whitelisted again, but when you're spamming again, then it's blacklisted for a month.
The hard part of such a whitelist is: where do you start? I think it would be sensible to start out by simply tagging mail originating from blacklisted IP's. Early adopters can then whitelist each and every IP they expect mail from. After a while a sufficiently small amount of mail will be tagged by the blacklist, so it can be used to start blocking with it.
If we only could convince each and every postmater on earth to use such a system, it could be very, very useful.
Meanwhile, please use Dynablocker. It can really help making h4x0red boxes useless as a spam source.
Personally, I can't see how that will ever be easy to use - for example, how do you abstractly ask the question 'How should the disk be partitioned?' uniformly across text/gui?
SuSE's Yast does this. Yast had both a Qt and a ncurses interface. They share the same backend. The backend is mostly platform independent.
SuSE installs using the graphical yast by default, but on the second CD in the cdset the text version of yast is included.
Both charter and rr are MAJOR sources of spam, so I'm not suprised.
The amount of spam coming out of rr.com is about equal to the amount of spam coming out of korea. At least for me it is. Charter isn't as bad, but it's a major source too.
Slashdot Mirror
Actually it's three 19" racks.
You can do this by adjusting the output voltage of the flyback transformer (the 220 V -> 35 KV transformer!). Your local TV repair shop can probably do it for you.
A CRT will ware out in about five years. Brightness and contrast will decrease to a level which is unacceptable.
You can increase the brightness again by pumping up the voltage level on your tube, but that will only increase the rate of detoriation.
Yeah, but I'm lazy so I also say I store data in SQL. Sue me.
I'd LOVE to see a Linux distribution based entirely on an OpenLDAP infrastructure. Most of the technoligy is already there, it just has to be pieced together in a nice ready-to-go package.
Here's what we already have:
YaST however does already have a simply LDAP tool to create users. YaST also makes setting up a LDAP client a breeze. Combined with Novell's knowledge on directories this could lead to an interesting development.
There are plenty of companies paying programmers good money to write free software. They want the software, and they believe that the quality of the software will increase by releasing the source. Or they believe they will sell more hardware when the software running on it is free. Or they sell support on the software they release.
Nobody asks a programmer to work for free. The author of the letter thinks that releasing code for free equals not getting paid for writing it. Think again.
I don't know much about Gnome, but KDE is certainly not dominated by traditional Unix hackers. The KDE developers do care about usability by normal users. With every release they improve.
They're not there yet, but it's certainly not hopeless.
As someone who doesn't know much about Gnome, I'm under the impression that Gnome is more traditional than KDE. They do have solid standards for usability, but these standards seem to be written in the mid nineties and never updated.
What is an haiku anyway? All I can see are three lines without rhime or rithm, probably intermixed with some 'wise' words.
Assembly programming is almost hardware programming. If you want to learn about programming real computer programs, you'll have to learn about algorithms. And algorithms are best implemented in higher level languages. Assembly is only used when all other options fail.
I do not know the interface of the iPod -- never seen such a thing. But: less buttons does not imply that the user interface is better. A lot of modern electronics have buttons which have two or more functions. That actually confuses users.
My monitor for example, has three buttons to navigatie through the OSD. But I have to press two simultaniously to exit the menu. Friendly? No.
The three buttons are: menu, -, +
When you press - or + in normal operation, you set the contrast. To set the brightness, set the contrast and press menu within the OSD timeout. Then press - or +. Argh!
Yes, I can figure it out. No problem. But is my granddad able to figure it out? Don't think so...
(it's an Iiyama Vision Master Pro 450)
Right, you don't understand spews either.
Spews is a boycot list.
Spews is not a list for blocking spam. Spews is a boycot against spam supporting providers. Spews wants the listed providers to clean up their act.
Note that a spam supporting provider is not by definition a large source of spam. They could be, but they meight as well be the hoster of spamvertized websites. And as long as providers are willing to (continue to) host spamvertized sites, spammers will continue to spam.
I see lots of comments in the forum like 'spews blocked my server'. Spews did no such thing. Spews is listing their provider. That's what spews does. They list providers. Spam friendly providers.
When your provider is listed by spews, it's time to move away. You are supporting your provider, which is supporting spammers.
When legitimate customers move away, providers will feel that supporting spam costs them real money. They will figure it out sooner or later: the community hates spam. Really, really hates it. And the community will hate you for not hating spam.
Why do rewrites happen? Quite simple. The world is changing, and it's changing in an incredible pace. We live in a world where processors double their speed roughly every 18 months. RAM gets bigger and cheaper.
What worked three years ago could be messy and clumbsy by today's standards.
The problem is: computers are getting more powerful. So the computers can do more. And computers should do more. That's why we make them in the first place. To make the life of the user easier.
Easy-of-use almost always implies complex software. It may well turn out that you can't add the required level of complexity to version N of your software, so you write version N+1.
Why IPv6? Because IPv4 isn't up to its task anymore. If you don't believe me, just ask your ISP for a /28 because your want to have all your machines online. Guys, this is a common situation and IPv4 can't deal with it! We have to use a dirty hack called NAT in order to keep things a little manageable.
Why Mozilla? Netscape 4 is slow, unstable, underfeatured. It won't meet the demands of the modern web by a long shot. It's got a poor CSS implementation, the HTML implementation is not standards compliant, XML? Nah...
In short: change is inherent to the modern (IT) world. Deal with it. If you really think netscape 4 is a good browser, it's getting time to look for a new field of interest. Seriously.
I promise I start using KiB and MiB as soon as the USA converts to the metric system.
If KDE or GNOME start to bloat or stagnate or become unsuitable, then I'm sure the three window managers I just mentioned might just see an increase in users.
Not going to happen. Old style window managers only attracts geeks and nerds, not regular users. On the end user desktop the traditional window manager is dead and buried.
But just FYI: the upcoming KDE 3.2 is WAY faster than KDE 3.1.
Maybe they're going to use Ximian's talent to make KDE even better. Like applying a HIG to KDE about which gnome users tend to whine and bitch a lot.
(I personally think having a HIG is a good thing, but it mustn't result in a desktop with a 1998 look, however nice and consistent)
And since the dollar is worth shit these days, the prices in dollars are relatively high. $25 to $100.
Keep voting Bush, it's very good for our import :-) (yet not so great for our export)
Suse 9.0 ships with one of the 2.6.0-test kernels. And debian unstable is no distribution of course ;-)
In an amazing coincidence I just implemented SPF filtering on my server yesterday.
This is what I got:
Jan 8 19:34:01 scrat sendmail[16839]: i08IY0ON016839: Milter: from=<larhondabeirne@aol.com>, reject=550 5.7.1 Command rejected
Jan 9 05:34:47 scrat sendmail[16305]: i094YlON016305: Milter: from=<krbsnag2gs@aol.com>, reject=550 5.7.1 Command rejected
Jan 9 08:59:45 scrat sendmail[25027]: i097xiON025027: Milter: from=<clairacree@aol.com>, reject=550 5.7.1 Command rejected
MSIE is very much intergrated with the operating system. And that intergration is good. From a technical point of view anyway. Not from a competative point of view :-)
Anyway, MSIE consists of a great number of libraries which are used by many applications, including msie-the-app.
msie-the-lib consists of an http library, an html rendering engine, mime handlers, etc, etc. That library is being used by Outlook (Express) for example. Also the reason why that app is so very insecure.
I don't know the exact state of intergration of msie-the-lib into the core ms windows application, but I can imagine is extensive.
In KDE the intergration is a little more visible. Konqueror is little more than a framework in which kparts can run. One of these kparts is khtml, the html renderer. khtml is to kde what msie-the-lib is to windows.
When you'd attempt to remove msie from windows, you'd probably could uninstall msie-the-app with little trouble.
It won't work.
On a small scale it has no impact.
On a large scale the spammer will just send a few 'test' messages through your system and move on to the next. With a million spamholes, a spammer can send a million mails at the least. Great.
Also, you'll get yourself blocklisted by every major DNSBL very soon. They scan for open relays too...
The server can simply store the information in the video RAM, where it belongs. As long as the data fits in video mem, it won't cost you any main memory.
But not whitelisting as we know it.
Think about it: most spam comes from cable and adsl connected machines. dynablock.easynet.nl is trying to block each and every dynamic IP on earth, effectively making it a whitelist of static and therefore blockable IP's.
One could even take this one step further: blacklist the entire internet and whitelist known mailservers. Getting out of that should be easy, but no so easy that a spammer could do it automatically. And when you're spamming from a whitelisted IP, the IP is blacklisted again for, say, 1 week. Then it can be whitelisted again, but when you're spamming again, then it's blacklisted for a month.
The hard part of such a whitelist is: where do you start? I think it would be sensible to start out by simply tagging mail originating from blacklisted IP's. Early adopters can then whitelist each and every IP they expect mail from. After a while a sufficiently small amount of mail will be tagged by the blacklist, so it can be used to start blocking with it.
If we only could convince each and every postmater on earth to use such a system, it could be very, very useful.
Meanwhile, please use Dynablocker. It can really help making h4x0red boxes useless as a spam source.
Personally, I can't see how that will ever be easy to use - for example, how do you abstractly ask the question 'How should the disk be partitioned?' uniformly across text/gui?
SuSE's Yast does this. Yast had both a Qt and a ncurses interface. They share the same backend. The backend is mostly platform independent.
SuSE installs using the graphical yast by default, but on the second CD in the cdset the text version of yast is included.
Both versions are very easy to use.
Both charter and rr are MAJOR sources of spam, so I'm not suprised.
The amount of spam coming out of rr.com is about equal to the amount of spam coming out of korea. At least for me it is. Charter isn't as bad, but it's a major source too.