November 2015 - openSUSE Users - openSUSE Mailing Lists

RE: Re: [opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 27 Nov '15

27 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Andrei Borzenkov > Gesendet: Do. 26.11.2015 18:08 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Help with blind os-prober > > 26.11.2015 19:22, stakanov(a)freenet.de пишет: >>> ypted (in ext4) >> > > And you are using BIOS, no UEFI? > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- You see me smiling there. This is a 939 mainboard from 2006. I used it up to now with 13.2. At that time, suse was 9.1, Sata was 1.5 mainly, Sata II was fancy, AM2 processor the near future and I was still young and had a life. MS did not even have had the bad idea of UEFI. And the "Matrix" was on display, brand new. Just Bios. I did send you a link to the reference manual of the board so you get an idea of somewhat still good but also historical technology. The boot goes over bus mastering from a PCI controller to the mainboard BIOS. It is the BIOS of the promise controller (PCI) that handles and manages the discs. So, no, no UEFI. --- 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

2 1

[opensuse] Journalctl and rsyncd.log
by Bob Williams 27 Nov '15

27 Nov '15

Leap 42.1 with KDE5 I used to do tail -f /var/log/rsyncd.log For example: :~> tail -f /var/log/rsyncd.log 2015/11/27 12:34:40 [12582] connect from hostxx-xxx-xxx-xx.range81-157.btcentralplus.com (81.157.xx.xx) 2015/11/27 12:34:41 [12582] rsync to mixes/ from play(a)host81-157-xx-xx.range81-157.btcentralplus.com (81.157.xx.xx) 2015/11/27 12:34:41 [12582] receiving file list 2015/11/27 12:34:41 [12582] ERROR: daemon refused to receive file "group" 2015/11/27 12:34:41 [12582] ERROR: daemon refused to receive file "passwd" 2015/11/27 12:34:42 [12582] sent 328 bytes received 32,634 bytes total size 17,763,552,626 2015/11/27 12:34:42 [12584] connect from host81-157-xx-xx.range81-157.btcentralplus.com (81.157.xx.xx) 2015/11/27 12:34:43 [12584] rsync to soundtracks/ from play(a)host81-157-xx-xx.range81-157.btcentralplus.com (81.157.xx.xx) 2015/11/27 12:34:43 [12584] receiving file list 2015/11/27 12:34:44 [12584] sent 125 bytes received 28,854 bytes total size 3,605,847,084 I believe the modern way is to use journalctl but I don't get much useful output. The following was done during the same rsync session from a remote machine as the tail command quoted above: :~> journalctl -f --unit=rsyncd -- Logs begin at Tue 2015-06-02 10:09:55 BST. -- How do I use journalctl to follow the last x lines of the log? Bob -- Bob Williams System: Linux 4.1.12-1-default Distro: openSUSE 42.1 (x86_64) with KDE Development Platform: 4.14.10

3 4

[opensuse] Fingerprint reader
by Koenraad Lelong 27 Nov '15

27 Nov '15

Hi, My laptop has a fingerprint reader, and I would like to use it. It's this one : Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader I tried on previous OS versions, but then the device was not supported, although I did find this : http://lists.freedesktop.org/archives/fprint/2014-December/000658.html, which says it was supported. I was hoping Leap would support it now. I also remember that yast had a module to configure the reader but I don't find it in Leap (and neither do I in OS 13.2). So, anyone can comment on this ? Thanks, Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

Re: [opensuse] Best FS fo PostgreSQL/MariaDB
by Vojtěch Zeisek 27 Nov '15

27 Nov '15

Dne Čt 26. listopadu 2015 13:58:23 jste napsal(a): > I've also often heard people complaining that because of ACID DBs are > wearing the SSD very fast, are you concerned about that? I think this used to be case few years ago, but as far as I know, it should be alright now. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

2 2

RE: Re: [opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 27 Nov '15

27 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Neil Rickert "configfile" entries to "/etc/grub.d/40_custom". > > If you want os-prober to see your systems, you must first make them > visible with "cryptsetup". And then you must make LVM volumes visible > with "vgchange -a". If you have conflicting volume group names, that > probably won't work > > > -----Ursprüngliche Nachricht Ende----- Sometimes the little things. You see, when I had this error -4013..... I think the fact that the automated installer is using the same volume names might well be the culprit. This especially if it does not take into account on what disk it installs. That however is a bug if it is so,. Even if nowadays it will be rare that somebody does not VM when installing two instances of the same distribution but of different versions But for VM this machine is way too slow. I will do a test with a modified custom name. If it solves I can give it to the bug report, so the next time it will not happen. Neat, thank you for giving me that idea. Grateful. --- 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

2 1

[opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 26 Nov '15

26 Nov '15

Hello everybody. I tried a lot of things but I do still not understand why I face this problem. I tried to install on the same system leap and tumbleweed. This failed constantly if installing with encrypted LVM. I then tried to work around this by deactivating all sata controllers but one, I attached only one disk, the one of install. I installed leap (success). I detached the disc, attached the other HDD and installed tumbleweed. (success). Now both are there, attached to sda and sdb of the controller. Both work flawlessly if I choose with F11 to start from one disk or another. But they do not see each other in the os-prober. So I cannot get them to be bound to grub. While both have their file-system accessible to each other and can be mounted. I looked ad /boot/grub/device.map. I checked, yes, both are there. (hd0) /dev/sda (hd1) /dev/sdb you run make devicemap or os-prober: nothing. Does see ONLY the active OS at the time. Does anybody has an idea where I do have to set this in order to make os-prober to understand that there is a second OS on /dev/sdb/sdb1 on the /boot partition? Since the record by default is written also to the MBR of sdb and not only to /boot I do understand even less why it doesn't work. Again, this kind of install is the only one that does not destroy my partition tables (especially XFS of home) when trying to install two suse editionds with encrypted lvm on the same PC (one per disk) In the latter case it gives error 4013 and if it installs even as non lvm, the second installation always destroys for whatever reason the XFS partiton of the existing first disk. I did report the bug, but since with the (admittedly) crude work around I made it up to here I would like to see if it is possible to get grub2 working as it should. If not the boot manager gets not useful because I have to use the F11 all the time. Not really handy. Thanks for all hints. --- 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

4 3

[opensuse] 13.1, KDE all white for root
by Roger Oberholtzer 26 Nov '15

26 Nov '15

I have a 13.1 install issue. I will say up front that it is with an OEM install built for KIWI. But I have never seen this before in other OEM builds. And I find myself in the rotten position of needing to use this particular OEM image. After a rather straight forward install, I want to log in as root, using KDE. I get the expected login, and the little status window with icons that shows the progress of the login. I then get the initial KDE welcome window that offers to give a tour and all. But the desktop is totally white. When I close the welcome window, the white is all I have. I have tried loggin out and deleting the /root/.kde4 directory, but it makes no matter. If I add a non-root user, KDE works a charm. No problem at all. It is only the root user that this happens to. Seems if it was a permissions problem that the root user would be okay and all others have a problem. But it is the other way around. Maybe I am missing removing some other files that confuses things for root? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

RE: Re: [opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 26 Nov '15

26 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Andrei Borzenkov > Gesendet: Do. 26.11.2015 17:08 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Help with blind os-prober > > 26.11.2015 17:19, stakanov(a)freenet.de пишет: >> >> >>> -----Ursprüngliche Nachricht----- >>> Von: Andrei Borzenkov >>> Gesendet: Do. 26.11.2015 14:58 >>> An: stakanov(a)freenet.de >>> Kopie: opensuse , >>> Betreff: Re: Re: Re: Re: Re: [opensuse] Help with blind os-prober >>> >>> On Thu, Nov 26, 2015 at 4:46 PM, wrote: >>>> >>>> So I do in the CLI a LUKSOPEN /dev/sdb2 ? >>>> And then os-prober will be able to see ? >>>> >>> >>> If you use LVM on top of encrypted partition, you also need to >>> activate VG so volumes are available. If filesystem is directly on >>> encrypted container, it should work. If not, upload log again. >>> -- >>> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >>> To contact the owner, e-mail: opensuse+owner(a)opensuse.org >>> >>> >>> >>> -----Ursprüngliche Nachricht Ende----- >> I tried as follows >> > > It is. So I suggest to drop it; you will need to repeat it every time > new kernel is installed which is simply silly. > > Just create manual menu entry that launches bootloader of other > installation. Do I understand it correctly that in both OSes you have > separate unencrypted /boot partition? > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Yes this is correct. On both partitons I have /boot unencrypted (in ext4) --- 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

2 1

RE: Re: Re: Re: Re: Re: [opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 26 Nov '15

26 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Andrei Borzenkov > Gesendet: Do. 26.11.2015 14:58 > An: stakanov(a)freenet.de > Kopie: opensuse , > Betreff: Re: Re: Re: Re: Re: [opensuse] Help with blind os-prober > > On Thu, Nov 26, 2015 at 4:46 PM, wrote: >> >> So I do in the CLI a LUKSOPEN /dev/sdb2 ? >> And then os-prober will be able to see ? >> > > If you use LVM on top of encrypted partition, you also need to > activate VG so volumes are available. If filesystem is directly on > encrypted container, it should work. If not, upload log again. > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- I tried as follows: linux-xmzn:~ # vgchange -a y /dev/system 3 logical volume(s) in volume group "system" now active which leaves me with the question WHICH system he did activate. The local sda one or the sdb one. How can I distinguish that? Normally I would expect that sda (since I am at Leap now) are already activated and open. So the three are of sdb.. Or am I wrong? linux-xmzn:~ # cryptsetup luksOpen /dev/system Command requires device and mapped name as arguments. linux-xmzn:~ # cryptsetup luksOpen [hdd1] /dev/system Device [hdd1] doesn't exist or access denied. I am lost. That means that it is NOT open? Or is my syntax faulty? --- 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

2 1

RE: Re: Re: Re: Re: [opensuse] Help with "blind" os-prober
by stakanov＠freenet.de 26 Nov '15

26 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Andrei Borzenkov > Gesendet: Do. 26.11.2015 14:35 > An: stakanov(a)freenet.de > Kopie: opensuse , > Betreff: Re: Re: Re: Re: [opensuse] Help with blind os-prober > > On Thu, Nov 26, 2015 at 4:25 PM, wrote: >> encrpyted /root > > As I said, os-prober cannot probe anything inside encrypted container > unless you manually open it. > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- So I do in the CLI a LUKSOPEN /dev/sdb2 ? And then os-prober will be able to see ? --- 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

2 1