Hello all,
First of all, thank you for all the help so far. I'm glad that Matt's
suggestion worked.
Now, this is where I am: The thin client starts booting, it gets an IP
from the server, and starts showing what looks like a Linux boot up
process until it reaches the following error:
<quote>
nfs: server 192.168.0.1 not responding, timed out
nfs: server 192.168.0.1 not responding, timed out
mount: I/O error
short read: 0 < 28
Begin: Running /scripts/nfs-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
run-init: current directory on the same filesystem as the root: error 0
Kernel panic - not syncing: Attempted to kill init!
</quote>
Okay, the first two lines point to the NFS server. So I rebooted the
server (/etc/init.d/nfs-kernel-server restart) and rebooted the client,
but this didn't help.
I don't know a lot about kernel panics, except that they are very bad
:-( I also don't understand the issue with the "current directory" being
on the same file system as /. It *is* on the same file system (it's on
/opt/ltsp/i386 I think) and I understand that that's the way it's
supposed to be.
I take hope that at least the boot up process gets further along than
before. But I am still confused about these errors.
I'm hoping that someone might nudge me in the right direction here.
Cheers,
Daniel.
--
/\/`) Leave your mark at OpenOffice.org
/\/_/ http://oooauthors.org
/\/_/
\/_/ "The pedant keep things in order, the genius
/ rules the chaos" -- Sigrid Kronenberger
--
edubuntu-devel mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
