From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20703 invoked by uid 1002); 27 Aug 2003 15:00:30 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 27871 invoked from network); 27 Aug 2003 15:00:30 -0000 From: Simon Reynolds To: gentoo-dev@gentoo.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-l5Mosb550iJkTdgBZp0F" Message-Id: <1061996324.4731.74.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 27 Aug 2003 11:00:18 -0400 Subject: [gentoo-dev] RC sysinit suggestion X-Archives-Salt: bdeadbe5-db80-4966-a218-9c12846149a4 X-Archives-Hash: b0664b92fbf00f5b362e8f06f785c00d --=-l5Mosb550iJkTdgBZp0F Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Esteemed developers and other Gentoo enthusiasts, A while back I posted a bug with an updated version crypto-loop to make encrypted swapspaces pretty simple. I've since thought up a couple of improvements/safeguards for it, so I should probably revisit it but that's another matter... Anyway, at the time, my version of crypto-loop didn't activate the swap-space for no good reason other than I just thought that that was what the "Activating Possibly More Swap-Space" in localmount was for. Well, at some point that stopped working because the baselayout changed to initialize an undocumented (except for the source) sysinit level. Since that isn't documented in the rc-script guide I thought that it was a bit confusing. Also, it is now impossible to say something like "before localmount". I had an alternative idea for this though, and was wondering if there was a good reason against it: * Add a new command for use in the depends function: "critical"; that accepts no arguments. * Eliminate the sysinit runlevel and instead just have /sbin/rc verify that all scripts marked as critical are running before we consider the boot level to be started. * Add a check in depscan.sh that prints a large, red warning if there is a critical dependency not currently included in the boot runlevel. I like this because 1) it re-opens the possibility of having a script in the boot level that can run before one of the current five critical dependencies, 2) because it allows dynamic setting of "critical" scripts, and 3) it also makes the existence and definition of critical scripts more clear to rc-script hackers like myself. Even if is deemed a bad idea to remove the sysinit runlevel, I still think that using the critical flag in the depends module would still be an improvement over the current method which is just to list them explicitly in /sbin/rc Let me know what you think. ~Simon Reynolds p.s. I'd more than willing to help implement this suggestion. --=-l5Mosb550iJkTdgBZp0F Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/TMckgqkmI1R75FURAngiAJwJZ+SgkTsVLZ7+AFpxOmvwnNQJQQCdFcK0 wFmdMKHfVxNwjciL3HVR9+g= =ZDwU -----END PGP SIGNATURE----- --=-l5Mosb550iJkTdgBZp0F--