Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
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).
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.