This code includes the installation of Boch, linux0.11 kernel code to compile, simulate a floppy disk. Boch program is installed first, and then load the linux0.11 and floppy disks. Boch is a very good system debugging tool. Many people have awe of linux, but in looking at the source code with Boch.
Desinstalar udhcpc
Para desinstalar unicamente udhcpc en Debian 8 (Jessie) ejecutar los siguientes comandos:
Desinstalar udhcpc e los paquetes dependientes
Para desinstalar el paquete udhcpc y todos los paquetes dependientes que ya no sean necesarios en Debian Jessie.
Purga udhcpc
Usted también puede eliminar la información de configuración del udhcpc en Debian Jessie ejecutar lo siguiente comando:
Para eliminar la información de configuración del udhcpc y todos los paquetes dependientes en Debian Jessie ejecutar:
More information about apt-get remove
Advanced Package Tool, or APT, is a free software user interface that works with core libraries to handle the installation and removal of software on Debian, Ubuntu and other Linux distributions. APT simplifies the process of managing software on Unix-like computer systems by automating the retrieval, configuration and installation of software packages, either from precompiled files or by compiling source code.
apt-get is the command-line tool for handling packages, and may be considered the user's 'back-end' to other tools using the APT library.
apt-get remove is identical to install except that packages are removed instead of installed. Note that removing a package leaves its configuration files on the system. If a plus sign is appended to the package name (with no intervening space), the identified package will be installed instead of removed.
Vea también
curmudgeon wrote: | ||
It blew up /etc/resolv.conf (without backing it up, which is doubly annoying). The DNS servers that udhcpc picked up were horrible (minimum fifteen seconds to return anything), and on top of that, I run dnsmasq (which any decent dhcp client would have incorporated into a modified resolv.conf, but udhcpc didn't). |
curmudgeon ... none of which are directly related to the quote above. It 'blows up' resolv.conf because dhcp clients do this *unless* they are told not to request DNS (using the 'nodns' switch in dhcp_${IFACE}), the dns servers 'picked up' are provided by whatever is serving dhcp on the network, and if you want resolv.conf to be handled by multiple sources, or be static, then you need to figure out why udhcpc is started in the first place. As I said, the issue seems to be elsewhere as having a static address defined should be sufficent for the interface to be brought up, and no dhcp client should be called. So, something else is no doubt causing udhcpc to be started, what I can't tell, as there is too little information to go on.
curmudgeon wrote: |
Beyond that, there are security implications involved in running a dhcp client when one is not desired. |
There are security implication to any number of things, but it is by understanding the cause behind an event that allows for its mitigation. So, sure, we can state 'that shouldn't happen' but that is in the realm of the obvious, and provides no clue as to the why.
curmudgeon wrote: |
Since my question has not been answered yet, I will repeat it - how do I block udhcpc from ever running under any circumstances? |
As I stated above with a staticly defined address it shouldn't, so you need to look for the root cause and/or provide some clue as to why it might. Generally, to get your question answered its best to present the question in a way in which others can help, your 'question has not been answered yet' because, quite frankly, no one has any idea what might be at work here, all we have is two lines from your /etc/conf.d/net ... and lots of huffing and puffing.
best ... khay