Hi,
Samuel Thibault wrote:
> Holger Wansing, le mer. 14 août 2019 22:33:11 +0200, a ecrit:
> > And the debian/control file does not list any dhcp client package
> > other than
> > isc-dhcp-client-udeb [kfreebsd-any hurd-any]
>
> ?
> wide-dhcpv6-client-udeb [linux-any]
Ah, ok. I over
Holger Wansing, le mer. 14 août 2019 22:33:11 +0200, a ecrit:
> I wonder what dhcp-client(s) is/are used in d-i.
>
> I stumbled over this message in netcfg:
> msgid "No DHCP client was found. This package requires pump or dhcp-client."
D'oh :)
> And the debian/control file does not list any dhcp
Hi,
I wonder what dhcp-client(s) is/are used in d-i.
I stumbled over this message in netcfg:
snip==
#. Type: error
#. Description
#. :sl2:
#: ../netcfg-dhcp.templates:5001
msgid "No DHCP client was found. This package requires pump or dhcp-client."
msgstr ""
snap
Hi Andrew,
On Thu, Jan 27, 2011 at 04:47:09PM +1000, Andrew Pollock wrote:
> On Sun, Jan 23, 2011 at 08:15:43AM +0100, Christian PERRIER wrote:
> > Quoting Matthew Palmer (mpal...@debian.org):
> > > Does any architecture use a DHCP client other than udhcpc? netcfg has
> > > support for running dh
Quoting Andrew Pollock (apoll...@debian.org):
> If I can stop making a udeb, please let me know, I'd love for isc-dhcp not
> to get stuck in unstable to testing transitions because it happens to make a
> udeb that isn't needed any more.
From what I see now, it looks like you can disable the build
On Sun, Jan 23, 2011 at 08:15:43AM +0100, Christian PERRIER wrote:
> Quoting Matthew Palmer (mpal...@debian.org):
> > Does any architecture use a DHCP client other than udhcpc? netcfg has
> > support for running dhclient and pump, but so far as I can tell (from some
> > grepping around in installe
Quoting Matthew Palmer (mpal...@debian.org):
> Does any architecture use a DHCP client other than udhcpc? netcfg has
> support for running dhclient and pump, but so far as I can tell (from some
> grepping around in installer/build/pkg-lists) nobody uses that code. I'm on
The code is probably lyi
Does any architecture use a DHCP client other than udhcpc? netcfg has
support for running dhclient and pump, but so far as I can tell (from some
grepping around in installer/build/pkg-lists) nobody uses that code. I'm on
a mission to gut unnecessary code, and this is first on my list, as DHCP
cli
On Fri, Nov 14, 2003 at 11:42:14AM -0500, Joey Hess wrote:
> I don't care which dhcp client we use, as long as it is *1* per
> architecture and not 3. At least we're using the same dhcp client on
> i386 and powerpc now, which will make switching to any other one a bit
> easier.
the plan was to dro
Bastian Blank wrote:
> On Wed, Nov 12, 2003 at 11:39:02PM -0500, Joey Hess wrote:
> > This does not seem like a good idea, it puts us in the position of
> > supporting more than one dhcp client. I have plenty of space on the
> > floppy for dhcp-client-udeb, and this would also let udhcp be turned o
On Wed, Nov 12, 2003 at 11:39:02PM -0500, Joey Hess wrote:
> This does not seem like a good idea, it puts us in the position of
> supporting more than one dhcp client. I have plenty of space on the
> floppy for dhcp-client-udeb, and this would also let udhcp be turned off
> in busybox-cvs-udeb, pos
On Thu, Nov 13, 2003 at 09:40:50PM +0100, Gaudenz Steinlin wrote:
> Am Don, den 13.11.2003 schrieb Joey Hess um 20:48:
> > I will at least switch all i386 images that need a dhcp client over to
> > dhcp-client-udeb. If someone can tell me what is the right dhcp client
> > for powerpc, it is still u
uation is even more confused for the netboot image, which uses:
> - dhcp-client-udeb (hppa, ia64, mipsel)
> - pump (all other arches)
>
> So we're suppporting *3* dhcp clients on i386 alone!
I think in the long term udhcpc is the best for our purposes and we
should be moving away
Am Don, den 13.11.2003 schrieb Joey Hess um 20:48:
> I will at least switch all i386 images that need a dhcp client over to
> dhcp-client-udeb. If someone can tell me what is the right dhcp client
> for powerpc, it is still using both udhcp and pump right now and I'd
> like to fix that.
I think we
Gaudenz Steinlin wrote:
> I suggest to only use dhcp-client-udeb if it's available on all arches.
> At least we should standardize on one dhcp client if there is no good
> reason for keeping different clients for different arches.
dhcp-client is available on all architectures. I do not know if it
d for the netboot image, which uses:
> - dhcp-client-udeb (hppa, ia64, mipsel)
> - pump (all other arches)
>
> So we're suppporting *3* dhcp clients on i386 alone!
I suggest to only use dhcp-client-udeb if it's available on all arches.
At least we should standardize on on
)
So we're suppporting *3* dhcp clients on i386 alone!
--
see shy jo
signature.asc
Description: Digital signature
17 matches
Mail list logo
