These are not small words like "kissing" that are under dispute, this is not about reusing some very common routines that everyone uses, that's just silly. Rather it's about companies wanting to maintain compatibility with legacy versions of UNIX and doing so by referring directly to the legacy UNIX at best, and plagiarizing their code at worst.
Except it's not about that at all. It's about implementing standard interfaces that are defined by POSIX. POSIX defines things down to the variable type so it's natural that the resulting header files will look similar. In fact, some of the differences I'm seeing in these files are from SCO not implementing POSIX properly ex return type int where it should be size_t.
You also need to keep in mind that SCO's predecessor (AT&T) was itself caught copying code from Berkely.
There was exactly one case where there was copying shown between SCO and Linux. In that case the code was from Berkely (licensed open source) copied into SCO and copied into Linux by SGI as one of their internal filesystem driver headers. The code was determined to be non infringing due to it's history but deleted because it was old and reimplemented in a better way elsewhere.
From working with the Linux kernel maintainers I know they take copyright very seriously and investigate even the possibility that code was copied and you owe them an huge apology for that uninformed set of accusations.
I have seen companies start up with no employees, a whole lot of spare time and a $80/month dedicated server by people who have expenses like families with Children.
I hate it when people say this because it justifies the most annoying fears of technology when the Bible doesn't actually say that technology is bad. You make the classic mistake of failing to consider the old testament when analyzing something written to people who would have considered the Torah as central to their lives.
Specifically: Deuteronomy 6-8 (NAS)
6"(A)These words, which I am commanding you today, shall be on your heart.
7"(B)You shall teach them diligently to your sons and shall talk of them when you sit in your house and when you walk by the way and when you lie down and when you rise up.
8"(C)You shall bind them as a sign on your hand and they shall be as frontals on your forehead.
If writing God's words on your hand and forehead is following God then writing the Beast's mark is following the Beast.
If you consider that the mark of the beast is an opposing religion than it is very logical that members if the beast's religion would not want to do business with anyone not like them and so you suddenly can't buy or sell with the people of the dominant religion of the area with no computerized tracking necessary. This sort of exclusion has been happening for thousands of years and still happens today. At most the mark would be a religious symbol of some sort but more likely it is a literary reference to following the beast (forehead = mind, hand = action) .
The problem is that these systems were sold by people with the right connections rather than the people who had the right employees.
Watching a company bail on a 2 million dollar project because of scalability issues caused by the programmers using MS SQL for a comms system because they didn't know about sockets convinced me that the vast majority of people who call themselves programmers.. well aren't.
What we have are hordes of people who's entire skill set is around building apps are either a combination of windows components or in the web2.0 world: writing pretty wrappers around databases.
Last time I tried installing 32 bit firefox it caused some interesting breakage in my system libraries because the compat 32 bit libs conflicted with apps that needed the same library in 64 bit.
That forced me to setup a 32 bit chroot that was ugly as a sollution but kind of worked for the most part. I ditched the 32 bit chroot in favor of Adobe's 64 bit flash because it worked more seamlessly with the rest of my system and was much more stable than nspluginwrapper.
What I did not expect was to have Adobe discontinue the beta and leave me with a flash version with known security holes and left with the vague promise to re introduce it at some point in the future that they refuse to disclose.
So now I'm left looking forward to making major changes to my setup again because I made the mistake of thinking Adobe could be trusted to not completely rearrange their product plans.
nspluginwrapper is not only unstable but it blocks keyboard input to flash. Using it is a complete waste of time.
Better off pressuring websites to dump flash.
Gartner the other marketing arm of Microsoft
on
Time To Dump XP?
·
· Score: 2, Informative
Gartner has been a Microsoft/Intel shill for a long time. Their predictions tend towards the laughable as well. If you want some good laughs check out their Itanium, bing or Windows Mobile predictions.
Exactly, I've seen a ton of commentary saying it should be easy to just plug the leak and they are letting the leak continue because they want to keep collecting oil from it etc.
Most of the solutions I've seen offered are covered by the saying "Anything is easy if you don't know what your talking about"
To be sure it seems BP messed up badly before the accident by skimping on technology that may have prevented this but the conspiracy theories don't help at all.
It has nothing to do with whether you have a phone or not. When I lived in an apartment in Montreal they would drop one phone book per apartment on the floor next to the mailboxes where they would sit for months.
And they weren't counting land lines.. I got one when I had no phone line at all.
I've seen exactly this happen. Two years ago my coworker and I were dragged to Spain and tossed into an apartment that didn't have internet.
First thing he did was put together a solid gaming machine that weighed a ton. But it was still another month before we would have internet so he was stuck hunting for a crack online just so he could play the game he payed for.
On Linux and OSX apps that want to edit non user files either need to be started as root or they won't run.. period. When MS Windows reaches the same point Microsoft will have finally caught up.
Right now I have mission critical accounting software that won't run as anything but administrator and I don't feel like were winning the security war at all.
I'll grade the C and give it the easiest F ever. C doesn't have to be unreadable and if whoever comes after you can't read the code you aren't doing it right.
This all misses the point though because there were a lot of features they spent years working on that never made it into Vista let alone Windows 7. Microsoft aimed too high with Vista and fell short and the process wasted far too much developer time.
Broadcom's Linux problem is Broadcom. They insist on forcing everyone to use their own crappy non open sourced drive that fails on all but a few kernels. Essentially they are trying to be like NVIDIA without being at all competent at creating drivers. It's a sad day when a company's windows drivers work better in Linux (NDIS) than their Linux drivers.
I had problems with my DELL laptop and Broadcom but I quickly learned the best fix for that is to just order an $18 Atheros based Mini-PCIE card from China and just swap the blasted thing.
In some ways I feel bad for Microsoft because a lot of business critical apps were designed in the windows 3.1/95 era where you could write to files anywhere on the drive and the OS wouldn't stop you. The problem now is that these software developers have yet to join the last decade and stop writing their files wherever they feel like it so now Microsoft is stuck because if they break the apps no one will upgrade leaving things insecure or if they leave things the same way they are now things will be insecure. UAC is the middle road where users get shown exactly what software is a problem but are still able to get work done.
Linux/*BSD/OSX all have the advantage here because on those OS apps that behave so badly won't even run in the first place and that's why non windows people get so annoyed when people go on about how cool UAC is.
You don't need gksudo unless your actually doing something "administrative" like changing system wide settings or installing system wide software.
No non administrative app should ever require root so if you didn't do something where you would otherwise expect to need gksudo you can just assume the prompt is fake.
The reason UAC needs to be so clever is that day to day tasks often cause it to activate and you need to be able to tell the difference.
Ipv6 was designed for sparse allocations to allow for easier routing that and if they figured if they need to painfully break something make it large enough so that it only has to be done once.
Ipv4 32 bit.. ipv6 128 bit so really if you wanted to reference the number the same way it would be 255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.
In grade 6 my class had this music teacher who wanted to be all trendy and made us do rap songs about things like the dangers of drug use. Had she actually been "up with it" she would probably have noticed how much we hated doing it. The DOS 5 upgrade ad is causing flashbacks to that music class.
Slashdot Mirror
On my servers it generated a ton of complaints about time critical emails being delayed for hours.
In the end I had to shut off greylisting to avoid losing all of my paying customers.
These are not small words like "kissing" that are under dispute, this is not about reusing some very common routines that everyone uses, that's just silly. Rather it's about companies wanting to maintain compatibility with legacy versions of UNIX and doing so by referring directly to the legacy UNIX at best, and plagiarizing their code at worst.
Except it's not about that at all. It's about implementing standard interfaces that are defined by POSIX. POSIX defines things down to the variable type so it's natural that the resulting header files will look similar. In fact, some of the differences I'm seeing in these files are from SCO not implementing POSIX properly ex return type int where it should be size_t.
You also need to keep in mind that SCO's predecessor (AT&T) was itself caught copying code from Berkely.
There was exactly one case where there was copying shown between SCO and Linux. In that case the code was from Berkely (licensed open source) copied into SCO and copied into Linux by SGI as one of their internal filesystem driver headers. The code was determined to be non infringing due to it's history but deleted because it was old and reimplemented in a better way elsewhere.
From working with the Linux kernel maintainers I know they take copyright very seriously and investigate even the possibility that code was copied and you owe them an huge apology for that uninformed set of accusations.
I have seen companies start up with no employees, a whole lot of spare time and a $80/month dedicated server by people who have expenses like families with Children.
$2000 is a lot of money in many cases.
I hate it when people say this because it justifies the most annoying fears of technology when the Bible doesn't actually say that technology is bad. You make the classic mistake of failing to consider the old testament when analyzing something written to people who would have considered the Torah as central to their lives.
Specifically:
Deuteronomy 6-8 (NAS)
6"(A)These words, which I am commanding you today, shall be on your heart.
7"(B)You shall teach them diligently to your sons and shall talk of them when you sit in your house and when you walk by the way and when you lie down and when you rise up.
8"(C)You shall bind them as a sign on your hand and they shall be as frontals on your forehead.
If writing God's words on your hand and forehead is following God then writing the Beast's mark is following the Beast.
If you consider that the mark of the beast is an opposing religion than it is very logical that members if the beast's religion would not want to do business with anyone not like them and so you suddenly can't buy or sell with the people of the dominant religion of the area with no computerized tracking necessary. This sort of exclusion has been happening for thousands of years and still happens today. At most the mark would be a religious symbol of some sort but more likely it is a literary reference to following the beast (forehead = mind, hand = action) .
Tyranny has never required technology.
The problem is that these systems were sold by people with the right connections rather than the people who had the right employees.
Watching a company bail on a 2 million dollar project because of scalability issues caused by the programmers using MS SQL for a comms system because they didn't know about sockets convinced me that the vast majority of people who call themselves programmers .. well aren't.
What we have are hordes of people who's entire skill set is around building apps are either a combination of windows components or in the web2.0 world: writing pretty wrappers around databases.
More like: swap is slow. When you are using it try to make things you need to access at the same time closer together to minimize reads.
The latest beta was actually quite stable and even the first beta was a lot more stable than 32bit+nspluginwrapper,
Last time I tried installing 32 bit firefox it caused some interesting breakage in my system libraries because the compat 32 bit libs conflicted with apps that needed the same library in 64 bit.
That forced me to setup a 32 bit chroot that was ugly as a sollution but kind of worked for the most part. I ditched the 32 bit chroot in favor of Adobe's 64 bit flash because it worked more seamlessly with the rest of my system and was much more stable than nspluginwrapper.
What I did not expect was to have Adobe discontinue the beta and leave me with a flash version with known security holes and left with the vague promise to re introduce it at some point in the future that they refuse to disclose.
So now I'm left looking forward to making major changes to my setup again because I made the mistake of thinking Adobe could be trusted to not completely rearrange their product plans.
nspluginwrapper is not only unstable but it blocks keyboard input to flash. Using it is a complete waste of time.
Better off pressuring websites to dump flash.
Gartner has been a Microsoft/Intel shill for a long time. Their predictions tend towards the laughable as well. If you want some good laughs check out their Itanium, bing or Windows Mobile predictions.
And Python.. Google also uses a lot of Python.
Exactly, I've seen a ton of commentary saying it should be easy to just plug the leak and they are letting the leak continue because they want to keep collecting oil from it etc.
Most of the solutions I've seen offered are covered by the saying "Anything is easy if you don't know what your talking about"
To be sure it seems BP messed up badly before the accident by skimping on technology that may have prevented this but the conspiracy theories don't help at all.
It has nothing to do with whether you have a phone or not. When I lived in an apartment in Montreal they would drop one phone book per apartment on the floor next to the mailboxes where they would sit for months.
And they weren't counting land lines.. I got one when I had no phone line at all.
Online from the office that is.
I've seen exactly this happen. Two years ago my coworker and I were dragged to Spain and tossed into an apartment that didn't have internet.
First thing he did was put together a solid gaming machine that weighed a ton. But it was still another month before we would have internet so he was stuck hunting for a crack online just so he could play the game he payed for.
On Linux and OSX apps that want to edit non user files either need to be started as root or they won't run.. period. When MS Windows reaches the same point Microsoft will have finally caught up.
Right now I have mission critical accounting software that won't run as anything but administrator and I don't feel like were winning the security war at all.
I'll grade the C and give it the easiest F ever. C doesn't have to be unreadable and if whoever comes after you can't read the code you aren't doing it right.
This all misses the point though because there were a lot of features they spent years working on that never made it into Vista let alone Windows 7. Microsoft aimed too high with Vista and fell short and the process wasted far too much developer time.
Broadcom's Linux problem is Broadcom. They insist on forcing everyone to use their own crappy non open sourced drive that fails on all but a few kernels. Essentially they are trying to be like NVIDIA without being at all competent at creating drivers. It's a sad day when a company's windows drivers work better in Linux (NDIS) than their Linux drivers.
I had problems with my DELL laptop and Broadcom but I quickly learned the best fix for that is to just order an $18 Atheros based Mini-PCIE card from China and just swap the blasted thing.
In some ways I feel bad for Microsoft because a lot of business critical apps were designed in the windows 3.1/95 era where you could write to files anywhere on the drive and the OS wouldn't stop you. The problem now is that these software developers have yet to join the last decade and stop writing their files wherever they feel like it so now Microsoft is stuck because if they break the apps no one will upgrade leaving things insecure or if they leave things the same way they are now things will be insecure. UAC is the middle road where users get shown exactly what software is a problem but are still able to get work done.
Linux/*BSD/OSX all have the advantage here because on those OS apps that behave so badly won't even run in the first place and that's why non windows people get so annoyed when people go on about how cool UAC is.
You don't need gksudo unless your actually doing something "administrative" like changing system wide settings or installing system wide software.
No non administrative app should ever require root so if you didn't do something where you would otherwise expect to need gksudo you can just assume the prompt is fake.
The reason UAC needs to be so clever is that day to day tasks often cause it to activate and you need to be able to tell the difference.
And except for the ones based on VxWorks (most Linksys and likely other routers) or other routers that run on another embedded OS.
Ipv6 was designed for sparse allocations to allow for easier routing that and if they figured if they need to painfully break something make it large enough so that it only has to be done once.
Ipv4 32 bit.. ipv6 128 bit so really if you wanted to reference the number the same way it would be 255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.
In grade 6 my class had this music teacher who wanted to be all trendy and made us do rap songs about things like the dangers of drug use. Had she actually been "up with it" she would probably have noticed how much we hated doing it. The DOS 5 upgrade ad is causing flashbacks to that music class.
I agree.. The only thing stopping me from using Chrome right now is the throw back to the 90s cookie controls.