From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx-relay31-dus.antispameurope.com ([94.100.134.231]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1WUc2t-0001IE-MB for ptxdist@pengutronix.de; Mon, 31 Mar 2014 15:14:36 +0200 From: "Gieseler, Christian" Date: Mon, 31 Mar 2014 13:13:28 +0000 Message-ID: Content-Language: de-DE MIME-Version: 1.0 Subject: [ptxdist] machine-id 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" Hi List, while thinking how to preserve the existing machine-id after an complete update I had I look how this is generated. In the rc-once.d folder there is a script generating an id and systemd also has the capability to generate one and obviously does check for a valid machine-id and regenerates one in case of an invalid/non exisiting one. Looking into the dependencys the ptxdist machine-id script is selectd with systemd. Is the existance of the ptxdist machine-id necessary if systemd takes care of the machine id? And finaly coming back to the original question what is the best way to preserve the machine-id? Patching Systemd to change the hardcoded path? Or are there other smarter solutions? Best regards Christian Gieseler -- ptxdist mailing list ptxdist@pengutronix.de