I guess the Debian install instructions on your site just haven't been updated to indicate this yet. (And here I was worried the Eazel/Nautilus conspiracy of only releasing RPMs had spread to Ximian.:)
I run Debian (potato) and from all appearances, they've removed the Debian repository that used to be on spidermonkey.ximian.com that my apt.sources points to.
I'm currently in the process of downloading their "Red Carpet" installer, which looks to me like I am now stuck with using this stupid GUI package tool thingie to manage my debian packages instead of the much preferred (to me) command-line 'apt-get' tool.
Can anyone say for sure one way or the other who's already done this with Debian?
I slogged through this piece of trash hoping it would get better, but it never did. The title Noir is particulary appropriate as, if any book could get the classification of "bad, barely b-grade film noir style" this would be the one. Stuff like (I'm making this up)
"She slouched slowly through the smoky door, her feet making short little scraping sounds that reminded me of cats fighting on a hot sultry summer evening when you sit outside with the girl you met after class but never got to know her name because you just wanted to get in her pants...."
etc etc etc... The sheer amount of overly descriptive turn of phrase completely overwhelms the actual point the author is trying to get across, until you're just reading strings upon strings of adjectives and descriptives with the narration completely lost in the noise.
To mis-quote a quote I can't remember the source, "Reading this book is like having your head pushed through a big bowl of slightly warm oatmeal."
Nonetheless, I kept trying to slog through, hoping I could get some hang of the story. Fortunately, the very very overdone prosaic style cleared up, slightly, but then it got much, much worse:
This huge book (it's many many pages long) is nothing more than a thinly veiled rant against copyright infringement!!!
Yep, instead of putting up a website ranting about people stealing copywritten work, like any normally insane ranting raving lunatic would do, this ranting raving lunatic wrote and got published a whole damn nearly 500 page long book!
I was offended, to say the least, that I paid money for this.
The only effect on me of having read this book is that I had the overwhelming urge to scan it in and (violating copyrights left and right) post it somewhere on the internet.
But I held back because I couldn't bear the thought of intentially subjecting anyone else to the horror that was this book.
Ok, so that first link isn't very useful, but it links to the other two articles!:)
The second link has the most meat and the third link has lots more links to lots more thread-related topics.
And the obligitory: Don't forget, Linux is open-source, if it doesn't do something you want it to do, feel free to implement it yourself. Or bug other people about it until someone does. If it never gets done, then you have to ask yourself, "is it really so good?"
His opinion is that there is very little, if anything, *useful* that thread-based programming brings to the table other than unneeded complexity. (I tend to agree though I've not done a whole lot of threads programming.) Any time someone pops into kernel-list and claims umpteen years experience at threads programming and how wonderful it is to have "real" threads, Linus will invariably offer his condolences and then tell them how silly they've been by dealing with all those concurrency, locking and other threading issues when they could have just done it the simple way by not using threads to begin with.
No, not everything linked there is going to be entirely 100% perfectly relevant, but it's good background for understanding. Those articles also have links to other articles discussing various issues relating to good coding practice and thread-programming under Linux etc.
Then, if you want to compare Microsoft threads to Linux threads, at some point someone (probably Linus) pointed out that Linux can fork() many times faster than Microsoft can spawn a new thread, and in fact creating a new thread and fork()ing a new process under Linux both consumed exactly the same amount of overhead, so trying to claim that Microsoft's thread-based model was more resource-friendly than a Linux/UNIX-like multi-process programming model is ridiculous. You might find this discussion in one of the links referenced above, you might not, I'm not gonna go through the effort of looking for it though.
Isn't that an oxymoron? Of all the firewall products I've ever had the, errr, pleasure to work on, Firewall-1 is the least advanced, most unpleasant. The ipfilter module for Solaris is just as functional and at least it's open-sourced.
Sorry, that response sounds a lot more asshole-ish than I had intended.
What I meant to say was that your perception of the lack of features on the empeg looks like you just haven't done enough research on it.
And if you think the empeg is too expensive for what it is, then you *really* shouldn't buy it. It's *not* for everyone, but it *is* for people who are really serious about their car audio, and people who are really serious about their car audio won't balk at the price of the empeg if they really understand what it is and of what it is capable.
Hmmm, you seem like you want a high-quality system in your car, but immediately dismiss the empeg on what really are not limitations. Sounds like you really aren't serious about it... I have an empeg and I can guarantee that neither the Aiwa nor the Kenwood are going to be even close comparisons.
You want CD playback:
Why? Why not just rip those CDs and dump the resulting mp3's onto the empeg? I haven't had the desire to play a CD a single time since I've had my empeg. (The only conceivable reason I can think of is that you've picked up some piece of ass at the local mall and she has some Britney Spears CD that she wants to listen to that you don't already have on your empeg but want to play so you can get some.)
Alternatively, if you've done your research, you'll know that the empeg can plug into a second head (or can be a second head for another unit) which can certainly be your CD/AM/FM unit. No sweat.
If you want really high-quality sound though, you'll use the empeg as your primary unit and find some cheapy little AM/FM tuner unit that you can listen to NPR until the empeg's tuner module becomes available. The AM/FM tuner module should pretty much be a no-brainer installation once its available.
The simple fact is that hands down the empeg is in an entirely different, higher class of hardware than either of the other two units you've mentioned and if you're dismissing it based on perceived lack of features, you're either being really naieve or you just haven't done your research. If you are dismissing the empeg based on price-for-features, then you simply aren't the kind of person who should own an empeg anyway since that would indicate you Just Don't Get It.
Simply regulate the industry so that nobody's allowed to sell a domain name for more than, say $35. That removes any reason for NSI to hang on to "good" domain names to auction for higher prices and removes the whole market for domain squatters since they're going to pay the $35 to register it and still only get $35 for it if they sell it, minus administrative overhead, making it a losing proposition in the end.
It's not a "silver bullet" solution, and I bet people like the crack.com guys would be annoyed, but it sure seems like it would cut out the majority of the dirtbags involved in domain reselling.
They are *very* cool. Absolutely simple to set up, a monkey could do it.
There also exists software (free even) that can pull images from them and do motion/delta analysis against them along with any sort of alerting you'd like. Home-brew motion detection system, although not so cheap when you figure in the cost of the cameras.
There are going to be (and already are) a LOT of people saying "Why do we need Linux on handhelds? that's stupid." I've got an iPAQ. I've been on the ipaq list at handhelds.org. I'd like to make some statements.
The people working on Linux for handhelds (at least the people at handhelds.org anyway) are NOT interested in reproducing your Linux desktop that is running on your AMD 1.4Ghz PC with the 64MB AGP video card. They are interested in making the Linux kernel work on handheld computers so that lots of other really smart people can come up with a really nice UI schema that will run on top of it. Read the list archives a bit to realize that these people *really get it.*
Lots of people are going to be talking about "the huge Linux distro" installed on their handheld computer, thinking about their home PC. Again, that's not the way it works. The Linux distro build by the handhelds.org people has the kernel, X11, some nice utilities, and fits into about 8MB. (Yes, that's the TCP/IP stack, fbdev X11, glibc, and most of the other usual suspects.) The point is to make a working operating *environment*, not a fancy e-based desktop. They know that that's not appropriate for the handheld form factor.
Like the article says, the point is *not* Linux-centric technofetishism. The point is to literally "open up" the capabilities of the devices to make them more accessible to the people who use them. I own a Palm IIIxe and I love it. I also am having a very hard time wrapping my head around the Palm API and trying to find decent tools to program it under Linux. If I have Linux running on my iPAQ, using Qt either under X11 or with Qt/Embedded, then I don't need to learn a new paradigm and can start programming my iPAQ right away. Of course, that doesn't mean I'll understand how to program for this sort of UI, but that at least will be my fault if I screw it up. The fact that now I *can* easily screw it up on my own is the important part.
I think what everyone's assuming is that the people who are involved in these projects are under the same mistaken assumption that Microsoft has been for so many years with WinCE that the whole point is to reproduce the desktop on a really tiny computer. BUT THEY'RE NOT! Everyone involved really understands that that's a BAD IDEA.
The reason, IMHO, that this stereotype keeps propagating is that right now, just getting Linux to boot on any of the handheld devices commonly available in the market is such an accomplishment that nobody's really been able to put a whole lot of effort into coming up with a good UI for the things now that we can actually use them. Qt/Embedded is a GREAT BIG step in that direction, and hopefully will make people start realizing that this is actually REALLY COOL STUFF and not just done for the sake of doing it.
I find this rather hard to swallow considering Kylix is supposed to be a very much commercial product and the compiler likely contains all sorts of "proprietary intellectual property" developed by Borland/Inprise over the last decade or so of compiler development. I'd think they'd want to keep all that stuff closed, if only to keep MS from swiping anything cool from it and using it in their own products, not to mention this is one of their few actual product lines anymore and giving it away would be kind of silly relative to their bottom line.
One of our more visible empeg users on the BBS (http://empeg.comms.net) lives in Fairbanks Alaska. Temperature is not much of an issue with devices like these since you remove them from your car when you're not using them, so they don't freeze, unless you happen to enjoy living in freezing temperatures.
Specifically for the empeg, though, the manual states operating temperatures as "5 C to 55 C" and non-operating temperatures as "-20 C to 60 C".
And in general, the empeg is just damned cool. (Sorry, couldn't resist.)
One: there are a number of people working on making the H3600 able to boot Linux from WinCE off of a CF device. As the handhelds.org site says, "A lot of people are very interested in this option." and "We expect that once this feature becomes available, the number of people running Linux on their iPAQs will increase at least an order of magnitude, possibly two." Personally I agree. If Ihad any skill whatsoever in this area of programming, I'd be working on making it happen myself.
It's certainly DO-able, as evidenced by the fact that the handheld.org guys can dump out of WinCE, from WinCE, to load the boot monitor you use to load Linux into flash. It's just a matter of someone having the time to come up with all the proper bits and bytes to make it happen.
Two: I've personally slapped linux onto my iPAQ (yes I have one, drool over it!) and successfully restored WinCE without a hitch. It's a little scary the first time, but so's swimming in the deep end. It's nothing that someone who's successfully compiled their own kernel isn't capable of doing. (Notice how I don't say it's EASY, but its certainly straightforward and not at all scary if you pay attention. I'll admit that it is definitely slow going, trying to pump 16MB across a 115k serial link, though.)
"2) Name a router that would even pass such an IP address."
Any router will, as long as it's been told to.
The trick is that most of the internet's routers know *not* to route those addresses...
If you're on RoadRunner and I'm on RoadRunner and I tell my gateway that to hit the 192.168.11 network, it needs to route packets to your gateway, it will, and maybe I can get into your network, assuming the two nodes are on the same segment and you don't have your gateway set up to deny incoming packets to those addresses.
But the point is, unless Mr. Gibson *is* on Roadrunner and his machine is sitting "right next to mine" on their network, no, there is absolutely no way his packets are going to get through my firewall to the machine at 192.168.1.5 behind it. They wouldn't get through anyway because I've told my firewall not to accept new connections to internal addresses.
If any of what he's saying has any basis in reality, he's just deprecated the use of firewalls since the whole *point* of firewalls is to restrict certain traffic.
I have the feeling that we're all still pretty safe though...
"By utilizing specially hand-crafted phrases, I can get my marketing baloney past the engineers in your corporation who actually know anything and slip these content-free fluff pages right through your middle management directly to the top level of PHB's, who of course will, when they realize the incredible quantity of technological gibberish and understand the amazing new level of buzzword-compatibility these hand-crafted phrases exhibit, want to give me bundles and bundles of money for a product that does essentially what 'nmap' already does and has done for many many years. Only mine only works under Windows, is all made out of hand-crafted bits-n-bytes (none of those 'compiled' bits-n-bytes for me!) and has an eight-hundred page manual that's so confusing that hopefully those PHB's will never figure out enough about my software to realize it doesn't really do anything new or unique or possibly even useful."
Slashdot Mirror
Mmm, actually you're completely wrong. Several components of the "SDK" are GPL things like xcopilot and gcc.
Have you seen the license agreement to download the "SDK"??
http://www.linuxda.com/download/SDK_agree.html
Seems like all those restrictions just maaaaaaaybe against the GPL...
I guess the Debian install instructions on your site just haven't been updated to indicate this yet. (And here I was worried the Eazel/Nautilus conspiracy of only releasing RPMs had spread to Ximian.
-=-=-=-=-
I'm currently in the process of downloading their "Red Carpet" installer, which looks to me like I am now stuck with using this stupid GUI package tool thingie to manage my debian packages instead of the much preferred (to me) command-line 'apt-get' tool.
Can anyone say for sure one way or the other who's already done this with Debian?
-=-=-=-=-
It's called freenet and you would be very welcome in becoming a node on the Freenet.
-=-=-=-=-
freetantrum.org
-=-=-=-=-
Is there a requirement that entries cannot be real books? If not, I would seriously consider nominating this one.
-=-=-=-=-
"She slouched slowly through the smoky door, her feet making short little scraping sounds that reminded me of cats fighting on a hot sultry summer evening when you sit outside with the girl you met after class but never got to know her name because you just wanted to get in her pants...."
etc etc etc... The sheer amount of overly descriptive turn of phrase completely overwhelms the actual point the author is trying to get across, until you're just reading strings upon strings of adjectives and descriptives with the narration completely lost in the noise.
To mis-quote a quote I can't remember the source, "Reading this book is like having your head pushed through a big bowl of slightly warm oatmeal."
Nonetheless, I kept trying to slog through, hoping I could get some hang of the story. Fortunately, the very very overdone prosaic style cleared up, slightly, but then it got much, much worse:
This huge book (it's many many pages long) is nothing more than a thinly veiled rant against copyright infringement!!!
Yep, instead of putting up a website ranting about people stealing copywritten work, like any normally insane ranting raving lunatic would do, this ranting raving lunatic wrote and got published a whole damn nearly 500 page long book!
I was offended, to say the least, that I paid money for this.
The only effect on me of having read this book is that I had the overwhelming urge to scan it in and (violating copyrights left and right) post it somewhere on the internet.
But I held back because I couldn't bear the thought of intentially subjecting anyone else to the horror that was this book.
-=-=-=-=-
-=-=-=-=-
The second link has the most meat and the third link has lots more links to lots more thread-related topics.
And the obligitory: Don't forget, Linux is open-source, if it doesn't do something you want it to do, feel free to implement it yourself. Or bug other people about it until someone does. If it never gets done, then you have to ask yourself, "is it really so good?"
-=-=-=-=-
For some great background information read:
here
here
and here
No, not everything linked there is going to be entirely 100% perfectly relevant, but it's good background for understanding. Those articles also have links to other articles discussing various issues relating to good coding practice and thread-programming under Linux etc.
Then, if you want to compare Microsoft threads to Linux threads, at some point someone (probably Linus) pointed out that Linux can fork() many times faster than Microsoft can spawn a new thread, and in fact creating a new thread and fork()ing a new process under Linux both consumed exactly the same amount of overhead, so trying to claim that Microsoft's thread-based model was more resource-friendly than a Linux/UNIX-like multi-process programming model is ridiculous. You might find this discussion in one of the links referenced above, you might not, I'm not gonna go through the effort of looking for it though.
-=-=-=-=-
Isn't that an oxymoron? Of all the firewall products I've ever had the, errr, pleasure to work on, Firewall-1 is the least advanced, most unpleasant. The ipfilter module for Solaris is just as functional and at least it's open-sourced.
-=-=-=-=-
What I meant to say was that your perception of the lack of features on the empeg looks like you just haven't done enough research on it.
And if you think the empeg is too expensive for what it is, then you *really* shouldn't buy it. It's *not* for everyone, but it *is* for people who are really serious about their car audio, and people who are really serious about their car audio won't balk at the price of the empeg if they really understand what it is and of what it is capable.
-=-=-=-=-
You want CD playback:
Why? Why not just rip those CDs and dump the resulting mp3's onto the empeg? I haven't had the desire to play a CD a single time since I've had my empeg. (The only conceivable reason I can think of is that you've picked up some piece of ass at the local mall and she has some Britney Spears CD that she wants to listen to that you don't already have on your empeg but want to play so you can get some.)
Alternatively, if you've done your research, you'll know that the empeg can plug into a second head (or can be a second head for another unit) which can certainly be your CD/AM/FM unit. No sweat.
If you want really high-quality sound though, you'll use the empeg as your primary unit and find some cheapy little AM/FM tuner unit that you can listen to NPR until the empeg's tuner module becomes available. The AM/FM tuner module should pretty much be a no-brainer installation once its available.
The simple fact is that hands down the empeg is in an entirely different, higher class of hardware than either of the other two units you've mentioned and if you're dismissing it based on perceived lack of features, you're either being really naieve or you just haven't done your research. If you are dismissing the empeg based on price-for-features, then you simply aren't the kind of person who should own an empeg anyway since that would indicate you Just Don't Get It.
-=-=-=-=-
It's not a "silver bullet" solution, and I bet people like the crack.com guys would be annoyed, but it sure seems like it would cut out the majority of the dirtbags involved in domain reselling.
-=-=-=-=-
There also exists software (free even) that can pull images from them and do motion/delta analysis against them along with any sort of alerting you'd like. Home-brew motion detection system, although not so cheap when you figure in the cost of the cameras.
-=-=-=-=-
The people working on Linux for handhelds (at least the people at handhelds.org anyway) are NOT interested in reproducing your Linux desktop that is running on your AMD 1.4Ghz PC with the 64MB AGP video card. They are interested in making the Linux kernel work on handheld computers so that lots of other really smart people can come up with a really nice UI schema that will run on top of it. Read the list archives a bit to realize that these people *really get it.*
Lots of people are going to be talking about "the huge Linux distro" installed on their handheld computer, thinking about their home PC. Again, that's not the way it works. The Linux distro build by the handhelds.org people has the kernel, X11, some nice utilities, and fits into about 8MB. (Yes, that's the TCP/IP stack, fbdev X11, glibc, and most of the other usual suspects.) The point is to make a working operating *environment*, not a fancy e-based desktop. They know that that's not appropriate for the handheld form factor.
Like the article says, the point is *not* Linux-centric technofetishism. The point is to literally "open up" the capabilities of the devices to make them more accessible to the people who use them. I own a Palm IIIxe and I love it. I also am having a very hard time wrapping my head around the Palm API and trying to find decent tools to program it under Linux. If I have Linux running on my iPAQ, using Qt either under X11 or with Qt/Embedded, then I don't need to learn a new paradigm and can start programming my iPAQ right away. Of course, that doesn't mean I'll understand how to program for this sort of UI, but that at least will be my fault if I screw it up. The fact that now I *can* easily screw it up on my own is the important part.
I think what everyone's assuming is that the people who are involved in these projects are under the same mistaken assumption that Microsoft has been for so many years with WinCE that the whole point is to reproduce the desktop on a really tiny computer. BUT THEY'RE NOT! Everyone involved really understands that that's a BAD IDEA.
The reason, IMHO, that this stereotype keeps propagating is that right now, just getting Linux to boot on any of the handheld devices commonly available in the market is such an accomplishment that nobody's really been able to put a whole lot of effort into coming up with a good UI for the things now that we can actually use them. Qt/Embedded is a GREAT BIG step in that direction, and hopefully will make people start realizing that this is actually REALLY COOL STUFF and not just done for the sake of doing it.
-=-=-=-=-
-=-=-=-=-
Specifically for the empeg, though, the manual states operating temperatures as "5 C to 55 C" and non-operating temperatures as "-20 C to 60 C".
And in general, the empeg is just damned cool. (Sorry, couldn't resist.)
-=-=-=-=-
Can I send my company's brochure in as a story and get it published too?
-=-=-=-=-
It's certainly DO-able, as evidenced by the fact that the handheld.org guys can dump out of WinCE, from WinCE, to load the boot monitor you use to load Linux into flash. It's just a matter of someone having the time to come up with all the proper bits and bytes to make it happen.
Two: I've personally slapped linux onto my iPAQ (yes I have one, drool over it!) and successfully restored WinCE without a hitch. It's a little scary the first time, but so's swimming in the deep end. It's nothing that someone who's successfully compiled their own kernel isn't capable of doing. (Notice how I don't say it's EASY, but its certainly straightforward and not at all scary if you pay attention. I'll admit that it is definitely slow going, trying to pump 16MB across a 115k serial link, though.)
-=-=-=-=-
Guess which two sites I'll never visit again?
-=-=-=-=-
The only problem is that you need to keep the light balance *very* consistent or it can easily get overgrown, die off, algae filled, etc....
-=-=-=-=-
Any router will, as long as it's been told to.
The trick is that most of the internet's routers know *not* to route those addresses...
If you're on RoadRunner and I'm on RoadRunner and I tell my gateway that to hit the 192.168.11 network, it needs to route packets to your gateway, it will, and maybe I can get into your network, assuming the two nodes are on the same segment and you don't have your gateway set up to deny incoming packets to those addresses.
But the point is, unless Mr. Gibson *is* on Roadrunner and his machine is sitting "right next to mine" on their network, no, there is absolutely no way his packets are going to get through my firewall to the machine at 192.168.1.5 behind it. They wouldn't get through anyway because I've told my firewall not to accept new connections to internal addresses.
If any of what he's saying has any basis in reality, he's just deprecated the use of firewalls since the whole *point* of firewalls is to restrict certain traffic.
I have the feeling that we're all still pretty safe though...
-=-=-=-=-
What crap.
-=-=-=-=-