From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: confused by netbase/udev
Date: Tue, 9 Feb 2010 14:29:13 +0100 [thread overview]
Message-ID: <20100209132913.GC24852@ibawizard.net> (raw)
In-Reply-To: <4B716090.2090104@dresearch.de>
Steffen Sledz <sledz@dresearch.de> [2010-02-09 14:18:08]:
> # Wired or wireless interfaces
> auto eth0
> iface eth0 inet dhcp
> iface eth1 inet dhcp
>
> But i'm not sure what this part means (especially what means 'auto'
> here. Where can i found some documentation about the content of this
> config file. The busybox and ifup/ifdown manpages are not very helpful
> here. :(
man 5 interfaces?
Quote:
" lines beginning with the word "auto" are used to identify the physical
interfaces to be brought up when ifup is run with the -a option. (This
option is used by the system boot scripts.) Physical interface names
should follow the word "auto" on the same line. There can be multiple "auto"
stanzas. ifup brings the named interfaces up in the order listed. "
> And another problem is the mentioned naming. If every connected
> USB-NIC gets a new name i cannot refer to it in this config file.
You can get unique name/symlink using udev rule.
-- ynezz
next prev parent reply other threads:[~2010-02-09 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 11:23 confused by netbase/udev Steffen Sledz
2010-02-09 11:59 ` Paul Menzel
2010-02-09 13:18 ` Steffen Sledz
2010-02-09 13:29 ` Petr Štetiar [this message]
2010-02-09 13:38 ` Steffen Sledz
2010-02-09 13:47 ` Petr Štetiar
2010-02-09 15:38 ` Steffen Sledz
2010-02-09 22:58 ` Paul Menzel
2010-02-09 21:14 ` Cliff Brake
2010-02-10 7:43 ` Steffen Sledz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100209132913.GC24852@ibawizard.net \
--to=ynezz@true.cz \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.