From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-dev-return-16172-arch-gentoo-dev=gentoo.org@lists.gentoo.org> Received: (qmail 32761 invoked from network); 29 Sep 2004 05:05:16 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 29 Sep 2004 05:05:16 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CCWeS-0007RK-B9 for arch-gentoo-dev@lists.gentoo.org; Wed, 29 Sep 2004 05:05:16 +0000 Received: (qmail 17808 invoked by uid 89); 29 Sep 2004 05:05:15 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: <mailto:gentoo-dev@gentoo.org> List-Help: <mailto:gentoo-dev-help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28578 invoked from network); 29 Sep 2004 05:05:15 +0000 X-cybertrench.com-virus-scan: clean Date: Wed, 29 Sep 2004 07:05:12 +0200 From: Corvus Corax <corvus-ml@cybertrench.com> To: gentoo-dev@lists.gentoo.org Message-Id: <20040929070512.5e6bf69e@VikingPC.home> In-Reply-To: <41586F16.5020409@gentoo.org> References: <41586F16.5020409@gentoo.org> X-Mailer: Sylpheed version 0.9.11claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: Re: [gentoo-dev] removing dhcpcd from system??? X-Archives-Salt: 50152010-ce7d-44d2-b062-fd0cb98dbeae X-Archives-Hash: 2ba3e77ce6a8cae4f4ecede50e919fce > wtf crack monkey ... hey guys, an oppinion from a gentoo user here: if you remove stuff like dhcpcd, do it right I agree that, while some ethernet networks NEED dhcp clients, as some gentoo users need pppd to get on the net, its an optional feature, we can live with that being emerged seperately if needed (as is pppd). However the current init scripts depend not only on a dhcp client, but on d= hcpcd hardcoded and they dont check for its presents, they just assume its there = like if it were ifconfig it not being there the ebuild would still somehow work and use the fallback static setting, if given, however this would get confusing to users (especi= ally if no static setting is set) thinking "i have set it to use dhcp ion /etc/conf.d/net like the install documentati= on says, and my dhcp server runs, but i cant get a lease, what the heck is wro= ng here ?!?" so either make /etc/init.d/net.ethx check for a dhcp client present before trying to use it and WARN the user if not (when you are on it, you could also add support to some other dhcp clients = and introduce VIRTUAL/dhcpc) or make dhcpcd an rdepent in the baselayout ebuild (it actually IS a runtime dependency right now the way those init scripts a= re written) while actually a bug in baselayout (and hopefully filed on bugzilla meanwhi= le after this discussion) I think the idea of silently removing dhcpcd from the profile, this way triggering that bug almost willingly was a bad practise not really crack monkey style, but not thought through either. my 2 =A2 Corvus -- gentoo-dev@gentoo.org mailing list