Re: [suse-sparc] DHCP setup problems with SuSE 7.0 on Sun Ultra/10

From: Bob Allen (ALLEN@uvvm.UVic.CA)
Date: Mon Feb 05 2001 - 21:48:19 PST

  • Next message: Thorsten Kukuk: "Re: [suse-sparc] DHCP setup problems with SuSE 7.0 on Sun Ultra/10"

    Date:         Mon, 05 Feb 2001 21:48:19 PST
    From: Bob Allen <ALLEN@uvvm.UVic.CA>
    Message-Id: <010205.220124.PST.ALLEN@uvvm.UVic.CA>
    Subject:      Re: [suse-sparc]      DHCP setup problems with SuSE 7.0 on Sun Ultra/10
    

    On Mon, 5 Feb 2001 07:12:31 +0100 you said:
    >>
    >> I am trying to get DHCP running with SuSE 7.0 on a Sun Ultra/10. The
    >> ethernet card is connected to a DSL modem. After the basic installation
    >> completes, I use YaST to integrate the ethernet card into the system
    >> and to specify DHCP for the network configuration. When I restart the
    >> system, I get the following messages:
    >>
    >> Starting service dhcp client on eth0dhcpcd[133]: broadcasting DHCP_DISCOVER
    >>
    >> dhcpcd[133]: terminating on signal 10
    >>
    >> startproc: exit status of /sbin/dhcpcd: 10
    >
    >dhcpcd is broken, please use the dhclient package instead.
    >

    I got a copy of "dhcp-2.0pl5.tar.gz" and did the make install. It was
    necessary to rename /sbin/dhclient to /sbin/dhcpcd before things worked
    properly. Is the name dhcpcd predefined somewhere? Is the package
    I used the one you meant?

    >>
    >> Is there a problem with dhcpclient with SuSE 7.0? Is there something
    >> I have overlooked? (RedHat 6.2 installs like a dream and configures
    >> DHCP with no problems at all!)
    >
    >The dhcpcd program on RedHat 6.2 has the same bug. They use the same
    >sources. But I think you are using RedHats pump program.
    >

    Not sure what you mean by the pump program but I guess I can figure
    that out with a little digging (a lot of this is very new territory
    for me).

    >>
    >>
    >> Another problem(?) is with the install. Part way through, after
    >> processing the second CD, I get the following message:
    >>
    >> /usr/lib/YaST2/bin/YaST2: line 203: 1326 Aborted ...
    >> y2bignfat "$modulename" $moduleargs ncurses -T
    >>
    >> Is the above message something I should worry about?
    >
    >When did you get it ? Does YaST2 aborts here ? Or is this line
    >after YaST2 finished and is killed (in the last case it is ok,
    >and I think that is what you are seeing).
    >

    The message appears immediately before the messages:

    INIT: Entering runlevel: 3
    Master Resource Control: previous runlevel: N, switching to runlevel: 3
    Re-Starting RPC portmap daemon
    Re-Starting syslog services

    ------
    Bob Allen
    University of Victoria
    Victoria, British COlumbia
    Canada



    This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:38 PDT