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.


Friday
21 November, 2014


face

I bought my wife a "new" old Thinkpad (T400, Core2 duo) to replace her old compaq nc6000 (Pentium M Dothan). Of course I installed it with openSUSE 13.2. Everything works fine. However, we soon found out that it takes ages to boot, something around 50 seconds, which is much more than the old machine (running 13.1 on an IDE SSD vs 13.2 on a cheap SATA SSD in the T400).
Investigating, I found out that in 13.2 the displaymanager.service is now a proper systemd service with all the correct dependencies instead of the old 13.1 xdm init script.
At home, I'm running NIS and autofs for a few NFS shares and an NTP server for the correct time.
The new displaymanager.service waits for timesetting, user account service and remote file systems, which takes lots of time.
So I did:

systemctl disable ypbind.service autofs.service ntpd.service
In order to use them anyway, I created a short NetworkManager dispatcher script which starts / stops the services "manually" if an interface goes up or down.
This brings the startup time (until the lightdm login screen appears) down to less than 11 seconds.
The next thing I found was that the machine would not shut down if an NFS mount was active. This was due to the fact that the interfaces were already shut down before the autofs service was stopped or (later) the NFS mounts were unmounted.
It is totally possible that this is caused by the violation in proper ordering I introduced by the above mentioned hack, but I did not want to go back to slow booting. So I added another hack:

  • create a small script /etc/init.d/before-halt.local which just does umount -a -t nfs -l (a lazy unmount)
  • create a systemd service file /etc/systemd/system/before-halt-local.service which is basically copied from the halt-local.service, then edited to have Before=shutdown.target instead of After=shutdown.target and to refer to the newly created before-halt.local script. Of course I could have skipped the script, but I might later need to add other stuff, so this is more convenient.
  • create the directory /etc/systemd/system/shutdown.target.wants and symlink ../before-halt-local.service into it.
And voila - before all the shutdown stuff starts, the nfs mounts are lazy unmounted and shutdown commences fast.

face

I was never very fond of dracut, but I did not think it would be so totally untested: openSUSE Bug #906592. Executive summary: hibernate will most likely silently corrupt (at least) your root filesystem during resume from disk.
If you are lucky, a later writeback from buffers / cache will "fix" it, but the way dracut resumes the system is definitely broken and I already had the filesystem corrupted on my test VM, while investigating the issue, so it is not only a theoretical problem.

Until this bug is fixed: Do not hibernate on openSUSE 13.2.

Good luck!


face

Postado por Edivaldo
Blog do Edivaldo - Um blog que fala sobre carreira, software, dá dicas e informações do mundo da tecnologia da informação e ainda descomplica o Linux

pale-moon-25-1-0

Foi lançado recentemente o Pale Moon 25.1.0, o navegador que é o Firefox mais rápido que o Firefox. Se você quiser experimentar essa versão, veja a seguir como instalar o Pale Moon 25.1.0 no Linux.

Leia o restante do texto "Como instalar o Pale Moon 25.1.0 no Linux " Continue Reading

Leia o texto original em: Como instalar o Pale Moon 25.1.0 no Linux, no site Blog do Edivaldo.
© 2014 Blog do Edivaldo. Todos os direitos reservados.
O conteúdo deste site pode ser divulgado, desde que a fonte (www.edivaldobrito.com.br) seja citada.
O conteúdo textual original desta página está disponível sob a licença GNU FDL 1.2.
Todas as marcas citadas pertencem aos seus respectivos proprietários. Os direitos autorais de todas as ilustrações pertencem aos respectivos autores, e elas são reproduzidas na intenção de atender ao disposto no art. 46 da Lei 9.610 - se ainda assim alguma delas infringe direito seu, entre em contato para que possamos removê-la imediatamente.


face

¿Quieres conocer las noticias y eventos de la Fundación de Software Libre? Entonces sigue leyendo

FSF_logo

La Fundación para el Software Libre o Free Software Foundation (FSF) es una organización creada en Octubre de 1985 por Richard Stallman y otros entusiastas del software libre con el propósito de difundir este movimiento.

La Fundación para el software libre (FSF) se dedica a eliminar las restricciones sobre la copia, redistribución, entendimiento, y modificación de programas de computadoras. Con este objeto, promociona el desarrollo y uso del software libre en todas las áreas de la computación, pero muy particularmente, ayudando a desarrollar el sistema operativo GNU.

Además de tratar de difundir la filosofía del software libre, y de crear licencias que permitan la difusión de obras y conservando los derechos de autorías, también llevan a cabo diversas campañas de concienciación y para proteger derechos de los usuarios frentes a aquellos que quieren poner restricciones abusivas en cuestiones tecnológicas.

Mensualmente publican un boletín (supporter) con noticias relacionadas con sus campañas, o eventos. Una forma de difundir sus proyectos, para que la gente conozca los hechos, se haga su propia opinión, y tomen partido si creen que la reivindicación es justa!!

El trabajo de traducción del boletín inglés fue realizado por Esteban Mesa, Marc Meseguer, Erbeth, y un servidor de Uds. Realizando labores de recopilación, traducción, y revisión.

Perdón por el retraso, el equipo de traductores teníamos preaparada desde el día 5 de noviembre la edición traducida y revisada, pero problemas ajenos a nosotros han retrasado la salida de la edición en español.

 no_privacy_without_free_software

Puedes ver todos los números publicados en este enlace: http://www.fsf.org/free-software-supporter/free-software-supporter

Aqui te traigo un extracto de algunas de las noticias que ha destacado la FSF este mes de octubre de 2014:

.- Matthew Garrett se une a la junta de directores de la Fundación Para el Software Libre

Del 16 de octubre

Matthew Garrett se une a la junta de directores de la Fundación Para el Software Libre. Matthew Garrett ha ofecido generosamente su tiempo y experiencia para asesorar a la FSF en muchos temas en los últimos años, especialmente en Restricted Boots (Arranque Restringido) y otras tendencias desconcertantes en la intersección de hardware y la distribución de software privativo.

.- Una victoria del software libre sobre el “impuesto de Microsoft”

Del 24 de octubre

La corte suprema de Italia (Corte di Cassazione) ha emitido una sentencia que prohíbe el “impuesto de Microsoft”, una práctica comercial que desalienta a los usuarios de convertir sus PCs a GNU/Linux u otros sistemas operativos libres


face

I had an idea for a long time. Well, my ubunt-o-friends always tell me that Ubuntu is easier because it has Software Center.
Well, I tell them that we have YaST and everything we do, it's through YaST. If something isn't there, there's always the magic URL:

http://software.opensuse.org/find

So I thought why don't create a cool "search engine" with goodies? Since I'm not the perfect guy to do it, I tried to create something using epiphany. As far as I know, epiphany has the feature to save a URL as Web application. So what I did was that:

1. Open this URL



2. Save as web application.




3. Save the icon and the name you prefer. I saved it as market.



4. Now search for market.



5. Search what you want and install it using the feature one click install that YaST provides us.



face



This is an attempt to make a list of things that someone-group of people can follow to develop a healthy community or team. This post is an overview of what I did with Kostas for the Greek openSUSE community.
A small detail is that we were only 2. So we took decisions fast. We didn't have to vote or something.
We had an "advantage" because we have an awesome global community and we asked for something we weren't sure how to proceed.

Let's start:

0. Have a clear goal. What you want to do. Have a big goal that some parts aren't "visible" when you start.
1. Web page: This is the web page-blog that will show information about community, the distro or the project. Make it visible on planets. BE CAREFUL. Don't focus on how to make a great site-blog using personal wordpress, drupal etc. Set it up on blogger and start post articles. You want CONTENT (write an article every other day). Don't spend time to maintain or secure your web page.
2. Mailing list: Ask the project if they can setup for you. If not, then try to find alternatives such as google groups.
3. IRC Channel
4. Forum: Prefer to ask from the project to setup a section for your language. If your project doesn't have forum, then ask a LUG or tech forum to use their's. Do not have your forum setup in your host for the same reasons as before. Don't spend time to maintain or secure the forum.

The above list is the MUST have to start.
A key to everything is to try to have all information in your language, so it'll be "attractive" to people who like the idea of open source but they don't speak English. What's the role of such people? They can organize local events.

Next step is to advertise the whole project-distro. This can happen:
1. Write to blogs-forums (technological or not).
2. Create Facebook group/page and advertise your attempt to other groups/pages.
3. Create Twitter account and tweet news about your community.
4. Create Google Plus Profile/Community.
5. Contact press. First contact local and then national press.
6. If you have a newsletter or weekly magazine, it's good to translate it (or a piece of it), so the open source community in your country will learn about you and your projects.

Before deciding what social media accounts to create, be aware that you have to maintain them. So search the web, what social media is more famous to users. For "tech" users, Google Plus Communities is the perfect place. It also can be used instead of Forums.



A distro or project, it's not all about write code. It's have fun. So advertise it.
1. Release parties. When a new release is out, it's time to party.
2. Meet ups. A good place to organize them is http


face

I'm happy to announce the release of mylvmbackup version 0.16. The source package is now available for download from http://lenzg.net/mylvmbackup/ and https://launchpad.net/mylvmbackup.

Installation packages for a number of platforms can be obtained from the openSUSE Build Service.

Version 0.16 adds support for sending out SNMP traps in case of backup successes or failures. I'd like to thank Alexandre Anriot for contributing this new feature and his patience with me.

Please see the ChangeLog and bzr history for more details.


face

Postado por Edivaldo
Blog do Edivaldo - Um blog que fala sobre carreira, software, dá dicas e informações do mundo da tecnologia da informação e ainda descomplica o Linux

google chrome 39

Foi lançado recentemente o Google Chrome 39, que vem com um monte de mudanças para todas as plataformas. Se você quiser experimentar essa versão, veja aqui como instalar ela no Ubuntu, Linux Mint, Pinguy OS, Elementary OS, LXLE, Linux Lite, Peppermint, Deepin, Debian, Crunchbang, SparkyLinux, Fedora, CentOS, OpenSUSE, Mageia e OpenMandriva.

Leia o restante do texto "Como instalar o Google Chrome 39 no Linux" Continue Reading

Leia o texto original em: Como instalar o Google Chrome 39 no Linux, no site Blog do Edivaldo.
© 2014 Blog do Edivaldo. Todos os direitos reservados.
O conteúdo deste site pode ser divulgado, desde que a fonte (www.edivaldobrito.com.br) seja citada.
O conteúdo textual original desta página está disponível sob a licença GNU FDL 1.2.
Todas as marcas citadas pertencem aos seus respectivos proprietários. Os direitos autorais de todas as ilustrações pertencem aos respectivos autores, e elas são reproduzidas na intenção de atender ao disposto no art. 46 da Lei 9.610 - se ainda assim alguma delas infringe direito seu, entre em contato para que possamos removê-la imediatamente.


face

Richard Stallman recorre el mundo dando conferencias, dando a conocer el software libre y los beneficios de este frente al software privativo.

Ese imparable ciclo de conferencias le trae de nuevo a España este mes de Noviembre y Diciembre de 2014, si tienes la oportunidad, no te lo pierdas!

Según podemos leer en la web de la FSF donde se recoge la agenda de las próximas charlas de Richard Stallman, comprobamos que en su periplo “evangelizador” del software libre de nuevo pasa por España, estas son las fechas:

Si estás cerca y tienes la oportunidad te recomendaría asistir y ver a uno de los grandes del mundo de la informática. La mayoría de las charlas que realizará serán en torno al tema “Por una Sociedad Digital Libre” una charla no técnica de acercamiento a las bases del software libre y porque este es importante para mantener la libertad del usuario, frente al software privativo.

Aqui tienes una muestra de una de sus charlas en España, si no puedes asistir, este puede ser un pequeño reemplazo para sacarte la espinita!

Al igual que memorable es su celebérrimo San iGNUcio de la iglesia de Emacs

—————————————————-



face

KDE tým se nyní zaměřuje na opravování Bugů a dolaďování.
Počítáme s uživateli při hledání bugů a jejich včasné rozmáčknutí.
Vývojáři zkrátka sami nemůžou otestovat všechny možné konfigurace počítačů.
Zvažte proto, že se přidáte do týmu tím, že si nainstalujete betu a budete reportovat každý bug.

Instalace KDE aplikací 14.2 Binárních balíčků

Někteří linuxoví distributoři vřele poskytli binární balíčky KDE aplikací 14.12 Beta 3 (interně 14.11.95) pro některé verze svých distribucí a v dalších případech to udělali dobrovolníci z komunity. Dodatečné binární balíčky stejně jako updaty balíčků jsou už k dispozici, nebo budou k dispozici v následujícíh týdnech. Pro aktuální seznam dostupných balíčků navštivte prosím Community wiki.

Kompilace KDE aplikací 14.2 Beta 3

Kompletní zdroj kódu pro KDE aplikace 14.12 Beta 3 lze volně stáhnout. Instrukce ke kompilaci a instalaci na této info stránce.

Podpora KDE

KDE je svobodný software, který existuje a rozvíjí se díky práci a snažení mnoha dobrovolníků. KDE má zájem o nové dobrovoníky a přispěvovatele at už pomůžou při kódování, hledání bugů, psaní dokumentace, překladů či dalších věcí. Za všechny přispěvovatele jsme velmi vděčni. Staňte se členem KDE tím, že se přidáte k naší nové iniciativě "join the game."

KDE

KDE software existuje v šedesáti jazykových mutacích. Aplikace běží nativně na systémech Linux, Solaris, Windows i Mac OS X.
O prostředí KDE bylo také napsáno v našem průvodci na tomto portále. Mrkněte (česky) ZDE
Originální článek ze kterého bylo čerpáno (anglicky) ZDE


Thursday
20 November, 2014


face

On nokia n900, pulseaudio is needed to have a correct call. Unfortunately that piece of software fights back.

pavel@n900:~$ pulseaudio --start
N: [pulseaudio] main.c: User-configured server at {d3b6d0d847a14a3390b6c41ef280dbac}unix:/run/user/1000/pulse/native, refusing to start/autospawn.
pavel@n900:~$

Ok, I'd really like to avoid complexity of users here. Let me try as root.

root@n900:/home/pavel# pulseaudio --start
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
N: [pulseaudio] main.c: User-configured server at {d3b6d0d847a14a3390b6c41ef280dbac}unix:/run/user/1000/pulse/native, refusing to start/autospawn.

Ok, I don't need per-user sessions, this is cellphone. Lets specify --system.

root@n900:/home/pavel# pulseaudio --start --system
E: [pulseaudio] main.c: --start not supported for system instances.

Yeah, ok.root@n900:/home/pavel# pulseaudio --system
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set!
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set!
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode!
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time!
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that.
W: [pulseaudio] main.c: If you do it nonetheless then it's your own fault if things don't work as expected.
W: [pulseaudio] main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea.

Totally my fault that someone forgot to document this pile of code. Thanks for blaming me. I'd actually like to read what is wrong with that, except that the page referenced does not exist. :-(.


Michael Meeks: 2014-11-20: Thursday

21:00 UTCmember

face
  • Into Cambridge, meeting with Lauren, Laura & Rob. Quarterly mgmt meetings, snatched lunch, board meeting; poked about in the server room; caught up with Daniel and discussed OpenGL funkiness.
  • Train home, stories, dinner, unscrewed various bits, heated the car bumper with a hair dryer (with the air inlet covered to reduce airflow & increase temperature) to make the plastic malleable; pushed out the worst of the dents, glued up the reflectors: much better. Bed.


face

This is my fourth post on Service Design Patterns in Rails. These posts have been inspired by the Service Design Patterns book by Robert Daigneau.

The previous posts were:


The Web Service Evolution patterns talk about what to do to make the API evolve with the minimum breaking changes. What that means? It means that changing your API should not break clients that consume it, otherwise said, that your API is backward compatible.

From this chapter, three patterns apply to the Rails framework:

  • Tolerant Reader
  • Consumer driven contract
  • Versioning

Tolerant Reader refers to the client. It means that if you write a client, you should be "tolerant" on what you get as a response. Rails provides the ActiveResource object. This object will get the response and create an object from it. This object per se is very tolerant.

However, only using that object does not make you tolerant reader. ActiveResource will create a model object like ActiveRecord does. For example, you can have a Product object that inherits from ActiveResource, the same way you would with ActiveRecord

  class Product < ActiveResource
  end

ActiveResource will create an attribute for each attribute found in the response. Thus if you expect a "name" attribute, you would try:

  Product.find(1).name

However, what if name is not in the response? Then, if you really want to be tolerant, you should do

  p = Product.find(1)
  if p.respond_to?(:name)
    p.name
  end

Thus, with little effort you can have a tolerant reader, even thought Rails per se does not fully implement it.
 
Consumer driven contract means testing. Actually, it means having a test suite provided by your consumer on what it expects from the service. Testing is a common good practice in Rails and Rails provides you with a lot of resources for that (rspec, factory girl, stubs, mock ups). You only need to use them to specify what you expect from the API, or what a consumer should expect, depending on whether you are writing the producer or the consumer.

And finally, versioning. Versioning is a very good practice for an API. How you can implement versioning is very well explained on this rails cast, better than I could do myself, so I'd recommend you watching it, to see how to use namespaces in the routes file and in the controller implementation:

 
 
Web Service Evolution patterns are partly implemented on Rails. However, it needs you to do some implementation in order to follow them, because the typical example (the one you would generate with "rails generate") does not implement them, but give you the tools or the base so that you can do it.
 
For example, versioning is not implemented when you generate a new rails application, but you can easily do it with namespacing; tests are not implemented but rails gives you the tools to do so; tolerant reader can be implemented by using ActiveResource and respond_to


face

The last days I played with lcms‘ unbound mode. In unbound mode the CMM can convert colours with negative numbers. That allows to use for instance the LMS colour space, a very basic colour space to the human visual system. As well unbound RGB, linear gamma with sRGB primaries, circulated long time as the new one covers all colour space, a kind of replacement of ICC or WCS style colour management. There are some reservations about that statement, as linear RGB is most often understood as “no additional info needed”, which is not easy to build a flexible CMS upon. During the last days I hacked lcms to write the mpet tag in its device link profiles in order to work inside the Oyranos CMS. The multi processing elements tag type (mpet) contains the internal state of lcms’ transform as a rendering pipeline. This pipeline is able to do unbound colour transforms, if no table based elements are included. The tested device link contained single gamma values and matrixes in its D2B0 mpet tag. The Oyranos image-display application renderd my LMS test pictures correctly, in opposite to the 16-bit integer version. However the speed was decreased by a factor of ~3 with lcms compared to the usual integer math transforms. The most time consuming part might be the pow() call in the equation. It is possible that GPU conversions are much faster, only I am not aware of a implementation of mpet transforms on the GPU.


face

For quite some time I was pretty confident that Weblate will need some UI rewrite at some point. This is always problematic thing for me as I'm no way an UI designer and thus I always hope that somebody else will do that. I've anyway spent few hours on train home from LinuxTag to check what I could do with that.

The first choice for me was to try Twitter Bootstrap as I've quite good experience with using that for UI at work, so I hoped it will work quite well for Weblate as well. The first steps went quite nicely, so I could share first screenshots on Twitter and continue to work on that.

After few days, I'm quite happy with basic parts of the interface, though the most important things (eg. the page for translating) are still missing. But I think it's good time to ask for initial feedback on that.

Main motivation was to unite two tab layout used on main pages, which turned out to be quite confusing as most users did not really get into bottom page of the page and thus did not find important functions available there. So all functions are accessible from top page navigation, either directly or being in menu.

I've also decide to use colors a bit more to indicate the important things. So the progress bars are more visible now (and the same progress bar now indicates status of translation per words). The quality checks also got their severity, which in turn is used to highlight the most critical ones. The theme will probably change a bit (so far it's using default theme as I did not care much to change that).

So let's take a look at following screenshot and let me know your thoughts:

Number of applications over time

You can also try that yourself, everything is developed in the bootstrap branch in our Git repository.

Filed under: English phpMyAdmin SUSE Weblate | 4 comments | Flattr this!


Michal Čihař: Weblate 1.9

16:00 UTC

face

Weblate 1.9 has been released today. It comes with lot of improvements and bug fixes and with experimental Zen mode for editing translations.

Full list of changes for 1.9:

  • Django 1.6 compatibility.
  • No longer maintained compatibility with Django 1.4.
  • Management commands for locking/unlocking translations.
  • Improved support for Qt TS files.
  • Users can now delete their account.
  • Avatars can be disabled.
  • Merged first and last name attributes.
  • Avatars are now fetched and cached server side.
  • Added support for shields.io badge.

You can find more information about Weblate on http://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Ready to run appliances will be soon available in SUSE Studio Gallery.

Weblate is also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far!

Filed under: English phpMyAdmin SUSE Weblate | 0 comments | Flattr this!


face

Same as in past year, I'm attending FOSDEM 2014. This is the best opportunity to meet with free software world in Europe and get in touch with people you know only from mailing lists.

If you want to meet me in person and discuss anything, just get in touch with me and we'll arrange it.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments | Flattr this!


Michal Čihař: Weblate 1.8

16:00 UTC

face

Weblate 1.8 has been released today. It comes with lot of improvements, especially in registration process where you can now use many third party services.

Full list of changes for 1.8:

  • Please check manual for upgrade instructions.
  • Nicer listing of project summary.
  • Better visible options for sharing.
  • More control over anonymous users privileges.
  • Supports login using third party services, check manual for more details.
  • Users can login by email instead of username.
  • Documentation improvements.
  • Improved source strings review.
  • Searching across all units.
  • Better tracking of source strings.
  • Captcha protection for registration.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Ready to run appliances will be soon available in SUSE Studio Gallery.

Weblate is also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far!

Filed under: English SUSE Weblate | 3 comments | Flattr this!


face

Thanks to great amount of changes I've been able do in Weblate during Hackweek, the 1.8 release is quite close.

All features I wanted there are implemented and it is already running for some time on my production servers which look quite stable. The only thing which needs still some improvement are translations. So that's your chance to contribute.

Translation status

If there won't be any blocking issue, Weblate 1.8 will be released during next week.

Filed under: English SUSE Weblate | 0 comments | Flattr this!


face

Θα έχετε δει πολλές δημοσιεύσεις σχετικές. Ίσως όμως όχι τόσο ολοκληρωμένη όσο αυτή.
Με τον όρο Ubunto-ποίηση εννοώ να μοιάζει με το Unity. Οι κινήσεις είναι κυρίως μέσω των extensions. Για να δούμε λοιπόν.

1. Dash to Dock. Την μπάρα dash την εμφανίζει όταν μετακινήσετε τον δρομέα προς τα αριστερά, όταν έχετε ανοικτό το παράθυρο. Όταν δεν έχετε ανοικτό κάποιο παράθυρο, εμφανίζει την μπάρα (σαν το Unity). Μπορείτε να την ρυθμίσετε βέβαια να είναι εμφανής συνέχεια.



2. Status Title Bar. Η μπάρα του τίτλου του παραθύρου, μετακινείται στην μπάρα όπου σας δείχνει ποιά εφαρμογή έχετε ανοικτή-ενεργή.



3. Maximus Two. Εξαφανίζει το Αρχείο, Επεξεργασία κλπ.



Τα 2 και 3, εμφανίζονται κάπως έτσι:


Θεωρητικά αυτό βολεύει όταν έχετε μικρό laptop. Αυτό όμως είναι μια "ανάγκη" των Unitάδων. Τόσα χρόνια ζούσαμε χωρίς αυτό και τώρα προέκυψε στα καλά καθούμενα.

face

Prečo vlastne došlo k zlúčeniu oboch projektov je vysvetlené v príspevku v emailovej konferencii opensuse-factory@opensuse.org.
Vďaka obrovskému zlepšeniu procesu vývoja vo Factory za posledné 2 roky sa v openSUSE reálne ocitli nie jedna, ale dve distribúcie s rolujúcim vydaním. Tumbleweed bolo dovtedy realizované ako rolujúce vydanie založené na poslednom aktuálnom vydaní hlavnej distribúcie. Jeho správca GregKH však naznačil svoj zámer zastaviť projekt. Zdalo sa preto prirodzené rozhodnutie zlúčiť Factory a Tumbleweed, aby sa mohli zjednotiť sily a vytvoriť jedno rolujúce vydanie v rámci openSUSE, ktoré je stabilné a efektívne, ako je to najviac možné.

Následné ponechanie Factory ako čisto „vývojového projektu“, ustanovilo Factory do úlohy vývojovej kódovej základne pre softvér openSUSE, spoločne s Tumbleweed ako distribúciou s rolujúcimi, testovanými aktualizáciami, ktorá je pripravená pre používateľa. Samozrejme aj ISO obrazy, ktoré boli doteraz tvorené pre Factory rolling release, sa už v súčasnosti generujú pod názvom Tumbleweed.

Technické podrobnosti pre existujúcich používateľov Factory a Tumbleweed o tom, aké kroky je potrebné vykonať na plynulý prechod do nového „kombinovaného“ rolujúceho vydania Tumbleweed, sú uvedené v sprievodcovi na wiki stránke openSUSE Tumbleweed.
Sprievodca ukazuje postup prestavenia softvérových repozitárov systému, ako i informácie pre tých, ktorí používajú naviac aj dodatočné repozitáre.

Ferdinand Galko

Použité informačné zdroje:
https://news.opensuse.org/2014/10/24/tumbleweed-factory-rolling-releases...
http://lists.opensuse.org/opensuse-factory/2014-10/msg00646.html
https://en.opensuse.org/SDB:Tumbleweed_Merger


face

I noticed lots of spam in my system logs:

20141120-05:15:01.9 systemd[1]: Starting user-30.slice.
20141120-05:15:01.9 systemd[1]: Created slice user-30.slice.
20141120-05:15:01.9 systemd[1]: Starting User Manager for UID 30...
20141120-05:15:01.9 systemd[1]: Starting Session 1817 of user root.
20141120-05:15:01.9 systemd[1]: Started Session 1817 of user root.
20141120-05:15:01.9 systemd[1]: Starting Session 1816 of user wwwrun.
20141120-05:15:01.9 systemd[1]: Started Session 1816 of user wwwrun.
20141120-05:15:01.9 systemd[22292]: Starting Paths.
20141120-05:15:02.2 systemd[22292]: Reached target Paths.
20141120-05:15:02.2 systemd[22292]: Starting Timers.
20141120-05:15:02.2 systemd[22292]: Reached target Timers.
20141120-05:15:02.2 systemd[22292]: Starting Sockets.
20141120-05:15:02.2 systemd[22292]: Reached target Sockets.
20141120-05:15:02.2 systemd[22292]: Starting Basic System.
20141120-05:15:02.2 systemd[22292]: Reached target Basic System.
20141120-05:15:02.2 systemd[22292]: Starting Default.
20141120-05:15:02.2 systemd[22292]: Reached target Default.
20141120-05:15:02.2 systemd[22292]: Startup finished in 21ms.
20141120-05:15:02.2 systemd[1]: Started User Manager for UID 30.
20141120-05:15:02.2 CRON[22305]: (wwwrun) CMD (/usr/bin/php -f /srv/www/htdocs/owncloud/cron.php)
20141120-05:15:02.4 systemd[1]: Stopping User Manager for UID 30...
20141120-05:15:02.4 systemd[22292]: Stopping Default.
20141120-05:15:02.4 systemd[22292]: Stopped target Default.
20141120-05:15:02.4 systemd[22292]: Stopping Basic System.
20141120-05:15:02.4 systemd[22292]: Stopped target Basic System.
20141120-05:15:02.4 systemd[22292]: Stopping Paths.
20141120-05:15:02.4 systemd[22292]: Stopped target Paths.
20141120-05:15:02.4 systemd[22292]: Stopping Timers.
20141120-05:15:02.4 systemd[22292]: Stopped target Timers.
20141120-05:15:02.4 systemd[22292]: Stopping Sockets.
20141120-05:15:02.4 systemd[22292]: Stopped target Sockets.
20141120-05:15:02.4 systemd[22292]: Starting Shutdown.
20141120-05:15:02.4 systemd[22292]: Reached target Shutdown.
20141120-05:15:02.4 systemd[22292]: Starting Exit the Session...
20141120-05:15:02.4 systemd[22292]: Received SIGRTMIN+24 from PID 22347 (kill).
20141120-05:15:02.4 systemd[1]: Stopped User Manager for UID 30.
20141120-05:15:02.4 systemd[1]: Stopping user-30.slice.
20141120-05:15:02.4 systemd[1]: Removed slice user-30.slice.

This is a server only system. I investigated who is starting and tearing down a sytemd instance for every cronjob, every user login etc.
After some searching, I found that pam_systemd is to blame: it seems to be enabled by default. Looking into the man page of pam_systemd, I could not find anything in it that would be useful on a server system so I disabled it, and pam_gnome_keyring also while I was at it:
pam-config --delete --gnome_keyring --systemd
...and silence returned to my logfiles again.

Wednesday
19 November, 2014


face

Berikut adalah beberapa tips bagi rekan-rekan yang ingin berkomunikasi via email, baik untuk melamar pekerjaan, korespondensi resmi ataupun sebagai bagian dari syarat suatu pendaftaran. Tips ini saya sarikan dari pengalaman menangani email server, termasuk mengamati banyaknya email false positive, yaitu email normal yang ditag sebagai spam oleh anti spam appliance karena satu atau lain hal.

Beberapa hal yang perlu diperhatikan antara lain :

  1. Baca petunjuk cara mengirim email yang diminta. Perhatikan penulisan subject, isi email maupun batasan maksimum jumlah attachment. Jika attachment dibatasi hanya 1 MB misalnya, umumnya email diatas kapasitas tersebut akan otomatis direject. Ingat, perusahaan/lembaga menerima banyak sekali lamaran, jangan sampai lamaran sudah terkena blacklist padahal belum dibaca sama sekali
  2. Sebaiknya Menulis Subject dalam Pola Title Case : Misalnya “Lamaran Pekerjaan Staff IT : Muhammad Rivai Andargini”. Jangan menulis CAPS LOCK alias HURUF KAPITAL semua karena anti spam biasanya memberikan penalti beberapa score point untuk penggunaan huruf kapital
  3. email-logo (1)Gunakan alamat email yang baik dan jangan menggunakan nama yang “nyeleneh”. Meski mungkin ingin menunjukkan jati diri, belum tentu pihak penerima memahami maksud si pengirim, apalagi jika digunakan untuk email komunikasi resmi. Contoh alamat email nyeleneh misalnya : nita_cantique, An4k_4l4y :-)
  4. Selalu isi subject email. Email tanpa subject biasanya terkena blacklist atau dipenalti sebagai spam
  5. Selalu isi body email, minimal kalimat sopan pengantar isi email. Email tanpa body akan menerima beberapa point pemberatan dan dicurigai sebagai spam
  6. Hindari menggunakan attachment dalam format aneh seperti .exe, .scr, .pps dan lain-lain karena biasanya ditumpangi virus. Mail server yang baik otomatis akan memblokir/mereject email dengan attachment tersebut
  7. Hindari menggunakan attachment gambar dalam format .bmp. Ukurannya besar sekali (rata-rata 3 MB). Sebaiknya gunakan .jpg atau .png
  8. Jika menggunakan email yang disediakan gratis oleh penyedia layanan (misalnya Gmail, Hotmail dan Yahoo), sebaiknya gunakan Gmail. Tidak ada statistik valid sih, tapi biasanya koneksi dari dan ke mail server gmail relatif lebih lancar (note, ini rekomendasi pribadi, silakan diabaikan jika merasa kurang sreg, jangan sampai saya dimusuhi oleh Yahoo atau Hotmail gara-gara menulis tips ini :-D)
  9. Jika memungkinkan, gunakan format email Plain Text. artinya tidak ada embel-embel format HTML seperti warna-warni, bold, italic, underline dll. Memang sih format email HTML lebih menarik, namun success rate kiriman lebih rendah daripada format plain text karena sebagian anti spam biasanya memberikan score penalti jika menggunakan format HTML
  10. Hindari attachment dalam format yang tidak umum, apalagi jika dipassword pula . Sebagian anti spam memblock email zip/rar/pdf berpassword. Format PDF sudah cukup standard, tampilan tidak berubah, namun sebaiknya jangan dipassword. Kita kan bukan hendak kirim slip tagihan kartu kredit kita ke perusahaan tempat kita melamar.

Sebagai penutup, tips ini sekedar saran, silakan diikuti dan silakan pula diabaikan, gunakan preferensi pribadi. Saya menulis tips ini karena sejak beberapa hari yang lalu memperhatikan pola pengenalan spam dari beberapa anti spam dan melihat score masing-masing email yang masuk. Siapa tahu bermanfaat.


Michael Meeks: 2014-11-19: Wednesday

21:00 UTCmember

face
  • Into Cambridge taking a machine to return to the server room. Quarterly Productivity Mgmt meetings, frantically prepared slides, crunched numbers etc. Meetings much of the day with a partner meeting in the middle.

face

¿Has instalado openSUSE 13.2? ¿Tienes algunas dudas? Aqui tienes unos cuantos videotutoriales que te ayudarán!

rescue_Geeko

Geeko el camaleón de openSUSE viene al rescate para ayudarte a usar su distribución de GNU/Linux. Echa un vistazo!

Los videotutoriales son una gran herramients para mostrar cómo realizar ciertas tareas. Y aunque openSUSE sea una distribución de GNU/Linux muy sencilla, nunca está de más mostrar cómo realizar ciertas tareas.

Por la red acabo de descubrir un canal de Youtube llamado Geeko Tutorials, donde de momento han subido poco vídeos, pero que sin duda resultan útiles. Puedes acceder a su canal en este enlace:

En ellos se muestra cómo realizar ciertas tareas, nada complicado, tareas sencillas que deben mostrarse a aquellos que son nuevos con la distro. Eso sí, se echa en falta algo de música de fondo que amenice un poco la visión…

Quizás te preguntabas cómo instalar el cliente de OwnCloud (cosa que has visto en mi blog ;) ) o cómo cambiar la opción por defecto en el Grub, cómo instalar Chromium, etc… todo eso y mucho más lo tienes en el canal!

Además también tienen cuenta en G+ y Tuiter.

Os dejo con uno de los vídeos como muestra, pero antes de eso quiero recomendaros el artículo que desde la web “La sombra del helicóptero” ha realizado para dar un repaso a openSUSE 13.2

Para aquellos que estáis indecisos, quizás esta revisión de los puntos fuertes y débiles realizada por Enrique pueda ayudaros a decidiros. Podéis leer el artículo en este enlace:

Y ahora sí un vídeo de muestra de cómo instalar VLC y los codecs multimedia realizado por Geeko Tutorials

——————————————————–



Tuesday
18 November, 2014


Michael Meeks: 2014-11-18: Tuesday

21:00 UTCmember

face
  • Chewed away at master, GL rendering, texture and context lifecycle, chased misc. rendering problems. Mail catchup. Worked late.

face

Weblate has started as a translation system tightly bound to Git version control system. This was in no means design decision, but rather it was the version control I've used. But this has shown not to be sufficient and other systems were requested as well. And Mercurial is first of them to be supported.

Weblate 2.0 already had separated VCS layer and adding another system to that is quite easy if you know the VCS you're adding. Unfortunately this wasn't the case for me with Mercurial as I've never used it for anything more serious than cloning a repository, committing fixes and pushing it back. Weblate needs a bit more than that, especially in regard to remote branches. But nevertheless I've figured out all operations and the implementation is ready in our Git.

In case somebody is interested in adding support for another version control, patches are always welcome!

Filed under: English phpMyAdmin SUSE Weblate | 0 comments | Flattr this!


face

Setelah proses mendapatkan iso firmware dan HP Service Pack for Proliant (SSP), saya siap melakukan proses update firmware. Untuk melakukan update firmware ini, saya melakukannya 2x. Yang pertama menggunakan DVD yang berisi hasil burning file firmware-10.10-0.iso. Berikut adalah langkah-langkahnya :

  1. Hidupkan server dengan posisi boot via CD/DVD ROM
  2. Karena tidak mau repot, saat pilihan pertama, saya pilih automatic (bertolak belakang dengan tampilan screenshot dibawah ini :-D) :
    vavai-update-firmware1
  3. Tunggu hingga update firmware selesai dijalankan. Prosesnya butuh waktu sekitar 5-15 menit
  4. Setelah selesai, restart server dan jangan lupa keluarkan DVD firmware yang sebelumnya dimasukkan

Setelah update firmware tahap 1, saya melakukan update ulang menggunakan DVD Service Pack for Proliant (SSP) versi 2014.06.0. Kali ini saya berusaha menjadi SysAdmin sejati dengan memilih menu interactive :-D. Berikut adalah beberapa screenshot yang saya ambil siapa tahu bisa membantu sebagai gambaran prosesnya. Mohon maaf kalau foto-nya agak miring karena tangan saya kesemutan (ahlesyan :-P)

vavai-update-firmware2

vavai-update-firmware3

vavai-update-firmware4

vavai-update-firmware5

Setelah proses update, saya melakukan restart server dan menggunakan CD/DVD HP Start Smart untuk melakukan konfigurasi RAID storage. Berikut adalah prosesnya :

20141116_091211

Setelah booting dan masuk ke menu, pilih menu Maintenance

20141116_091413

Pada pilihan berikutnya, pilih menu HP Array Configuration and Diagnostics

20141116_091446

Pada pilihan Select an available device, pilih RAID Controller yang tersedia

20141116_091509Pada menu Available Tasks, pilih menu Controller settings, Arracy Accelerator Settings dan Physical Driver Write Cache Settings, kemudian aktifkan write cache ratio dan nobatterywritecache pada masing-masing pilihan yang tersedia. Lihat screenshot berikut untuk gambar lebih jelas.

20141116_091541

20141116_091550

20141116_091603

20141116_091614

Sebagai tambahan informasi, pilihan nobatterywritecache bisa diaktifkan, namun HP akan memperingatkan bahwa jika tiba-tiba power off, data yang sedang diproses bisa jadi akan hilang karena tidak disimpan sementara di battery backup. Artinya, jika pilihan ini dijalankan, pastikan server dilindungi oleh UPS dari kemungkinan mati listrik mendadak.

Contoh diatas saya menggunakan skema RAID-0. Ini hanya ilustrasi, rekomendasinya adalah menggunakan RAID 1+0 untuk production server, terutama untuk data yang sifatnya penting.

Berikut adalah hasil test kecepatan setelah proses update firmware, dengan menggunakan perintah yang ada di artikel ini : Tips Mengecek Kecepatan dan Performa Baca-Tulis Harddisk

vavai-hp-proliant-write-performance


face

Salah satu masalah utama pada 2 unit server HP Proliant ML 370 G5 yang tiba di markas Excellent beberapa waktu yang lalu adalah lambatnya akses write pada harddisk yang menggunakan RAID Controller P400. Masya kecepatan write hanya 4 MB/s??

Saya sudah coba menggunakan beberapa kombinasi baik RAID 1+0, RAID 5, RAID 1 bahkan RAID 0, hasilnya tetap poor performance. Saat mengeceknya menggunakan HP Smart Start maupun HP ACUCLI, diketahui bahwa kombinasi cache ratio = 100% read, 0% write, pantas saja kemampuan write-nya ngeselin :-P.

Saat saya coba aktifkan pilihan nobatterywritecache dan mengubah pilihan cache ratio via hpacucli dengan perintah :

controller slot=1 modify nobatterywritecache=enable
ctrl slot=1 modify cacheratio=25/75

Pesan errornya adalah bahwa perintah kedua tidak bisa diterapkan. Baca-baca literatur lebih detail, untuk meningkatkan kecepatan write, rekomendasinya adalah menambahkan BBWC alias Battery Backup Write Cache, yang sialnya tidak include didalam server yang saya beli ini.

logo

Saya sudah hendak menyerah dan berniat membeli BBWC di Ebay atau Amazon namun sempat terpikir, kenapa tidak mencoba update firmware, siapa tahu bisa jadi clue untuk perbaikan performa. Akhirnya saya coba download HP Service Pack for Proliant (SSP). Saat tulisan ini saya buat dan saat saya lagi oprek server tersebut, versi SSP terbaru adalah 2014.09.0, yang sialnya, sudah tidak lagi support HP server Proliant G5. Saya coba cari di archive SSP, versi terakhir yang support Server Proliant G5 adalah SSP versi 2014.06.0. Okelah, saya akan coba download file iso ini yang berukuran sekitar 3.5 GB.

Masalah berikutnya muncul. Untuk download SSP, HP meminta syarat adanya garansi/support yang masih berlaku. Lha ini server lama, sudah tidak ada garansi support lagi. Akhirnya saya coba cari di Google dan mendapatkannya. Untuk mendapatkannyapun mesti berjuang, saya mesti mendownloadnya via server cloud Excellent yang ada di Singapore karena download langsung dari markas Excellent lambat sekali.

hp-ml-370-g5

SSP sudah didapatkan, saat dijalankan ternyata tidak berjalan secara normal, dalam arti tidak mau melakukan update firmware. Saya sempat membaca dari beberapa referensi, ternyata saya mesti melakukan update dulu menggunakan file ISO lainnya, nama file iso-nya : firmware-10.10-0.iso. File ini saya dapatkan dari browsing di Google dan saya download via server cloud Excellent yang ada di Singapore kemudian baru saya download via server Jakarta dan Bekasi.

Setelah kedua file ISO tersebut saya dapatkan, saya burning ke DVD dan saya siap melakukan update firmware. Perjalanan yang panjang hanya untuk update firmware, tapi saya no retreat no surrender ;-). Seperti moto openSUSE : Have a lot of fun :-D

Tulisan ini akan berlanjut ke bagian kedua, karena saya butuh mengumpulkan screenshot :-)

Bagian kedua tulisan ini bisa dibaca disini : Update Firmware pada Server HP/Compaq Proliant-Bagian 2

<- Current blog entries