search for: namescope

...e >> upper-level netdev. For identification purpose, the >> kobject for hidden netdev still presents in the sysfs >> hierarchy, however, no uevent message will be generated >> when the sysfs entry is created, modified or destroyed. >> >> For that end, a separate namescope needs to be carved >> out for IFF_HIDDEN netdevs. As of now netdev name that >> starts with colon i.e. ':' is invalid in userspace, >> since socket ioctls such as SIOCGIFCONF use ':' as the >> separator for ifname. The absence of namescope started >> wi...

...he >> upper-level netdev. For identification purpose, the >> kobject for hidden netdev still presents in the sysfs >> hierarchy, however, no uevent message will be generated >> when the sysfs entry is created, modified or destroyed. >> >> For that end, a separate namescope needs to be carved >> out for IFF_HIDDEN netdevs. As of now netdev name that >> starts with colon i.e. ':' is invalid in userspace, >> since socket ioctls such as SIOCGIFCONF use ':' as the >> separator for ifname. The absence of namescope started >> wi...

...ation purpose, the >> >> kobject for hidden netdev still presents in the sysfs >> >> hierarchy, however, no uevent message will be generated >> >> when the sysfs entry is created, modified or destroyed. >> >> >> >> For that end, a separate namescope needs to be carved >> >> out for IFF_HIDDEN netdevs. As of now netdev name that >> >> starts with colon i.e. ':' is invalid in userspace, >> >> since socket ioctls such as SIOCGIFCONF use ':' as the >> >> separator for ifname. The abse...

...hidden device through the > upper-level netdev. For identification purpose, the > kobject for hidden netdev still presents in the sysfs > hierarchy, however, no uevent message will be generated > when the sysfs entry is created, modified or destroyed. > > For that end, a separate namescope needs to be carved > out for IFF_HIDDEN netdevs. As of now netdev name that > starts with colon i.e. ':' is invalid in userspace, > since socket ioctls such as SIOCGIFCONF use ':' as the > separator for ifname. The absence of namescope started > with ':' can r...

I have an app that has the following in the routes file: namespace "admin" do # ADMINISTRATIVE ROUTES ONLY root :to => ''home#index'' resources :comments do member do get :approve get :reject end end resources :users do member do get :block get :unblock end end end When browing to