Saludos
Disculpa... No es Sid -> Sidux. Sid es un sobrenombre que se le da a la version "inestable" de Debian... Son cosas distintas.
Sobre el tema del dhclient... ¿Lo estas haciendo en tu casa o en el conservatorio? Es posible que las configuraciones varien de un lugar a otro..
Salud y Suerte!!!!
Perdon Estoy bastante perdido
Tengo que actualizar mi sistema a Sid , Sidux.
Hay explicaciones en google, no se cual de todas es la conveniente.There is already a pid file /var/run/dhclient.pid with pid 6623
está diciendo que el comando dhcp no existe
es que el comando que estás tratando de ejecutar se llama:
dhclient
no dhcp client.
y si, va con sudo, o como root
sudo su
dhclient
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:22:5f:13:6b:17
Sending on LPF/wlan0/00:22:5f:13:6b:17
Listening on LPF/eth0/
Sending on LPF/eth0/
Listening on LPF/eth1/00:21:70:7f:a7:0b
Sending on LPF/eth1/00:21:70:7f:a7:0b
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@chivilnote:/home/Pablo#
root@chivilnote:/home/Pablo# knetworkmanager
si se te complica usá knetworkmanager
Link points to "/tmp/ksocket-root"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Link points to "/tmp/kde-root"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-7017' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
knetworkmanager: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-7007' to 'knetworkmanager'
ERROR: Communication problem with knetworkmanager, it probably crashed.
root@chivilnote:/home/Pablo# knetworkmanager
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-7103' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
knetworkmanager: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-7094' to 'knetworkmanager'
ERROR: Communication problem with knetworkmanager, it probably crashed.
root@chivilnote:/home/Pablo#En el archivo sources.list escribo? Disculpen hasta ahora entre a ese archivo y pegue direcciones con descomentar o comentar.
ese es el mejor programa para conectarse por red... el resto de lo que dice
debajo tal como PL dice, quizá deberías actualizar algunos paquetes a SID
(debian unstable) o lenny (testing)
eso se puede hacer así:
habilitás un repositorio unstable o testing en el sources.list
luego al instalar un paquete le das además del nombre del mismo, la rama de
debian que querés usar, ejemplo
apt-get install paquete/rama
o sea
apt-get install paquete/testing
apt-get install paquete/unstablese entiende? No, esta explicacion es para actualizar a sidux?
en cualquier caso, podés volver a versiones anteriores con cosas como
apt-get install paquete/stable
_______________________________________________
Musix GNU+Linux - www.musix.org.ar
Musix-usuarios mailing list
Musix-usuarios@lists.ourproject.org
https://lists.ourproject.org/cgi-bin/mailman/listinfo/musix-usuarios