[Click] click proc fs problem

[Eddie Kohler]

Hi Jinyang,

I use 2.6.16.13 all the time with no problem.  How did you install click, by 
hand or with click-install?

Eddie


Jinyang Li wrote:
> Has anyone had problem with mounting click fs with the latest click cvs
> checkout and 2.6.16.13 kernel?
> 
> I'm able to do "mount -t click none /click", however, i cannot access the /click 
> directory afterwards, e.g.
> 
> $ ls /click
> ls: /click: Not a directory
> 
> $ dmesg|tail
> click: starting router thread pid 469 (c7007578)
> kclick: click_read_super
> kclick: click_config_lock
> kclick: 50000000:c75bca00:c7110090: leaving click_inode
> kclick: got root inode c75bca00:c7110090
> kclick: got root directory
> kclick: done click_read_super
> 
> I don't see any kclick verbose output as a result of doing "ls /click".
> 
> Another strange thing different from a working previous click module is that the modules are "permanent" and could not 
> be removed after being inserted.
> 
> $ lsmod
> Module                  Size  Used by
> click                3408192  0 [permanent]
> proclikefs              6740  2 click,[permanent]
> 
> BTW, the srcversion of click module is
> $ modinfo click.ko
> vermagic:       2.6.16.13 386 gcc-3.4
> depends:        proclikefs
> srcversion:     2783D6B919274628FBC2250
> parm:           accessible:make /click world-readable [1] (int)
> parm:           uid:UID owning /click [0] (int)
> parm:           gid:GID owning /click [0] (int)
> parm:           greedy:Click takes a whole CPU [0] (int)
> 
> Many thanks!
> Jinyang
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click