That is a good point. No in house team can expect to be expert on every application out there, so there will always be a market for application specific support. The trick is to see it coming an be ready with competitive offerings (as opposed to whining about the good old days like RIAA).
The point is that businesses don't buy an "enterprise" version of Ubuntu for $800/yr to get support. The Canonical company sells professional support services and training a la carte.
What about the Red Hat business model? (A little arm chair CEOing here - clearly I'm not CEO material, but this is Slashdot.) Hopefully, it can continue to support a steady stream of businesses migrating away from Microsoft for some time. But what about when that runs out?
The self supported businesses will still need to obtain their in-house expertise somehow. So training and certification would be one profit center. Contract work like IBM does would likely become the core business. Having an inside track as the distro maintainers is a valuable selling point, so continuing RHEL is vital - but must now be subsidized by training and contract work.
The most important part of a marriage is the vows and the witnesses. The "in love" feelings will come and go. When they go, you need a determination to see it through regardless. For people who honor their word, solemn vows before a crowd of witnesses accomplishes that. Maybe you've made a promise to yourself to stick it out. Why not make it public? Maybe you have some private conditions under which you would give yourself permission to bail out?
The expense of a wedding can be a symbol of the degree to which the bride is "cherished". Some Christian pro-family speaker (whose name I've forgotten) tells an insightful (though likely legendary) story of an African girl who was considered the ugly duckling and despised. While most girls fetched a bride price of 4 or 5 cows, her father set hers at 1 cow in the hopes of at least getting rid of her. A man came courting (with much gossip), and ultimately paid a bride price of 10 cows. The villagers were astonished. Even more astonishing, the girl looked radiant at the ceremony. They couldn't believe their eyes. Over the years, the girl gained confidence and the inner beauty that lasts - in large part because her husband continued to demonstrate how greatly he valued her.
By banning MPL and then reversing the ban once the discussion heated up, Google has "made a statement".
What would help is for some OSS lawyer to come up with a simplified menu of licenses something like Creative Commons. You do need at least BSD and GPL, but I agree there are way too many licenses. We non-legal geeks just want simple choices like "share alike" (GPL), "attribution" (BSD), "non commercial" (like M$ "open" licenses - not in the open source spirit but ok when used sparingly).
Cox tells you what the limit is (40GB/mo on my plan), but doesn't give you a meter. I don't want to be "contacted about excessive use", I want a meter like the gas gauge on my car. Fortunately, I use a linux router with vnstat so I can keep tabs, but how many home users are able to provide their own meter?
My dad uses Wild Blue, and they provide a nice web page with a meter to check your usage. Their cap is a continuous time average over 30 days, so you don't have to wait until the end of the month for it to reset - the average bandwidth starts going down again after he finishes his Ubuntu download, and is ready for another in a few days with worrying about hitting the limit.
The real problem with this MMO is that the death penalty is too harsh.
Why? Other MMOs terminate their subscribers for any reason. In this one, terminations are always a consequence of game events. Even the rare administrative terminations are carried out via "random" events (lightning, earthquake, volcano, etc) or the actions of other players.
Dovecot uses standard mbox format mail files. It does so efficiently for the usage I described because it builds a cached index. The index is thrown away and rebuilt on any hint of discrepancy - in which case that operation takes as long as uw-imap (a few seconds). Appends to the mbox file are handled without rebuilding. Reading one large mbox format file sequentially to build the index is much more efficient that reading 10000 individual message files, for any current filesystem including xfs. With the index, user queries are instant.
With more than 6 billion current subscribers, it seamlessly tracks the direct and indirect consequences of every player action. Cause and effect are so detailed, that it is possible to build toy MMOs within the simulation. It features total immersion with 5 or more senses that routinely covers 16 hour continuous stretches of simulation time. Longer stretches are possible, but the experience starts becoming erratic after 24 hours or so of simulation time. Administrator interventions are quite rare and well integrated when applied - to the point that many players believe there haven't been any.
The immersion is so complete, that when a players connection is temporarily interrupted, their experience in the real world is often remembered as a dream when returning to the simulation.
All player decisions are exhaustively recorded, and are reviewed and judged when their subscription is terminated.
While the hierarchical filesystem has been great for programming, it doesn't work so well for end users. I've been coaching customers and my wife on organizing email for decades. Creating folders and filing messages in them is *not* what they want to do. Many are not even capable of it.
What an end users wants to do is not "file" anything any "where". Let the email pile up in the INBOX, and click on columns to sort, or use a query to find emails. Is the imap server not handling that practice efficiently? "Bad imap server", *not* "bad user". (We switched from uw-imap to dovecot since the latter is efficient for multi-gigabyte inboxes.)
In the same vein, users want their desktops to work like email. No folders. Just a desktop view with columns pulled from file content like in thunderbird, instant sorting and searching on any column, and a simple query screen to search by logical combinations of columns. The current filename, filetype, modified, size columns are insufficient. For open office documents, the document properties should be searchable.
So maybe there is not a single set of columns that is useful for all kinds of documents. Maybe the hierarchy should be a class hierarchy. The base class has bare unix file properties (name, modified, size, permissions, etc). Email extends that to add subject, sender, to, etc. Office software extends it to add author, title, subject, lastprinted, revision, template, etc.
The extra memory is essentially data from a caching perspective. The loops cache just fine. I use the Sun Java JIT, and it really does run fast. It just uses annoying amounts of memory, (so I keep the JIT turned off except for long running applications where it really helps).
In general, JIT systems can really provide CPU performance near C speed, or even faster for some benchmarks, once the application gets going. The catch is that you pay two penalties: startup time and memory. Lots of memory: for keeping stats on what needs compiling, trampolines to call in and out of the interpreter vs. JIT native code, and the native code *plus* the byte code.
Even dynamic languages like Python can have a JIT - it specializes a function for various combinations of argument types, and then provides a catchall generic version for general objects. The catchall version is not much faster than the interpreter, usually (in fact it could *be* the interpreter), but the specialized versions can be much, much faster. (Also blocks can be specialized within any of the function versions.) But all those specialized versions take up memory. So the JIT keeps stats and tries to make only the ones that really help.
I think this is what you were trying to say, but the endpoints, not the ISP should tag packets for QoS. No DPI is required - except in the consumer routers with options like "minimize VOIP latency" or "accelerate large downloads". There should be an extra cost for low latency or high bandwidth packets - so there is nothing to gain by "cheating". (High bandwidth packets can take advantage of a longer but more capacious route, or get to keep their place in a deep queue.)
Looking at an app that uses regex to match both IP4 and IP6 precisely (as opposed to numbers and dots or hexchars and colons), the IP4 pattern is: PAT_IP4 = r'\.'.join([r'(?:\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])']*4) RE_IP4 = re.compile(PAT_IP4+'$')
and the IP6 pattern is: RE_IP6 = re.compile( '(?:%(hex4)s:){6}%(ls32)s$'
'|::(?:%(hex4)s:){5}%(ls32)s$'
'|(?:%(hex4)s)?::(?:%(hex4)s:){4}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,1}%(hex4)s)?::(?:%(hex4)s:){3}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,2}%(hex4)s)?::(?:%(hex4)s:){2}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,3}%(hex4)s)?::%(hex4)s:%(ls32)s$'
'|(?:(?:%(hex4)s:){0,4}%(hex4)s)?::%(ls32)s$'
'|(?:(?:%(hex4)s:){0,5}%(hex4)s)?::%(hex4)s$'
'|(?:(?:%(hex4)s:){0,6}%(hex4)s)?::$'
% {
'ls32': r'(?:[0-9a-f]{1,4}:[0-9a-f]{1,4}|%s)'%PAT_IP4,
'hex4': r'[0-9a-f]{1,4}'
}, re.IGNORECASE)
Longer, but not any less handy. I mean, what do you care care once the expression is compiled?
The 6 sundae customers were girlfriends of the intelligent and good looking blond trainee. And they all had a giggle fit every time the idiot trainer failed to figure out how to correct such a simple mistake.
Since the basis of the attack is spoofing server IPs, how does DJBDNS detect spoofed packets? "only come from defined servers" is useless when the packets are spoofed. It helps, of course, to not accept new glue records whenever they appear, but keep existing ones until they expire. But this just makes the attack take a little longer.
The exploit depends on a GigE connection to the DNS server. So a caching server behind a T1 is going to take much longer to exploit. So running your own caching server on a T1, DSL, or cable is going to be more resistant than using the ISP DNS with a fat pipe.
If there is actually 1 GigE of DNS traffic at an ISP, they could distribute the requests to 100 bandwidth limited servers. Then the attack would only manage to poison one of the servers in 10 hours. Even more interesting would be if the 100 servers could compare notes to detect the poisoning.
This has nothing to do with BIND vulnerabilities. DJdns, or whatever you feel is more secure, has exactly the same problem. It is a protocol weakness. The article mentions BIND only because it is the reference implementation for DNS.
The most interesting idea I've seen is to use IPv6 for DNS. The oldest idea is to start using DNSSEC.
The bad guy hijacks the domain, and buys a $20 cert from rapidssl or whatever (authenticated by email only). Cheap certs look the same as any other in older browsers, and customer may not notice on newer browsers (that color code by alleged security level).
and then reuse them for trash can liners, Auto trash bags, kitty litter bags, organizers, etc. If they outlaw plastic grocery bags, they will force us to start buying non-biodegradable trash bags in the paper boxes. Seriously, why do people buy trashcan liners that are the same size as gocery bags.
How does a predilection for debt show responsibility? All a credit score shows is that *given* you are in debt - you managed to keep up with payments. It doesn't say whether getting in debt in the first place was unavoidable (disaster), a calculated risk (entrepreneur), convenient (credit card), or foolish (spending more than you make).
Slashdot Mirror
That is a good point. No in house team can expect to be expert on every application out there, so there will always be a market for application specific support. The trick is to see it coming an be ready with competitive offerings (as opposed to whining about the good old days like RIAA).
The point is that businesses don't buy an "enterprise" version of Ubuntu for $800/yr to get support. The Canonical company sells professional support services and training a la carte.
What about the Red Hat business model? (A little arm chair CEOing here - clearly I'm not CEO material, but this is Slashdot.) Hopefully, it can continue to support a steady stream of businesses migrating away from Microsoft for some time. But what about when that runs out?
The self supported businesses will still need to obtain their in-house expertise somehow. So training and certification would be one profit center. Contract work like IBM does would likely become the core business. Having an inside track as the distro maintainers is a valuable selling point, so continuing RHEL is vital - but must now be subsidized by training and contract work.
The most important part of a marriage is the vows and the witnesses. The "in love" feelings will come and go. When they go, you need a determination to see it through regardless. For people who honor their word, solemn vows before a crowd of witnesses accomplishes that. Maybe you've made a promise to yourself to stick it out. Why not make it public? Maybe you have some private conditions under which you would give yourself permission to bail out?
The expense of a wedding can be a symbol of the degree to which the bride is "cherished". Some Christian pro-family speaker (whose name I've forgotten) tells an insightful (though likely legendary) story of an African girl who was considered the ugly duckling and despised. While most girls fetched a bride price of 4 or 5 cows, her father set hers at 1 cow in the hopes of at least getting rid of her. A man came courting (with much gossip), and ultimately paid a bride price of 10 cows. The villagers were astonished. Even more astonishing, the girl looked radiant at the ceremony. They couldn't believe their eyes. Over the years, the girl gained confidence and the inner beauty that lasts - in large part because her husband continued to demonstrate how greatly he valued her.
By banning MPL and then reversing the ban once the discussion heated up, Google has "made a statement".
What would help is for some OSS lawyer to come up with a simplified menu of licenses something like Creative Commons. You do need at least BSD and GPL, but I agree there are way too many licenses. We non-legal geeks just want simple choices like "share alike" (GPL), "attribution" (BSD), "non commercial" (like M$ "open" licenses - not in the open source spirit but ok when used sparingly).
Cox tells you what the limit is (40GB/mo on my plan), but doesn't give you a meter. I don't want to be "contacted about excessive use", I want a meter like the gas gauge on my car. Fortunately, I use a linux router with vnstat so I can keep tabs, but how many home users are able to provide their own meter?
My dad uses Wild Blue, and they provide a nice web page with a meter to check your usage. Their cap is a continuous time average over 30 days, so you don't have to wait until the end of the month for it to reset - the average bandwidth starts going down again after he finishes his Ubuntu download, and is ready for another in a few days with worrying about hitting the limit.
The real problem with this MMO is that the death penalty is too harsh.
Why? Other MMOs terminate their subscribers for any reason. In this one, terminations are always a consequence of game events. Even the rare administrative terminations are carried out via "random" events (lightning, earthquake, volcano, etc) or the actions of other players.
Dovecot uses standard mbox format mail files. It does so efficiently for the usage I described because it builds a cached index. The index is thrown away and rebuilt on any hint of discrepancy - in which case that operation takes as long as uw-imap (a few seconds). Appends to the mbox file are handled without rebuilding. Reading one large mbox format file sequentially to build the index is much more efficient that reading 10000 individual message files, for any current filesystem including xfs. With the index, user queries are instant.
With more than 6 billion current subscribers, it seamlessly tracks the direct and indirect consequences of every player action. Cause and effect are so detailed, that it is possible to build toy MMOs within the simulation. It features total immersion with 5 or more senses that routinely covers 16 hour continuous stretches of simulation time. Longer stretches are possible, but the experience starts becoming erratic after 24 hours or so of simulation time. Administrator interventions are quite rare and well integrated when applied - to the point that many players believe there haven't been any.
The immersion is so complete, that when a players connection is temporarily interrupted, their experience in the real world is often remembered as a dream when returning to the simulation.
All player decisions are exhaustively recorded, and are reviewed and judged when their subscription is terminated.
While the hierarchical filesystem has been great for programming, it doesn't work so well for end users. I've been coaching customers and my wife on organizing email for decades. Creating folders and filing messages in them is *not* what they want to do. Many are not even capable of it.
What an end users wants to do is not "file" anything any "where". Let the email pile up in the INBOX, and click on columns to sort, or use a query to find emails. Is the imap server not handling that practice efficiently? "Bad imap server", *not* "bad user". (We switched from uw-imap to dovecot since the latter is efficient for multi-gigabyte inboxes.)
In the same vein, users want their desktops to work like email. No folders. Just a desktop view with columns pulled from file content like in thunderbird, instant sorting and searching on any column, and a simple query screen to search by logical combinations of columns. The current filename, filetype, modified, size columns are insufficient. For open office documents, the document properties should be searchable.
So maybe there is not a single set of columns that is useful for all kinds of documents. Maybe the hierarchy should be a class hierarchy. The base class has bare unix file properties (name, modified, size, permissions, etc). Email extends that to add subject, sender, to, etc. Office software extends it to add author, title, subject, lastprinted, revision, template, etc.
The extra memory is essentially data from a caching perspective. The loops cache just fine. I use the Sun Java JIT, and it really does run fast. It just uses annoying amounts of memory, (so I keep the JIT turned off except for long running applications where it really helps).
In general, JIT systems can really provide CPU performance near C speed, or even faster for some benchmarks, once the application gets going. The catch is that you pay two penalties: startup time and memory. Lots of memory: for keeping stats on what needs compiling, trampolines to call in and out of the interpreter vs. JIT native code, and the native code *plus* the byte code.
Even dynamic languages like Python can have a JIT - it specializes a function for various combinations of argument types, and then provides a catchall generic version for general objects. The catchall version is not much faster than the interpreter, usually (in fact it could *be* the interpreter), but the specialized versions can be much, much faster. (Also blocks can be specialized within any of the function versions.) But all those specialized versions take up memory. So the JIT keeps stats and tries to make only the ones that really help.
You need the extra complexity to obfuscate the bias introduced by the machines.
I think this is what you were trying to say, but the endpoints, not the ISP should tag packets for QoS. No DPI is required - except in the consumer routers with options like "minimize VOIP latency" or "accelerate large downloads". There should be an extra cost for low latency or high bandwidth packets - so there is nothing to gain by "cheating". (High bandwidth packets can take advantage of a longer but more capacious route, or get to keep their place in a deep queue.)
Looking at an app that uses regex to match both IP4 and IP6 precisely (as opposed to numbers and dots or hexchars and colons), the IP4 pattern is:
PAT_IP4 = r'\.'.join([r'(?:\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])']*4)
RE_IP4 = re.compile(PAT_IP4+'$')
and the IP6 pattern is:
RE_IP6 = re.compile( '(?:%(hex4)s:){6}%(ls32)s$'
'|::(?:%(hex4)s:){5}%(ls32)s$'
'|(?:%(hex4)s)?::(?:%(hex4)s:){4}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,1}%(hex4)s)?::(?:%(hex4)s:){3}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,2}%(hex4)s)?::(?:%(hex4)s:){2}%(ls32)s$'
'|(?:(?:%(hex4)s:){0,3}%(hex4)s)?::%(hex4)s:%(ls32)s$'
'|(?:(?:%(hex4)s:){0,4}%(hex4)s)?::%(ls32)s$'
'|(?:(?:%(hex4)s:){0,5}%(hex4)s)?::%(hex4)s$'
'|(?:(?:%(hex4)s:){0,6}%(hex4)s)?::$'
% {
'ls32': r'(?:[0-9a-f]{1,4}:[0-9a-f]{1,4}|%s)'%PAT_IP4,
'hex4': r'[0-9a-f]{1,4}'
}, re.IGNORECASE)
Longer, but not any less handy. I mean, what do you care care once the
expression is compiled?
The 6 sundae customers were girlfriends of the intelligent and good looking blond trainee. And they all had a giggle fit every time the idiot trainer failed to figure out how to correct such a simple mistake.
Farnsworth fusors are widely used in medicine and research as an easily controlled and cheap source of neutrons.
or when updating your cache, compare with your cached copy, and if different ask again to double check.
That is the best idea I've heard yet.
Since the basis of the attack is spoofing server IPs, how does DJBDNS detect spoofed packets? "only come from defined servers" is useless when the packets are spoofed. It helps, of course, to not accept new glue records whenever they appear, but keep existing ones until they expire. But this just makes the attack take a little longer.
The exploit depends on a GigE connection to the DNS server. So a caching server behind a T1 is going to take much longer to exploit. So running your own caching server on a T1, DSL, or cable is going to be more resistant than using the ISP DNS with a fat pipe.
If there is actually 1 GigE of DNS traffic at an ISP, they could distribute the requests to 100 bandwidth limited servers. Then the attack would only manage to poison one of the servers in 10 hours. Even more interesting would be if the 100 servers could compare notes to detect the poisoning.
This has nothing to do with BIND vulnerabilities. DJdns, or whatever you feel is more secure, has exactly the same problem. It is a protocol weakness. The article mentions BIND only because it is the reference implementation for DNS.
The most interesting idea I've seen is to use IPv6 for DNS. The oldest idea is to start using DNSSEC.
The bad guy hijacks the domain, and buys a $20 cert from rapidssl or whatever (authenticated by email only). Cheap certs look the same as any other in older browsers, and customer may not notice on newer browsers (that color code by alleged security level).
and then reuse them for trash can liners, Auto trash bags, kitty litter bags, organizers, etc. If they outlaw plastic grocery bags, they will force us to start buying non-biodegradable trash bags in the paper boxes. Seriously, why do people buy trashcan liners that are the same size as gocery bags.
How does a predilection for debt show responsibility? All a credit score shows is that *given* you are in debt - you managed to keep up with payments. It doesn't say whether getting in debt in the first place was unavoidable (disaster), a calculated risk (entrepreneur), convenient (credit card), or foolish (spending more than you make).
for what their Viking ancestors did to my Scottish ancestors.[/satire]