January 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Yast partioner not opening on opensuse 13.1
by Jeroen Groenewegen van der Weyden 30 Jan '14

30 Jan '14

Hello, When I try to open the yast partitioner it fail and return to the 1) opening -> yast -> system -> partitioner 2) Initializing 3) answer question with yes 4) Initializing 5) no partitioner screen is shown, return back to previous screen -> yast -> system. Journalctl -f does not give any output during this failure. I have 2 machines running opensuse 13.1, and they both behave the same. Any thoughts? BR, Jeroen **** rpm -qa output ****** yast2-packager-3.0.8-1.1.x86_64 yast2-runlevel-3.0.1-1.1.noarch yast2-backup-3.0.0-2.1.4.noarch patterns-openSUSE-kde4_yast-13.1-13.6.1.x86_64 yast2-3.0.11-7.1.x86_64 yast2-ruby-bindings-3.0.4-1.1.x86_64 yast2-apparmor-3.0.1-2.1.4.noarch yast2-users-3.0.1-2.1.4.x86_64 yast2-scanner-3.0.0-2.1.4.x86_64 yast2-tune-3.0.2-1.1.x86_64 yast2-services-manager-0.0.11-3.4.1.noarch yast2-inetd-3.0.0-2.1.4.noarch yast2-proxy-3.0.0-2.1.4.noarch yast2-printer-3.0.0-3.1.4.x86_64 yast2-pam-3.0.0-2.1.4.noarch yast2-ycp-ui-bindings-3.0.2-6.1.x86_64 yast2-samba-server-3.0.2-2.1.4.noarch yast2-branding-openSUSE-3.0.0-2.1.2.noarch yast2-online-update-3.0.0-2.1.4.noarch yast2-slp-3.0.2-1.1.x86_64 yast2-security-3.0.0-2.1.4.noarch yast2-perl-bindings-3.0.1-3.1.x86_64 yast2-vm-3.0.2-2.1.4.x86_64 yast2-iscsi-client-3.0.0-2.1.4.noarch yast2-control-center-qt-3.0.0-2.1.3.x86_64 yast2-pkg-bindings-3.0.3-8.1.x86_64 yast2-storage-3.0.8-1.1.x86_64 patterns-openSUSE-yast2_install_wf-13.1-13.6.1.x86_64 yast2-nis-client-3.0.1-2.4.3.x86_64 yast2-sysconfig-3.0.1-2.1.4.noarch yast2-samba-client-3.0.1-3.1.noarch yast2-mail-3.0.0-2.1.4.noarch yast2-nfs-common-3.0.0-2.1.4.noarch yast2-ldap-3.0.1-2.1.3.x86_64 yast2-transfer-3.0.1-2.1.3.x86_64 yast2-country-3.0.2-1.1.x86_64 yast2-theme-openSUSE-3.0.1-1.2.noarch yast2-firewall-3.0.1-2.1.4.noarch yast2-restore-3.0.0-2.1.4.noarch yast2-trans-stats-2.19.0-14.1.3.noarch yast2-x11-3.0.1-2.2.1.x86_64 yast2-core-3.0.3-1.1.x86_64 yast2-ldap-client-3.0.2-2.4.1.noarch yast2-sound-3.0.3-1.1.x86_64 yast2-network-3.0.8-5.1.x86_64 yast2-ntp-client-3.0.1-7.1.noarch yast2-theme-openSUSE-Oxygen-3.0.1-1.2.noarch yast2-qt-branding-openSUSE-13.1-10.4.13.noarch yast2-xml-3.0.0-2.1.2.x86_64 yast2-control-center-3.0.0-2.1.3.x86_64 yast2-trans-en_US-3.0.0-4.11.1.noarch patterns-openSUSE-yast2_basis-13.1-13.6.1.x86_64 autoyast2-installation-3.0.8-5.1.noarch yast2-metapackage-handler-3.0.0-2.1.4.noarch yast2-nfs-client-3.0.2-1.3.noarch yast2-country-data-3.0.2-1.1.x86_64 yast2-kerberos-client-3.0.0-2.1.4.noarch yast2-installation-3.0.8-1.1.noarch yast2-add-on-3.0.2-1.1.noarch yast2-hardware-detection-3.0.1-2.1.3.x86_64 yast2-sudo-3.0.0-2.1.4.noarch yast2-update-3.0.4-2.1.4.x86_64 yast2-bootloader-3.0.3-2.1.3.x86_64 yast2-online-update-frontend-3.0.0-2.1.4.noarch -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Anyone booting 13.1 with root on nfs?
by Per Jessen 30 Jan '14

30 Jan '14

I've upgraded a system to 13.1 and I'm having trouble getting the initrd built correctly, or such that it will boot with root on nfs. This is how I build it: mkinitrd -k vmlinuz-xen -i initrd-xen -d /dev/nfs If I don't add "-d /dev/nfs", the initrd is built without nfs and network support. However, when I boot it with: root=/dev/nfs rw nfsroot=10.1.2.3:/srv/nfs/madrid/root rootflags=hard,intr,v3,wsize=8192,rsize=8192 root is never mounted, and the startup breaks out into a shell. -- Per Jessen, Zürich (2.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 9

[opensuse] Need Linux based wifi-Security Camera Monitoring Setup Help
by David C. Rankin 30 Jan '14

30 Jan '14

Braintrust, I need to buy several wifi security cameras and install them in my office and then setup something on my server to communicate with them and store video/(possibly audio) from them. A basic security system setup. I haven't a clue what linux packages can do this and what cameras can talk to any such package. Does anyone have any experience or suggestions how to accomplish this or where a good link/howto is for something like this. I have general articles from google on cameras, etc.., but nothing regarding what works really well in a linux environment. What say the experts? -- 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

2 1

[opensuse] Strange processes owned by root
by ianseeks 29 Jan '14

29 Jan '14

Hi Does anyone know what all these processes are and if they are symptoms of an error somewhere? regards Ian 7 root rt 0 0 0 0 S 0.000 0.000 0:00.01 migration/0 8 root -2 0 0 0 0 S 0.000 0.000 0:00.00 rcuc/0 9 root -2 0 0 0 0 S 0.000 0.000 0:00.00 rcub/0 10 root 20 0 0 0 0 S 0.000 0.000 0:06.58 rcu_preempt 11 root 20 0 0 0 0 S 0.000 0.000 0:04.82 rcuop/0 12 root 20 0 0 0 0 S 0.000 0.000 0:08.04 rcuop/1 13 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/2 14 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/3 15 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/4 16 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/5 17 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/6 18 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuop/7 19 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcu_bh 20 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/0 21 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/1 22 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/2 23 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/3 24 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/4 25 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/5 26 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/6 27 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuob/7 28 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcu_sched 29 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/0 30 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/1 31 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/2 32 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/3 33 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/4 34 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/5 35 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/6 36 root 20 0 0 0 0 S 0.000 0.000 0:00.00 rcuos/7 37 root rt 0 0 0 0 S 0.000 0.000 0:00.14 watchdog/0 38 root rt 0 0 0 0 S 0.000 0.000 0:00.13 watchdog/1 39 root -2 0 0 0 0 S 0.000 0.000 0:00.00 rcuc/1 40 root rt 0 0 0 0 S 0.000 0.000 0:00.01 migration/1 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] How to add an older repository ..............
by Duaine Hechler 29 Jan '14

29 Jan '14

How do I add an older repository without screwing things up ? I need the old libicu .... 46 from 12.1 OSS. Do I add it then set priority lower than 99 - say 50 ? Thanks, Duaine -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] [long story] HP server/NIC/router/gateway frustration
by Felix Miata 29 Jan '14

29 Jan '14

Internet friend Georg from 4,000 miles away bought a house near me. He subscribed to cable, installed an internet router, and installed a Logitech camera system so that he could monitor his house here from his distant home. That system continues to work via the Logitech module plugged into a router LAN port. Later he bought a HP Windows 2011 server puter with no OM drive to use for remote desktop so that he could pay bills from local utility systems whose archaic billing systems do not accept international payments in sensible fashion electronically. Remote desktop was supposed to solve the problem by making the transactions look local, created via online banking with a bank located across the street from the utility. RDP worked for a time, but stopped when the HP became unable to access the internet. I brought his HP here to troubleshoot. The problem appeared on the basis of its lights not lighting up when a cable is plugged into it to be the onboard NIC died, probably as a result of our area's infamous power outages hitting his unprotected-by-UPS HP. I had no NIC to test with because his HP has no PCI slots and I had only PCI NIC spares to test with. Hoping for a minimal likelihood of compatibility issues I ordered and installed http://www.newegg.com/Product/Product.aspx?Item=N82E16833106033 . With it installed and the HP plugged into my LAN everything appeared to be copasetic with regard to the HP, though leaving it on long enough for Windows to do updates left my Samba dysfunctional for more than 24 hours while I tried to figure out what went wrong and how to fix it[1]. When I took the HP back to its home, it still refused to see the internet. Blinking router lights on unconnected ports made me think the router had been damaged at the same time as the NIC. Not wanting to disturb continued function of the camera system, I quit trying and brought the HP back here, then ordered Georg's choice of new router, D-Link DIR-655. The new router like most consumer products nowadays comes with no paper manual, just a short quick start sheet. A PDF manual comes on a CD with a Windows driver and Windows installation Wizard utility that in big black letters on an big orange sticker on the router says must do first. Of course this is not possible because I have no OM USB device to read the CD, and his HP has no OM drive to read it either. I called D-Link support to report the media type problem, and complain about the upside down ethernet ports and port labels underneath the ports instead of above where they would be visible. I was told by machine the wait queue was 11+ minutes. 64 minutes later after no further response I hung up. I've never bought D-Link before. I'll never buy D-Link again. I tried testing it all here sans manual by plugging the new router into my router via the same cable normally used for my test puters, with the brand new router's new ethernet cable connecting new NIC to router port 4. On first try, no luck, no NIC lights. I removed the new cable from the NIC, and plugged one of my cables into the NIC and router port 2. Wired thus, router chained to router, it enabled Firefox to reach the internet, and the new router's setup utility page. I proceeded through the router's initial setup "wizard", setting a name and password for wireless. At the end of that process the router purposefully rebooted itself. Since that reboot, nothing I do makes the exclamation mark leave the Windows network function icon, or the new router's light for that port stop blinking. FF cannot reach the internet. I shut the HP down, then plugged one of my (multiboot) openSUSE systems into the new router using my own same cable. I first tried 12.1. It too could not reach internet (no response to ping www.google.com). This made me think my first try at chaining the two routers succeeding was either a fluke, or something via running the new router's wizard was blocked/canceled/destroyed. So my plan is now to figure out how to get openSUSE to see the internet through both routers. Once that's done, I'll need to make a live Linux USB stick (that's been waiting for an available round tuit for many moons), and ensure that whatever I got to work on my own system will work reliably on the HP, possibly with its old NIC. As another option alternative to USB, I could temporarily remove the HP HD (a quick and easy process) and put in one of my own with openSUSE already configured for Intel CPU and HD controller. Once I know I have the HP working reliably with live Linux or my own HD, I can then see about getting Windows to do as well. Then once that's done I can try taking the HP and new router to Georg's house. So, step next: get any openSUSE from 11.4 up through 13.2 to reach the internet through both routers. Is there something special that needs to be done WRT routing or DNS setup for such a router configuration to succeed? Anything else I'm missing? [1] http://lists.opensuse.org/opensuse/2014-01/msg00943.html Additionally, every time the HP connects to``````` my LAN, my own router changes the HTTP port assignment from where it belongs for running Apache to the IP assigned via DHCP address to the HP. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Temp directories NOT cleared at boot (oS13.1)
by Dylan 28 Jan '14

28 Jan '14

Hi I was doing some general HD housekeeping recently, and found several hundred old and irrelevant files scattered through the directories under /tmp. This was surprising, since I have the "clear temp directories on boot" option set to "yes" in the YaST sysconfig editor module. Is this no longer the 'correct' method to cleat the temp directories? How should I make sure that these directories do not become overloaded with redundant files in future? Thanks Dylan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 36

[opensuse] EOL of openSUSE 12.1 in 12.2
by Bjoern Voigt 28 Jan '14

28 Jan '14

Hello, there is a funny bug in updated package release-notes-openSUSE-12.2.9-1.16.3.noarch from openSUSE 12.2. It announces the EOL of the previous version 12.1: rpm -q --scripts release-notes-openSUSE-12.2.9-1.16.3.noarch preinstall scriptlet (using /bin/sh): echo "This announcement marks the end of the maintenance period for openSUSE 12.1. [...] I filed the bug as https://bugzilla.novell.com/show_bug.cgi?id=860830 Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Spamassassin and Thunderbird
by Bob Williams 28 Jan '14

28 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Long. long ago in a galaxy faraway, I used to use Spamassassin in association with Kmail, configured using the built-in setup wizard. Several years ago, I switched from Kmail to Thunderbird for email collection, but I just noticed that spamd still starts up automatically on this machine. I've also started getting more spam here recently (must be getting through my ISPs filters) and that started me wondering if it was possible to route my incoming mail through spamassassin before it gets to Thunderbird. I collect my mail from an IMAP account 'out there'. Do I have to setup my own local IMAP server, or can Thunderbird be configured somehow? See my sig for system information. Thanks, Bob - -- Bob Williams System: Linux 3.11.6-4-desktop Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.12.1 Uptime: 12:00pm up 1 day 20:56, 3 users, load average: 0.23, 0.21, 0.22 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLepMsACgkQ0Sr7eZJrmU5WngCfX2FSh+o4g4fVn3ZHndk6KB6B d2EAnA3cIF18PfVvZq3ss2EfjSDUJjoT =pHD+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Installing openSUSE 13.1 alongside OEM Windows 8.1 with Intel Rapid Storage
by Pablo Dotro 28 Jan '14

28 Jan '14

Greetings All! I just bought a new ultrabook. It came with a 500Gb HDD and a 32 Gb SSD. It is configured as a RAID0 array, and is being used at the moment by the preinstalled Windows 8.1 (8 originally, it upgraded itself). Windows is set to use "Intel Rapid Storage Technology" and "Intel Rapid Start Technology". As far as I know, this is a software raid technique to use the SSD as a cache for the standard disk, improving speed and response time of windows applications. It is not true hardware raid, but "fakeraid", firmware based. When I try to install openSUSE (from the KDE liveDVD), I get a message indicating that there are partitions on a raid setup,but when I get to the partitioning part of YAST, I do not see them listed. I am clueless about the underlying technology (RAID, rapid start/rapid storage), this is my first notebook with this type of configuration. I tried googling for an answer, but while I found some data about creating RAID sets, and installing from scratch (i.e. without Windows), I have not found a way to set up openSUSE alongside Windows 8.1 in a multiboot configuration in a stable fashion. Disabling Intel Rapid Storage and setting the SATA subsystem to AHCI results in a broken Windows, so I have to keep it working. Is it possible? Any help is appreciated. Best regards, Pablo -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1