I like El Cerrito, preferrably the hills. Prices get higher closer to Berkeley (only 7 miles away), lower in the Richmond direction but some parts of Richmond qualify as slums.
I can get them for $80K. They are, generally, coming from two-income families. They want to live and work in the same town, or at least nearby, they don't want to drive to the south bay at any cost.
Of course as soon as I'm linked from Slashdot, Covad has a massive outage in the S.F. Bay area taking Technocrat down. Thus, the John Perry Barlow editorial is off the air for a few hours.
Over here in the East Bay, Berkeley area, I see lots of nice homes in the $220K range. Really good office space runs $2 per square foot, and I'm paying less because I found a sub-let. I'm at most 1.5 hours from any valley destination with traffic, but I can live in a nice place and work in the same town, and spend 10 minutes on the commute. There is every sort of culture and entertainment right here, and S.F. is a 20-minute train ride away. Outsiders think the food prices are high, but the fact is we eat better than many parts of the country because the standards for groceries are higher, and in my experience the food prices aren't any worse than the East Coast even though the quality is much better here. Gasoline does cost more because higher pollution standards mean we can't use the same gas as the rest of the country - it has to be refined differently, and we can't import cheap gas from elsewhere because it won't burn as cleanly.
I can see those expensive South Bay towns from the top of the hill I live on. Yet it costs much less to live here. Sure, it's even less expensive as you get away from the bay, but it's possible to find a happy medium.
What burns me is that some people think they can't afford to live where I am, because they confuse it with "Silicon Valley".
A key component of the Lineo system is busybox, a collection of tiny Linux tools that I wrote for the Debian installation and rescue system. Besides that, it's used in the Linux router project, and I think in some other tiny-linux and rescue systems. Lineo has had a full-time employee working on busybox for months, and all that work has been GPL-ed.
I think they are trying to find a balance between making a buck and making free software, just like everyone else in the industry. I personally feel that Linus made a mistake in making his GPL exception for kernel modules, but as far as I can tell Lineo is playing by the rules.
Note that they are not preventing you from making your own, 100% free, embedded environment. Go ahead and use busybox when you do that. Such a thing is not terribly difficult, and would be quite popular, and no doubt somebody's already doing it - I just haven't looked up who.
Because he's the kind of fellow who buys Monster cable and gold-plated connectors for his stereo, puts conductive lubricant in all of the RCA connectors, and puts those little metal cones under the speakers that acousticaly couple them to the floor. He also feels his car runs better after it's been washed.:-)
Well, maybe not so but there sure are a whole lot of people like that. Some are just perfectionists, like this guy. Some are fatuous. My favorite was someone who bought these little plastic rings that were applied to CD discs to make them sound better.
Software licenses are meant to be executed by non-attorneys. That means they should be unambiguously worded and in a language that the person who executes the license understands. This license is ambiguous regarding what it restricts and what it does not. To parse it correctly takes more understanding of the law than the person who will execute the license can be reasonably expected to have.
Hey, Bruce. A lot of people probably think we're bitter and angry at each other now, because a lot of people like to stir up controversy where there's none to be had. I bet we'll be a Register headline tomorrow morning. Wanna blow this up into a nuclear knock-down drag-out, sell tickets and donate the proceeds to Software in the Public Interest?
Yeah. Sometimes I think their median age is 12 and this is the most important thing going on in their sad little lives [that should stir them up:-)].
Naah, I'm not going to drum up controversy with you. You guys don't follow through on that stuff. Remember when I publicly promised to pop out of the sunroof of Robin's limo in front of the Javitz Conference Center and make a spectacle of myself promoting your release if you would just release the Slashcode as Open Source? You even said you'd videotape it, Emmett. And Robin could never get it together to even pull up his darned car during the conference. You guys are wet noodles.
Well, at least I got to send Robin teasing emails about when to pick me up at the airport:-)
They brought this up with me a few weeks ago. It seems that TOG makes money from Motif, and at the moment they can't go Open Source because they can't make up for the funds they'd lose. I suppose if they could get a grant or something, an Open Source license might become possible. So we agreed on that FAQ language and left it at that - the principle here is If It's Not Open Source, Don't Say It's Open Source and they are complying with that.
I think this would have been much more important if it happened before KDE and GNOME were so well established. Motif now has two worthy competitors on Unix, not just Linux, and both are themselves OSD-compliant.
Content providers put money into providing that content. Even Slashdot, which is mostly user-contributed, spends a lot of money on editing, management and facilities. In exchange, they want a few little rectangles on the screen in which they can advertise. That's the quid-pro-quo: you read their content, you pay them back with your attention to their ads.
In this content, junk-busting banner ads feels to me as if the reader is trying to welsh on their part of the bargain.
I read it the same way you did. It sounds like open APIs.
If Microsoft's strategy for dealing with the DOJ were distilled to instructions like those on a shampoo bottle, it would read "confuse, delay, repeat".:-)
Actually, Linus started the tradition when he announced "Linus 2.0", thus You have criticized the venerable Linus! Your karma has been reset to -1000, play again:-)
Gee, Bruce 2.0 was a joke. People accuse me of being humor impaired...
If Be meant to rip me off, they would have removed my copyright string from the code. They didn't.
I think in this case attribution did get "confused".
OK, it's probably a comedy of errors and I'm barking a bit too loud. But I'm so terrified by the extent that this seems to be going on - we're only catching a few percent of the offenders, and I am afraid that this will eventually discourage people from writing GPL code.
I don't know AOL's management except by reputation. But I know the Mozilla folks pretty well, and they are not about to stand for their company running rough-shod over other people's rights. AOL would have to both dismiss all of those folks and continue the project. Not likely.
Also, given the directory license, you could (and in fact someone should) archive the project as insurance - if the terms change, you can continue the project under the old terms.
Given the choice of using publicity for enforcement or using a lawsuit, I think all parties would prefer the publicity. I am not interested in using or provoking lawsuits. I don't think we have to go there at all as long as publicity remains a viable tool for enforcement. But if we decide that's out of bounds, the law becomes our only remaining chouce.
Very funny. Did you think for a minute about what we get to use for an enforcement tool when we can no longer use publicity? We go to court. I don't want to go to court, and the other side would prefer a little egg on their face to a lawsuit any day. So, do the whole community a favor and try not to erode our ability to use publicity to warn off others, etc.
I am very concerned that we are only catching a few percent of the real problem - just the tip of the iceberg.
nVidia would be no problem if they were an isolated incident. It's the fact that this is going on in such a widespread way, across so many companies, that is threatening. It's threatening because if people don't see that their GPL work is being protected, they won't write as much.
I think perhaps if you want to kill free software, this is the way to do it. Just show the authors that there is a pervasive violation of both the letter and the intent of their licenses for somebody else's pecuniary gain, and that we can't afford to go to court and we can't use publicity to go after the offenders because it's not popular to do so. They'll stop writing.
No, Be was a different circumstance. They never planned to make Open Source software. Also, the consultant involved is known to me and is actually a free software contributor of some repute.
nVidia put that code in their driver while they planned to make Open Source. Remember they announced that, and we all bought their cards, and then they changed their minds and left us with expensive paperweights? Having changed their minds about Open Sourcing their driver, they should have gone over the code base for Open Source code that they could have used legitimately until they changed their minds.
So, now I feel ripped off twice. Once for the money I paid for the card, and a second time because of this. OK, unlike Be it's not my code and I have no right to be upset about it unless someone asks me to help. But what really upsets me is the scope on which this must really be happening. Are we catching 5% of the accidents? If we get too nice about it, we will end up with the court being our only remaining enforcement tool, and we don't want that.
I don't really believe in this "oversight". They got caught, and they lied about how it happened. Just like every other company that rips off GPL code.
Well, the biggest problem with Apollo was that the Lunar Module was from Grumman and the Command and Service Modules were from Boeing and things weren't interoperable or interchangible. That almost killed off some astronauts, and the politics and inter-corporation back-biting were awful all through the program.
By the way, Apollo 13 wasn't the way Oliver Stone portrayed it: When the Service Module blew up, Apollo 13 astronauts rode home on the LM life-support and got their deorbit burn from the LM, and the Grumman engineering team was at least as responsible for saving their lives as NASA and Boeing were. But they were at each other's throats, as they were all through the rest of the program.
Given that the Russians ran power electrical cables through open doors that they needed to close to keep their astronauts breathing, I'm not sure I believe in them as orbital habitat designers. What they have, though, and we don't, is experience.
Slashdot Mirror
Bruce
Bruce
Bruce
Bruce
I can see those expensive South Bay towns from the top of the hill I live on. Yet it costs much less to live here. Sure, it's even less expensive as you get away from the bay, but it's possible to find a happy medium.
What burns me is that some people think they can't afford to live where I am, because they confuse it with "Silicon Valley".
Thanks
Bruce Perens
Take a look at the restructuring rule-making documnent. You'll find my name in attribution several places throughout the document.
There is no going back now.
Bruce
I think they are trying to find a balance between making a buck and making free software, just like everyone else in the industry. I personally feel that Linus made a mistake in making his GPL exception for kernel modules, but as far as I can tell Lineo is playing by the rules.
Note that they are not preventing you from making your own, 100% free, embedded environment. Go ahead and use busybox when you do that. Such a thing is not terribly difficult, and would be quite popular, and no doubt somebody's already doing it - I just haven't looked up who.
Thanks
Bruce
Well, maybe not so but there sure are a whole lot of people like that. Some are just perfectionists, like this guy. Some are fatuous. My favorite was someone who bought these little plastic rings that were applied to CD discs to make them sound better.
Bruce
Thanks
Bruce
Yeah. Sometimes I think their median age is 12 and this is the most important thing going on in their sad little lives [that should stir them up :-)].
Naah, I'm not going to drum up controversy with you. You guys don't follow through on that stuff. Remember when I publicly promised to pop out of the sunroof of Robin's limo in front of the Javitz Conference Center and make a spectacle of myself promoting your release if you would just release the Slashcode as Open Source? You even said you'd videotape it, Emmett. And Robin could never get it together to even pull up his darned car during the conference. You guys are wet noodles.
Well, at least I got to send Robin teasing emails about when to pick me up at the airport :-)
Bruce
The connotation in common usage is different from that listed in your Funk and Wagnalls.
Bruce
Thanks
Bruce
I think this would have been much more important if it happened before KDE and GNOME were so well established. Motif now has two worthy competitors on Unix, not just Linux, and both are themselves OSD-compliant.
Thanks
Bruce
In this content, junk-busting banner ads feels to me as if the reader is trying to welsh on their part of the bargain.
Thanks
Bruce
If Microsoft's strategy for dealing with the DOJ were distilled to instructions like those on a shampoo bottle, it would read "confuse, delay, repeat". :-)
Bruce
Gee, Bruce 2.0 was a joke. People accuse me of being humor impaired...
Thanks
Bruce
I think in this case attribution did get "confused".
OK, it's probably a comedy of errors and I'm barking a bit too loud. But I'm so terrified by the extent that this seems to be going on - we're only catching a few percent of the offenders, and I am afraid that this will eventually discourage people from writing GPL code.
Thanks
Bruce
Also, given the directory license, you could (and in fact someone should) archive the project as insurance - if the terms change, you can continue the project under the old terms.
Bruce
Bruce
Thanks
Bruce
nVidia would be no problem if they were an isolated incident. It's the fact that this is going on in such a widespread way, across so many companies, that is threatening. It's threatening because if people don't see that their GPL work is being protected, they won't write as much.
I think perhaps if you want to kill free software, this is the way to do it. Just show the authors that there is a pervasive violation of both the letter and the intent of their licenses for somebody else's pecuniary gain, and that we can't afford to go to court and we can't use publicity to go after the offenders because it's not popular to do so. They'll stop writing.
That's why these incidents bother me so much.
Bruce
nVidia put that code in their driver while they planned to make Open Source. Remember they announced that, and we all bought their cards, and then they changed their minds and left us with expensive paperweights? Having changed their minds about Open Sourcing their driver, they should have gone over the code base for Open Source code that they could have used legitimately until they changed their minds.
So, now I feel ripped off twice. Once for the money I paid for the card, and a second time because of this. OK, unlike Be it's not my code and I have no right to be upset about it unless someone asks me to help. But what really upsets me is the scope on which this must really be happening. Are we catching 5% of the accidents? If we get too nice about it, we will end up with the court being our only remaining enforcement tool, and we don't want that.
Thanks
Bruce
They must really think we are naive.
Bruce Perens
By the way, Apollo 13 wasn't the way Oliver Stone portrayed it: When the Service Module blew up, Apollo 13 astronauts rode home on the LM life-support and got their deorbit burn from the LM, and the Grumman engineering team was at least as responsible for saving their lives as NASA and Boeing were. But they were at each other's throats, as they were all through the rest of the program.
Given that the Russians ran power electrical cables through open doors that they needed to close to keep their astronauts breathing, I'm not sure I believe in them as orbital habitat designers. What they have, though, and we don't, is experience.
Thanks
Bruce
Thanks
Bruce