[arch-dev-public] [signoff] udev 118-2

[Dan McGee]

On Thu, Feb 21, 2008 at 9:33 AM, Roman Kyrylych
<roman.kyrylych at gmail.com> wrote:
>
> 2008/2/21, Roman Kyrylych <roman.kyrylych at gmail.com>:
>  > 2008/2/21, Roman Kyrylych <roman.kyrylych at gmail.com>:
>  >
>  > > 2008/2/21, Aaron Griffin <aaronmgriffin at gmail.com>:
>  >  >
>  >  > > This superseeds Dan's previous signoff for the 118 version bump.
>  >  >  >  Included are the following changes:
>  >  >  >   FS#8702 - Fix persistant input devices
>  >  >  >   FS#8878 - Attempted speed up of load-modules.sh
>  >  >  >   FS#8591 - Fix loading of RTC devices
>  >  >  >
>  >  >  >  Additionally, this package is required for the new initscripts which
>  >  >  >  are required for the new ISOs. Please sign off
>  >  >
>  >  >
>  >  > Sorry, won't signoff until http://bugs.archlinux.org/task/9636 will be checked.
>  >
>  >
>  > Actually, it turned out that the bug is in initscripts, not in udev.
>  >
>
>  I've just rendered my system unusable after installing udev-118-2 but
>  not the latest initscripts,
>  because initscripts in core check for start_udev, and when it's not
>  available - falls back to static /dev which obviously has only a
>  couple of files, and no /dev/sda*.
>  User has to remount / in rw mode (to make changes to local db
>  possible), then downgrade udev or update initscripts.
>
>  This happens only when user upgrades udev without upgrading to
>  initscripts first.
>  I don't know how this should be solved in a clean way.
>  Will a big fat warning in udev's pre_upgrade with 'read' command and
>  Ctrl-C possibility be enought?
>  The situation when upgrading initscripts and using older udev is
>  already covered by depends=(... udev>=118 ...) in initscripts'
>  PKGBUILD.

This is exactly why I wanted to do the udev upgrade a bit more gradually...

start_udev sucks, but we can leave it in for an iteration or two.

-Dan