Re point 1: If you had read my comment, I proposed a way to allow specific users to bind to 1024, not everyone. On point 2:, Remote hosts should not be trusted.. Why are you trusting the remote admins in this case, anyway?
The question should not be "why do (some) standard services bind to ports 1024?" but "why is the test for opening 1024 rootness?". Or to put things another way, why is there not a file (/etc/ports, say) in the format of (port:[udp|tcp]:uid[,uid]*:gid[,gid]*)? which details which ports can be opened by who? Or even make it dead simple and only allow for a single user per port. It would seem to me to be a relatively trivial kernel change....
I am not planning on getting in a car accident any time soon, but yet I have far more insurance then is required by law. Why would one do such a thing? And in the case of the Novell/Microsoft deal, Novell actually makes money! I would have all the insurance in the world if the insurance companies paid me.
Does anyone here think that embedding Acrobat into a browser is a good idea? Ignoring the plethora of stupid people who use PDF when HTML would work better, even.
I guess it boils down to: because the full ISO stack never worked.
First off, it was never "finished", insofar as many features available in other things were/are not available in OSI.... Given the level of "optional" features of OSI, in practice, full systems never did manage to communicate with each other. Given the complexity of the standards, building software, and debugging things, was very, very hard.
I am more then willing to grant that some very specific bits coming out of the OSI process were good, and are still used. Some of x500. Some of WAN routing protocols. Some of a few low level WAN media stuff. Some of ATM. Etc.
The problem - and this is a lesson that the IPv6 people know - is that "actually works" was never a specific requirement of the OSI process. And with the "Internet/RFC" process, "actually works" is about the only firm technical requirement (some legal patent ones, as well).
My understanding is that the "business logic" of the AK-47 is marginally worse then the M-16 - that is slightly less accurate, lower rate of fire, etc. But "everything else" is much, much better. As you say, more rugged. Easier to repair in the field. Easier to manufacturer. Less to do, less to train. Just generally cheaper to build and operate.
I point this out because I was somewhat annoyed/interested/curious at a recent news story vis Canadians training/equipping various Afghan forces. Notably how some are complaining that the C7 (Canadianized M-16) are slow to arrive. What the fuck? I guess being good enough to fight off the Red Army in the 80's isn't good enough today. Have people gotten resistant to AK-47 fired rounds in the last 20 years?
I've been doing sysadmin type work for a decade. Smaller shops, I grant. But I have in the past been around a few SunOS/Solaris boxes - which worked just fine (if you consider the lack of GNU tools by default "fine").
But.... So what?
Really, why would I want to use Solaris over Linux? I guess to answer myself, there may be some very specific enterprisey things that Linux falls down on, but I think that with everything from SysV init to YaST, to no-broken tar(1) leading Linux distros just makes normal things easier.
Its not a direct analogy, but an example of how things play out in real life. Well, it is a direct analogy if you consider that to each internal party, not apologizing (or suing) is the right thing to do, but to third parties, the collective scenario is insane.
It is part of the social contract. You are getting something for "free", except nothing is free. It is ad supported. And you overtly being a leech by not even displaying the ad. Why do you have the right to demand their content for free?
The problem here is that the site in question seems to be blocking all FF users, not just the leeches. I'm not sure how they could do just the later, but that is another question, entirely.
Novell hasn't had the greatest year. I guess if they sell of one of their two or three corporate jets, and Debian picks it up, then Debian may begin to impress the likes of AMD.
At least when it first came out, Doom3 under Wine was faster then the "native" Doom3 for linux. The port was quick and dirty, with all the inline ASM stuff not handled by GCC, so it was dropped. Doom3 under Wine, compiled with the VC++ (I guess) compatible ASM inlines was faster. That said, I still play(ed) the native version.
Lots of the development tools built into the doom3 executable didn't work at all under Linux, either. Not sure if they did under Wine at day 0, or if they do at all today.
"Return" the real estate to their rightful owners? Im sure Cuba will get on that right after 'merkins turn over half of Boston and Manhattan to the Loyalists.
The second copy also makes it easy to take home, and to show to the guy either threating you with the baseball bat, or tempting you with a brown paper bag with rum in it. Good job, there.
And 15 years ago every studio camera you would have seen would have taken 35mm film. SD is newer then CF. The 3 new Nikon SLRs since August have been SD/SDHC... While they do happen to be the lower end kit, there isnt any reason to think that the upcoming replacements for the higher end stuff won't also be SD/SDHC, given that the theoretically maximum size of the SDHC is greater then that of the current CF spec.
As much as I loath the US Congress, and celebrate Wikipedia, I haven't quite gotten to the point where I think that the the later should be able to overrule the former.
Pfft. Thats like complaining that no one should buy 2x4s because you like making them yourself with glue and toothpicks. The goal of a network is to get stuff done, not to demonstrate the size of your cock to your networking geek friends.
Re point 1: If you had read my comment, I proposed a way to allow specific users to bind to 1024, not everyone. On point 2:, Remote hosts should not be trusted.. Why are you trusting the remote admins in this case, anyway?
The question should not be "why do (some) standard services bind to ports 1024?" but "why is the test for opening 1024 rootness?". Or to put things another way, why is there not a file (/etc/ports, say) in the format of (port:[udp|tcp]:uid[,uid]*:gid[,gid]*)? which details which ports can be opened by who? Or even make it dead simple and only allow for a single user per port. It would seem to me to be a relatively trivial kernel change....
I am not planning on getting in a car accident any time soon, but yet I have far more insurance then is required by law. Why would one do such a thing? And in the case of the Novell/Microsoft deal, Novell actually makes money! I would have all the insurance in the world if the insurance companies paid me.
Does anyone here think that embedding Acrobat into a browser is a good idea? Ignoring the plethora of stupid people who use PDF when HTML would work better, even.
There must be more of me. Because my personal share is not going up that much.
I guess it boils down to: because the full ISO stack never worked.
First off, it was never "finished", insofar as many features available in other things were/are not available in OSI.... Given the level of "optional" features of OSI, in practice, full systems never did manage to communicate with each other. Given the complexity of the standards, building software, and debugging things, was very, very hard.
I am more then willing to grant that some very specific bits coming out of the OSI process were good, and are still used. Some of x500. Some of WAN routing protocols. Some of a few low level WAN media stuff. Some of ATM. Etc.
The problem - and this is a lesson that the IPv6 people know - is that "actually works" was never a specific requirement of the OSI process. And with the "Internet/RFC" process, "actually works" is about the only firm technical requirement (some legal patent ones, as well).
Wow, and all the graphics were done on a Super Foonly, which had at best a couple of meagbytes.
My understanding is that the "business logic" of the AK-47 is marginally worse then the M-16 - that is slightly less accurate, lower rate of fire, etc. But "everything else" is much, much better. As you say, more rugged. Easier to repair in the field. Easier to manufacturer. Less to do, less to train. Just generally cheaper to build and operate.
I point this out because I was somewhat annoyed/interested/curious at a recent news story vis Canadians training/equipping various Afghan forces. Notably how some are complaining that the C7 (Canadianized M-16) are slow to arrive. What the fuck? I guess being good enough to fight off the Red Army in the 80's isn't good enough today. Have people gotten resistant to AK-47 fired rounds in the last 20 years?
I've been doing sysadmin type work for a decade. Smaller shops, I grant. But I have in the past been around a few SunOS/Solaris boxes - which worked just fine (if you consider the lack of GNU tools by default "fine").
But.... So what?
Really, why would I want to use Solaris over Linux? I guess to answer myself, there may be some very specific enterprisey things that Linux falls down on, but I think that with everything from SysV init to YaST, to no-broken tar(1) leading Linux distros just makes normal things easier.
Or am I missing something?
Its not a direct analogy, but an example of how things play out in real life. Well, it is a direct analogy if you consider that to each internal party, not apologizing (or suing) is the right thing to do, but to third parties, the collective scenario is insane.
Well, the reason why apologies and admissions of fault never happen is because of the tort system. See game theory/MAD.
Please do not throw sausage packaging away prior to masturbation.
I win, biatches.We Live In A Society!
It is part of the social contract. You are getting something for "free", except nothing is free. It is ad supported. And you overtly being a leech by not even displaying the ad. Why do you have the right to demand their content for free?
The problem here is that the site in question seems to be blocking all FF users, not just the leeches. I'm not sure how they could do just the later, but that is another question, entirely.
Novell hasn't had the greatest year. I guess if they sell of one of their two or three corporate jets, and Debian picks it up, then Debian may begin to impress the likes of AMD.
So you have reduced down all potentially bad ideas to a single mode? This is better, how?
Its better to annoy people then to have them not have any reason at all to come.
At least when it first came out, Doom3 under Wine was faster then the "native" Doom3 for linux. The port was quick and dirty, with all the inline ASM stuff not handled by GCC, so it was dropped. Doom3 under Wine, compiled with the VC++ (I guess) compatible ASM inlines was faster. That said, I still play(ed) the native version.
Lots of the development tools built into the doom3 executable didn't work at all under Linux, either. Not sure if they did under Wine at day 0, or if they do at all today.
"Return" the real estate to their rightful owners? Im sure Cuba will get on that right after 'merkins turn over half of Boston and Manhattan to the Loyalists.
The second copy also makes it easy to take home, and to show to the guy either threating you with the baseball bat, or tempting you with a brown paper bag with rum in it. Good job, there.
And 15 years ago every studio camera you would have seen would have taken 35mm film. SD is newer then CF. The 3 new Nikon SLRs since August have been SD/SDHC... While they do happen to be the lower end kit, there isnt any reason to think that the upcoming replacements for the higher end stuff won't also be SD/SDHC, given that the theoretically maximum size of the SDHC is greater then that of the current CF spec.
Only a cat was in the window. Did the cat tell the owner about the Google van? So the problem is that the cat can't grep access_log's?
I can see you were writing up your list there in parallel. And you have some concurrency issues, I guess, with your system to hand out labels.
As much as I loath the US Congress, and celebrate Wikipedia, I haven't quite gotten to the point where I think that the the later should be able to overrule the former.
Pfft. Thats like complaining that no one should buy 2x4s because you like making them yourself with glue and toothpicks. The goal of a network is to get stuff done, not to demonstrate the size of your cock to your networking geek friends.
Its not GNUPlot. Gnuplot, or gnuplot, sure. But it has exactly nothing to do with GNU.