From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A764413873B for ; Mon, 3 Mar 2014 18:36:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8BF7CE0ABD; Mon, 3 Mar 2014 18:36:26 +0000 (UTC) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by pigeon.gentoo.org (Postfix) with ESMTP id AFDF3E0ABB for ; Mon, 3 Mar 2014 18:36:25 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta10.emeryville.ca.mail.comcast.net with comcast id Z2ms1n0051HpZEsAA6cRGy; Mon, 03 Mar 2014 18:36:25 +0000 Received: from crud.chemoelectric.org ([66.41.30.59]) by omta14.emeryville.ca.mail.comcast.net with comcast id Z6cP1n00c1GXozm8a6cQKq; Mon, 03 Mar 2014 18:36:24 +0000 Received: by crud.chemoelectric.org (Postfix, from userid 1501) id 9E9D72009B0C7; Mon, 3 Mar 2014 12:36:23 -0600 (CST) Date: Mon, 3 Mar 2014 12:36:23 -0600 From: Barry Schwartz To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Please get me straight about sysvinit vs. systemd, udev vs eudev vs mdev, virtuals and other things... Message-ID: <20140303183623.GB10870@crud> References: <5314B8C6.3040803@libertytrek.org> <20140303131242.5cb4eb9a6e0128e678d12a92@comcast.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393871785; bh=IE8Zl3AK285h1eZPItf2UgK5vh5CqByQEk4uc+k22TM=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=PCZT9hnSNFP8c315P4DQJo2hMuAyc6AlhGcoau3gGmS1HrVQ1S3EhH1r6PWw3ytvK /K7OtGogv14vDUk2srGKxLpdTvmJRkM+0y8VsGDj9OLOIIygp51sOMa+nwu75Xh2Ha l0Obsb6sY/IYaempdFPFvB6cmlWtedm2/aNUlOaF5MeLFjpea0JL6Di2QEt10aoM2g 3/2EWBrXQK1e8+XuEBBLbOae3PcqBiWkHsLhOSVqJKs/qm52S1WYZNA4lhCYkzjTay ujEq1M5clw+nEGq8IMX1RMVQ5GZFkoOZp+xqYf11fI3HFaXWa0bfjge7i4KMdqeErD T0MAd2SVyOMiw== X-Archives-Salt: ce9ce139-9ac1-4857-8fae-02ea88c5c559 X-Archives-Hash: deb536499a46cfbe6db4284b040a927a Canek Peláez Valdés skribis: > On Mon, Mar 3, 2014 at 12:12 PM, Frank Peters wrote: > > Manually creating a /dev tree that perfectly reflects ones own system > > is rather trivial. That's how Linux used to be and that's how Linux, > > for the most part, still is. There is, or at least should be, no need > > for udev or any substitute for udev. > > If you want to create a /dev tree for a computer that never gets new > hardware connected via USB, bluetooth, or another bus, yeah, it's > pretty trivial. What’s hard? You create nodes for those devices. If you have a lot of devices, you create more nodes. With a script, you can create enough nodes to wrap the earth a few times over. All udev does is create and destroy nodes according to an unfathomable set of rules that changes all the time.