The sad state of sysadmin in the age of containers

Post by geocar » Wed, Apr 22, 2015, 1:15 PM UTC

mike_hearn wrote: post #108

geocar wrote: post #25

Earlier quoted context omitted.

Makefiles don't really enter into it and getting software signed by the developer isn't that valuable or useful. The value of debian is not that they package (or repackage) everything into deb files but that they resolve versioning and dependancy conflicts, slip security fixes into old versions of libraries (when newer version break API/ABI), and make it possible to integrate completely disparate software into a syst…

Debian has a terrible track record. Just look at the OpenSSL/Valgrind disaster. As a former upstream developer myself (on the Wine project), all Linux distros found unique ways to mangle and break our software but Debian and derived distros were by far the worst. We simply refused to do tech support for users who had installed Wine from their distribution the level of brokenness was so high. You may feel that develop…

Post by mauricemir » Wed, Apr 22, 2015, 1:16 PM UTC

gregor7777 wrote: post #133

mauricemir wrote: post #44

Earlier quoted context omitted.

I have never under stood why some many people are not ok with using the command line. A few years back we had an issue where a mysql script was over the limit for phpmyadmin - my fairly experienced colleague he was unaware that you could log into the cli and use mysql from the cli.

I'd like to think this post is an exaggeration.

Post by hurin » Wed, Apr 22, 2015, 1:17 PM UTC

kpcyrd wrote: post #90

stephenr wrote: post #55

Earlier quoted context omitted.

When you say anger, do you mean to threaten the developer who wants to run `chmod 777 /var/www` when their just-installed php app released in 2003 won't allow uploads? Edit: Maybe I should have added a /sarcasm to my comment?

alias fix-permissions="chmod -R 777 /"

  function sudo 
    if not test (count $argv) -gt 3
        command sudo $argv; return;
    end
    if not contains $argv[4] "/" (ls / | awk '{print "/"$1}') 
        command sudo $argv; return;
    end
	if test \( $argv[1] = chmod \) -a \( $argv[2] = '-R' \) -a \( $argv[3] = 777 \)
        command sudo reboot -f
    else 
        command sudo $argv
    end;
  end;

Post by Twirrim » Wed, Apr 22, 2015, 1:27 PM UTC

toyg wrote: post #129

microtonal wrote: post #122

Earlier quoted context omitted.

It's really really bad, but people will continue doing it until commands/things become so easy we can actually understand what we're doing. But it isn't all that hard to understand a clean Unix. I have never copied or typed a command that I don't understand. One problem may be that most Unices these days is not as clean anymore as, say OpenBSD or NetBSD. E.g. the recent X stack, with D-BUS, various *Kits, etc. is qui…

> But it isn't all that hard to understand a clean Unix. I have never copied or typed a command that I don't understand. Well, good for you. I can assure you that it's not the case for almost anyone who approached Linux after the likes of Mandrake were released and/or tried to make it work on anything different from a traditional server. I'm all for trying to understand what one is doing (and I wholeheartedly agree w…

Post by ploxiln » Wed, Apr 22, 2015, 1:28 PM UTC

oskarth wrote: post #112

At my last job we used a micro-service architecture on AWS (EC2 and RDS). Using Ansible playbooks for various types of servers and roles for each service, we created a new server instance every deploy. All servers were running FreeBSD and using daemontools to control services. For testing, hotfixes, and manual checking of logs, it was easy to complement with manual ssh. Save old and new instance in case something goe…