Upgrade your Linux distribution... Ooop there goes your custom kernel.
You have a point generally speaking, but the above is just user error: if you had installed your custom kernels through the package management system, they douldn't have disappeared.
That has nothing to do with pre-compiled vs source. You can edit config files in either.
In fact this is what I see in Debian when a config file that I've modified changes: Configuration file `/etc/icecast2/icecast.xml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version. *** icecast.xml (Y/I/N/O/D/Z) [default=N] ?
I pretty much answered this already above, but the short version is this: It's a question of numbers: If everyone plays by the rules, the system works. If _anyone_ breaks the rules, the system is useless.
Countermeasures like that are doomed to fail because of a this simple fact:
There are millions of copies of a work that can potentially end up in piratebay. For disney to win everyone that has legal access to any of those copies must obey the rules and refrain from posting it. For pirates to win, it's enough for a single copy to end up on piratebay...
Pirates win everytime (except possibly against ninjas).
I have no idea what you mean with the Apple/Amazon comment? Are you suggesting it's somehow difficult to find music that's at the same quality level as itunes?
You said that the dogma is that it absolutely has to be open source. Now you told me that your alternative solution is... an open source driver.
So where is the dogmatism? We all seem to agree that the practical solution to this problem is a high quality open source driver.
About that "bitching and moaning": I, Chandon Seldon or the original AC did nothing of that sort, as far as I can tell. We just pointed out why we chose another solution. So... could please tell what are you referring to?
Sorry, but if you don't accept anything else this is clearly dogmatic and puristic.
I explained my selection criteria. I don't want to fuck around with drivers, I want my operating system to work, now and as long as I use the machine. My experience is that in-kernel drivers generally and Intel graphics specifically are good at that sort of thing. Your mileage may naturally vary, but how is my view dogmatism?
Sure a driver where the code is open source has advantages. But having a driver also has advantages compared to not having a driver.
Right. That's a perfectly valid (although quite obvious) point which I would never ridicule. Let's take another look at what the original S.O.B said:
Everything you've mentioned can also be addressed by a freely available hardware spec without requiring the release of the source code.
Stating that the above is totally ludicrous does not mean I think open source is better in every way.
Sorry but that is not just an inexact analogy, that's a total failure as an analogy: "car of blue" is not at all like "1st of April". The first one is clearly wrong, the second is clearly correct.
Could you give an example of this (blocking a specific dialog from working) in Windows? The way you described it sounds impossible to implement in any operating systen, so I'm guessing there is a communication problem here...
a huge majority of programs simply don't work with it
IMHO this is untrue. Some programs have problems, but a vast majority of apps I've tried worked, either without problems or with minor annoyances. Currently I'm playing Spotify just fine (re-streamed to my media server for listening through proper speakers).
Would you like to expand on your statement? I find it hard to believe that a _huge majority_ of any significant sample would fail to work unless there was some selection bias. If you've mostly tried games, you should mention that...
You keep telling yourself that it's just because we're dogmatic. I'll add an anecdote in the meantime.
I was in a similar selection dilemma as the original AC and ended up selecting Intel graphics (Thinkpad X61s) because I knew it would just work and I could use the kernels from the distro I've chosen.
I later found out that the whole linux development team had individually made the same decision (not picked the same machine, but all went for Intel graphics).
I'd also like to point out that "Everything you've mentioned can also be addressed... without requiring the release of the source code" is a totally laughable idea when you present it without details. As an example how do you expect the community to be able to fix bugs and keep old drivers up-to-date (two of GPs points) when the source is not available?
1. the question was will it be backported, not how to install it 2. there is exactly one command there that requires root. Doing the others as root is not smart
Grandparent asked aren't they jumping straight into "abusive monopoly" territory?, and I answered the question. There may well be other reasons their actions are illegal.
Saying this apparently means I'm a troll. I'm sorry but the word 'monopoly' has a meaning (and it's not "a company does something I don't like").
I'm going to agree with the AC: your post is a failure. The build-up is massive and then you finish without a single real point.
I'll take GNOME as an example: your point seemed to be that GNOME is an example of poor code quality, horrible design and uncooperative developers, with BSDs as a reference point. After reading your comment I don't know which BSD Desktop Environment I should look at to see comparable code that is higher quality (something that apparently should leave GNOME so far behind it isn't even funny). I have no idea how GNOME is an abomination (don't get me wrong, I know GNOME has problems, but you imply a lot more). I don't know any of the numerous occassions where the GNOME developers were told about this.
Please explain, preferably in a way that justifies all the trash talk.
See a problem? then fix it, regardless of a bug list, report # id.
And how do I mark it fixed? Oh, I can't because there is not bug report for this particular issue.
How does QA know to test the fix? They have no way of doing that.
How does the fix end up in release notes? It doesn't.
How do people with a similar issue find out if their problem is that same or not? They don't because the discussion includes 8 different bugs and is totally incomprehensible.
My point: You don't seem to understand what issue trackers are used for and how (calling it red tape makes you sound pretty ignorant). They are actually tools that are supposed to make our jobs easier. Filing bad bug reports may be good for you therapeutically but it doesn't make our jobs any easier.
Yeah, I agree. I've been following physics lately and it's weird how the "scientists" only test micro-gravity -- it's like they are trying avoid building planet size objects for their tests even though it's clearly required before their theory could be taken seriously. "Theory of Gravity", hah!
[micro-evolution] is an entirely different thing than macro-evolution
Sure it is. The difference between the two just changes all the time, and can't really be expressed in a scientific way (why is number of chromosomes the most important thing?). But of course they are _entirely_ different things...
The bacteria in this experiment managed to produce a totally new advantageous trait. This used to be a definition of macro-evolution at some point but I see the goal posts have moved again.
If a new trait is not good enough for you, would a hundred new traits suffice? That would probably make the bacteria totally different from a normal E. coli and could be produced just by continuing this test.
did any of the mutations ever result in more information being encoded into the structure of the virus?
Yes they did. This is in my opinion the main finding of the research.
By the way, E. coli is a bacteria not a virus.
I'm not commenting on your statistical jabs because you conveniently didn't point to any specific problems that could be debunked, just vaguely spread FUD around. I'm sorry if that sounds harsh but that's what the last paragraphs are: you have no scientific basis to for your doubts but you try to make it sound like you do.
Exactly, I think it was Nokias Ari Jaaksi who said something like this several years ago: "there is only one web. If your device does not work there, you lose". That was pretty much true then, and it's even more true today.
Even going up to San Francisco is difficult. Taking a train from Union Station to Oakland is 11 hours, followed by a bus to San Francisco running almost an hour, and costs $52 each way. I can drive up there and back for less than the cost of a rental car and gas, or I can fly up for about the same price while landing in SFO, with a flight time of barely over an hour.
I have no idea if this example was picked because it's particularly bad, but I hope you're not deducing that rail travel as an idea is bad because of this fucked up connection -- 12 hours to travel ~600km, between the two largest cities in the area? That is totally fucked up.
Your flight time estimate must have some optimism though: reserving less than two hours for drives at both ends, security, loading and unloading sounds optimistic, or maybe your origin and destination are right nect door to the airports (or maybe my experiences of American air travel have not been representative -- I nowadays try to avoid flying inside the USA).
Heh, this is the one area where Microsoft really can't be beat... I don't use their OS products anymore but I can still admit that their product lifetimes are longer than anyone elses.
Let's take XP as an example: If you bought it on release in 2001 you've been able to use it for eight years already and you've still got five years of security updates left. This is seriously impressive.
Apple on the other hand doesn't even have a End-of-life policy so you can't tell when security updates will stop appearing! History seems to suggest that Apple releases updates for two version at time: most recent 10.x and the previous 10.x-1. This seems to mean that a specific version gets security updates for 2-4 years.
Probably not, but you are one of the 500 million people who are allowed to use amazon MP3 store. The rest of us can't.
Buying DRM-free music online is pretty damn hard without itunes here...
You have a point generally speaking, but the above is just user error: if you had installed your custom kernels through the package management system, they douldn't have disappeared.
That has nothing to do with pre-compiled vs source. You can edit config files in either.
In fact this is what I see in Debian when a config file that I've modified changes:
Configuration file `/etc/icecast2/icecast.xml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** icecast.xml (Y/I/N/O/D/Z) [default=N] ?
I don't participate in conversations like this. You can consider yourself the "winner".
I pretty much answered this already above, but the short version is this: It's a question of numbers: If everyone plays by the rules, the system works. If _anyone_ breaks the rules, the system is useless.
Countermeasures like that are doomed to fail because of a this simple fact:
There are millions of copies of a work that can potentially end up in piratebay. For disney to win everyone that has legal access to any of those copies must obey the rules and refrain from posting it. For pirates to win, it's enough for a single copy to end up on piratebay...
Pirates win everytime (except possibly against ninjas).
I have no idea what you mean with the Apple/Amazon comment? Are you suggesting it's somehow difficult to find music that's at the same quality level as itunes?
You said that the dogma is that it absolutely has to be open source. Now you told me that your alternative solution is ... an open source driver.
So where is the dogmatism? We all seem to agree that the practical solution to this problem is a high quality open source driver.
About that "bitching and moaning": I, Chandon Seldon or the original AC did nothing of that sort, as far as I can tell. We just pointed out why we chose another solution. So... could please tell what are you referring to?
I explained my selection criteria. I don't want to fuck around with drivers, I want my operating system to work, now and as long as I use the machine. My experience is that in-kernel drivers generally and Intel graphics specifically are good at that sort of thing. Your mileage may naturally vary, but how is my view dogmatism?
Right. That's a perfectly valid (although quite obvious) point which I would never ridicule. Let's take another look at what the original S.O.B said:
Stating that the above is totally ludicrous does not mean I think open source is better in every way.
Sorry but that is not just an inexact analogy, that's a total failure as an analogy: "car of blue" is not at all like "1st of April". The first one is clearly wrong, the second is clearly correct.
Could you give an example of this (blocking a specific dialog from working) in Windows? The way you described it sounds impossible to implement in any operating systen, so I'm guessing there is a communication problem here...
IMHO this is untrue. Some programs have problems, but a vast majority of apps I've tried worked, either without problems or with minor annoyances. Currently I'm playing Spotify just fine (re-streamed to my media server for listening through proper speakers).
Would you like to expand on your statement? I find it hard to believe that a _huge majority_ of any significant sample would fail to work unless there was some selection bias. If you've mostly tried games, you should mention that...
This is pretty much irrelevant as a floppy wouldn't be useful on a modern desktop anyway ;)
You keep telling yourself that it's just because we're dogmatic. I'll add an anecdote in the meantime.
I was in a similar selection dilemma as the original AC and ended up selecting Intel graphics (Thinkpad X61s) because I knew it would just work and I could use the kernels from the distro I've chosen.
I later found out that the whole linux development team had individually made the same decision (not picked the same machine, but all went for Intel graphics).
I'd also like to point out that "Everything you've mentioned can also be addressed ... without requiring the release of the source code" is a totally laughable idea when you present it without details. As an example how do you expect the community to be able to fix bugs and keep old drivers up-to-date (two of GPs points) when the source is not available?
1. the question was will it be backported, not how to install it
2. there is exactly one command there that requires root. Doing the others as root is not smart
Got a reference for "being adopted by android"? Just an experimental git tree on android.git.kernel.org doesn't prove much...
I didn't imply they are.
Grandparent asked aren't they jumping straight into "abusive monopoly" territory?, and I answered the question. There may well be other reasons their actions are illegal.
Saying this apparently means I'm a troll. I'm sorry but the word 'monopoly' has a meaning (and it's not "a company does something I don't like").
yeah, that might easily be the case, if they were a monopoly.
I'm going to agree with the AC: your post is a failure. The build-up is massive and then you finish without a single real point.
I'll take GNOME as an example: your point seemed to be that GNOME is an example of poor code quality, horrible design and uncooperative developers, with BSDs as a reference point. After reading your comment I don't know which BSD Desktop Environment I should look at to see comparable code that is higher quality (something that apparently should leave GNOME so far behind it isn't even funny). I have no idea how GNOME is an abomination (don't get me wrong, I know GNOME has problems, but you imply a lot more). I don't know any of the numerous occassions where the GNOME developers were told about this.
Please explain, preferably in a way that justifies all the trash talk.
And how do I mark it fixed? Oh, I can't because there is not bug report for this particular issue.
How does QA know to test the fix? They have no way of doing that.
How does the fix end up in release notes? It doesn't.
How do people with a similar issue find out if their problem is that same or not? They don't because the discussion includes 8 different bugs and is totally incomprehensible.
My point: You don't seem to understand what issue trackers are used for and how (calling it red tape makes you sound pretty ignorant). They are actually tools that are supposed to make our jobs easier. Filing bad bug reports may be good for you therapeutically but it doesn't make our jobs any easier.
Yeah, I agree. I've been following physics lately and it's weird how the "scientists" only test micro-gravity -- it's like they are trying avoid building planet size objects for their tests even though it's clearly required before their theory could be taken seriously. "Theory of Gravity", hah!
Sure it is. The difference between the two just changes all the time, and can't really be expressed in a scientific way (why is number of chromosomes the most important thing?). But of course they are _entirely_ different things...
The bacteria in this experiment managed to produce a totally new advantageous trait. This used to be a definition of macro-evolution at some point but I see the goal posts have moved again.
If a new trait is not good enough for you, would a hundred new traits suffice? That would probably make the bacteria totally different from a normal E. coli and could be produced just by continuing this test.
Yes they did. This is in my opinion the main finding of the research.
By the way, E. coli is a bacteria not a virus.
I'm not commenting on your statistical jabs because you conveniently didn't point to any specific problems that could be debunked, just vaguely spread FUD around. I'm sorry if that sounds harsh but that's what the last paragraphs are: you have no scientific basis to for your doubts but you try to make it sound like you do.
Exactly, I think it was Nokias Ari Jaaksi who said something like this several years ago: "there is only one web. If your device does not work there, you lose". That was pretty much true then, and it's even more true today.
I have no idea if this example was picked because it's particularly bad, but I hope you're not deducing that rail travel as an idea is bad because of this fucked up connection -- 12 hours to travel ~600km, between the two largest cities in the area? That is totally fucked up.
Your flight time estimate must have some optimism though: reserving less than two hours for drives at both ends, security, loading and unloading sounds optimistic, or maybe your origin and destination are right nect door to the airports (or maybe my experiences of American air travel have not been representative -- I nowadays try to avoid flying inside the USA).
Heh, this is the one area where Microsoft really can't be beat... I don't use their OS products anymore but I can still admit that their product lifetimes are longer than anyone elses.
Let's take XP as an example: If you bought it on release in 2001 you've been able to use it for eight years already and you've still got five years of security updates left. This is seriously impressive.
Apple on the other hand doesn't even have a End-of-life policy so you can't tell when security updates will stop appearing! History seems to suggest that Apple releases updates for two version at time: most recent 10.x and the previous 10.x-1. This seems to mean that a specific version gets security updates for 2-4 years.
So... did this answer your question?