May 2018 - 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] Spec'ing a 50 TB dedicated storage subsystem and room to grow?
by Greg Freemyer 22 Feb '19

22 Feb '19

All, I bought a used iSCSI based Drobo in 2016 with 50TB in it. It works great, but it isn't fast by today's standards. (100 MB/sec absolute max). And I never got it to work from openSUSE (Windows and Mac did work). I now need to buy something similar, but with fast I/O and Linux support: 10 Gbit Ethernet and fibre-channel may be my only options? Or are there point-to-point SAS external racks I should consider? Also, I will likely want to put a SSD based cache in the mix at some point. It could be integrated into the storage subsystem, or I could use something like bcache and have the SSD be in the server,. It just needs to be reliable and fast. Recommendations? (I'm thinking used and $10K at the high-end for the subsystem including PCIx cards and switches, if needed.) == details I need to buy a server with 50TB usable disk for a production environment. A high speed disk subsystem is critical. And the project may scale up over time. It doesn't need to be a fail-over cluster, just a single server. I'm looking at used equipment most likely. I was thinking one with 4 CPU sockets would let me start with 2 CPUs and then expand to 4 later on. Lots of RAM capacity would also be great. My first thought was to get a Dell R920 and throw a bunch of disks in it. https://goo.gl/images/x3Rfj2 24 disk slots! But then I looked at what size drives are available for those slots: 2.5 inch. I only see 2TB drives max. I'm hoping to use a Dell server because it's the preferred brand at my (new) job. Unless I'm missing something a standalone rack mount Dell won't work. So, now I'm looking at a used R820 most likely and some sort of disk subsystem to support it. I picked it because it is only a 5-year old design and it has 4 CPU sockets I can expand into as the server demand increases over time. Also 3TB max ram is way above what this will require, even long term. https://media.adn.de/media/DE/DocLib/Poweredge_Easy_Matrix.pdf A used, barebones R820 can be had for under $2K. Just add CPUs and ram. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 41

[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] SuSE 42.3 on laptop?
by Markus Egg 30 Jun '18

30 Jun '18

Hello, my trustful laptop had it's final shutdown after 11 years. There are currently 2 choices for my usage (watching videos, doing 3D printing, usenet, dual ethernet). Dell Inspiron 7577 ( 256GB SSD, 1TB HDD, 16GB) Acer Aspire VX5 ( 512GB SSD + 1.000GB, 16GB) All of them are missing a DVD Writer (or even BluRay player). So which combination of USB (3.0?) Bluray player/DVD writer can I use with the above laptops to install SuSE 42.3 from DVD beside that Windows 10 (dual boot)? Also I need a 2nd Ethernet. I was using PCAMCIA/Cardbus up to now which worked fine, now I have to dump this working hardware also. :-/ Which USB-Ethernet dongles do you suggest? Is there any other better combination? Thanks in advance BR ME -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 15

[opensuse] dd to copy a partition?
by Lew Wolfgang 16 Jun '18

16 Jun '18

Hi Folks, One of my acolytes reported that she used dd to copy one disk partition to another partition on the same disk, as in: dd if=/dev/sda1 of=/dev/sda2 She said it failed, but was a little fuzzy about exactly what happened (I wasn't there), just that the destination partition appeared to be "empty" after the operation. I don't know how she made that determination. I've been doing UNIX stuff for a long time but I never would have thought to use dd in this fashion. Maybe instinct? But assuming that the two partitions are exactly the same size, what could possibly go wrong? I think she was using 42.3, probably with ext4. Definitely not btrfs, if that matters. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 12

[opensuse] Mailinglist changes going forward
by Simon Lees 14 Jun '18

14 Jun '18

Hello everyone, Firstly I am cross posting this across a number of mailinglists because this post affects several, but I would ask that you keep your replies / feedback on the openSUSE project list as not to fragment discussion. It has been raised with the board by several members of the community that some of our mailinglists have not been working as effectively as we would like. As such and as raised in our annual discussion with the community during the conference, the board has decided to take a couple of steps that we hope will resolve these issues or that will at least be a starting point in resolving these issues. Firstly we have created a new opensuse-support(a)o.o mailing list, we as the board felt that in the transition from factory -> tumbleweed in particular the change in role for opensuse(a)o.o did not work well and in many cases there was an attitude that factory/tumbleweed issues should still be posted on the factory mailing list. As such we have created the support mailing list to help clarify these changes in policy that we don't believe worked when we tried to change them last time. In short we would like you to use opensuse-support(a)o.o whenever you require support whether it is for Tumbleweed, Leap (regardless of whether you are using a Leap beta or not) or any other project under the openSUSE umbrella. This brings us to the next issue, posting bugs / bug reports on mailing lists rather then bugzilla. This is a practice we would like to see stopped and we will be gently reminding people if they continue posting bugs on mailinglists, this especially includes if a package / application breaks when updating tumbleweed / leap (including beta's). We would ask that you search for your issue prior to reporting but in case you accidentally report a duplicate bug its easy for us to mark it as such, also if you report something that is intentional and not a bug it doesn't take long to mark it as such, so if in doubt file a bug rather then posting to a mailing list, there is useful information for filing bugs at the following links [1][2]. But if you are really stuck with trying to file your bug the friendly people at opensuse-support(a)o.o can support you through the process. The board hopes that with the changes outlined above the contents of the opensuse-factory(a)o.o will go back to just being general distro development discussion so if your post to openSUSE factory is something other then that think twice about where the more appropriate place to post is. The new tumbleweed snapshots will continue to be posted to factory but we would ask you do not reply to them in order to report issues / bugs. If a bug is reported that a package maintainer believes will cause significant issues for most tumbleweed users ie not being able to boot / login or severe data loss we still invite the maintainer to post a warning to opensuse-factory but such issues happen very rarely and as such we don't expect to see many such posts. The board has decided that it would like to see how well these changes work before deciding to add / remove / change openSUSE's mailing lists further. Although we have discussed several other possibilities that we could also try in the future. 1. https://en.opensuse.org/openSUSE:Bug_reporting_FAQ 2. https://en.opensuse.org/openSUSE:Submitting_bug_reports -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

28 130

[opensuse] Alt-F2 still doesn't work for man - 15.0
by James Knott 10 Jun '18

10 Jun '18

Once again, pressing Alt-F2 and then entering #<command> does not bring up the man page. This was a very useful feature, that hasn't worked for some time. Any chance of getting it back? When I try to get a man page, at the bottom of the list of things that can be opened, there's a line that says "Locations: Go to man:/", but clicking on it opens Seamonkey. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11