On Thursday 03 February 2005 16:39, SR wrote: > > Po uruchomieniu vmware-config.pl otrzymuje: >
[...] > Using standalone build system. > make: Entering directory `/tmp/vmware-config0/vmnet-only' > make: Leaving directory `/tmp/vmware-config0/vmnet-only' > The module loads perfectly in the running kernel. a u mnie to tak wygląda (kawałek moduł vmnet) : CC [M] /tmp/vmware-config22/vmnet-only/driver.o CC [M] /tmp/vmware-config22/vmnet-only/hub.o CC [M] /tmp/vmware-config22/vmnet-only/userif.o CC [M] /tmp/vmware-config22/vmnet-only/netif.o CC [M] /tmp/vmware-config22/vmnet-only/bridge.o CC [M] /tmp/vmware-config22/vmnet-only/procfs.o LD [M] /tmp/vmware-config22/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config22/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config22/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.5-7.111.30' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config22/vmnet-only' The module loads perfectly in the running kernel. Poza tym skrypt nie kończy tylko na budowie modułów, pyta jeszcze o ustawienia netu.
