#ifconfig — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ifconfig, aggregated by home.social.
-
Why I love freeBSD
Additional data
I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.
I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times
- using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
- these tools were depreciated due to many issues with them, decades later (IIRC)
- no linux distro ever told me as a user that I needed to use replacements like
ip - I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
- names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
- WTF?!?
In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stabilityMind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds
TLDR;
- choose BSD for your servers if you need consistent OS behaviour for decades
- choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
- choose win64 for love of being tortured
- choose mac to give away your aurum to the mac overlords
- choose the abacus for absolute stability
#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis
-
Why I love freeBSD
Additional data
I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.
I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times
- using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
- these tools were depreciated due to many issues with them, decades later (IIRC)
- no linux distro ever told me as a user that I needed to use replacements like
ip - I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
- names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
- WTF?!?
In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stabilityMind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds
TLDR;
- choose BSD for your servers if you need consistent OS behaviour for decades
- choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
- choose win64 for love of being tortured
- choose mac to give away your aurum to the mac overlords
- choose the abacus for absolute stability
#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis
-
Why I love freeBSD
Additional data
I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.
I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times
- using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
- these tools were depreciated due to many issues with them, decades later (IIRC)
- no linux distro ever told me as a user that I needed to use replacements like
ip - I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
- names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
- WTF?!?
In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stabilityMind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds
TLDR;
- choose BSD for your servers if you need consistent OS behaviour for decades
- choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
- choose win64 for love of being tortured
- choose mac to give away your aurum to the mac overlords
- choose the abacus for absolute stability
#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis
-
Why I love freeBSD
Additional data
I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.
I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times
- using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
- these tools were depreciated due to many issues with them, decades later (IIRC)
- no linux distro ever told me as a user that I needed to use replacements like
ip - I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
- names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
- WTF?!?
In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stabilityMind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds
TLDR;
- choose BSD for your servers if you need consistent OS behaviour for decades
- choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
- choose win64 for love of being tortured
- choose mac to give away your aurum to the mac overlords
- choose the abacus for absolute stability
#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis
-
Why I love freeBSD
Additional data
I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.
I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times
- using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
- these tools were depreciated due to many issues with them, decades later (IIRC)
- no linux distro ever told me as a user that I needed to use replacements like
ip - I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
- names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
- WTF?!?
In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stabilityMind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds
TLDR;
- choose BSD for your servers if you need consistent OS behaviour for decades
- choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
- choose win64 for love of being tortured
- choose mac to give away your aurum to the mac overlords
- choose the abacus for absolute stability
#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis
-
@vermaden @omar
I always use alsamixer -c0 up to cxx from the OSS ALSA period since it's ncurses based & faster than GUI programs.Many things in Linux were changed for good reason, but some are questionable. I don't use systemD init is easier to maintain. It aint broke so KISS
Pipewire is fun to add FX in my signal chain to my DAW, but for serious work I have a physical FX rack.
I love pavucontrolI understand why Wayland was made and only have it on my SBC Raspberry Pi5
#Ifconfig #ip #init #systemD #Xorg #Wayland #programming #pipewire #ALSA #OSS
-
If you want a FreeBSD-like ifconfig on Linux-based operating systems, I made one. I needed the same syntax across both.
http://jdebp.info/Softwares/nosh/
http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml
-
2.
Probably best to illustrate how ifconfig handles netmasks too.
3.
Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.
-
2.
Probably best to illustrate how ifconfig handles netmasks too.
3.
Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.
-
2.
Probably best to illustrate how ifconfig handles netmasks too.
3.
Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.
-
2.
Probably best to illustrate how ifconfig handles netmasks too.
3.
Coming from GNU et al. toolsets, the naming pattern of procstat/fstat/vmstat/netstat/kldstat/sockstat/iostat is not obvious when only sees them presented as piecemeal equivalents.
-
If you like the FreeBSD syntax, I have an ifconfig that is closer to FreeBSD syntax than the net-tools one is.
In fact, that was its raison d'être. It brought (most of) the FreeBSD syntax to Debian so that I could auto-translate /etc/network/interfaces into FreeBSD-like setup that used ifconfig.
http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml
-
1/2
Vamos con el feedback de la encuesta!! Mil gracias a todos por participar!! 🤗
🟢 Solución: ip a
El comando #ip permite realizar casi todas las configuraciones de red en GNU/Linux.
"ip a" es la abreviatura de "ip addr", o "ip address", todos hacen lo mismo.
Es parte del paquete #iproute2, reemplazo de net-tools de #Unix, y remplaza a varias herramientas hoy consideradas obsoletas en Linux (creo que hace todo lo que antes hacíamos con #ifconfig, #route, #iptunnel, o #arp).
(sigue)
-
Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig
-
Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig
-
Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig
-
Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig
-
Call for testing: bge/bnx/iavf/igc/ix/ixl/ngbe/pcn: ifq_restart() fix https://www.undeadly.org/cgi?action=article;sid=20250624072336 #openbsd #bugfix #current #callfortesting #test #bge #bnx #iavf #igc #ix #ixl #ngbe #pcn #networking #ifq_restart #ifconfig
-
As implied, the #NetBSD port of #nosh, #redo, and #djbwares is pretty much done.
NetBSD doesn't make it as easy to switch between process 1 programs as FreeBSD does, so the system manager is not tested. But many of the other tools from tai64nlocal, cyclog, and setterm; through login-envuidgid and envdir; to the service manager and console-tty37-viewer; have now been used in earnest.
There are known missing bits in #ifconfig and list-process-table. And UVT realizers are not tested at all yet.
-
#iproute2 6.14.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2
-
#iproute2 6.11.0 has been released (#iproute / #ifconfig / #TCPIP) https://wiki.linuxfoundation.org/networking/iproute2
-
@nixCraft I find the iproute2 syntax so much saner! I love it ❤️
Although I spent some years working with good old ifconfig I wouldn’t even consider using it today and writing this I realize I can’t remember its syntax anymore. And that’s a good thing for me.
-
lladdr-tied interface config support has been committed https://undeadly.org/cgi?action=article;sid=20221206062638 #openbsd #ifconfig #networking #macaddress #lladdr
