using …

Pure C#

Mart, 2009 için Arşiv

parted

Yazan: esersahin 28/03/2009

NAME
GNU Parted – a partition manipulation program

SYNOPSIS
parted [options] [device [command [options...]…]]

DESCRIPTION
parted  is  a disk partitioning and partition resizing program.  It allows you to create, destroy, resize, move and copy ext2, ext3, linux-swap, FAT, FAT32, and reiserfs partitions.  It can create, resize, and move Macintosh
HFS partitions, as well as detect jfs, ntfs, ufs, and xfs partitions.  It is useful for creating space for new operating systems, reorganising disk usage, and copying data to new hard disks.

This manual page documents parted briefly.  Complete documentation is distributed with the package in GNU Info format; see near the bottom.

OPTIONS
-h, –help
displays a help message

-i, –interactive
prompts for user intervention

-l, –list
lists partition layout on all block devices

-m, –machine
displays machine parseable output

-s, –script
never prompts for user intervention

-v, –version
displays the version

Yazı kategorisi: Linux | » yorum bırak;

fdisk

Yazan: esersahin 28/03/2009

NAME
fdisk – Partition table manipulator for Linux

SYNOPSIS
fdisk [-u] [-b sectorsize] [-C cyls] [-H heads] [-S sects] device

fdisk -l [-u] [device ...]

fdisk -s partition …

fdisk -v

DESCRIPTION
Hard disks can be divided into one or more logical disks called partitions.  This division is described in the partition table found in sector 0 of the disk.

In the BSD world one talks about `disk slices’ and a `disklabel’.

Linux needs at least one partition, namely for its root file system.  It can use swap files and/or swap partitions, but the latter are more efficient. So, usually one will want a second Linux partition dedicated as swap par-
tition.  On Intel compatible hardware, the BIOS that boots the system can often only access the first 1024 cylinders of the disk.  For this reason people with large disks often create a third partition, just a few MB  large,
typically mounted on /boot, to store the kernel image and a few auxiliary files needed at boot time, so as to make sure that this stuff is accessible to the BIOS.  There may be reasons of security, ease of administration and
backup, or testing, to use more than the minimum number of partitions.

fdisk (in the first form of invocation) is a menu driven program for creation and manipulation of partition tables.  It understands DOS type partition tables and BSD or SUN type disklabels.

fdisk doesn’t understand GUID Partition Table (GPT) and it is not designed for large partitions. In particular case use more advanced GNU parted(8).

The device is usually one of the following:
/dev/hda
/dev/hdb
/dev/sda
/dev/sdb
(/dev/hd[a-h] for IDE disks, /dev/sd[a-p] for SCSI disks, /dev/ed[a-d] for ESDI disks, /dev/xd[ab] for XT disks).  A device name refers to the entire disk.
OPTIONS
-b sectorsize
Specify the sector size of the disk. Valid values are 512, 1024, or 2048.  (Recent kernels know the sector size. Use this only on old kernels or to override the kernel’s ideas.)

-C cyls
Specify the number of cylinders of the disk.  I have no idea why anybody would want to do so.

-H heads
Specify the number of heads of the disk. (Not the physical number, of course, but the number used for partition tables.)  Reasonable values are 255 and 16.

-S sects
Specify the number of sectors per track of the disk.  (Not the physical number, of course, but the number used for partition tables.)  A reasonable value is 63.

-l     List the partition tables for the specified devices and then exit.  If no devices are given, those mentioned in /proc/partitions (if that exists) are used.

-u     When listing partition tables, give sizes in sectors instead of cylinders.

-s partition
The size of the partition (in blocks) is printed on the standard output.

-v     Print version number of fdisk program and exit.

Yazı kategorisi: Linux | » yorum bırak;

su

Yazan: esersahin 28/03/2009

NAME
su – run a shell with substitute user and group IDs

SYNOPSIS
su [OPTION]… [-] [USER [ARG]…]

DESCRIPTION
Change the effective user id and group id to that of USER.

-, -l, –login
make the shell a login shell

-c, –command=COMMAND
pass a single COMMAND to the shell with -c

-f, –fast
pass -f to the shell (for csh or tcsh)

-m, –preserve-environment
do not reset environment variables

-p     same as -m

-s, –shell=SHELL
run SHELL if /etc/shells allows it

–help display this help and exit

–version
output version information and exit

A mere – implies -l.   If USER not given, assume root.

AUTHOR
Written by David MacKenzie.

REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.

COPYRIGHT
Copyright © 2008 Free Software Foundation, Inc.  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.  There is NO WARRANTY, to the extent permitted by law.

Yazı kategorisi: Linux | » yorum bırak;

uname

Yazan: esersahin 28/03/2009

NAME
     uname - print name of current system

SYNOPSIS
     uname [-aimnprsvX]

     uname [-S system_name]

DESCRIPTION
     The uname utility prints information about the current  sys-
     tem on the standard output. When options are specified, sym-
     bols representing one or more system characteristics will be
     written to the standard output. If no options are specified,
     uname  prints  the  current  operating  system's  name.  The
     options  print  selected  information  returned by uname(2)
     sysinfo(2), or both.

OPTIONS
     The following options are supported:

     -a              Prints basic information currently available
                     from the system.

     -i              Prints the name of the platform.

     -m              Prints the machine  hardware  name  (class).
                     Use of this option is discouraged. Use uname
                     -p instead. See NOTES section below.

     -n              Prints the nodename  (the  nodename  is  the
                     name  by which the system is known to a com-
                     munications network).

     -p              Prints the current host's ISA  or  processor
                     type.

     -r              Prints the operating system release level.

     -s              Prints the name  of  the  operating  system.
                     This is the default.

Yazı kategorisi: Linux | » yorum bırak;

Setting up VMware Workstation

Yazan: esersahin 28/03/2009

http://en.opensuse.org/Setting_up_VMware_Workstation

Contents

[hide]

if (window.showTocToggle) { var tocShowText = “show”; var tocHideText = “hide”; showTocToggle(); }

Introduction

VMware Workstation is a very popular proprietary virtual machine suite. There are other alternatives such as VirtualBox and QEMU (both open source software) which, unfortunately, are not as a feature rich as a VMware Workstation.

This article explains how to install VMware Workstation 6.5.0 on openSUSE 11.0 and 11.1 beta 5. It may work on older/newer versions.

Installing required packages

Before beginning the installation of VMware Workstation 6.5.0, you have to install the following packages:

  • gcc
  • make
  • kernel-source
  • kernel-syms
  • linux-kernel-headers (this is probably already installed)

There are different ways of installing packages on openSUSE. For instance, you can use YaST or zypper.

Using YaST

Go to YaST -> Software Management. Search for the packages you need (one at a time) and select them by clicking on the checkbox.

Using zypper

Open the terminal, type the following as the root user:

zypper in gcc make kernel-source kernel-syms linux-kernel-headers

Starting the VMware installer

Once you have installed the aforementioned packages, you can proceed to run the installer. Before doing so, make it executable;

Note: this is an example, replace the version number with the one you have.

chmod +x VMware-Workstation-6.5.0-118166.i386.bundle

Then type (as root):

./VMware-Workstation-6.5.0-118166.i386.bundle

Running VMware Workstation

To run VMware Workstation on openSUSE, you can either click on the VMware Workstation icon or run it from a terminal.

from a Menu entry

There are two ways of doing running VMware Workstation from a menu entry;

  • Click on the lizard, type vmware and click on VMware Workstation

OR

  • go to lizard -> Applications -> System -> More Programs -> VMware Workstation

from a Terminal

Open a terminal and type

vmware

See Also

Yazı kategorisi: Linux, OpenSuse, VMware | » yorum bırak;

Setting up SUSE Linux as a VMware Guest

Yazan: esersahin 28/03/2009

http://en.opensuse.org/Setting_up_SUSE_Linux_as_a_VMware_Guest

Installing SUSE Linux as a VMware Workstation guest operating system is mostly easy. However, certain aspects of the process, such as setting up VMware Tools, may be somewhat unintuitive. This page is intended to help you make your SUSE Linux guest operating system work as smoothly as possible.

Note: Since SUSE 11.0, an open source version of VMware tools (vmware-kmp) is installed by default if you install the system inside VMware.

Contents

[hide]

if (window.showTocToggle) { var tocShowText = “show”; var tocHideText = “hide”; showTocToggle(); }

Creating the VMware Virtual Machine for SUSE Linux

This section should explain the optimal settings for running SUSE Linux as a guest.

Installing SUSE Linux in a VMware Virtual Machine

This section should document only the highlevel steps, and then refer to the normal setup instructions for SUSE Linux. We’ll get to this later, since it’s the easiest part.

There are some good screenshots of installing RC1 and RC2 into VMware 5.5 here.

Set Up VMware Tools on a SUSE Linux Guest

Install the Packages Required for Building Kernel Modules

On the guest SUSE Linux system. install the following packages. The Software Management tool in YaST makes this easy to do.

  • binutils
  • gcc
  • gcc-c++
  • kernel-source
  • make

Make sure that your Kernel is up to date.

Your kernel version must match the version of the kernel-source packages. To know which version of the kernel you are running, type:

uname -a

in a terminal window.

When you select the kernel version in yast2, click on the “Version” tab, and make sure that you are installing the same version that matches your running kernel. The defaults version downloaded is sometimes incorrect.

Install the VMware Tools Package

1. In the VMware Workstation console, click on the VM menu, then select Install VMware Tools.

  • If you have multiple workstations installed, make sure that you have switched to the tab for the workstation in which you want to install the VMware Tools.

Your SUSE Linux guest system should have mounted a (virtual) CD, which will appear on the guest system’s desktop.

2. In the guest system, double-click the CD on the desktop to open it in the file manager.

3. Do not use the RPM package to install VMware tools, the package contains dependencies to kernel modules which will overwrite your currently installed kernel.

4. Right click on VMwareTools-6.0.2-59824.tar.gz archive and extract it into into /tmp/VMwareTools.

Run the VMware Tools configuration script

http://www.vmware.com/support/ws55/doc/ws_newguest_tools_linux.html

1. Open a terminal as root and configure VMware Tools by running:

su
cd /tmp/VMwareTools/vmware-tools-distrib
./vmware-install.pl

2. Respond to the questions the installer displays on the screen. Press Enter to accept the default value. Note: Be sure to respond yes when the installer offers to run the configuration program.

3. To launch the VMware Tools background application:

vmware-toolbox &

Note: Some guest operating systems require a reboot for full functionality.

Troubleshooting the VMware tools configuration script

While running the configuration script, you may encounter an error similar to this one while trying to build some of the VMware tools:

The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.18.2-34-default). Even if the module were to compile successfully, it would not load into the running kernel.

One possible reason for this is that the version of the kernel-source downloaded in the previous step did not match the version of your running kernel. Go back into yast2, search for “kernel-source”, click on the “versions” tab, and select the currently running version of the kernel from the selection of radio boxes.

Another possible reason for this is because some kernel header configurations in the default header directory do not include the file utsrelease.h, which specifies the release version. The folder that contains the correct version information should look like this:

/usr/src/linux-obj/i386/<version name>/include/linux

You should find the folder that matches your version’s name, and enter that path at the prompt.

If you try to install the vmware-tools from ESX3, it’s possible that the vmware-config-tools script fails to compile the modules with an error about a missing config.h (depends of the version)

Use the following patches+instructions to fix this: http://www.astroarch.com/virtual/patches.html

Tips & Tricks

Switching between sessions on the guest system

  • The normal Ctrl-Alt-F1 or Ctrl-Alt-F2 keys do not work on a guest system. (If your VMware host is Linux, they will actually do their normal function on the host OS.)
  • Hold Ctrl+Alt and hit Space and then F1 (or Fn) without releasing Ctrl+Alt. This will invoke the Ctrl-Alt-F1 on the guest OS.

Yazı kategorisi: Linux, OpenSuse, VMware | » yorum bırak;

VMware İş İstasyonunu Bir Çekirdek Güncellemesinden Sonra Düzeltme

Yazan: esersahin 28/03/2009

http://tr.opensuse.org/VMware_%C4%B0%C5%9F_%C4%B0stasyonunu_Bir_%C3%87ekirdek_G%C3%BCncellemesinden_Sonra_D%C3%BCzeltme

Çekirdek güncellemeleri çalışan önceki bir VMware İş İstasyonu kurulumunu bozacaktır. Bu, VMware çekirdek birimleri belirli bir çekirdek sürümü için yapılmış olmasından kaynaklanır. VWware İş İstasyonları’nı kurtarma adımları aşağıdaki gibidir.
Eğer SUSE Linux 10.0′da VMware kurmak için vmware-any-any update kullanmadıysanız, lütfen Setting up VMware on SUSE Linux‘e başvurun.

Contents

[hide]

if (window.showTocToggle) { var tocShowText = “show”; var tocHideText = “hide”; showTocToggle(); }

Çekirdek Güncellemesinden Kaynaklanan Bozuklukların Belirtileri

  • VMware İş istasyonu uygulaması başlatıcıdan başlamayacaktır.
  • VMware İş İstasyonu uygulaması onu terminal penceresinden vmware komutunu kullanarak başlattığınızda şu hatayı verir :
   vmware is installed, but it has not been (correctly) configured
   for this system. To (re-)configure it, invoke the following command:
   /usr/bin/vmware-config.pl.
  • VMware İş İstasyonu aygıt desteği çalışmayı durdurur, özellikle köprü ağ çalışmasını.
  • Ön yükleme sırasında, sistem başlangıç ayrıntıları VMware çekirdek biriminin yüklemede başarısız olduğunu gösterir. (gereksiz sözlerle dolu ön yükleme ekranını görmek için, yükleme ilerleme ekranınından çıkış (escape) basın)
   Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0                                   failed
   Host-only networking on /dev/vmnet1 (background)                    done
   Bridged networking on /dev/vmnet2                                   failed
   Host-only networking on /dev/vmnet8 (background)                    done
   NAT service on /dev/vmnet8                                          failed

VMware İş İstasyonunu Düzeltme Adımları

Çekirdek Birimlerini Yeniden Yapmak için Çekirdeği Hazırlama

1. Bir Terminal Penceresi açın

2. Kaynak olmak için su kullanın

3. /usr/src/linux dizinine geçin ve şu komutu çalıştırın:

make cloneconfig

4. Aşağıdaki komutu çalıştırın:

make modules_prepare

VMware İş İstasyonunu Yeniden Yapılandırma

  • VMware İş İstasyonu kurucu RPM’i yeniden uygulmanız gerekmez.
  • vmware-any-any den runme.pl betiğini çalıştırmanız gerekmez

1. Bir Terminal penceresi açın. (Yukarıda açtığınız aynı terminal oturumunu kullanabilirsiniz.)

2. Kaynak (root) olmak için su kullanın. (Yukarıdaki terminal oturumunu kullanıyorsanız, zaten kaynaksınızdır.)

3. VMware yapılandırma betiğini çalıştırın (/usr/bin/vmware-config.pl) ve birimleriniz oluşturmak için istenenleri izleyin.

4. Sonraki adımda, önceki ağ yapılandırmalarınızı korumak için “evet” yanıtı verin.

   You have already setup networking.

   Would you like to skip networking setup and keep your old settings as they are?
   (yes/no) [no] yes

Öneriler ve İpuçları

Adımları Tek Bir Komutta Birleştirmek

Ana çekirdeğin güncellenmesinden doğan VMware bozukluklarını giderme konusunda güven kazandıktan sonra, aşağıdaki komutu bir çok komutu tek bir sürece indirgemek için kullanabilirsiniz :

   # su -c "cd /usr/src/linux && make cloneconfig && make modules_prepare && vmware-config.pl --compile"

Komut satırını deşifre etmek:

  • su -c geçiçi olarak kaynağa geçer ve kotalar içindeki komutları çıkarır.
  • make cloneconfig , çalışan çekirdekten güncel yapılanmayı /proc/config.gz’dan dosya sistemine yazar.
  • make modules_prepare çekirdek birim bağımlılıklarını hazırlar
  • vmware-config.pl --compile VMware yapılandırma betiğini başlatır ve gereken birimlerin derlenmesine zorlar.

Sorun Giderme

“Kaynak Kurulumlarınız Arızalı”

  • Belirti: VMware çekirdek birimlerini yeniden derlemeye çalıştığınızda, aşağıdaki hata çıkışını alırsınız:
   VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
   *** Your sources installation is broken:
   *** /usr/src/linux/include/.. does not contain .config file
   *** vmmon/vmnet build may fail, or built vmmon/vmnet may crash.

   *** Hit ENTER to continue, or ^C to stop build.
  • Derleyici çekirdek kaynağınızın çekirdek sürümünüzle uyumlu olmadığını öne sürer.
  • Çözüm
    • Büyük olasılıkla, make cloneconfig ve make modules_prepare için adımları atladınız. vmware-config.pl çalıştırmadan önce bunları çalıştırmanız gerekir.
    • Gerçekte, çekirdek ve kaynak sürümleri arasında uyumsuzluk olması da mümkündür. Bu paket sürümlerinin şunları karşıladığından emin olun:
        • kernel-default
        • kernel-source
        • kernel-syms

Derleme Halen Tamamlanmadı

  • Belirti: Tüm gerekli adımları yerine getirdiniz, ama hala derleme hatası alıyorsunuz. Saçınız dökülüyor ve kanlanan gözleriniz şişiyor..
    • Çekirdek-Güncellemeleri eski çekirdek sürümünü temel alan .config dosyalarının arkasından gider. vmware-config.pl çalıştırdığınızda bu sorun yaratabilir.
  • Çözüm: Bir terminal açın, kaynak (root)a geçin, /usr/src/linux’a çevirin, ve tüm eski yapılandırmaları ve hala daha eski çekirdek sürümlerine giden nesne dosyalarını temizlemek için make mrproper çalıştırın. (Temel olarak, bu özgün yerinde tüm Çekirdek Kaynak Ağacı’nı sıfırlar).Tamamlandığında, yeniden vmware-config.pl betiğini kullanmayı deneyin.

Ayrıca Bakınız


VMware-Documentation: Setting up VMware on SUSE LinuxUninstalling VMware from SUSE LinuxRecovering VMware Workstation After a Kernel UpdateInstalling SUSE Linux 9.0 as a VMware guestInstalling SUSE Linux 9.1 as a VMware guest

tr:Şablon:VMware

Yazı kategorisi: Linux, OpenSuse, VMware | » yorum bırak;

GNOME 2.26 Released – openSUSE 11.1

Yazan: esersahin 28/03/2009

http://www.benkevan.com/blog/gnome-226-released-opensuse-111/

The GNOME Project has announced the release of GNOME 2.26. Here’s some information from gnome.org:

Introduction to GNOME
GNOME 2.26 is the latest version of the GNOME Desktop: a popular, multi-platform desktop environment for your computer. GNOME’s focus is ease of use, stability, and first class internationalisation and accessibility support. GNOME is Free and Open Source Software and provides all of the common tools computer users expect of a modern computing environment, such as e-mail, groupware, web browsing, file management, multimedia, and games. Furthermore, GNOME provides a flexible and powerful platform for software developers, both on the desktop and in mobile applications.

GNOME 2.26
Figure 1 GNOME 2.26

The GNOME Desktop is released every six months and contains many new features, improvements, bug fixes, and translations. GNOME 2.26 continues this tradition. To learn more about GNOME and the qualities that distinguish it from other computer desktop environments (such as usability, accessibility, internationalisation, and freedom) visit the About GNOME page on our website.

Here’s some information they have which is more directed towards the 2.26 release:
The GNOME Project’s focus on users and usability continues in GNOME 2.26 with its hundreds of bug fixes and user-requested improvements. The sheer number of enhancements makes it impossible to list every change and improvement made, but these notes aim to highlight some of the more exciting, user-oriented features in this release.

* 2.1. Comprehensive New Disc Burning
* 2.2. Simpler File Sharing
* 2.3. Evolution Evolves its Migration from Windows
* 2.4. Media Player Improvements
* 2.5. Volume Control Integrated with PulseAudio
* 2.6. Support for multiple monitors and projectors
* 2.7. Almost Telepathic Communication
* 2.8. Location Epiphany
* 2.9. Fingerprint Reader Integration

There is a bunch more information and details on the GNOME 2.26 Release Notes page.

The build service repository for GNOME Factory now includes the said 2.26 packages (I haven’t installed as I am a KDE user, but after seeing some changes in GTK (they actually have progress bars and icons in widgits.. about time) I may have to give it more thought (the nm-applet also has TLS-EAP capabilities, which KNetworkManager lacks).

The repository for GNOME 2.26 is:
http://download.opensuse.org/repositories/GNOME:/Factory/openSUSE_11.1/

You must also add the backport repository:
http://download.opensuse.org/repositories/GNOME:/Backports/openSUSE_11.1/

You can set the repository up by running:

sudo zypper ar http://download.opensuse.org/repositories/GNOME:/Factory/openSUSE_11.1/ GNOME\ Factory && sudo zypper ar http://download.opensuse.org/repositories/GNOME:/Backports/openSUSE_11.1/ GNOME\ Backport

You can set it to autorefresh by doing:

sudo zypper mr -r GNOME\ Factory && sudo zypper mr -r GNOME\ Backport

You can then update doing:

sudo zypper up -t package -r GNOME\ Factory -y && sudo zypper up -t package -r GNOME\ Backport

Also, there is an X Bug that will cause your CPU to go to 100%. If you experience this setup the following repository:
http://download.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/

Add, and update with:

sudo zypper ar http://download.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ Magnus\ Home && sudo zypper up -t package -r Magnus\ Home

Make sure you thank:
Iznogood
Bryen Yunashko
Magnus Boman

For bringing up the important updates to the CPU bug and backports.

I have not tested the packages on the factory repository, and you should be aware that this is from a FACTORY repository, which is the area for the next release of openSUSE (which will be 11.2). I mustsay.. I may actually give this GNOME a shot.. so I’ll report back later..

  1. March 21st, 2009 at 11:26 | #1
  2. March 21st, 2009 at 17:01 | #2

    Iznogood is correct in listing the additional repositories required when using GNOME:Factory.

    The GNOME:Factory version of 2.26 is running swell on most of our desktops. Naturally there’s a few bugs here and there which those of us on the GNOME Team are identifying and rectifying.

    I would encourage users to wait a few more days until GNOME:Stable repository is done populating from :Factory. Or they’ll end up getting updates to the next factory version of GNOME which may be quite unstable. :-)

  3. March 21st, 2009 at 22:54 | #3

    Thanks Ben for that. I would appreciate if you could update it to reflect what Iznogood said though. It is important :-)

  4. March 22nd, 2009 at 06:59 | #4

    Iznogood, Bryen and Magnus.. Thanks for the updates.. I’ve added.

Yazı kategorisi: Linux, OpenSuse | » yorum bırak;

Amarok 2.0.2 Release – One step closer to perfection

Yazan: esersahin 28/03/2009

http://www.benkevan.com/blog/amarok-202-release-one-step-closer-to-perfection/

Since the code shift from KDE 3 to KDE 4, many KDE and KDE Application Developers endured lots of hate, unjust bias and down right mean reviews.

However, those comments sure haven’t gotten the Amarok team down as they blast away with another awesome release of Amarok. Amarok 2.0.2 has the following Changes and Major Bugfixes:

Changes
*Show a statusbar message when loving a lastfm track.
*Show error message when Wikipedia information cannot be retrieved.

Bugfixes
*Fix showing of book information from the LibriVox service.
*Don’t crash if a script has uncaught exceptions.
*Open ogg files in Amarok when using Dolphin and other file managers. *Patch thanks to Lubos Lunak . (BR 180155)
*Fix podcast episodes not ordered right because of incorrect parsing of pubdate. (BR 181338)
*Fix crash in tagdialog when editing tracks without an artist. (BR 183180)
*Statistics were not calculated properly in all instances. (BR 182025)
*Compilation fixes on Open Solaris.
*Trim URL before adding a new podcast.
*Add Ok button to the podcast configuration dialog to improve usability. (BR 181339)
*Add tooltips to now playing widget icons.
*Fix not possible to download episodes from newly added podcast channel. (BR 180851)

Amarok 2.0.2

On the amarok.kde.org, they also had some other words to point out:

The Amarok team is proud to bring you Amarok 2.0.2, codenamed “Only Time Will Tell”. It is a stability update for the Amarok 2.0 series.

Our primary focus is on the upcoming 2.1 feature release, but we have fixed a number of the most critical and annoying bugs present in 2.0.1.1.
Get Amarok 2.0.2 while it is fresh, and keep Amarokin’. And remember, good things are on the way! Check our blogs for updates.

Be sure to give all the KDE and KDE Application Developers your praises (k3b, amarok, kaffine and the likes) to show that the community support for them is still there and strong.

You can upgrade to Amarok 2.0.2 (and the newest version of KDE) by adding the following repository on openSUSE 11.1:

http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openSUSE_11.1/

By doing a:

sudo zypper ar http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openSUSE_11.1/ KDE 4 Unstable Desktop

And upgrading using:

sudo zypper up -r KDE 4 Unstable Desktop

or installing with:

sudo zypper in kde4-amarok

Have fun and enjoy.

Yazı kategorisi: Linux, OpenSuse | » yorum bırak;

KOffice 2.0 Beta 7 Released

Yazan: esersahin 28/03/2009

http://www.benkevan.com/blog/koffice-20-beta-7-released/

A few days ago KOffice 2.0 beta 7 was released with the following highlights from dot.kde.org:

The KOffice developers have released their seventh beta for KOffice 2.0. This release may be the last of the many betas. A decision on whether there will be another beta or if the next version will be the first Release Candidates will be made next week.

The list of changes is longer than ever. For this release we have concentrated on crashes, data loss bugs and ODF saving and loading. Take a look at the full announcement to find out more, or look at the changelog for the details.

Here are a few highlights of this release:
Crashes fixed in all applications
Fix loading and saving of shapes in the text shape (KWord)
Fixed an important cell edit bug in KSpread
Use the format of a master page when using a layout in KPresenter
Many bugs fixed in the chart shape
Also many bugs fixed in Krita
Improved support for SVG in Karbon

Remember that now it is more important than ever to test it and report bugs. If no new severe bugs are found, the next version of KOffice 2.0 will be a release candidate.

KOffice 2

If you want to dabble into some KOffice Beta you can install the packages from the following repository:

http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Extra-Apps/openSUSE_11.1/

You can setup the repository with zypper on openSUSE 11.1 doing:

sudo zypper ar http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Extra-Apps/openSUSE_11.1/ KDE 4 Unstable Extra-Apps

Turn on automatic refresh:

sudo zypper mr -r KDE 4 Unstable Extra-Apps

Update:

sudo zypper up -y -r KDE 4 Unstable Extra-Apps

or Install:

sudo zypper in koffice2

Yazı kategorisi: Linux, OpenSuse | » yorum bırak;