-
Notifications
You must be signed in to change notification settings - Fork 0
workstation opensuse
Why openSUSE (vs.Fedora):
- Rolling
- zypper
- nicely decorated bash
- other little items already installed/work out of box (so what else have I been missing?)
a. firefox flash
b. chrome-gnome stuff
c. more ir codes
openSUSE adds a gui/management layer in between the DE and the underlying OS.
Upside(s):
- because openSUSE has intelligent, centralized, and fine grained control over all aspects, despite upstream of DE.
- using the tools ensure that the process is done right/completely, despite what the end-user thinks they understand about unix/linux
Downside(s)
- tutorials are more limited than more standard distro (centos, redhat, fedora, arch)
- adds distro-specific stuff for the end-user to know about/learn
- This layer is mostly gui
These aren't strong, but raise the flag of whether it is worth it for the (few) benefits.
packages (util):
zypper in hplip nfs4-acl-tools git htop
markdown extension for browser (best markdown find to date!)
packages (preference):
zypper in materia-gtk-theme paper-icon-theme
zypper rm gnome-software PackageKit
opensuse-multimedia-libs:
sudo zypper ar -f http://ftp.gwdg.de/pub/opensuse/repositories/multimedia:/libs/openSUSE_Tumbleweed/ opensuse-multimedia-libs
sudo zypper ref
fstab mount options for NFS shares:
defaults,x-systemd.automount,x-systemd.requires=network-online.target
ensures that NFS shares are mounted upon resume
ref:Arch wiki: Mount using /etc/fstab with systemd
add relevant groups
append groups to users appropriately
(see Fileshare for details)
/etc/idmapd.conf
uncomment & enter domain-name <- same name as used in server idmapd.conf
Domain = sameDomainNameHere
Enable (& start) rcpbind service
systemctl enable rpcbind
systemctl start rpcbind
- for laptop? NetworkManager. full stop.
- I like the configurability of Wicked, but it lacks gnome integration (applet)
- Wicked (so far, for kodibox) shows no significant advantage over NM
Service switch (to Wicked)
systemctl status network
#show/verify which service is managing the network, and its status
systemctl stop network
#stop the network (& assigned services)
systemctl disable NetworkManager
systemctl enable wicked
systemctl start network
#start the network (& assigned services)
systemctl status network
#show/verify which service is managing the network, and its status
Use gateway ip for dns server address, if needed.
CLI setup differs per service chosen"
If NetworkManager, ~three files need to be modified if not done through the gui.
You need to edit three files:
/etc/sysconfig/network/ifcfg-eth0BOOTPROTO='static' IPADDR='192.168.2.77' MTU='1500' NAME='' NETMASK='255.255.255.0' STARTMODE='auto' USERCONTROL='no'
/etc/sysconfig/network/routes
default 192.168.2.1 - -
/etc/resolv.conf
nameserver 192.168.2.1
And then this gem of advice:
Another idea, not nearly as geeky or sexy, would be to enter "yast" at that terminal prompt, then use the arrow and tab keys to get to Network Devices -> Network Settings.
If you insist on knowing how to do it manually, just look at the contents of the files named above after you use Yast to see what it did.
If wicked, theres an xml to spar with (unexplored)
/etc/wicked/*.xml
see:
https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet_manconf.html
https://github.com/openSUSE/wicked/blob/master/README