December 2017 - openSUSE Users - openSUSE Mailing Lists

Mount Windows NT(NTFS) drive as drive Z: for all users
by Keith Jacobs 25 Sep '21

25 Sep '21

We have an winNT server and need to auto mount a shared folder as if it were a windose mapped drive Z: on SuSE8 Could someone please explain how to do this and how to make sure it is set-up for every user everytime the system is booted. Thanks Regards Keith Jacobs New to Linux

3 2

[opensuse] Raid, Raid6, what file system for good fault tolerance?
by cagsm 21 Dec '20

21 Dec '20

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

9 23

[opensuse] oS 13.1 : "gnome keyring socket is not owned with the same credentials as the user"
by ellanios82 11 Aug '19

11 Aug '19

Hello List am using Xfce : - in /var/log/warn : i see warning " The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring-4i77r7/control 2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login keyring " ............... - any ideas how to fix ? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Mapping and re-mapping Keyboard Keys
by Paul Groves 14 Mar '19

14 Mar '19

On 27/06/17 12:22, Paul Groves wrote: > > On 27/06/17 08:34, Aaron Digulla wrote: >> xmodmap -pke | less > > These keycodes do not seem to match the system. For example in the > output of this command it says: > > keycode 158 = XF86WWW NoSymbol XF86WWW > > I ran setkeycodes e020 158 > > When I press the e020 (Internet) button xev says I have pressed code > 166 (Back button). > > How on earth has this happened? I specified 158 not 166. What have I > done wrong? > > Just been emailed this link: https://unix.stackexchange.com/questions/49650/how-to-get-keycodes-for-xmod… To quote this article: Here you can see keycode 97 is unused on my system: |keycode 94 = less greater less greater bar brokenbar keycode 95 = F11 XF86Switch_VT_11 F11 XF86Switch_VT_11 keycode 96 = F12 XF86Switch_VT_12 F12 XF86Switch_VT_12 keycode 97 = keycode 98 = Katakana NoSymbol Katakana keycode 99 = Hiragana NoSymbol Hiragana | The keycode X uses and the keycode the kernel uses are OFF BY 8 for "historical reasons". So take 97 - 8 = 89 and use 89 with the setkeycodes command (again as root): So to make my vol - button work (xmodmap keycode 122 -8 = 114) setkeycodes e01e 114 This has worked! I have re-mapped apl the buttons apart from my hotkeys. >> No but there are lots of uncommon keycodes which you can use. For >> example, F13-F35 or KP_F1...KP_F4. > > In the output of the command xmodmap -pke | less there are no codes > for F13-F35 or KP_F1 etc > > I would like to set HK1 - HK4 to F13 - F16 How do I find the keycodes > for these buttons Still looking for the keycodes for F13-16 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 19

[opensuse] continous access on/spinning up of floppy drive
by Paul Neuwirth 23 Oct '18

23 Oct '18

This is an OpenPGP/MIME signed message (RFC2440, RFC3156). --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: text/plain; charset="utf-8" Content-Disposition: inline; filename="message.txt" Content-Transfer-Encoding: quoted-printable Hello group, I have on several machines this problem: they are continously trying to=20 access the floppy drives. Two drives already defective, due to the=20 mechanic stress. dmesg shows following continously: [1537682.559487] sd 0:0:3:0: [sdc] Read Capacity(10) failed: Result:=20 hostbyte=3DDID_OK driverbyte=3DDRIVER_SENSE [1537682.559496] sd 0:0:3:0: [sdc] Sense Key : Not Ready [current] [1537682.559498] sd 0:0:3:0: [sdc] Add. Sense: Logical unit not ready,=20 cause not reportable [1537682.656688] sd 0:0:3:0: [sdc] Spinning up disk... [1537683.668046]=20 ............................................................................= ..................not=20 responding... [1537783.093938] sd 0:0:3:0: [sdc] Spinning up disk... [1537784.104049]=20 ............................................................................= ..................not=20 responding... this can't be the wanted behaviour for any removable storage devices? Any Hints? Thank you and have a nice weekend --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: application/pgp-signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Topal (http://freshmeat.net/projects/topal) iQIcBAEBAgAGBQJaLS66AAoJEIiaa+Y8YDPuZSUP/itt7+QHjNCwX6Wi352+lANf whjep7nBWy6Q0bS2PO/ymWDGiodFkO/AvM+MIitdK4cAm1HCBbMZjKsZYLD3e1LR ZnskqO66VG58TU6lVB1jEXWKlp6OKeb6Ar24SR0YxB4F+ZcbSwZI5w62JEBsozhV X4imcBdO+ztJFSW/hFLeV4WrfrplcTufyL6nw+5TtImrVs62uEg20LYjA//OxlHJ NmXM07A48uVBijRUmMsqeyRMevoKjKop2iICZgKyvTnRtRqx0jbzVeqj+aLqnbaq ncdBnBr7Vr9S86TVGHjIDHPN8Ws8dnufk1GwRTQR+Aj4z58g2r88j/u6o7csTFla vINP3ClCp6MRVbVbEqIYOIvG8NDIVTiwQwXk3CeCf+Be71JbDUMjV9GwVl+X9ksC oNBwwFi+mhHQGJOuX/54HGUEn3lJ1ixQzLimuXTgWmdsb1WoWuG+lNO13NhU+ZVn /IKpcqVjkXikQi9hrmZTUutmrFjJ1QusjnPJQDuBLYB0E/lMWjTpUNmRGw71hrDb uccAYc3sQP6zMuUfEgPWewhMmuTwn1LoQdqYrZ0p1+1z/+w5cB3DOB4JILmbKBUH QUYaDhefxPL1oRBtOxoDAdABJLAfgfKdEE0+g0u6HA67Atioe3HP8MWonrKgs3FC pvU9BHc2k0ASHh7HEsRx =uYfb -----END PGP SIGNATURE----- --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_=-- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

17 75

[opensuse] zypper addrepo - http:// vs. https://
by Per Jessen 10 Apr '18

10 Apr '18

I'm sure someone has a quick explanation: a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…' This fails: Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openS…' Works fine. (notice the extra slash between 'Virtualization:' and 'container'. c) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:containers/openSUS…' d) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:/containers/openSU…' Both work fine. -- Per Jessen, Zürich (9.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 13

[opensuse] Which distros for ReiserFS?
by Stevens 03 Apr '18

03 Apr '18

On the odd chance that I was ignored for possibly hijacking a thread, I shall start a new one but copy and paste my comments in hope of an answer: (re: Killing ReiserFS) I have been following this thread with some interest because of having been running ReiserFS since before he turned homicidal. I have had zero, count that ZERO, problems in all that time so I read with some dismay the effort to actively kill its usage in this whatever-you-call-it distro. I think that the more relevant question to ask is not "can we keep this file system around, pretty please" but "what distros are allowing its use by not actively trying to kill it"? I have used opensuse since before Mandrake went away, which has been a while and, although I don't really want to change distros, I am not married to suse (or leap, or whatever). I feel that what we have here with opensuse/leap is an example of the classic "swing" cartoon which shows the stages of project development from sales, engineering, installation and what the customer actually wanted. My need is not as complex as some and for that ReiserFS works quite well. So, my question remains, "If not suse/leap, then who"? Hopefully someone will know what distros allow the freedom to use whichever FS one wishes without running afoul of the FS nazis. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

22 99

[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

[opensuse] systemd unit file ignores minidlna default configuration
by Bob Williams 03 Jan '18

03 Jan '18

For some time I have been successfully running a minidlna server which streams music to a Bose Soundtouch device over WiFi. However, it stopped working a few weeks ago, and the SoundTouch device could only find an empty folder. After several re-writes of /etc/minidlna.conf without success, searching for other versions of minidlna.conf in non-default locations, I finally tracked the culprit down to /usr/lib/systemd/system/minidlna.service: [Unit] Description=MiniDLNA UPnP-A/V and DLNA media server After=var-run.mount nss-lookup.target network.target remote-fs.target [Service] Type=forking PIDFile=/var/run/minidlnad.pid ExecStartPre=/usr/sbin/minidlnaconfig EnvironmentFile=-/var/lib/minidlna/rescan.conf ExecStart=/usr/sbin/minidlnad $RESCAN -P /var/run/minidlnad.pid -f /var/lib/minidlna/minidlna.conf [0] [Install] WantedBy=multi-user.target So the unit file was forcing minidlna to use the configuration file in /var/lib/minidlna/minidlna.conf rather than the default /etc/minidlna.conf! /var/lib/minidlna/minidlna.conf pointed to media_dir=/mnt and was recreated at start-up, so even editing the media_dir= line didn't work. Changing line [0] to include "-f /etc/minidlna.conf" got things working again - and just in time for Christmas. ;-) I have no idea how this got changed, but I wonder if anyone else has come across anything similar? Bob -- Bob Williams System: Linux 4.4.103-36-default Distro: openSUSE 42.3 (x86_64) Desktop: KDE Frameworks: 5.32.0, Qt: 5.6.2 and Plasma: 5.8.7 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 8

[opensuse] Why is Leap 42.2 missing /usr/include/sys/random.h?? (and no getrandom in linux/random.h)
by David C. Rankin 03 Jan '18

03 Jan '18

All, getrandom() was added with the 3.17 kernel, yet Leap 42.2 does not contain a prototype in /usr/include/linux/random.h and does not include /usr/include/sys/random.h at all. Anybody know why?? -- 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 10