From: "Alec Warner" <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Removal of net-misc/udhcp will break systems
Date: Fri, 26 Dec 2008 10:36:35 -0800 [thread overview]
Message-ID: <b41005390812261036o27cc73d7p48e489a3bd4a7d15@mail.gmail.com> (raw)
In-Reply-To: <giud38$4fq$1@ger.gmane.org>
On Wed, Dec 24, 2008 at 2:28 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> Not sure where to report this. net-misc/udhcp got masked recently with
> following notice:
>
> - net-misc/udhcp-0.9.9_pre20041216-r4 (masked by: package.mask)
> /usr/portage/profiles/package.mask:
> # Diego Pettenò <flameeyes@gentoo.org> (23 Dec 2008)
> # Mask these for removal, busybox provides those already, and are
> # unmaintained. As requested by solar.
>
> This should NOT happen until Bug 205286 is resolved. The current Busybox in
> portage cannot be used as a replacement for udhcp, and dhcpcd is not
> reliable for many routers (reports broken MAC address), leaving us with no
> DHCP client on Gentoo.
use the ISC client or pump?
-Alec
>
>
>
prev parent reply other threads:[~2008-12-26 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 22:28 [gentoo-dev] Removal of net-misc/udhcp will break systems Nikos Chantziaras
2008-12-26 18:36 ` Alec Warner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b41005390812261036o27cc73d7p48e489a3bd4a7d15@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox