[bproc]I need to help about Bproc-2.2.2.

[Rob Latham]

On Tue, May 22, 2001 at 09:49:49AM -0300, Orlando Rocha wrote:
> When I did (make mods) look at:
> $insmod vmadump.o
> vmadump.o: unresolved symbol k_write_u
> vmadump.o: unresolved symbol k_write
> vmadump.o: unresolved symbol k_read_all_u
> vmadump.o: unresolved symbol k_read_all
>                .....
> $insmod bproc_masq.o
> bproc_masq.o: unresolved symbol bproc_next_req
> bproc_masq.o: unresolved symbol bproc_next_req_wait
> bproc_masq.o: unresolved symbol bproc_put_back_req
>                 .....
> 
> $insmod bproc_ghost.o
> bproc_ghost.o: unresolved symbol k_close
> bproc_ghost.o: unresolved symbol bproc_send_req
> bproc_ghost.o: unresolved symbol k_listen
> 
> What could It be? How can I solve this problem?

don't 'insmod' them.  or insmod them in the right order.  "modprobe
bproc" should do the trick.  

where did you get bproc_ghost.o?  that's
no kernel module (at least not since october bproc ).  A 'modern'
bproc only needs ksycall, vmadump, and bproc kernel modules. 

like erik said, it sounds like you are running an *ancient* bproc.  do
upgrade and see if things make more sense. 

==rob

-- 
[ Rob Latham <rlatham@plogic.com>         Developer, Admin, Alchemist ]
[ Paralogic Inc. - www.plogic.com                                     ]
[                                                                     ]
[ EAE8 DE90 85BB 526F 3181                   1FCF 51C4 B6CB 08CC 0897 ]