I'm not sure why you've resorted belittling me. Maybe the practice works in your favor elsewhere?
Take heed to your own advice and read my entire post. You insinuated that forking is limited to kernels. It is not. Thus my reply.
My second comment was an extension of the first. It had nothing to do with your comments regarding NT and NT embedded (which I understand and agree with so consider your ego stroked). The entire point was to emphasize the fact that this embedded version of OS X will likely be a radical modification of the original (a fork). Looking back, the delusional comment was undeserving flamebait.
Why does everyone assume that an OS is solely comprised of a kernel? Do you not consider Ubuntu to be a fork of Debian?
Anyone who thinks these devices are going to run full blown OS X is delusional. This will be a stripped down, platform specific, optimized version of OS X for mobile devices and appliances (iTV anyone?). They will share code. They will share APIs.
Oh.. that's right! All those devices run a similar kernel and distribution. Give me a break. If "Linux" was a single unified source base as you describe, would we really have so many players in the market? I think not. Fork. Fork. Fork. Merge. Merge. Merge.
I'm not saying they don't share code. I'm saying that they're probably maintained as two disjoint projects with some shared code base. I consider this a fork.
You can be certain that the OS X that runs on the iPhone is a distant relative of the OS X that runs on the desktop. The two OS probably have as much as common as say, Windows XP and Windows Mobile. Think fork.
Does your company design, manufacture and market hacky sacks?
Without authentication, you can pretty much write off accounting. What happens when Chuck logs into Bill's workstation with Bill's username and deletes the secret recipe for the ultra-soft hemp yarn used for your product? Looks like Bill is out of a job.
What happens when you decide you want to take credit card orders instead of using a system of bartering? AAA (authentication, authorization and accounting) is required by VISA PCI.
"Every time you eat a steak, a hippie's hacky sack goes down the gutter." -- Patton Oswalt
This bacon wallet should have a similar effect on your friends. Maybe with the added bonus of causing them to gag a bit. Toss a few strips of real bacon in there for added effect.
Yes and No.. you could set up a new office-wide LAN utilizing existing switching equipment (vlans + trunks). Depending on switch platform, cabling, etc, this could be quite easy. The trouble is dropping the AoE clients on the new LAN without pulling more cable. Not a problem in the node room.. but certainly a problem if you want to boot a bunch of desktops residing in each cube (IMO, AoE isn't well suited for this).
You'll find that most people who leverage this type of technology will use a dedicated gigE NIC in each client and build a separate LAN solely for storage. So in many cases, the ability to retrofit is of little concern.
Packets on his LAN will not be visible to wireless clients. A WAP running as a bridge selectively forwards frames. If it did not, wireless performance would suffer greatly.
ettercap fun aside, sniffing other's traffic on a LAN is not as simple as it was in the big-fat-bus days.
Many auction buyers seem to think they can get a steal on an item. That is, they can buy it for less than the going rate and cheat the rules of supply and demand. These buyers tend to underbid items. They don't bid going rate because they won't get the satisfaction of stealing it should someone else run it up.
This strategy (if you can call it that) is why snipers exist. If I give someone ample opportunity to reconsider their maximum bid, I'll probably end up paying more for an item. If I bid last minute for the going rate, I'll probably get it for just over what the cheapskate hopes to land the item for. Worst case scenario, I get it at the going rate.
With all that space and bandwidth, why not 13.3!? Honestly though, most _consumers_ will not commit to the expense or trouble of 7.1. Likewise, so few films have properly mixed 5.1. Odds are, the consumer won't _appreciate_ the additional channels either.
Hrm.. most if not all of the software you mention supports PostgreSQL. If I were to take a bet on _which_ bits don't, it would be Courier and SASL (I know you didn't list it but it's implied). All the milter bits are in perl and work just fine with PostgreSQL.
I tend to trigger/cron a hash dump of local recipients instead of plugging Postfix straight into MySQL. It simply does not play nice. The hash files are much faster. Once local delivery is confirmed, SQL lookups are fine.
Check out the mail build instructions on my wiki for details of my most recent deployment. IIRC, there's no step where I had to use MySQL over PostgreSQL.
I ran into the same problem years ago. I'm sure several factors contribute to this slowdown. Remember that PostgreSQL tends to be transactional in nature. The default behavior (at the time) was to flush _everything_ to disc after each operation. No soft updates. This kicks the crap out of performance. However, it's really nice if someone decides to take your db down with a pull of the plug.
Kindly give one or more examples as to why one would choose not to utilize software which is distributed under the BSD license.
Additionally, have you actually _READ_ the MySQL complex hybrid licensing policy? If you have any commercial interests, you will probably have to pay for MySQL whereas PostgreSQL will remain free.
Anyone with a clue will likely weigh out the pros and cons of each license. However, in the grand scheme of things, it's likely that functionality will outweigh the license differences.
The cookie is something that's easily computed based upon tuple information and a rotating key. All that needs to be remembered is key history. These cookies would not solve anything if they too were resource tied.
Anything that's sent out of state (i.e. not part of an established connection) would be dropped. Hopefully SCTP implementations handle this better than old TCP implementations did.
Maybe your wrist is broken? Put your left hand on your forearm while you rotate your wrist from a vertical (thumbs up) to a horizontal position (palm on table). The graphic may be exaggerated but it is not without merit.
Slashdot Mirror
I'm not sure why you've resorted belittling me. Maybe the practice works in your favor elsewhere?
Take heed to your own advice and read my entire post. You insinuated that forking is limited to kernels. It is not. Thus my reply.
My second comment was an extension of the first. It had nothing to do with your comments regarding NT and NT embedded (which I understand and agree with so consider your ego stroked). The entire point was to emphasize the fact that this embedded version of OS X will likely be a radical modification of the original (a fork). Looking back, the delusional comment was undeserving flamebait.
Cheers.
Cripes. Maybe I wasn't clear enough. A kernel does not an OS make. Is Ubuntu not a fork of Debian?
Why does everyone assume that an OS is solely comprised of a kernel? Do you not consider Ubuntu to be a fork of Debian?
Anyone who thinks these devices are going to run full blown OS X is delusional. This will be a stripped down, platform specific, optimized version of OS X for mobile devices and appliances (iTV anyone?). They will share code. They will share APIs.
Oh.. that's right! All those devices run a similar kernel and distribution. Give me a break. If "Linux" was a single unified source base as you describe, would we really have so many players in the market? I think not. Fork. Fork. Fork. Merge. Merge. Merge.
I'm not saying they don't share code. I'm saying that they're probably maintained as two disjoint projects with some shared code base. I consider this a fork.
Stream much 1080p? How's that going for you? How's your collection of 1080p content sizing up? 720p will meet consumers expectations.
You can be certain that the OS X that runs on the iPhone is a distant relative of the OS X that runs on the desktop. The two OS probably have as much as common as say, Windows XP and Windows Mobile. Think fork.
Like hell you won't. You'll pay a "recycling fee". Costco will then punt the used tires for additional profit.
Does your company design, manufacture and market hacky sacks?
Without authentication, you can pretty much write off accounting. What happens when Chuck logs into Bill's workstation with Bill's username and deletes the secret recipe for the ultra-soft hemp yarn used for your product? Looks like Bill is out of a job.
What happens when you decide you want to take credit card orders instead of using a system of bartering? AAA (authentication, authorization and accounting) is required by VISA PCI.
"Every time you eat a steak, a hippie's hacky sack goes down the gutter." -- Patton Oswalt
This bacon wallet should have a similar effect on your friends. Maybe with the added bonus of causing them to gag a bit. Toss a few strips of real bacon in there for added effect.
V IEWPROD&ProdID=1733
http://www.perpetualkid.com/index.asp?PageAction=
Yes and No.. you could set up a new office-wide LAN utilizing existing switching equipment (vlans + trunks). Depending on switch platform, cabling, etc, this could be quite easy. The trouble is dropping the AoE clients on the new LAN without pulling more cable. Not a problem in the node room.. but certainly a problem if you want to boot a bunch of desktops residing in each cube (IMO, AoE isn't well suited for this).
You'll find that most people who leverage this type of technology will use a dedicated gigE NIC in each client and build a separate LAN solely for storage. So in many cases, the ability to retrofit is of little concern.
BZZT! Wrong.
Packets on his LAN will not be visible to wireless clients. A WAP running as a bridge selectively forwards frames. If it did not, wireless performance would suffer greatly.
ettercap fun aside, sniffing other's traffic on a LAN is not as simple as it was in the big-fat-bus days.
Many auction buyers seem to think they can get a steal on an item. That is, they can buy it for less than the going rate and cheat the rules of supply and demand. These buyers tend to underbid items. They don't bid going rate because they won't get the satisfaction of stealing it should someone else run it up.
This strategy (if you can call it that) is why snipers exist. If I give someone ample opportunity to reconsider their maximum bid, I'll probably end up paying more for an item. If I bid last minute for the going rate, I'll probably get it for just over what the cheapskate hopes to land the item for. Worst case scenario, I get it at the going rate.
zero voltage does not voltage make.
And when the spam bots decide to use a proxy of their own.. say outbound on 80/tcp ? :P
With all that space and bandwidth, why not 13.3!? Honestly though, most _consumers_ will not commit to the expense or trouble of 7.1. Likewise, so few films have properly mixed 5.1. Odds are, the consumer won't _appreciate_ the additional channels either.
I for one support the protection of spyware. Without the propagation of spyware, malware and viruses, many companies would go out of business. :P
Maybe they could rename the act?
Hrm.. most if not all of the software you mention supports PostgreSQL. If I were to take a bet on _which_ bits don't, it would be Courier and SASL (I know you didn't list it but it's implied). All the milter bits are in perl and work just fine with PostgreSQL.
I tend to trigger/cron a hash dump of local recipients instead of plugging Postfix straight into MySQL. It simply does not play nice. The hash files are much faster. Once local delivery is confirmed, SQL lookups are fine.
Check out the mail build instructions on my wiki for details of my most recent deployment. IIRC, there's no step where I had to use MySQL over PostgreSQL.
I ran into the same problem years ago. I'm sure several factors contribute to this slowdown. Remember that PostgreSQL tends to be transactional in nature. The default behavior (at the time) was to flush _everything_ to disc after each operation. No soft updates. This kicks the crap out of performance. However, it's really nice if someone decides to take your db down with a pull of the plug.
Typical uneducated fanboy drivel.
Kindly give one or more examples as to why one would choose not to utilize software which is distributed under the BSD license.
Additionally, have you actually _READ_ the MySQL complex hybrid licensing policy? If you have any commercial interests, you will probably have to pay for MySQL whereas PostgreSQL will remain free.
Anyone with a clue will likely weigh out the pros and cons of each license. However, in the grand scheme of things, it's likely that functionality will outweigh the license differences.
Are you sure _you're_ not on crack? Who's Charles Mason? Grammar nazis are undoubtedly eyeing your post as well. Stay off the rock FanBoyDave.
PepsiCo? Get all those coffee addicts freaked out. When they start itching, they'll surely turn to cola.
Go look at implementation details.
The cookie is something that's easily computed based upon tuple information and a rotating key. All that needs to be remembered is key history. These cookies would not solve anything if they too were resource tied.
Anything that's sent out of state (i.e. not part of an established connection) would be dropped. Hopefully SCTP implementations handle this better than old TCP implementations did.
All of these "lackluster" features are likely the result of cooling concerns.
10K RPM drives produce a fair amount of heat compared to 7200 RPM.
Pretty much all "performance" GPU now have fairly high wattage requirements.
Maybe your wrist is broken? Put your left hand on your forearm while you rotate your wrist from a vertical (thumbs up) to a horizontal position (palm on table). The graphic may be exaggerated but it is not without merit.