Last four months have gone fast, really fast:

• Akademy-es in Zaragoza
• Flying to Berling to work on KDE eV economic report and LinuxTag
• Moving to Nuremebrg
• Begin to work as openSUSE Team Lead at SUSE
• Prepare my Akademy keynote and my talk about KDE Connect
• Develop and present the economic report during KDE eV AGM plus Board elections
• Complete the administrative work derived from relocation
• Flying to GUADEC
• Looking for a flat and moving.

and working, of course. All of them time consuming, but specially, vital energy consuming. So this August I've been trying to cool down a little and go back to routine, now that I have my flat (how important is this step, right?).

Meanwhile, at SUSE.....

the openSUSE Release team, together with the community, have managed to release 12.2 RC2 on time. This could be no news for openSUSE users and supporters. But for us means that we are delivering even tough we are in a transition phase, and despite the fact that we are reducing the pressure over the Release Team instead of increasing it. Delivering on time is always a good sign.

12.2 RC2 is usable so, if you are a developer or an openSUSE power user, consider installing it and giving us feedback. No major bugs should be expected but your reports are very valuable to us. I already have it in my laptop and, except for little details, it works as expected. If you prefer to wait until September 5th, you will be able to install the fresh 12.2. openSUSE Team at SUSE is finishing these days the last few tasks, specially related with generating the Gold Master and creating marketing material.

This month of August openSUSE Team is also putting energy into the openSUSE Conference organization. As you probably know, this is not a normal event. We host four events in one

• Future Media
• openSUSE Conference
• Gentoo Conference
• Linux Days

so there is a lot to do, as you can imagine. Organizing Free Software events is something that follows me in every job I take, no matter where that is. I'm kind of getting used to it. Don't know if that is a good sign though.

openSUSE community in America has an important milestone in September at openSUSE Summit, the community conference organized right after the SUSE Conference in Orlando, Florida, USA. So if you live in South, Central or North America and like openSUSE, don't miss it. More than 50 people have registered already so it looks like is going to be a good opportunity to give a push to our community in North America.

So September and October are going to be busy months for me and the Team.

 

Na semana de 03 a 08 de Dezembro de 2012 promoveremos os 05 mais importantes eventos sobre a infraestrutura da Internet no Brasil: o PTT Fórum, o Fórum IPv6, o ION, o GTER e o GTS. Programa-se e participe! A participação é gratuita.

Saiba mais em: http://nic.br/semanainfrabr/.


Fonte: http://ipv6.br/ii-semana-da-infraestrutura-da-internet-no-brasil/






Avise se algum erro for encontrado nesse artigo.


O conteúdo desse artigo pode ser modificado ou atualizado, por isso, visite essa página constantemente e mantenha-se atualizado.

Sería como un post de descargo, porque no se cual será el problema jaja. Tengo un Router Kozumi K-5400GR sin uso, y lo quería usar. Anteriormente, antes de mudarme, lo usaba sin ningún problema para navegar, con Gigared como ISP (Argentina), usando tanto Linux como Windows. Me mude hace unos meses y aca usamos el ISP Arnet…Más

Once again our team meets for another release of our distribution of choice, openSUSE 12.2. As part of the artwork team, we focused on this release on going back to the strong greens that identify our distribution. We also added a few wallpapers with images of chameleons so that our mascot would be part of our distribution again.
On the subject of chameleons, I have been pondering recently about the variety of designs that can come from this reptile. It is one that changes colors to adapt to its environment, it also has a tongue that extends sometimes longer than its own body and it lives in trees eating insects. I own a chameleon myself and as I have lived with it, I have realized that it is a great design inspiration. Recently also, I found these images from Igor Siwanowics

Puede que en algún momento nos hayamos topado con una imagen en un formato no estándar. Pues bien, aquí os digo brevemente como convertirlas a formato iso en Linux

de bin/cue a iso:

1. Instalamos bchunk: zypper in bchunk
2. Lo ejecutamos: bchunk archivo.bin archivo.cue archivodesalida.iso

de daa a iso:

1. Nos descargamos la versión de PowerISO para Linux: wget http://poweriso.com/poweriso-1.3.tar.gz
2. Lo extraemos: tar xzvf poweriso-1.3.tar.gz
3. Lo ejecutamos: ./poweriso convert archivo.daa -o archivodesalida.iso -ot iso

de uif a iso:
En este caso tenemos dos opciones: usar uif2iso o MagicISO.

1. Instalamos uif2iso (búscalo en build.opensuse.org, ya que no está en los repositorios principales e instala el paquete rpm)
2. Ejecutamos uif2iso archivo.uif archivodesalida.iso

Si no nos funcionase uif2iso, podemos probar con MagicISO (el formato uif es de éste programa). No está disponible para Linux, pero funciona perfectamente bajo Wine.

1. Nos bajamos MagicISO.
2. Instalamos wine: zypper in wine
3. Después instalamos MagicISO: wine Setup_MagicISO.exe
4. Para ejecutarlo hacemos clic en el acceso directo o bien directamente en el archivo uif.
5. Y finalmente convertimos el archivo.uif a iso yendo a «File»→»Save as» o «Tools»→»Convert» e introduciendo los datos que nos piden (ej: nombre del archivo iso de salida).

La imagen iso resultante la podremos montar en algún lado (ej: mount -o loop -t iso9660 image.iso /mnt/) o abrir directamente haciendo clic derecho sobre ella desde Dolphin; Acciones → Examinar ISO. Se nos abrirá una nueva ventana mostrándonos los contenidos de la imagen iso.

También comentar que existe una aplicación muy útil que se llama AcetoneISO. Desafortunadamente, no admite el formato uif pero admite bastantes como, por ejemplo bin, nrg, img, daa o dmg. Está en KDE:Extras

August is a busy month for birthdays!

This all starts with openSUSE, on August 9th. Seven years ago, the development of SUSE Linux opened up and openSUSE was born. The openSUSE project is actually pretty young, compared to the other projects delivering distributions. But it has 20-years old roots... I joined the project in February 2008, and I've seen the community grow and become more and more involved and, more importantly to me, in charge.

On August 15th, we celebrate the birthday of the GNOME project. Miguel announced the GNU Network Object Model Environment Desktop project fifteen years ago. I'm happy the letters in GNOME don't stand for anything anymore ;-) It's been a long ride, with the great GNOME 1.0 release in 1999 (let's be honest, it was crappy by today's standards — I tried GNOME back then, and quickly gave up), the GNOME 2.0 release in 2002 (I joined the project around that time, I still remember the excitement in the community) and the recent GNOME 3.0 release in 2011 (I can't believe I wrote the 3.0 plan more than three years ago already...). Even though I'm less involved nowadays, GNOME is my family.

And finally, on August 16th, Debian reaches a new milestone. In 1993, the imminent release of the first version was announced, which makes the project nineteen years old now. I've always loved Debian, and I've long wondered whether I should become a Debian Developer, but I never made the jump as I chose to focus on upstream activities instead for my free time. And then I joined openSUSE. But it's never too late, so who knows, maybe one day...

I use what those three projects deliver daily, literally. Many thanks to everyone who made and still make this possible!

Hi,

as I already I wrote in an earlier post the last week I worked on implementing osc2’s “request”
command. In order to create a new submit request the user has to run
osc request create --submit api://src_project/src_package api://tgt_project
What’s still needed is a way to specify a revision of the src_package. It isn’t possible
to introduce a “–revision ” option because it’s possible to specify multiple submit
actions for a request (so we can’t distinguish to which –submit action a revision
belongs to).
Finally I implemented darix’ cool idea: simply use a svn-like syntax:
osc request create --submit api://src_project/src_package@rev api://tgt_project

Marcus

Hi,

here’s a small summary of the 12th (coding) week. The last week I continued
the work on the new user interface. As a result the “request” command is more
or less implemented. Yesterday I pushed the current code and it’s also possible
to play around with it:

• checkout the code [1]
• cd osc2/osc/cli
• export PYTHONPATH=/path/to/osc2
• python cli.py -h (for more information)

Example:
In order to list a request it is sufficient to run
“python cli.py request api://your_project” (Note: all https requests are
_insecure_ – so far the certificate etc. is not checked).

Some implementation details:
In my last mail/post I described how a new (sub)command can be specified
so I’ll leave out the details here.
In the following I’ll shortly explain how the arguments specified by the
user at the commandline are passed to a function (which does the actual
work – like listing the requests).

class RequestList(CommandDescription, Request):
    """
    ...
    """
    cmd = 'list'
    args = 'api://project?/package?'
    opt_user = Option('U', 'user', 'list only requests for USER')
    func = call(request.list)

As we can see the project and package parameters are optional. After
the parsing process a so called “info” object is returned which encapsulates
the specified arguments. Assume the user runs “request list api://test_prj”
then the info object has the following attributes:

    info.apiurl = the default apiurl
    info.project = 'test_prj'
    info.package = None

The question is how can we pass this data to the request.list function?
A simple (and naive) approach would be to simply pass the “info” object
to the request.list function that is “list” has the following signature
“def list(info)”. As a consequence inside the method we always have to
use “info.project”, “info.package” etc. which is a bit awkward – at least
for parameters which are quite frequently used in the method definition.

So it would be nice if there’s a way to pass frequently used parameters
directly to the method (that is they’re declared as formal parameters
in the method definition) and infrequently used parameters can still be
accessed via the info object. Exactly like this it is currently
implementend in osc2.

So the following signatures would be correct for our example:

    def list(project, package, info)
    def list(project, package, user)
    def list(project, package, user, info)
    def list(project, info)
    def list(info, project)
    def list(project)  # using the info object is not mandatory
    def list()  # quite useless...
    ...

Invalid signatures:

    def list(prj, pkg, info)
    def list(foo, info)
    ...

So it is up to the developer how to define the signature of the
request.list function – it is not completely dictated by osc:)

Marcus

[1] https://github.com/openSUSE/osc2

MANDRIVA BRASIL (CONECTIVA) contrata profissionais de desenvolvimento e suporte:

1. Profissional de desenvolvimento (kernel). Requisitos: experiência em desenvolvimento e manutenção do kernel de Linux.

2. Profissional de suporte técnico. Requisitos: experiência em suporte técnico interno e externo, conhecimentos avançados no sistema operacional Linux e soluções para servidores: DNS (BIND), web server HTTP/HTTPS (Apache), FTP, SMTP, IMAP, POP3, SQUID, SARG, SAMBA, OpenVPN, LDAP, Firewall e boot remoto. Desejável: Certificação Mandriva ou LPI.

Local de trabalho: Curitiba/Paraná. Jornada: de segunda a sexta-feira, das 09h às 18h. Início: imediato. Benefícios: plano de saúde e odontológico, vale refeição, seguro de vida.

Interessados deverão enviar currículo, com pretensão salarial, para: curriculo_tech@mandriva.com.br.


Fonte: http://br-linux.org/2012/vagas-para-desenvolvimento-e-suporte-na-mandriva-brasil/




Avise se algum erro for encontrado nesse artigo.


O conteúdo desse artigo pode ser modificado ou atualizado, por isso, visite essa página constantemente e mantenha-se atualizado.