<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>SecOPS / SysOp blog - Latest Comments</title><link>http://sysopsblog.disqus.com/</link><description></description><atom:link href="https://sysopsblog.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 05 Jan 2019 10:54:57 -0000</lastBuildDate><item><title>Re: Gmail like &amp;#8220;+&amp;#8221; adresses aliases in Postfix</title><link>https://maciek.lasyk.info/sysop/2013/12/27/gmail-like-adresses-aliases-in-postfix/#comment-4270890628</link><description>&lt;p&gt;Hi, can "recipient_delimiter = +" be restricted to some domains only on the server?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vishnu N</dc:creator><pubDate>Sat, 05 Jan 2019 10:54:57 -0000</pubDate></item><item><title>Re: KVM &amp;#8211; libvirt-guests &amp;#8211; autostart / shutdown / pause</title><link>https://maciek.lasyk.info/sysop/2013/04/29/kvm-libvirt-guests-autostart-shutdown-pause/#comment-2630730354</link><description>&lt;p&gt;An easy way to make systems start up in order, sort of, is, set the GRUB_TIMEOUT to each machine differently.  First server, 1 second.  Second server, perhaps 30 seconds, etc.  It's crude, but works great for me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ralph Horque</dc:creator><pubDate>Mon, 18 Apr 2016 20:01:27 -0000</pubDate></item><item><title>Re: How to change OVH kernel to normal Centos kernel</title><link>https://maciek.lasyk.info/sysop/2012/12/23/how-to-change-ovh-kernel-to-normal-centos-kernel/#comment-2316511438</link><description>&lt;p&gt;Hi!&lt;/p&gt;&lt;p&gt;I found this tutorial because I have similar needs. But after all steps, centos complaint about network card&lt;/p&gt;&lt;p&gt;eth2 is not present...&lt;/p&gt;&lt;p&gt;Did you have any net issues?&lt;/p&gt;&lt;p&gt;Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ruben Ortiz</dc:creator><pubDate>Tue, 20 Oct 2015 06:35:33 -0000</pubDate></item><item><title>Re: SELinux &amp;#038;&amp;#038; Ganglia / Multicast &amp;#038;&amp;#038; Apache &amp;#038;&amp;#038; RRDs</title><link>https://maciek.lasyk.info/sysop/2013/09/29/selinux-ganglia-multicast-apache-rrds/#comment-2019795333</link><description>&lt;p&gt;BZ filed against RHEL-7 &lt;a href="https://bugzilla.redhat.com/show_bug.cgi?id=1220663" rel="nofollow noopener" target="_blank" title="https://bugzilla.redhat.com/show_bug.cgi?id=1220663"&gt;https://bugzilla.redhat.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Milos Malik</dc:creator><pubDate>Tue, 12 May 2015 03:20:55 -0000</pubDate></item><item><title>Re: SELinux &amp;#038;&amp;#038; Ganglia / Multicast &amp;#038;&amp;#038; Apache &amp;#038;&amp;#038; RRDs</title><link>https://maciek.lasyk.info/sysop/2013/09/29/selinux-ganglia-multicast-apache-rrds/#comment-2019786522</link><description>&lt;p&gt;The same problem appears on RHEL-7 too, when ganglia-3.7.1-2.el7 is used.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Milos Malik</dc:creator><pubDate>Tue, 12 May 2015 03:07:09 -0000</pubDate></item><item><title>Re: SELinux &amp;#038;&amp;#038; Ganglia / Multicast &amp;#038;&amp;#038; Apache &amp;#038;&amp;#038; RRDs</title><link>https://maciek.lasyk.info/sysop/2013/09/29/selinux-ganglia-multicast-apache-rrds/#comment-2016429574</link><description>&lt;p&gt;Hah, nice Dan - thx; above method is rather nasty workaround - I didn't even check if there is any Ganglia policy back then :/&lt;/p&gt;&lt;p&gt;Btw - there's still no official Ganglia packages for RHEL7, so not sure if this problem will be replicated or not. Interesting&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Sun, 10 May 2015 04:12:54 -0000</pubDate></item><item><title>Re: SELinux &amp;#038;&amp;#038; Ganglia / Multicast &amp;#038;&amp;#038; Apache &amp;#038;&amp;#038; RRDs</title><link>https://maciek.lasyk.info/sysop/2013/09/29/selinux-ganglia-multicast-apache-rrds/#comment-2013648122</link><description>&lt;p&gt;Good article.  BZ filed for this bug, here: &lt;a href="https://bugzilla.redhat.com/show_bug.cgi?id=1219900" rel="nofollow noopener" target="_blank" title="https://bugzilla.redhat.com/show_bug.cgi?id=1219900"&gt;https://bugzilla.redhat.com...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dan Yocum</dc:creator><pubDate>Fri, 08 May 2015 11:59:25 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1712651683</link><description>&lt;p&gt;Thanks for the help, sounds like LXC is more fit for me. But I'll look into Docker as well, I'm curious how it works for my lab.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frederic Mohr</dc:creator><pubDate>Tue, 25 Nov 2014 16:31:50 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1712567371</link><description>&lt;p&gt;First of all Ansible is an automation tool, so you can use it for LXC and for Docker orchestration.&lt;/p&gt;&lt;p&gt;So let's keep to this "Docker vs LXC" subject. After couple of months I can write couple of things:&lt;/p&gt;&lt;p&gt;1. LXC is awesome, but so is Docker. It depends on use - cases and your situation&lt;br&gt;2. If you're building continuous integration (/deployment) env then Docker is a way to go (see my last presentation: &lt;a href="http://www.slideshare.net/d0cent/orchestrating-docker-containersatscale" rel="nofollow noopener" target="_blank" title="www.slideshare.net/d0cent/orchestrating-docker-containersatscale"&gt;www.slideshare.net/d0cent/o...&lt;/a&gt; )&lt;/p&gt;&lt;p&gt;3. If this is only about lightweight virtualization (containerization) of your already existing envs then you could probably go with LXC. This is because you can use your already created workflows / tools with LXC as those containers simulate VMs in many ways Docker is a completely different approach (Single Application Containers - this means that only one process should be created in Docker container and those should be treated as ephemeral).&lt;/p&gt;&lt;p&gt;I think that I should work on an update for this post as this is really interesting subject. If you have any more questions - plz ask :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Tue, 25 Nov 2014 15:41:13 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1711516407</link><description>&lt;p&gt;So, what's your answer a few months later? I currently have my &lt;br&gt;private lab running on LXC and I want to automate things with ansible. &lt;br&gt;But docker keeps popping up everywhere so I'm not sure if I should use &lt;br&gt;it instead.&lt;/p&gt;&lt;p&gt;The thing is, that this is a dev-env for me so I'm spinning up pre-setup operating systems more than pre-setup applications.&lt;/p&gt;&lt;p&gt;Is Docker a good choice or should I stick to plain LXC and introduce ansible to it?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frederic Mohr</dc:creator><pubDate>Tue, 25 Nov 2014 05:13:57 -0000</pubDate></item><item><title>Re: Gmail like &amp;#8220;+&amp;#8221; adresses aliases in Postfix</title><link>https://maciek.lasyk.info/sysop/2013/12/27/gmail-like-adresses-aliases-in-postfix/#comment-1571664878</link><description>&lt;p&gt;you can use "recipient_delimiter = +" in postfix's config instead&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eric</dc:creator><pubDate>Wed, 03 Sep 2014 05:56:34 -0000</pubDate></item><item><title>Re: Private: Atmosphere Conference 2014 recap</title><link>https://maciek.lasyk.info/sysop/2014/05/26/atmosphere-conference-2014-recap/#comment-1495769767</link><description>&lt;p&gt;Unfortunately those are not posted yet; try following this conference's youtube channel &lt;a href="http://www.youtube.com/user/AtmosphereConference" rel="nofollow noopener" target="_blank" title="http://www.youtube.com/user/AtmosphereConference"&gt;http://www.youtube.com/user...&lt;/a&gt; - probably they'll upload videos soon&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Mon, 21 Jul 2014 11:30:08 -0000</pubDate></item><item><title>Re: Private: Atmosphere Conference 2014 recap</title><link>https://maciek.lasyk.info/sysop/2014/05/26/atmosphere-conference-2014-recap/#comment-1468257025</link><description>&lt;p&gt;Is there an accompanying video?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Woody</dc:creator><pubDate>Fri, 04 Jul 2014 09:42:28 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1304617977</link><description>&lt;p&gt;If you mean for the testing platform I plan to use plain Dockerfiles. Ansible for the rest.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">victorcoder</dc:creator><pubDate>Wed, 26 Mar 2014 19:28:17 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1297831385</link><description>&lt;p&gt;What tools will u use for automation?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Sun, 23 Mar 2014 16:33:20 -0000</pubDate></item><item><title>Re: Docker vs LXC/Ansible?</title><link>https://maciek.lasyk.info/sysop/2014/03/16/docker-vs-lxcansible/#comment-1292895852</link><description>&lt;p&gt;I'm in the exact same state as you but instead of duplicating efforts I'm planning to use Docker to build an automated teting env (I use vagrant/ansible for the dev platform and I'm quite happy) time will say.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">victorcoder</dc:creator><pubDate>Thu, 20 Mar 2014 05:41:42 -0000</pubDate></item><item><title>Re: Google Reader is dead. What now?</title><link>https://maciek.lasyk.info/sysop/2013/07/01/google-reader-is-dead-what-now/#comment-948278774</link><description>&lt;p&gt;Nice one - I could go this way if I knew it earlier ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Mon, 01 Jul 2013 16:21:29 -0000</pubDate></item><item><title>Re: Google Reader is dead. What now?</title><link>https://maciek.lasyk.info/sysop/2013/07/01/google-reader-is-dead-what-now/#comment-947795326</link><description>&lt;p&gt;I went for &lt;a href="http://www.newsblur.com/" rel="nofollow noopener" target="_blank" title="http://www.newsblur.com/"&gt;http://www.newsblur.com/&lt;/a&gt; and for now quite happy with that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Grzegorz Szczepanik</dc:creator><pubDate>Mon, 01 Jul 2013 07:11:53 -0000</pubDate></item><item><title>Re: (Polish) Opowieść o chorym administratorze, czyli OpenSource w walce ze zbyt wysokim ciśnieniem wody</title><link>https://maciek.lasyk.info/sysop/2013/01/20/polish-opowiesc-o-chorym-administratorze-czyli-opensource-w-walce-ze-zbyt-wysokim-cisnieniem-wody/#comment-773390902</link><description>&lt;p&gt;Mam w domu PandaBoarda (&lt;a href="http://pandaboard.org/)" rel="nofollow noopener" target="_blank" title="http://pandaboard.org/)"&gt;http://pandaboard.org/)&lt;/a&gt; - i powoli zaczynam realizować monitoring CO, temperatury, ruchu itd. Bardzo powoli - to taki projekt, który wyląduje na koniec na githubie :)&lt;/p&gt;&lt;p&gt;Odnośni elektrozaworu i tego co podesłałeś - super pomysł :) Piec będę wymieniał w okolicach wakacji jak się cieplej zrobi, to akurat w sam raz :) Dzięki&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Sun, 20 Jan 2013 16:49:58 -0000</pubDate></item><item><title>Re: (Polish) Opowieść o chorym administratorze, czyli OpenSource w walce ze zbyt wysokim ciśnieniem wody</title><link>https://maciek.lasyk.info/sysop/2013/01/20/polish-opowiesc-o-chorym-administratorze-czyli-opensource-w-walce-ze-zbyt-wysokim-cisnieniem-wody/#comment-773372839</link><description>&lt;p&gt;A co myślisz o zakupie coś ala aldruino za 100zł, na pewno byś sobie poradził z skonfigurowaniem modułu internetowego. Do tego mikrokontrolera podpiąłbyś czujnik ciśnienia. Dla pełnego zautomatyzowania wpiąłbyś przy odpowietrzeniu kaloryfera elektrozawór sterowany tak samo. if ciśnienie &amp;gt; 3 {zawór=open} else zawór =closed. Zaraz zaraz... Można przecież kupić &lt;a href="http://www.skleparmatura.pl/syr/syr-zawory-itp/12443.html" rel="nofollow noopener" target="_blank" title="http://www.skleparmatura.pl/syr/syr-zawory-itp/12443.html"&gt;http://www.skleparmatura.pl...&lt;/a&gt; za 40 zł.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pitorek</dc:creator><pubDate>Sun, 20 Jan 2013 16:12:39 -0000</pubDate></item><item><title>Re: Postfix: Backup MX</title><link>https://maciek.lasyk.info/sysop/2012/01/06/postfix-backup-mx/#comment-500066760</link><description>&lt;p&gt;No it's not necessary, but due to some security reasons it's good to use it (but remember to do it together with permit_mx_backup_networks). There were problems with backups MX over IPv6 DNS records - under some circumstances it was possible to inject some messages to the backup MX server from a spam-server in order to deliver it to the main mail server. I believe, that this is already patched, but I see no reasons not to use this particular configuration option.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Tue, 17 Apr 2012 15:07:08 -0000</pubDate></item><item><title>Re: Postfix: Backup MX</title><link>https://maciek.lasyk.info/sysop/2012/01/06/postfix-backup-mx/#comment-500046233</link><description>&lt;p&gt;Is it really necessary to add the permit_mx_backup ? In my first setup, I found that it worked as expected without permit_mx_backup. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Xcom</dc:creator><pubDate>Tue, 17 Apr 2012 14:42:44 -0000</pubDate></item><item><title>Re: Wacom Bamboo Fun in Fedora 15</title><link>https://maciek.lasyk.info/sysop/2012/01/11/wacom-bamboo-fun-in-fedora-15/#comment-497471647</link><description>&lt;p&gt;Thanks for this tip - will use for sure ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Sat, 14 Apr 2012 09:48:53 -0000</pubDate></item><item><title>Re: Wacom Bamboo Fun in Fedora 15</title><link>https://maciek.lasyk.info/sysop/2012/01/11/wacom-bamboo-fun-in-fedora-15/#comment-497437296</link><description>&lt;p&gt;Thank you for the post!&lt;br&gt;Just a small comment: to set working space of the tablet to a specific display, you can also use the "MapToOutput" option of xsetwacom.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nick</dc:creator><pubDate>Sat, 14 Apr 2012 09:24:48 -0000</pubDate></item><item><title>Re: Hello there!</title><link>https://maciek.lasyk.info/sysop/2011/12/05/hello-there/#comment-381596821</link><description>&lt;p&gt;Just testing disquis integration :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maciej Lasyk</dc:creator><pubDate>Wed, 07 Dec 2011 18:09:17 -0000</pubDate></item></channel></rss>