Na štai ir išbandžiau, taip ilgai lauktą Gentoo 2008 Live CD. Išbandžiau ir pamačiau, kad tai tėra muilo burbulas, apie kurį pernelyg daug šnekėta. Visiškai pasišlykštėtinai nuteikianti Xfce, nevykęs Mozilla Firefox rebranding'as, kažkodėl neveikiantis terminalas ir GTK install'eris, kuris irgi neveikė, nes ištisai rodė, kad diskas "nešvarus", t.y., kad jame yra failų. Nors aš ten  viską jau ištrynęs buvau. Tiesa, dar buvo ir "Command Line" istaller'is ant Xfce desktop'o, bet vos pabandžius nustatyt "mount'inimo" sąlygas, jis tuoj ėmė ir apsikiaulino - išdidžiai pranešė, jog tokia galimybė bus dar ateityje.

Po velnių! Gentoo Linux tikrai yra pati blogiausia mano testuota distribucija. Neišsivaizduoju, kas galėjo kurti tokį kiaulišką reikalą, bet čia net Linux pavadinti būtų gėda. Aplamai, Slackware'o laikais tokios velniavos net nebuvo. Kiek bandžiau "Slaką", - nors ir kietas jis šmotas yra, man nebuvo jokių problemų su instaliacija. O čia viskas blogai. Tiksliau viskas nenormalu, ne taip, kaip reikia. Ne taip, kaip turi (turėtų) būti.

Iš kitos pusės - truputį gaila... Būčiau bent pažiūrėjęs, kaip šitas produktas veikia. Na, bet - jei nelemta, tai ir nereikia. Netikėsiu nei vienu, užtat, kas girs šitą mėšlo kupetą forumuose...

O dabar - vėl su Ubuntu. Nes ji geriausia. Ne aplamai, galbūt. Bet tiesiog geriausiai suderinta. Be jokių nustatymų (ko nereikia), be papildomo galvos sukimo. Tiesiog "imk ir naudok". Būtent taip ir yra geriausia. Nes, kaip sakoma, - "durnius myli darbą, darbas myli durnių". Tai būtent taip ir yra, - jeigu vartotojas neturi ką veiti daugiau gyvenime - ima ir krapšosi per dienas konfiguruodamas įvairias, neišbaigtas distribucijas, kaip Gentoo. O kas mieliau mėgsta paklausyti muzikos, redaguoti nuotraukas, bendrauti ir rašyti WordPress, be abejo rinksis paprastą ir suderintą Linux distribuciją, nekeliančią jokio vargo ir nereikalaujančią šaistyti ir taip brangaus laiko, per kurį galima nuveikti ką nors naudingo sau arba savo aplinkai.

Taigi, labanaktis. Kompiueriuką palieku va šitam procesui:

En la partición en donde almaceno /var/tmp/ccaché uso reiserfs de un tal Hans Reiser, un señor que va por la vida matando mujeres, y que espero que le den una notebook ahora que en la carcel va a tener mucho tiempo libre, por que es un genio...

Tantos malos apagados sucesivos me deterioraron tanto el sistema de archivos que la pc moría con un kernel panic. A continuación, como reparar el sistema de archivos de cualquier linux sin usar el livecd de otro linux, arrancando desde el mismo kernel del linux que no funciona:

GRUB tiene la capacidad de editar el menú al vuelo, lo que nos permite hacer cambios sobre las lineas que hacen referencia a como se cargará el kernel y que parametros se le pasarán, para acceder al modo edición de GRUB, estando en el menú, basta con presionar la tecla [e].

Dentro del menú edición, podemos posicionarnos sobre cualquiera de las lineas que hubiera con la tecla de cursor para de nuevo presionar [e] y ahora si, hacer todas las modificaciones que quisieramos... Del modo edición se sale con la tecla [Esc] y se arranca la opción seleccionada con la tecla [b].

Init es el parámetro que controla que hace el kernel inmediatamente después de haber terminado de cargarse y se puede modificar al vuelo. Si a la linea que hace mención al kernel le agrego la opción init=/bin/bash o /bin/sh dependiendo la distribución, inmediatamente después de cargar el kernel quedo parado en una consola como root, sin haber introducido la contraseña (y sin necesidad de conocerla, por si quieren hacer maldades).

Como soy root y no tengo ningun servicio corriendo que acceda a la partición raiz de mi linux, puedo montarla en modo solo lectura (Read Only, ro) para poder reparala con el comando:

mount -o remount,ro /dev/sdX #Donde X es el número que corresponde a la partición en donde almaceno mi unidad raíz.

Teniendo ya montada en modo solo lectura la partición, ahora si la puedo reparar con tranquilidad. ReiserFS es bastante robusto aunque no tanto como un buen ext3 al que basta con ejecutarle un fsck -f /dev/sdX para ponerlo en carrera de nuevo.

Como una pasada con reiserfsck me indicó que había algunos errores, tuve que ejecutar:

reiserfsck --rebuild-tree /dev/sdX

Y con eso alcanzó para solucionar todos los problemas que venía experimentando.

Since I'm not the only one with circular dependencies I'll try to explain how to get rid of them.
If you can't update your world set because of circular dependencies, then you can best comment out your USE-flags in /etc/make.conf and put USE="-*" underneath it. Then update world and when that succeeds, remove the latter USE declaration in your make.conf and uncomment your former USE-flags. Update/rebuild world again and if all goes well you won't have a single circular dependency :)

Okay, it's not as pretty as GNOME (but beauty is in the eye of the beholder), and perhaps not nearly as configurable as KDE. All conceded. But like anything else you fall in love with, it need not be the best in every category or everyone's favorite--its unique features made you a silly fanboy and you just can't help but love that, too.

Maybe I should outline what I like about desktop environments, for starters. I, like most Linux users to be sure, am very much into my user experience on the computer.

So I've got my particulars. And they are:

• I lean towards minimalism over busy desktops
• Sleek and streamlined, aesthetically pleasing look
• Fair amount of options for theme, icons and window managers
• A light set of applications that get the job done, but don't hog resources
• Usually, two toolbars. If one always did the trick, I'd use Windows! Nevermind...

For someone who seems a little fanatical about his GUI, I still swear by the Command Line. Perhaps that's why I prefer to keep my desktop environment so clean--I don't need all the GUI apps bringing things down! That said, I think a Desktop Environment (be it KDE, GNOME, Xfce, Fluxbox, and so on) should be just what it says it is. It's not a necessary evil on top of a text session, but it's probably not what Microsoft thinks it is. It should be a digital environment in which you enjoy surfing the web, getting work done, and enjoying some type of media. It should be clean, it should be effortless, and it should be efficient, but it should feel right. Interior decorators have feng shui; I have the Human Interface Guidelines.

What I'm trying to say is: Elegance, and usability. Forget the rest. Consider, my friends, Xfce... It's light, it's fast, it looks really good in blue. And it's gotta be blue or black, by the way. Why would your theme be any other color? Tisk tisk. Take a look at this snapshot of desktop bliss:

You can obviously tell from the screenshot that I'm running Xfce on Ubuntu. It's a full Ubuntu 8.04 install--so it's also packing GNOME, and others. Xubuntu is however on my Asus EEE PC, and it's fantastic with the EEE 701 4G's modest specs. Besides downloading Xfce for your distro of choice, it can be found by default on plenty of Linux distros, including:

• Arch Linux
• Dreamlinux
• Eeedora
• Gentoo Linux 2008.0 installation
• Gentoo Linux for Playstation 3
• Mythbuntu
• SAM Linux
• VectorLinux
• Zenwalk

Some of those are gorgeous distros that make my setup look a bit bland! It's really your choice, Xfce can be as bare and simple, or as flashy and attractive as you care for. For those of you who are inclined to use Compiz Fusion, you'll be happy to know that as of the current release, Xfce has a built-in compositor, offering some minor effects like transparency and drop shadow. I've found Xfce to be the most versatile, almost chameleon-like environment in that aspect. I've made my Xfce desktop look like plenty of other default setups, just for fun and because Xfce simply can! Here's the rest of a short tour around my Xfce desktop:

Xfce 4's Orage calendar program is light and fast, yet still provides the same scheduling and time management features you'd expect from Outlook or Evolution. Orage is based on and compatible with the iCal format.

The included Xfce Terminal is--you guessed it--very snappy to start up but it doesn't sacrifice extra configuration if you like to retool the appearance a bit, like I do. This app starts in the blink of an eye on my EEE PC.

Here's the no-nonsense Xfce file manager, Thunar. It's still possible to add a nice touch to your files and folders with emblems, like you see here. My only complaint is that you can't preview audio files by placing your cursor over its icon, as with Nautilus. Thunar is still faster and more responsive than other file managers, and is also extendable with scripts and plugins. (See this page for a memory comparison among Thunar and other file managers)

Also shown is Xfmedia, a rather bare bones xine-based music player part of the Xfce project. It obviously lacks much of what heavy-hitters Amarok, Rhythmbox and my new favorite Banshee have to offer, but you'll never find Xfmedia to be the cause of a slowdown with several apps running on multiple desktops. Where it lacks Last.fm support, it more than makes up for it by being the music player you can load a playlist into, hit play and forget about on your fourth desktop. Works for me.

Besides all of that, who can resist that endearing little mouse that is Xfce's mascot? That's the face of a light and swift animal who's gonna help you get things done!

]]> http://tiplace.wordpress.com/?p=37 Wed, 08 Oct 2008 21:45:27 +0000 Alexandre Pereira http://tiplace.th.wordpress.com/2008/10/08/mantendo-sistemas-atualizados/ Achei um artigo super interessante que mostra como manter sistemas operacionais atualizados. Tem exemplo de vários sistemas. Uma parte do artigo aborda a instalação e configuração da ferramenta GLSA ( Gentoo Linux Security Advisories), para quem não conhece, existe uma base de dados com informações sobre vulnerabilidades e tal ferramenta faz uma checagem no sistema e compara com a base, no fim é emitido um relatório com as vulnerabilidades do sistema. Além disso ainda existe a possibilidade de enviar o relatório por email e de automatizar a tarefa via CRON, mantendo assim o administrador sempre informado.

Enfim, segue o link ...

http://www.csirt.pop-mg.rnp.br/docs/so/atualizacao.html

While I was trying to install a taxprogram I think I messed up my /usr, got all sorts of 'Permission Denied' so I decided to reinstall Gentoo.
Which didn't go fast enough because I needed my laptop for school use. So I decided to install Sabayon, but that didn't go so well. So in the end I decided to install fedora 9 which runs nice and smooth.
But I longed back for Gentoo, that when I installed KVM and I started with my Gentoo install.

I used the stage3 from www.funtoo.org/linux and the portage tree from www.github.com/funtoo
At the moment I intend to create a solid base-system with all my needs and create a stage4. I hope Daniel Robbins his stage-create-tool a.k.a. Metro is finished before I get to that stage :P

Anyway I'm just done with getting rid of circular dependencies. I'm now rebuilding the system with enabled USE-flags
After that I'll review all the USE-flags and adjusting /etc/make.conf || /etc/portage/package.use accordingly
And when I'm done rebuilding those packages I'll move to emerging X

Sounds like I'm not done yet.. And to make it more interesting it's all in kvm.

Paludis also has ways of tracking packages installed by hand. Whilst useful on Gentoo, this really comes into play on Exherbo, where we don't want to end up with a massive unmaintainable tree full of packages used by only two people.

The logical next step is tracking packages that don't exist yet.

An unimaginative person might think that the way to solve this would be to have a bug for each requested package. But that gets messy -- it's not integrated with the package manager, and requires considerable extra effort from the user. A while ago Bernd suggested something more interesting: tracking unwritten packages in a repository in a similar way to how we do unavailable packages.

The implications:

• Most obviously, we can keep track of things we want that haven't been written yet in a way that doesn't involve leaving the package manager to look things up.
• We can also use it to track version bumps that we know will take a while. Doing paludis --query '>=hugescarypackage-4', say, would show that it's being worked upon.
• We can also depend upon things that don't exist, rather than leaving incomplete dependency strings around. This is fine in at least two cases -- if a dependency is conditional upon an option that should probably be implemented but isn't yet, we can add the option and make it unusable. And we can handle obscure suggested dependencies (e.g. git has lots of optional dependencies upon weird perl modules, so we can say "if you want support for git-send-email with SSL, you need to write such and such a package").
• Bored developers could simply paludis --query '*/*::unwritten' and get ideas for what to do.

Adding support to Paludis for this only took a couple of hours. So now Exherbo developers can use this:

format = unwritten
location = /var/db/paludis/repositories/unwritten
sync = git://git.exherbo.org/unwritten.git
importance = -100

And see this:

$ paludis -q genesis
* sys-apps/genesis
    unwritten:               (1.0)X* {:0}
    Description:             The daddy of all init systems
    Homepage:                http://www.exherbo.org/
    Comment:                 We need an init system.
    Masked by unwritten:     Package has not been written yet

As with unavailable, installing behaves sensibly:

$ paludis -pi genesis
Building target list...
Building dependency list...
Query error:
  * In program paludis -pi genesis:
  * When performing install action from command line:
  * When executing install task:
  * When building dependency list:
  * When adding PackageDepSpec 'sys-apps/genesis':
  * All versions of 'sys-apps/genesis' are masked. Candidates are:
    * sys-apps/genesis-1.0:0::unwritten: Masked by unwritten (Package has not been written yet)

Those interested in the repository format can browse the tree. The observant might notice that the file format is quite similar to the one used by unavailable repositories, and wonder whether I was feeling lazy and swiped a load of code rather than implementing a new repository from scratch.

In the spirit of silly buzzwords, one could argue that this increases distributivity and democratisation of the repository, since there's nothing to stop motivated users from creating their own wishlist repositories. It wouldn't be hard to make a simple web interface that lets users request and vote on packages and version bumps, automatically generating a repository that anyone can use. But fortunately Exherbo is a dictatorship and has no users, so we don't have to put up with that kind of nonsense.

• dev-tex/pdftex
• dev-tex/mplib
• app-admin/eselect-mpost
• app-admin/eselect-pdftex

While our TeX distributions already ship them (pdftex and mpost), the first two are standalone packages and the last two are eselect modules to easily switch and use them.
With the bump to TeX Live 2008 I've made it possible to switch between different versions instead of being bound to what has been shipped with the release. This means that they will get bumped more frequently than they used to.

For the pdftex case, it is currently the same version that comes with TeX Live 2008 with the difference that the standalone version is patched to use poppler instead of its bundled xpdf library. I've prefered to leave the xpdf library as default for TeX Live because that is what upstream is using but some people asked for it to use poppler instead and a lot of other distributions (debian, fedora and their derivatives) are using it as the only way. That will probably make it easier to get improvements and security fixes on that side. If you wish to try it, install pdftex and eselect-pdftex and use "eselect pdftex" to set the standalone package as your default pdftex!

As for mplib, it is a reworked and rewritten version of the good old metapost. It can be used as a library (as luatex does) but you can also switch your default mpost interpreter to be it via the eselect-mpost package. Upstream says it is a work in progress but so far I have not seen any problem with it.

By the way, I have unmasked TeX Live 2008 today so that means ~arch users will upgrade to this release and can try these alternatives out of the box.

I'll generate and link versions approved by the Gentoo Council by checking out their signed tags and those versions that the PMS editors deem important. I'll also link to current HEAD, but this won't be automated so it might lag a bit if I'm extremely busy.

Also, for those that can't be bothered reading technical documentation aimed at people implementing a package manager and want to know what's new in EAPI2, Ciaran McCreesh has published a series of blag posts explaining the new features and whence they came. Make sure to take a look at What's in EAPI 2?

— ferdy

Here are my 4 tips for beginners:

1. Make sure you learn why each command does what it does. Don't just copy n paste.
2. Use Google for everything. Learn to find stuff on your own. Pretty much everything you can think of has been already done. If you have a bug, type it in on Google and see what you get.
3. Learn the terminology. Things like nano, symlink, Kernel, Desktop Environment, etc.
4. Explore Your Options. Every operating system is different. Mac is different from Windows and Linux is different yet. Linux offers a large amount of features for customization. Just because you don't like the colors or the desktop features doesn't mean Linux isn't for you. You might not get it right the first time, just keep searching until you find the right software, desktop environment or what not that suits YOU.

I hope these help, if you have any questions please comment.

-Clinton

The true problem arose when I attempted to actually implement changing my background. With fluxbox, this should be possible with a simple command like so:

fbsetbg -a -r /home/dfego/.fluxbox/backgrounds/

Simple enough, right? Well, as simple as it was, it just didn't quite work. So I changed my cron timings, in case I got that wrong then used absolute paths, once again, just in case. Freaked out for a while, because the command itself works just fine. I ran it from a terminal about 29,834 times to make sure, but still, that little cron daemon that could just wouldn't budge. It would, however, write the text "working" into ~/cronf*cker every minute. As a matter of fact, it still is. Allow me to go take care of that...

Now that that's taken care of, I'll go ahead and tell you what the real problem was. Apparently the cron daemon doesn't have any inherent knowledge of the X display server I want to set the background of. Fair enough, since it starts running well before X gets started. But I didn't realize this would matter, or even think about it at all until I saw a post online about setting fluxbox backgrounds in a more general sense. It proposed butting DISPLAY=:0.0 before the line, like so:

DISPLAY=:0.0 fbsetbg -a -r /home/dfego/.fluxbox/backgrounds/

I changed the file, bit my lip, and a second or so after the next minute passed, my background was changed anew! As a note, my X server is not using display :0.0, but rather :1.0. You can find out what your value is by opening up a terminal and typing:

echo $DISPLAY

Anyway, there you have it. My first pearl of wisdom to the world! Apologies for verbosity, but sometimes in explanations such as this, it helps. So the moral of the story/digest version: be aware of context when running commands for X! Or something like that. I actually was at work today trying to impress a co-worker of mine with the power of the command line, but unfortunately my attempt fell flat on its face when passing commands to xmessage. I'm not too worried about it though. My ping/grep antics seemed to be enough to win him over.

With that, I'm off to bed, and to watch my background change once more before daybreak!

So today I was trying to get dual monitor support to work with my laptop and an external CRT I have laying around my house. Sadly though... somewhere between xorg-xserver-1.2.0.0 and xorg-xserver-1.3.0.0 support for mergedfb was dropped. This was particularly problematic for me since that is what I use to do dual screens. I accidentally received the upgrade when installing OpenOffice a week or so ago. Apparently versions of xserver less than 1.3.0.0 are no longer in portage. So I was up a creek on that particular issue. So... I figured if I was going to run an "unstable" version of X I might as well try out Xorg 7.4. To do this I had to add the following to /etc/portage/package.keywords:

=x11-base/xorg-x11-7.4
=x11-apps/x11perf-1.5
=x11-apps/mkfontdir-1.0.4
=x11-libs/libXrender-0.9.4
=x11-proto/renderproto-0.9.3
=x11-apps/xprop-1.0.4
=x11-libs/libXau-1.0.4
=x11-libs/libXrandr-1.2.3
=media-fonts/font-xfree86-type1-1.0.1
=x11-libs/libXxf86vm-1.0.2
=x11-libs/libpciaccess-0.10.3
=x11-apps/xkbcomp-1.0.5
=x11-apps/sessreg-1.0.4
=x11-apps/xset-1.0.4
=x11-apps/mkfontscale-1.0.5
=x11-libs/libX11-1.1.5
=x11-apps/xdpyinfo-1.0.3
=x11-libs/xtrans-1.2.1
=x11-libs/libXinerama-1.0.3
=x11-libs/libXmu-1.0.4
=x11-apps/xrdb-1.0.5
=x11-libs/libFS-1.0.1
=x11-apps/xwininfo-1.0.4
=x11-apps/xauth-1.0.3
=x11-apps/luit-1.0.3
=x11-misc/util-macros-1.1.6-r1
=x11-misc/xinput-1.3.0
=x11-libs/libSM-1.1.0
=x11-libs/libXfont-1.3.3
=x11-libs/libXv-1.0.4
=x11-apps/xrandr-1.2.3
=x11-libs/libXScrnSaver-1.1.3
=x11-libs/libxkbfile-1.0.5
=x11-libs/libXft-2.1.13
=x11-libs/libXext-1.0.4
=x11-base/xorg-server-1.5.0
=x11-proto/xproto-7.0.13
=x11-proto/xextproto-7.0.3
=media-libs/mesa-7.1
=x11-libs/libdrm-2.3.1
=x11-proto/inputproto-1.4.4
=x11-proto/xf86driproto-2.0.4
=x11-proto/dri2proto-1.1
=x11-apps/mesa-progs-7.1
=x11-misc/xkeyboard-config-1.3
=x11-apps/rgb-1.0.3
=x11-apps/xinit-1.0.8-r3
=x11-proto/randrproto-1.2.2
=x11-drivers/xf86-input-keyboard-1.3.1
=x11-drivers/xf86-video-ati-6.9.0
=x11-drivers/xf86-input-mouse-1.3.0
=x11-apps/xwd-1.0.2

Then I simply ran:

emerge -av xorg-x11

Then I let the magic begin. This will probably not work for everyone and certainly if you aren't running at least modular X already you will have many issues because you need to follow the modular X migration guide.

Anyway so far it has been running very well, and I love having the use of xrandr. Especially on my laptop where I do a lot of moving around and switching of external monitors. I had several problems this week getting my laptop to work with projectors and I am hoping that this will help solve some of those problems as well. It really is quite amazing how far along X has come since I first started running Linux about 4 years ago.The one problem is that the synaptics driver does not compile against Xorg 7.4. I can still use the touchpad and as long as I can disable tap to click all will be well :) . However I did find a synaptics driver. To install it I had to add the follow to /etc/portage/package.keywords:

=x11-drivers/xf86-input-synaptics-0.15.2-r2

Then I emerged it:

emerge -av xf86-input-synaptics

After I restarted X everything worked great with my touchpad again and pesky tap to click was disabled once again!

On another note I am starting to think my "only update every 6 months" policy needs some refining. Once I am done with college hopefully I will be able to afford updating more often. At present I don't enjoy dealing with the potential breakages that can occur with upgrades when I need to get work done. Luckily this problem occured at the beginning of my fall break so I had some extra time to mess around with it :) . Hopefully I can get in another blog entry or two in this time as well!

Distrowatch Weekly recalled attention to the original article several days later and amplified the lightly trolling post. The past two weeks Gentoo has taken a beating.

First Thomas Capricelli (a Gentoo user) voiced his disappointment that KDE-4.1 is not in the tree yet.

This has become a big issue because 4.1 essentially marks KDE out of beta and because it has been more than a month of KDE-4.1's official release. Marcus Hanwell (part of Gentoo's KDE team) noted three weeks ago that the KDE-4.1 delay is partly do to Portage's new EAPI 2 standard and how KDE-4.1 can be multi-slotted. Jan Kundrát, another Gentoo KDE team member, points out the new spec as well as that several of Gentoo's KDE team left recently.

The gong really sounded on an article last week not because of it's content but rather it's title. This article generated alot of unwanted buzz and stopped a few hearts (including yours truely). "Gentoo Linux Cancels Distribution" the article was largely optimistic though, and was probably just written by someone new to Linux definitions.

Justin Dugger also pondered "Is Gentoo Dying? and Loren Bandiera asks "What happened to Gentoo?"

The " The Decline of Gentoo Linux" loosely posited Gentoo's decline by three criteria: long delay of installation media releases, KDE-4.1 not being in the portage tree yet, and the project's fewer developers. Criteria hardly indicating his assertion that Gentoo is barely holding it together.

I've used Gentoo for one and a half years now and I have no evidence that Gentoo is declining. Gentoo's package system almost always has the newest version of a package I need in the portage tree. Gentoo recently has changed it's voting method so it is more likely the most experienced, most active developers make the decisions as part of the Council that best influence Gentoo. I also still see a good volume of postings in Gentoo's forums, and the Gentoo-wiki.

Gentoo is in a change of flux more than usual (I believe) because of the new leadership structure. And I think you can argue here that there is a warning signal going off on Gentoo's decentralization. Many people choose to create their own projects. But is this decentralization going to cause an unraveling of Gentoo? I don't think so.

Gentoo is a hobbyist's distrobution so fluxes are expected, to predict it's demise by those three criteria is a loose exposition at best. The Gentoo Council seems to be more homegenous than I have known it for the last year and a half. So I look to a greater Gentoo later. Gentoo is a great distrobution and I plan to use it for a long time.

Вот тут-то он и собрался.

Warning! Overlay at /opt/abarajameloverlay is missing a repo_name entry and the world will the probably exploit in billions of pieces!

Por que nadie me avisó de que tenía que crear un directorio profiles en mi overlay y dentro del mismo un archivo repo_name que diga "abarajameloverlay"? Y para que tanto lío carajo mierda?

Para muchos un desenlace largamente anunciado: finalmente el proyecto Gentoo anunció que cancelará su próxima versión 2008.1 y reconsiderará su proceso de lanzamientos en general. "Gentoo
se enfocará en un acercamiento más básico que ofrecerá un medio de
instalación actualizado frecuentemente y hará un mucho mejor uso
nuestros recursos humanos. Estamos pensando en lanzamientos semanales
automatizados de los CDs mínimos y de los stage y también tal vez un
LiveCD anual", dicen.

Las interpretaciones de este acontecimiento pueden ser muchas: mientras que para algunos fué efectivamente la partida de Daniel Robbins, fundador original de Gentoo, lo que mató al proyecto, para otros Ubuntu tuvo la culpa (!).

Fuente: VivaLinux!

Soluzione: proxare!

Dal menu di Gnome facciamo... Sistema -> Preferenze -> Proxy di Rete
"Configurazione manuale del proxy" e flaggare "Usare lo stesso proxy per tutti i protocolli"

il proxy d settare è....
159.149.134.17
porta 8080

buona navigazione!!!

The doman helper is one of those pesky little beasts that makes specifying EAPI behaviour formally such a nuisance (although it is nowhere near as horrible as dohtml). EAPI 2 makes it even peskier.

I'll try that again.

The doman helper makes writing ebuilds substantially easier by automagically doing the right thing when installing manual pages, freeing the developer from having to care about manual sections. EAPI 2 makes doman even more useful by making it aware of language codes as well as sections.

The painful details are available in PMS, but basically this will now 'do the right thing':

doman foo.1 foo.en.1 foo.en_GB.1

Previously only the first of the items would go to the right place.

This one's a Gentoo innovation; see bug 222439 for its history. It was shamelessly stolen for exheres-0, but was too late for kdebuild-1.

Las interpretaciones de este acontecimiento pueden ser muchas: mientras que para algunos fué efectivamente la partida de Daniel Robbins, fundador original de Gentoo, lo que mató al proyecto, para otros Ubuntu tuvo la culpa (!).

Вот это решение:

emerge -1 libstdc++-v3

p.s.: Теперь осталось дождаться сборки openoffice