A couple Christmases ago, I gave my brother the audio version of A Short History of Nearly Everything by Bill Bryson. I think it's around six hours long. At the time, he had a four hour daily commute, so he breezed through it pretty quickly, but he seemed to enjoy it. Amazon has it for under twenty bucks. Might be worth a shot.
I've read Slashdot over really slow dialup links from Thailand, mainly Bangkok, but a couple times in Hua-Hin and I think Chiang Mai too. Reading something like Slashdot over flakey phones lines makes you appreciate websites that aren't laid out in tables. Because it's all tables, whatever browser I was using at the time didn't like displaying anything until the whole page was loaded. I eventually switched to the "light" version of the site, but even that was painfully slow.
That's great, except Kerry voted for the PATRIOT Act ("non-Bush" realistically means Kerry). Of course, Kerry is against the thing now, but that doesn't really help us, does it? When it counted, he made the wrong decision. All his complaining now isn't worth a damn.
The problem with removing strcat and strcpy is that you can use them safely if you put some thought into what you're doing. There's no reason to ban them from libc just because some programmers don't check their buffer sizes. Removing the old string functions would make a lot of code not work on OpenBSD.
Also, the OpenBSD team isn't going to touch most of the third party code in the tree: "We are obviously not doing this to some parts of the tree which we borrow from other projects. In particular, the gnu part of the tree might remain largely dirty." So they'd kill a lot of functionality by banning them. They did make the changes in OpenSSL and Apache and it sounds like they've had some luck convincing the BIND and Sendmail guys to move to strl. It's obvious OpenBSD knows you can't change the world, but they can change their neighborhood and set a good example.
What they might end up doing in the future is adding a compile time warning similar to the one generated by mktemp that suggests using mkstemp instead. That's probably the best approach.
Aha! Good question. The IPv4 security bit will not be implemented on OpenBSD because IPv4 support has been dropped. Todd Fries says, "It is too hard to get IPv4 addresses, we're switching to IPv6 tomorrow."
(This post is a day late, of course, so just pretend it's still the 1st.)
Yes and no. spamd uses whatever list you give it. pf just forwards any incoming SMTP connections from a certain list of hosts to the spamd. Theo suggests using lists from Spews. However, Daniel uses bmf to build his own blacklist. If you want to get your point across to open relays, go the Spews route. If you want a solution with less collateral damage, use Daniel's approach.
This is the same thing as OpenBSD's spamd, which Theo de Raadt wrote specifically to cause spam relays pain. spamd uses some new features of pf and blacklists from Spews to create a tarpit for incoming messages from known spam relays. It was even discussed on Slashdot in this article. Also, Daniel Hartmeier, pf developer extraordinaire and all around good guy, wrote a little piece about annoying spammers using pf, spamd, and bmf.
I don't think they are better at chess. I think the computers are just better at the things that are useful in chess. They can analyze moves faster and remember more about their opponent's technique than their human creators. Given enough time and maybe a notebook to keep track of stuff, you could accomplish the same thing. The computer is using the same basic chess rules that everyone else uses. The difference here is the computer can apply the rules ridiculously fast.
On a similar note, I noticed that AOL causes a lot of DNS lookups. From what I can see from my firewall logs, each TCP connection from an AOL user is handled by a separate proxy. Each proxy then does its own lookup on the host. So, for a normal sized webpage with some images or whatever, you get like 10 TCP connections for the content and 10 UDP connections for the DNS lookup. Seems kind of excessive to me.
No, they get nearly all of the money from their album sales. Their management company Q Prime discussed this in an interview that appeared in a recent issue of "So What?" magazine. They have one of the best contracts in the business because they renegotiated it sometime around 1990, give or take a year or two.
Do you know why Metallica got pissed? They have one of the best record deals in the industry because way back around 1990, Elektra realized how important Metallica was. I forget the exact numbers, but they get nearly all of the money from album sales, unlike most other bands who only get a few pennies. Also, they lost more money paying lawyers than they did to lost album sales. They readily admit this. It wasn't about the money, it was a matter of principle. Very few people stand up for their beliefs these days.
You are wrong. The definition you cite for affected is not relevent as it is an adjective. The word in question is effect, which you used as a verb in your sentence: "Let me just remind you all that this bug does NOT effect the OS/2 Warp 3.0 kernel."
From dictionary.com, definition 1 of affect: "To have an influence on or effect a change in."
Also from dictionary.com, effect as a verb means "To produce, as a cause or agent; to cause to be." or "To bring to pass; to execute; to enforce; to achieve; to accomplish."
The leak isn't producing, executing, enforcing, achieving, or accomplishing FreeBSD. It is, however, having an influence or effect on FreeBSD.
So, your grammar argument is completely wrong. Technically, however, your original sentence isn't completely wrong because the bug does not effect OS/2. In this context, you really meant that is does not affect OS/2.
I had the same problem with my host entry at NSI. My IP changed, so I went through the process of trying to change it via their stupid email system. No matter what I tried, it would never approve me. Eventually I just gave up and used other hosts. I just checked the NSI site and they've changed the host management stuff to a simple webform. So, I submitted the changes I've been wanting to make for nearly a year and they went through without a problem.
It's still a rip-off though. I have one domain at Go Daddy and pay like 9 bucks a year instead of 35 at NSI.
I have this very card in two boxes, one FreeBSD and the other OpenBSD. I knew the card wasn't fancy, but I figured it was at least halfway decent so I was a bit disappointed when I read your post. The same comment is in/usr/src/sys/dev/ic/rtl81x9.c on OpenBSD. I found this a few paragraphs after what you already posted:
* It's impossible given this rotten design to really achieve decent
* performance at 100Mbps, unless you happen to have a 400Mhz PII or
* some equally overmuscled CPU to drive it.
*
Good thing my CPU is sufficiently overmuscled, by their standards at least;).
While neither in Linux nor in the the kernel, there is some humor in shutdown.c (/usr/src/sbin/shutdown) in both FreeBSD and OpenBSD. The function die_you_gravy_sucking_pig_dog gave me a good laugh when I saw it the first time.
I agree completely. I'm a senior in college now. After my freshman year, I got a pretty cool internship with a business-to-business start-up. I worked at the same place the next summer, but did different stuff. I liked my work, but I hated the company. They downsized after two years of wasteful spending and I got cut. So, this past summer I was stuck without a job. A neighbor of mine owns a landscaping company, so I went to work for him. I went from 18 bucks an hour writing code in an air-conditioned office in Boston to 8 bucks an hour mowing lawns and pulling weeds around my area. It was the best job of my life.
The work day was better: 7 AM to 3 or 4 PM with a 4 minute commute, compared to 7 AM to 7 PM including a long commute. I got exercise. I got a tan for the first time since I started college. I got to do other stuff in the late afternoon and every evening. The guys I worked with were stereotypical manual labor guys, but they were great to work with. They cared more about having fun and enjoying their lives than the people at the start-up. It was really nice to interact with people like that for a change.
I think my dream job would be working at some company writing code and mowing their lawn when I need a break from the computer.
I haven't used Red Hat since 6.0 (I think) or Mandrake at all, but I think the OpenBSD installer is outstanding. I even like it better than FreeBSD's somewhat fancier installer. OpenBSD was my first serious experience with a Unix-like OS. I had a dual boot with Windows and Red Hat and then Windows and Slackware, but never used the Linux partition so they don't really count. When I got a cheap box, I read the installation FAQ for OpenBSD and installed without a problem. It's straightforward and fast (under 30 minutes with an FTP install and being very careful about what I typed). So, try harder to convince your friends because the install really isn't that bad.
I don't see how it's wrong to send it back to the open relay. They are saying, "Here, have this," and you are just replying, "Not right now, thanks." That's perfectly valid use of SMTP codes. It's not like you launch an attack every time you get email from these relays, you're just telling them you don't want it right now. The idea is just to take the pain of SPAM away from the user and give it to the ones responsible (to some extent) for it. The open relays caused it, they should deal with it.
The kid that lived next door to me my freshman year in college was addicted to EverQuest. I asked him how much he played once, and he showed me the cumulative time he had been playing on just one of his characters: 54 days. It's scary considering he didn't start playing until a few month into freshman year. He didn't come back sophomore year...
Don't forget systrace, which lets a program have only the privileges it needs. Check out Project Hairy Eyeball, which is a collection of systrace policies (some of them from OpenBSD developers themselves). They just released version 1.1 of their policies.
I'm wondering if there are plans to use systrace to get around the super-user requirement for binding to low ports. That would pretty cool.
I've never heard of it either. Google found this for me. You might be interested in going straight to the What is Extreme Programming page. Based on my quick look through their pages, it seems like just another buzz word for something that isn't really exciting (ooooh, listening to customers and testing throughout the development cycle!? How revolutionary!)
Slashdot Mirror
A couple Christmases ago, I gave my brother the audio version of A Short History of Nearly Everything by Bill Bryson. I think it's around six hours long. At the time, he had a four hour daily commute, so he breezed through it pretty quickly, but he seemed to enjoy it. Amazon has it for under twenty bucks. Might be worth a shot.
I thought this was the virgin model.
He doesn't want to be in power. He wants (the universal) you to be in power. That's the whole point.
Being in cement is no big deal, it's getting stuck in concrete that causes problems.
I've read Slashdot over really slow dialup links from Thailand, mainly Bangkok, but a couple times in Hua-Hin and I think Chiang Mai too. Reading something like Slashdot over flakey phones lines makes you appreciate websites that aren't laid out in tables. Because it's all tables, whatever browser I was using at the time didn't like displaying anything until the whole page was loaded. I eventually switched to the "light" version of the site, but even that was painfully slow.
That's great, except Kerry voted for the PATRIOT Act ("non-Bush" realistically means Kerry). Of course, Kerry is against the thing now, but that doesn't really help us, does it? When it counted, he made the wrong decision. All his complaining now isn't worth a damn.
The problem with removing strcat and strcpy is that you can use them safely if you put some thought into what you're doing. There's no reason to ban them from libc just because some programmers don't check their buffer sizes. Removing the old string functions would make a lot of code not work on OpenBSD.
Also, the OpenBSD team isn't going to touch most of the third party code in the tree: "We are obviously not doing this to some parts of the tree which we borrow from other projects. In particular, the gnu part of the tree might remain largely dirty." So they'd kill a lot of functionality by banning them. They did make the changes in OpenSSL and Apache and it sounds like they've had some luck convincing the BIND and Sendmail guys to move to strl. It's obvious OpenBSD knows you can't change the world, but they can change their neighborhood and set a good example.
What they might end up doing in the future is adding a compile time warning similar to the one generated by mktemp that suggests using mkstemp instead. That's probably the best approach.
Aha! Good question. The IPv4 security bit will not be implemented on OpenBSD because IPv4 support has been dropped. Todd Fries says, "It is too hard to get IPv4 addresses, we're switching to IPv6 tomorrow."
(This post is a day late, of course, so just pretend it's still the 1st.)
Yes and no. spamd uses whatever list you give it. pf just forwards any incoming SMTP connections from a certain list of hosts to the spamd. Theo suggests using lists from Spews. However, Daniel uses bmf to build his own blacklist. If you want to get your point across to open relays, go the Spews route. If you want a solution with less collateral damage, use Daniel's approach.
This is the same thing as OpenBSD's spamd, which Theo de Raadt wrote specifically to cause spam relays pain. spamd uses some new features of pf and blacklists from Spews to create a tarpit for incoming messages from known spam relays. It was even discussed on Slashdot in this article. Also, Daniel Hartmeier, pf developer extraordinaire and all around good guy, wrote a little piece about annoying spammers using pf, spamd, and bmf.
I don't think they are better at chess. I think the computers are just better at the things that are useful in chess. They can analyze moves faster and remember more about their opponent's technique than their human creators. Given enough time and maybe a notebook to keep track of stuff, you could accomplish the same thing. The computer is using the same basic chess rules that everyone else uses. The difference here is the computer can apply the rules ridiculously fast.
On a similar note, I noticed that AOL causes a lot of DNS lookups. From what I can see from my firewall logs, each TCP connection from an AOL user is handled by a separate proxy. Each proxy then does its own lookup on the host. So, for a normal sized webpage with some images or whatever, you get like 10 TCP connections for the content and 10 UDP connections for the DNS lookup. Seems kind of excessive to me.
No, they get nearly all of the money from their album sales. Their management company Q Prime discussed this in an interview that appeared in a recent issue of "So What?" magazine. They have one of the best contracts in the business because they renegotiated it sometime around 1990, give or take a year or two.
Now go away.
Do you know why Metallica got pissed? They have one of the best record deals in the industry because way back around 1990, Elektra realized how important Metallica was. I forget the exact numbers, but they get nearly all of the money from album sales, unlike most other bands who only get a few pennies. Also, they lost more money paying lawyers than they did to lost album sales. They readily admit this. It wasn't about the money, it was a matter of principle. Very few people stand up for their beliefs these days.
You are wrong. The definition you cite for affected is not relevent as it is an adjective. The word in question is effect, which you used as a verb in your sentence: "Let me just remind you all that this bug does NOT effect the OS/2 Warp 3.0 kernel."
From dictionary.com, definition 1 of affect: "To have an influence on or effect a change in."
Also from dictionary.com, effect as a verb means "To produce, as a cause or agent; to cause to be." or "To bring to pass; to execute; to enforce; to achieve; to accomplish."
The leak isn't producing, executing, enforcing, achieving, or accomplishing FreeBSD. It is, however, having an influence or effect on FreeBSD.
So, your grammar argument is completely wrong. Technically, however, your original sentence isn't completely wrong because the bug does not effect OS/2. In this context, you really meant that is does not affect OS/2.
I had the same problem with my host entry at NSI. My IP changed, so I went through the process of trying to change it via their stupid email system. No matter what I tried, it would never approve me. Eventually I just gave up and used other hosts. I just checked the NSI site and they've changed the host management stuff to a simple webform. So, I submitted the changes I've been wanting to make for nearly a year and they went through without a problem.
It's still a rip-off though. I have one domain at Go Daddy and pay like 9 bucks a year instead of 35 at NSI.
I have this very card in two boxes, one FreeBSD and the other OpenBSD. I knew the card wasn't fancy, but I figured it was at least halfway decent so I was a bit disappointed when I read your post. The same comment is in /usr/src/sys/dev/ic/rtl81x9.c on OpenBSD. I found this a few paragraphs after what you already posted:
;).
* It's impossible given this rotten design to really achieve decent
* performance at 100Mbps, unless you happen to have a 400Mhz PII or
* some equally overmuscled CPU to drive it.
*
Good thing my CPU is sufficiently overmuscled, by their standards at least
While neither in Linux nor in the the kernel, there is some humor in shutdown.c (/usr/src/sbin/shutdown) in both FreeBSD and OpenBSD. The function die_you_gravy_sucking_pig_dog gave me a good laugh when I saw it the first time.
I agree completely. I'm a senior in college now. After my freshman year, I got a pretty cool internship with a business-to-business start-up. I worked at the same place the next summer, but did different stuff. I liked my work, but I hated the company. They downsized after two years of wasteful spending and I got cut. So, this past summer I was stuck without a job. A neighbor of mine owns a landscaping company, so I went to work for him. I went from 18 bucks an hour writing code in an air-conditioned office in Boston to 8 bucks an hour mowing lawns and pulling weeds around my area. It was the best job of my life.
The work day was better: 7 AM to 3 or 4 PM with a 4 minute commute, compared to 7 AM to 7 PM including a long commute. I got exercise. I got a tan for the first time since I started college. I got to do other stuff in the late afternoon and every evening. The guys I worked with were stereotypical manual labor guys, but they were great to work with. They cared more about having fun and enjoying their lives than the people at the start-up. It was really nice to interact with people like that for a change.
I think my dream job would be working at some company writing code and mowing their lawn when I need a break from the computer.
I haven't used Red Hat since 6.0 (I think) or Mandrake at all, but I think the OpenBSD installer is outstanding. I even like it better than FreeBSD's somewhat fancier installer. OpenBSD was my first serious experience with a Unix-like OS. I had a dual boot with Windows and Red Hat and then Windows and Slackware, but never used the Linux partition so they don't really count. When I got a cheap box, I read the installation FAQ for OpenBSD and installed without a problem. It's straightforward and fast (under 30 minutes with an FTP install and being very careful about what I typed). So, try harder to convince your friends because the install really isn't that bad.
I don't see how it's wrong to send it back to the open relay. They are saying, "Here, have this," and you are just replying, "Not right now, thanks." That's perfectly valid use of SMTP codes. It's not like you launch an attack every time you get email from these relays, you're just telling them you don't want it right now. The idea is just to take the pain of SPAM away from the user and give it to the ones responsible (to some extent) for it. The open relays caused it, they should deal with it.
The kid that lived next door to me my freshman year in college was addicted to EverQuest. I asked him how much he played once, and he showed me the cumulative time he had been playing on just one of his characters: 54 days. It's scary considering he didn't start playing until a few month into freshman year. He didn't come back sophomore year...
Don't forget systrace, which lets a program have only the privileges it needs. Check out Project Hairy Eyeball, which is a collection of systrace policies (some of them from OpenBSD developers themselves). They just released version 1.1 of their policies.
I'm wondering if there are plans to use systrace to get around the super-user requirement for binding to low ports. That would pretty cool.
I've never heard of it either. Google found this for me. You might be interested in going straight to the What is Extreme Programming page. Based on my quick look through their pages, it seems like just another buzz word for something that isn't really exciting (ooooh, listening to customers and testing throughout the development cycle!? How revolutionary!)
Replying to this just to undo the accidental "redundant" moderation. I meant to mark this post as "informative." Sorry about that.