Re: dnf install stuck

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 16 Aug 2023 13:04:07 +0930 Tim via users wrote:

> On Tue, 2023-08-15 at 22:02 +0100, Barry wrote:
>> Better these days to replace ifconfig with:

>>      ip addr

> I'm not so sure I agree with that, there's some useful info provided by
> ifconf that ip addr doesn't supply.  For example:

>         RX packets 24927062  bytes 16569920396 (15.4 GiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 8396381  bytes 1513217283 (1.4 GiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Add the -s (-stats) option to the ip command.

Example: a can be used as a shortcut of addr show.

ip -s a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
<snip>

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f8:b1:56:cd:32:b6 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet <snip>
    RX:  bytes packets errors dropped  missed   mcast           
      10695641   36120      0       3       0     175 
    TX:  bytes packets errors dropped carrier collsns           
       2616615   14078      0       0       0       0 

One can really forget ifconfig. For example, ifconfig do not output the
permanent mac addresses of the wifi interfaces.

Example: see the permaddr below:

ifconfig -a
<snip>
wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e2:71:46:a6:ee:81  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip a
<snip>
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether e2:71:46:a6:ee:81 brd ff:ff:ff:ff:ff:ff permaddr 00:24:d7:0f:d4:2c
    altname wlp3s0


-- 
francis
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux