Bug 181593 - anaconda, udev, and upgrades
anaconda, udev, and upgrades
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
Blocks: FC5Blocker
  Show dependency treegraph
Reported: 2006-02-14 19:54 EST by Bill Nottingham
Modified: 2014-03-16 22:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-20 15:28:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2006-02-14 19:54:42 EST
1. Install FC2
2. Start anaconda to upgrade

anaconda bind mounts its own /dev for the upgraded system

3. Have anaconda upgrade
4. anaconda installs new packages. Including udev.
5. anaconda starts removing old packages. It gets to dev.
6. dev starts removing its files... including device nodes in the /dev shared
between anaconda and the upgraded system?
7. udev has the following trigger:

triggerpostun scriptlet (using /bin/sh) -- dev <= 0:3.12-1
if [ $2 = 0 ]; then
        if [ -x /sbin/MAKEDEV ]; then
                /sbin/MAKEDEV null
                /bin/mknod /dev/null c 1 3
        /sbin/start_udev >/dev/null 2>&1
        if [ -e /dev/mapper/control -a -x /sbin/lvm ]; then
                /sbin/lvm vgmknodes >/dev/null 2>&1
exit 0

start_udev runs... which not only starts udev in the chroot, it also starts
loading modules - sound modules, hardware monitors, random drivers. It also
starts firing off all the helper programs for these - unmuting sound, etc.

All this during the end of the upgrade.

Not sure what we want to do here, but this probably isn't it. :)

I *think* this can be solved by adding dev to the upgrade_remove_blacklist;
this should run before the dev is bind mounted, even...
Comment 1 Jeremy Katz 2006-02-15 14:51:17 EST
Yeah, sounds like a sane enough resolution I guess.  That or the call to
start_udev in the trigger should call something which doesn't do all the module
loading stuff that udev has grown.
Comment 2 Harald Hoyer 2006-02-16 02:10:04 EST
Hmm, we cannot disable module loading without loosing device creation, without
altering the rules...
Comment 3 Jeremy Katz 2006-02-20 15:28:06 EST
Added dev to the upgrade_remove_blacklist

Note You need to log in before you can comment on or make changes to this bug.