Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] WARNING: boot order/init.d changes test grimoire

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: George Sherwood <pilot AT beernabeer.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] WARNING: boot order/init.d changes test grimoire
  • Date: Sun, 19 Mar 2006 15:11:51 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 11 Mar 2006 23:28:01 -0600
"Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org> wrote:

> I've just integrated some pretty significant changes to the init.d and
> module-init-tools spells in test. These change the boot order from
> 'mountall.sh', 'modutils' to a new 'mountroot.sh', 'modutils',
> 'mountall.sh'. These are necessary to get better support for LVM2
> and to allow general use of other module-based filesystems. See bugs
> 9177 and 10146.
>
> These changes have been in devel for the last couple of weeks and
> tested on several systems without an issue, however I wanted to
> mention them here since changes like this have potential to make
> systems unbootable. If you're a paranoid person you may want to make
> sure you're around when these updates hit your system(s) so you can
> make sure nothing breaks for you.
>
> Basically the next time you 'scribe update test' and 'sorcery queue'
> you should see that init.d and module-init-tools want to update.
> They have UP_TRIGGERS to make sure they cast together. They'll each
> prompt to enable/set as default a couple of new providers
> (mountroot.sh for root_fs and modutils for modules); they should
> default to 'y' and you definitely want to say 'y'.
>
> Once this is done you should reboot if possible to make sure nothing
> in your system's boot process is broken. If you can't reboot yet you
> may want to just make sure at your next reboot you're watching it
> (again, if you're paranoid).
>
> The one known caveat is that if you just do 'cast init.d' (instead of
> eg 'cast --queue') you should make sure you use 'cast -c init.d',
> otherwise the init scripts may not get enabled correctly if you
> already have the existing version installed and it just gets
> resurrected.
>
> If you have any questions or issues please let me know.

Looks like I had one machine get bit by this. I did a cast --queue
and all seemed to go well. There was all the spells from the recent
gnome updates, so I guess didn't see all that was being cast. It is a
really old install so maybe the TRIGGER didn't work correctly. Now it
boots until entering runlevel 2 and then hangs after success with
network. I booted with a rescue disk and mounted the disk. Looks to me
like the new init.d got cast but not module-init-tools for some
reason. Any idea how I an go about getting this system working again?

George Sherwood
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEHbsMkVJnfkgKg60RAivQAJ49xYMvt2pgOqR2skVn/i7P5btaDACfcI/O
deApmC3lyDIPMPl5yUjIItU=
=XRan
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.24.

Top of Page