Skip to main content

the avatar of Sankar P

Offended

As some of you might know, I am a Vegan and I saw the error codes http://en.wikipedia.org/wiki/0xDEADBEEF#Magic_debug_values and was shocked to see code like 0xDEADBEEF

I am offended by this. Cow is a holy god in our Hindu/Jain religions and killing of it is banned in our faith. Such constants make the code more offensive to a nation of a billion people (India). So, I am going to ask everyone to remove such constants.

Also, I noticed that Christopher Blizaard's website is http://www.0xdeadbeef.com/ This is indeed offensive and I am going to ask him to change his website. His blog's feed is in many planets and I don't want to see that word, when I hover over a link.

Also, I should ask to get the planet Uranus renamed.

Mentioning beef may sound a simple thing to you. But such things makes Vegans feel insecure wondering if the whole development activity is for meat-eaters only.

#satire #reductioadabsurdum?

---

Will I write such a code ? 
No
Is it in good taste ? 
Probably Not, for the majority of people.
Will I get offended on seeing such a code ? 
If I do, I will have to lose my sleep over everything.

Calling "[Microsoft] managed to make the kernel more offensive to half the population" is too much of an over-reaction, to, what is just a lame joke of a programmer trying to be funny. There is no need to drag Microsoft's name here, for the same reason, why we don't accuse The Linux Foundation of propagating male supremacy ideas, when Linus Torvalds says "Do you pine for the days when men were men and wrote their own device drivers?"

Inspiration for the post: http://mjg59.dreamwidth.org/14955.html  

I stumbled onto the comments section and found that someone has posted the exact same thing as this blogpost, that I had in mind. World is in indeed small. Sadly no idea who made the comment.

Disclaimer: All opinions expressed are purely personal and do not represent my employer.

the avatar of Vincent Untz

Moving on to something completely different

Last month, I got a new job! After three years in the openSUSE Boosters team, I joined the SUSE Cloud team. I'm now working on OpenStack and on SUSE Cloud itself. Quite a big change!

I had planned a long time ago that the release of GNOME 3.0 would be a good time for me to look at what's next. When it went out, I actually took a few months to cool down a bit (it was pretty much needed), and also have some good fun with openSUSE. But after a while, this desire of trying something new came back: I had been working on the desktop for nearly ten years, and on a distribution for four years. Those were exciting years, but at the end, it started to feel like, you know, work. I wanted to stay involved in GNOME, in the free desktop in general, in openSUSE, in cross-distro collaboration: this is not just work and this should not be just work. I didn't want to slowly move to doing stuff while not caring anymore. This is how I found out that I needed to go back to the early days and contribute in my free time again :-)

There was still the question of, well, work. I started looking around, and I had some good discussions with several people about what to do next (thanks to everyone who took some time for this!). i must admit I changed my mind several times. I was not necessarily looking for a developer position (quite the contrary, actually), as I knew that for me to be motivated for a new project as a developer, the project had to be one that I could care about, one that has a free software community around it and one that would get me out of my comfort zone (so not on the desktop nor on a distro) — yeah, not easy :-) But at some point, SUSE had this cool developer position related to OpenStack. Good timing. (Btw, we're still hiring!)

It's been great so far; of course, you need to ignore the buzz words ;-) I wanted a new challenge and I wanted to get out of my comfort zone, I got served: new project, new community, new code, etc. It didn't help that the hard disk in my laptop decided it was the perfect moment to die, and that Lenovo took weeks to send me a replacement disk (finally got it yesterday). But now I'm all set, so let's have fun!

the avatar of Sascha Peilicke

a silhouette of a person's head and shoulders, used as a default avatar

Ative e use o IPv6


Ativando o IPv6 em seu sistema operacional

O IPv6 já vem habilitado por padrão nos sistemas operacionais modernos. Se você têm uma versão atualizada de Windows, Linux, MacOS ou BSD, o IPv6 estará ativado.

As páginas a seguir mostram como verificar se esse é seu caso, e ativar o IPv6, se for preciso:

Obtendo conectividade IPv6 e usando o novo protocolo

Uma vez que o IPv6 esteja ativo, caso seu provedor de acesso Internet já suporte IPv6, a configuração do seu computador provavelmente se dará de forma automática. Consulte seu provedor e pergunte se ele já tem IPv6. Se não tiver, pergunte quando terá!

A maior parte dos provedores de acesso no Brasil (em 2012) ainda não ativam o IPv6 para usuários domésticos.

Se você quiser testar o novo protocolo, sua melhor alternativa é usar um serviço gratuito de túneis, chamado de Tunnel Broker, para obter conectividade. Há três opções que recomendamos, e as instruções estão nos links a seguir. Os melhores resultados à partir do Brasil são obtidos com a primeira opção, o SixXS:



Link de Referência: http://ipv6.br/entenda/ative/





Lembre-se, sempre:


De acompanhar o Cronograma de implantação do IPv6 no Brasil:

http://ipv6.br/cronograma/





E verifique se o seu sistema operacional ou equipamento de rede, suporta o IPv6:

IPv6 support Ready Logo Phase 2

http://www.ipv6ready.org/?page=phase-2

http://www.ipv6ready.org/?page=phase-2-about




E também, faça os:



Testes IPv6



Quer saber se seu computador já opera com IPv6? Utilize este teste: http://test-ipv6.com.br.



Quer saber se um site na internet já está usando o IPv6? Utilize este teste: http://validador.ipv6.br.







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.

a silhouette of a person's head and shoulders, used as a default avatar

Quando for escolher alguma distribuição (distro) Linux ou alguma certificação Linux, preste atenção se a distro ou certificação segue os 4 (quatro) principais padrões e normas do Software Livre.

Padrões e normas (sempre, com o suporte completo, com total compatibilidade e usando versões atualizadas e estáveis):   

   



1 - LSB x86-64 4.x (ou superior):

https://wiki.linuxfoundation.org/en/LSB_Roadmap

http://www.linuxfoundation.org/collaborate/workgroups/lsb



O SUSE, Red Hat, entre outros, estão na listagem:

https://www.linuxbase.org/lsb-cert/productdir.php?by_lsb








2 - GPL 3:

http://www.gnu.org/licenses/gpl.html







3 - IPv6 support Ready Logo Phase 2:

http://www.ipv6ready.org/?page=phase-2

http://www.ipv6ready.org/?page=phase-2-about



Red Hat, Kernel.org, NEC, NTT, Motorola, entre outros, estão na listagem:

https://www.ipv6ready.org/db/index.php/public/search/?do=1&lim=25&o=14



O SUSE, HP, Oracle, Cisco, Xerox, entre outros, também:

https://www.ipv6ready.org/db/index.php/public/search/?c=US&ap=2&o=3&do=1&lim=25&p=10



E o CentOS Linux (http://en.wikipedia.org/wiki/CentOS, baseado no Red Hat Enterprise Linux, RHEL: https://www.redhat.com/products/enterprise-linux-add-ons/extended-lifecycle-support/):

http://wiki.centos.org/About/Product







4 - LPI: 






LPIC-1:

http://www.lpi.org/linux-certifications/programs/lpic-1


LPIC-2:

http://www.lpi.org/linux-certifications/programs/lpic-2



LPIC-3:

http://www.lpi.org/linux-certifications/programs/lpic-3







Observações:


openSUSE Linux 12.1, não segue: o LSB x86-64 4.x (ou superior) e o IPv6 support Ready Logo Phase 2, o suporte ao IPv6 ainda é limitado (http://en.opensuse.org/SDB:Native_IPv6), mais na versão 12.2 deve melhorar.   





openSUSE Linux 12.1, não possui o AppArmor instalado por padrão, depois do Firewall (SuSEfirewall2: http://en.opensuse.org/openSUSE:Security_Features#Firewall, Fedora Firewall: http://fedoraproject.org/wiki/SystemConfig/firewall, http://fedoraproject.org/wiki/FirewallD, http://fedoraproject.org/wiki/Features/firewalld-default, http://fedoraproject.org/wiki/Features/DynamicFirewall, Mandriva Firewall: http://wiki.mandriva.com/en/Interactive_Firewall, Shorewall Firewall: http://www.shorewall.net/, Ubuntu Firewall: https://help.ubuntu.com/8.04/serverguide/firewall.html, https://wiki.ubuntu.com/BasicSecurity#Firewall, https://wiki.ubuntu.com/UncomplicatedFirewall, http://gufw.tuxfamily.org/ e o Firewall Builder: http://www.fwbuilder.org/), o AppArmor é uma ferramenta importante:

http://en.opensuse.org/FAQ#AppArmor



Security features

http://en.wikipedia.org/wiki/Comparison_of_Linux_distributions#Security_features











O AppArmor funciona tipo o SELinux (http://fedoraproject.org/wiki/Security/Features#SELinux
Já o Security Overview (http://doc.opensuse.org/documentation/html/openSUSE/opensuse-security/cha.security.yast_security.html#sec.security.yast_security.overview e http://www.suse.com/documentation/sles11/singlehtml/book_security/book_security.html#sec.yast_security.overview), funciona tipo o Msec (http://wiki.mandriva.com/en/Msec), a ordem é essa: 1 - Firewall, 2 - Security Overview e 3 - AppArmor, eu não citei o Security Overview antes, porque o Security Overview já vem instalado e configurado por padrão.




Essas ferramentas de segurança, usadas em conjunto com outras ferramentas de privacidade, como o BleachBit (http://bleachbit.sourceforge.net/) e o Tor (https://www.torproject.org/), te garantem segurança e privacidade ao mesmo tempo.







SUSE Linux Enterprise 11 SP2, não suporta o sistema de arquivos EXT4 (http://en.wikipedia.org/wiki/Ext4) que é o mais atual e estável, pelo menos suporta de forma experimental o futuro Btrfs (http://en.wikipedia.org/wiki/Btrfs), o Btrfs é atual mais ainda não é estável: http://www.suse.com/products/server/technical-information/ e http://distrowatch.com/table.php?distribution=sle







Dicas e sugestões:


Use o Texas Flood Boot System do Resulinux (http://pt.wikipedia.org/wiki/Resulinux) em alternativa ao SYSVINIT, para aumentar a velocidade do boot.  


Use o Kernel 3.5 ou superior: http://www.kernel.org/ e http://kernelnewbies.org/Linux_3.5


Seja uma distribuição Linux, Rolling release: http://en.wikipedia.org/wiki/Rolling_release


Vencendo o comando da morte: http://www.linuxtotal.org/viewtopic.php?f=6&t=246


Adicionar suporte e ter preferência, ao hardware e as distribuições Linux, que tenham suporte as arquiteturas de processadores: ARM (http://en.wikipedia.org/wiki/ARM_architecture) e x86-64 (http://en.wikipedia.org/wiki/X86-64).


Adicionar suporte ao MPLS VPN (http://en.wikipedia.org/wiki/MPLS_VPN) com suporte ao IPv6 (http://ipv6.br/), o 6VPE (http://sourceforge.net/apps/mediawiki/mpls-linux/index.php?title=Main_Page, http://www.lume.ufrgs.br/handle/10183/37170, http://ipv6.br/entenda/transicao/#tecnicas-6pe, https://sites.google.com/site/amitsciscozone/home/important-tips/mpls-wiki/6vpe-ipv6-over-mpls-vpn, http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_8-2/ipv6.html, http://www.ipflow.utc.fr/index.php/6VPE_-_IPv6_VPN_over_MPLS e http://eng.registro.br/pipermail/gter/2008-December/020916.html).


Use as ferramentas de manutenção do Parted Magic: http://partedmagic.com





Vamos esperar o openSUSE Linux 12.2 (http://en.opensuse.org/Main_Page) e o SUSE Linux Enterprise 12 (http://www.suse.com/products/server/), para ver se a situação melhora.







Sobre o:


openSUSE Linux 12.2: http://en.opensuse.org/openSUSE:Major_features, http://en.opensuse.org/openSUSE:Roadmap e http://www.susebr.org/forum/index.php


Fedora Linux 18: http://fedoraproject.org/wiki/Releases/18/FeatureList, http://fedoraproject.org/wiki/Releases/18/Schedule e http://projetofedora.org/


Mandriva Linux 2012: http://wiki.mandriva.com/en/2012_Development, http://blog.mandriva.com/br/ e http://www.mandrivabrasil.org/site/


Ubuntu Linux 12.10: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule, http://www.ubuntu-br.org/ e http://ubuntuforum-br.org/




Entre outras distros Linux, que não seguem os principais padrões e normas ou falta algum recurso importante para o sistema operacional.











LDP-BR Projeto de Documentação do Linux - Brasil:

Site oficial: http://trac.watter.net/ldp-br/wiki


Lista de E-mails do LDP-Brasil:

https://lists.sourceforge.net/lists/listinfo/ldpbr-translation








Boas práticas para peering no PTTMetro:

http://www.slideshare.net/LuisBalbinot/boas-prticas-para-peering-no-pttmetro






PTT.br - Infraestrutura Crítica - São Paulo - 5º PTT Fórum - 29 Nov 2011 (Espero que essa solução definitiva, prevista para 2014, se estenda a todos os PTTMetro (http://ptt.br/) em todo o Brasil):

http://ptt.br/doc/pttforum/5/ptt.br.5pttforum.infraestrutura_critica_spo.20111129.pdf








Cartilha de Segurança para Internet:

http://cartilha.cert.br/








Faça como o Comitê Gestor da Internet no Brasil (CGIbr, http://www.cgi.br/regulamentacao/resolucao2012-003.htm), seja contra o: SOPA (http://pt.wikipedia.org/wiki/Stop_Online_Piracy_Act) e também seja contra o: PIPA (http://pt.wikipedia.org/wiki/PROTECT_IP_Act) e ACTA (http://pt.wikipedia.org/wiki/Acordo_Comercial_Anticontrafa%C3%A7%C3%A3o), ou qualquer outra coisa que tire qualquer tipo de liberdade da internet, pois a internet tem que ser livre em todos os sentidos.







Atualização:


Participem da discussão aqui (a FSF faz a sua parte e nós temos que fazer a nossa parte, e também, eu não faço spam, flame, trolagem, vaporware, marketing ou merchandising, de site, blog, distro, fórum, apenas quero discutir esses assuntos com todos, melhorando o que existi, que são todas as distribuições Linux, que tecnicamente, falta muita coisa, pelo menos para a maioria das distros, pois ranking de popularidade de sites como DistroWatch http://distrowatch.com/ ou tradição http://futurist.se/gldt/, não garantem qualidade, o que garante qualidade é ter o que eu falei aqui, e as distros que mais se aproximam da garantia de qualidade, que também precisam melhorar, as versões Desktop Free/Pago e Enterprise Free/Pago, são essas: Fedora Linux, Mandriva Linux e openSUSE Linux):    

http://ubuntuforum-br.org/index.php?topic=98247


ARM no openSUSE Linux: http://en.opensuse.org/Portal:ARM








Avise se algum erro for encontrado nesse artigo.


O conteúdo desse artigo pode ser modificado ou atualizado, por isso, visite essa página (http://genixinfo.blogspot.com.br/2012/07/quando-for-escolher-alguma-distribuicao.html) constantemente e mantenha-se atualizado.
a silhouette of a person's head and shoulders, used as a default avatar

Midterm completed


I successfully completed my midterm evaluation, its awesome! I just can't stop staring at that figure in my account :D


Till now, I have completed integration of Karma with Twitter, Bugzilla, planet openSUSE and Build service. The Build service part though complete, still needs modifications due to some troubles in the approach that I am following. Using the api and getting commit history or parsing the changes file associated with each package both have some side effects. So I'm still looking for a better solution.


Then I also have plans to reward people on forums. People providing technical help to others deserve to be rewarded I think. Though I haven't researched on how to go about it, so I won't commit anything but lets  hope it works out.


And karma plugin is deployed on Connect and working, so pull in that widget on your dashboard or your profile and have fun. I made a post about the karma widget not working but I completely forgot to post about the issue being resolved, my bad :)


So try it out, and please let me if you like it or dislike it even or leave any suggestion for me, if you think I can make it better in any way.


You can even check my code at Karma. Let me know what you feel.

a silhouette of a person's head and shoulders, used as a default avatar

[gsoc] osc2 client – summary of week 8

Hi,

here’s a small summary of the 8th (coding) week. The last days I
was working on getting build support into the osc2 library. I just
checked in a BuildInfo and Builder class (+ testcases). Here’s a
brief example how they can be used:

# example how to use the Builder class
builder = Builder(su_cmd=Builder.SUDO, root='/var/tmp/build-root')
builder.rpmlist = '/path/to/rpmlist'
builder.dist = '/path/to/buildconfig'
builder.without = 'feature1'
builder.without += 'feature2'
builder.arch = 'x86_64'
# run the build:
builder.run('/path/to/osc.spec')
# this executes:
sudo /usr/bin/build --arch x86_64 --dist /path/to/buildconfig \
   --root /var/tmp/build-root --rpmlist /path/to/rpmlist \
   --without feature1 --without feature2 /path/to/osc.spec

Basically Builder is just a wrapper around the build script
(all options will be passed to the build script; if an option contains
a “-” character like “vm-type” it can be set like this:
“binfo.vm_type = ‘xen'” (a “_” will be replaced with “-“)).

Additionally here’s a small example how to utilize the BuildInfo
class:

# fname is a path to a spec file
binfo = BuildInfo('openSUSE:Tools', 'osc', 'openSUSE_Factory', 'x86_64',
                  filename=fname)
# print preinstall packages
for bdep in binfo.preinstall():
    print bdep.get('name'), bdep.get('version')
# save binfo xml in a file
binfo.write_to('/path/to/file.xml')

The next thing on my TODO is the fetcher and cachemanager code.

Marcus

the avatar of George Bratsos

openSUSE 12.2 RC1!


Το openSUSE 12.2 Release Candidate 1 είναι πλέον διαθέσιμο για να το κατεβάσετε.

Αποκτήστε το!

Κατεβάστε το από το software.opensuse.org/developer. Ως συνήθως, μια λίστα από τα πιο ενοχλητικά σφάλματα διατηρείται και μπορείτε να τη δείτε και / ή να υποβάλετε ένα νέο στο Bugzilla.

Αναβαθμίσεις!

Από τη Beta 2, οι ακόλουθες αλλαγές έχουν γίνει:

Ο grub2 ενημερώθηκε στη 2,0 τελική έκδοση. Το branding του επίσης ενημερώθηκε. Υπήρξαν διορθώσεις για το udev, και τα udisks και udisks2 για την απόκρυψη των LVM κατατμήσεων RAID και έγιναν πολλές διορθώσεις στο autofs. Πολλές διορθώσεις ήρθαν στο systemd.

Πολλά πακέτα περιλαμβάνουν τώρα systemd αρχεία εγγενώς, και έτσι αυτά αφαιρέθηκαν από το ίδιο το πακέτο του systemd, για παράδειγμα για το Plymouth, το οποίο έχει ενημερωθεί στην έκδοση 0.8.5.1. όπου το rpm καλεί τώρα το systemctl daemon-reload όταν εγκαθιστά νέα init scripts.

Στον τομέα της διαχείρισης των πακέτων, το zypper ενημερώθηκε στην έκδοση 1.7.3, φέρνοντας καλύτερο καθαρισμό και υποστήριξη για διπλό πλάτος γραμματοσειράς. Το OSC, ο Open Build Service πελάτης, αναβαθμίστηκε στην έκδοση 0.135.1, με πολλές διορθώσεις και προσθέτοντας πακέτα στήριξης για archlinux. Στο YaST UI διορθώθηκε ένα segfault.

Ενημερώθηκε ο gcc στην έκδοση 4.7.1, διορθώνοντας πολλά σφάλματα του gcc47. Ενημέρωση για το automake στην έκδοση 1.12.1 επίσης διορθώνοντας επίσης αρκετά σφάλματα. Αναβαθμίστηκε και το OpenJDK, στην έκδοση 1.7.0. Το vim είναι τώρα στο 566 patchlevel με πολλές μικρότερες διορθώσεις. Το Kiwi, που χρησιμοποιείται στη διαδικασία δημιουργίας εικόνας λογισμικού, έλαβε επίσης πολλές διορθώσεις που του επιτρέπει πιο αξιόπιστη ανάπτυξη στο openSUSE 12.2.

To ALSA έχει λάβει πολλές μικρές διορθώσεις, και ένα segfault βρέθηκε και διορθώθηκε. Ενημερώσεις έγιναν σε μεγάλο αριθμό των πακέτων, μια μικρή επιλογή είναι τα VirtualBox, nmap, R, pango, Go, phpmyadmin, vym, aria2, GnuTLS, mariadb και jedit. Το Xorg είναι τώρα στη τελευταία έκδοση 1.12.3, και πολλές διορθώσεις έγιναν στα πακέτα του πηγαίου κώδικα.

Tα μεγάλα γραφικά περιβάλλοντα εργασίας ενημερώθηκαν επίσης.

Το KDE έχει ενημερωθεί στην τελευταία έκδοση, 4.8.4, φέρνοντας βελτιώσεις σε ολόκληρη την επιφάνεια εργασίας. Ένα σοβαρό πρόβλημα με το Soprano που επηρεάζει πολλά προγράμματα του KDE έχει επιλυθεί.

Στο GNOME έγιναν πολλές μικρές διορθώσεις. Τα Empathy, Tracker, Pidgin, Rhythmbox, gnome-bluetooth, έλαβαν σημαντικές ενημερώσεις.

Το Lxpanel του LXDE έχει ενημερωθεί στην έκδοση 0.5.1, και διορθώθηκε ένα σφάλμα στο xfdesktop του XFCE.

Το LibreOffice βρίσκεται τώρα στην έκδοση 3.5.4.6, ένα πρόβλημα στο Gimp βρέθηκε και διορθώθηκε, ο Chromium αναβαθμίστηκε στην έκδοση 22.0.1190, και έγιναν διορθώσεις στο εικονίδιο του Scribus για τη βελτίωση στη χρήση του στο GNOME.

Επόμενα βήματα!

Στο μήνα Αύγουστο θα δείτε εντατικές διορθώσεις σφαλμάτων, οπότε δοκιμάστε και αναφέρετε σφάλματα. Η τελική έκδοση έχει προγραμματιστεί για τα μέσα Σεπτεμβρίου και η RC2 θα είναι διαθέσιμη στις 2 Αυγούστου.

Οι συσκευαστές και οι δοκιμαστές θα πρέπει να γνωρίζουν ότι η ανάπτυξη του openSUSE 12.2 γίνεται στο δικό του branch, έτσι το Factory είναι πολύ μπροστά από το 12.2. Το δημόσιο 12.2 αποθετήριο θα ενημερωθεί στη συνέχεια με την RC2 και οι αναβαθμίσεις θα είναι διαθέσιμες σαν online ενημερώσεις.

Αλλαγές στο μοντέλο ανάπτυξης για το openSUSE θα εξακολουθήσουν να συζητούνται στην λίστα openSUSE-factory.

a silhouette of a person's head and shoulders, used as a default avatar

a silhouette of a person's head and shoulders, used as a default avatar