March 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] [12.3 64Bit]-How To Install LibreOffice 4 ?
by Jesse Palser 13 Mar '13

13 Mar '13

Hi, Running openSUSE 12.3 64Bit and noticed LibreOffice is not version 4. How would I install LibreOffice 4 onto openSUSE 12.3 64Bit? Thanks. JeZ+Lee -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] It's inhumane......
by Basil Chupin 13 Mar '13

13 Mar '13

....and inhuman to display publicly the directory where 12.3 deltas and isos are sitting and then issue the error message "Access forbidden!" when you enter the iso directory to download the latest 12.3! :-) United Nations Commission on Human Rights should be made aware of this, I tell you :-) BC -- Using openSUSE 12.3 x86_64 with KDE 4.10.1 & kernel 3.8.2-1 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] Grub2 and installing multiple distros on same computer
by Basil Chupin 13 Mar '13

13 Mar '13

A while back I had a bit of a gripe about grub2 (vs grub) because it wasn't clear how I would be able to install other distros on my computer apart from my main openSUSE. At that time I wished that I had used grub when I installed 12.2. Well, earlier today I took the plunge and decided to create the situation whereby I could install Tumbleweed and openSUSE RC2 later today - or, if I failed, to re-install 12.2 from scratch using grub. With my heart in my mouth I started the procedure - only to find that I still had a working 12.2 but now with the ability to install more distros. In fact the whole process was "a piece of cake" so to speak. If others are contemplating doing same I recommend reading which is where I got my "inspiration" from: http://www.linuxidentity.com/us/index.php?name=CmodsDownload&file=index&req… use Okular to view it, and save it. The article is titled, "Installing Multiple Distributions on the same computer". Read this article SEVERAL+ times before doing anything. I read the article before I installed 12.2 and chose to go the Case #3 way when installing 12.2. 12.2 was installed, but then I got stuck with working out what to do next - and only found the stomach to "take the plunge" today. However, just before the end of the process I broke out in a profuse sweat because on page #16 of the article it states, "Then run the command sudo grub-mkconfig -o ..........". When doing so I got the error message that I was way up there with the fairies as the command "grub-mkconfig" is something I dreamt up after being sprinkled with Tinker Bell's pixie dust. Well, the answer was that the command should read "grub2-mkconfig". Once I found this out everything worked to its finality as expected. One more thing: go into YaST2>Bootloader and make sure that it is sited as described in the article. If not, adjust and save the changes. BC -- Using openSUSE 12.2 x86_64 KDE 4.10.00 & kernel 3.8.0-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 43

[opensuse] Upgrade openSUSE 12.3 64Bit RC2 To Final Release?
by Jesse Palser 13 Mar '13

13 Mar '13

Hi, Running openSUSE 12.3 64Bit Release Candidate 2(RC2) natively. How would I upgrade RC2 to final release? Thanks! JeZ+Lee -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] vrrpd
by Klaus Vink Slott 12 Mar '13

12 Mar '13

Hello I am struggling to make VRRPD work on a OpenSUSE 12.2. Have anybody managed to make it work? I have configured the settings in /etc/sysconfig/vrrpd so the command line resolves to: /usr/sbin/vrrpd -i eth1 -v 10 -p 100 -d 1 -n 130.225.200.10 Before I added -n my default gateway disappeared from the route table at vrrpd startup. With -n most thing seems to work. Provided that I delay vrrpd a few second after boot. Now if I kill the vrrpd demon on one machine, the other takes over as it should, and reverse takeover works as well. But if I unplug one server, resulting in a link down, - link up, then vrrpd looses its ability to take over. If I subsequently kill the other server vrrpd correctly states "we are now the master router." but the vrrpd ip does not respond to anything. Restarting vrrpd reestablishes functionality. A guru told me to set net.ipv4.ip_nonlocal_bind = 1 in /etc/sysctl.conf, but that did not seem make any difference. Any ideas? -- Regards Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] clone for autoyast is greyed out?
by Per Jessen 12 Mar '13

12 Mar '13

I'm slowly beginning to play a bit with autoyast and I noticed that the tickbox for "Clone config for auto-yast" is greyed out on the last window in phase 2 of the installation? -- Per Jessen, Zürich (6.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] no wireless on suse 12.3
by Joe Zien 12 Mar '13

12 Mar '13

I installed the latest suse 12.3 and it works fine except can't get wireless to work. Wireless works out-of-the-box in mepis 12, mint 14-kde and pclinux 2013-2, so the wirless is ok. jozien -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 6

[opensuse] GRUB2 hell
by Basil Chupin 12 Mar '13

12 Mar '13

My 2 HDDs are partitioned as follows: Device Boot Id System /dev/sda1 83 Linux /dev/sda2 82 Linux swap / Solaris /dev/sda3 83 Linux /dev/sda4 * 5 Extended /dev/sda5 83 Linux /dev/sda6 83 Linux /dev/sda7 83 Linux /dev/sda8 83 Linux /dev/sda9 7 HPFS/NTFS/exFAT Disk /dev/sdb: Device Boot Id System /dev/sdb1 * 7 HPFS/NTFS/exFAT /dev/sdb2 7 HPFS/NTFS/exFAT /dev/sdb3 83 Linux /dev/sdb4 5 Extended /dev/sdb5 83 Linux I am using grub2. On sda1 I have a common bootloader for all OSs installed. On sda3 I have openSUSE 12.2 installed. On sda5 I have openSUSE 12.3 RC2 installed. On sda6 I have Tumbleweed installed. I had kernel 3.8.1 installed on oS 12.2 and also on oS 12.3 RC2. Everything worked fine. This morning I installed kernel 3.8.2-1 on oS 12.2 (sda3) and it everything went well, No hassles. I then installed kernel 3.8.2-1 on oS 12.3 RC2 (sda5) - and now I cannot boot. All the parameters in the bootloader(s) appear to be OK except when I go to boot into "safe mode" in 12.3 (sda5) I get the error message: Invalid Magic number. What the f*** is "Invalid Magic number"?! *WHAT* number?! Of all the lame-brained, inane, stupid, meaningless error messages to have ever existed this one MUST take the cake! I think this beats whatever Windows ever managed to come with - and that's saying something. The use of "Magic Mushrooms" seems most appropriate here for whoever used "Magic number" in an error message. OK, apart from knowing what this "Magic number" may be all about, any ideas of how I can boot into oS 12.3 RC2 (sda5) just to be able to, say, tun YaST2 to get back kernel 3.8.1-2? I've tried using the Recovery mode of RC2 but I don't know how to get this to boot into sda5. I can always re-install RC2 and take it from there but there MUST be a way to recover from something like this. Does anyone know, please, what can be done to 'recover' my oS 12.3 RC2 installation? BC -- Using openSUSE 12.3 x86_64 KDE 4.10.00 & kernel 3.8.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 12

[opensuse] Root and boot partitions on a sw raid volume (opensuse 12.2 - 12.3 rc1 64bit)
by jjletho67-esus＠yahoo.it 11 Mar '13

11 Mar '13

Hi all, i'm relatively new to opensuse, but i have been using linux (red hat based distros) since ten years ago (linux is not my job however). I've done several test installations using opensuse 12.2 and 12.3 rc1 and i encountered some unexpected problems with my partition layout and i started to realize that, probably, booting from a raid volume is not a supported configuration. I've already shared my experience on the forum without finding a definitive answer https://forums.opensuse.org/english/get-technical-help-here/pre-release-bet… https://forums.opensuse.org/english/get-technical-help-here/pre-release-bet… This is the partition layout i would like to implement: /boot -> /dev/md0 (raid1) -> sda1, sdb1 swap -> /dev/md1 (raid1) -> sda2,sdb2 / -> logvol1 -> volgroup1 -> /dev/md2 -> sda3,sdb3 /home -> logvol2 ->volgroup1 -> /dev/md2 -> sda3,sdb3 /tmp -> logvol3 -> volgroup1 -> /dev/md2 -> sda3,sdb3 /var -> logvol4 -> volgroup1 -> /dev/md2 -> sda3,sdb3 /space1 -> sda4 /space2 -> sdb4 The bootloader I selected was grub2. The system i obtain using full dvd yast graphical installation is unbootable. Doing some investigation (details on the forum) i discovered that grub was installed only on the first disk and the /dev/md0 raid volume was not initialized. All the /boot files were in sdb1 and nothing was written in sda1 which is the boot device really addressed by grub2 instance installed in the sda mbr. I manually started /dev/md0 with sdb1 and then i hot added sda1. Sinchronization started and completed few seconds later ( /boot is only 500 MB large). After sync was completed a rebooted the system and grub2 was able to regularly boot the system. By this way the system can boot, but can't survive to an sda failure because gurb is missing from sdb. I did some more test and i manually installed grub2 on sdb, without touching the configuration files. The system apparently is now able to survive an sda failure a boots from sdb. So my questions are: 1) Is really this configuration unsupported by opensuse ? I'm very surprised about that because redhat based distros i used in the past support booting form raid since, at least, 2008 2) Is manually adjusting the system as i described above (manual sync and manual grub installation) a reasonably secure way to have a stable system ? I also tryed to manually create partitions, raid and lvm volume prior to start the yast installer (see my second forum thread) but i encountered an erratic and unpredictable behavior of yast which refuses to use some raid volume, seeing them as they were physical disks. Any similar experience ? I have also opened a feature request on openfate https://features.opensuse.org/314870 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] Revisit old topic: Re: Question re filesystem reserved block percent
by Linda Walsh 11 Mar '13

11 Mar '13

Lew Wolfgang wrote: > On 02/10/2013 12:43 PM, Dennis Gallien wrote: >> Advice, please . . . >> >> The default filesystem reserved blocks is 5%. IIRC that goes back a >> long time >> to when much smaller drives were in use. Is there a formula or >> rule-of-thumb >> now for today's large drives/partitions? I have quite a few 100-300GB >> partitions which I have tuned down to 3%, but it still seems I'm >> wasting a lot >> of space. Suggestions? ----------------------- > Hi Dennis, > > As I recall, the reserved blocks were used to improve read/write > performance because it makes it easier to find contiguous > blocks. Anton Aylward wrote: > Certainly not ones that use B-Tree algorithms! ----- Sorry to bring this up so long after the fact, but I wanted to add some *counter* information to the idea of *decreasing* a reserve factor. Instead of decreasing it, there are times when you might want to increase it -- it depends on *your priorities*. If you need space and don't care so much about speed, shrinking is likely the best way to go, but if you want to keep your disks running in their maximum speed range, I've noticed with 1-1.5TB partitions on a 24gB (12x2tB) RAID that free space should be kept around 20-25% and that's on a B-Tree based file system (XFS). That's because my max rate in read/write is 1TB/s, so even the smallest delays will create a much more noticeable hit in performance than they would out of 1 disk -- i.e. the computer can do many computations while the I/O controller is doing a 64K read/write on 1 disk, but the time it has to do calculations on a 12 spindle raid is a decimal order of magnitude less. So the cpu needs to search through 12X the data in 1/10th the time to maintain max I/O rates. The block allocator starts having problems finding large contiguous free spaces on file systems over 75% full, if (like me) you've gone up into the low 90's% usage, and back down. Once you've done that, you've got files spread throughout the free area. (I could rebuild the fs from scratch and that would give some more speed, until I let it get too full again). If your HD was the speed of a floppy, using it up 99%, you wouldn't notice a speed hit because the I/O was so slow, but the faster your HD subsystem, the more you'll notice the lag time caused by the block allocator and the buffering system. Many people with RAIDs have noticed a 30% or greater speed boost by avoiding the buffer cache. As long as CPU and memory speeds were staying 100-1000 times faster than disk, alot can be done to optimize I/O in memory, but with cpu speeds going down (to conserve power) and disk speeds going up with moves to SSD's and RAID's, those same algorithms won't work as well at the limits... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3