I think this can probably be decomposed in to a series of problems that result in this bug:
1) Networking in specific, but all devices in general, should have a way of specifying if it's an 'initrd', 'early', 'late' or 'later/optional' type of event. initrd items would be rolled in to the initrd script with their dependencies and run before the root file system was mounted. early items would run after root was mounted RO but before anything else. late would run after root is mounted RO (very likely with all other filesystems being mounted first at this point). later/optional events would run in the background automatically after a terminal/X login was started if the hardware existed, or would trigger after that stage when hardware is hot-plugged. 2) early WPA might work if the correct directories are mounted as RW using a ram based filesystem and any files that required write access were there. (/dev/shm comes to mind) 3) Sane defaults for these things, and 'Are you REALLY sure you want to do this? It looks like you're going to brick your system if you start your crypto late.' with full mollyguard style 'enter the system name and module name in question' confirmation boxes for deviations on items marked as critical. 3 would allow for the current (everything but /boot) LUKS + LVM setups to properly integrate (instead of with a warning and occasional failures) in to the initrd but later upgrade if users wanted and it was supported, to unlocking things like /home based on the users current login information, or some other UI improvement. -- wpasupplicant doesn't start when the network start https://bugs.launchpad.net/bugs/44194 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
