October 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] separate disks
by buhorojo 01 Oct '15

01 Oct '15

Hi http://ofertaexpress.pccomponentes.com/toshiba_canvio_alu_2_5_2tb_usb_3.htm… Does anyone have experience with these for to work offline? It says windows ntfs only. I wonder if we could hack a different file system onto it. Or will our opensuse portables work ok? Also, we wonder if we upload to our google domain, does it syncronize the whole 2tb each time? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 11

[opensuse] Leap, question about smartcards with gpg. Regression?
by stakanov＠freenet.de 01 Oct '15

01 Oct '15

Hi, I wanted to ask if anybody else tried to use the cryptostick or an opensc smartcard in leap and encounters problems. I did and while I am able to get in konsole gpg --card-status as su -, I cannot get any card status in konsole as a user. As a result also gpa fails "fail to open card". Therefore it seems that in leap there is a regression with permissions. In 13.2 the same card runs flawlessly as a user. Anybody else exprienced this? In case I will have to file a bug. Cli as user: gpg --card-status gpg: selecting openpgp failed: Errore della scheda gpg: OpenPGP card not available: Errore della scheda The card is good and in su- the card gives complete output. # gpg --card-status Application ID ...: D27600012401020000050000xxxx0000 Version ..........: 2.0 Manufacturer .....: ZeitControl Serial number ....: 00001xxx Name of cardholder: [not set] Language prefs ...: de Sex ..............: male URL of public key : [not set] Login data .......: [not set] Signature PIN ....: forced Key attributes ...: 3072R 4096R 3072R Max. PIN lengths .: 32 32 32 PIN retry counter : 3 0 3 Signature counter : 4 Signature key ....: AD88 9619 0569 B313 5916 FDAE 443B 12F4 1A77 8DF8 created ....: 2015-08-30 18:03:32 Encryption key....: FC6B D738 657F 2788 86C5 B547 697A 7A51 F184 B3F1 created ....: 2015-08-30 18:00:27 Authentication key: E6A1 9CAE 7FBF E0D3 6EDB 76A7 9A74 732F 45B8 2A22 created ....: 2015-08-30 18:21:01 General key info..: [none] scdaemon[4661]: updating slot 0 status: 0x0000->0x0007 (0->1) scdaemon[4661]: scdaemon (GnuPG) 2.0.24 stopped --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Developing Leap 42.1 Info
by Douglas DeMaio 01 Oct '15

01 Oct '15

The release date for Leap 42.1 is approaching and to make this release is as successful as the last, we could sure use your help. There are several things we can do as a community to improve awareness of Leap both inside and outside of the Free and Open Source Software community. I kindly ask everyone involved with the openSUSE project to update the wiki in preparation for the release at https://en.opensuse.org/Portal:42.1. Our last release, 13.2, was very successful and it would be great if we can replicate that effort by updating the information for 42.1, so it looks similar to https://en.opensuse.org/Portal:13.2 Developers, packages maintainers and anyone else knowledgeable about what has changed in the new versions could add information to https://en.opensuse.org/openSUSE:Major_features42.1, which we can use to replace https://en.opensuse.org/Features on the day of the release. Screenshots are also important and anyone can do it! Just help replace the 13.2 screenshots on https://en.opensuse.org/Portal:42.1/Screenshots/1 page with Leap 42.1 screenshots. It will replace the https://en.opensuse.org/Screenshots page on Nov. 4 with the updated screenshots. Media - Please retweet, +1 or share all info related to the release of Leap 42.1. Test the Beta, RC1 and release and express your opinion about it. Let people know what you like about it or what could improve for Leap 42.2. Submit articles to open source media outlets, write blogs and comment articles related to openSUSE. Attend FOSS and Open Source events to help others learn about openSUSE. If you want to represent openSUSE at these events, contact me and I?ll see what marketing material I can send you. Have a lot of fun! Doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

Re: [opensuse] separate disks
by stakanov＠freenet.de 01 Oct '15

01 Oct '15

¡Hola! So I cannot tell you about google. But for all external SATA I have ever seen applies the following: The SATA interface is branched onto a card inside the box that does the communication via the USB channel. USB3.0 as HDD interface is actually worth the money if you have 3.0 or 2.1 on your PC or laptop because even in the case of 2.1 in my experience it is still faster, even if slightly. With 3.0 hdd to 3.0 PC it becomes really fast. Besides, inside is a normal HDD in standard format. So if one day it brakes and the box is still good, you can simply change the HDD. NTFS is only on it, because it is thought to work "out of the box" with people using Windows and technically not capable to format a disc. I tried several flavours on my disks: ext4, fat32, ntfs, luks encrypted ext4. All worked out of the box in Opensuse. It may be a bit more difficult to mount multiple partitions in automatic, with or without luks encryption. But it is possible, I recall having it done I do not know what google uses to synchronize. If you use rsync you will sync only the changes and you can even fine-tune what and how often you do synchronize (but you have to RTFM, intended). Hope that helps. Hasta pronto. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] FYI: WARNING: iputils is not very fresh, upgrade is recommended; bug in iputils or kernel?
by Linda Walsh 01 Oct '15

01 Oct '15

According to the comment in the iputils code: --- /* Sigh, IP_RECVERR for raw socket * was broken until 2.4.9. So, we ignore * the first error and warn on the second. */ if (once++ == 1) fprintf(stderr, "\rWARNING: kernel is not very fresh, upgrade is recommended.\n"); ---- When I first saw the error I wondered how fresh my kernel had to be to pass iputils' tests, since I'm running on: Ishtar:packages/build/iputils-s20121221> uname -a Linux Ishtar 4.1.0-Isht-Van #2 SMP PREEMPT Tue Jun 23 07:52:09 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux So I looked at code Um... why is iputils thinking that 4.1.0 < 2.4.9 -- or that 4.1.0 is older than 2.4.9? I humbly submit that 4.1.0, released in 2015 is unquestionably 'fresher' than the date on iputils of 2012. Does this mean the check in iputils is faulty w/r/t new kernels, or do new kernels have a *SERIOUS* regression? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1