please, mods, please stop encouraging these morons. all your base isn't funny. "clever" rewording of the same formula isn't funny. it stopped being funny a long time ago. it could have still been funny ocassionally, but assholes, like this one, ruined it. its dead. it hurts me to read it.
it hurts you to read it? ouch, sounds like you are a bit uptight, try to have some fun sometimes. as for me being an 'asshole' feel free to look over my other past posts, they're usually not this funny. Oh, and just so you know:
Let me be the first to recommend n00bs pick up Snort for Dummies, perhaps the best "for Dummies" book I've read; a perfect primer. "If you want to get your feet wet or you've been tasked with deploying a snort system, this is a good way to start. In the typical, humorous, "for dummies" style, this book walks you through getting, setting up and using Snort and the ACID console.
The book also covers how to maintain and tweak the system, once it is up and running. A good effort by the authors." For work or for home, there's really no reason not to learn an enterprise level IDS.
It takes a community...
on
Open Sources 2.0
·
· Score: 4, Interesting
This book should be much more relevant now that the 'dot-com' hype has disappated and people can see the fruits of real community supported development. When you see how poorly properitary software companies are run (I'm talking about the ones I('ve) work(ed) for); things like that are not tolerated in OSS. If push comes to shove (I'm looking at you XFree86) a fork may develop giving users a true option that could become superior to it's ancestor. The burning man ref seems a bit off, as that's not people being realy, it's a vacation. OSS is real in that real work gets done by someone everyday (unlike me at my job...)
"White House cybersecurity adviser, argued at a seminar in London that programmers should be held responsible for flaws in code they write
"The problem with that is when an employee writes code for a company, it becomes the companies' code, so it would follow that any litigation should fall on the company, and not the programmer. I would also argue that the programmer doesn't release the software, that's up to the company which *should* have testing and QA measures in place to find bugs and insecurity.
Looks very nice, but what stes it apart from free alternatives? From your site I see that, "RocketPost is $149 per license", which seems steep. What is the selling point above other blog posters? Thanks, looks like some nice work.
nice, also without giving away too much detail let's just say that I was allowed access to a certain companies' CVS server passwd file to run a password audit against it. Needless to say, 'password' 'default' 'tomato' or the users username are not good passwords to protect a companies' proprietary source code! The kicker? I know they still haven't implemented a password change policy on the server...
sloppy admining is everywhere unfortunately; it's seen as more of a nuisance rather than a safeguard. It's just pervasive, and even when new projects are brought onboard at my company, the password ends up being the username's name, or -blank-. I even wrote an article about my recent experience with this at work: Password deficiency in the workplace where the person implementing the software said, "Well, there's a password, it's not a really good password, and it's the same for everybody (hehe)" Yeah, she said that...and then laughed - during the presentation introducing the project to the team.
(yeah, even the timesheet software has the same password -FOR ALL USERS!-)
I'm neither a java or php programmer, but I do work with both. While java is nice and portable, I'm very impressed with how far PHP (Personal Home Page) has gone. There are acclerator projects out there that cache php scripts, making them much more responsive. I use eAceelerator (formerly MmTURKE Cache or something like that) and it's obvious that php performance can be improved. For many a simple LAMP setup is very powerful, I've been using it for a website, as well as webmail, for over 4 years now.
Let's hope all the FOSS projects they support won't be effected; Hula / Beagle / Evolution / GNOME / LDTP / MONO / Mozilla / OpenOffice and UDDI are worked on by many employees. Last I heard they employed about 50 people just to work on Hula, and their overall view to FOSS has been excellent. Having worked with some of them on the project, I am amazed at the support they've recieved from Novell; let's hope it continues.
I agree, the blogger they include is pretty basic, but I like the idea of having one integrated in the browser. did you see how you can highlight text and have it populate in the blog editor? or the shelf? I think those are two, if basic, new options that are pretty cool. hmmm...maybe there's an extention for FF for a similar tool.
Yep, I didn't RTFA - so a stumble on my part. Ok, so he's Indian, what would be the equv to an Arab as Indians are to us? Hmm...prob nothing. How about a Greek person?
built in blogging tools, plus you can highlight text/urls/images, right click and choose 'blog this'. I like the 'shelf' allot; a small window that allows you to drag blocks of text to blog with later. favorites automatically upates your del.ico.us bookmarks - that's nifty...it sorta feels like a pimped out FF with a bunch of extentions, but they are pretty helpful, and cool if you want to blog allot. will it change the world? no, but it may allow ppl to work more efficiently with their online browsing/colaboration.
The thing is, the execs that have to make these decisions are used to having a big company behind their Unix OS and are more comfortable with Windows in general, so just that alone works against Linux migration. Still, time will come as this generation quickly moves up the ladder and becomes the decision makers; the value of Linux and BSD will not be overlooked as it is today. While Linux has captured a good market, this will acclerate much more as the years go by.
Alternative APT source maintained by Sam Vilain:
deb http://apt.utsl.gen.nz/debian <distname> all
# where <distname> is one of woody, sarge, sid, warty, hoary or breezy
Re:What do you use for Rails? FCGI, FCGID, or SCGI
on
What is Ruby on Rails?
·
· Score: 1
1.2G Athlon 512M PC133 RAM 20Gig IBM 80Gig Western Digital NIC some 10/100 3com FreeBSD 6.0 (RELENG_6) Speakeasy 1.5/384 ADSL
As pointed out by others, the bottleneck was def the DSL - but the server was working pretty hard. I'll post some more detailed stats, but suffice to say, over 95,000 hits for 10/15 was a new rekerd for my home server.
I'm always facinated to see what stands the test of time, obvious good food stays around, just take beer (just not mine!) for example:
More than 6,000 years ago, the refreshing qualities of beer were recognized and enjoyed, and ancient peoples have left records to indicate that they took the brewing of this thirst-quenching beverage very seriously.
The Chinese, Inca, African, Babylonian, Assyrian, Egyptian, Hebrew and Saxon are just a few civilizations in which beer has been associated with family life, friendship, romance and celebrations. Through the years it has been immortalized in songs, stories, poems, and legends. Although the taste of beer has changed over the last few thousand years, the enjoyment has remained constant. Other than water and tea, beer is the most popular beverage on earth. When today's beer drinkers lift a frosty mug of their favorite brew, they can do so knowing that they are in good company, sharing a kinship with pharaohs, kings, queens, statesmen, literary giants and explorers.
Today, as in the past, beer has no cultural boundaries. Its long tradition of providing enjoyable refreshment to consumers continues.
Re:What do you use for Rails? FCGI, FCGID, or SCGI
on
What is Ruby on Rails?
·
· Score: 1
That's a good question, basically it's just the way Typo's FreeBSD howto said to do it if you already have an exisiting Apache install. It's silly to run two webservers, however I also did want to try out Lighttpd since I had heard good things. I like it, and if it can do all I need Apache for, I may migrate to it, again, just because and to learn new stuff. On the other hand, would be interesting to learn how to make mod_fcgi do it, so there's another route.
Re:What do you use for Rails? FCGI, FCGID, or SCGI
on
What is Ruby on Rails?
·
· Score: 1
I use mod_fastcgi, as it's the general way most ppl use it with Typo. I still have Apache2 on:80, but use mod_proxy to pass any request for *fak3r to:3000 where Lighttpd picks it up and then hands it to fastcgi if a database call is needed. From lighttpd.conf:
Yep, mostly what I'm seeing (apache's http-access.log and typo/logs) are straight web-server access (mod_proxy on apache -> lighttpd) but plenty of 'live searches' (which is why I suggested it) when fcgi (dispatch.fcgi) takes over and chats with the database. Still, even those are coming back faster than I'd expected. Yes, I've had 1 minute refreshes of the front page, but I didn't expect it to be perfect, I've just never had this kinda sustained traffic to study, and am really impressed with how Typo/Lighttpd are working.
It's just something when it's a box that you built by hand from newegg parts, then installed/tweaked freebsd on, and then setup a new blog just a few weeks back, to see it perform.
Me as well, I've never seen it this slow, but yeah, the server still has plenty of RAM/proc overhead, so it's just waiting on requests through the DSL. Even typing through ssh is s-l-o-w, but hey, this is why I built the box - now maybe my wife will see the value in Speakeasy's 6.0/768 DSL! (currently sporting 1.5/384)
Once things calm down I'll get some stats on what the webserver was able to do, and how many DB requests fcgi was able to carry out. Top is showing ruby (fcgi) running as high as 33% at times, with mysql usually below 1% still.
Agreed, it is a pointless trend, and I always enjoy hitting those links only to find the site ARE NOT XHTML 1.0 valid. No, mine is not, and I took that out of the footer, but that was the cached page, so it got overwritten. Still learning Typo, but I will take that out, and yes, it's misspelt - that's the way it came from Typo! Hey, maybe I'll sub my 1st patch to the project, thanks for pointing it out.
Oh, and yeah, the site that demos the Ruby On Rails framework with Typo is fak3r.com - thanks for helping me load test Lighttpd!
Slashdot Mirror
it hurts you to read it? ouch, sounds like you are a bit uptight, try to have some fun sometimes. as for me being an 'asshole' feel free to look over my other past posts, they're usually not this funny. Oh, and just so you know:
You have no chance to survive make your time.
HA HA HA HA
"All your .com domains are belong to US"
Let me be the first to recommend n00bs pick up Snort for Dummies, perhaps the best "for Dummies" book I've read; a perfect primer. "If you want to get your feet wet or you've been tasked with deploying a snort system, this is a good way to start. In the typical, humorous, "for dummies" style, this book walks you through getting, setting up and using Snort and the ACID console. The book also covers how to maintain and tweak the system, once it is up and running. A good effort by the authors." For work or for home, there's really no reason not to learn an enterprise level IDS.
This book should be much more relevant now that the 'dot-com' hype has disappated and people can see the fruits of real community supported development. When you see how poorly properitary software companies are run (I'm talking about the ones I('ve) work(ed) for); things like that are not tolerated in OSS. If push comes to shove (I'm looking at you XFree86) a fork may develop giving users a true option that could become superior to it's ancestor. The burning man ref seems a bit off, as that's not people being realy, it's a vacation. OSS is real in that real work gets done by someone everyday (unlike me at my job...)
Right, I'm not arguing that point, but once the rights are the companies', shouldn't the liability be the companies' as well? I'm arguing 'yes'.
- "White House cybersecurity adviser, argued at a seminar in London that programmers should be held responsible for flaws in code they write
"The problem with that is when an employee writes code for a company, it becomes the companies' code, so it would follow that any litigation should fall on the company, and not the programmer. I would also argue that the programmer doesn't release the software, that's up to the company which *should* have testing and QA measures in place to find bugs and insecurity.Looks very nice, but what stes it apart from free alternatives? From your site I see that, "RocketPost is $149 per license", which seems steep. What is the selling point above other blog posters? Thanks, looks like some nice work.
nice, also without giving away too much detail let's just say that I was allowed access to a certain companies' CVS server passwd file to run a password audit against it. Needless to say, 'password' 'default' 'tomato' or the users username are not good passwords to protect a companies' proprietary source code! The kicker? I know they still haven't implemented a password change policy on the server...
sloppy admining is everywhere unfortunately; it's seen as more of a nuisance rather than a safeguard. It's just pervasive, and even when new projects are brought onboard at my company, the password ends up being the username's name, or -blank-. I even wrote an article about my recent experience with this at work: Password deficiency in the workplace where the person implementing the software said, "Well, there's a password, it's not a really good password, and it's the same for everybody (hehe)" Yeah, she said that...and then laughed - during the presentation introducing the project to the team.
(yeah, even the timesheet software has the same password -FOR ALL USERS!-)
I'm neither a java or php programmer, but I do work with both. While java is nice and portable, I'm very impressed with how far PHP (Personal Home Page) has gone. There are acclerator projects out there that cache php scripts, making them much more responsive. I use eAceelerator (formerly MmTURKE Cache or something like that) and it's obvious that php performance can be improved. For many a simple LAMP setup is very powerful, I've been using it for a website, as well as webmail, for over 4 years now.
Let's hope all the FOSS projects they support won't be effected; Hula / Beagle / Evolution / GNOME / LDTP / MONO / Mozilla / OpenOffice and UDDI are worked on by many employees. Last I heard they employed about 50 people just to work on Hula, and their overall view to FOSS has been excellent. Having worked with some of them on the project, I am amazed at the support they've recieved from Novell; let's hope it continues.
I agree, the blogger they include is pretty basic, but I like the idea of having one integrated in the browser. did you see how you can highlight text and have it populate in the blog editor? or the shelf? I think those are two, if basic, new options that are pretty cool. hmmm...maybe there's an extention for FF for a similar tool.
Yep, I didn't RTFA - so a stumble on my part. Ok, so he's Indian, what would be the equv to an Arab as Indians are to us? Hmm...prob nothing. How about a Greek person?
built in blogging tools, plus you can highlight text/urls/images, right click and choose 'blog this'. I like the 'shelf' allot; a small window that allows you to drag blocks of text to blog with later. favorites automatically upates your del.ico.us bookmarks - that's nifty...it sorta feels like a pimped out FF with a bunch of extentions, but they are pretty helpful, and cool if you want to blog allot. will it change the world? no, but it may allow ppl to work more efficiently with their online browsing/colaboration.
Who will play Apu? They should get the original guy, or someone with a heavy Southern US accent to turn the tables!
The thing is, the execs that have to make these decisions are used to having a big company behind their Unix OS and are more comfortable with Windows in general, so just that alone works against Linux migration. Still, time will come as this generation quickly moves up the ladder and becomes the decision makers; the value of Linux and BSD will not be overlooked as it is today. While Linux has captured a good market, this will acclerate much more as the years go by.
Another one here:
1 -4-6-release-for-debian
http://rubyists.com/articles/2005/10/12/lighttpd-
Ubuntu (request for inclusion)
Debian (request for inclusion)
Alternative APT source maintained by Sam Vilain:
deb http://apt.utsl.gen.nz/debian <distname> all
# where <distname> is one of woody, sarge, sid, warty, hoary or breezy
or another APT source maintained by bougyman:
deb http://debian.bougyman.com/ unstable main
1.2G Athlon
512M PC133 RAM
20Gig IBM
80Gig Western Digital
NIC some 10/100 3com
FreeBSD 6.0 (RELENG_6)
Speakeasy 1.5/384 ADSL
As pointed out by others, the bottleneck was def the DSL - but the server was working pretty hard. I'll post some more detailed stats, but suffice to say, over 95,000 hits for 10/15 was a new rekerd for my home server.
That's a good question, basically it's just the way Typo's FreeBSD howto said to do it if you already have an exisiting Apache install. It's silly to run two webservers, however I also did want to try out Lighttpd since I had heard good things. I like it, and if it can do all I need Apache for, I may migrate to it, again, just because and to learn new stuff. On the other hand, would be interesting to learn how to make mod_fcgi do it, so there's another route.
Yep, mostly what I'm seeing (apache's http-access.log and typo/logs) are straight web-server access (mod_proxy on apache -> lighttpd) but plenty of 'live searches' (which is why I suggested it) when fcgi (dispatch.fcgi) takes over and chats with the database. Still, even those are coming back faster than I'd expected. Yes, I've had 1 minute refreshes of the front page, but I didn't expect it to be perfect, I've just never had this kinda sustained traffic to study, and am really impressed with how Typo/Lighttpd are working.
It's just something when it's a box that you built by hand from newegg parts, then installed/tweaked freebsd on, and then setup a new blog just a few weeks back, to see it perform.
Me as well, I've never seen it this slow, but yeah, the server still has plenty of RAM/proc overhead, so it's just waiting on requests through the DSL. Even typing through ssh is s-l-o-w, but hey, this is why I built the box - now maybe my wife will see the value in Speakeasy's 6.0/768 DSL! (currently sporting 1.5/384) Once things calm down I'll get some stats on what the webserver was able to do, and how many DB requests fcgi was able to carry out. Top is showing ruby (fcgi) running as high as 33% at times, with mysql usually below 1% still.
Agreed, it is a pointless trend, and I always enjoy hitting those links only to find the site ARE NOT XHTML 1.0 valid. No, mine is not, and I took that out of the footer, but that was the cached page, so it got overwritten. Still learning Typo, but I will take that out, and yes, it's misspelt - that's the way it came from Typo! Hey, maybe I'll sub my 1st patch to the project, thanks for pointing it out.
Oh, and yeah, the site that demos the Ruby On Rails framework with Typo is fak3r.com - thanks for helping me load test Lighttpd!