Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752568Ab0KYWSn (ORCPT ); Thu, 25 Nov 2010 17:18:43 -0500 Received: from mail-wy0-f174.google.com ([74.125.82.174]:46524 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752387Ab0KYWSl (ORCPT ); Thu, 25 Nov 2010 17:18:41 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=G1GNjrpUjI3ertoH/SO9YMAfSBylAer+2vr5aK0zlYbiHt+ehEOfLp91CvrcG38alQ TGwIS4JGAmlst225J7yzMtkQMb0lMDSeqzfRCuQSTVKtU26p+PTLv5UhvvZTDCfuXj6b oYsJgZrnAS4v1K1p7mSjH2vbiA8k8rMWY4k1Q= Message-ID: <4CEEE0BB.6020509@gmail.com> Date: Thu, 25 Nov 2010 23:18:35 +0100 From: Jarek Poplawski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.13) Gecko/20100916 SeaMonkey/2.0.8 MIME-Version: 1.0 To: Ben Gamari CC: Mike Caoco , Stephen Hemminger , Netdev , LKML Subject: Re: Unplug ethernet cable, the route persists. Why? References: <144174.46619.qm@web63401.mail.re1.yahoo.com> <87bp5df9j9.fsf@gmail.com> In-Reply-To: <87bp5df9j9.fsf@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1346 Lines: 27 Ben Gamari wrote: > On Wed, 24 Nov 2010 12:29:43 -0800 (PST), Mike Caoco wrote: >> So if you rely on NetworkManager or Connman or Quagga to remove the >> route, the routing daemons will recompute the route table anyway. So >> why cannot this be done in the kernel? > > This is policy. In the Linux world we generally strive to separate > policy from mechanism, leaving the former to userspace. This allows > (potentially complex) policy decisions to be made in user-space. The > reason for this is two-fold: First, every line of kernel code introduces > the potentially for a bug and error handling in the kernel is generally > more complex than it is in user-space. Secondly, allowing user-space to > handle policy allows users to do things with the kernel that kernel > developers did not envision. This flexibility is one reason why the > kernel is so suited for running on anything from your cell-phone to 4000 > processor big iron. Secondly and a half, if you add a specific route you may really mean it, and prefer not to send at all than use default. Cheers, Jarek P. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/