You could always test that you can assign an IP with
ifconfig eth0 192.168.0.199
or one that you know is spare, and see if that works in the meantime
while you debug the dhcpcd problem.
perke wrote:
> you're right, sorry... i was doing something on debian :)) and had to do
> it as root
>
> not sure what could cause this, i remember once i had same issues on
> debian....deleted interfaces in /etc/network then touch eth0
> and then dhclient eth0 did the job....sure it could be done through GUI.
> have you checked cables or some other distro just to make sure
> connection is OK?
>
> On 7/11/06, * Kristofer Dale* <barefoot@???
> <mailto:barefoot@nmia.com>> wrote:
>
> On Mon, 10 Jul 2006, perke wrote:
>
> :i guess you need to do this as root
>
> Lumumba defaults to a root login, doesn't Dhoruba? I tried several
> variations with your suggestion, still getting "command not found"...
>
> _______________________________________________
> dynebolic mailing list
> dynebolic@??? <mailto:dynebolic@lists.dyne.org>
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
::
Re: [dyne:bolic] net configuration …
