I recognized the problem of the misbehaving kernel,
there seems to be another server within my domain which
answers my bootparams request's. It sends me my clients name
but no kernel. Is there a way of blocking it with the OpSys
or do I have to ask the admin of this server  to stop this
unwanted service?

More about HOWTO config a DISKLESS workstation:

My kernel reports
   'WARNING: boot program didn't supply boot device.
    Please update your boot program.'
 and I have to enter 'le0'.   How to avoid this?

Is there a optimal version af a diskless computer running X-windows
and having just 8MB of memory.


What services should the diskless do himself and which can be better 
done by the faster server (server: hp380 <-> client: hp360).
I do have 5 disk's and 3 hp's(apollo 400(43T)(is still running HP-UX B9.00), 
hp380, hp360) should the HD's be managed by one (maybe slow) 'just disk 
server' or should the fastest be used or is it better to have them 
distributed and composed together(to give somehow the users the 
impression of "ONE" system). Most of the work will probably be 'mailing 
and 'surfing'.

	Thanks Andreas

PS: I am open(and ready to look more inside) to offer information about this 
    configuration to the hp300 hardware FAQ if I can figure it out with 
    not too much work. There are also following HP-Manuals( HP 9000 
    Series 200/300) in the desk: peripheral installation guide, Sys admin 
    man (vol 1 & 2), Installation Reference, Using & Admin. NFS, Inst. & 
    Maint. NS-ARPA services.