"apt-cache search curses" on debian yields a number of higher-level libraries (built on curses) that can simplify your work. For example: libaca "The Advanced nCurses API", libcdk ("curses-based widget library" in both C and perl), libcurses-ui-perl, libcurses-widgets-perl, libperlmenu-perl, libtexttools ("ada and c++ library for writing console applications"), python-urwid ("curses-based UI/widget library for Python"), twin ("Text mode WINdow environment"). So, I think the previous posters who mentioned ncurses are on the right track, but you probably want to use one of these other libraries as well, so you don't end up reimplementing menus, thermometer widgets, etc.
The environmental impact statement's description of the "low altitude demonstrator of the propulsion module" confirms its use of a high-test peroxide monopropellant.
It seems that Blue Origin would have to amend their Environmental Impact Statement if they changed propellants, but perhaps they'd first develop and validate the LOX/LH2 engine design before doing the EPA paperwork.
The problem was not Christianity, but the tightly held monopoly of the Church of Rome that kept its people in the dark about the truths of scripture while allowing corrupt people to wield incredible power.
Ah, yes. It's not Christianity, it's the Catholics who are so evil. And those darn Puritans with that whole bogus witch-trial thing... and Baptist television preachers are notoriously corrupt... and don't let's get started on Pentacostals. Some Pentacostals handle snakes in church, and sometimes they die doing this...
Let's face it, it's easy to knee-jerk blame some "other" group. Even within Christianity, you can just blame some other slightly-different subsect that believes something slightly different. It's about time you opened your eyes a little wider and started evaluating things based on a rigorous application of what you claim to believe, instead of falling back on lazy name-calling excuses. This game may claim to be holy, but not all that glitters is gold.
Why isn't anyone suggesting that the free nv drivers get fixed? See, there'd be a lot more incentive to keep the free drivers working well on nvidia hardware (and a lot more useful bug reports) if so many people weren't selling out and installing the proprietary junk.
I've seen crashing bugs in both the nv and nvidia drivers. Turning off acceleration usually makes them go away (you can selectively turn off any one(s) of about 20 different accelerated methods in xorg.conf, if you feel ambitious enough to narrow down the problem). Ultimately, I'm sticking with the free drivers because I *know* they'll get better (and that my bug reports help that cause). The nvidia drivers leave you dependent on & begging from mamma nvidia.
Re-read my post. I didn't say that the manufacturer didn't make a profit on the console. I said they didn't make "much" of a profit -- certainly not much compared to the licensing fees.
My point was that the lion's share of the money is from continued purchase of games, not from the initial console purchase.
That's all the money that these companies are going to get from me, because from here on out, all I'm going to be buying is games.
Surely you know that most of the money the console manufacturers make is from per-game licensing fees? The console isn't sold at much of a profit (if any). So it is, in fact, crucial that the console manufacturer ensure that good games for their platform keep being produced, and that you in fact continue to buy new games for the platform.
Yes, it's pretty simple to take the Z buffer from any OpenGL/DirectX game and make a quasi-3d display from it. The technology to do 2d->3d live conversion exists (it depends on camera tracking to provide different views and thus an estimate of depth) but would be a much bigger technical challenge (and much more likely to not work well in practice).
In particular, I'd like to see OpenGL support in some fashion -- even if only "software" OpenGL, as long as the software was running on a different core.
Java would be nice, too, but I suspect that gcj would do as well, and probably has a much better chance of being supported.
If you could run Java3D games on it, with a simple install technique (ie, burn the "game plus linux" installer yourself) -- that would rock! It wouldn't have to tap the entire potential speed of the PS3 for this to be a kick-ass option for hobby programmers.
This is elementary spy stuff. You want to do something the US won't like. So try out your laser on the satellite to conceal yourself while doing it. There will be some bluffing involved, but over time it will become clear whether the laser works: either because it is actually effective, or because the US so wants you to believe so that it will let you get away with anything you do while the laser is turned on. Either way, it allows you to do things you otherwise wouldn't.
You're mixing patents into the discussion. That's a separate thing entirely.
Are you claiming that, in order to be distributed under the GPLv3, the *hardware* that runs your software not only allow arbitrary modification, but have a low-cost and user-friendly download mechanism? You may like that, but not even the GPLv3 requires this.
Torvalds point is good: you may *like* to buy hardware that allows easy modification, but enforcing this is not the job of a *software* license. (At any rate, 'Make' magazine will do more towards this end than the GPLv3 will.)
And I think you're completely missing the point: there's a difference between hardware and software. It's a bad idea to try to regulate hardware with a software license. Just because I write a program for a Cray-XMP supercomputer doesn't mean that I can't make it "free" or GPL it. So, the hardware is expensive? Then tweak the code to run on something less expensive (like a general purpose computing device).
Hmm, I think Linus was arguing that the whole 'dicotomy' was miscast. The GPLv2 guarantees that any user can become a developer. There's no barrier or difference there, nothing that a developer can do that a user can't do. That doesn't magically mean that your application compiled for an Intel x86 chip will magically run on your old Commodore 64 without modification. But it guarantees you all the pieces you'd need to recompile it and kludge it into shape (or hire someone to do the same), if that's what you wanted to do.
Similarly, it doesn't guarantee that the TiVo box will run anything but TiVo-supplied source code. But it does guarantee the availability of the source code, so that you can recompile & kludge it into shape to run on your own (non-TiVo) hardware if you like. You can even sell the "unTiVo", running the same software on your free hardware. What freedoms exactly are you missing?
Linus' contention is that trying to force TiVo to allow you to run arbitrary stuff on their hardware isn't a software issue, and isn't something that a software license has any business meddling in, anymore than a software license should try to enforce that all your code be runnable on a Commodore 64, or that all your slashdot posts be modded up to +5. The operation of the slashdot mod system, like the TiVo software authentication, should be "free": the owners/operators of the system should be able to implement whatever they like. There are already non-software mechanisms for regulation here: in these two cases, primarily the marketplace. If you don't like the TiVo hardware restrictions, use a open hardware platform instead. If you don't like Slashdot's moderation, use alterslash or surf some other site. Licenses don't need to be involved, and so (via a principle of simplicity) shouldn't be involved.
Linus has such a dislike for the FSF that he rants on these things that he doesn't even know about and what's worse, uses his position to spread his ignorance like a cancer, a malignant ignorance.
I think you're attributing too much to malice. The "Linus vs FSF" debate has become "news" and so now every two-bit journalist wants to write a story on it. They corner Linus, prod him into a rant, and then record every last thing he says as "the considered opinions of Linus Torvalds". If you want to flame Linus for not "researching his position" why not also flame the journalist for not fact-checking?
The truth is that 90% of these "stories" are just transcriptions of bar chatter, done by hack journos who are trying to fan flames. The truth is more moderate and more rational. I'm certain that if Linus had to testify in a court of law, he'd construct a reasoned argument and only use examples to support it which he could reliably prove. You can flame Linus for being approachable and for speaking his mind, but (a) he's always been like that, (b) rms is the same way, and (c) IMO he/they should be able to be/do so.
Linus himself rebutted your contention in his GrokLaw post:
This is not about "programmers vs users". That's a totally false dichotomy, exactly the same way it's a totally false dichotomy to make it about "DRM vs the good guys". That's not how "freedom" works (and, that's not how DRM works either. It can be used for good, it can be used for evil. It's just technology).
The thing is, "freedom" is not a thing that you can say "freedom for some people, not for others". You have to respect the people who do the work, and you absolutely have to respect their freedoms too. And you cannot and must not try to make it about some group vs another.
You're way too eager to throw away the rights of people who actually work on things. You're way too eager to say that people who worked on something for decades should just do what you want. Here's a hint: that's not freedom.
So whenever you say "freedom for group X", you're using a totally invalid argument. That's like saying that slavery was "freedom for the white people", and that I'm against freedoms, because I think your arguments are bad. Don't you see that? You can't willy-nilly try to limit the freedoms for one group versus another. That's not "freedom", that's just using a word that sounds good to make your argument for you.
So don't talk to me about "programmers vs users". That's a deeply flawed argument, and that's not how freedoms work. It's especially not how freedoms work with the GPL, since the two aren't even distinct groups. I'm a user too, and part of the whole point is that users now have the option of becoming doers.
Finally, there's a distinct logical fallacy in the argument that "users" should be protected. It's the fallacy of thinking that people who consume are equal to people who produce. And that's not true. People who produce are the one who get to decide how things are done, because they are the ones doing it. It's that simple.
This is your board, so you get to set the rules, right? If people complain that you're doing something wrong, you can tell them to make their own board, right?
That's right. That's how the world works. And it is how the world should work, because that's what motivates people to get off their lazy behinds and do something.
In other words, if you're just a user, and you don't like how you're treated, you have the choice of becoming something more. If you don't like Tivo, you can buy a regular PC, and put MythTV on it. You'll even get to use the Tivo code, thanks to the GPLv2 (not that you'd want to).
Speak for yourself. I'm perfectly happy to settle for slightly longer seek times in exchange for putting all my archives in one place & never having to worry about running out of space.
Think of the seek time on a 500-DVD robotic jukebox!
Take a look at the Gecko/Firefox roadmaps, and you'll see that: (1) the "development branch" is actually the *trunk*, (2) there is a plan for "merging" this (ie, creating a new product branch from the trunk) -- Firefox 3, in Q1 2007.
"Why doesn't Firefox support CSS3 yet?" -- Because CSS3 is not a final recommendation. It's still in-process. The -moz-foo stuff are implementations of parts of CSS3 that have not yet been finalized, so that the standards-writers (many of them Mozilla folk) can get feedback on implementations (and fix any problems) before making the standards final.
I'd add a gratuitous personal insult here, just for fun, but you're anonymous and a coward.
Andrew Appel's papers include many on this topic; the first is "Garbage Collection can be better than Stack Allocation" and the most recent seems to be "Cache Performance of Fast-Allocating Programs". Basically, the amortized time taken by fast allocation and then later garbage collection is less than the combined time to allocate and deallocate memory the "usual" way. The memory locality of the garbage collector can be made very good as well. I believe a detailed discussion in in Appels "Modern Compiler Implementation" textbook(s).
The linked article demonstrated how Tridge accessed the bk system. He typed 'clone' at it, and it started spitting BK data at him. He dumped that binary data to disk and started munging through it. He was looking at the *on-disk format*, not any "wire formats" other than the one demonstrated with the telnet session. He didn't need to be sniffing anyone's network to do this.
I think your lynx does not support SSL. Am I wrong?
Re:Real time EIRS incident maps.
on
Verified Voting
·
· Score: 1
Every call received by the 866-OUR-VOTE is recorded in the system; I'll admit that our classification system does not always adequately distinguish between *inquiries* and *incidents*. This is partly by design: the first called who wants to know where the county clerk's office is, is an inquiry, but if 100 people call then there's probably something going on that bears inquiry.
The 'Florida Incident' filter shows the calls received during the hours the Florida primary hotline was in operation. Washington state's primary election is held on September 14, so there were some calls received regarding that (and other late primaries) on the day of the Florida primary (August 31).
Re:Fascinating....
on
Verified Voting
·
· Score: 2, Informative
Yes, and yes.
However, we don't have it normed per population. We discussed a number of such display options, but time didn't really permit their implementation.
What is really wanted is some metric for the # of people affected by each incident (rather than having all incidents count the same). But the reporters were very inaccurate in their estimates of this.
Slashdot Mirror
That's what CafePress is for.
"apt-cache search curses" on debian yields a number of higher-level libraries (built on curses) that can simplify your work. For example: libaca "The Advanced nCurses API", libcdk ("curses-based widget library" in both C and perl), libcurses-ui-perl, libcurses-widgets-perl, libperlmenu-perl, libtexttools ("ada and c++ library for writing console applications"), python-urwid ("curses-based UI/widget library for Python"), twin ("Text mode WINdow environment"). So, I think the previous posters who mentioned ncurses are on the right track, but you probably want to use one of these other libraries as well, so you don't end up reimplementing menus, thermometer widgets, etc.
It seems that Blue Origin would have to amend their Environmental Impact Statement if they changed propellants, but perhaps they'd first develop and validate the LOX/LH2 engine design before doing the EPA paperwork.
Ah, yes. It's not Christianity, it's the Catholics who are so evil. And those darn Puritans with that whole bogus witch-trial thing... and Baptist television preachers are notoriously corrupt... and don't let's get started on Pentacostals. Some Pentacostals handle snakes in church, and sometimes they die doing this...
Let's face it, it's easy to knee-jerk blame some "other" group. Even within Christianity, you can just blame some other slightly-different subsect that believes something slightly different. It's about time you opened your eyes a little wider and started evaluating things based on a rigorous application of what you claim to believe, instead of falling back on lazy name-calling excuses. This game may claim to be holy, but not all that glitters is gold.
Why isn't anyone suggesting that the free nv drivers get fixed? See, there'd be a lot more incentive to keep the free drivers working well on nvidia hardware (and a lot more useful bug reports) if so many people weren't selling out and installing the proprietary junk.
I've seen crashing bugs in both the nv and nvidia drivers. Turning off acceleration usually makes them go away (you can selectively turn off any one(s) of about 20 different accelerated methods in xorg.conf, if you feel ambitious enough to narrow down the problem). Ultimately, I'm sticking with the free drivers because I *know* they'll get better (and that my bug reports help that cause). The nvidia drivers leave you dependent on & begging from mamma nvidia.
Re-read my post. I didn't say that the manufacturer didn't make a profit on the console. I said they didn't make "much" of a profit -- certainly not much compared to the licensing fees.
My point was that the lion's share of the money is from continued purchase of games, not from the initial console purchase.
Yes, it's pretty simple to take the Z buffer from any OpenGL/DirectX game and make a quasi-3d display from it. The technology to do 2d->3d live conversion exists (it depends on camera tracking to provide different views and thus an estimate of depth) but would be a much bigger technical challenge (and much more likely to not work well in practice).
In particular, I'd like to see OpenGL support in some fashion -- even if only "software" OpenGL, as long as the software was running on a different core.
Java would be nice, too, but I suspect that gcj would do as well, and probably has a much better chance of being supported.
If you could run Java3D games on it, with a simple install technique (ie, burn the "game plus linux" installer yourself) -- that would rock! It wouldn't have to tap the entire potential speed of the PS3 for this to be a kick-ass option for hobby programmers.
This is elementary spy stuff. You want to do something the US won't like. So try out your laser on the satellite to conceal yourself while doing it. There will be some bluffing involved, but over time it will become clear whether the laser works: either because it is actually effective, or because the US so wants you to believe so that it will let you get away with anything you do while the laser is turned on. Either way, it allows you to do things you otherwise wouldn't.
You're mixing patents into the discussion. That's a separate thing entirely. Are you claiming that, in order to be distributed under the GPLv3, the *hardware* that runs your software not only allow arbitrary modification, but have a low-cost and user-friendly download mechanism? You may like that, but not even the GPLv3 requires this. Torvalds point is good: you may *like* to buy hardware that allows easy modification, but enforcing this is not the job of a *software* license. (At any rate, 'Make' magazine will do more towards this end than the GPLv3 will.)
And I think you're completely missing the point: there's a difference between hardware and software. It's a bad idea to try to regulate hardware with a software license. Just because I write a program for a Cray-XMP supercomputer doesn't mean that I can't make it "free" or GPL it. So, the hardware is expensive? Then tweak the code to run on something less expensive (like a general purpose computing device).
Hmm, I think Linus was arguing that the whole 'dicotomy' was miscast. The GPLv2 guarantees that any user can become a developer. There's no barrier or difference there, nothing that a developer can do that a user can't do. That doesn't magically mean that your application compiled for an Intel x86 chip will magically run on your old Commodore 64 without modification. But it guarantees you all the pieces you'd need to recompile it and kludge it into shape (or hire someone to do the same), if that's what you wanted to do.
Similarly, it doesn't guarantee that the TiVo box will run anything but TiVo-supplied source code. But it does guarantee the availability of the source code, so that you can recompile & kludge it into shape to run on your own (non-TiVo) hardware if you like. You can even sell the "unTiVo", running the same software on your free hardware. What freedoms exactly are you missing?
Linus' contention is that trying to force TiVo to allow you to run arbitrary stuff on their hardware isn't a software issue, and isn't something that a software license has any business meddling in, anymore than a software license should try to enforce that all your code be runnable on a Commodore 64, or that all your slashdot posts be modded up to +5. The operation of the slashdot mod system, like the TiVo software authentication, should be "free": the owners/operators of the system should be able to implement whatever they like. There are already non-software mechanisms for regulation here: in these two cases, primarily the marketplace. If you don't like the TiVo hardware restrictions, use a open hardware platform instead. If you don't like Slashdot's moderation, use alterslash or surf some other site. Licenses don't need to be involved, and so (via a principle of simplicity) shouldn't be involved.
I think you're attributing too much to malice. The "Linus vs FSF" debate has become "news" and so now every two-bit journalist wants to write a story on it. They corner Linus, prod him into a rant, and then record every last thing he says as "the considered opinions of Linus Torvalds". If you want to flame Linus for not "researching his position" why not also flame the journalist for not fact-checking?
The truth is that 90% of these "stories" are just transcriptions of bar chatter, done by hack journos who are trying to fan flames. The truth is more moderate and more rational. I'm certain that if Linus had to testify in a court of law, he'd construct a reasoned argument and only use examples to support it which he could reliably prove. You can flame Linus for being approachable and for speaking his mind, but (a) he's always been like that, (b) rms is the same way, and (c) IMO he/they should be able to be/do so.
Dude, the guy couldn't have made it more obvious; one point after another were so plainly wrong as to be overwhelmingly ironic.
Overwhelmingly... IRONIC? Sigh. I blame Alanis Morissette.
Speak for yourself. I'm perfectly happy to settle for slightly longer seek times in exchange for putting all my archives in one place & never having to worry about running out of space.
Think of the seek time on a 500-DVD robotic jukebox!
Take a look at the Gecko/Firefox roadmaps, and you'll see that: (1) the "development branch" is actually the *trunk*, (2) there is a plan for "merging" this (ie, creating a new product branch from the trunk) -- Firefox 3, in Q1 2007.
"Why doesn't Firefox support CSS3 yet?" -- Because CSS3 is not a final recommendation. It's still in-process. The -moz-foo stuff are implementations of parts of CSS3 that have not yet been finalized, so that the standards-writers (many of them Mozilla folk) can get feedback on implementations (and fix any problems) before making the standards final.
I'd add a gratuitous personal insult here, just for fun, but you're anonymous and a coward.
The weakness in OpenSSH public key authentication is man-in-the-middle attacks. Just while we're talking about it.
Andrew Appel's papers include many on this topic; the first is "Garbage Collection can be better than Stack Allocation" and the most recent seems to be "Cache Performance of Fast-Allocating Programs". Basically, the amortized time taken by fast allocation and then later garbage collection is less than the combined time to allocate and deallocate memory the "usual" way. The memory locality of the garbage collector can be made very good as well. I believe a detailed discussion in in Appels "Modern Compiler Implementation" textbook(s).
The linked article demonstrated how Tridge accessed the bk system. He typed 'clone' at it, and it started spitting BK data at him. He dumped that binary data to disk and started munging through it. He was looking at the *on-disk format*, not any "wire formats" other than the one demonstrated with the telnet session. He didn't need to be sniffing anyone's network to do this.
I think your lynx does not support SSL. Am I wrong?
Every call received by the 866-OUR-VOTE is recorded in the system; I'll admit that our classification system does not always adequately distinguish between *inquiries* and *incidents*. This is partly by design: the first called who wants to know where the county clerk's office is, is an inquiry, but if 100 people call then there's probably something going on that bears inquiry.
The 'Florida Incident' filter shows the calls received during the hours the Florida primary hotline was in operation. Washington state's primary election is held on September 14, so there were some calls received regarding that (and other late primaries) on the day of the Florida primary (August 31).
Why yes, I am!
So kind of you to ask!
Yes, and yes.
However, we don't have it normed per population. We discussed a number of such display options, but time didn't really permit their implementation.
What is really wanted is some metric for the # of people affected by each incident (rather than having all incidents count the same). But the reporters were very inaccurate in their estimates of this.