So yes, it works just as easy as the doctor sez it does. Nice that the Gentoo Handbook is updated for GPT and UEFI. Thanks to Gentoo volunteers for that. I presume the bios_grub partition is for Windows dual boot; I do not use one. genkernel installed files into /boot
Well, after I got into reading that wonderful set of documentation, the added complexity of encrypting the file systems and LVM was a bit distracting; causing me to lose track of the details that I am trying to sort out. Haha! :)
So, now I am back to the updated Gentoo Handbook, on this page ...
Is the fstab in the aforementioned Quick Installation Guide workable with the partitions created and subsequent mount points from an earlier section of the document?
In an attempt to make use of my current state, here is what I did. While chroot'd, sysresccd boot # mount /dev/sda2 efi sysresccd boot # grub2-install --target=x86_64-efi Installing for x86_64-efi platform. Installation finished. No error reported. where, sda2 is the vfat ...
I'd like to get a kind of sanity check regarding the document Quick Installation Checklist . Can it be relied on for UEFI booting? I would have thought the document would mention 'efibootmgr'. But what do I know. :) I suppose my ultimate question about that guide is, "Does it cover ...
During the last couple of days a gentoo system would not make it through complete build of world. The update of libpeas was consistently failing. I barely recall what the log said. :) I decided to simply try adjusting use flags to see if it helped and it did.
I saw the new ebuild for django 1.7 and decided to uninstall the one installed via pip and go with this one. I'm assuming that the Gentoo community decided that the bundle created by the django dependency list is a useful collection for use with django.
Hopefully, you are meaning 1TB, not 1GB. As 1GB for $50-55 is rather high (specialy considering a dvdr holds about 4GB, and you can get a pack for about $15-20) Yeah. 1TB last week for $55. This week, $75. Appears to be basically same specs, different warranty: 2yr, 5yr respectively. Perhaps that ...
You appear to have wiped your vdb (the installed pkg database): /usr/sbin/python-updater: line 758: /var/db/pkg/*/*/RDEPEND: No such file or directory So yeah you might have to reinstall: you can save off your configs, like /var/lib/portage/world but get a more comprehensive list first. Thanks so ...
Indeed, I have the following during all the portage complaints: $ eix sys-power/upower * sys-power/upower Available versions: 0.9.23-r3 0.99.0-r1(0/2) {doc +introspection ios KERNEL="FreeBSD linux"} Homepage: http://upower.freedesktop.org/ Description: D-Bus abstraction for enumerating power ...
Does portage sometimes say the wrong thing? or is it merely confusing? Perhaps a bad ebuild is misguiding us in our attempts to get through this systemd madness.
Can someone help me interpret what the following snippets indicate? # emerge -NDutvp world [ebuild N ] media-libs/cogl-1.18.0:1.0/20 ...
I'm using the gnome/systemd profile; masking sys-power/upower-pm-utils works, thanks.
I still think this either shouldn't be necessary or at least hinted at in the news item. I have a pretty standard stable gnome/systemd system, so I guess this confusion affects a bunch of people. upower-pm-utils ...
I read somewhere that I can remove, PYTHON_TARGETS, USE_PYTHON as they are unnecessary. As I should leave the system's python alone and instead use pyenv or whatever is the equivalent of rvm (for ruby)
Here is state of my system's portage config $ emerge --info Portage 2.2.10 (default/linux/amd64 ...
I do not know what action to take. Can anyone help? I think I have systemd issues... My `eselect profile` is set to [3] default/linux/amd64/13.0/desktop *
So, to begin... Is this a sign of waiting too long before sync? # python-updater --enable-all * Starting Python Updater... * Main ...
I think I recognize a bit of "customer focus" here from ssuominen. :) So, I appreciated the operative string supplied to get me going in a familiar way, without taking a whole lot of his time to be comprehensive. I was very grateful, man!
It seems there's some good clarifications in this thread as ...
Thanks tons for the "clue-by-four" and the solution to immediately disable this feature.
I've started reading this, now: Predictable Network Interface Names
I may as well learn the new way, while I am at it!