[ENBD] diskless enbd-client/enbd on initrd

[Rudolph Bott]

Hey,

well i tracked down one of my mistakes: i tried several execl()'s with 
only one fork() (which is not the best thing to try). Now, after some 
modifications, everything gets executed properly, but the whole thing 
still fails:

--begin onsole output:

IP-Config: Complete:
       device=eth0, addr=172.16.20.3, mask=255.255.255.224, 
gw=255.255.255.255,
      host=nbdtest, domain=, nis-domain=(none),
      bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
RAMDISK: romfs filesystem found at block 0
RAMDISK: Loading 1944KiB [1 disk] into ram disk... done.
VFS: Mounted root (romfs filesystem) readonly.
Freeing unused kernel memory: 108k freed
enbd_root version 0.2
root: 172.16.20.1:1111
Loading enbd module...
ENBD #5427[0]: enbd_init Network Block Device originally by 
pavel at elf.mj.gts.cz
ENBD #5428[0]: enbd_init Network Block Device port to 2.0 by ptb at it.uc3m.es
ENBD #5430[0]: enbd_init Network Block Device move networking to user 
space by amarin at it.uc3m.es
ENBD #5432[0]: enbd_init Enhanced Network Block Device 2.4.30 $Date: 
2002/09/17 16:33:22 $ by ptb at it.uc3m.es
ENBD #5472[0]: enbd_init registered device at major 43
Starting enbd-client...
enbd-client   593: client says target 0 is 172.16.20.1:1111
enbd-client   593: # 853 cmdline: client specified no route nor number 
of channels! Try -n 2. Assuming 2.
enbd-client   593: client (-1) opened device /dev/nda
enbd-client   593: client (-1) opened NBD device /dev/nda (2b00)
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
enbd-client   593: client (-1) left kernel bdflush sync boundary at 
134988640%
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
warning: process `enbd-client' used the obsolete bdflush system call
Fix your initscripts?
enbd-client   593: client (-1) set kernel bdflush async boundary to 25% 
from 134971615%
enbd-client   593: client (-1) detaches from shell
nbd/pidfile   594: # 147 lockpidfile: returning err -30 for lock attempt
enbd-client   594: #4268 main: Warning - couldn't make a new pidfile 
/var/run/enbd-client-xenoo.pid!
enbd-client   594: client (-1) starts introduction sequence on 
172.16.20.1:1111
ENBD #2469[1]: do_enbd_request device not enabled.
EXT3-fs: unable to read superblock
mount: Invalid argument
pivot_root: Device or resource busy
Failed to start init :(
Kernel panic - not syncing: Attempted to kill init!

--end console output

Well, obviously it fails because of the ro-access to the ramdisk - is it 
possible to turn that into rw? Or do i have to alter the enbd-client's 
sourcecode to not create a pid-file (which isn't very useful in this 
case anyways).


-- 
Mit freundlichen Gruessen / with kind regards
  Rudolph Bott

-------------------------------------------------------------------
Megabit Informationstechnik GmbH  Karstr.25  41068 Moenchengladbach
Tel: 02161/308980   mailto:info at megabit.net       ftp://megabit.net
Fax: 02161/3089818  mailto:support at megabit.net   http://megabit.net
-------------------------------------------------------------------