From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Rizjp-00021w-Ab for garchives@archives.gentoo.org; Fri, 06 Jan 2012 02:41:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B0CA21C18C; Fri, 6 Jan 2012 02:40:52 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 463DD21C020 for ; Fri, 6 Jan 2012 02:39:56 +0000 (UTC) Received: by ghrr19 with SMTP id r19so593987ghr.40 for ; Thu, 05 Jan 2012 18:39:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=ytPgdTMErUUJc3212Lvkp7UhJZJIWIJsBOaCsy5/87k=; b=jiTPrvhaXvGESOoQmsA03sIBU1Npc2BK8lpDpeyiqD01QUyYAVZQDu/nXl0AZ5S73B hpcrql2f2ZGgQTFfVIi+X5VLJqqON/Cbk2U2MwyiWJalwIeHFj71cVh0GXBmeKIkGjTD DQMjvl6qOasMvLXU3XubzjJCNDsxNUByqZyNo= Received: by 10.236.9.106 with SMTP id 70mr4913361yhs.118.1325817595818; Thu, 05 Jan 2012 18:39:55 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-65-42.jan.bellsouth.net. [65.0.65.42]) by mx.google.com with ESMTPS id j25sm85227531yhm.12.2012.01.05.18.39.53 (version=SSLv3 cipher=OTHER); Thu, 05 Jan 2012 18:39:55 -0800 (PST) Message-ID: <4F065EF8.9000503@gmail.com> Date: Thu, 05 Jan 2012 20:39:52 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20120104 Firefox/7.0.1 SeaMonkey/2.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Beta test Gentoo with mdev instead of udev; version 3 References: <20120103131346.GC2410@nicolas-desktop> <20120103143120.GF2410@nicolas-desktop> <20120103221555.22c778a3@digimed.co.uk> <4F038C23.5030708@gmail.com> <20120105100149.GA2443@nicolas-desktop> <20120105220807.GC1263@vidovic> <20120106001036.5974967a@rohan.example.com> <4F065220.30004@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------010006040407090509010308" X-Archives-Salt: db63faab-a8b5-43bf-94a2-5db3c289e08c X-Archives-Hash: b4703c0af2a8dc640e266c6b8491bfbf This is a multi-part message in MIME format. --------------010006040407090509010308 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Pandu Poluan wrote: > > > On Jan 6, 2012 8:50 AM, "Dale" > wrote: > > > > Alan McKinnon wrote: > >> > >> I see that as a liability not a feature. Our routers have very > clear naming conventions for interfaces and they are exactly how Cisco > enumerates them and no other way. It's a firing offense to dick with > them and dream up useless "descriptive names". Mind you, these for the > most part are big iron with several 1000 interfaces each and 100+ > support personnel working on them. But even the on-site routers and > firewalls at customer premises have the same rule. I assume we are > talking about kit that routes properly (whether a Unix or something > else is not relevant) and not some joke system. As for NICs that do > not come up at boot time in a consistent order, if any piece of > hardware in our DC did that it would be sent right back to the vendor > labeled as a piece of shit with a demand for a refund. FFS, if my boss > shells out 3 months wages for some iron and it can't even get > something that basic correct, I start to wonder what else might be > dodgy. There is ZERO excuse for a system that cannot deterministically > enumerate it's fixed devices at boot time. > > > > > > I have a couple desktop rigs. I had a card that would sometimes not > do right and change the order of my cards numbering. Since it was > earlier than the card that hooked to my modem, it would mess up my > connection to the internet. The card was eth0 and I had internet > coming through on eth2. That rig now has two nics. The defective nic > was removed. It has a new address called /dev/dump. > > > > It may be a desktop rig but I like them being recognized the same > each time I reboot. Although, I forgot about being able to give them > names. < scratches chin > Nah, I'll leave well enough alone. It's > working and we don't mess with what is working, except for Fedora > devs. lol > > > > mdev is capable of renaming devices, you know ;-) > > https://svn.mcs.anl.gov/repos/ZeptoOS/trunk/BGP/packages/busybox/src/docs/mdev.txt > > Rgds, > udev does too. I'm just used to et0, eth1 etc. If I renamed them, I'd forget the names anyway. Then I would have to /etc/init.d/ then slap forehead. lol Right now, I only use one nic on each rig. I got a Linksys router now. I used to use my main rig as a router so it had three nics not counting the built in which I didn't use and was disabled in the BIOS. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n" --------------010006040407090509010308 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Pandu Poluan wrote:


On Jan 6, 2012 8:50 AM, "Dale" <rdalek1967@gmail.com&g= t; wrote:
>
> Alan McKinnon wrote:
>>
>> I see that as a liability not a feature. Our routers have very clear naming conventions for interfaces and they are exactly how Cisco enumerates them and no other way. It's a firing offense to dick with them and dream up useless "descriptive names". Mind you, these for the most part are big iron with several 1000 interfaces each and 100+ support personnel working on them. But even the on-site routers and firewalls at customer premises have the same rule. I assume we are talking about kit that routes properly (whether a Unix or something else is not relevant) and not some joke system. As for NICs that do not come up at boot time in a consistent order, if any piece of hardware in our DC did that it would be sent right back to the vendor labeled as a piece of shit with a demand for a refund. FFS, if my boss shells out 3 months wages for some iron and it can't even get something that basic correct, I start to wonder what else might be dodgy. There is ZERO excuse for a system that cannot deterministically enumerate it's fixed devices at boot time.
>
>
> I have a couple desktop rigs. =C2=A0I had a card that would sometimes not do right and change the order of my cards numbering. =C2=A0Since it was earlier than the card that hooked t= o my modem, it would mess up my connection to the internet. =C2=A0The = card was eth0 and I had internet coming through on eth2. =C2=A0That ri= g now has two nics. =C2=A0The defective nic was removed. =C2=A0It h= as a new address called /dev/dump.
>
> It may be a desktop rig but I like them being recognized the same each time I reboot. =C2=A0Although, I forgot about being able to give them names. < scratches chin > =C2=A0Nah, I'll leave well enough alone. =C2=A0It's working and we don't mess wit= h what is working, except for Fedora devs. =C2=A0lol
>

mdev is capable of renaming devices, you know ;-)

https://svn.mcs.anl.gov/repos/ZeptoOS/trunk/BGP/packag= es/busybox/src/docs/mdev.txt

Rgds,


udev does too.=C2=A0 I'm just used to et0, eth1 etc.=C2=A0 If I renam= ed them, I'd forget the names anyway.=C2=A0 Then I would have to /etc/init.d/<tab tab> then slap forehead.=C2=A0 lol=C2=A0

Right now, I only use one nic on each rig.=C2=A0 I got a Linksys rout= er now.=C2=A0 I used to use my main rig as a router so it had three nics= not counting the built in which I didn't use and was disabled in the BIOS.=C2=A0

Dale

:-)=C2=A0 :-)=C2=A0 

--=20
I am only responsible for what I said ... Not for what you understood or =
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS=3D"--quiet-build=3Dn"
--------------010006040407090509010308--