Archive for the ‘SuSE Linux’ Category
Posted by jpluimers on 2018/01/01
For my research list (thanks Mariusz Fik @Fisiu):
Actually: this was more of a reminder checking out if someone else by now has made OpenSuSE Tumbleweed builds for ODROID (:
–jeroen
via:
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2017/12/14
Yes, there are still static web-sites. A long time ago, they were uploaded over FTP. Now many use more secure protocols.
So here are some links and notes to allow this on a Linux based host running OpenSSH.
I got to the above via these two links:
An alternative might be web-dave, but that would probably mean some hassle to separate uploading the site from accessing the site.
[Archive.is] How To Set Up WebDAV With Apache2 On OpenSUSE 12.2
–jeroen
Posted in *nix, Communications Development, Development, Internet protocol suite, Linux, openSuSE, Power User, SSH, SuSE Linux, TCP | Leave a Comment »
Posted by jpluimers on 2017/12/01
I had zypper being confused about the dist-upgrade between these snapshots:
< CPE_NAME="cpe:/o:opensuse:tumbleweed:20171125"
---
> CPE_NAME="cpe:/o:opensuse:tumbleweed:20171129"
It ran into this:
Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch
Based on [WayBack] Re: [opensuse-factory] openssl dependency problems with snapshot 2017112 after discussing with DimStar, I choose to have zypper dist-upgrade to perform
deinstallation of libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64
Now all is fine.
Thanks Dominique a.k.a. DimStar!
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/11/30
SuSEconfig has been dead for a while, but still indexed at quite a few of the official sites stressing the importance to use it.
It used to apply the configuration in /etc/sysconfig to the system.
The rationale for removal was simple:
Let’s remove all SuSEconfig scripts since only YaST calls SuSEconfig but other tools like rpm and zypper do not call it.
If scripts are needed, they need to be invoked as part of the postinstall.
Now most services either know to directly handle the configuration data there (and apply it during reload/restart/start of the service), or have a tool (like postfix now has /usr/sbin/config.postfix) to apply the settings.
–jeroen
References:
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/11/09
Interesting as it has steps for both OpenSuSE and Debian each well suited for running on a Raspberry Pi.
[WayBack] MX Backup – Postfix Email Server | samhobbs.co.uk
It seems postfix is a lot easier to configure than sendmail so I already like it.
First I need to read a bit more in Postfix greylisting.
I’ll need to catch up on Sam’s other parts with the postfix tag as well:
–jeroen
Posted in *nix, *nix-tools, Debian, Development, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, Raspbian, sendmail, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/11/07
Learned a few things when modifying https://github.com/gkotian/gautam_linux/blob/master/scripts/colours.sh
Note: `printf` supports emitting `ESC` (ASCII character `\033` aka `27` aka `0x1B`)as `\e` the same way that `echo` does
https://linux.die.net/man/1/printf
https://linux.die.net/man/1/echo
Format strings are at https://linux.die.net/man/3/printf
%-10s means left adjusted (aligned) string of length 10
–jeroen
via:
I was investigating how the colour definitions on my OpenSuSE system actually work internally so I added some extra output: ${TYPE} and ${COLOUR}.
Source: Show type and colour definition in addition to the rendered colour. by jpluimers · Pull Request #5 · gkotian/gautam_linux
Posted in *nix, *nix-tools, bash, bash, Development, Linux, openSuSE, Power User, Scripting, Software Development, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2017/09/28
kvm [1]: Invalid trigger for IRQ4, assuming level low
OF: /soc/usb at 7e980000: could not get #phy-cells for /phy
Via [WayBack] Oops. – Jeroen Wiert Pluimers – Google+
This was after updating my Raspberry Pi 3 with Tumbleweed to 20170920.
Not sure what do do now. Some searches didn’t reveal much:
–jeroen
Posted in *nix, Development, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/09/15
I totally missed this announcement 2 months ago:
after this update, zypper dup will default to –no-allow-vendor-change, whichhas been the recommended way for Tumbleweed for a long time now.
Source: Re: [opensuse-factory] dup –no-allow-vendor-change is now default
So Dominique was glad to “rub the salt” a bit (:
[WayBack/Archive.is] Dominique / DimStar @DimStar Replying to @sysrich @jpluimers: for the record: –no-allow-vendor-change has become the default in Tumbleweed, see also http://dominique.leuenberger.net/blog/2017/06/review-of-the-week-201726/
It was documented at least on these places:
- [Archive.is] Review of the week 2017/26 – Dominique a.k.a. DimStar (Dim*):
libzypp: change of default setting for ‘allow vendor change to false’ during zypper dup (just a change in the default shipped zypp.conf file)
- [WayBack] openSUSE News: Tumbleweed Snapshots Update AppStream, Mesa, Frameworks – July 13th, 2017 by Douglas DeMaioThe 20170708 snapshot had a big change to
libzypp 16.13.0. The new version update hides the switch of the default for zypper dup; after this update, zypper dup will default to --no-allow-vendor-change, which has been the recommended way for Tumbleweed for a long time now, according to an email post on the openSUSE Factory Mailing List from Dominique Leuenberger. That is if the user did not change /etc/zypp/zypp.conf -.
- [WayBack] [opensuse-factory] New Tumbleweed snapshot 20170708 released!
– Adjust zypp.conf for openSUSE Tumbleweed (bsc#1031756)
- [WayBack] Re: [opensuse-factory] dup –no-allow-vendor-change is now default
– Adjust zypp.conf for openSUSE Tumbleweed (bsc#1031756)
^^^^ This change hides the switch of the default for zypper dup: after
this update, zypper dup will default to –no-allow-vendor-change, which
has been the recommended way for Tumbleweed for a long time now.
NOTE: This will ONLY update your default configuration if you did not
touch /etc/zypp/zypp.conf – If you had local modifications, rpm will
have put a file NEXT to it (zypp.conf.rpmnew), in which case you have
to adjust the settings manually (or you likely already did)
Hope this will eliminate a good part of the issues people kept on
reporting about updates – bringing Tumbleweed one step closer to what
you expect it to do in all situations.
–jeroen
Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/09/13
If you see error message like below when performing zypper refresh or zypper dist-upgrade, then please inform the opensuse team (for instance Twitter or the #openSUSE-factory IRC channel) as this is part of the aftermath of the download.opensuse.org trouble that started last week.
Permission to access 'http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/suse/setup/descr/appdata-icons.tar.gz' denied.
What happened to me with Raspberry Pi 3 and Tumbleweed is below and fixed because after I got in touch: the data restore had worked out OK, but the permissions didn’t.
I got there as the search for “Permission to access ‘http://download.opensuse.org/ports/aarch64/” got me to [WayBack] TUMBLEWEED Zypper Permission to access:
Unfortunately there was a catastrophic issue last week with the openSUSE download system (read: stuff is still broken and not all mirrors are fully functional).
–jeroen
Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2017/08/21
I didn’t notice this bind change for a while, but some time ago after doing an rcnamed restart it would split out this error message:
the working directory is not writable
It seems harmless as BIND still starts:
Starting name server BIND ..done
Anyway, some links that helped me solve it:
The last entry provides the solution:
rcnamed stop
chown named:named /var/lib/named/ -R
rcnamed start
rcnamed status
The latter didn’t show any error message.
–jeroen
Posted in *nix, bind-named, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
The Wiert Corner - irregular stream of stuff 