A bug has existed since Apache 2.0.39's release that causes PHP compilation to fail under certain conditions. I'm somewhat astonished that the PHP group neglected to repair it.
A patch is publicly accessible via my webserver here (http://www.initialized.org/patches/php4.2.2-apach e2.0.39.diff).
To install the patch on a Unix machine and install PHP using apxs:
(r) designates commands that must be executed as the superuser (root).
Download the tarball. I recommend using us2.php.net, Hurricane Electric's mirror.
Execute 'patch sapi/apache2filter/php_functions.c php4.2.2-apache2.0.39.diff'. This command will apply the patch.
Execute './configure --with-apxs2'. You may specify further options (such as --with-mysql if your applications require MySQL support) following "--with-apxs2".
(r) Execute 'make'.
(r) Execute 'make install'.
(r) Restart Apache. 'apachectl restart' is the most common method of doing so.
If you have any questions or encounter difficulties, feel free to email me.;)
Be absolutely certain (*especially* when installing 3.3 remotely) that you have created an sshd user, sshd group, and/var/empty directory prior to invoking OpenSSH 3.3. These requirements must be satisfied even if you do not intend to utilize the privilege separation feature. The daemon fails to start without them.
(Disclaimer: This may be blatantly obvious to you, but I'm only attempting to help.:))
"All paid jobs absorb and degrade the mind." - Aristotle
The O'Reilly Network seems to have overlooked the fact that many individuals program open source code because they *enjoy programming*, not because they intend to generate revenue from it.
... he's replaced his "wireless iPaq" website with a more mundane version. He may have been merely attempting to advertise his URL freely to a wide range of individuals.
After all, he didn't accomplish an amazing feat. A few commands and some retail hardware will render your iPaq a wireless webserver.
Especially considering active development has ceased on source trees that have been superceded and that modern applications are sometimes much more secure than their predecessors.
Oh, and occasionally development occurs only because of a serious exploit that requires immediate attention. Let's install BIND 8.0, hoping that the script kiddies will not observe this blatant error, oblivious to the fact that experienced (cr|h)ackers would perceive exploiting such an application or operating system a trivial activity.
This concept is nothing more than an esoteric form of "security by obscurity." It disappoints me that the Slashdot editors would begin to advertise such a blatantly rhetorical and poor security practice.
He seems to be a jackofalltrades who must reference September 11 in every article he authors. You certainly aren't the only individual who isn't fond of his "work."
You do realize that Star Wars: Episode II premiered in an amount of theaters significantly less than that of Spider-Man?
You do realize that Spider-Man's marketing campaign began prior to last August, nearly a full year before its theatrical release? If I recall correctly, one of its first teaser trailers was appended to all prints of Final Fantasy: The Spirits Within, a movie that was released on July 11, 2001. (That was my AC post you read earlier.:p)
And finally, you do realize that both Spider-Man and Star Wars: Episode II are already most likely classified as "blockbusters" by the MPAA?
The narrow margin by which Spider-Man has defeated Star Wars isn't worthy of an article.
With bills such as the "Violent Video Game Protection Act" (Slashdot | CNN) becoming more prevalent in Congress, it is certainly interesting that this project was approved. I suppose that a "violent video game" is acceptable in the eyes of our government provided it propagates military propaganda. The inherent trivialization of human conflict and death is irrelevant, as long as little Billy applies to be a soldier.
If these inane bills are enacted, only first person shooters sponsored by the government will remain uncensored. Interesting.
It's truly ironic that we, The Free People (tm), must consider relocating to another country (vacating the "free" one) in order to avoid affiliating ourselves with a monopoly.
Equal rights, yeah. This country is rapidly becoming a bastardization of what it once was, courtesy of the media conglomerates.
I had strongly considered posting a response similar to this one in the worm thread appended to Slashdot earlier today.
Nearly every member of the Slashdot community is an advocate of "secure programming," but the possibility exists that we may be overlooking some of the most trivial preventative measures that could be utilized to protect our applications from intrusion.
Don't assume that the individual installing your program is competent, proficient, or intelligent. Had MS SQL been programmed in this manner, it would have never accepted logins to usernames without (strong) passwords applied. SQLsnake would most likely not have propagated as easily beyond its author's machine.
Both programmers and administrators must act responsible for an application to be configured securely. I'm certainly not suggesting that administrators should be permitted to shirk becoming educated and competent. I'm merely recommending that programmers attempt to prevent incompetency from compromising an otherwise secure application by dedicating a small amount more of time and effort.
Appromimately fifteen minutes of the Microsoft programmer's time and ten lines of code may have prevented the loss of hundreds of manhours and perhaps gigabytes of bandwidth.
I was intent on using my HP NetServer (with four Xeons) as an SMP OpenBSD machine. Unfortunately, Theo and co. haven't yet implemented any support (officially, at least) for SMP.
An SMP mailing list, CVS branch, and information page do exist, though.:)
Heh heh, it's only open source because they've modified the Gnucleus client to contain the Morpheus artwork and assorted "hidden functionalities" (I doubt that they'd distribute them as open source if they were attempting to obscure them from the public's view). The Slashdot editors accepted a pseudo-fabricated story at the beginning of the month with information about how Morpheus PE was a GPL violation. Apparently, Streamcast had not yet made the source available.
absorbing technology formerly available only to the computing elite
but we are l33t!1111111 d0nt j0 c4ll m3 c0mpu3t3r3 l3tma4m3@!!11111
1 l33t!11111
Absorbing technology? Extend and embrace?:p
I'm going to reiterate a post I made to another Slashdot "royalty" thread a few weeks ago.
The proposed royalty tree is ludicrous. After all, they're proposing that I pay *them* to give *their* "artists" free publicity. Considering I generate no revenue from the project I'm about to discuss, this is unacceptable!
I'm currently developing a web application called "laconica," which is slated for release in early 2003. Basically, the software permits the users to manipulate the playlist by vote. You could even add music to it. However, such a webcast would be almost impossible to operate legally. First, you would purchase the requisite $500 *license* to be a non-profit channel.
Now, as a non-profit broadcaster, you'd pay $0.05 per every song played. Oh, wait, but laconica is configured with six "genre channels" by default. So, per the CARP, you'd pay $0.14. Although such a small amount of money may appear affordable to casual observers, basic mathematics teaches us that it'd cost $67.20 (assuming that all songs are three minutes in duration and this is a twenty-four hour broadcast) per day to broadcast. That's $2,083.20 per month.
But don't worry, I'm certain that the RIAA will have their own manipulative, uninteractive webcasts (laden with ads) for all of us to listen to, designed solely to boost revenues. On one hand, they're ingenious. The RIAA eliminates any chance of an innovative competitor by legislating a monetary defense.
Re:there's always a deal to be found...
on
Low-end Laptops?
·
· Score: 2
They once offered me a $6 protection plan on a $3 calculator.
Civilians film a lot of the tornado footage with their home video cameras. I would suppose that it is more dramatic, considering the majority of these people don't have any training, are terrified, and escape unscathed by chance. Their emotions are in strong contrast to tornado enthusiasts, who, from most peoples' observations, usually appear intrigued, not frightened.
Of course, to capture a tornado, a number of variables must be correct and you must meet several objectives first.
Obviously, there must be light (or you must have nightvision). A great number of tornadoes occur during the night hours and probably aren't captured on film due to this reason.
You must actually locate the area of a storm that is most likely to produce a tornado. The advent of Doppler [sic, it's named after a person] radar has made this task much less difficult. Meteorologists will usually search for the classic "hook and coil" signature that is indicative of a tornado.
Finally, you must arrive at the target location before the tornado activity disippates. They usually last less than 20 minutes.
I incorrectly assigned the "superuser" label to the command 'make'. You may execute the 'make' command either as root or a normal user.
'make install', however, must be performed as root.
A patch is publicly accessible via my webserver here (http://www.initialized.org/patches/php4.2.2-apac
To install the patch on a Unix machine and install PHP using apxs:
(r) designates commands that must be executed as the superuser (root).
- Download the tarball. I recommend using us2.php.net, Hurricane Electric's mirror.
- Execute 'tar xvfz php-4.2.2.tar.gz' from a shell.
- Execute 'cd php-4.2.2'.
- Execute 'wget http://www.initialized.org/patches/php4.2.2-apach
e 2.0.39.diff'. - Execute 'patch sapi/apache2filter/php_functions.c php4.2.2-apache2.0.39.diff'. This command will apply the patch.
- Execute './configure --with-apxs2'. You may specify further options (such as --with-mysql if your applications require MySQL support) following "--with-apxs2".
- (r) Execute 'make'.
- (r) Execute 'make install'.
- (r) Restart Apache. 'apachectl restart' is the most common method of doing so.
If you have any questions or encounter difficulties, feel free to email me.-- Scoria
Be absolutely certain (*especially* when installing 3.3 remotely) that you have created an sshd user, sshd group, and /var/empty directory prior to invoking OpenSSH 3.3. These requirements must be satisfied even if you do not intend to utilize the privilege separation feature. The daemon fails to start without them.
:))
(Disclaimer: This may be blatantly obvious to you, but I'm only attempting to help.
"Brought to you by Clear Channel..."
Taco's primary motivation for Slashdotting Linux Journal are obvious:
To convince the world that PERL is superior to PHP.
(-1, Lame)
"All paid jobs absorb and degrade the mind." - Aristotle
The O'Reilly Network seems to have overlooked the fact that many individuals program open source code because they *enjoy programming*, not because they intend to generate revenue from it.
... he's replaced his "wireless iPaq" website with a more mundane version. He may have been merely attempting to advertise his URL freely to a wide range of individuals.
After all, he didn't accomplish an amazing feat. A few commands and some retail hardware will render your iPaq a wireless webserver.
Especially considering active development has ceased on source trees that have been superceded and that modern applications are sometimes much more secure than their predecessors.
Oh, and occasionally development occurs only because of a serious exploit that requires immediate attention. Let's install BIND 8.0, hoping that the script kiddies will not observe this blatant error, oblivious to the fact that experienced (cr|h)ackers would perceive exploiting such an application or operating system a trivial activity.
This concept is nothing more than an esoteric form of "security by obscurity." It disappoints me that the Slashdot editors would begin to advertise such a blatantly rhetorical and poor security practice.
GeekAustin has also authored a thread pertaining to this subject.
He seems to be a jack of all trades who must reference September 11 in every article he authors. You certainly aren't the only individual who isn't fond of his "work."
Jon,
:p)
You do realize that Star Wars: Episode II premiered in an amount of theaters significantly less than that of Spider-Man?
You do realize that Spider-Man's marketing campaign began prior to last August, nearly a full year before its theatrical release? If I recall correctly, one of its first teaser trailers was appended to all prints of Final Fantasy: The Spirits Within, a movie that was released on July 11, 2001. (That was my AC post you read earlier.
And finally, you do realize that both Spider-Man and Star Wars: Episode II are already most likely classified as "blockbusters" by the MPAA?
The narrow margin by which Spider-Man has defeated Star Wars isn't worthy of an article.
... by secrecy, I wouldn't instantly arrive at the conclusion that any of this interview (with a somewhat elusive subject) is valid. :p
With bills such as the "Violent Video Game Protection Act" (Slashdot | CNN) becoming more prevalent in Congress, it is certainly interesting that this project was approved. I suppose that a "violent video game" is acceptable in the eyes of our government provided it propagates military propaganda. The inherent trivialization of human conflict and death is irrelevant, as long as little Billy applies to be a soldier.
If these inane bills are enacted, only first person shooters sponsored by the government will remain uncensored. Interesting.
It's truly ironic that we, The Free People (tm), must consider relocating to another country (vacating the "free" one) in order to avoid affiliating ourselves with a monopoly.
Equal rights, yeah. This country is rapidly becoming a bastardization of what it once was, courtesy of the media conglomerates.
I had strongly considered posting a response similar to this one in the worm thread appended to Slashdot earlier today.
Nearly every member of the Slashdot community is an advocate of "secure programming," but the possibility exists that we may be overlooking some of the most trivial preventative measures that could be utilized to protect our applications from intrusion.
Don't assume that the individual installing your program is competent, proficient, or intelligent. Had MS SQL been programmed in this manner, it would have never accepted logins to usernames without (strong) passwords applied. SQLsnake would most likely not have propagated as easily beyond its author's machine.
Both programmers and administrators must act responsible for an application to be configured securely. I'm certainly not suggesting that administrators should be permitted to shirk becoming educated and competent. I'm merely recommending that programmers attempt to prevent incompetency from compromising an otherwise secure application by dedicating a small amount more of time and effort.
Appromimately fifteen minutes of the Microsoft programmer's time and ten lines of code may have prevented the loss of hundreds of manhours and perhaps gigabytes of bandwidth.
Symantec has produced a more informative bulletin; however, they have entitled the worm "Digispid" as opposed to SQLsnake.
I was intent on using my HP NetServer (with four Xeons) as an SMP OpenBSD machine. Unfortunately, Theo and co. haven't yet implemented any support (officially, at least) for SMP.
:)
An SMP mailing list, CVS branch, and information page do exist, though.
Heh heh, it's only open source because they've modified the Gnucleus client to contain the Morpheus artwork and assorted "hidden functionalities" (I doubt that they'd distribute them as open source if they were attempting to obscure them from the public's view). The Slashdot editors accepted a pseudo-fabricated story at the beginning of the month with information about how Morpheus PE was a GPL violation. Apparently, Streamcast had not yet made the source available.
Will somebody please enlighten me as to how my post was a troll? Unfair moderation really sucks.
absorbing technology formerly available only to the computing elite but we are l33t!1111111 d0nt j0 c4ll m3 c0mpu3t3r3 l3tma4m3@!!11111 1 l33t!11111 Absorbing technology? Extend and embrace? :p
You add the music by submitting the MP3; people then preview it, and, provided it's good, vote it higher.
Har har.
the letter A's placement.
I'm going to reiterate a post I made to another Slashdot "royalty" thread a few weeks ago.
The proposed royalty tree is ludicrous. After all, they're proposing that I pay *them* to give *their* "artists" free publicity. Considering I generate no revenue from the project I'm about to discuss, this is unacceptable!
I'm currently developing a web application called "laconica," which is slated for release in early 2003. Basically, the software permits the users to manipulate the playlist by vote. You could even add music to it. However, such a webcast would be almost impossible to operate legally. First, you would purchase the requisite $500 *license* to be a non-profit channel.
Now, as a non-profit broadcaster, you'd pay $0.05 per every song played. Oh, wait, but laconica is configured with six "genre channels" by default. So, per the CARP, you'd pay $0.14. Although such a small amount of money may appear affordable to casual observers, basic mathematics teaches us that it'd cost $67.20 (assuming that all songs are three minutes in duration and this is a twenty-four hour broadcast) per day to broadcast. That's $2,083.20 per month. But don't worry, I'm certain that the RIAA will have their own manipulative, uninteractive webcasts (laden with ads) for all of us to listen to, designed solely to boost revenues. On one hand, they're ingenious. The RIAA eliminates any chance of an innovative competitor by legislating a monetary defense.
They once offered me a $6 protection plan on a $3 calculator.
IANAM (I am not a meteorologist), but...
Civilians film a lot of the tornado footage with their home video cameras. I would suppose that it is more dramatic, considering the majority of these people don't have any training, are terrified, and escape unscathed by chance. Their emotions are in strong contrast to tornado enthusiasts, who, from most peoples' observations, usually appear intrigued, not frightened.
Of course, to capture a tornado, a number of variables must be correct and you must meet several objectives first.
Obviously, there must be light (or you must have nightvision). A great number of tornadoes occur during the night hours and probably aren't captured on film due to this reason.
You must actually locate the area of a storm that is most likely to produce a tornado. The advent of Doppler [sic, it's named after a person] radar has made this task much less difficult. Meteorologists will usually search for the classic "hook and coil" signature that is indicative of a tornado.
Finally, you must arrive at the target location before the tornado activity disippates. They usually last less than 20 minutes.
That was an utterly wonderful troll.