🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: pl.comp.os.linux.sprzet
Article #74513

Re: udev, przewidywanie nazwy

#74513
From: ein
Date: Mon, 25 Nov 2013 23:31
129 lines
6745 bytes
Jan K wrote:
> Cześć,
>
> Zajrzyj tutaj jak są nadawane nazwy:
>
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>
> Co do twojego pliku reguł - składnia 70-persistent-net czy podobnych się
> trochę zmieniła, poniżej fragment z newsów gentoo ('eselect news' w
gentoo...
> nie wiem gdzie to się da dostać online)

Tak, gdyż pokazałem wycinek z leciwego systemu jakim jest slackware 13.37.

> =============== 2013-03-29-udev-upgrade ==========
> 3. Old interface naming rules:
>
> If the system still has old network interface renaming rules in
> /etc/udev/rules.d, like 70-persistent-net.rules, those will need
> to be either modified or removed.
>
> If you choose to modify them, you must use free namespace (like net*
> or internet*) instead of kernel namespace (like eth* or wlan*)
> because in-place renaming has been deprecated, see small
> documentation of it if you like[2].
>
> The file 70-persistent-net.rules, like the 70-persistent-cd.rules
> should be removed, so if you modify, rename the file also to something
> else like 70-my-network.rules to silence the deprecation warning coming
> from the end of the sys-fs/udev emerge.
>
> This is the old format with reserved namespace:
>
> SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="eth0"
> SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="eth1"
>
> This is the new format with free namespace:
>
> SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="net0"
> SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="net1"
> =============================================

Serdecznie dziękuję za zainteresowanie, ale widzę, że analiza tego
zajmie mi kilkadziesiąt razy więcej czasu niż podróż do klienta i
wykonanie tego z palca, albo ew. eksperymentalne sprawdzenie jak jajko
sobie to nazwie.


Przykładowo u mnie (Debian 7 stable) lspci -vvv wygląda tak:

02:00.0 *Ethernet* controller: Qualcomm Atheros Attansic L1 Gigabit
Ethernet (rev b0)
        Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fe7c0000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at fe7a0000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [58] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<4us, L1 unlimited
                        ExtTag- AttnBtn+ AttnInd+ PwrInd+ RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s,
Latency L0 unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt+
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr-
                AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+
ChkEn-
        Kernel driver in use: atl1




05:02.0 *Ethernet* controller: Intel Corporation 82541PI Gigabit
Ethernet Controller (rev 05)
        Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (63750ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at fe9e0000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at fe9c0000 (32-bit, non-prefetchable) [size=128K]
        Region 2: I/O ports at ec00 [size=64]
        [virtual] Expansion ROM at f0100000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [e4] PCI-X non-bridge device
                Command: DPERE- ERO+ RBC=512 OST=1
                Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple
DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
        Kernel driver in use: e1000
Technical Details
Message-ID: <l70mju$79j$2@node1.news.atman.pl>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mail
References: <l6sd0e$tv0$1@node2.news.atman.pl>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mail
From: ein <ein@no.spam>
Newsgroups: pl.comp.os.linux.sprzet
Subject: Re: udev, przewidywanie nazwy
Date: Tue, 26 Nov 2013 00:31:19 +0100
Organization: ATMAN - ATM S.A.
Lines: 129
Message-ID: <l70mju$79j$2@node1.news.atman.pl>
References: <l6sd0e$tv0$1@node2.news.atman.pl>
NNTP-Posting-Host: 89-65-113-147.dynamic.chello.pl
Mime-Version: 1.0
X-Trace: node1.news.atman.pl 1385422270 7475 89.65.113.147 (25 Nov 2013 23:31:10 GMT)
X-Complaints-To: usenet@atman.pl
NNTP-Posting-Date: Mon, 25 Nov 2013 23:31:10 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
In-Reply-To: <l6sd0e$tv0$1@node2.news.atman.pl>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit