Quietly editing your comment after being called out to hide it is even worse.
1,041 karma · joined May 18, 2013
Quietly editing your comment after being called out to hide it is even worse.
Could you please recommend some good resources for learning to write, in the context of technical writing or more generally?
I wonder if it has anything to do with the way "an" sounds when spoken with an American accent. A mishearing and then repetition of "an accident" seems much more plausible to me than confusion with "on purpose".
"It's called The Grid. No templates, no coding."
The real value comes from things like DockerHub, and getting people to buy into the whole ecosystem.
I'd marked 'docker pull' as out of scope because I thought it would be fairly hard to interface with their API from bash, looks like I was wrong.
One of the things I found really interesting here is how much could be done with just basic userland tools, and how old some of those tools are.
Docker was released in 2013, but support for kernel namespacing has been around since ~2007. That's quite a long time for such a great feature to go mainstream.
I'll have to look info CoreOS's reasons for going with Ext4.
The author(A) allows the distributor(D) to distribute their(A) code so long as they(D) provide the source plus any modifications to the recipient.
The recipient has no right to demand the code due to there being no agreement to provide it between the distributor and the recipient.
So the author, on behalf of the recipient, must be the one to enforce the conditions of the agreement they made with the distributor.
In cases involving projects like Linux or BusyBox this can be anyone who has committed code, as these projects do not require copyright assignment.
In cases involving projects like GNU and Ubuntu all committed code is owned by the parent organization, the FSF and Canonical respectively. So they are the only ones who can enforce the GPL.
That said, the end user can report violations to groups like The Software Freedom Law Center and GPL-Violations.org. These groups have contacts to various copyright holders and will assist with enforcing them on a pro bono basis.
Additionally the biggest problem I find when turning off the heating in winter is hands and feet. You can wear gloves but then you can't type.
Are they a "true" engineer? That's probably not for me to say, but the roles of "Systems Engineer" and "Systems Administrator" are very different things in my experience.
The point of the GPL is to fight for the rights of the user, no matter if that user is a single hacker wanting to tinker with the code or a giant multinational wanting to use it for $$$.
1. Delve Labs has commercial scanners which bundle but do not link with WPScan.
2. WPScan, previously licensed under the GPL, introduce a commercialization clause in addition to the GPL.
Side Note. WPScan may not have the right to do this because they do not use copyright attribution. Without this they need permission from everyone who has ever contributed code to their project.
3. WPScan demand money from Delve Labs.
4. Delve Labs make a fork from a point before WPScan introduced the commercialization clause. They keep this version licensed under the GPL.
1: http://www.techempower.com/benchmarks/#section=data-r9&hw=ec...
We only saw the issue when using the "iSCSI Auto-Config" mode. Manually configuring the switches with the same config but entered by hand resolved the issue.
The pain of ruby versions / gem versions are often felt by developers who are working with various untested components.
For traditional end users a package manager hides all of this and by typing "pkgmgr install rubyapp" it will pull in stable and well tested versions of ruby plus any dependencies. Applications installed this way should just work without the user going anywhere near rubygems.
So the real value added here is for developers not having to create/manage packages? Surely this is offset by the huge number of issues that working outside of a package manager causes. No shared libraries/dependencies, no universal way to update everything, no ability to manage installations with tools such as puppet/chef, no global mirror network, no assurances of package integrity, ect.
Windows + Vim: https://i.imgur.com/soTIhNy.png
SSH + Vim: https://i.imgur.com/aLs9ACy.png
GNOME Foundation - January 2002 - Present (12 Years 11 Months)