If you can't trust your developers, you have more than the GPL to worry about. If you think the cost of a GPL violation is bad, just wait and see the results of someone borrowing code claimed by a former employer (or even writing code too similar). Just ask Google where the one thing that has cost them the most pain so far, was a 9 line function that one of their programmers copied into the Android source code..
The GPL is designed to avoid the "What's yours is mine and what's mine is mine" scenario where someone uses the code +their changes to always stay one step ahead of the free version and so the GPL requires that they hand over the full source with any changes they made that were used to build whatever product they shipped. If they made changes to the GPL code that were included in the shipped product, they must publish those changes. On the other hand, if they made changes they did not ship with any product(internal releases etc), they are under no obligation to release those changes.
In this case, they are not shipping all of the changes they made to their source code that was used to build their firmware so that is a clear violation of the GPL.
It's worse than that. Linus would tell everyone not to worry and go on about how Bitkeeper was a great improvement and Larry would prove him wrong by throwing public tantrums and generally playing stupid licensing games. Ex banning IBM from using the free version since they had a competing SCM being built by another (far removed) department. Banning anyone who worked directly on a competing SCM from using Bitkeeper at all. And responding to said developer reverse engineering one of the export interfaces by discontinuing the free version of Bitkeeper.
The best part of it all was that Linus helped him design the thing in the first place.
I'm thinking IBM doesn't use their license anymore. AFIK IBM was only using Bitkeeper for the Linux kernel. Larry made them pay for a license since IBM has it's own competing SCM and the free version banned use by any company that has a competing SCM.
Or you can just use GitHub's Windows client which, the last time I used it required me to use the command line to init non Githib repos but then didn't require the user to use the command line for anything. Might even be better now, it's been a couple of years since I had to support software developers running on windows.,
To be fair I bought a TV a few weeks back from FutureShop because I wanted to compare picture quality myself. In the end, not only was FutureShop cheaper than the local retailers, it was $50 cheaper than Amazon.
When you are the size of the EC, hiring a few developers to add any needed features becomes cheaper than the software licenses for the proprietary competition.
Sorry but you are projecting. By all accounts Clarkson was the one spewing verbal abuse. Clarkson knew he was out of line after the indecent and tried to apologize . Here it is from the BBC report "It was not disputed by Jeremy Clarkson or any witness that Oisin Tymon was the victim of an unprovoked physical and verbal attack"
I love Jeremy Clarkson's work on Top Gear but he was really out of line and I really don't see what other option the BBC had but to let him go.
Right, so you wouldn't punch a guy who called your mom, or someone close to you, a whore? We have to know exactly all those things that provoked Jeremy to punch this guy instead of rushing to a quick and inaccurate judgement.
I really wouldn't. Or at least not now that I'm an adult and have gotten over my teenage anger issues. I may very well tell someone off for name calling or have someone fired but I would not intervene physically unless they either started with physical violence or were doing something to make someone I cared about feel physically in danger (for instance got right in their face/backed them into a corner).
Even if the guy intentionally put his food in the refrigerator, it would not justify flipping out and yelling for 20 minutes
The refrigerator thing would definitely deserve being yelled at, don't you think? Employees have been fired for lesser offences.
It still wouldn't justify a 20 minute screaming tantrum that disrupted the entire hotel. A proportionate response would be to demand the food be heated or file a complaint. A proportionate response could even be to have someone fired (if it were negligent or malicious)
Even if the guy intentionally put his food in the refrigerator, it would not justify flipping out and yelling for 20 minutes, let alone punching the producer in the face.
It has the advantage that it does backwards compatibility well with advance notice when a feature is about to disappear This means that if I need to upgrade my PHP application, I am sure to have a version that supports both the new interfaces and the old deprecated interfaces and more importantly it means that if I have a number of different apps that I need installed, I am not likely to need to move them each into their own VM. Python as an example of everything I hate doesn't even try. Their "fix" is to install a local copy of python with the app which is great until something needs a security update and now someone must upgrade each app's environment individually.
It also, quite amusingly doesn't come pre tuned to handle Oracle databases. Last month a burst of traffic crashed two Oracle instances on Oracle Linux machines I don't maintain. When they called me in to debug it, the problem turned out that the SHM limits were too small.
One thing I absolutely love about PostgreSQL is that it sanity checks the system limits on startup and throws an error if something is off.
Not always, sometimes it's that they want perfection. I had one case where the requirements were pretty much the existing guy's exact experience but they forgot that they didn't hire him in that condition he grew into it as their needs expanded. In the end they found no one and put the decision off for later. In the meantime I wish them the best of luck finding a Linux server admin, storage admin and Mac deployment expert in a single person.
Toshiba: large hole in the bottom where the air gets sucked in and then blown against a heat sink on with tiny fins. dust gets sucked in and blown against the heat sink where it gets stuck and when that dust layer gets thick enough, the only way to clean it is to rip the whole laptop apart. It's almost as if they designed the laptop to wear out after a year or two passes.
Right, you would put Telefonica's pubic key into the authorized_keys on each device file but never the local device public key. The simple fact is that unless they are far more stupid than the article suggests this cannot be used to break into the routers.
Isn't TFS supposed to explain what it's talking about? 1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit? 2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?
Given that they were deployed by one particular provider (Telefónica de España in this case) they probably requested a special firmware from the vendor for their CPE to allow remote management. And then did a bad job of keeping the master key safe (by putting a copy of it on 250,000+ devices). And then the vendor used it elsewhere, too.
Honestly, after the Carna botnet, does anyone think the internet isn't a raging sea of completely compromised devices?
I don't think so. The pubic and private keys are only good for outgoing connections and not incoming.
They could do that, but then Telefonica wouldn't be able to buy the routers from China for $15 each (non wholesale price for the exact model Telefonica had in my house when I lived in Spain).
I strongly suggest avoiding Lenovo completely. They already fail to boot if there is an unrecognized wifi card ( I had to hack the BIOS) and for their latest move towards evilness refuse to charge both third party and batteries the system detects as too old.
Unlikely, it is a minority of malcontents who are upset about SystemD who have created an echo chamber of half truths and outright lies.
Speaking of outright lies... where is your proof that only a minority of people are unhappy about SystemD?
You do realize RedHat (the distro running systemd for the longest) has reported their subscriptions going up for the last several quarters? Meanwhile we have people who are making a lot of noise about leaving but never actually do. (Distrowatch is showing interest in *BSD as dropping) We have a Debian fork claiming to be a bunch of "veteran admins" without naming any of them and a mailing list of people who like to argue more than they like actually doing anything. So where are all of these upset people going?
Let's examine our current environment: Slashdot.
Here there are more people who are deeply against SystemD than there are for SystemD. If you look at the arguments against, there are numerous well-reasoned arguments that nobody from the SystemD has even begun to address.
Well reasoned like the post I was replying to? It managed a "Score 5: Informative" despite not having any arguments that were actually true.
The Slashdot echo chamber is what annoys me the most about all of this. I see posts like "SystemD is Monolithic" (it isn't) "SystemD includes an NTP and DHCP server in PID 1(They are optional and don't run as PID 1). Or my all time favorite: "SystemD" is designed for desktops and makes server administration harder" When the reality is that SystemD was designed with some of the more complicated server setups in mind and the speed improvement on the desktop was mostly an accidental byproduct. The only actual valid complaint I have seen so far is about the binary logs but they are easy to bypass and even with journald doing mostly nothing, the whole thing uses less RAM and disk space than the init system it is replacing.
If you look at the arguments for, they do not seem terribly convincing, such as "this is a better way" or "startup is faster in the best case".
Naturally, this is plumbing and boring by nature. "Works best for this case" is actually a good reason for doing it In the meantime, the old system was a bug ridden mess. I mean really, I had until recently some servers that need a partial filesystem mount followed the network followed by GlusterFS followed by Apache. Care to guess how well that works in a default Debian stable install?
I mean really, even if the damned thing did what it claims to do, the specific implementation is clearly lacking. So I have to ask, why exactly are you so gung-ho for SystemD? Surely you should be gung-ho for a solution, not a specific method. No?
I am not so much pro SystemD as much as I am anti FUD. I am annoyed that I let the slashdot crowd actually made me worry about my future as a Linux admin until I researched for myself what the facts were.In the end, I wouldn't be shocked if SystemD ended up being a good proof of concept and replaced with something else. In the meantime, it solves more problems than it creates and manages to be better than the alternatives.
Debian switched because they were losing market share on larger systems that the current init system only handles under extreme protest.
What are you talking about? losing market share? larger systems? Which systems? How was market share measured? Show me where the Debian project claims this. You sound like an MBA.
Slashdot Mirror
If you can't trust your developers, you have more than the GPL to worry about. If you think the cost of a GPL violation is bad, just wait and see the results of someone borrowing code claimed by a former employer (or even writing code too similar). Just ask Google where the one thing that has cost them the most pain so far, was a 9 line function that one of their programmers copied into the Android source code..
The GPL is designed to avoid the "What's yours is mine and what's mine is mine" scenario where someone uses the code +their changes to always stay one step ahead of the free version and so the GPL requires that they hand over the full source with any changes they made that were used to build whatever product they shipped. If they made changes to the GPL code that were included in the shipped product, they must publish those changes. On the other hand, if they made changes they did not ship with any product(internal releases etc), they are under no obligation to release those changes.
In this case, they are not shipping all of the changes they made to their source code that was used to build their firmware so that is a clear violation of the GPL.
It's worse than that. Linus would tell everyone not to worry and go on about how Bitkeeper was a great improvement and Larry would prove him wrong by throwing public tantrums and generally playing stupid licensing games. Ex banning IBM from using the free version since they had a competing SCM being built by another (far removed) department. Banning anyone who worked directly on a competing SCM from using Bitkeeper at all. And responding to said developer reverse engineering one of the export interfaces by discontinuing the free version of Bitkeeper.
The best part of it all was that Linus helped him design the thing in the first place.
I'm thinking IBM doesn't use their license anymore. AFIK IBM was only using Bitkeeper for the Linux kernel. Larry made them pay for a license since IBM has it's own competing SCM and the free version banned use by any company that has a competing SCM.
Or you can just use GitHub's Windows client which, the last time I used it required me to use the command line to init non Githib repos but then didn't require the user to use the command line for anything. Might even be better now, it's been a couple of years since I had to support software developers running on windows.,
To be fair I bought a TV a few weeks back from FutureShop because I wanted to compare picture quality myself. In the end, not only was FutureShop cheaper than the local retailers, it was $50 cheaper than Amazon.
Or you could submit the changes and have them merged into the project.
When you are the size of the EC, hiring a few developers to add any needed features becomes cheaper than the software licenses for the proprietary competition.
Any manual that encourages Perl encourages bad code.
Sorry but you are projecting. By all accounts Clarkson was the one spewing verbal abuse. Clarkson knew he was out of line after the indecent and tried to apologize . Here it is from the BBC report "It was not disputed by Jeremy Clarkson or any witness that Oisin Tymon was the victim of an unprovoked physical and verbal attack"
I love Jeremy Clarkson's work on Top Gear but he was really out of line and I really don't see what other option the BBC had but to let him go.
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
Right, so you wouldn't punch a guy who called your mom, or someone close to you, a whore? We have to know exactly all those things that provoked Jeremy to punch this guy instead of rushing to a quick and inaccurate judgement.
I really wouldn't. Or at least not now that I'm an adult and have gotten over my teenage anger issues. I may very well tell someone off for name calling or have someone fired but I would not intervene physically unless they either started with physical violence or were doing something to make someone I cared about feel physically in danger (for instance got right in their face/backed them into a corner).
The refrigerator thing would definitely deserve being yelled at, don't you think? Employees have been fired for lesser offences.
It still wouldn't justify a 20 minute screaming tantrum that disrupted the entire hotel. A proportionate response would be to demand the food be heated or file a complaint. A proportionate response could even be to have someone fired (if it were negligent or malicious)
Even if the guy intentionally put his food in the refrigerator, it would not justify flipping out and yelling for 20 minutes, let alone punching the producer in the face.
Someone who hates everything else even more?
It has the advantage that it does backwards compatibility well with advance notice when a feature is about to disappear This means that if I need to upgrade my PHP application, I am sure to have a version that supports both the new interfaces and the old deprecated interfaces and more importantly it means that if I have a number of different apps that I need installed, I am not likely to need to move them each into their own VM. Python as an example of everything I hate doesn't even try. Their "fix" is to install a local copy of python with the app which is great until something needs a security update and now someone must upgrade each app's environment individually.
It also, quite amusingly doesn't come pre tuned to handle Oracle databases. Last month a burst of traffic crashed two Oracle instances on Oracle Linux machines I don't maintain. When they called me in to debug it, the problem turned out that the SHM limits were too small.
One thing I absolutely love about PostgreSQL is that it sanity checks the system limits on startup and throws an error if something is off.
Not always, sometimes it's that they want perfection. I had one case where the requirements were pretty much the existing guy's exact experience but they forgot that they didn't hire him in that condition he grew into it as their needs expanded. In the end they found no one and put the decision off for later. In the meantime I wish them the best of luck finding a Linux server admin, storage admin and Mac deployment expert in a single person.
This one seems better
Why would the guy who wrote the driver in question not have standing?
Beta no longer exists.
Toshiba: large hole in the bottom where the air gets sucked in and then blown against a heat sink on with tiny fins. dust gets sucked in and blown against the heat sink where it gets stuck and when that dust layer gets thick enough, the only way to clean it is to rip the whole laptop apart. It's almost as if they designed the laptop to wear out after a year or two passes.
Right, you would put Telefonica's pubic key into the authorized_keys on each device file but never the local device public key. The simple fact is that unless they are far more stupid than the article suggests this cannot be used to break into the routers.
Isn't TFS supposed to explain what it's talking about?
1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?
2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?
Given that they were deployed by one particular provider (Telefónica de España in this case) they probably requested a special firmware from the vendor for their CPE to allow remote management. And then did a bad job of keeping the master key safe (by putting a copy of it on 250,000+ devices). And then the vendor used it elsewhere, too.
Honestly, after the Carna botnet, does anyone think the internet isn't a raging sea of completely compromised devices?
I don't think so. The pubic and private keys are only good for outgoing connections and not incoming.
They could do that, but then Telefonica wouldn't be able to buy the routers from China for $15 each (non wholesale price for the exact model Telefonica had in my house when I lived in Spain).
I strongly suggest avoiding Lenovo completely. They already fail to boot if there is an unrecognized wifi card ( I had to hack the BIOS) and for their latest move towards evilness refuse to charge both third party and batteries the system detects as too old.
Unlikely, it is a minority of malcontents who are upset about SystemD who have created an echo chamber of half truths and outright lies.
Speaking of outright lies... where is your proof that only a minority of people are unhappy about SystemD?
You do realize RedHat (the distro running systemd for the longest) has reported their subscriptions going up for the last several quarters? Meanwhile we have people who are making a lot of noise about leaving but never actually do. (Distrowatch is showing interest in *BSD as dropping) We have a Debian fork claiming to be a bunch of "veteran admins" without naming any of them and a mailing list of people who like to argue more than they like actually doing anything. So where are all of these upset people going?
Let's examine our current environment: Slashdot.
Here there are more people who are deeply against SystemD than there are for SystemD. If you look at the arguments against, there are numerous well-reasoned arguments that nobody from the SystemD has even begun to address.
Well reasoned like the post I was replying to? It managed a "Score 5: Informative" despite not having any arguments that were actually true.
The Slashdot echo chamber is what annoys me the most about all of this. I see posts like "SystemD is Monolithic" (it isn't) "SystemD includes an NTP and DHCP server in PID 1(They are optional and don't run as PID 1). Or my all time favorite: "SystemD" is designed for desktops and makes server administration harder" When the reality is that SystemD was designed with some of the more complicated server setups in mind and the speed improvement on the desktop was mostly an accidental byproduct. The only actual valid complaint I have seen so far is about the binary logs but they are easy to bypass and even with journald doing mostly nothing, the whole thing uses less RAM and disk space than the init system it is replacing.
If you look at the arguments for, they do not seem terribly convincing, such as "this is a better way" or "startup is faster in the best case".
Naturally, this is plumbing and boring by nature. "Works best for this case" is actually a good reason for doing it In the meantime, the old system was a bug ridden mess. I mean really, I had until recently some servers that need a partial filesystem mount followed the network followed by GlusterFS followed by Apache. Care to guess how well that works in a default Debian stable install?
I mean really, even if the damned thing did what it claims to do, the specific implementation is clearly lacking. So I have to ask, why exactly are you so gung-ho for SystemD? Surely you should be gung-ho for a solution, not a specific method. No?
I am not so much pro SystemD as much as I am anti FUD. I am annoyed that I let the slashdot crowd actually made me worry about my future as a Linux admin until I researched for myself what the facts were .In the end, I wouldn't be shocked if SystemD ended up being a good proof of concept and replaced with something else. In the meantime, it solves more problems than it creates and manages to be better than the alternatives.
Debian switched because they were losing market share on larger systems that the current init system only handles under extreme protest.
What are you talking about? losing market share? larger systems? Which systems? How was market share measured? Show me where the Debian project claims this. You sound like an MBA.
It's right in their "Why SystemD" document. " But the real problems arise on big server setups, where Debian is losing ground because of its antiquated init system. On these systems, you need fine service management, process monitoring, reliable dependencies, complex device setups and proper event handling."