That means that a PS3 running Linux, even with its ridiculously low 512MB RAM, can be used as a $500 development platform for these CellBE BladeServers.
Yes, Terrasoft promotes the PS3 as a cheap testbed/devstation for Cell blades, been doing so practically since the PS3 launch. They even sell individual PS3's with Linux pre-installed, as well as clusters.
Re:Dialup is plenty fast enough, if you use it rig
on
Dealing With Dialup
·
· Score: 1
Grow a backbone and learn to say "no" and make it stick when people tell you you just *have* to see this hilarious thing they found on YouTube
Youtube-dl, using the -s option will give you a video URL you can download with wget.
Also, it would be desirable to have hyperlinks in the document, but my current PDF doesn't have them. With a bit of effort, I could get these, I suppose,
Using the hyperref package with pdflatex will do the trick.
Add to the preamble:
\usepackage{hyperref}
And then your links will look like:
\href{URL}{text}
As for latex2html I think part of the problem is that it's not kept pace with LaTeX, the newest version was released in 2002.
Your PDF, though above my level of comprehension, has that nice "LaTeX look"
I used the "-c -dev jpeg" options with pdftohtml, so it created html pages with jpeg backgrounds (with the figures). It's the version installed with xpdf 3.02. I'm also using GPL ghostscript 8.54 if that makes any difference.
One other thing you might try, that I saw mentioned on a mobile forum, convert your PDF to a series of images and then convert the images back into a PDF and then use the mobi tools.
Sony is a large company somewhat at war with itself. There's content creation Sony, like SonyBMG, that hires an outside company to make DRM stuff for it's CD's and then doesn't pay close enough attention to how that outside company achieved that.
Then there's the hardware making Sony, the Sony that makes eBooks readers that run Linux, video game consoles that run Linux, etc.
Why Sony just doesn't "bless" the bookr binaries so they can run on non-homebrew PSP's is beyond me. Even if they don't want people running emulators on it, they could still allow bookr, nethack and lots of other things.
I upgrade the firmware of my PSP from homebrew enabled to standard firmware and bookr is one of the things I miss.
But I find (in my experience, at least) that very very *very* few people actually put their time where their mouth is and write a patch.
You are forgetting one simple thing, perhaps because you are used to the old days when people who used open source were pretty much all coders of some kind, these days, non-coding open source users are far far more numerous than ones that can code. For example, I run LInux but I can't code my way out of a paper bag. Sure I can edit a Makefile or configure script with advice from google to fix issues I might have, but that's about it.
Meaning, the classic "fix it yourself" response might have been acceptable then, but now, it's basically saying, "shut up, loser user."
Of course in the open-source world, code contributions are more highly prized than stuff that the average user can do, like testing the software in "real use" conditions, or even submitting a bug report.
Unfortunately, CronoCloud, you actually could have argued it better.
I figured that out, after I quit the channel.
Contacts with multiple protocol accounts Protocol-specific functions
I had thought of those, but thought that they were so glaringly obvious that I didn't mention them in the chat, and thought that the devs were being intentionally obtuse. It didn't help that people had already used that reasoning in their bug tracker thread devoted to the issue, and got shot down by the devs. The devs KNOW that pidgin's capabilities differ by protocol, so it's helpful to know at a glance what protocol someone is using. Like you said, the pidgin devs are a complicated bunch.
I hope the fork is actually maintained and supported. If the fork maintainers are truly serious, they could effectively cause pidgin to become deprecated except for all the back-end work. So the ideal combination is funpidin for the GUI and pidgin for the back-end (libpurple and protocol support).
I agree. As someone said earlier in this huge discussion the current mess was the straw that broke the camels back. I only found out today that a fork had been threatened over the protocol icons, which is why they put them back, (but in that slightly annoying way on the right side, not back on the left) All those small but annoying UI changes just added up to frustration.
Maybe someday we'll see webcams supported so I can kick Kopete off the system?:)
Maybe. It is probably the most requested feature besides getting file transfers to work in all protocols.
While you probably can't call the Pidgin developers wild-eyed radicals (heck, a fair number of us don't use any software projects started after about 1998 with any regularity
I was personally thinking that if that's the case, why the heck do they think they have any business designing UI ( at least, not without user input)
And my response to this bit:
Remember, at the end of the day, it is the developers' sweat and effort that go into the software, so the buck stops there.
That's right, you're not getting paid, but neither are the users for being your unpaid beta testers and your unpaid marketing people. They make your software famous enough that when you put it on your resume/CV you get the job at Google, or a writing contract for a book on open source development.
I tried to compile Pidgin once, and it requires that pile-of-crap GnuTLS that I couldn't get to compile for the life of me.
I had trouble compiling GnuTLS for gaim back when they started using it, when was that, 2004. It's got to be compiled in the right order. Pidgn folks say:
start with libgpg-error, then move onto libgcrypt (which needs libgpg-error), then libtasn1. Once these three are installed, install GNUTLS.
I have to force supports_anon_versioning=no in those configure scripts. If the errors you're getting a "PARSE ERROR in VERSION SCRIPT" errors you'll have to do something similar.
One of the pidgin UI decisions that annoyed me is how they took out the invite button in Yahoo conferences. Now you have to go to Conversation>Invite. And there's no default shortcut for it.
Now normally when I see something like that I'd do what I'd do in Claws Mail, and other applications, point my mouse at the option and use the shortcut I want for that option. Or perhaps use some preference dialog in others, but oh no, not pidgin. you HAVE to type some arcane option in some obscure text file, not even the main configuration file. Sure it's nice to be able to set the option via a text file in an emergency, but why the heck can't they do it the other way too.
Don't ask the pidgin devs about documentation, they'll tell you to write it yourself. Of course the problem is that we the users don't have enough information on how this stuff actually works and what some of it does to actually write documentation.
And if you did write it, then they keep changing the UI, remember when that stupid Disable/Enable protocol actually made sense and was named Login/Logoff.
Lose the sense of entitlement; you're getting this software for free, you know.
Kelnos, meet pkarlos
All in all I agree open source developers need to be more open to change and ideas. and be more considerate that people are not attacking their work, but offering ideas and suggestions that their fan base might enjoy. We recognize that they are donating their own time, os if they don't have time, then perhaps they could be more receptive to allowing others to join the project and add those requested features...if they make their project public they need to realize they need to support the public to some degree or allow others to participate. A project without a fan base is a dead project, and thats what will happen to all their time and effort if they don't support the public to some degree.
or as I said:
If I build a house for someone and get them to sign a contract stating I have no responsibility as it's actual usability or quality, and then it leaks water from the first day and collapses on the second, I am morally and spiritually responsible, even if the contract or say "license" says I';m not legally.
Slashdot Mirror
Yes, Terrasoft promotes the PS3 as a cheap testbed/devstation for Cell blades, been doing so practically since the PS3 launch. They even sell individual PS3's with Linux pre-installed, as well as clusters.
Youtube-dl, using the -s option will give you a video URL you can download with wget.
http://www.arrakis.es/~rggi3/youtube-dl/
Also usefule on non x86 Linux without Flash itself, but with the ability to play flv.
pdflatex can handle eps, by converting it to pdf on the fly and including that.
Yes, hyperref can do that, in fact, it automatically does so, though I've only used it for external links so far.
http://en.wikibooks.org/wiki/LaTeX/Packages/Hyperref/
Maybe they'll get everything right in "Kindle 2.0"
Your PDF, though above my level of comprehension, has that nice "LaTeX look"
I used the "-c -dev jpeg" options with pdftohtml, so it created html pages with jpeg backgrounds (with the figures). It's the version installed with xpdf 3.02. I'm also using GPL ghostscript 8.54 if that makes any difference.
One other thing you might try, that I saw mentioned on a mobile forum, convert your PDF to a series of images and then convert the images back into a PDF and then use the mobi tools.
You must be new here.
Hey, c'mon, he is new here, relatively.
I just ran your book through pdftohtml on Linux, seemed to do an okay job of it.
Sony is a large company somewhat at war with itself. There's content creation Sony, like SonyBMG, that hires an outside company to make DRM stuff for it's CD's and then doesn't pay close enough attention to how that outside company achieved that.
Then there's the hardware making Sony, the Sony that makes eBooks readers that run Linux, video game consoles that run Linux, etc.
Why Sony just doesn't "bless" the bookr binaries so they can run on non-homebrew PSP's is beyond me. Even if they don't want people running emulators on it, they could still allow bookr, nethack and lots of other things.
I upgrade the firmware of my PSP from homebrew enabled to standard firmware and bookr is one of the things I miss.
ffmpeg isn't simple if they keep changing the command line options. Do they still do that with every release?
That only works with some videos, not all of them yet.
You are forgetting one simple thing, perhaps because you are used to the old days when people who used open source were pretty much all coders of some kind, these days, non-coding open source users are far far more numerous than ones that can code. For example, I run LInux but I can't code my way out of a paper bag. Sure I can edit a Makefile or configure script with advice from google to fix issues I might have, but that's about it.
Meaning, the classic "fix it yourself" response might have been acceptable then, but now, it's basically saying, "shut up, loser user."
Of course in the open-source world, code contributions are more highly prized than stuff that the average user can do, like testing the software in "real use" conditions, or even submitting a bug report.
you're correct when I entered the channel I was speaking of the comments the developers made in their bug tracker in regards to the issue.
Ahh good point, thank you.
I had thought of those, but thought that they were so glaringly obvious that I didn't mention them in the chat, and thought that the devs were being intentionally obtuse. It didn't help that people had already used that reasoning in their bug tracker thread devoted to the issue, and got shot down by the devs. The devs KNOW that pidgin's capabilities differ by protocol, so it's helpful to know at a glance what protocol someone is using. Like you said, the pidgin devs are a complicated bunch.
I agree. As someone said earlier in this huge discussion the current mess was the straw that broke the camels back. I only found out today that a fork had been threatened over the protocol icons, which is why they put them back, (but in that slightly annoying way on the right side, not back on the left) All those small but annoying UI changes just added up to frustration.
Maybe. It is probably the most requested feature besides getting file transfers to work in all protocols.
I thought it was ESR that was into Nethack and not RMS But maybe I'm getting my facial-haired somewhat controversial 'nix geeks confused.
.
http://pidgin.im/~elb/cgi-bin/pyblosxom.cgi/giving_back.html/
especially this part:
I was personally thinking that if that's the case, why the heck do they think they have any business designing UI ( at least, not without user input)
And my response to this bit:
That's right, you're not getting paid, but neither are the users for being your unpaid beta testers and your unpaid marketing people. They make your software famous enough that when you put it on your resume/CV you get the job at Google, or a writing contract for a book on open source development.
Apparently all one needs to do is to add:
gtk-can-change-accels = 1 to your gtkrc-2.0 file.
Funny thing is, both GIMP and Claws Mail can change shortcuts by pointing and using the shortcut without having that line in the gtkrc-2.0
They even stick out like a sore thumb as text links in Dillo!
I had trouble compiling GnuTLS for gaim back when they started using it, when was that, 2004. It's got to be compiled in the right order.
Pidgn folks say:
start with libgpg-error, then move onto libgcrypt (which needs libgpg-error), then libtasn1. Once these three are installed, install GNUTLS.
I have to force supports_anon_versioning=no in those configure scripts. If the errors you're getting a "PARSE ERROR in VERSION SCRIPT" errors you'll have to do something similar.
Once you put that code out in the wild, and create a community for that code, you DO have responsibility for users whether you want it or not.
You wouldn't happen to be a pidgin dev, would you, because they said pretty much what you did on IRC.
One of the pidgin UI decisions that annoyed me is how they took out the invite button in Yahoo conferences. Now you have to go to Conversation>Invite. And there's no default shortcut for it.
Now normally when I see something like that I'd do what I'd do in Claws Mail, and other applications, point my mouse at the option and use the shortcut I want for that option. Or perhaps use some preference dialog in others, but oh no, not pidgin. you HAVE to type some arcane option in some obscure text file, not even the main configuration file. Sure it's nice to be able to set the option via a text file in an emergency, but why the heck can't they do it the other way too.
Don't ask the pidgin devs about documentation, they'll tell you to write it yourself. Of course the problem is that we the users don't have enough information on how this stuff actually works and what some of it does to actually write documentation.
And if you did write it, then they keep changing the UI, remember when that stupid Disable/Enable protocol actually made sense and was named Login/Logoff.
The pidgin devs are actively user-hostile
Kelnos, meet pkarlos
or as I said:
If I build a house for someone and get them to sign a contract stating I have no responsibility as it's actual usability or quality, and then it leaks water from the first day and collapses on the second, I am morally and spiritually responsible, even if the contract or say "license" says I';m not legally.
Why would they do a stupid non-intuitive thing like that for? Oh wait, they're the pidgin developers.