Alessandro Barbieri , Your email system is severely misconfigured (Actually, I think that that's part of why you have problems with nfsroot, but see later). As I didn't want to waist those good 8 minutes I spent chewing up an answer to your email, I'm now sending it to debian-user. I've already tried sending it to: [EMAIL PROTECTED], and another root account, whose name escapes me. Both fails, and basically, your email headers don't give me any clues to who else I can send email to.
> Hi Mr Joost, > I am debian/linux newcomer, so be patient. > I chose debian because of the nfsroot package, which, I believe, is > something spectacular. Thanks! The main problem with my nfsroot package is I believe the description: although it sortof is true in principle to set it up really easily, it appears to be somewhat more difficult in practice. But I hope I can help you with it. > Due to my ignorance I couldn't succeded in making it work. Reading the rest of your email, it doesn't sound like ignorance, but something else probably failed. > Only one problem:every few mins(200sec I think) I see a message like this > logged by nrprobenet (I think): > > +++++++++++++++++++++++++++++++++++++++++++++++++++ > /var/run/bootpid.pid no such file or directory > +++++++++++++++++++++++++++++++++++++++++++++++++++ Don't worry about that. I should get rid of that message, but apparently bootpd does get restarted, as the client does get the correct clientip. > ++++++++++++++++++++++++++++++++++++ > invalid host ip#: qname=.. ....= ...= > ++++++++++++++++++++++++++++++++++++++ > or something similar.I'm very disappointed with approximation.Excuse me > please. Ah. So "mknfsroot clientname" does get run (that message is from mknfsroot, I just changed all error messages from mknfsroot to also include the name of the programme). I'd be interested in what that message really was (did it really say "ip#", or did it have a valid IP number there?), and what were the other strings? >From "mknfsroot", the lines that print the above error message: if test -z "$fqhostname" -o -z "$hostname" -o -z "$hostip"; then echo "mknfsroot: invalid host: $host, fqname=$fqhostname, name=$hostname, ip=$hostip" exit fi At least one of those strings was "" (empty), and this usualy points at a misconfigured dns server (or an unassigned IP number). I'm sure this is the source of your problem. Could you give me > Last question: > what do you think about a net boot with loadlin, as described in the > "kernel korner" of LJ issue38. That's something else I really should do some time. (but wait, not with loadlin, but with that netbios stuff, or what was it's name? Get the kernel over the network that's really cool). > Thanks in advance Mr Joost for any reply. It's OK to just call me "joost" (it's my first name). Thanks, -- joost witteveen, [EMAIL PROTECTED] #!/usr/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) #what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .