Tejun Heo <[EMAIL PROTECTED]> writes: > * Automatic symlink handling. Symlink names can be formatted with the > name of its target. e.g. if the symlink name is specified as > "link-%1:%0" and points to "devices/mybus0/mydev0", its name becomes > "link-mybus0-mydev0" && the symlink will be automatically renamed when > the target node or one of its ancestor is moved or renamed. The symlink > is also plugged and removed together with its target. So, once created, > the user doesn't have to care about the symlink. sysfs will take care > of it.
Sounds nice. > * I think most of the changes wouldn't hinder implementation of tagged > nodes. In fact, most of the new rename logic which handles symlink > rename together is taken from tagged node implementation, so with some > luck it should be easier to support tagged nodes. Hopefully. > *** Future plans. > > * Move uevent support over to sysfs and bridging the current users. > This makes sense because sysfs hierarchy is all that userland can see > and sysfs users which don't use kobject also needs uevent support. This could have an interesting interaction with the namespace work. I think my current implementation only makes these events visible in the initial network namespace. But that should change. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
