openSUSE Users August 2020

users@lists.opensuse.org

62 participants
56 discussions

[opensuse] Raid, Raid6, what file system for good fault tolerance?

by cagsm

Hi list, speaking about software raid, not hardware controller based. I am trying to go for some local OpenSuse machine and adding some storage to it. Was considering Raid6, and now reading about a bit and people left and right scaremongering about the larger the disks these days in the double digit terabyte capacities even, the more likely it is that during a reconstruction of a raid subsequent errors would occur. I would absolutely like to keep my data consistent, and I am not thinking about double digit terabytes either, would stick to 2TB or 4TB disks, with Raid6 thats at least 4 physical drives. Now I am wondering if it possible to use a good robust file system that can add some more parity or check blocks or redundancy on top of the hardware disks, to absolutely be able to always read my data. I can't add multiple machines or like those high availability stuff like clusters and what not I read about DRBD (Distributed Replicated Block Device), or maybe I am just too scared by those technical terms or consider myself to be just a simpleton and wanting to keep it rather simple. My use case here is also not constant availablity, when a disk needs to be replaced, so be it, but I don't want to lose my data that I can not ever read certain parts of it again or such stuff. The thing that came to my mind was, if there is some file systems that would add redundancy and robustness onto the mdraid system of the linux kernel? Anyone with some useful insights? Roughly speaking, I was considering some simple pcie esata interfaced controller card and an external case enclosure with esata port and portmulitplier stuff inside, that can present at least 4 physical disks as JBOD, just a bunch of disks, so that the Linux can seem them all separately. Speed and rebuild times are not my concern, but data persistence and data integrity. Not even number of physical disks, I could live with even one of those 8 bay device enclosures and cases that are out there on the market. Thanks for any help and hints. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 months

[opensuse] Fw: [Bug 1128204] retext crashes with core dump

by Dave Howorth

Hmm, I just got this message from Atri, who I've seen looks at this list. I haven't migrated my bugzilla account because I don't want to continue to use the old account name. I just tried to respond and it wants details I cannot supply (I don't know what username/password are - I've never needed them - my browser supposedly knows them but apparently can't reproduce whatever information is required to respond to the 'migration portal') But more fundamentally, I don't use TW. I use Leap and I'm still on 15.0. Begin forwarded message: Date: Sun, 07 Jun 2020 19:16:08 +0000 From: bugzilla_noreply(a)suse.com To: ********* Subject: [Bug 1128204] retext crashes with core dump http://bugzilla.suse.com/show_bug.cgi?id=1128204 http://bugzilla.suse.com/show_bug.cgi?id=1128204#c11 --- Comment #11 from Atri Bhattacharya <badshah400(a)gmail.com> --- Sorry Dave, I missed the train on this one. Can you still reproduce this with the latest TW? -- You are receiving this mail because: You are on the CC list for the bug. You reported the bug. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 months, 1 week

[opensuse] Issue with smartd

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have one disk that is giving me problems with the smartd daemon. I get this in the log: <3.6> 2018-10-21T13:45:23.829155+02:00 Isengard smartd 1173 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.483719+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], opened <3.6> 2018-10-21T13:45:24.484570+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB <3.6> 2018-10-21T13:45:24.503334+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not found in smartd database. <3.6> 2018-10-21T13:45:24.525071+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Attribute Autosave. <3.6> 2018-10-21T13:45:24.530486+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Automatic Offline Testing. <3.6> 2018-10-21T13:45:24.535003+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], is SMART capable. Adding to "monitor" list. <3.6> 2018-10-21T13:45:24.535627+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.880219+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T14:15:25.233525+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 147 to 144 <3.6> 2018-10-21T15:45:31.681938+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T15:45:33.632399+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T16:15:24.678100+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email <3.6> 2018-10-21T18:15:31.767150+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T18:15:33.717688+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T18:45:24.587304+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email It intermitently but periodically fail to read atributes, triggering hundreds of emails sent to me to warn of the problem: +++------------ Subject: SMART error (FailedReadSmartData) detected on host: Isengard This message was generated by the smartd daemon running on: host name: Isengard DNS domain: valinor The following warning/error was logged by the smartd daemon: Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data Device info: WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB For details see host's SYSLOG. You can also use the smartctl utility for further investigation. Another message will be sent in 24 hours if the problem persists. - ------------++- The disk is indeed smart capable and it works fine, as long as I call smartctl with "-d sat,16", which I do: Isengard:~ # smartctl --test=short -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 2 minutes for test to complete. Test will complete after Sun Oct 21 13:50:18 2018 Use smartctl -X to abort test. Isengard:~ # Isengard:~ # smartctl --health -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Isengard:~ # It is crucial to use "-d sat,16" or it fails: Isengard:~ # smartctl --health /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0: Unknown USB bridge [0x1058:0x25ee (0x4004)] Please specify device type with the -d option. Use smartctl -h to get a usage summary Isengard:~ # Of course I use that option on the config: Isengard:~ # cat /etc/smartd.conf | egrep -v "^[[:space:]]*$|^#" /dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000000000000001 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000c5009399305f -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 -d sat,16 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor Isengard:~ # What else am I missing? Is smartd not using "-d sat,16" somewhere else? Is it some other problem? Isengard:~ # rpm -q smartmontools smartmontools-6.6-135.1.x86_64 Isengard:~ # - -- Cheers Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvM5UMACgkQtTMYHG2NR9WCwQCePjOt8PSMKsx6DwSe9bZJRhHf 2lQAn02eBTrtfAqmEg5ydZVagvMfW2r6 =eIzR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 months, 1 week

[opensuse] 2~2~2~Can clonezilla be "used" inside openSUSE?

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I know that it is used as a live cd or stick, but I wonder if could create an external hard disk with openSUSE and the clonezilla tools. The external would be the live system, the storage space for the images, and a familiar Linux system, with openSUSE, that would do more than just clone/restore a system. I suppose it is a script and some tools like partclone. Anybody tried? - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX0USgRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVJsYAmQFcsTz4Ll3HHI8Y/Jlx eYdaoB17AKCZMG6+Lz1hM3ZzmoiePGLouSN5vA== =ctoz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 3 weeks

[opensuse] 15.2 zypper up NEW package virtualbox-guest-x11 - Why? I don't want it... I build guest modules

by David C. Rankin

All, For my 15.2 guests, I use Oracles virtualbox (currently testbuilds) I build my own modules for guest additions. I explicitly removed virtualbox-guest-x11 because I don't want the conflicting guest modules. DKMS rebuilds the modules just fine on kernel update with the vboxadd.service enabled. Now, for some reason, when I attempt zypper up I get: The following NEW package is going to be installed: virtualbox-guest-x11 I know I can just put a lock or exclusion of some type on it -- but why is it trying to install itself as a new package? I didn't ask it to? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 3 weeks

[opensuse] Thunderbird 78.2.1 available for testing in mozilla:beta

by Wolfgang Rosenauer

Am 30.08.20 um 19:23 schrieb Wolfgang Rosenauer: > Hi, > > Am 30.08.20 um 15:07 schrieb Mathias Homann: >> thunderbird 78.2.0 is out and has working gpg integration now, I think it's >> safe to upgrade the package in /mozilla... > > for the mozilla projet I think so as well. So when can we get it? oh, wait, I guess I just asked myself. This mail - in case it arrives for you - has been sent with Thunderbird 78.2.1 on openSUSE Leap 15.2 using the package in mozilla:beta. I'm not planning to upgrade Tumbleweed within the next few days but give people the chance to test this one and send feedback / open bugreports. Please also keep in mind that the OpenPGP integration in TB 78 does not use system GPG and also not the regular keyring but has its own keymanagement only right now. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 3 weeks

[opensuse] kernel RPM bad magic number

by Anton Aylward

I've been getting errors like this for a while now. An I alone in this? Anyone else? Retrieving package kernel-default-5.8.5-2.1.g34111a4.x86_64 (11/11), 82.2 MiB (175.5 MiB unpacked) Retrieving: kernel-default-5.8.5-2.1.g34111a4.x86_64.rpm ......................................[done (54.4 KiB/s)] (11/11) Installing: kernel-default-5.8.5-2.1.g34111a4.x86_64 ..............................................[error] Installation of kernel-default-5.8.5-2.1.g34111a4.x86_64 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed: cpio: Bad magic error: kernel-default-5.8.5-2.1.g34111a4.x86_64: install failed This is retrieved from the kernel_Stable repository http://download.opensuse.org/repositories/Kernel:/stable/standard/ I've been using this for a couple of years now and not had any problems. When I look at the tile, it's not what I expect, it's an info file begining... using 'less' =============================== Information ==================================== Name : kernel-default Version : 5.8.5 Release : 2.1.g34111a4 Architecture: x86_64 Install Date: (not installed) Group : System/Kernel Size : 184011822 License : GPL-2.0 Signature : RSA/SHA256, Sat Aug 29 06:38:02 2020, Key ID eceef21003579c1d Source RPM : kernel-default-5.8.5-2.1.g34111a4.nosrc.rpm Build Date : Sat Aug 29 06:30:47 2020 Build Host : cloud131 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/Kernel URL : http://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2020-08-28 08:13:28 +0000 GIT Revision: 34111a4d58e41d742247fcdfbc75c119245dfdba GIT Branch: stable Distribution: Kernel:stable ================================= Changelog (head) ============================= * Fri Aug 28 2020 tiwai(a)suse.de - fs/cachefiles: Drop superfluous readpages aops NULL check (bsc#1175245). - commit 34111a4 * Thu Aug 27 2020 jslaby(a)suse.cz - Linux 5.8.5 (bsc#1012628). - binfmt_flat: revert "binfmt_flat: don't offset the data start" (bsc#1012628). That's just too weird. But it's the right size -rw-r--r-- 1 root root 86202179 Aug 30 21:48 /var/cache/zypp/packages/Kernel_Stable/x86_64/kernel-default-5.8.5-2.1.g34111a4.x86_64.rpm using od -cb 0000000 355 253 356 333 003 \0 \0 \0 \0 001 k e r n e l 355 253 356 333 003 000 000 000 000 001 153 145 162 156 145 154 0000020 - d e f a u l t - 5 . 8 . 5 - 2 055 144 145 146 141 165 154 164 055 065 056 070 056 065 055 062 0000040 . 1 . g 3 4 1 1 1 a 4 \0 \0 \0 \0 \0 056 061 056 147 063 064 061 061 061 141 064 000 000 000 000 000 0000060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 0000100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 005 000 000 000 000 000 000 000 000 000 000 000 000 000 001 000 005 0000120 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 0000140 216 255 350 001 \0 \0 \0 \0 \0 \0 \0 \t \0 \0 022 344 216 255 350 001 000 000 000 000 000 000 000 011 000 000 022 344 0000160 \0 \0 \0 > \0 \0 \0 \a \0 \0 022 324 \0 \0 \0 020 000 000 000 076 000 000 000 007 000 000 022 324 000 000 000 020 0000200 \0 \0 001 \f \0 \0 \0 \a \0 \0 \0 \0 \0 \0 001 030 000 000 001 014 000 000 000 007 000 000 000 000 000 000 001 030 0000220 \0 \0 001 \r \0 \0 \0 006 \0 \0 001 030 \0 \0 \0 001 000 000 001 015 000 000 000 006 000 000 001 030 000 000 000 001 0000240 \0 \0 001 021 \0 \0 \0 006 \0 \0 001 A \0 \0 \0 001 000 000 001 021 000 000 000 006 000 000 001 101 000 000 000 001 0000260 \0 \0 003 350 \0 \0 \0 004 \0 \0 001 204 \0 \0 \0 001 000 000 003 350 000 000 000 004 000 000 001 204 000 000 000 001 or in hex 0000000 355 253 356 333 003 \0 \0 \0 \0 001 k e r n e l abed dbee 0003 0000 0100 656b 6e72 6c65 0000020 - d e f a u l t - 5 . 8 . 5 - 2 642d 6665 7561 746c 352d 382e 352e 322d 0000040 . 1 . g 3 4 1 1 1 a 4 \0 \0 \0 \0 \0 312e 672e 3433 3131 6131 0034 0000 0000 0000060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0000 0000 0000 0000 0000 0000 0000 0000 0000100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 005 0000 0000 0000 0000 0000 0000 0100 0500 0000120 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0000 0000 0000 0000 0000 0000 0000 0000 0000140 216 255 350 001 \0 \0 \0 \0 \0 \0 \0 \t \0 \0 022 344 ad8e 01e8 0000 0000 0000 0900 0000 e412 0000160 \0 \0 \0 > \0 \0 \0 \a \0 \0 022 324 \0 \0 \0 020 0000 3e00 0000 0700 0000 d412 0000 1000 0000200 \0 \0 001 \f \0 \0 \0 \a \0 \0 \0 \0 \0 \0 001 030 0000 0c01 0000 0700 0000 0000 0000 1801 0000220 \0 \0 001 \r \0 \0 \0 006 \0 \0 001 030 \0 \0 \0 001 0000 0d01 0000 0600 0000 1801 0000 0100 0000240 \0 \0 001 021 \0 \0 \0 006 \0 \0 001 A \0 \0 \0 001 0000 1101 0000 0600 0000 4101 0000 0100 0000260 \0 \0 003 350 \0 \0 \0 004 \0 \0 001 204 \0 \0 \0 001 0000 e803 0000 0400 0000 8401 0000 0100 Well the first four bytes seem right. Smallend/bigend problem? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 4 weeks

[opensuse] Leap 15.2: grub2 patch openSUSE-2020-1282 made my system unbootable

by Mathias Homann

Hi all, was I the only one having issues with openSUSE-2020-1282 (the grub2 patch) that was rolled out yesterday? After installing it I couldn't boot to linux anymore, the error was something about being unable to read the kernel and ram disk. grub2-mkconfig didn't help, only rolling back to the grub version before the patch did. Did anyone else notice? cheers Mathias -- Mathias Homann Mathias.Homann(a)openSUSE.org Jabber (XMPP): lemmy(a)tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

5 months, 4 weeks

[opensuse] cpu heat

by jdd＠dodin.org

Hello, On my main laptop, I find the cpu is getting hot very fast My desk is climatized, temperature is not cold but not hot either (around 27°C) at rest the cpu temp is around 60° a simple copy from a disk to an other makes it go up to 85°C, and dmesg gives red warning cpu speed is reduced. [ 661.011117] CPU2: Core temperature above threshold, cpu clock throttled (total events = 1) [ 661.011118] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) [ sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +60.0°C (high = +84.0°C, crit = +100.0°C) Core 0: +59.0°C (high = +84.0°C, crit = +100.0°C) (...) the computer become completely unresponsive, impossible to switch desktop or applications, copy:> sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +79.0°C (high = +84.0°C, crit = +100.0°C) the bottom of the computer can be opened, but it's not that easy (lot of just now I couldn't finish this mail before the copy (from caddy hdd to usb disk - system is on ssd). Smartctl shows disks are fully ok I *can* try to remove dust :-). But is there any use to change thermal grease on cpu (much more difficult) top and pas ax do not show any btrfs activity (root), involved disk is ext4 thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 months, 4 weeks

[opensuse] Getting rid of all traces of python2?

by Mathias Homann

Hi, is it possible by now to uninstall python2 and **not** break half of one's system? Leap 15.2 here... and a "zypper rm -u python-base" would wipe out several desktop apps that I use... Cheers Mathias -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users August 2020