Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.


Thursday
09 September, 2010


face

Siempre he notado que existen miles de tutoriales en Internet para hacer instalaciones de Linux paso a paso, pero en algunos no se toman el tiempo de explicar varias cosas, y si lo hacen, pues la gente sencillamente no lee ;-) .

Por eso decidí crear este par de vídeos donde trato de explicar al público en general cómo instalar Linux, desde la preparación de la partición de Windows para ser redimensionada hasta el paso a paso del Instalador de openSUSE.

Acá los tienen, y recuerden siempre es recomendable hacer respaldos antes de realizar operaciones de cambios en cualquier disco duro.

Primera parte – Preparando Windows

Segunda parte – Instalando openSUSE

Luego de terminar la instalación les recomiendo mis tres artículos de “Cosas por hacer luego de instalar openSUSE”, Parte 1, Parte 2, Parte 3.

Recursos utilizados en los vídeos

Defragler: www.piriform.com/defraggler/

Página de descarga de openSUSE: http://software.opensuse.org/113/es


Wednesday
08 September, 2010


face

Can you beat that? Without using wheels :-)? And can you beat 600m in 2minutes?

And now, how do you generate such numbers from gpx track? No, gpsbabel is not tool for that job, and I could not find anything suitable. So there are now some tools in gtracks project, in the CVS.

I re-used existing "wherewasI" python script, and added custom "all_best_speeds" tool to generate "best speed on every possible distance" matrix. (Suggested usage is something like ./wherewasi.py --summary foo.gpx | ./delete_fast | ./all_best_speeds | sort -n | less). Closer look at all_best_speeds will reveal that it computes the matrix in something like O(N^3) time; I and of course the question is: can you figure out algorithm with better complexity?

And... is there some existing tool that can do this?


face

The launcher menu paradox has almost been around ever since graphical environments were created. They provided a simple method through which users could access their applications pertaining to a particular task. Before the start menu, users had a folder view, generally, with the applications in a list. Earlier environments had to omnipresent shell which launched programs by just typing the name.

Later, along came Linux and graphical environments for it. Some of them have kept the basic idea of a start menu, like the one on Windows 95. KDE did it, Gnome did it and many others, even the high end ones like Enlightenment, did it. It should be admitted though that this is a very clever idea to work with. It is fast, simple, and very visually engaging. However, this launching model by todays standards seems outdated. At least, this is something that frustrates me every now and then because it is so common. It is time for a revolution, a change.

The first thing that we need to do in order to change the start menu is to understand it. I am sure that a lot of people have decided that it is just OK to imitate what others have done. This is not a bad thing, the launcher menu is something that's very clever already, but I want to see innovation. It is time to rethink the way we work with a launcher menu. It is important to remember that these ideas have developed in great length overtime and I do not intend to cover 100% of what has been done, but rather, focus on the things that saw the day of light. I will point out their strengths and weaknesses to ultimately work with the strengths to come up with the best possible idea about how to improve the start menu for openSUSE.
 This is the main reason why I have decided to split this study into 4 parts. It is such a daunting task that as I was doing my research, I realized that it will take very long to work something out that is useful and better than what we already have available for Linux.
The first part will be an analysis of the many ideas and projects that launched "start menus." the second part will cover the good aspects developed for start menus; the third article will talk about the usability and design problems and finally I will conclude with a proposal for a launch menu. This will be my idea on what openSUSE should do with their Kickoff menu.

So, wait for this first article to come out. It will be soon.

Thank you for your support.

Anditosan


face

For those who didn’t know yet, about two weeks ago Novell introduced SUSE Gallery.com where you can submit your SUSE Studio Appliances for the world to see and download. Over the last year, the 400.000 appliances have have already been downloaded 3 million times and now they are available from the Gallery that number will surely skyrocket.

Together with the launch Novell started a contest with a grand prize of $10.000! Creative minds have until the end of this month to submit their crazy/cool/unique/useful appliance to SUSE Gallery.com and enter the contest. So those looking for Fame and Fortune, enter your software appliance into “The Disters” contest and see how you stack up to the rest!

If you haven’t registered for a SUSE Studio account, be sure to request an invitation to get signed up. It’s a quick and easy process and you’ll be able to get started with your appliance in minutes!


face


(Zoot Woman - Lonely By Your Syde)

During the last months I've kept working {with|on} Mono, but not working for Novell anymore.

Today I'm proud to blog about a bit of work I've done on Mono towards a better Binary Serialization experience:

  • mono-api-info command now can output ABI instead of API if you append the flag --abi. It has been useful for us in LindenLab while working on binary serialization compatibility between versions (already upstream!, so will be available in Mono v2.8, even with a new man page).

    If you ever wondered why your .NET code is no longer capable of deserializing some old binary object you had in your servers, instead of fixing the problem in a case-by-case basis, you can now see the whole picture by just diffing the output of mono-api-info --abi from your current and old codebase! A small TODO that I haven't completed yet is to deal with automatic properties (because we still don't use them) so that would be an exercise for the reader!

  • Fix for upstream Mono to act as .NET in regards to Version Tolerant Serialization, a patch to which I have just added a lot more unit tests (soon to be pushed hopefully).

    You can see the patch of this quite old mono bug here. Disclaimer: to be honest you will only need the previous --abi tool if you use a Mono version prior this fix, because from my testing VTS in MS.NET works as if every new field had an [OptionalField] attached! (At least the BinaryFormatter, the TODO here for the reader is to test the SoapFormatter ;) )


On a totally unrelated note: kudos to the MonoDevelop team for making such a great releases lately (and fixing the bugs I report so promptly). I've been testing it the last months on Windows and I can say it's a great experience to see your favorite IDE working cross-platform and making you not depend on VS anymore if you need to work on Windows from time to time (I know the Express versions are free, and are great! but they do not support plugins :( ). BTW, I've been lately experimenting with the C language support in this IDE, and have had some problems, but the real culprit seems to lay behind some wierd behaviour of my gdb in opensuse. Taking advantage that I'm in opensuse planet, can I do a couple of lazyweb requests?:

a) If you're quite familiar with gdb, can you take a look at these 2 bugs in case it rings any bell for you? BNC#588175, BNC#459274

b) Can you try to reproduce those bugs in openSUSE 11.3? (I haven't migrated yet from 11.2 because I fear about the HALlessness of it :) )

PS: Wondered why the video on the top? Well, I like the trend that some people have about posting random photos in their blog posts even when they may be completely unrelated


face

Inicio una serie de artículos a destacados miembros de la asociación KDE España. Empezamos con el secretario de la asociación, Aleix Pol, que aúna juventud y trabajo para ser uno de los programadores más activos de la comunidad KDE en España.

Hola Aleix, ¿podrías empezar presentándote a nuestros lectores?

A ver, me llamo Aleix, tengo 24 años y soy de Barcelona. He pasado los últimos años estudiando Ingeniería Informática en la UPC, carrera que debería llegar a su fin en cuanto acabe mi proyecto fin de carrera próximamente. Aparte, soy un entusiasta de KDE, proyecto con el que he colaborado durante los últimos 4 años aproximadamente, sobre todo en los proyectos de KDevelop y KAlgebra.

¿Cuándo y cómo descubriste el software libre? ¿Y KDE?

Desde muy pequeño me interesó la informática, empezando por los juegos sin duda, pero un buen día mi padre me habló de que un compañero suyo de trabajo estuvo probando un sistema operativo nuevo llamado Linux. Siempre he tenido la sensación que desde entonces supe que lo usaría y, además, que quería ser bueno en ello, y de ahi las cantidades de horas que he dedicado al pingüinito, a los engranajes y a todo el movimiento en general.

¿Cuales han sido tus proyectos en el Software Libre? ¿Y en KDE?

La gran mayoría de mis proyectos han sido en KDE. La historia fue un poco así: primero me pasé a GNU/Linux pero ya había estado haciendo programas en MS Visual Studio y MS Visual Basic sobretodo (-.- sí… tengo un pasado oscuro) y necesitaba alguna plataforma que me ayudara a proseguir en mis proyectillos. Aunque usé KDE casi desde el principio, yo quería trabajar con interficies gráficas y para aquél entonces el ecosistema dejaba bastante que desear. Pasé por Mono, GTK, Qt y no fue hasta que empecé KAlgebra que me opté decididamente por KDE.

KAlgebra fue el primer proyecto en el que trabajé en serio y la verdad es que me fue muy bien. Era un proyecto que tenía bastante pensado desde el principio, era algo que quería hacer desde hacía tiempo, así que las cosas fueron saliendo y pronto empezó a empaquetarse y a ser distribuido en algunas distribuciones educativas. Esto para mi fue muy motivador, hasta el punto que el proyecto aún sigue vivo, más vivo que nunca.
Justo cuando KAlgebra entró en KDE, después de pasar 2 o 3 años en el limbo de KDE-Apps.org, fui aceptado por primera vez al programa Google Summer of Code para KDevelop donde empecé a trabajar en el soporte de CMake en KDevelop que me introdujo a este proyecto.
Estos son los proyectos más importantes en los que he trabajado, pero con el tiempo han salido otros como Kamoso, un programa que hice con Álex


face

Heute (08.09.2010) wurde für openSUSE 11.3 das erste Kernelupdate mit der Kernel-Version 2.6.34.4 veröffentlicht und ist ab sofort im Update-Repo verfügbar. Es wurden einige Fehler wie auch sicherheitsrelevante Fehler behoben.

Das Kernelupdate lässt sich über YaST2 oder per zypper einspielen:

zypper up

Hinweis für Besitzer einer ATI-Grafikkarte, die ATI Catalyst auf ihrem openSUSE-System installiert haben:
Nachdem man den Kernelupdate eingespielt hat, sollte man bei einem Neustart zuerst in den Runlevel 3 booten. Dann loggt man sich als root ein und anschließend den fglrx-Kernelmodul neu bauen lassen:

fglrx-kernel-build.sh

Danach mittels reboot neustarten.
Weitere Informationen: openSUSE 11.3 – proprietären Grafik-Treiber ATI Catalyst 10.8 als RPM installieren

Die offizielle Ankündigung von Marcus Meissner zum Kernelupdate:
http://lists.opensuse.org/opensuse-security-announce/2010-09/msg00003.html

Ein Auszug der Changelog aus der RPM:

  • kabi/severities: Ignore changes in md, jbd2 and kvm.
  • ssb: Handle Netbook devices where the SPROM address is changed (bnc#617912).
  • novfs: backing device info initialization (bnc#623472).
  • novfs: Fix a memory leak that causes an OOM condition (bnc#610828).
  • ALSA: hda – Add beep mixer support to Conexant codecs (bnc#619727).
  • novfs: code cleanup for one case of novfs return value (bnc#624606).
  • novfs: Fix error codes for getxattr for novfs (bnc#529535).
  • x86,nobootmem: make alloc_bootmem_node fall back to other node when 32bit numa is used (bnc#623005).
  • drm/i915: enable low power render writes on GEN3 hardware (bnc#621598).
  • drm/i915: add ‘reclaimable’ to i915 self-reclaimable page allocations (bnc#621598).
  • drm/i915: Define MI_ARB_STATE bits (bnc#621598).
  • drm/i915: gen3 page flipping fixes (bnc#617530).
  • drm/i915: don’t queue flips during a flip pending event (bnc#617530).
  • Refresh due to acpi_power_register now properly defining the field values.
  • ALSA: hda – Add pin-fix for HP dc5750 (bnc#624118).
  • GFS2: rename causes kernel Oops (bnc#627386 CVE-2010-2798).
  • ALSA: hda – patch_nvhdmi.c: Add missing codec IDs, unify names (bnc#627212).
  • NFS: allow close-to-open cache semantics to apply to root of NFS filesystem (bnc#584720).
  • Char: nozomi, set tty->driver_data appropriately (bnc#619021).
  • Char: nozomi, fix tty->count counting (bnc#619021).
  • novfs: Lindent novfs sources. Added to keep SLE11SP1, 11.3, and master codebases in sync.
  • vmscan: raise the bar to PAGEOUT_IO_SYNC stalls (bnc#625339).
  • ALSA: hda – Add quirk for Dell Vostro 1220 (bnc#631066).
  • ALSA: hda – Handle pin NID 0x1a on ALC259/269 (bnc#631185).
  • ALSA: hda – Handle missing NID 0x1b on ALC259 codec (bnc#631185).
  • kabi/severities: Updated kABI severities to deal with some changes introduced by the -stable patches.
  • KABI-REVERT: perf_events: Fix races and clean up perf_event and perf_mmap_data interaction.
  • KABI: Guard struct firmware against kabi checker.
  • KABI: Guard against compat.h in fs/aio.c.
  • KABI-REVERT: wrong type for ‘magic’ argument in simple_fill_super().
  • kabi/severities: Ignore changes in usb_buffer_{,un}map_sg
  • blktap2: eliminate bogus clearing of PG_reserved (bnc#624814).
  • Update Xen patches to 2.6.34.4.
  • Fix kabi files (symsets were missing).
  • ALSA: Enable jiffies-check in xrun-debug as default (bnc#631319).
  • ALSA: emu10k1 – delay

face

Linux.com, konkrétně Jack Wallen, si pozval na kus řeči nového komunitního managera projektu openSUSE, se kterým probral několik zajímavých témat, která se týkají především jeho bývalé práce u KDE, ale došlo i okrajově na jeho novou práci u openSUSE.

Ještě než se pustíte do pročítání tohoto rozhovoru, si něco řekněme o Jose Poortvlietovi. Ten byl začátkem srpna přijat Novellem na post komunitního managera. Předtím působil jako dobrovolník komunity KDE a tam pracoval na postu vedoucího marketingového týmu. Při tomto zaměstnání koordinoval a přispíval k práci kolem vydávání nových verzí KDE, tvorbě marketingových materiálů, navštěvování a organizování konferencí a udržoval kontakt s tiskem a médii. Ve svém "reálném" životě pracoval například jako obchodní konzultant pro Royal Bank of Scotland. Dále pak dělal pro holandské státní oddělení Vzdělávání a KPN a také pro holandského poskytovatele Telecom.

číst dál


face

SUSE Studio offers nice user interface for configuring software appliances with many options. But what if you already had a configuration ready — for example a carefully tuned AutoYaST profile which your company uses for installing workstations? Or a KIWI configuration of your appliance exported from Studio (so that you could build that appliance on your machine) which you modified locally? Until now, there was no easy way how to apply it in Studio.

This is why we prepared a brand new KIWI and AutoYaST configuration import feature. If you enable it (more about that below), you can easily create an appliance based on your settings. Just go to your Studio home page, click the Create new appliance... button and select the Import icon instead of one of the templates.

Import icon

You can then upload your KIWI configuration or AutoYaST profile. Studio will automatically detect which one you used and create a new appliance with the configuration settings applied.

Supported settings

KIWI and AutoYaST imports support the following settings:

Setting KIWI AutoYaST
Name X
Architecture X (1)
Base system X (1)
Users X X
Repositories X X
Pacakges X X
Patterns X
Network settings X
Boot settings X
Build scripts X
Logos X
Background theming X
Overlay files X X

(1) The architecture and base system are selected by the user during the import. This information is not contained in the AutoYaST profile as the profiles are designed to be generic.

What about the settings Studio can’t import? In case of AutoYaST, we apply the unimported settings using AutoYaST itself when the appliance boots for the first time. You can edit the applied profile (with already imported settings stripped) in the Configuration → Scripts tab in the appliance configuration.

Enabling the imports

The KIWI and AutoYaST imports are still in beta — which means they aren’t enabled by default. To enable them, go to your profile page and click on the Enable experimental features button (this will give you access to all beta features we introduce).

As with all software still in beta, bugs are expected. If you’ll note anything not working as expected, let us know so we can look at the issue and fix it.


face

Savin Alex has been busy working on improving kiwi-ltsp lately. The basic idea behind the new development is easier management of multiple LTSP images that can be served over NBD or AOE. Earlier Shrenik Bhura had added multiple image support for AOE, now it is also supported when using NBD.

For example, with very powerful hardware available, images of KDE, GNOME desktops or any other profile of your choice  can be served as  LTSP_FATCLIENT, this will enable images to use resources on the clients’ local hardware instead of traditional LTSP way of running all the client sessions on the server. Advantage of this way is making use of local hardware resources and central management of OS deployed in the entire network. LTSP can also be clustered to load balance and in case one of the servers fail.

New development also include easier way of managing PXE boot menu. See kiwi-ltsp-setup –intro for more.

Check out the detailed  howto for using multiple LTSP images hereStart here to know more about LTSP and how you can get started with it in your network. openSUSE Education Li-f-e DVD comes bundled with KIWI-LTSP server and takes just a few clicks to get it up and running.


Sirko Kemter: Virtuelle Adventures

05:52 UTCmember

face

Vor nicht all zu langer Zeit habe ich über SUSE Studio berichtet, mit dem sich mit wenigen Mausklicks Live-ISOs für DVD,CD oder Sticks oder auch Images für XEN, KVM, VMWare oder VirtualBox erstellen lassen. Einloggen, Template auswählen, Software hinzufügen, konfigurieren, builden lassen und herunterladen und nutzen.
Auch unter ubuntu gibt es Möglichkeitenderartiges zu Erstellen. Für das Erstellen von Live-ISO gibt es das Ubuntu Customization Kit oder Remastersys, wie sieht es aber mit Werkzeugen zum Erstellen von Images für XEN, KVM oder ähnlichen Virtualisierungslösungen aus? Gefunden habe ich dafür zwei Lösungen den ubuntu-vm-builder und vmbuilder.
Ersterer ist gemäß den Hilfeseiten bei Ubuntu eigentlich veraltet, was mich dabei stutzig macht ist das, dass Paket trotzdem noch installierbar ist und seltsamerweise das neuere Werkzeug mit installiert.

sudo apt-get install qemu-kvm qemu-kvm-extras debootstrap kpartx python-cheetah python-libvirt devscripts libvirt0 libxen3 libaio1 bridge-utils qemu-common seabios vgabios ubuntu-vm-builder

Ein paar weitere Abhängigkeiten werden dann auch noch mit installiert. Das Manual zu dieser Software ist nicht sehr umfangreich, aber es fördert immerhin zu Tage, dass man mit dem Aufruf ubuntu-vm-builder <hypervisor> <distro> –help Hilfe erhalten könnte. Mir neu mehr Hilfe in der Hilfe als im Manual zu finden.
Der Aufruf ubuntu-vm-builder kvm lucid erzeugt ein Image für kvm mit einem JeOS auf Lucid Lynx Basis und zwar mit allen default Einstellungen. Die allerdings herauszufinden war nicht einfach. Eine Suche in den Dateien unter /etc/vmbuilder brachte nicht wirklich viel zum Vorschein. Eine Suche bei Google brachte dann folgendes Onlineformular zum Vorschein, das nicht nur den ellenlangen Aufruf generiert sondern ganz zufällig auch die Defaultwerte enthält.
Das die Dateien unter /etc/vmbuilder/ eine Art Templates darstellen scheint wohl Fehlanzeige zu sein, so ganz zufrieden bin ich mit dieser Lösung nicht. Also habe ich die zweite Lösung ausprobiert.

sudo apt-get install python-vm-builder

Der Aufruf ist vmbuilder <hypervisor> <distro> also identisch zu ubuntu-vm-builder auch die Optionen sind identisch bis auf eine, aber entscheidende. vmbuilder akzeptiert Konfigurationsfiles. Und so kann ein solches Konfigurationsfile aussehen.

[DEFAULT]
arch = i386
ip = 192.168.10.100
part = vmbuilder.partition
user = user
name = user
pass = geheim
tmpfs = -
firstboot = boot.sh
firstlogin = login.sh

[ubuntu]
mirror = http://paketserver:9999/ubuntu
suite = lucid
flavour = virtual
addpkg = openssh-server, weiteres-paket, und-noch-eins
ppa = name

[kvm]
libvirt = qemu:///system

Der Aufruf wäre dann folgender.

sudo vmbuilder kvm ubuntu -c configuration.cfg

vmbuilder lädt dann alle entsprechenden Pakete von den angegebenen Servern herunter, daher empfiehlt es sich wenn man häufiger derartige Abbilder erzeugen will apt-proxy oder apt-mirror zu verwenden. Nach der Beendigung findet man in seinem Home-Verzeichnis ein Verzeichnis namens ubuntu-kvm, welches das Abbild und ein Startskript run.sh enthält, mit der man die Maschine direkt starten kann.
Das man statt eines JeOS mit Hilfe der Konfiguration auch eine Desktop-Maschine erzeugen kann ist einfach. Dazu einfach die folgenden Pakete installieren lassen.

  • ubuntu-desktop
  • language-pack-de
  • language-pack-de-base
  • language-support-de
  • language-pack-gnome-de
  • language-pack-gnome-de-base

Das Paket ubuntu-desktop ist ein Metapaket, welches alle benötigten Pakete als Abhängigkeit


face

In diesem Artikel behandele ich das Thema “X11-Forwarding” über SSH, um eine GUI-Anwendung (z.B. Thunderbird, OpenOffice, usw.) auf einem entfernten Desktop-Rechner auszuführen und z.B. auf einem Netbook anzeigen zu lassen. Das klingt sehr verlockend und die Einrichtung ist auch nicht so schwierig. ;-)

Bevor man eine Anwendung über das Netzwerk starten kann, muss man erst noch ein wenig vorarbeiten.

Auf dem entfernten Rechner (z.B. Desktop):

  1. Man öffnet die Datei /etc/ssh/sshd_config mit einem Editor als root
  2. Jetzt prüft man, ob die folgende Einstellung aktiv ist. Hinweis: Es darf keine Raute vorne weg sein:
    X11Forwarding yes
  3. Wenn man nur ein IPv4-Netzwerk (z.B 192.168.0.2) anstatt ein IPv6-Netzwerk (z.B. fe80::c0a8:2) verwendet, so sollte man besser den SSH-Server zwangsweise per IPv4 kommunizieren lassen. Andernfalls könnte es Probleme geben. Daher trägt man noch folgendes ein:
    AddressFamily inet
  4. Nachdem man die Konfiguration abgespeichert hat, muss man jetzt noch den SSH-Server neustarten:
    rcsshd restart
  5. Wenn der SSH-Server bei jedem Neustart mitstarten soll, so kann man dies im Runlevel-Editor ändern. Man ruft per ALT + F2 den Krunner auf und gibt ins Eingabefeld folgendes ein:
    yast2 runlevel

    Danach in der Liste den sshd aktivieren und mit Okay die Änderung bestätigen.

Auf dem Rechner (z.B. Netbook oder Notebook), von dem später eine Verbindung zum entfernten Rechner aufgebaut wird:

  1. Man öffnet die Datei /etc/ssh/ssh_config mit einem Editor als root
  2. Dann ändert man folgenden Eintrag
    #  ForwardX11 no

    in

       ForwardX11 yes

    ab.

  3. Abschließend prüft man noch, ob die folgende Einstellung aktiviert ist. Hinweis: Es darf keine Raute vorne weg sein:
    ForwardX11Trusted yes
  4. Diese Konfiguration speichert man nun ab.

Somit ist man jetzt mit der Konfiguration durch. ;-)

Wie baut man jetzt eine Verbindung zum entfernten Rechner auf und startet eine Anwendung (z.B. Dolphin)?

Zuerst benötigt man die lokale IP vom entfernten Rechner. Das kann man sehr leicht auf dem entfernten Rechner herausfinden und gibt in der Konsole folgendes ein:

ifconfig

Dann pickt man sich in der Ausgabe die IP-Adresse heraus
z.B. bei eth0: inet Adresse: 192.168.0.2

Man kann es auch über das Internet durchleiten lassen, jedoch benötigt man die IP-Adresse vom entfernten Rechner, die vom Internet-Provider zugeteilt wurde, und eine entsprechende Änderungen an der Firewall im Router (Port 22 von außen freischalten und zum “entfernten” Rechner umleiten) müssen auch vorgenommen werden. Jedoch würde ich für Linux-Neulinge abraten, diese Änderung am Router vorzunehmen. Wer daran interessiert ist, sollte sich besser zuerst mit dem Thema “Sicherheit unter Linux” auseinandersetzen. Das fängt mit der Stärke des Passwortes an und geht über Verwendung des SSH-Schlüssels und hört mit der Umlegung des SSH-Ports auf. (Dazu werde ich auch nochmal ein Artikel schreiben ;-) )

Jetzt geht’s ans Eingemachte und tippen folgendes in der Konsole auf dem Netbook (Notebook) ein, um z.B. Dolphin vom Desktop-Rechner zu starten und auf dem Netbook (Notebook) anzeigen zu lassen. (Bitte ersetzt hier den Usernamen und die IP vom


face

Mucho días sin escribir, la verdad es que he tenido proyectos en los que he aprendido muchas cosas y que valen la pane escribir, mas como referencia para futuros proyectos en los que tenga que hacer algo similar :)

Estos días preparare algo y espero regresar a escribir con mayor regularidad, me siento mas productivo en mi blog que en facebook :headbang:


Tuesday
07 September, 2010


face

Die Ausgabe 09/2010 von “freiesMagazin” ist fertig. freiesMagazin ist ein kostenloses, monatlich erscheinendes Magazin, das über Wissenswertes und Neues aus den Welten Freier Software, Open Source und Linux berichtet. Das Magazin kann von der Seite freiesmagazin.de als PDF-Datei heruntergeladen werden. Außerdem sind zwei für Mobilgeräte geeignete Versionen verfügbar die aber auch mit normalen Browsern betrachtet [...]


face

Při brouzdání internetem a hledání námětu na další článek na tento server jsem narazil na hezky zpracovaný článek o vývoji popularity jednotlivých distribucí. Nejedná se ani tak o srovnání popularity ani počtu instalací, ale jde o srovnání výsledků vyhledávání jednotlivých distribucí prostřednictvím nejpoužívanějšího nástroje pro vyhledávání... Ano, je tu řeč o Googlu. K tomuto srovnávání byl použit nástroj Google Statistiky vyhledávání (Insights), který tvoří grafy, jež znázorňují počty dotazů na zadaný podmět v nastaveném časovém horizontu. Tento počet dotazů je vyjádřen škálou od 0 až po 100.

číst dál


face

From a small chit chat on IRC the other day with Bryen and Sirko somehow I ended up with the task to providing an article about openSUSE Build Service. I have to say Sirko is awesome in Guerrilla Marketing, a cool proof could be the way how he got me into this. Anyway… though I’m not a journalist, every article should start with some basic research…

  • Checked out Build Service Portal;
  • Signed on opensuse-buildservice mailing lists;
  • Got 2 software packages not so visible on openSUSE:
  • Packaged the stuff with my narrow knowledge (keep in mind that my stuff is actually marketing management and not computer science);
  • Consulted the opensuse-buildservice mailing list to get some feedback about the specs (DimStar was most helpful on this).

This was done so far… as personal interest and also as a way to get some qualitative research and knowledge about the topic I’m writing. I understand that there is some tremendous potential on openSUSE Build Service and that it can bring much to the openSUSE Community and to openSUSE as a GNU/Linux distribution (yes, I know some might not like the terminology from RMS, but I do).

My next steps are simple and will provide me the rest of the information I require to start writing the article:

  • Get a cool group for my 2 packages;
  • Try to push them into openSUSE:Contrib; (understanding that I will be responsible for their maintenance, lucky for me Canonical did a good job on them and I wont probably be subject of long wild goose chases… or bug hunts).

Once I get my reply from openSUSE:Contrib, this research process if finished for me, despite of the outcome, it really doesn’t matter if it’s accepted or not, the most important thing is to document it and take some qualitative feedback out of it.

I’ve also sent a small email to the openSUSE’s Marketing Team requiring help from Andreas Jaeger, the openSUSE Build Service liaison to get some materials that I am aware they exist and if possible to help me on this task.

My goal is to get this done shortly before the openSUSE Conference 2010. This project is my personal reply to Sirko claims that I’m a story teller! Thanks for the motivation Sirko.

Oh! I almost forgot… Do YOU have something useful for this article? Please feel free to share. My contacts are somewhere here.


Michael Meeks: 2010-09-07: Tuesday.

13:02 UTCmember

face
  • Up too early, got babes practised with time to spare; packed them off to school. Reviewed a PackageKit / zypp backend bug or two, compiled a new Python so I could build gobject-introspection, and thus PK. Prodded and merged misc. fixes.
  • Lunch. Considered DOS on Dope as a platform for a Web Office suite, particularly with it's lack of known scalability problems (the time-wasting perils of twitter strike again).

face

Na stronie projektu openSUSE pojawił się już wstępny roadmap dla wydania 11.4. Planowane jest wydanie 6 kamieni milowych, 2 wydań kandydujących, a ostateczna premiera wersji 11.4 miałaby odbyć się 10 marca 2011 roku.

  • czwartek, wrzesień 02, openSUSE 11.4 Milestone 1
  • czwartek, wrzesień 30, openSUSE 11.4 Milestone 2
  • piątek, listopad 05, openSUSE 11.4 Milestone 3
  • czwartek, listopad 25, openSUSE 11.4 Milestone 4
  • czwartek, grudzień 16, openSUSE 11.4 Milestone 5
  • czwartek, styczeń 20, openSUSE 11.4 Milestone 6
  • czwartek, luty 10, openSUSE 11.4 RC 1 release
  • piątek, luty 25, openSUSE 11.4 RC 2 release
  • czwartek, marzec 03, openSUSE 11.4 Goldmaster
  • czwartek, marzec 10, openSUSE 11.4 Wydanie oficjalne

face

Ostatnio przeinstalowałem sobie Windows 7 z płytki firmowej Della od innego zestawu, tak więc po instalacji należałoby zmienić klucz produktu. Przy użyciu standardowej płytki instalacyjnej klucz produktu możemy zmienić poprzez funkcję Zmień klucz produktu w Mój komputer – Aktywacja systemu, jednak w przypadku instalacji z płytek Della system jest już aktywny i opcja ta jest niedostępna. W takim przypadku możemy skorzystać z narzędzia SLMGR. Narzędzie to służy do zarządzania licencjonowaniem systemu Windows. Aby z niego skorzystać uruchamiamy wiersz poleceń z podniesionymi uprawnieniami i wpisujemy:

smlgr -ipk twój_klucz

Przełącznik -ipk służy do zmiany klucza produktu. Po wywołaniu po chwili pojawi się okienko z komunikatem o pomyślnej zmianie klucza. Następnie wpisujemy:

smlgr -ato

Przełącznik -ato z kolei przeprowadzi ponowną aktywację systemu. Po wywołaniu otrzymamy informację o pomyślnej aktywacji systemu.


face

Since many years I am an (open)SUSE user and spread openSUSE wherever I could in my private environment.
The openSUSE strategy discussion has scratched my itch and I started to contribute more to openSUSE.

What could you expect?
Don't expect much code from me. My experiences are more in the area of strategy, marketing and promotion. Perhaps I could also share some results from my researches during the last years about open source communities.

So be curios and stay tuned.
I am happy to join the openSUSE community and I am looking forward to know more of you.

Let's have a lot of fun!

Cheers,
Thomas


face

Leído en Paraiso Linux, pero original de Angel Verde os os invito a leer un artículo donde un usuario de Linux decide migrar a Windows y se encuentra con bastantes dificultades.
De lectura obligada nos hace reflexionar sobre la libertad de elección, el respeto a los otros, la eficencia y las razones económicas de utilizar un sistema GNU/Linux frente a Windows.
Resalto solo un párrafo, por no hacer copia y pega, y os invito a leer el artículo completo.

OK, decidí que lo instalaría. Seguí las instrucciones de la pantalla, pero me puse nervioso porque no me pregunto si tenia otros sistemas operativos instalados. Se que en cada GNU/Linux que instalo, siempre me pregunta por crear nuevas particiones o cosas por el estilo. Le volví a llamar a mi amigo y el me dijo que Windows 7 elimina cualquier otro sistema operativo previamente instalado. Bien, OK, regrese a GNU/Linux y respalde todos mis datos antes de regresar a instalar mi copia de Windows.

Versión completa: Angel Verde


face

Salah satu masalah utama jika akses SSH server dibuka untuk keperluan remote adalah adanya user lain (cracker, hacker) yang coba-coba mendapatkan akses masuk kedalam sistem. Hal ini bisa diantisipasi dengan berbagai macam cara, misalnya dengan mengubah port default SSH, tidak membolehkan akses root secara remote, hanya membolehkan host tertentu untuk akses dan lain-lain.

Contoh berikut adalah log cracker yang ingin mencoba masuk kedalam sistem :

Sep 6 23:44:33 myhostname sshd[22483]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:37 myhostname sshd[22488]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:43 myhostname sshd[22494]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:46 myhostname sshd[22499]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:48 myhostname sshd[22504]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:51 myhostname sshd[22509]: Invalid user operator from 119.6.62.xxx
Sep 6 23:44:54 myhostname sshd[22514]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:44:56 myhostname sshd[22519]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:44:59 myhostname sshd[22524]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:02 myhostname sshd[22530]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:05 myhostname sshd[22689]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:07 myhostname sshd[22773]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:10 myhostname sshd[22904]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:13 myhostname sshd[22954]: Invalid user oracle from 119.6.62.xxx
Sep 6 23:45:15 myhostname sshd[22962]: Invalid user oracle from 119.6.62.xxx

Seperti bisa dilihat pada log diatas, pengakses mencoba dictionary attack menggunakan berbagai nama user untuk mencoba akses. Meski akses tersebut gagal dilakukan, server tetap terbebani karena terpaksa melayani request yang masuk.

Salah satu cara yang bisa ditempuh untuk melindungi akses SSH adalah dengan menggunakan aplikasi denyhosts. Aplikasi denyhosts melindungi ssh dengan cara memasukkan IP pengakses kedalam daftar blacklist jika beberapa kali salah memasukkan password.

Proses instalasi dan apliksinya sangat mudah. Berikut adalah proses instalasi pada openSUSE 11.3 :

  1. Buka [http://software.opensuse.org/search openSUSE Build Service]. Cari aplikasi denyhosts. Sesuaikan versi openSUSE yang digunakan. Jika tidak ada aplikasi untuk versi openSUSE yang digunakan, silakan ambil paket untuk versi yang berdekatan, misalnya SLES 11 SP1 bisa menggunakan package untuk SLES 11 atau untuk openSUSE 11.1, 11.2 atau untuk openSUSE 11.3.
  2. Install menggunakan one-click-install
  3. Review file konfigurasi /etc/denyhosts.conf. Pada distro openSUSE, denyhosts secara default akan menganalisa file log /var/log/messages, namun mungkin saja kita perlu mengubah nama file log untuk dianalisa, misalnya jika menggunakan aplikasi Zimbra, denyhosts bisa diperintahkan untuk mengakses file log /var/log/zimbra.log. Check juga mengenai jumlah maksimum kesalahan pemasukan password dan pilihan lain yang tersedia.
  4. Jika

Monday
06 September, 2010


Michael Meeks: 2010-09-06: Monday.

21:00 UTCmember

face
  • Overslept, not into the 6:45am waking routine from the holidays yet. Fed, and hurried babes off to school. M. looking so tiny and sweet in her new uniform.
  • Back to the mail hill, admin, Clarity, tested bootchart2 pieces, merged branches and pushed out a 0.12.4 - with memory graphing from Dave Martin at Linaro, and lots more nice fixes and features from Riccardo Magliocchetti.
  • Started slogging through abstracts: I know everyone wants their simple calculator-app to be 'more a platform than an app' but apparently they now want to be virtual platforms - perhaps fair enough if it has at least some tenuous link to virtualisation; but if not ?
  • Dinner, baby stories, more mail thrash. Finished LotR in the evening while J. painted.

face

El equipo de desarrollo de KDEPIM, el gestor de información personal de KDE, sigue con su trabajo en dos frentes.
El primero, y más esperado, es la publicación de la tercera beta de la versión 4.5. Esta versión, evidentemente, es más estable que la anterior y ofrece más servicios (por ejemplo, KMail además de POP y disconnected IMAP, ahora soporta Push IMAP)(gràcies Aleix)
Si vais a actualizar, haced una copia de seguridad de vuestra información.
Más información: bash’s blog
Por otra parte, también se está preparando la versión 4.4.6, que parece que estará lista para el jueves 9 de setiembre.
Atentos a las actualizaciones de vuestras distribuciones.
Más información: awinterz’s blog


face

Die 139. Ausgabe der deutschsprachigen openSUSE Wochenschau ist nun online. Das Team  hat wieder interessante Neuigkeiten rund um openSUSE und Linux für euch zusammengetragen. Unter anderem in dieser Ausgabe: openSUSE Connect Beta – die neue zentrale Benutzerdatenbank Neues von openFATE – ein Gemeinschaftsportal für das Feature- und Anfragesystem von openSUSE Tipps & Tricks für Desktopanwender, [...]


face

We want YOU!

As you might have noticed, except for a couple of articles by a few others, I have largely been writing the majority of content for OMG! SUSE!. It has been tremendously fun but the volume of interesting content is very much dependent on the amount of free time I have on the weekends, which is when I do the majority of my writing.

There are some events coming up which will likely gobble up a few weekends this Autumn and I'd like to ensure that OMG! SUSE! stays up to date during that time. This means that we want you! I'm hoping to get some other regular contributors that can write while I'm otherwise indisposed.

If you have ideas for an articles or tutorials you'd like to write for OMG! SUSE!, drop me a line and let's get it published! Even if you don't have any ideas but feel like helping out covering recent events in the openSUSE community, that'd be appreciated too.

If all else fails, OMG! SUSE! might go quiet for a few weeks in early October which might not be the end of the world (but it sure will be boring!)

Note: Image courtesy of tuxparty.org



face

Back in "ye olde days" of Linux, there were no games. If you wanted to entertain yourself, you either played nethack or you tried to compile Gentoo, neither of them terrifically fun. (In those days I played a game called "learn to program" which was probably the most entertaining game on Linux at the time.)

Gaming on openSUSE, HIIIYAAAAH!

These days gaming on Linux is a completely different story, we now have everything from Minesweeper (KMines) to first-person shooters and flight simulators. While the gaming experience is far from perfect on the Linux Desktop, it's miles ahead of where it was just four years ago.

Today gaming on Linux is becoming increasingly popular, so much so that my pals over at OMG! Ubuntu! are launching a new site called Ubuntu Gamer before the year is out. I don't plan on launching a site called "openSUSE Gamer", but I did want to jot down a list of some pretty stellar games available for Linux users of all kinds.

The full list of awesome Linux games after the jump

Shooters

  1. UrbanTerror Looking through the scope in Urban Terror is by far one of my all-time favorite Linux-based games. It feels like a slightly more dated version of Counter Strike with clients for Mac OS X, Linux and Windows. It continues to have a great online presence with hundreds of busy UrbanTerror (UrT) servers running around with plenty of skilled shooters and noobs galore. UrT offers a few different kinds of game play such as "Team Survivor" (when you die in a round, you're dead, last man standing wins), "Free for All" (no teams, everybody kills everybody), "Team Deathmatch" (two teams rack up kills against each other) and my favorite: Capture-the-Flag. The download is big and unfortunately not packaged for openSUSE but you can download 32-bit or 64-bit executables here.

  2. BZFlag is probably one of the oldest 3D games still played on the Unix platform, developed originally in 1992 it is likely the oldest game on this list. Similar to UrbanTerror, BZFlag has a online multiplayer component which allows you to connect to various servers for different kinds of game play, the most common of which being Capture-the-Flag. Unlike UrT however, in BZFlag you're cruising around in a tank shooting at people, and depending on the map, you tank may be capable of incredible power-ups or even jumping/flying abilities!


  3. Nexuiz is another first-person shooter based around a modified version of the Quake engine. Nexuiz offers very fast-paced but straight-forward deathmatch-style play, which I tend to suck at. If you ever dominated while playing Quake back in the day, Nexuiz might be for you.


  4. Warsow feels very similar to Nexuiz to my unsophisticated gaming palate, unlike Nexuiz, Warsow has taken the speed and movement aspect of the game to the extreme. Just watching other people play Warsow wears me out, the best players sprint through levels gobbling up power-ups and shooting their opponents. Similar to some of the other games, Warsow includes a Capture-the-Flag, Team Deathmatch and a few other

Sunday
05 September, 2010


Michael Meeks: 2010-09-05: Sunday.

21:00 UTCmember

face
  • Up early, J. off to West Suffolk to have dressing changed, (why does she so frequently get ill when I'm away). Tended babes.
  • Off to NCC, ran the creche, which (despite the loss of M.) is more packed with fun-sized people than before.
  • Home for lunch, with Andre and Lottie - good to get to know them a little better. J. slept a while, while I disappeared into the Lord of the Rings and the babes watched cbeebies.
  • Dinner, put babes to bed and read to them; J. went out to meet up with Myriam, while I read ever more.

face

Tampoco se queda atrás mi distribución favorita, OpenSuSE, que ya lanza su primera beta, llamada por ellos mismos Milestone 1.
Tenemos pocos datos a nuestra disposición pero los que tenemos son los siguientes:

  • La siguiente Milestone será para el 30 de septiembre
  • El lanzamiento definitivo de OpenSUSE 11.4 será en Marzo de 2011.
  • Traerá mejoras en el gestor de paquetes Libzypp, que será más rápido y eficaz.
  • Esta Milestone ya presenta mejoras como la inclusión de XOrg 1.9, KDE 4.5 y GNOME 2.32.0 Beta 1.

Si queŕeis podéis ver línea temporal de desarrollo en el siguiente enlace.

Vía: OpenSuSE News


face

Now we are ready. We’re pleased to announce our new openSUSE Weekly News #139. Enjoy it! :-)



Announcements

openSUSE News: Software Freedom Day is Coming!

“On September 18, it is international Software Freedom Day. Software Freedom Day aims to celebrate Free Software and the people behind it. It wants to spread the word about Free Software and help people find each other.”

openSUSE Announce First 11.4 Development Milestone With Improved Package Management Performance, New XOrg, KDE and GNOME

“openSUSE 11.4 Milestone 1 is available today, Thursday, September 2 for developers, testers and community members to test and participate in the development of openSUSE 11.4. M1 starts off openSUSE 11.4 development at a cracking pace with performance improvements in the package management network layer and version updates to major components. This milestone contains libzypp version 8.1, which has a new backend for http and ftp package downloads. MultiCurl replaces the old MediaAria backend, and brings support for zsync transfers and better Metalink download support. These will improve both repository refresh and package install and update performance. Metalink allows the multi-channel download of packages by downloading the individual blocks of a package in parallel from multiple servers. ZSync reduces the amount of data to download by only fetching the changed parts of a file instead of the whole file. This speeds up repository refreshes, since due to the way the repository data is structured, it is easy to locate the parts of the metadata that changed since the last update. The new Curl-based zypp backend also gives libzypp and therefore zypper and YaST better support for network proxies, by using the same proxy configuration as the rest of YaST instead of its own, and adds support for HTTP BASIC password-protected repositories. And as an added bonus, MultiCurl should eliminate slow and hanging package installations that occurred due to bugs in the old MediaAria backend.”

openSUSE Connect Beta

“As a result of the openSUSE Boosters’ ‘HackMeck‘ two weeks ago at FrOSCoN we are proud to present you with a new beta of openSUSE Connect. Connect is supposed to become the central user database for the openSUSE project. Sounds bland, don”t it? But you know the Boosters, everything we do comes with a grain of spice and Connect is no different. The spice here are a lot of nifty social network features like user profiles, friending, groups, an event calendar and possibly more. Thats possible because on top of the user database we use a Free Software social network framework called

Older blog entries ->