Re: Debian replicator boot disk problem

In comp.os.linux.misc Christian Maier <tomtailor@xxxxxxxxxxx>:
> 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,
[..]

> 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.

So the client boot image doesn't work probably on your hardware,
you can now open up a bug report to the maintainer of replicator.
Create an updated working version of it and send in patches or
use something else/your own image.

Personally found pushing an compressed dd image through ssh
working nicely. To reinstall a system you just can't walk up to
or/and that can't be patched into some kind of install LAN. For
convenience the system should have a complete remote BIOS
redirection. Though (with luck) it can be done without, you have
the possibility to fix things with it.

Good luck

BTW
Please read this before posting anything else:

http://cfaj.freeshell.org/google

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 34: (l)user error
.

Relevant Pages

  • Re: Debian replicator boot disk problem
    ... I can connect from an other client in the LAN 192.16.0.12 pretty good. ... say: yes 100% serverside. ... The Clienet is about a 1,44MB Floppy with a realy small kernel on it ...
    (comp.os.linux.misc)
  • Re: NAT-T and L2TP
    ... L2TP on our LAN but they fail from the internet. ... the second one from a client having a public IP address. ... IKE security association negotiation failed. ... Destination Port 0 ...
    (microsoft.public.win2000.ras_routing)
  • L2TP + NAT-T
    ... connect L2TP on our LAN, but they fail from the internet. ... from a NATted client, the second one from a client having ... IKE security association negotiation failed. ... Destination Port 0 ...
    (microsoft.public.win2000.ras_routing)
  • Re: opensuse on laptop
    ... Unfortunately I have a web development business which undertakes to update client websites within 4 hours of receipt of the material 24/7. ... Means I need a good desktop, bitmap graphics, vector graphics, good FTP client to access a series of client sites, web development tools, T-Mobile G3 Modem, WiFi, Bluetooth phone modem, land-line modem and wired network. ... I find XFCE's Thunar file manager with its lack of built in LAN viewing of shared computers / files not to my taste - never had this trouble with SUSE - or even Ubuntu with Gnome or KDE. ...
    (alt.os.linux.suse)
  • Problem related with Subnetting
    ... So at the server side if we see that for both client the host IP ... It may have a single big LAN, if those 2 host exist in that same ... 20.0.0.X, by using a another router, which will have its WAN address ...
    (comp.os.linux.networking)