On Sun, 04 Jan 2009, Petter Reinholdtsen wrote: > The async kernel also affect network interfaces, so we might need to > come up with a solution there.
You can use the very same solution. Use the rw store to do it just once, key by MAC, and add helpers to ifup interfaces marked as auto assyncronously, updating the sync initscript to not do the job twice. I think the only issue with network interfaces and disks is that you must make sure to only try to process them, after the rest of the userspace setup crap is done (such as renaming of network interfaces by udev, addition of /dev nodes based on UUID and so on for disks, etc). We clearly will need help from maintainers of the other subsystems on this, particularly from the udev maintainer to help us get all locking and timing correct. We can't play something like this by the ear. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org