February 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Re: update
by Chuck Davis 18 Feb '18

18 Feb '18

I never was able to get my first machine to update from 20171228 to 201802xx (tried a few versions). So I reinstalled using 20180214 and it's back on track. Fearfully, I updated my development machine today from 20180205 to 20180215 and it went quite smoothly while I held my breath! I even still have a functional desktop after the update. So at least I'm current. Next is my laptop though it is using the Nvidia driver so should go smoothly. This just to confirm that it is apparently "safe" once again to do updates if you're lurking -- at least if you're not still at the end of December like my first machine. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Ancient History
by Richard Brown 18 Feb '18

18 Feb '18

> On 10 February 2018 at 19:59, Carlos E. R. <robin.listas(a)telefonica.net> wrote: >> Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is >> much older than 13.x), so it will not work. And I do not use btrfs, either. SuSE 6.2 was released in 1999 and support ceased for it in 2001 That is 18 and 16 years ago respectively 18 years before SuSE 6.2 was released, IBM PC 5150 was launched (August 1981). This technology was no longer supported by 1999, and was not supported by SuSE 6.2 in any way, manner, or form. 16 years ago, IBM PC XT was launched. This technology was also not supported by 1999 and was also not supported by SuSE 6.2 in any way, manner, or form. I'm legitimately curious how 16-18 years after the release of SuSE 6.2 you can make the quoted statement like it's a 'good thing' you've been able to do that. The best case implies you have an likely endless collection of hacks and workarounds to handle the winds of time that have no doubt ravaged that system over those years. Your system heralds from an era of the Melissa and ILOVEYOU viruses, of a time before the HTTP/1.1 standard was written, of Windows XP and KDE 1.1.1. When ext3 was the new filesystem on the horizon scaring the shit out of people. I can only imagine the collection of digital crud that are cluttering up forgotten parts of the filesystem on a system that old. I think it might be valuable to a museum, but I honestly cannot understand how anyone could possibly want to run a system that is so encumbered with ancient history. What benefit do you think you get from such an approach to computing? How do you think someone running an IBM PC 5150 in 1999 would have been seen by the people developing Linux 2.2 and SUSE 6.2? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 30

[opensuse] Leap 42.3 and Coffe Lake?
by Peter Suetterlin 16 Feb '18

16 Feb '18

Hi list, I wonder if someone here has experience with running 42.3 on Coffee Lake hardware. The MB of our server is having issues, and a (possible) replacement is an ASRock Fatality Z370 with an i7-8700. Are there known issues with the 4.4 kernel and Coffe Lake CPUs? I know the onboard graphics isn't working with Mesa 17, but I don't really care, its a server and runs text mode anyhow. The board also has a 10G card using the 'atlantic' kernel module that is not (yet) there in the 42.3 kernel. I can also live without that (for now). I'm running the board with TW at the moment, and that seems to work nicely (including graphics and 10G), but I'm not going to run TW on a server. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] /var/log and btrfs on Leap 42.3
by Roger Oberholtzer 16 Feb '18

16 Feb '18

I have a Leap 42.3 system that was working fine. I started a zypper dup, and part way through, it started complaining that there was no space on /var/log. This is not true. There are a couple of GB free on the /var file system. Still, I deleted a couple of log files to see what happened. The files deleted fine, and the free space as reported by df increased ad expected. However, I cannot write anything to /var/log. If I just try to touch a new file it complains that there is no free space on the device. I have rebooted, but the problem persists. The setup is btrfs as Leap 42.3 set up. Until this, all has been working great. When you cannot write to /var/log or such places, lots of system stuff no longer starts. So even though I can log in, all is rather basic. If this was the old ext4, I would run fsck. I have to admit that the options with btrfs are less clear to me. I have tried the suggestions here: https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_… When I run "btrfs fi balance start -dusage=5 /mount/point", no chunks are relocated. So I tried increasing the usage= value. When I hit 70, it complains that there is no space left on the device. So this seems not to be able to solve the problem. I cannot get it re reallocate a chunk. I have also checked here: https://www.suse.com/documentation/sles11/stor_admin/data/trbl_btrfs_volful… It suggests pretty much the same thing. I have not tried removing a snapshot. I would only expect that to help when there is actually no free space. But that is not the case. I do not want to destroy this system It is my work system. I'm open to suggestions. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 9

[opensuse] Display managers...
by Roger Oberholtzer 16 Feb '18

16 Feb '18

Recent versions of openSUSE have been using the sddm display manager as the default one. I think it looks and acts okay. Unfortunately, it does not work with XDMCP. So running rdesktop against such a system is not possible. I need to access the systems via something like rdestop. We have enabled kdm instead. It does work. But I think it is butt ugly. Is it really the case that it should be a gray screen with a gray Gecko? And a field in which you enter the name, and after pressing enter get a new field for the password? And that has a useless (IMHO) console window both during the login and after KDE starts? Not looking very impressive. Perhaps I have missed something that looks better? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] list of users of primary group
by Alex Naumov 15 Feb '18

15 Feb '18

Hey, can someone tell me how to get users list of some primary group. For example, I know only the name of this group: users. This is primary group and I can see it in id(1) output. How to get list of users who has the same prrmary group? Without needing to parse files. getent(1) and id(1) can do it, but it works contrariwise: it returns name of primary group (by giving user name). Thanks for info! Cheers, Alex -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 14

[opensuse] Package search web page does not work for me
by Carlos E. R. 15 Feb '18

15 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I go to: <https://software.opensuse.org/search> and search for any package, say "meld". I get a list of hits. I click on one: meld Visual diff and merge tool Show 1 Development packages and I get this error: <https://software.opensuse.org/package/meld> Error :codecs is not a valid locale I have been getting that error for some days. However, on a new user I don't get any error, it works. I do not have "codecs" as locale: cer@Telcontar:~> set | grep codec __git_mergetools_common=$'diffuse diffmerge ecmerge emerge kdiff3 meld opendiff\n\t\t\ttkdiff vimdiff gvimdiff xxdiff araxis p4merge bc codecompare\n' cer@Telcontar:~> locale | grep codec cer@Telcontar:~> - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAln06z8ACgkQtTMYHG2NR9U3lgCgjdg/rLggwxeTlT1Dh2qaCp03 bocAn3DlEbzUMiMOhh0uvItf/j6c/7Z7 =vPYi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 21

Re: [opensuse] Ancient History
by Stevens 15 Feb '18

15 Feb '18

While we are going down this rabbit hole, I have a complete TI 99/4a system with tape reader, 5" floppies and expansion cabinets (2) and some of the rom software: DOD, Calc, etc plus manuals. Been trying to find it a new home. Need to find a history buff or museum or something. Ancient History is the thread, hope I'm not hijacking. Located in north central Texas, north of Dallas. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 20

[opensuse] openSUSE on OpenVZ or Virtuozzo
by Bjoern Voigt 14 Feb '18

14 Feb '18

Some years ago some hosters offered openSUSE vServers based on the Virtuozzo virtualization platform. Now other distributions like Ubuntu LTS, Debian or CentOS are offered by such hosters. Even if someone tries to use openSUSE vServers for smaller setups based on Virtuozzo or the free OpenVZ project, this is not easy, because nobody created openSUSE templates more recent than openSUSE 13.2: https://help.virtuozzo.com/customer/en/portal/articles/2509591 https://openvz.org/Download/template/precreated Does anyone know the reasons for this development? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] grub2 won't show me the menu..
by Peter Suetterlin 14 Feb '18

14 Feb '18

Hi list, (I'm running TW, but I assume the issue is more general) After some issues with the latest update, I wanted to boot the previous kernel to see if that helps. /etc/default/grub is set to GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=0 As there is only on main OS on anyhow. OK, so press SHIFT during boot and ..... nothing, it just boots the default entry without even showing the menu. Also tried 't' (which is sometimes requested to press, too). No luck either, so I eventually gave up. So I changed the two timeout values to 2, and ran the grub2-mkconfig program. It still doesn't show the menu and just boots the default entry! I start getting quite pissed, TBH. OK, change the default boot entry or use grub2-once. But to what!? There are 31 possible commands listed if you type grub2-<TAB><TAB> NONE of them seems to be useful to provide the boot numbers from the menu. Nor does the manpage of programs that need this number as input give you a clue where to get the right number from. Why is SHIFT not working? Why does it ignore TIMEOUT settings? Why are manpages close to useless? What kind of **** is this? (Sorry for bad words, it's the weakest I could find) OK, somewhat cooled down, I'll try googling a bit more. But if someone already knows (some of) the answers.... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8