jorgicio

Did you set the kernel settings before installing systemd? http://wiki.gentoo.org/wiki/Systemd

Indeed, you must install the networkmanager package with the USE="plugins_openvpn" to bring support for that.

Consider using mcpdf instead of pdftk. The reason is explained in the bug link you posted.

Edit /etc/conf.d/xdm to use the prefered display manager (KDM, GDM, LightDM, etc.), add the service to the default level: rc-update add xdm default It also must be started. And add your user to the bumblebee group. Everything must be work fine.

Is there a way to setting the Grub GFX Theme using files such as /etc/boot.conf ? Or adding some other entries such as memtest+. Thanks :D

I followed that tutorial: http://liquidat.wordpress.com/2013/12/19/howto-share-ethernet-via-wifi-with-networkmanager-in-kde/ And compiled with the necessary flags, and also activated the package forwarding. However, I created the access point, as mentioned on that link, then I connected from my mobile phone, and it's working, but it can't surf the web. A connection without forwarding packages. Checked iptables, and everything is clean. Thanks.

Ok, but at least, if some packages are working fine as they where (as happened with Gentoo), I don't know why the modifications done, for example, with imaging. Indeed, it's using the former name (now it's called Pillow).

Well, I understand, while Gentoo's GCC is working for toolchains, everything's ok :)

In a few words: Chromium, since release 36, doesn't support NPAPI plugins (Netscape), but use PPAPI plugins (Peppermint). The ns-plugins in java, means for Netscape, so Chromium/Chrome won't support it since then. The only remaining options are: Using another browser that supports Netscape plugins. Waiting for a PPAPI plugin for Java.

As an Arduino developer, I use crossdev for creating toolchains (in this case, avr), but then I found recent versions (from 4.6.4) don't support cross-compiling, and I don't know why. 4.6.2-r2 has some errors at compiling, and I had (for a while) to use a pretty older version, 4.3.3. Anyway, as a workaround, I had to download the Gentoo GCC ebuilds (that support toolchain), and all works flawlessly. Also, I made a script for that. #!/bin/bash URL="data.gpo.zugaina.org/gentoo/sys-devel/gcc/" #URL="sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/gcc/" PORTDIR="/usr/local/portage/cross-avr" wget -r --no-parent --reject "index*" --quiet "http://$URL" if [[ -e "$PORTDIR/gcc" && -L "$PORTDIR/gcc" ]];then rm -v $PORTDIR/gcc fi cp -r $URL $PORTDIR if [[ "$?" == "0" ]];then echo "Success!" else echo "Something failed" fi echo "Cleaning..." rm -rv $URL Now, my question is: it will be (re)supported in future ebuilds for, at least, most of the Funtoo GCC ebuilds?

You're welcome :D Also, there's something I can't understand: Why Funtoo imaging package does not generating the headers as the Gentoo ebuild does. Anyone knows?

The same thing happend to me. I reported it as a bug in the bug tracker, and they said the newest version of uniconvertor will be masked for now. Meanwhile, as a workaround, I created the imaging-headers ebuild. That's on my overlay: https://github.com/jorgicio/jorgicio-gentoo Install it, (together with imaging itself and python-imaging), then compile the newest version of uniconvertor, and all works like a charm.