CarlosRibeiroColeção de posters openSUSE 12.1!
Coleção de posters openSUSE 12.1!
Estamos a menos de uma semana do lançamento do openSUSE 12.1, e para contribuir com as pessoas que vão celebrar esta data, compartilho os posters que crie junto com aos demais participantes do openSUSE Hackweek - Los Angeles, material este que foi adaptado em seus respectivos conteúdos para o momento atual. Este material é a tradução do material original em ingles, para o portugues utilizado no Brasil e será utilizado de apoio durante as eventuais festas de lançamento que ocorreram ao redor do mundo! onde o idioma utilizado for o portugues, podendo então ser impresso, compartilhado, e utilizado conforme o necessário.
O material está divido em três posters com conteúdos bem distintos e diversificados entre eles possibilitando ser utlizados nas mais diversas ocasiões. para os mais diversos níveis de audiencia. Segue os materias:
O Tumbleweed visa proporcionar atualizações evolutivas de versão do openSUSE contendo as últimas versões estáveis ao invés de observar ciclos de lançamentos periódicos rígidos de qualquer distribuição. O projeto faz isto para os usuários que querem ter os software mais recentes, porém estáveis.
O OBS é uma plataforma para desenvolvimento de distribuições que oferece aos desenvolvedores uma infraestrutura transparente para o empacotamento de aplicativos para a maioria das distribuições que incluem mas não são limitadas a debian, fedora, redhat, suse, x86, 64 bits, arm, ... A instância do openSUSE atualmente tem mais de 20.000 usuários e existe mais de 100.000 pacotes para 21 distribuições base e 6 arquiteturas. Já o STUDIO é uma interface web, facil de usar, construir e testar seu prõprio sistema operacional, sem a necessidade de conhencimentos tecnicos ou avançados.
Neste material deixamos algumas informações referentes a flexibilidade de escolha de desktop no openSUSE 12.1, alẽm de informações sobre formas e maneitas de entrar em contato ou de se aproximar das comunidades do projeto openSUSE.
Todas as imagens e conteúdos compartilhados aqui foram criadas e trabalhadas utilizando o openSUSE 12.1 RC2 como plataforma operacional e GIMP com Inkscape como ferramentas de edição vetoria e de imagens, ambos disponiveis para as download nas plataformas, linux, mac e windows.
Os arquivos tambem pode ser baixados em maior resolução a partir de meu album de fotos.
Boas festas!
CarlosRibeiro
MemberFOSDEM 2012: announcing the devrooms
Just sent out the ack/nack emails for the developer rooms at FOSDEM 2012, the latter part always being pretty tough, but we have to make choices.
On the good side: here is the list of the devrooms for FOSDEM 2012.
Mind you, that list does not include the Distribution Miniconf, which will take place in two rooms during both days and will gather sessions, talks, ideas from many (mostly Linux) distribution projects.
Smartphones - Acquired Necessity
Smartphones - An acquired necessity
I have used a Motorola E398 mobile phone for the last 6 years. For the last one month, I tried using a Samsung Galaxy S2 smartphone. I have concluded that Smartphones are an acquired necessity and is not needed for most of my workflows. I will not buy a smartphone in the near foreseeable future.
Smartphones gives an impeccable improvement for one workflow - Email. If your work involves time-sensitive emailing, a smartphone is a crucial tool. However, if it doesn't, then you are better off buying a good desktop/laptop and a normal mobile phone, imho. A shortlog of things observed in this one month are:
Observations:
- Vibration: Smartphones are too thin and don't have enough vibration, if you are used to thick phones (Not a big problem)
- Poor signal reception: A biiiig problem. In the quest to slim the phone, the signal reception abilities of the phone are heavily hampered. While we were travelling in a car (from Bangalore to Chennai), A cheap Samsung GURU E1081 consistently beat Galaxy S2 in terms of signal strength. Most of the times the Galaxy S2 was showing "Emergency calls only" only. May be a phone from a real phone-maker like Motorola/Nokia may not have this problem. We had to keep the phone upright near the car window too.
- Typing: Even with the on-screen-keyboard, swype etc. the phone is totally unsuitable for typing long text. We can do only twitter/facebook updates and not do any serious document editing or long blogpost(s). The requirement for Siri (Voice Control) is just a natural demand. I wonder how the folks at Google missed this big requirement. They should have introduced this with a big bang and not play catch-up to Siri. Probably they missed it as they were busy tomato-saucing Google+ to all their applications ;-)
- Screen Estate: The screen size is totally unsuitable for reading books, blogs. It is okay for occasional blog reading, but it is straining. There are people who read blogs using their phone primarily. But I am spoiled by my employer who gave me an iPad, a Samsung GalaxyTab and a Thinkpad to play with, for some mobile related coding. I did not prefer the smartphone even once when I had my good old Thinkpad. Tablets and laptops provide far better reading experience and are equally handy. The GalaxyTab can act as a phone too for all your needs.
- Fragile: Smartphones need extreme care. Not ideal for rough use, unless you are using a rugged phone like Motorola Defy+ (which has its own set of problems). A friend once dropped a Google phone from his hands while taking from pant pocket (~3 Feet) and the glass shattered into pieces. I have thrown my E398 numerous times (atleast few dozen times from ~5.6 feet) and nothing has happened except an automatic restart.
- A Patentable Idea: The unlock pattern (of Android) leaves fingerprints and so your phone is not really secure. If you look at the phone, by keeping the screen flat in front of your nose, you can easily detect the unlock pattern finger prints. This may be fixed soon with the advent of touchscreens that do not leave a finger print. I wonder why can't we just authenticate based on the fingerprint in a smartphone !? That may be cool. I should probably patent it, as it seems in mobile phones any stupid thing can be patented. Think: SYSTEM and METHOD for RECORDING and AUTHENTICATION of users to mobile phones via fingerprints, by letting them swipe on either the surface/camera/etc.
- Battery Life: Even after switching off the wireless, due to the rich display, the battery life of all the smartphones is very less. My phone battery did not last more than 3 days. With wireless on and just GMail app running, the battery lasted for just about 1 day. Some of the non-smart phones these days have close to 2 weeks battery life. If battery life is your criteria or travel a lot, you must order a extra battery if you are buying a smartphone.
- Muscle Memory: After laying in my bed for sleep, many times, I have taken my motorola phone, unlocked it, launch the alarm application, set alarm for a specific time, exited the application, locked the phone again. I do all this while keeping my eyes closed. The normal phones with keypad are easily operable in one hand. I can take a call in one hand, while the other hand is balancing my body in a bus moving through the high-traffic streets of India. Contrary to what you hear, smartphones require both hands to be used and is not so easily adaptive for muscle memory. For a basic operation like calling a recently called number, you will take more time in a smartphone than a phone with a dedicated CALL button.
- COST: The single biggest reason why I won't buy a smartphone is Cost. Smartphones from any decent hardware maker are very costly. Personally, with my Indian mentality that takes pride in being cheap, I find it stupid to spend 30,000 INR (600 USD) on a phone which will be valued at 1,000 INR (20 USD) after may be 3 years. This inference is based on the Motorola Razor handset pricing in India. Compare this to a new Samsung GURU phone with color-display, USB charging capacity etc. that costs a mere 1000 INR (20 USD) and has battery life of about 1 week with normal usage. However, there is a big demand for cheap smartphones in markets like India. If and when Nokia releases their cheap smartphones in India, they are sure to repeat their success story in India, just like they did with their Torchlight series phones.
Samsung-specific-observations:
- The default alarm application does not have snooze option. There is no excuse for this.
- Samsung Kies - Ahem :/
Also, it is not available on Linux. Good news is that with the recent versions, the software update can be done within the phone itself without Kies. - The indic support patch is not upstreamed yet. But kudos to Samsung as they are the only Android handset makers who support Indic fonts native as of today, afaik. A few of my Tamil friends bought Samsung phones just for this reason.
- OLED - Amazingly rich screen, especially while displaying black color.
- The front camera in S2 is just a joke. Totally useless for my needs.
Android:
- "Android" brand has a better image than "Linux" in the consumer market. It is not without reasons. There are a lot of positive things about Android. I have not mentioned any of them because you can find them easily.
- However, To be honest, the usability of Android phones is *not* jaw-droppingly-awesome, imho. They are just as normal (good ?) as say Meego UI or GNOME 3. But consumers love them. If enough money is spent on marketing, pigs really can fly. I wish some of the earlier projects like openmoko/maemo/meego had rich companies that were as committed as Google is to Android.
- I hope ChromeOS opens a door for Linux on Desktops, just as how Android made Linux the most dominant operating system on mobiles. That may help PC OEM vendors to think a little instead of their current act of blindly worshipping Microsoft.
- The biggest positive impact of Android imho is: Android made companies which usually don't bother about Linux users (like Evernote) to write applications for Linux.
Every-Packet's Changing... my Keane Parody
Every-Packet's changing and I start to go insane
You're gone from here, soon you will disappear
Fading into tri-colored light
Cause Every-Packet's changing and I don't feel right
Every-Packet's changing and I start to go insane
Every-Packet's changing and I don't feel the same
Ooooh, Every-Packet's changing and I report abends...
Geekos agora com página no Google+!
Gostaria de convidar a todos os admiradores do openSUSE e software livre a conhecerem a nova página G+ anunciada a poucas horas.
Segue então a tradução e adaptação do texto.
-
O mundo de TI se move rapidamente e junto com ela as redes sociais. Fazem poucos dias que o Google anunciou a disponibilidade limitada das páginas Google + e milhares de Google-plussers já criaram páginas Google+. É claro que também somos bastante sociais, portanto, o projeto openSUSE agora tem uma página oficial do Google +!
Se você criou uma página para a comunidade openSUSE, como o Kostas fez para a comunidade Grega, então não se esqueça de adicionar sua página junto aos contatos de mídia social do openSUSE para que os entusiastas do openSUSE possam facilmente encontrar as páginas oficiais do openSUSE e adicioná-la aos seus círculos. Essa página também é uma referência para outras atividades de mídia social que envolvam o openSUSE como o Facebook, Twitter ou LinkedIn.
Além disso, se você gosta de se envolver e promover o openSUSE em mídia e redes sociais, por favor fale com a equipe de marketingdo openSUSE.
Eu gostaria de agradecer Roger Luedecke por cuidar da nova página G+ do openSUSE e convidar a todos a compartilharem conteúdo nesta página, promover e seguir o que fazemos!
Texto original: Geekos go on G+
Autor: Koudaras Konstantinos
Tradução e adpatação: CarlosRibeiro
O Planeta Verde!
Nos últimos dias algumas pessoas que utilizam o planet através do http://planetsuse.org/ tem manifestado problemas de conexão.
Estes problemas não aconteceram devido ao openSUSE Planet ter saído do ar mas sim como anunciado pelo Pascal Bleser a poucos dias na lista de emails do openSUSE Project , aconteceu devido a este nome de dominio não estar sob os domínios de controle do Projeto e sim sob responsabilidade e dominio de outra pessoa que deixou o projeto anos atras.
Atualmente a única maneira de ir para o planeta openSUSE é digitando http://planet.opensuse.org/ e a maneira correta de adicionar o feed ao seu agregador é adicionando esse. Xml.
No caso de encontrar dificuldades em configurar seu agregador, por favor entre em contato com admin@opensuse.org que alguem certamente irá auxiliá-lo a resolver qualquer que seja o problema.
Muito obrigado pela informação, mas enfim, o que é este Planeta openSUSE?
Alguns de vocês podem saber o que é, mas existem outros por aí que realmente não sabem o que é o Planeta openSUSE e qual é o seu uso.
O Planeta openSUSE não é aquele Planeta escondido onde vivem os reais geekos, que são enviados para a Terra em seus respectivos avatares, para conquistar apreciadores de Sci-fi com coisas que voce nem imagina ;-)
Na verdade o Planeta openSUSE é um agregador de feeds da web que recolhe mensagens de blog de pessoas que contribuem para o openSUSE. Mesmo o Inglês não sendo seus idioma preferido você também pode adicionar seu blog.[1]
Como posso participar?
Se você se parece com uma destas pesoas e gostaria que outros lessem suas atividades relacionadas ao openSUSE, envie um email para os administradores[2] com as seguintes informações:
* URL do seu blog ou, melhor ainda, a URL para o feed RSS / Atom de seu blog
* em qual idioma você bloga, especialmente se não é em Inglês
* seu nome completo (por exemplo, Carlos Ribeiro)
* seu apelido no IRC Freenode, se você tiver qualquer (por exemplo CarlosRibeiro)
* se você já for um membro openSUSE um botão de "Membro" podera ser adicionado abaixo de seu nome na lista de feeds.
* um hackergotchi[3] - embora não seja obrigatório, é muito mais agradável para os leitores. Caso precise de ajuda, enviar uma foto para a equipe de arte do openSUSE[4].
-
Texto original: The Green Planet!
Autor: Koudaras Konstantinos
[1] Planeta openSUSE em portugues
[2] email de contato dos administradores do Planeta openSUSE
[3] Hackergotchi
[4] Lista de email do time de artwork do openSUSE
gpodder 2 vs 3 in Packman
The gpodder project introduced its new major release 3.0.0 today and, unfortunately, it seems like I didn't pay attention to the complete change announcement, as I just bumped the gpodder package in Packman to 3.0.0 (from 2.18).
Now, gpodder 3.0.0 does introduce a lot of changes, notably in the UI but also regarding its database format and requires migrating the database from 2 to 3. It doesn't seem to have all of the features of 2.20 either. So what happens is that when you just upgrade the gpodder package, you end up with something you don't necessarily want to use. At least as of now.
Upstream will still maintain the 2.x branch for quite a while, and gradually port features from 2 to 3 and, hence, it actually makes sense to do it differently. What I have done now is to revert the gpodder package at Packman to the 2.xx branch (and upgrade to 2.20 at the same time).
If you want to use gpodder 3.0.0, then just install the package gpodder3 instead: zypper or YaST2 will tell you to remove gpodder in order to do so, as you cannot have both installed at the same time (they have file conflicts).
Now, if, in between those changes, you already did the upgrade, do one of the following:
-
if you want to keep using 3.x: then run
rpm -e gpodder && zypper install gpodder3(as root) -
if you want to go back to 2.x: then run
rpm -e gpodder && zypper install gpodder(as root)
On a side note, please wait a couple of hours (after this blog post) before doing so, as our main repository server is only synced to some mirrors after 4 hours (after 1 hour for most though).
Sorry for the inconvenience.
Network Installation of openSUSE
What is the Motivation for this setup?
1) Local Area Networks (LANs) are ubiquitous... even in homes where, chances are, you have a modem to the Internet and next to it is a wireless/ethernet router for multiple wifi and ethernet capable devices (PCs, Laptops, Smartphones, Tablets etc) to connect and surf the web.
2) If you are a Linux/OSS enthusiast, you would be constantly downloading the latest ISOs from the web, burning them onto a DVDs and installing them on physical/virtual machines. This is time/resource intensive... time to download, time to burn a DVD, time/money spent on blank DVDs etc. Of course, if you install openSUSE on virtual machines, you avoid the DVD part of the process but you would still have lots of ISOs on your filesystem... if you have a classroom of 20 machines... well, you get the idea.
3) Almost all PCs and Laptops these days have an ethernet port and are capable of booting up from the network (ie PXE-boot). This means you physically power them on, tell it to go into PXE-boot mode and it will go onto the network and seek out an installation server to download and install the openSUSE binaries.
4) This is an efficient way to install openSUSE onto both physical and virtual machines in a LAN environment where there is only one central place for your software binaries.
Pre-requisites:
i) You have a LAN environment connecting a few machines via the network cable. Although booting from wifi is possible but it is out of the scope of this discussion.
ii) You have a physical machine (preferably*) with openSUSE installed and this will be the designated network installation server.
*It is possible to set this up on a virtual machine but you need to ensure it is connected to the physical LAN in a Bridge networking mode and not the usual NAT networking mode for typical virtual machines.
3 Simple^ Steps to Success:
^Simple - it will become more simple as you do this more frequently.
Step 1: Install and configure Apache2 webserver to host and distribute openSUSE binaries.
Please refer to my other blog entry on this subject - Using Apache2 to deploy & maintain SUSE
Step 2: Install and configure tftpboot server to enable initial boot of target machines over the network.
Please refer to my other blog entry on this subject - Install and configure TFTP server for PXE boot environment
Step 3: Install and configure dhcpd server to provide an IP address for target machines and redirect them to the tftpboot server.
Please refer to my other blog entry on this subject - Install and configure DHCP server
Step 4: On the target physical machines, on boot and depending on the BIOS, activate the boot from LAN option and watch it get an IP address from the Installation Server (via Step 3), followed by connecting to the TFTP server and presenting an installation menu (via Step 2). Enter the choice of OS to install and your installation will commence over the LAN (via Step 1).
Additional points of note:
a) Everything discussed here applies to SLES, SLED and openSUSE. The steps documented are based on openSUSE 11.x and should work on older versions and even the enterprise editions of SUSE.
b) Software installation (apache2, tftpboot, syslinux, dhcpd etc) assumes your SLE or openSUSE server have access to their respective binaries, either in DVD (also ISO) or software repository on the web.
References:
- openSUSE.org - SDB:PXE boot installation
- Novell Cool Solutions - Setting Up a SUSE PXE Installation Server in an Existing NetWare Environment
- Novell Article - Setting up a PXE Boot Server
Enjoy!
Install and configure TFTP server for PXE boot environment
1) Install SysLinux (Bootloader for Linux)
Command-line (as root): zypper in syslinux
2) Install tftp
Command-line (as root): zypper in tftp yast2-tftp-server
3) Enable tftp
Command-line (as root): yast2 tftp-server
In TFTP Server Configuration dialog, check to Enable the service. Ensure the Boot Image Directory is set to /srv/tftpboot. Finally, check the Open Port in Firewall and click Ok.
Note: Its been observed that the SUSE Firewall may still block incoming traffic to the TFTP boot server despite the Open Port in Firewall setting.
To ensure the Firewall is not blocking incoming TFTP traffic, open the Firewall setting via YaST (or command-line yast2 firewall). Navigate to the Allow Services section (left-hand pane) and click on Advanced button. Ensure that port 69 is listed in the UDP section and click OK to accept. Click Next and complete the settings change.
Next, create the sub-directory /srv/tftpboot/pxelinux.cfg via the command-line: mkdir -p /srv/tftpboot/pxelinux.cfg
4) Populating the /srv/tftpboot directory
Copy pxelinux.0 file (part of syslinux package installed earlier) to the /srv/tftpboot directory. Command-line: cp /usr/share/syslinux/pxelinux.0 /srv/tftpboot/
Copy the relevant Linux kernel and initrd boot files to /srv/tftpboot and provide meaning names (to avoid confusion later). This is best described by way of an example. Let's say I want to enable my installation server to provide an option to install both the 32-bit and 64-bit of openSUSE 11.4. Therefore, I would do the following:
a) Mount both 32-bit and 64-bit of openSUSE 11.4 ISO on the filesystem:
mount -t iso9660 -o ro,loop /directory/to/openSUSE-32-bit.iso /mnt/openSUSE-11.4-i586
mount -t iso9660 -o ro,loop /directory/to/openSUSE-64-bit.iso /mnt/openSUSE-11.4-x86_64/
b) Copy the relevant Linux kernel and initrd files to /srv/tftpboot and rename them with more meaning names:
cp /mnt/openSUSE-11.4-i586/boot/i386/loader/linux /srv/tftpboot/openSUSE-114-32bit.krnl
cp /mnt/openSUSE-11.4-i586/boot/i386/loader/initrd /srv/tftpboot/openSUSE-114-32bit.initrd
cp /mnt/openSUSE-11.4-x86_64/boot/x86_64/loader/linux /srv/tftpboot/openSUSE-114-64bit.krnl
cp /mnt/openSUSE-11.4-x86_64/boot/x86_64/loader/initrd /srv/tftpboot/openSUSE-114-64bit.initrd
c) Copy the message file from any openSUSE ISO to /srv/tftpboot:
cp /mnt/openSUSE-11.4-x86_64/boot/x86_64/loader/message /srv/tftpboot/
*You may unmount the ISOs as these copy are a one-time operation.
5) Prepare the text-based menu
[Update on 3 Dec 2011: added the directory where the file default should reside below]
Create a text-file (via your favourite editor as root), named default in the /srv/tftpboot/pxelinux.cfg directory with the following contents:
default harddisk
display message
prompt 1
timeout 600
# Install openSUSE 11.4 (32-bit)
label openSUSE-114-32
kernel openSUSE-114-32bit.krnl
append initrd=openSUSE-114-32bit.initrd splash=silent vga=0x314 showopts install=http://IP_ADDRESS_OF_SERVER/software/openSUSE-11.4-i586/
# Install openSUSE 11.4 (64-bit)
label openSUSE-114-64
kernel openSUSE-114-64bit.krnl
append initrd=openSUSE-114-64bit.initrd splash=silent vga=0x314 showopts install=http://IP_ADDRESS_OF_SERVER/software/openSUSE-11.4-x86_64/
Everything is self-explanatory above except for the install=http://IP_ADDRESS_OF_SERVER portion. Please refer to my other blog entry on using Apache2 webserver to host and serve up software binaries.
Finally, edit the message file in step 4c earlier to correspond with the example default file entries.
Welcome to openSUSE!
To start the installation, type one of the options below and press
Available boot options:
openSUSE-114-32 - Installation of 11.4 32bit
openSUSE-114-64 - Installation of 11.4 64bit
Have a lot of fun...
Done.
Install and configure DHCP server
The PXE boot environment (TFTP server) is documented in another blog entry Install and configure tftp server for PXE boot environment and the main entry discussion on Network Installation of openSUSE.
1) Install DHCP Server (dhcpd)
Command-line (as root): zypper in dhcp-server yast2-dhcp-server
2) Configure DHCP
Make a backup of the dhcpd.conf file to start afresh: mv /etc/dhcpd.conf /etc/dhcpd.org.conf
Create a new dhcpd.conf file, using your favourite text editor as root, from scratch with the following content:
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
option domain-name "example.org";
option routers 192.168.11.1;
max-lease-time 7200;
ddns-updates off;
ddns-update-style none;
log-facility local7;
default-lease-time 600;
# define rules to identify DHCP Requests from PXE and Etherboot clients.
class "pxe" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
}
class "etherboot" {
match if substring (option vendor-class-identifier, 0, 9) = "Etherboot";
}
subnet 192.168.11.0 netmask 255.255.255.0 {
range 192.168.11.51 192.168.11.60;
default-lease-time 14400;
max-lease-time 172800;
server-name "192.168.11.200";
next-server 192.168.11.200;
filename "pxelinux.0";
# allow members of "pxe";
}
Using the sample dhcpd.conf above, you can see that
- My router IP is 192.168.11.1
- DHCP daemon is giving out IP address starting from 192.168.11.51 to 192.168.11.60. You can adjust this setting to provide more IP addresses. The important part is to assign IP addresses outside the range of any other existing DHCP server (either in the router or in another environment where you do not have access to the official DHCP server).
- server-name and next-server points to the IP address of the network installation server (ie pointing back to the openSUSE server that is running DHCP server, TFTP server, Apache2 server with binaries)
Alternatively, if you would like a GUI interface, you may try yast2 dhcp-server. Below are screenshots of the 4 step wizard.
3) Starting and Stopping the DHCP Server
Its best to manually start and stop the DHCP Server as required... as most LANs already have some DHCP service running... doubly so if your machine is portable (ie Laptop), you wouldn't want your Laptop to start dishing out IP addresses on boot.
To start the DHCP server, command-line (as root): rcdhcpd start
To stop the DHCP server, command-line (as root): rcdhcpd stop