From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: util-linux-owner@vger.kernel.org Received: from zeniv.linux.org.uk ([195.92.253.2]:53843 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753419Ab2ATSrV (ORCPT ); Fri, 20 Jan 2012 13:47:21 -0500 Date: Fri, 20 Jan 2012 18:47:17 +0000 From: Al Viro To: Denys Vlasenko Cc: Karel Zak , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, util-linux@vger.kernel.org Subject: Re: /etc/fstab.d yes or not Message-ID: <20120120184716.GB23916@ZenIV.linux.org.uk> References: <20120120140444.GC13157@x2.net.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: util-linux-owner@vger.kernel.org List-ID: On Fri, Jan 20, 2012 at 07:20:33PM +0100, Denys Vlasenko wrote: > On Fri, Jan 20, 2012 at 3:04 PM, Karel Zak wrote: > > ?BTW, systemd allows to define addition mountpoints in > > ?systemd.mount(5) unit file(s), so we already have additional place > > ?for fstab stuff... > > systemd needs a large blunt object be stuck into its eye. > > systemd was supposed to be an init replacement. > Its continuing attempts to infiltrate entire system > are very worrying. I'm not saying I like /etc/foo.d/* (hell, sed in post-install is not a big deal; not for fstab, not for inetd.conf, etc.), but yes, complaints about changes that make life somewhat more difficult for systemd are rather hypocritical, what with the embrace-and-extend games they are playing.