Messages in this thread | | | Date | Fri, 4 Jun 2004 13:26:53 -0700 | From | Greg KH <> | Subject | Re: 2.6.7-rc2-bk4: empty-named directory in /sys |
| |
On Fri, Jun 04, 2004 at 10:53:23PM +0300, Denis Vlasenko wrote: > # ls /sys > block bus class devices firmware module > # ls -l /sys > total 0 > drwxr-xr-x 9 root root 0 Jun 5 2004 > drwxr-xr-x 29 root root 0 Jun 5 2004 block > drwxr-xr-x 10 root root 0 Jun 5 2004 bus > drwxr-xr-x 16 root root 0 Jun 5 2004 class > drwxr-xr-x 7 root root 0 Jun 5 2004 devices > drwxr-xr-x 2 root root 0 Jun 5 2004 firmware > drwxr-xr-x 30 root root 0 Jun 5 2004 module > > I cannot enter that directory. Actually, it looks more like > directory named " ", because I get similar ls outputs when > I create regular directory named " ". However, I can enter into > regular directory named " ", unlike /sys one. > > # mkdir " " a b c > # ls > a b c > # ls -l > total 0 > drwxr-xr-x 2 root root 48 Jun 4 22:45 > drwxr-xr-x 2 root root 48 Jun 4 22:45 a > drwxr-xr-x 2 root root 48 Jun 4 22:45 b > drwxr-xr-x 2 root root 48 Jun 4 22:45 c > > .config and boot messages are attached
Hm, is the hostap code in the main kernel tree now? That's the only thing odd that I see from your messages. Does this happen with 2.6.7-rc2 with no extra patches?
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |