Re: Debian replicator boot disk problem
- From: "Christian Maier" <tomtailor@xxxxxxxxxxx>
- Date: 31 Dec 2005 00:21:06 -0800
OK:
What I am doing. All steps described at
http://replicator.sourceforge.net/documentation/Replicator-UserGuide/node5.html
I can connect from an other client in the LAN 192.16.0.12 pretty good.
Premissions in exports ist 192.168.0.* (rw, no_root_squash), so is it
realy a serverside problem? Or is ist caus client cant detect his hd,
filesystem, controller, what so ever? It would be great if you could
say: yes 100% serverside. I don't want to compile kernels anymore (it's
always a problem with the size and the supported stuff)
The Clienet is about a 1,44MB Floppy with a realy small kernel on it
(ONLY supports ip autoconfig., DHCP, NFS, ext3 and ISA support).
Compiling your own kernel isn't basic stuff for me!
The Floppy boots and the mini kernel want to connect via NFS to my
model -> seems the request is recognised and logged at serverside. And
then the client crashes with kernel panic. Don't know why. Sais
connection refused from Server but I can mount with mount -t nfs ....
fromanother linux in the LAN fine.
THX!
Christian
.
- Follow-Ups:
- Re: Debian replicator boot disk problem
- From: Enrique Perez-Terron
- Re: Debian replicator boot disk problem
- From: Michael Heiming
- Re: Debian replicator boot disk problem
- References:
- Debian replicator boot disk problem
- From: Christian Maier
- Re: Debian replicator boot disk problem
- From: Christian Maier
- Re: Debian replicator boot disk problem
- From: Peter T. Breuer
- Debian replicator boot disk problem
- Prev by Date: MENCODER: segfaults caused by v scale ???
- Next by Date: Re: Debian replicator boot disk problem
- Previous by thread: Re: Debian replicator boot disk problem
- Next by thread: Re: Debian replicator boot disk problem
- Index(es):
Relevant Pages
|