Actually, this can be good even for Ubuntu. Think of having i7, Atom and Phenom versions of executable alongside classic 586 version. Also, having one repository instead of several can also streamline few things. Downside is more data transferred on software updates, unless some create really smart update which transfers only part of fat binary that is actually used on client.
Hold on: isn't smart update which transfers only part of fat binary that is actually used on client the same as what we've got today. I mean, I just get the bits I use (x86_64) and nothing else. How often do you really have a single system that supports multiple architectures? Almost no one does at home, and at work folks usually have to support different rev levels for different situations. Either way, a central shared image where all the versions are updated lockstep isn't as useful as something that could bind to different library levels. From what little I've read, the fat binary isn't up to that task. It might be nice in a few situations, but it smells like a solution looking for a problem.
BTW: I could see this fat binary working in the installer to help newbies who don't really know what type of executable system to download, and I can see it being useful for 3rd party stuff, but not core Ubuntu. And even for that, I bet a bit JavaScript at download time could answer that question.
Technically speaking VASIMR, like ion propulsion, is electrically powered. For it to be constant thrust it would need to have that electricity generated by a nuclear reactor. Since solar power decreases as an inverse square law, a solar powered VASIMR would not be constant thrust.
s/constant/continuous/
The idea is that there is ongoing thrust, as opposed to burn then drift. Even if the additional thrust is small, it adds up over time.
But I'm pretty sure the engine discussed will need to be roughly 100x more powerful to make that 39 day trip a reality.
No, not really. Hauling the fuel for chemical rockets into orbit is expensive, so mostly they do hard burns to get the right speed and direction, then they coast most of the trip. VASIMR doesn't need the heavy fuel, as it is solar powered, so it provides constant thrust. Apparently days of constant acceleration makes a difference.
You mean like the backroom deals that just got the Lockerbie bomber released? Yuck. I understand full well that slimy stuff like this happens, but I don't have to like it. Let the EC vote down the sale if they like, or tack on clauses to ensure whatever it is that they want to ensure because that is what they are paid to do. But to drag things out is just wrong.
To quote Yoda: Do, or don't do. Halfway stuff sucks.
Was there an ALGOL 60? I thought that was just called "ALGOL". Later when they revised ALGOL and called it "ALGOL 68" it became common to call the older version "ALGOL 60", but it was never part of its name.
Yep, that's what I'd do. The rsync --server means sending signatures instead of files to prevent pointless copies, and it does an excellent job of ensuring good copy or failure. It is certainly better than any ftp variant.
She shouldn't bother suing because her myspace page is public. But the newspaper was able to fill its pages because of her work, and that means that they profited due to her actions. That says to me that she should bill them. I don't know how much reporters get paid per column inch, but that is what she should charge them. It won't be much, because reporters have to fill a lot of column inches to live well, but it is the best chance she has for getting something out of this.
Major power blocks in the US want people to pay for usage (think RIAA, MPAA, etc), and if that is the road we're going down, then every consumer who redistributes should pay. That newspaper redistributed her content, therefore she is entitled to payment. Anyone at the RIAA will swear to that on a stack of bibles.
I read the report earlier, and there are some very valid issues with the source. The first is that in incorrectly averages readings taken, assigning more weight to the first reading than the subsequent ones.
Actually, Bruce seemed to get that one wrong. The description is one of a rolling average which averages the most recent measurement with the previous average. This weights the average with the final measurement, as it is 50% of the final average. With 3 measurements, the result is 25% based off of #1, 25% based off of #2, and 50% from #3. With the fourth measurement that becomes 12.5% from #1, 12.5% from #2, 25% from #3, and 50% from #4. Only the last few measurements have any noticeable impact on the final result.
BTW: This isn't necessarily wrong. Assuming all the measurements are in the same basic range, does this really matter? Also there could be a valid reason that the final sample is weighted more heavily, but I haven't seen that. If they can give a solid reason for this, then the outrage is much ado about nothing. If not, well, then they deserve to lose a lot of contracts.
I think that turning off the error checking logic (those interrupts) is the bigger deal. That will be the source of a lot of reasonable doubt which is all that is required.
What I'm not sure is the role that breathalysers have in the conviction process. If the cop is an independent observer, then both he and the machine are likely to agree before a judge convicts. But if the cop is swayed by the readings, then there is no serious review of the machine's results. My guess is that the cop thinks you're guilty when he pulls you over, so the machine is just justifying his position after the fact, but I have no way of knowing if that is really the case.
I use rxvt and run an X server. This isn't a smooth as my linux setup, but it does work well enough. Since it does support
ssh -Yt me@somebox
I'm happy with it.
Keep in mind that the 8.10 release is not designed for broad use and that most users (even now that 9.04 has been released) should still be using 8.04, the last stable LTS release.
Untrue.
While there is no long term support (LTS) for anything since 8.04, but for those of us who don't need it, that isn't a concern. There is 18 months of support for every Ubuntu release. That is plenty long enough for most uses.
If I were designing a process that required multi-year support and maintenance, then I'd certainly think about LTS, but that isn't the world I work in.
Corporate taxes are a stupid idea anyway. The money has to leave the corporation somehow.
True enough. But what it it leaves the country, and then does those things in other countries? Something needs to be done before it leaves the US. How about something where companies don't pay any taxes paid out as salary and dividends and is reported to the IRS. Anything else, presumably including anything that leaves the country, is then taxed. I bet this could be made revenue neutral if such a thing could really exist.
Hmmm. Aren't both Bermuda and the Cayman Islands part of the British Commonwealth? Wouldn't an attack on them mean that we're at war with England, Canada, and Australia? While we could win, aren't they our friends? Canada is even helping to prop up GM & Chrysler, and if that isn't throwing away good money on our behalf, I don't know what is.
The Netherlands is a NATO country, and we are bound by treaty to attack any nation which invades a NATO nation. NATO is first and foremost a mutual defence alliance. Since obeying treaties is a Constitutional obligation, we would have to fight ourselves. Should we use blue state vs. red state, or do you have some other division in mind? Maybe redo 1861-1865, but give the Confederates a few other states to even things up a bit?
Shutting down the tax havens is an excellent idea, but claiming to be serious about a war is just stupid.
That said, we can strong arm them into line. We can embargo and blockade all we want. It won't work with the Dutch, because they have land access into Europe, but being an island in the USA's backyard leaves them at a serious disadvantage. Might Makes Right and a fleet would get them to tow the line quickly.
Then what do we do when the Tax Havens move further away?
Yes. All new kernel features should do anything it takes to ensure they work with popular applications. If a new kernel feature breaks an application, even if it is because the developers made incorrect assumptions about how things work, then the new kernel feature should be discarded. This is simple common sense, and something that even Microsoft gets right.
Then why bother coming up with standards? If Firefox doesn't properly render IE specific pages, is firefox at fault? Or is the webserver that isn't following W3C standards? Sorry, but following the standard always trumps everything else.
I don't particularly like the standard, but I've known about the need to make sure that writes hit the disk for years. And since it is a standard, it is documented. If the KDE folks (and whomever else) don't bother learning how to follow standards, then the egg is on their face.
Channel your indignation to change (ie "fix") the POSIX standard. But as someone else posted, a bunch of people will immediately scream for a way to defer the writes because the way you think it should work is too slow.
While I don't personally care for smallTalk, it has a simple enough syntax and was designed as a teaching language.
More important than language, you'll want to keep the kids engaged. Basically they'll need some results quickly, and printing strings to the tty isn't likely to count for much. That is one of the strengths of GUI programming, poping up windows, playing with colors, and stuff like are likely to keep the kids paying attention long enough to learn something.
True, it is in constitution. But remember that it was not universally liked by the founding fathers. Jefferson in particular did not like it, and argued against it. Some of us wonder if we'd be better of if TJ had won that round.
Some companies keep fake openings circulating just to stir up the waters. The question then becomes: are those openings real or phantom? I have no idea if MS does phantom openings or not, I'm just saying that it does happen.
Technically it was only the free bitkeeper license that had that restriction. If you had paid for a copy, I'm pretty sure that you could have used bk to develop whatever you liked.
My day job is with SCM systems, and I was a CC admin for nearly a decade. You're right about CC needing a bunch of helpers. Don't consider CC to be a standalone tool and you're OK. It is more of a tool kit with all the primitives that you need to build something custom for your group. UCM is more full blown, and is too much into bondage for my taste. CC is a fine environment, it isn't slow when set up right, and you can make it do lots of things. But it is expensive, and it is showing its age. I'm not sure that anyone should move to CC now, but if you're there, you don't need to abandon it. Soon you will, but not yet.
If you're talking about "cleartool update" and hijacking files, then you're using snapshot views. Ungh. They suck. Stick with dynamic views, and get your winkins to work, which usually means major makefile hackage. It is worth it.
That said, I'm different company now and going through a git vs. subversion selection process. For some reason I can't get motivated by subversion. Git seems like a whole lot more fun. Not a very scientific or profession attitude, but that is also the reason I first switched to perl oh so many years ago.
I agree. I was looking for a game to play with my sons (8 and 10) that required a bit of planning, and freeciv has worked remarkably well. Sharing a single PC sucks, but does work. My Mom watched my 8 year old play and was amazed at how many facts he was juggling.
The sad thing is that they now prefer freeciv to the wii that I stayed out in the rain to buy for them last year. If only I had known.
This sounds like a nice feature to keep stupid people from voting.
Spoken like a true, arrogant techie.
SoupIsGoodFood_42, that is simply not true. A "true, arrogant techie" would have brought up using a MySQL database to track these people so they can be prevented from voting in the future. Just because someone gets lucky the third or tenth time, it doesn't mean that they're not still the same clueless dweeb who couldn't figure how to click OK the first time. You need to spend more time around techies and arrogant people.
Slashdot Mirror
Actually, this can be good even for Ubuntu. Think of having i7, Atom and Phenom versions of executable alongside classic 586 version. Also, having one repository instead of several can also streamline few things. Downside is more data transferred on software updates, unless some create really smart update which transfers only part of fat binary that is actually used on client.
Hold on: isn't smart update which transfers only part of fat binary that is actually used on client the same as what we've got today. I mean, I just get the bits I use (x86_64) and nothing else. How often do you really have a single system that supports multiple architectures? Almost no one does at home, and at work folks usually have to support different rev levels for different situations. Either way, a central shared image where all the versions are updated lockstep isn't as useful as something that could bind to different library levels. From what little I've read, the fat binary isn't up to that task. It might be nice in a few situations, but it smells like a solution looking for a problem.
BTW: I could see this fat binary working in the installer to help newbies who don't really know what type of executable system to download, and I can see it being useful for 3rd party stuff, but not core Ubuntu. And even for that, I bet a bit JavaScript at download time could answer that question.
- doug
Technically speaking VASIMR, like ion propulsion, is electrically powered. For it to be constant thrust it would need to have that electricity generated by a nuclear reactor. Since solar power decreases as an inverse square law, a solar powered VASIMR would not be constant thrust.
s/constant/continuous/
The idea is that there is ongoing thrust, as opposed to burn then drift. Even if the additional thrust is small, it adds up over time.
- doug
No stated in this article.
But I'm pretty sure the engine discussed will need to be roughly 100x more powerful to make that 39 day trip a reality.
No, not really. Hauling the fuel for chemical rockets into orbit is expensive, so mostly they do hard burns to get the right speed and direction, then they coast most of the trip. VASIMR doesn't need the heavy fuel, as it is solar powered, so it provides constant thrust. Apparently days of constant acceleration makes a difference.
- doug
You mean like the backroom deals that just got the Lockerbie bomber released? Yuck. I understand full well that slimy stuff like this happens, but I don't have to like it. Let the EC vote down the sale if they like, or tack on clauses to ensure whatever it is that they want to ensure because that is what they are paid to do. But to drag things out is just wrong.
To quote Yoda: Do, or don't do. Halfway stuff sucks.
- doug
Was there an ALGOL 60? I thought that was just called "ALGOL". Later when they revised ALGOL and called it "ALGOL 68" it became common to call the older version "ALGOL 60", but it was never part of its name.
Yep, that's what I'd do. The rsync --server means sending signatures instead of files to prevent pointless copies, and it does an excellent job of ensuring good copy or failure. It is certainly better than any ftp variant.
She shouldn't bother suing because her myspace page is public. But the newspaper was able to fill its pages because of her work, and that means that they profited due to her actions. That says to me that she should bill them. I don't know how much reporters get paid per column inch, but that is what she should charge them. It won't be much, because reporters have to fill a lot of column inches to live well, but it is the best chance she has for getting something out of this.
Major power blocks in the US want people to pay for usage (think RIAA, MPAA, etc), and if that is the road we're going down, then every consumer who redistributes should pay. That newspaper redistributed her content, therefore she is entitled to payment. Anyone at the RIAA will swear to that on a stack of bibles.
- doug
This is a good time to recirculate professor's speech.
http://www.youtube.com/watch?v=i8z7NC5sgik
I read the report earlier, and there are some very valid issues with the source. The first is that in incorrectly averages readings taken, assigning more weight to the first reading than the subsequent ones.
Actually, Bruce seemed to get that one wrong. The description is one of a rolling average which averages the most recent measurement with the previous average. This weights the average with the final measurement, as it is 50% of the final average. With 3 measurements, the result is 25% based off of #1, 25% based off of #2, and 50% from #3. With the fourth measurement that becomes 12.5% from #1, 12.5% from #2, 25% from #3, and 50% from #4. Only the last few measurements have any noticeable impact on the final result.
BTW: This isn't necessarily wrong. Assuming all the measurements are in the same basic range, does this really matter? Also there could be a valid reason that the final sample is weighted more heavily, but I haven't seen that. If they can give a solid reason for this, then the outrage is much ado about nothing. If not, well, then they deserve to lose a lot of contracts.
I think that turning off the error checking logic (those interrupts) is the bigger deal. That will be the source of a lot of reasonable doubt which is all that is required.
What I'm not sure is the role that breathalysers have in the conviction process. If the cop is an independent observer, then both he and the machine are likely to agree before a judge convicts. But if the cop is swayed by the readings, then there is no serious review of the machine's results. My guess is that the cop thinks you're guilty when he pulls you over, so the machine is just justifying his position after the fact, but I have no way of knowing if that is really the case.
- doug
I use rxvt and run an X server. This isn't a smooth as my linux setup, but it does work well enough. Since it does support ssh -Yt me@somebox I'm happy with it.
- doug
Keep in mind that the 8.10 release is not designed for broad use and that most users (even now that 9.04 has been released) should still be using 8.04, the last stable LTS release.
Untrue.
While there is no long term support (LTS) for anything since 8.04, but for those of us who don't need it, that isn't a concern. There is 18 months of support for every Ubuntu release. That is plenty long enough for most uses.
If I were designing a process that required multi-year support and maintenance, then I'd certainly think about LTS, but that isn't the world I work in.
Corporate taxes are a stupid idea anyway. The money has to leave the corporation somehow.
True enough. But what it it leaves the country, and then does those things in other countries? Something needs to be done before it leaves the US. How about something where companies don't pay any taxes paid out as salary and dividends and is reported to the IRS. Anything else, presumably including anything that leaves the country, is then taxed. I bet this could be made revenue neutral if such a thing could really exist.
There is also:
3. Invade tax havens.
Hmmm. Aren't both Bermuda and the Cayman Islands part of the British Commonwealth? Wouldn't an attack on them mean that we're at war with England, Canada, and Australia? While we could win, aren't they our friends? Canada is even helping to prop up GM & Chrysler, and if that isn't throwing away good money on our behalf, I don't know what is.
The Netherlands is a NATO country, and we are bound by treaty to attack any nation which invades a NATO nation. NATO is first and foremost a mutual defence alliance. Since obeying treaties is a Constitutional obligation, we would have to fight ourselves. Should we use blue state vs. red state, or do you have some other division in mind? Maybe redo 1861-1865, but give the Confederates a few other states to even things up a bit?
Shutting down the tax havens is an excellent idea, but claiming to be serious about a war is just stupid.
That said, we can strong arm them into line. We can embargo and blockade all we want. It won't work with the Dutch, because they have land access into Europe, but being an island in the USA's backyard leaves them at a serious disadvantage. Might Makes Right and a fleet would get them to tow the line quickly.
Then what do we do when the Tax Havens move further away?
- doug
Yes. All new kernel features should do anything it takes to ensure they work with popular applications. If a new kernel feature breaks an application, even if it is because the developers made incorrect assumptions about how things work, then the new kernel feature should be discarded. This is simple common sense, and something that even Microsoft gets right.
Then why bother coming up with standards? If Firefox doesn't properly render IE specific pages, is firefox at fault? Or is the webserver that isn't following W3C standards? Sorry, but following the standard always trumps everything else.
I don't particularly like the standard, but I've known about the need to make sure that writes hit the disk for years. And since it is a standard, it is documented. If the KDE folks (and whomever else) don't bother learning how to follow standards, then the egg is on their face.
Channel your indignation to change (ie "fix") the POSIX standard. But as someone else posted, a bunch of people will immediately scream for a way to defer the writes because the way you think it should work is too slow.
- doug
While I don't personally care for smallTalk, it has a simple enough syntax and was designed as a teaching language.
More important than language, you'll want to keep the kids engaged. Basically they'll need some results quickly, and printing strings to the tty isn't likely to count for much. That is one of the strengths of GUI programming, poping up windows, playing with colors, and stuff like are likely to keep the kids paying attention long enough to learn something.
- doug
No, we only wish that we could.
Avoid the "xhost +" stuff. From the netbook try something like
ssh -YtC user@beefy.box.com /path/to/eclipse
and you just might get what you're looking for.
- doug
Capital punishment solves nothing, and just feeds the basest desire of humans for revenge.
I thought it reduced the rate of recidivism and repeat offenders.
True, it is in constitution. But remember that it was not universally liked by the founding fathers. Jefferson in particular did not like it, and argued against it. Some of us wonder if we'd be better of if TJ had won that round.
Some companies keep fake openings circulating just to stir up the waters. The question then becomes: are those openings real or phantom? I have no idea if MS does phantom openings or not, I'm just saying that it does happen.
- doug
Technically it was only the free bitkeeper license that had that restriction. If you had paid for a copy, I'm pretty sure that you could have used bk to develop whatever you liked.
- doug
If your dog food tasted that bad, would you eat it?
My day job is with SCM systems, and I was a CC admin for nearly a decade. You're right about CC needing a bunch of helpers. Don't consider CC to be a standalone tool and you're OK. It is more of a tool kit with all the primitives that you need to build something custom for your group. UCM is more full blown, and is too much into bondage for my taste. CC is a fine environment, it isn't slow when set up right, and you can make it do lots of things. But it is expensive, and it is showing its age. I'm not sure that anyone should move to CC now, but if you're there, you don't need to abandon it. Soon you will, but not yet.
If you're talking about "cleartool update" and hijacking files, then you're using snapshot views. Ungh. They suck. Stick with dynamic views, and get your winkins to work, which usually means major makefile hackage. It is worth it.
That said, I'm different company now and going through a git vs. subversion selection process. For some reason I can't get motivated by subversion. Git seems like a whole lot more fun. Not a very scientific or profession attitude, but that is also the reason I first switched to perl oh so many years ago.
- doug
I agree. I was looking for a game to play with my sons (8 and 10) that required a bit of planning, and freeciv has worked remarkably well. Sharing a single PC sucks, but does work. My Mom watched my 8 year old play and was amazed at how many facts he was juggling.
The sad thing is that they now prefer freeciv to the wii that I stayed out in the rain to buy for them last year. If only I had known.
This sounds like a nice feature to keep stupid people from voting.
Spoken like a true, arrogant techie.
SoupIsGoodFood_42, that is simply not true. A "true, arrogant techie" would have brought up using a MySQL database to track these people so they can be prevented from voting in the future. Just because someone gets lucky the third or tenth time, it doesn't mean that they're not still the same clueless dweeb who couldn't figure how to click OK the first time. You need to spend more time around techies and arrogant people.