From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 416E9158090 for ; Mon, 23 May 2022 09:39:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 103F0E086A; Mon, 23 May 2022 09:39:28 +0000 (UTC) Received: from turkos.aspodata.se (turkos.aspodata.se [185.140.117.226]) by pigeon.gentoo.org (Postfix) with ESMTP id AF575E084A for ; Mon, 23 May 2022 09:39:27 +0000 (UTC) Received: from turkos.aspodata.se (localhost.aspodata.se [127.0.0.1]) by turkos.aspodata.se (Postfix) with ESMTP id C377381A66A3 for ; Mon, 23 May 2022 11:39:26 +0200 (CEST) Received: by turkos.aspodata.se (Postfix, from userid 1000) id 9BC5381A66A4; Mon, 23 May 2022 11:39:26 +0200 (CEST) X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7+dev X-Exmh-Isig-CompType: comp X-Exmh-Isig-Folder: inbox From: karl@aspodata.se To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] packages touching files in /dev Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <20220523093926.9BC5381A66A4@turkos.aspodata.se> Date: Mon, 23 May 2022 11:39:26 +0200 (CEST) X-Virus-Scanned: ClamAV using ClamSMTP X-Archives-Salt: ed107b64-b58a-4441-8f1c-3ca977683b0a X-Archives-Hash: d7f36d0e725f77d151f616fcd945c100 Dear package maintainers, please do not mess with preexisting files in /dev. I have static /dev and that suit me well for quite a few systems that has a static environment, especially system that are intended to run for a long time and where I tend to minimize the number of running processes, every running process is something that can go wrong. Their /dev/ files are set up for their intended use, and I don't want surprises there. When upgrading it isn't easy to see what package that did something to /dev so it isn't easy to bug the guilty party. If sys-fs/static-dev is installed, please do not touch /dev, if you want you can leave suggestions in some file. Regards, /Karl Hammar