[prev in list] [next in list] [prev in thread] [next in thread] 

List:       npaci-rocks-discussion
Subject:    Re: [Rocks-Discuss] network interface
From:       Philip Papadopoulos <philip.papadopoulos () gmail ! com>
Date:       2012-05-29 18:17:31
Message-ID: CACnkd5hzwq_6y9GhOWFRTUek7=+jmrdjPKrAaRCRfRTo2VmKaQ () mail ! gmail ! com
[Download RAW message or body]

Welcome to biosdev naming, courtesy of Dell! Really, this isn't a
Rocks specific thing. It's a "new and better" way to name Ethernet
devices.  Okay, there is significant debate on that topic in the
blog-o-sphere.

You cannot revert -after- installation, this is something that can
only be fixed at
install time (also not a Rocks specific problem, we're just trying to keep up).

To have eth<n> naming, you have to give biosdevname=0 as boot and install
argument.  That's not too hard. But, is there a problem with em0, em1, ...?
We could have made biosdevname=0 as the default, but chose not too.  There are
some advantages to biosdevnaming, and some obvious disadvantages.

-P


On Tue, May 29, 2012 at 10:43 AM, Marcelo Brandão
<brandao.marcelo@gmail.com> wrote:
> Hi guys
> We are installing version 6 on our new cluster previously running
> version 5.4.3.
> The anaconda installer recognise our network interface as em1 and em2
> instead eth0 and eth1, is this normal? Is there a way to revert this
> latter on a installed system?
> Cheers
>
> Marcelo
>
> --
> Marcelo Mendes Brandão
> Postdoc fellow
> Young Investigator on Bioinformatics
> Laboratório de Biologia Molecular de Plantas - ESALQ/USP
> Website: http://bioinfo.esalq.usp.br
> AtPIN: http://bioinfo.esalq.usp.br/atpin
> SKYPE: mmbrand
> Tel: (+55) 19 3429 4442
>



-- 
Philip Papadopoulos, PhD
University of California, San Diego
858-822-3628 (Ofc)
619-331-2990 (Fax)
[prev in list] [next in list] [prev in thread] [next in thread]