From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0] ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YZJbE-0003Ao-4Y for ptxdist@pengutronix.de; Sat, 21 Mar 2015 14:38:00 +0100 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80) (envelope-from ) id 1YZJbE-0001ez-3L for ptxdist@pengutronix.de; Sat, 21 Mar 2015 14:38:00 +0100 Date: Sat, 21 Mar 2015 14:38:00 +0100 From: Michael Olbrich Message-ID: <20150321133800.GK20453@pengutronix.de> References: <201503161419.38672.jbe@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] [PATCH] Dropbear: Provide init script install entry only for the initV based system startup Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de On Mon, Mar 16, 2015 at 02:53:19PM +0100, Alexander Dahl wrote: > I had a brief look and it seems the dropbear package does not provide a > systemd unit file, so AFAIK systemd should use the legacy init script > for starting up dropbear. In other words: the startscript can be used by > systemd if there's no unit file and will always be used by bbinit. That does not work. 1. systemd sysv legacy support is disabled in PTXdist 2. It only works with init scripts with lsb headers. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list ptxdist@pengutronix.de