Google's results are now less accurate because people are cheating. The way pagerank works is widely documented, and people abuse from it to get better scores.
I work for a company that hosts pr0n sites. Maybe 95% of our partneers are cheating that way. Fake sites, fake auto-generated HTML pages (with pseudo real sentences), cloaking (what Google sees is not what visitors see), javascript tricks, etc. are a must. They spend most of their time on trapping google, it brings more money than working on the site itself.
The company I'm working for has even a team working full-time on this (spamming search engines, and creating thousands of fake sites just to promote one real site) .
I've been running Gentoo Linux for some times with XFS. Here's my experience with this filesystem:
- It's extremely reliable. Filesystems never got corrupted, even after a lot of ugly reboots.
- Recoveries after a crash are really fast. Almost immedate, better than ext3 and reiserfs.
- Every needed tool is available to resize filesystems, check filesystems, analyze filesystems and backup/restore filesystems.
- _BUT_ there's something strange. Basically during disk I/O, the whole system is unresponsive. While I'm compiling something, KDE becomes slow, playing videos is not smooth at all, etc. Just as if it didn't scale at all for concurrent disk access. So I finally switched back to ReiserFS just because of this. Maybe the 2.5.x series of kernel behaves differently.
All these add-ons are nice, but you can easily have a very hardened server without installing nor patching anything. Linux, *BSD and probably other operating systems have extended fs attributes for ages.
With standard commands like chflags (BSD) or chattr (Linux), you can mark files and directories read-only (immutable) or append-only.
The point is that once you have a working system, and if you have local access to the console, you can set proper attributes to all your files.
You then have the concept of "security levels". Once your box is in multi-user mode, the "security level" can increase, and a lot of thing will be refused by the kernel : changing firewall rules, access to kmem, to raw devices, etc. and changing extended attributes.
So even if an attacker gets root access on your box, he won't be able to alter anything except some ever changing files (something that can be solved by using an NFS mount) . And the append-only log files are really nasty, because he won't be able to hide what he's doing. Patch your favorite shells to always log history files to an append-only file to get even more fun.
On a properly configured box (that you have console access on), you must be able to run "rm -rf/" as root, and your system must still be up and running. No need for any integrity checker.
Non-commercial Linux distributions like Gentoo or Debian are impressive. They have more package than most commercial distros, they are actively maintainer, they have an amazing packaging system, they are free and everyone can put his finger in the pie.
But *commercial* distros are really important. Why? Because companies like SuSE or RedHat have a marketing force. Without them, a lot of companies would never have heard about Linux. Just like a lot of other free operating systems, Linux would have been something designed by geeks, and for geeks. SuSE, RedHat, etc. give an important professional aspect to Linux. Thanks to them, some hardware vendors gave specs or developped Linux drivers. Thanks to them, web plugins like Flash are supported on Linux. Thanks to them and their money, Linux has been ported to Intel and AMD 64 bits architectures. Thanks to them, any dummy can buy a SuSE package with a comprehensive printed manual, everything on CD's and DVD's, and get technical support.
Sure, once you are familar with Unix/Linux, you can easily use any distro, commercial or not, or even switch to BSD. But I guess a lot of people would never have installed Linux/Unix on their computer if the only thing they was given was http://www.debian.org/ or http://www.openbsd.org/.
So please stop bashing commercial Linux distributions. Linux would never have been what it is nowadays without them.
This is true, the latest Netcraft surveys confirmed it : the Internet is dying.
Let's have a look at some numbers. According to TCP/IP's leader Richard Stevens, ehm... nothing.
How many devices connected to the Internet do I have in my toilets? Zero. This is coherent with the number of posts on Usenet whoose title is "How to upgrade my toilets to IPv6"
Movies theaters were designed so that you can go there with a girl you don't know very much, and kiss her one hour later if the film is romantic.
So, home theaters can't be valid substitutes for real theaters. Looking a romantic film at home with a girl you just met is: 1) more difficult. "let's go to my room" sounds like a trap. "let's go to the cinema" sounds more uninterested. 2) less fruitiful. A romantic scene has more impact on an huge screen, with plenty of speakers that emphasizes the power of beautiful slow violins.
Plus: in real theaters you can always get beer, ice and popcorn.
If you define structure with public stuff but default, why the hell are you using 'class'? Use 'struct'. The only difference between 'class' and 'struct' is that 'class' has private members by default, while 'struct' has them public by default.
IMHO, comments are often confusing. A source code that has plenty of comments becomes unreadable. And comments aren't always in sync with the code when changes are made.
A source code with no comment, but whoose structure is very simple is way easier to understand. When the compiler sees long and overcomplicated expressions, it painfully transforms them into more, but basic expressions. So why not write simple code?
I often see complicated lines with plenty of ternary operator usage. Why? Write the same code with simple 'if' statements. The generated code will be exactly the same, but the source code will be easy to understand.
Another very confusing thing (IMHO) is the usage of expressions without explicit braces in loops and conditional statements. Ie. things like:
if (ready())
while (*++take)
if (*take == 4)
foo();
Without indentation, it's very confusing. Worse : what if I want to add an 'else' here? If I want to add an 'else' to the second if, I really have to properly indent it to avoid confusion. If I want to add an 'else' to the first if, I have to add braces. This sort of thing doesn't ease the usage of macros and can give very nasty bugs when cutting/pasting blocks without carefully understanding where implicit braces are. So why not simply write:
if (ready() != 0) {
while (*++take != 0) {
if (*take == 4) {
foo();
}
} }
The generated code will be exacly the same, but there's no possible confusion here.
Also, 'goto' is not bad. Really. When you have to break from several loops, or just to avoid deep nesting of statements, a well placed 'goto end' is way clearer and faster than useless functions and silly 'flag_to_see_if_we_have_to_exit' variables. Don't forget that after compilation, any program will have 70% of goto-like assembler opcodes.
Comments can be interesting to note bugs, or TODO stuff.
Also have a look at the style(9) adopted by the OpenBSD team. There are good ideas.
It's based upon an OpenBSD-current kernel (so you get PF and all the great OpenBSD stuff), with FreeBSD tools, an hardened installation, custom additions and ports, a stripped-down base, etc.
The worst thing about that virus is that it has massively hit a lot of mailing-lists.
Interesting threads on mailing lists died because of this. People got insulted although they didn't send anything. A lot of people unsubscribed from mailing-lists due to this.
So people installed antivirus software, personal firewalls, etc. The result was that on mailing-list, instead of having tons of viruses, we got tons of "alert: you have sent a virus, it has been removed by our robot", that is as frustrating as the original virus.
Thanks a lot to Microsoft for being responsible of the most annoying viruses so far.
It produces similar reports, but it can works with a lot of servers, including FTP servers, firewalls, a bunch of web servers, realserver, shoutcast, squid, etc.
Slashdot Mirror
The article is about *WEB* high performance.
I don't see your point. "ping" has never been designed to benchmark web servers AFAIK.
My servers don't answer to "ping". Does it mean that the web server is down? Noppe... it's up a running...
"ping" is not an all-in-one magic tool. By using "ping" you can test a "ping" server. Nothing else.
I don't understand.
Their article is about building a high performance web server, and they tell people to use Apache.
Apache is featureful, but it has never been designed to be fast.
Zeus is designed for high performance.
The article supposes that money is not a problem. So go for Zeus. The Apache recommendation is totally out of context.
The description includes :
"1x Biology U-Port"
What kind of beast is that?
Why did Microsoft _pay_ a company to port Passport to _some_ operating systems?
:
They'd better
- Release the source code and the protocol description, so that anyone can freely create Passport compatible software for every operating system.
- Keep their cash for marketing, so that people understand what Passport could bring.
I've never used PGP, only GPG. What's good in PGP that GPG doesn't have?
Google's results are now less accurate because people are cheating. The way pagerank works is widely documented, and people abuse from it to get better scores.
I work for a company that hosts pr0n sites. Maybe 95% of our partneers are cheating that way. Fake sites, fake auto-generated HTML pages (with pseudo real sentences), cloaking (what Google sees is not what visitors see), javascript tricks, etc. are a must. They spend most of their time on trapping google, it brings more money than working on the site itself.
The company I'm working for has even a team working full-time on this (spamming search engines, and creating thousands of fake sites just to promote one real site) .
Slashdot is the site I spent 90% on when I'm connected to the internet. It's the first thing I read every day.
Slashdot is a source of info, of pure fun and of substancial debates.
Congrats, Mista Taco!
Funny. The RC5 algorithm has just been removed from OpenBSD because of copyrights.
I've been running Gentoo Linux for some times with XFS. Here's my experience with this filesystem :
- It's extremely reliable. Filesystems never got corrupted, even after a lot of ugly reboots.
- Recoveries after a crash are really fast. Almost immedate, better than ext3 and reiserfs.
- Every needed tool is available to resize filesystems, check filesystems, analyze filesystems and backup/restore filesystems.
- _BUT_ there's something strange. Basically during disk I/O, the whole system is unresponsive. While I'm compiling something, KDE becomes slow, playing videos is not smooth at all, etc. Just as if it didn't scale at all for concurrent disk access. So I finally switched back to ReiserFS just because of this. Maybe the 2.5.x series of kernel behaves differently.
The problem is that when you sum up everything, you end up with something _more expensive_ than just buying it from Apple.
Oh and of course you also have to purchase MacOS.
Nikola TESLA
A lot of things wouldn't exist without the help of this very first 'hacker'.
This is not specific to FreeBSD. Every BSD variant has this feature for ages AFAIK.
All these add-ons are nice, but you can easily have a very hardened server without installing nor patching anything. Linux, *BSD and probably other operating systems have extended fs attributes for ages.
/" as root, and your system must still be up and running. No need for any integrity checker.
With standard commands like chflags (BSD) or chattr (Linux), you can mark files and directories read-only (immutable) or append-only.
The point is that once you have a working system, and if you have local access to the console, you can set proper attributes to all your files.
You then have the concept of "security levels". Once your box is in multi-user mode, the "security level" can increase, and a lot of thing will be refused by the kernel : changing firewall rules, access to kmem, to raw devices, etc. and changing extended attributes.
So even if an attacker gets root access on your box, he won't be able to alter anything except some ever changing files (something that can be solved by using an NFS mount) . And the append-only log files are really nasty, because he won't be able to hide what he's doing. Patch your favorite shells to always log history files to an append-only file to get even more fun.
On a properly configured box (that you have console access on), you must be able to run "rm -rf
Non-commercial Linux distributions like Gentoo or Debian are impressive. They have more package than most commercial distros, they are actively maintainer, they have an amazing packaging system, they are free and everyone can put his finger in the pie.
.
But *commercial* distros are really important. Why? Because companies like SuSE or RedHat have a marketing force. Without them, a lot of companies would never have heard about Linux. Just like a lot of other free operating systems, Linux would have been something designed by geeks, and for geeks. SuSE, RedHat, etc. give an important professional aspect to Linux. Thanks to them, some hardware vendors gave specs or developped Linux drivers. Thanks to them, web plugins like Flash are supported on Linux. Thanks to them and their money, Linux has been ported to Intel and AMD 64 bits architectures. Thanks to them, any dummy can buy a SuSE package with a comprehensive printed manual, everything on CD's and DVD's, and get technical support.
Sure, once you are familar with Unix/Linux, you can easily use any distro, commercial or not, or even switch to BSD. But I guess a lot of people would never have installed Linux/Unix on their computer if the only thing they was given was http://www.debian.org/ or http://www.openbsd.org/
So please stop bashing commercial Linux distributions. Linux would never have been what it is nowadays without them.
The version they should upgrade to is 2.8.10, that fixes a buffer overlow that can be triggered through .htaccess files.
...and if you want to bench your internal pc speaker, install vi .
The Ebone network hasn't been shut down. I'm a pround Ebone customer, and our network is properly wor
This is true, the latest Netcraft surveys confirmed it : the Internet is dying.
Let's have a look at some numbers. According to TCP/IP's leader Richard Stevens, ehm... nothing.
How many devices connected to the Internet do I have in my toilets? Zero. This is coherent with the number of posts on Usenet whoose title is "How to upgrade my toilets to IPv6"
Movies theaters were designed so that you can go there with a girl you don't know very much, and kiss her one hour later if the film is romantic.
:
So, home theaters can't be valid substitutes for real theaters. Looking a romantic film at home with a girl you just met is
1) more difficult. "let's go to my room" sounds like a trap. "let's go to the cinema" sounds more uninterested.
2) less fruitiful. A romantic scene has more impact on an huge screen, with plenty of speakers that emphasizes the power of beautiful slow violins.
Plus: in real theaters you can always get beer, ice and popcorn.
If you define structure with public stuff but default, why the hell are you using 'class'? Use 'struct'. The only difference between 'class' and 'struct' is that 'class' has private members by default, while 'struct' has them public by default.
IMHO, comments are often confusing. A source code that has plenty of comments becomes unreadable. And comments aren't always in sync with the code when changes are made.
:
:
A source code with no comment, but whoose structure is very simple is way easier to understand. When the compiler sees long and overcomplicated expressions, it painfully transforms them into more, but basic expressions. So why not write simple code?
I often see complicated lines with plenty of ternary operator usage. Why? Write the same code with simple 'if' statements. The generated code will be exactly the same, but the source code will be easy to understand.
Another very confusing thing (IMHO) is the usage of expressions without explicit braces in loops and conditional statements. Ie. things like
if (ready())
while (*++take)
if (*take == 4)
foo();
Without indentation, it's very confusing. Worse : what if I want to add an 'else' here? If I want to add an 'else' to the second if, I really have to properly indent it to avoid confusion. If I want to add an 'else' to the first if, I have to add braces. This sort of thing doesn't ease the usage of macros and can give very nasty bugs when cutting/pasting blocks without carefully understanding where implicit braces are. So why not simply write
if (ready() != 0) {
while (*++take != 0) {
if (*take == 4) {
foo();
}
}
}
The generated code will be exacly the same, but there's no possible confusion here.
Also, 'goto' is not bad. Really. When you have to break from several loops, or just to avoid deep nesting of statements, a well placed 'goto end' is way clearer and faster than useless functions and silly 'flag_to_see_if_we_have_to_exit' variables. Don't forget that after compilation, any program will have 70% of goto-like assembler opcodes.
Comments can be interesting to note bugs, or TODO stuff.
Also have a look at the style(9) adopted by the OpenBSD team. There are good ideas.
Has anyone looked at the MicroBSD project yet?
It's based upon an OpenBSD-current kernel (so you get PF and all the great OpenBSD stuff), with FreeBSD tools, an hardened installation, custom additions and ports, a stripped-down base, etc.
This kernel looks very stable so far. The only trouble I got is with the keyboard. Sometimes, it blo
The worst thing about that virus is that it has massively hit a lot of mailing-lists.
Interesting threads on mailing lists died because of this. People got insulted although they didn't send anything. A lot of people unsubscribed from mailing-lists due to this.
So people installed antivirus software, personal firewalls, etc. The result was that on mailing-list, instead of having tons of viruses, we got tons of "alert: you have sent a virus, it has been removed by our robot", that is as frustrating as the original virus.
Thanks a lot to Microsoft for being responsible of the most annoying viruses so far.
ModLogAn is the successor of Webalizer.
It produces similar reports, but it can works with a lot of servers, including FTP servers, firewalls, a bunch of web servers, realserver, shoutcast, squid, etc.