I've been using Debian for a long time and netinstall has a its own place in my heart. But this is a bit of a cry because both the good and de bad must be told.
I started a new virtual server, just a little thing for a personal project, something that should be done in less than a single afternoon and tried the latest Debian 9 like "hey, the best distro, I don't have to deal with annoying packages ", this goes along with a rivalry to arch and manjaro .
but this is a cry and the subject gives you the hint.
I started configuring interfaces and I couldn't find ifconfig, my old reliable and well known ifconfig... gone .no program, no man no apropos-fu. So I read the patch notes and it's deprecated in favor of IP due to it's lack of support. No problem, I understand, I installed net-tools and kept using ifconfig and left learning IP for another day. (hooray Debian team for keeping a reliable system). But I start researching and I find that almost 95% of the manuals I've read in the later years in which ifconfig has been deprecated or going to be in a short time, still use ifconfig to set up networks. Furthermore Debian manuals for network configuring still use ifconfig. Damn you Debian managers, why don't you update your manuals before letting them rot in oldness. it's just the logical order, update first the manual (bonus points for starting by saying that ifconfig is old and unreliable) and then kicking it off the package list).
Wo, a big cry post. I don't want to be known as a crybaby so my part is going to be this: How do I have to do to update the manuals, both in English and Spanish (my mother language)??. Also whatever discussion grows from here is going to be welcome. Have you find out reading the patch notes?, or a story similar to mine? am I right, or just a cry nobody should care
Yours trully
#874512
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Cry: ifconfig vs IP
Re: Cry: ifconfig vs IP
I've never been in an organization with a documentation program that actually kept pace with reality. Documentation always takes a back seat. You are doing well, if that is your biggest complaint about Debian.
Nobody would ever ask questions If everyone possessed encyclopedic knowledge of the man pages.
Re: Cry: ifconfig vs IP
There were a poll a while ago on some website were people complained about the documentation and I personally think that's one of the major reason why people still think Linux is hard. Even with a black belt in Google-fu you might still end up with a tutorial for an older version and under the best of circumstances it just takes more time, under the worst you break or make your system vulnerable to something that hasn't been a problem for years. Always check and see if there's a date or a version number in a tutorial and if it's more than a couple of years old try to find something newer.
With that said, net-tools is one of the first packages I install on a fresh system
With that said, net-tools is one of the first packages I install on a fresh system
Bullseye amd64, AMD Ryzen 5 3600
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX
Buster amd64, Intel Xeon E3-1240 v3
Sid ppc, PowerPC 7447a
Sid ppc64, PowerPC 970FX
Re: Cry: ifconfig vs IP
If what you are setting is a WIFI you can also go low level and use iwconfig, ifconfig, dhclient and wpa_supplicant. In the case of a wired connection you can connect by first bringing a network interface up and then assign an IP using dhclient. That way I succeeded to eliminate the use ifupdown in my version of network manager.
P.S.
As far as I can remember, systemd also supports connecting to a network but personally I do not use systemd. So, be cautious about this advice.
P.S.
As far as I can remember, systemd also supports connecting to a network but personally I do not use systemd. So, be cautious about this advice.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
-
- Posts: 1394
- Joined: 2007-03-04 21:10
- Location: U.S.A. - WI.
Re: Cry: ifconfig vs IP
The "ip" command sucks donkey balls.
First off every command is longer than the corresponding ifconfig suite.
for exapmple:
VS.
to get the same stats.
There is probably some flag or another you can pass, maybe, to get all of the info at once like in ifconfig. Don't know, didn't bother to look into it very far since ifconfig works just fine. It can be pried from my cold dead hands.
First off every command is longer than the corresponding ifconfig suite.
for exapmple:
Code: Select all
root@debianvm:/home/mojo# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.75.130 netmask 255.255.255.0 broadcast 192.168.75.255
inet6 fe80::20c:29ff:fe08:cd57 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:08:cd:57 txqueuelen 1000 (Ethernet)
RX packets 1023007 bytes 460282713 (438.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 195943 bytes 45330696 (43.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 210 bytes 15818 (15.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 210 bytes 15818 (15.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Code: Select all
ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:08:cd:57 brd ff:ff:ff:ff:ff:ff
inet 192.168.75.130/24 brd 192.168.75.255 scope global dynamic eth0
valid_lft 1298sec preferred_lft 1298sec
inet6 fe80::20c:29ff:fe08:cd57/64 scope link
valid_lft forever preferred_lft forever
AND
ip -stats addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
15818 210 0 0 0 0
TX: bytes packets errors dropped carrier collsns
15818 210 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:08:cd:57 brd ff:ff:ff:ff:ff:ff
inet 192.168.75.130/24 brd 192.168.75.255 scope global dynamic eth0
valid_lft 1236sec preferred_lft 1236sec
inet6 fe80::20c:29ff:fe08:cd57/64 scope link
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
460324576 1023153 0 0 0 0
TX: bytes packets errors dropped carrier collsns
45336016 195958 0 0 0 0
to get the same stats.
There is probably some flag or another you can pass, maybe, to get all of the info at once like in ifconfig. Don't know, didn't bother to look into it very far since ifconfig works just fine. It can be pried from my cold dead hands.
fortune -o
Your love life will be... interesting.
How did it know?
The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches
Your love life will be... interesting.
How did it know?
The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches
Re: Cry: ifconfig vs IP
Code: Select all
ip -s link
Code: Select all
~$ ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
45840 583 0 0 0 0
TX: bytes packets errors dropped carrier collsns
45840 583 0 0 0 0
2: ens5f5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether bc:ae:c5:a0:62:b7 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
47248469 35928 0 5 0 796
TX: bytes packets errors dropped carrier collsns
1613440 20467 0 0 0 0
12: wls1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 10:6f:3f:4c:83:6d brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
3199917160 2392245 0 0 0 0
TX: bytes packets errors dropped carrier collsns
138934113 1283157 0 0 0 0
13: mon0: <BROADCAST,ALLMULTI,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/ieee802.11/radiotap 48:5d:60:9d:71:48 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
23232116396 46779290 0 46832353 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0