Tony Su
2018-09-14 16:12:29 UTC
Follow up to Last night's meeting
I thought I might post this follow up to last night's discussions that
sprung from the two presentations I gave...
First,
Links to the content...
First Hour
Because there were several people who either didn't see my July
presentation on installing openSUSE for the first time or had
questions about their first install, I skimmed the slide deck again
with more emphasis on audience questions...
https://slides.com/tonysu/opensuse
Second hour,
Since the topic of the night was scripting tricks for newbies,
I presented on a small collection of script examples I'd collected
over the years, largely based on links you'll find at the following
page
https://en.opensuse.org/User:Tsu2/Scrips_and_Scriplets
You'll also find the above and other scripting examples in other Wiki
pages I've created, particularly for setting up complex
applications... I've found that the more complex the setup is, the
more importance in scripting the install and setup so that it's
replicable if the machine has to be replaced or if at a later time you
need to re-evaluate security.
For those who are interested in other topics in my openSUSE wiki, the
following is my "Index page." It's just a place where I write about
interesting and useful things I've run into over the years first for
my own personal benefit but also for anyone else who might find the
info useful. I don't keep it up, so some content is old and may be
obsolete but most continue to be relevant no matter when they were
written.
https://en.opensuse.org/User:Tsu2
There was a discussion about the new socket-based implementation of
Wayland in openSUSE (replacing the Xorg Xserver which has been around
since forever). I'd recommend anyone interested in this to inspect the
relevant systemd Unit files which now describe socket activation
instead of running a server. I don't know that there a proper
technical documentation exists for this new and very important
implementation of Wayland, but there is plenty written about new
methods to setup VNC.. In fact, it's been a real bone of contention in
the openSUSE forums where there are those who want to set up VNC the
same way they've done so for the last 10 years (it's usually
possible), or the way it was possible just before the current major
change(That common sense approach apparently is no longer possible),
or the new ways (Massive new learning curve).
You can get an idea of the "new way" to do things in the following
documentation, as always if you just want a simple remote connection
without complications you should use the openSUSE YaST tool to
setup...
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.vnc.html
But, it's not as simple as the above!
If you <really> want to dig a bit deeper, you should read the very
extensive TigerVNC documentation (openSUSE installs TigerVNC) and
you'll find that there are at least 2 major sub-implementations of
VNC, xVNC (which is set up by default using YaST),
x0vncserver(preferred by a very large number of Users), and then there
are a multitude of additional options... I use the Arch Linux Wiki
article on TigerVNC for most of this(which may in turn link to other
Arch Wiki pages)
https://wiki.archlinux.org/index.php/TigerVNC
VNC is no longer something simple to set up unless and until someone
in that project decides to change its current course of development...
And is likely a preview of what is to come if not already seen in
other distros.
I thought I might post this follow up to last night's discussions that
sprung from the two presentations I gave...
First,
Links to the content...
First Hour
Because there were several people who either didn't see my July
presentation on installing openSUSE for the first time or had
questions about their first install, I skimmed the slide deck again
with more emphasis on audience questions...
https://slides.com/tonysu/opensuse
Second hour,
Since the topic of the night was scripting tricks for newbies,
I presented on a small collection of script examples I'd collected
over the years, largely based on links you'll find at the following
page
https://en.opensuse.org/User:Tsu2/Scrips_and_Scriplets
You'll also find the above and other scripting examples in other Wiki
pages I've created, particularly for setting up complex
applications... I've found that the more complex the setup is, the
more importance in scripting the install and setup so that it's
replicable if the machine has to be replaced or if at a later time you
need to re-evaluate security.
For those who are interested in other topics in my openSUSE wiki, the
following is my "Index page." It's just a place where I write about
interesting and useful things I've run into over the years first for
my own personal benefit but also for anyone else who might find the
info useful. I don't keep it up, so some content is old and may be
obsolete but most continue to be relevant no matter when they were
written.
https://en.opensuse.org/User:Tsu2
There was a discussion about the new socket-based implementation of
Wayland in openSUSE (replacing the Xorg Xserver which has been around
since forever). I'd recommend anyone interested in this to inspect the
relevant systemd Unit files which now describe socket activation
instead of running a server. I don't know that there a proper
technical documentation exists for this new and very important
implementation of Wayland, but there is plenty written about new
methods to setup VNC.. In fact, it's been a real bone of contention in
the openSUSE forums where there are those who want to set up VNC the
same way they've done so for the last 10 years (it's usually
possible), or the way it was possible just before the current major
change(That common sense approach apparently is no longer possible),
or the new ways (Massive new learning curve).
You can get an idea of the "new way" to do things in the following
documentation, as always if you just want a simple remote connection
without complications you should use the openSUSE YaST tool to
setup...
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.vnc.html
But, it's not as simple as the above!
If you <really> want to dig a bit deeper, you should read the very
extensive TigerVNC documentation (openSUSE installs TigerVNC) and
you'll find that there are at least 2 major sub-implementations of
VNC, xVNC (which is set up by default using YaST),
x0vncserver(preferred by a very large number of Users), and then there
are a multitude of additional options... I use the Arch Linux Wiki
article on TigerVNC for most of this(which may in turn link to other
Arch Wiki pages)
https://wiki.archlinux.org/index.php/TigerVNC
VNC is no longer something simple to set up unless and until someone
in that project decides to change its current course of development...
And is likely a preview of what is to come if not already seen in
other distros.
--
KPLUG-***@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
KPLUG-***@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list