November 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] How smart is the 12.x installer?
by Anton Aylward 28 Nov '12

28 Nov '12

Regular readers will recall that I, like many others here, run more than one type of Linux. In particular, I run mandriva on my file server, the old Dell box under my desk. Its a good, solid machine, well engineered, even if, by todays standards, under powered. That's got to change. A replacement is on the way. But even so, initially it will run of the same disk, same mandriva. Mandriva has got to go. Its not being maintained aggressively. Mandriva 2012 Alpha came out in September, two months late. Distrowatch tells me that Alpha 2 came out earlier this month, so I can expect mandriva 2012 some time in 2013. I think I'll change. The disk in my server is large and runs LVM apart from the root partition, which includes /boot. I have no problem creating a new LVM partition that is root+/usr and using the old root partition as /boot. A 700G /boot :-) Plenty of room for all the stuff in grub2. Like Fedora and openSuse, Mandriva is a RPM based distribution. Now my question. Is the installer for openSuse 12 smart enough to a) deal with root+/usr in a LVM partition? if /boot is in the physical partition... b) recognise and preserve all the config files in the /etc in the LVM partition c) recognise all the installed applications with the "-mdv2011*" suffix and replace them with - possibly later version - openSuse equivalents? What I'm asking is 'can I do an 'upgrade' across distributions? I'd hate to do a 'rpm -q -a' on the present system and then manually make sure all the stuff was installed in the new. Googling for "linux upgrade across distributions" doesn't return a lot that seems helpful. This http://news.opensuse.org/2012/09/05/opensuse-12-2-green-means-go/ claims that the " latest release of the world’s most powerful and flexible Linux Distribution" ... Flexible? What if I just install Zypper and try to do a live update? Thoughts and suggestions, please -- Marketing is the science of convincing us that What You Get Is What You Want. -- John Carter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Big problem with mdadm and grub after update from 11.4 to 12.2
by Claudio ML 28 Nov '12

28 Nov '12

Hello all, After a DVD update from OpenSuSE 11.4 to 12.2, the system won't boot anymore. I can see now uses /dev/md125 /dev/md126 /dev/md127 (previously are /dev/md0 md1 etc.). I tryied what described here: http://lists.opensuse.org/opensuse-updates/2012-09/msg00019.html Without any success. Now i am trying to fix it, but with strange results. My actual situation is the following: mdadm --examine --scan ARRAY /dev/md127 UUID=41b65403:6ae2a15a:e25497b3:838ac1a8 ARRAY /dev/md125 UUID=8faffc2b:c1cbcd9f:40cf110f:2c33bb8a ARRAY /dev/md127 UUID=c649ac3a:7e130d44:da2c2182:96c632e9 notice the two md127 with different UUID. cat /proc/mdstat Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid1 sda1[0] sdb1[1] 1052160 blocks [2/2] [UU] md125 : active raid1 sda2[0] sdb2[1] 3148672 blocks [2/2] [UU] unused devices: <none> mount devtmpfs on /dev type devtmpfs (rw,relatime,size=503192k,nr_inodes=125798,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) /dev/md125 on / type reiserfs (rw,relatime,user_xattr,acl) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) securityfs on /sys/kernel/security type securityfs (rw,relatime) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) /dev/md125 on /var type reiserfs (rw,relatime,user_xattr,acl) tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755) md125 is mounted two times, in / and in /var.... cat /etc/fstab /dev/md126 / reiserfs acl,user_xattr 1 1 /dev/md125 /var reiserfs acl,user_xattr 1 2 /dev/md127 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 I am now a little confused, what i am missing? Help is needed.... Claudio. notice the two /dev/md126, with different UUID... Here is my mdadm --examine --scan output: -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] Need help setting up openvpn server
by Marc Chamberlin 28 Nov '12

28 Nov '12

From what I can grok about setting up and running an openvpn server, because I want to allow a Windoz client to connect to the server, I need to set up a tap and br interface and set up an ethernet bridge. I have a few questions which I don't seem to be finding answers for - 1. openvpn supplies a sample script for creating the tap and br interfaces. I know I need to modify it and run the bridge-start script before starting up the openvpn server. Also the bridge-stop script when shutting down the openvpn service. But where and how is this script incorporated into the boot up/server start up processes if I want the openvpn server to run as an automatic service? I don't see anything that references it in the /etc/openvpn/server.conf file or in the /etc/rc.d/openvpn file. 2. Within the bridge-start script there is a parameter called eth_ip that wants to be set to some IP address. Is this the IP address of the NIC that interfaces my server to my internal LAN? 3. How do I configure SuSEFirewall2 to support the tap and br interfaces? Do I just add these to the "FW_DEV_INT=" setting? (It was previously suggested that I could use the shorewall firewall instead of SuSEFirewall2, but unless SuSEFirewall2 will not support openvpn with an ethernet bridge I am reluctant to learn a whole new tool and figure out how to configure it to support this and all the other settings I currently have set/grokked in SuSEFirewall2) 4. The openvpn documentation mentions that my DCHP server cannot send the IP address of the default gateway (currently this is the IP address of the NIC on my server that interfaces to my internal LAN) but I do not see how to configure my DHCP server to differentiate between my laptop when it is connecting from my internal LAN and when it is a "roadwarrior" connecting over the VPN. My dhcpd.conf is configured to give out a static internal IP address to my laptop based on the dhcp id that the laptop sends when it is requesting a lease on the IP address that the DCHP server will assign it. I want to maintain this IP address for my laptop, regardless of whether it is connecting in from the internal LAN or over the VPN. But I do not see how to send out the "option routers" setting in the dhcpd.conf file to react differently based on how the laptop is connecting to the network. Thanks for any help/elucidation that you kind gurus can offer this poor beginner... I probably will have more questions but they can wait for now.... Marc.. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 10

[opensuse] Re: wireless access points and traditional ifup on SuSE-12.2
by Joachim Schrod 27 Nov '12

27 Nov '12

Mark Hounschell wrote: > As Per implies in the next post or so down, there appears to be a > bug but I can't tell at this point if it is in the userland side or > the kernel side? I guess I need to go ahead and look closer at the > /etc/sysconfig/network/ifup-wireless script to determine if it is > getting the $WIRELESS_AP variable from the config file and then > using it properly. This is no bug. $WIRELESS_AP is only used for Wi-fi networks with no or WEP-based authentication, i.e., configurations that can be done by calling iwconfig. That's not possible for WPA-based authentication mode. Wi-fi networks using WPA-based authentication *must* use wpa_supplicant, if you don't want to use NetworkManager. The bad message for the OP: In wpa_supplicant.conf, there is no possibility to specify an AP MAC address. wpa_supplicant associates with SSID, and roams between APs with the same SSID. See /usr/share/doc/packages/wpa_supplicant/wpa_supplicant.conf for more information. I haven't exactly understood why the OP wants to associate to a specific AP device and isn't able to use the roaming-feature within an SSID network (wpa_supplicant calls this a "network block"). Well, according to documentation, that's not possible. As the OP, I would research if MAC-based association directives for WPA-authenticated Wi-fi networks are possible with NetworkManager and, if yes, would establish a static network interface definition in NM. My 0.02 EUR, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod(a)acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] Tap devices
by Frans de Boer 26 Nov '12

26 Nov '12

Dear Reader, I would like to use OpenvSwitch + Qemu together with opensuse 12.2. I have OpenvSwitch and Qemu working correctly...as user root! The problem is neither of them above, rather it's the creation of tap devices from Userspace. I see all kinds of possible solutions, some very dated some newer, but nothing yet I believe will work from Userspace only. I have used VDE before, but had to disable the Firewall to have Internet access from the quests. OpenvSwitch is slightly faster then VDE so I would like to give that a try. Any suggestions regarding the creation of tap devices from Userspace are welcome. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] wireless access points and traditional ifup on SuSE-12.2
by Mark Hounschell 26 Nov '12

26 Nov '12

I am trying to force a desktop wireless connection to use a specific AP. I see in Yast network config where I can put the mac address of the AP I want to use but it doesn't seem to work and _most_ always picks one I don't want it to use. Using network manager obviously works correctly but I must use traditional ifup on this box. How can I force it to use the AP I want it too? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 15

[opensuse] Why is initrd needed...
by Linda Walsh 26 Nov '12

26 Nov '12

So far no one is able to explain why it is needed other than It's a fad or it's cool.. You have a 20MB RAM disc that you think you have to load and do secret things before you start my OS. I have a 12GB root disk (and RH/Fedora on their "Excuses for UsrMerge page, claims to need 400GB in root?! Talk about a broken model to be following!) Never the less, a 14 GB root with over 50% free.. and What, can't I put on my root hard disk that you have to have initrd? The drivers on my kernel are built-in. You are deliberately making people use a ram disk for no reason. Give me ANY reason. and don't say it's to mount /usr A "toy /usr/ that is not the full /usr partition lives on your ram disk in less than 20MB, I can throw away that much space in a 'dummy /usr' that the real /usr mounts over. It would be preferable to having to read all of it from disk and duplicating it 12 times for the 12 kernels I had in lilo when I last cleaned it out of initrd's that don't get used. Not only are you duplicating the space of all the utils in /usr that you need to put (ONLY because you moved them from /bin.. which if you hadn't done you wouldn't need to to copy them all to /usr). I read the /usrmerge crap... They miss a major point. If they want to merge /usr/bin with /bin, why not get rid of /usr/bin? Why not copy all of /usr/bin into /bin? But to boot do you really need 15G of /usr/share? Is /usr/games really required for boot? Do you need the complete linux source to boot in /usr/src? All of these irrelevant directories live in /usr The total of my /usr/bin, lib and lib64 (1.4G, 1.3G 3.2G) can easily live in the 9.7G free of my root. It's the rest of /usr that you are pulling along. If you want /usr/bin/lib/lib64 on root... why not just move them there? I split /usr and root because I don't need 20G of docs or fonts or source on my boot disk. Why would you claim that's the only viable answer you could come up with? Moreover, what is there on initrd that you can't put in root? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 19

[opensuse] Chromium browser has changed it's home location
by Raymond Wooninck 24 Nov '12

24 Nov '12

Dear openSUSE users, Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution. Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman. In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory. The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg. The new version 25.0.1329 is already available from Packman and should be installed automatically as that it replaces the chromium-ffmpeg package. If not, please check manually in order to get the latest version from Packman. This should be a one-time manual intervention. Regards Raymond Community Maintainer for the openSUSE Chromium package -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 16

[opensuse] chromium problem
by lynn 24 Nov '12

24 Nov '12

12.2 with YOU Hi everyone. Since I last updated I now get this message when launching chromium: 'Your profile can not be used because it is from a newer version of Chromium. Some features may be unavailable. Please specify a different profile directory or use a newer version of Chromium.' However, my profile woks fine. How should I proceed? Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] RE: Help with establishing an FTP Server
by secure domain 24 Nov '12

24 Nov '12

Could someone help walk me through the creation of an FTP Server using the GUI in YAST I hope there is a 'how to' procedure as the help text is of little value and the Global Help app in opensuse is next to useless. Here is what I dont understand in the YAST FTP Server Help Page >Umask for Anonymous: >The value that the umask for file creation is set to for anonymous users. If you want to specify >octal values, remember the "0" prefix, otherwise the value will be treated as a base 10 integer. >Umask for Authenticated Users: >The value that the umask for file creation is set to for authenticated users. If you want to specify >octal values, remember the "0" prefix, otherwise the value will be treated as a base 10 integer. I have a feeling the mask is the user UI number and I should use the user FTP, however I dont know that users password or if there is any password. >FTP Directory for Anonymous Users: >Here you can specify a directory which is used for ftp anonymous users. By pressing Browse you >can select a directory from the local filesystem. >FTP Directory for Authenticated Users: >You can specify a directory which is used for ftp authenticated users. By pressing Browse you can >select a directory from the local filesystem. I do not know what directory/file permissions are needed as far a owner/user/group/others when I do not want to use the default /srv/ftp directory. >Enable/Disable Anonymous and Local Users >Anonymous Only If enabled only anonymous logins are permitted. Authenticated Users Only If >enabled only authenticated users are permitted. Both If enabled authenticated users and >anonymous users are permitted. What is the difference between passive mode and an anonymous user found in >Enable Passive Mode >If enabled the ftp server will allow passive mode for connections All other fields I understand and in this situation upload from the FTP is not required, only write access. Thanks...BTW...IF the GUI Interface can not accomplish configuring an FTP server I need to know as we need to either remove it from Yast or fix it Thank you to all...... -- Confidentiality/Limited Liability Statement This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message, you must not disseminate, copy or take any action in reliance on it. If you have received this message in error,please notify the author immediately. Any views expressed in this message are those of the individual sender and the author accepts no liability for the content of this message except where the sender specifically states them to be the views of the author. IMPORTANT NOTE - Disclaimer: Whilst the services and the information and the facilities provided by and/or through this e-mail are provided in good faith, no representations, warranties or other promises are made in relation to the accuracy, quality, reliability or suitability of the services or the information or the facilities provided by and/or through this e-mail and you accept them and make use of them at your own risk and relieve the author from all liability (in contract, tort or otherwise whatsoever) for any loss, expense or damage suffered by you as a result of such use. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3