Re: regarding sysfs/kobject separation

2007-09-10 Thread Cornelia Huck
On Sun, 02 Sep 2007 22:40:58 +0900, Tejun Heo <[EMAIL PROTECTED]> wrote: > * Suicidal nodes don't need special treatment. If a file tries to > commit suicide, sysfs will detect the condition and deactivate and drain > the node except for the suiciding reference. Excellent. This is so easy to ove

Re: regarding sysfs/kobject separation

2007-09-09 Thread Tejun Heo
Greg KH wrote: >> * much more compact and flexible interface based on sysfs_dirent instead >> of kobject. > > Why? What would use this kind of interface? Why would you want to > create things in sysfs without a kobject? Compulsory 1:1 mapping between kobject (thus driver model) and sysfs has be

Re: regarding sysfs/kobject separation

2007-09-09 Thread Greg KH
On Sun, Sep 02, 2007 at 10:40:58PM +0900, Tejun Heo wrote: > Hello, just a note to tell you guys what's going on. > > It's taking more time than I expected but it's near completion. I'm > testing things now. After that, they need to be split and documented. > It'll be a BIG change and due to oth

Re: regarding sysfs/kobject separation

2007-09-02 Thread Eric W. Biederman
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 automa

regarding sysfs/kobject separation

2007-09-02 Thread Tejun Heo
Hello, just a note to tell you guys what's going on. It's taking more time than I expected but it's near completion. I'm testing things now. After that, they need to be split and documented. It'll be a BIG change and due to other things including moronic military reserve training, I'll probably