From mboxrd@z Thu Jan 1 00:00:00 1970 From: Detlev Zundel Date: Tue, 12 May 2009 10:48:28 +0200 Subject: [U-Boot] [PATCH 1/4] net: extend the netdev to have a common way to set the hw mac address In-Reply-To: <200905112036.18168.vapier@gentoo.org> (Mike Frysinger's message of "Mon, 11 May 2009 20:36:16 -0400") References: <1242023969-13542-1-git-send-email-plagnioj@jcrosoft.com> <200905111257.00648.vapier@gentoo.org> <20090512000446.GD18336@game.jcrosoft.org> <200905112036.18168.vapier@gentoo.org> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, >> > > how do set a mac for NFS Rootfs? >> > >> > use initramfs >> >> don't you think it's overkill to use a initramfs just for set a mac >> address?? > > no, i think it's perfectly reasonable. and considering you have no other > option here that'll get merged ... Can you please explain to me, why you think it to be reasonable to demand providing an initramfs in the order of 100s of k to set an attribute of a hardware device which has its own driver? Apart from being constantly repeated, I do not understand this reasoning at all. My (old-school) belief was that an operating system deals with abstracting the hardware thus userspace does not need to (nor should) know too many hw details. Knowing that there is not a clear distinction line, I still fail to see why a mac address of a network interface should be handled by userspace. Can someone enlighten me here? Thanks Detlev -- Ftpd never switches uid and euid, it uses setfsuid(2) instead. The main reason is that uid switching has been exploited in several breakins, but the sheer ugliness of uid switching counts too. -- pure-ftpd(8) -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de