Breaking Old Standards
 

I just installed arch linux in a VM and everything is fine. Arch is pretty impressive and really cool.

I just have two caveats with arch. Some commands are not linux standards. So far, I only encountered two, but there could be more or not.

I opened the terminal to do a quick netstat to see what ports are open and netstat wasn't available. A quick google search says it is now ss. The other one is ifconfig, now ip.

The second caveat is stating services. The old standard that I used for years when I came to linux was /etc/init.d/service-name start|stop|restart. Now it's systemctl.

If you're used to old standards be prepared to be re-schooled with arch. The good news it is just a few changes to learn. :)

So far, ip and ss are the new replacements in arch. Are there others?

Thanks in advance.

ip and ss are not necessarily Arch things. Yes, they are relatively new commands, but they are relatively new Linux commands, not new Arch commands.

Both are included in Slackware, Debian, and CentOS, for example, not one of which can be accused being bleeding edge (and they are probably in many other distros, but those are ones I can test right now).

That's what I meant to to say. But you said it better :)

When you're used to using certain commands for years, I mean years. You get used to them, you expect them to be in all linux distros.

It's good to learn new things so you can deal with systemd distros and those new command replacements.

Thanks frank for the reply +1

This I get.

I'm still learning my way around the ip command. As an aside, I find its output to be much less pleasingly formatted than the output of ifconfig, but I'm sure they'll get there eventually.

That's way when one is using linux, we are forever continuously learning. :)

Welcome to LQ! Sounds like you are a 'heavy' Linux/Unix 'oldtimer' ;)
(feel free to share a bit of 'autobiography' in the Intro Forum)

IF you'd like to read a bit of the discussions on this, toss: ifconfig deprecated
into an LQ (or web) search.

Great to hear you're enjoying Arch! Just doNOT start any debates on systemd:D

You don't have to worry about that as I know very little of it. I just learn enough to get the job done like start, stop, enable and disable services.

I am aware that there are people who don't like it. All I can say is there are other penguins in the sea :)

Thank you Jjanel for the welcome.

I sympathise! Then there's the disappearance of eth0, and the change /mnt > /media > /run... Like the man sang, "Slow down, you move too fast"

netfilter instead of iptables instead of ipchains.
ip instead of ifconfig
iw instead of iwconfig
dhcpcd instead of dhclient (arch anyway)

The syntax of shutdown changed with systemd:
# shutdown -h now
became
# shutdown -H -P +0

And service instead of /etc/init.d/{script} start|stop|restart
# service --status-all
# service cron stop
(didn't seem to work in fedora 23)

Where systemctl works too, but slight different syntax.
# systemctl stop ModemManager

Instead of creating a custom xorg.conf, you now use xinput, xrandr, and other things AFTER booting X to fine tune things. Or a modern DE that does those things for you, sometimes correctly.