Hi all,

        I'm working on setting up PCs with 1 server and about
10 diskless clients. I followed those HOWTOs and chose RARP
negotiation. At the RARP stage it's perfectly ok. However, it
becomes problematic around init: (I'm using Debian 2.1)

1)      /bin/login simply won't work; it just output
        invalid password for 'UNKNOWN' on 'tty0'
        regardless of what username and password I entered.
        Seems unable to read /etc/{passwd,shadow} at all. If I
        enterd shell directly the UID and GID is 0.

2)      nfs mount behaves strangely. Mounting of
        /tftpboot/<ip_addr> is perfectly ok, but it's not so when
        mounting everything else. It output
                "RPC: sendmsg returned error 101" and
                "portmap: server localhost not responding, timed out"

        but from the server log Isaw that the nfs mount was
        instantly successful. However everything was
        performed under command prompt. If I add mount
        commands under /etc/init.d/rcS (it's sysvinit), it
        PRETENDS to successfully mount everything
        while in fact it mounted NOTHING. 

3)      /etc/mtab can be absent or wrong.  Directories can
        be mounted twice or more, and some other entries
        (e.g. "/") can be missing. Probably it can be my
        fault ( I didn't remove it while shutdown system )...

In fact, my goal is to boot with rarp, and instantly go to xwin
(and open some gui app) without even giving login prompt
to users. But this becomes a disaster experience... does anybody
have related experience? Thansk a lot. If config is needed, I'll
post them here... Besides, if anybody knows any link to resource
talking about diskless clients under linux (there isn't much in
deja.com) or any general guideline OF SETTING UP INIT, please
tell me too......

Abel


Get your FREE Email at http://mailcity.lycos.com
Get your PERSONALIZED START PAGE at http://my.lycos.com
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to