From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QCjYt-0000U2-N3 for garchives@archives.gentoo.org; Thu, 21 Apr 2011 02:24:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1DE841C038; Thu, 21 Apr 2011 02:23:58 +0000 (UTC) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by pigeon.gentoo.org (Postfix) with ESMTP id 4CC6F1C008 for ; Thu, 21 Apr 2011 02:23:23 +0000 (UTC) Received: from epia.jer-c2.orkz.net (D4B2706A.static.ziggozakelijk.nl [212.178.112.106]) (authenticated bits=0) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id p3L2NKZH071239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 21 Apr 2011 04:23:22 +0200 (CEST) (envelope-from jer@gentoo.org) Date: Thu, 21 Apr 2011 04:23:19 +0200 From: Jeroen Roovers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] openrc portage news item Message-ID: <20110421042319.5a3a248e@epia.jer-c2.orkz.net> In-Reply-To: <20110421011221.GA1736@eee> References: <20110413181538.GA2894@linux1> <20110421011221.GA1736@eee> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; i686-pc-linux-gnu) 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 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner X-Archives-Salt: X-Archives-Hash: 4f4b944b7e164bf383373909af789461 On Wed, 20 Apr 2011 20:12:21 -0500 Donnie Berkholz wrote: > From a glance over the guide, it wasn't immediately obvious what in > there would result in a broken system. Perhaps it's the "run > dispatch-conf" that's buried in the middle of a paragraph without > enough emphasis? That's particularly confusing for people who use > etc-update instead, and it *needs* to move somewhere more obvious > like a separate code listing with big tags and bold text. > The line of red text just isn't enough, it needs to stand out even > more. I have converted all my systems to baselayout-2/openrc now, and on all of them, the very /last/ message shown after the emerge run is that "[x] important configuration files [in /etc]" need to be updated. I would think that Gentoo users are already primed to this message and that they would respond accordingly. Even when it's dozens of packages you have updated, this message should stand out, because it's basically the first one you read scrolling back up. > One potential cleaner approach to the same idea Kfir suggested is to > make it an interactive emerge with an ACCEPT_LICENSE-like feature > that pops up something you must read and agree to. I've been thinking about an openrc mechanism that refuses rebooting (reboot, halt, which are calls that openrc handles) when /etc/{conf,init}.d files have not been updated. Anyone game to get coding? :) jer