From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 301D91381F3 for ; Sun, 26 May 2013 13:00:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 61B52E0D23; Sun, 26 May 2013 12:59:48 +0000 (UTC) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by pigeon.gentoo.org (Postfix) with ESMTP id 5898AE0CA6 for ; Sun, 26 May 2013 12:59:47 +0000 (UTC) Received: from [212.54.42.137] (helo=smtp6.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UgaY6-0004JV-QV for gentoo-dev@lists.gentoo.org; Sun, 26 May 2013 14:59:46 +0200 Received: from 54698b76.cm-12-2c.dynamic.ziggo.nl ([84.105.139.118] helo=data.antarean.org) by smtp6.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UgaY6-0007p0-Bu for gentoo-dev@lists.gentoo.org; Sun, 26 May 2013 14:59:46 +0200 Received: from www.antarean.org (net.lan.antarean.org [10.20.13.13]) by data.antarean.org (Postfix) with ESMTP id 5EF554B for ; Sun, 26 May 2013 14:58:45 +0200 (CEST) Received: from 10.55.16.19 (SquirrelMail authenticated user joost) by www.antarean.org with HTTP; Sun, 26 May 2013 14:59:28 +0200 Message-ID: <67590649bf4a40ee66c557235e41c9b5.squirrel@www.antarean.org> In-Reply-To: <20130525215520.77ca8df0@TOMWIJ-GENTOO> References: <51A08A68.3020900@gentoo.org> <20130525153827.61ed2ca4@TOMWIJ-GENTOO> <5d832c4680bfbd3ae7da6dfe5608be2d.squirrel@www.antarean.org> <20130525215520.77ca8df0@TOMWIJ-GENTOO> Date: Sun, 26 May 2013 14:59:28 +0200 Subject: Re: [gentoo-dev] eselect init From: "J. Roeleveld" To: gentoo-dev@lists.gentoo.org User-Agent: SquirrelMail/1.4.22 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=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: - X-Ziggo-spamscore: -1.9 X-Ziggo-spamreport: BAYES_00=-1.9,RDNS_DYNAMIC=0.982,RP_MATCHES_RCVD=-1.07,TW_JS=0.077 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: eb3e703e-38b6-4c1a-9d20-0cd5462279e5 X-Archives-Hash: 835318c546cfbb839e9a8dfecd3a3f82 On Sat, May 25, 2013 21:55, Tom Wijsman wrote: > On Sat, 25 May 2013 21:09:47 +0200 > "J. Roeleveld" wrote: > >> How will the stop/start part of services/init-scripts/... be done? > > Not sure what you mean here; if you keep init function the same as the > init you boot with, this should continue to work. As an example. Lets say I want to test a new init-system. To do this, I follow the (still to be written) guide on "eselect init" and boot into new-and-shiny-init-system. I am still used to stopping/starting services using "/etc/init.d/ start/stop" And using the "rc" command to add/remove services from the runlevel(s). If I then, accidentally, type "/etc/init.d/xyz start" when "xyz" hasn't been started by any means yet. What will happen? I would assume that openrc will try to start "xyz"? This is, I believe, something that could cause issues as dependencies might also try to start and I then have a service running not managed by the "new-and-shiny-init-system" that I was testing. >> I am assuming that should be for the user to keep in mind, but will >> it be possible to add something that will make init.d-scripts not >> work when systemd is running and unit-files not work when systemd is >> not running? > > They currently just bail out with bogus errors as far as I am aware. > > # /etc/init.d/ntpd start > ntpd | * WARNING: ntpd is already starting > # /etc/init.d/ntpd stop > ntpd | * ERROR: ntpd stopped by something else See above, what about if "ntpd" wasn't running yet? >> >> hooks on reboot are still needed for more complex ones. >> > >> > Which complex cases would these hooks be needed on? >> >> I think one of these would be the stopping/starting of services (see >> above) > > No, if you keep the init system the same as the one you boot with there > should be no problems. See above, what about trying to start services using the method of the not-running init? >> [[ Below is my ONLY remark on that, please feel free to mentally >> paste it as a response any email trying to explain why it's important >> to reduce the boottime ]] > > My intention was not to advocate optimizing boot times; I know, that bit was meant generic, not just as a reply to you. > as a kernel > maintainer / developer I need to test new releases, run git bisects, do > Nouveau reclocking work. I really need this, the average person that > keeps his PC running, not so much; I care for it because I can't wait 2 > minutes, not because I think it's shiny to have such a short boot... > > PS: I'm also a mobile laptop user that no longer has a battery. :/ I believe you can still use hibernate there? :) -- Joost