stac80

I just resynced my tree and updated and it worked as expected. I was just coming here to say as much but you beat me to it. Thank you Oleg!

Has anyone run across an error like this one when upgrading? !!! All ebuilds that could satisfy "x11-libs/libXres" have been masked. !!! One of the following masked packages is required to complete your request: - x11-libs/libXres-1.0.7::gentoo (masked by: invalid: DEPEND: USE flag 'ppc-aix' referenced in conditional 'ppc-aix?' is not in IUSE) There is no mention of ppc-aix in the offending ebuild. I'm not sure where to begin with this problem because it doesn't make much sense. Here's the ebuild: # Copyright 1999-2017 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Id$ EAPI=5 inherit xorg-2 EGIT_REPO_URI="git://anongit.freedesktop.org/git/xorg/lib/libXRes" DESCRIPTION="X.Org XRes library" KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris" IUSE="" RDEPEND="x11-libs/libX11 >---x11-libs/libXext >---x11-proto/xextproto >---x11-proto/resourceproto" DEPEND="${RDEPEND}"

I don't see your point about Funtoo choosing to be left out of the systemd club. I can't speak for the Funtoo community at large but I think Funtoo itself is systemd agnostic. Anyone is welcome to run Funtoo with systemd or with Openrc. If upstream packages support systemd then they should also work on Funtoo. Funtoo leaves that choice up to the end user which is, to me, a "pure" linux way of doing things. Every Funtoo installation is like a snowflake; everyone different and unique.

I use ati-drivers and had a problem with X booting to a blank screen very recently. There was a new config file placed by a recent update into /etc/X11/xorg.conf.d/20opengl.conf In it there was a reference to a non existent folder for loading modules. You might start there and see if you're experiencing the same update? I just commented out the one that was incorrect and my X booted up as expected. What do your Xorg logs say?

Btrfs is a great filesystem to use and Btrfs works great on Funtoo: I've been using Btrfs successfully on Funtoo for over a year on my file-server on 4 x 3 terabyte drives in a mirrored (RAID1) setup. I initially had only two drives but added two more when space started to run out. It couldn't have been easier to put additional drives into the RAID array. (Step 1. Plug drives into computer, Step 2. #btrfs device add /dev/sdx /export) I've seen a number of improvements in Btrfs tools since I started using it and I think Funtoo may be the ideal distribution to run Btrfs on because improvements are constantly being added to the kernel so having the latest kernel, which a lot of other distros do not have, makes a difference. A part of me is looking forward to a drive failure just so I can do a drive swap without any data loss (hopefully).

While there isn't a 2015-04-11 stage3 tarball you should be fine to copy the funtoo install documents exactly to get the latest current stage3 tarball. # cd /mnt/funtoo # wget http://build.funtoo.org/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz You may be having trouble if your network connection isn't working in which case you need to download the tarball and put it onto your installation media before booting into the install process.

It's not a dumb question. There is no "default" anything in Funtoo. You can pick and choose all your applications and through your choice of USE flags can further define what capabilities your various pieces of software are compiled with. Funtoo is the ultimate personalized linux os. That being said; If you want to install PulseAudio then all you should need to do is add pulseaudio to your USE flags in /etc/portage/make.conf and do an update. That will most likely pull in pulse and its dependencies. This might also help: https://wiki.gentoo.org/wiki/PulseAudio

I had the same issue. Everything worked for a long time with dhcpcd getting its IP from my DD-WRT router, which also handled all the DNS for my lan; including handing out a "static" IP to my server. I honestly don't know what changed either. I generally don't reboot too often so many updates had happened in the interim making it unlikely I was going to be able to track down the exact change that caused the problem. The solution that worked for me, once I realised samba was failing because it wasn't getting an IP early enough, was with the Funtoo networking config assigning my IP address during boot before samba gave up and failed. This is what I have in my /etc/conf.d/netif.eth0: template="interface" ipaddr="192.168.145.22" gateway="192.168.145.1" nameservers="...." domain="server.me.lan" But like you said, it might be your upgrade of OpenWRT that did it.

I had this problem a while back. It stemmed from the fact that the network was not coming up before the samba server tried to start. It turned out that the zero configuration set up (dhcpcd) was taking too long. My solution was to create a static ip network configuration via the Funtoo networking configuration system. (http://www.funtoo.org/Networking) My server is not in a VM though so I don't know if this is relevant to you or not but hopefully this points you in the right direction.

I don't have a lot of experience dual booting with Funtoo nonetheless I'm going to suggest that you add an entry for PC-BSD in your /etc/boot.conf and run boot-update. That should create an entry for PC-BSD in your Funtoo managed Grub menu. The specifics of what to add to boot.conf, to get PC-BSD booting, I am unsure of. Perhaps someone else can chime in?

That's a good question. Normally I would think that boot-update could handle adding Funtoo to grub. It might clobber the settings from Arch unless you configure your /etc/boot.conf to include it.

Related to my other post about mission critical services on Funtoo hosting. If one wanted to transplant a container to another datacenter what would the likely-hood of incompatibility be? or other possible hurdles?

Is running something "mission critical" a good idea on our Funtoo hosting accounts? (My specific use isn't strictly mission critical so I might try it anyway but in case others are considering it.) If not what would y'all recommend? Is anyone else out there offering funtoo hosts?

I've had an on again off again relationship with regularly monitoring my logfiles. I've used app-text/multitail which is good but I feel like there's probably something better out there that I'm not aware of. (By "better" I mean a log viewing program that is as simple or simpler than multitail. I don't monitor enough hosts to have some elaborate enterprise behemoth.) So do you guys generally monitor your logs in any way or do you use them when something goes wrong? I've done both and to be frank waiting until something stops working seems, for me, to take alot less "mental energy" than constantly having a terminal with log files spewing forth and that constant nag to want to check them. At the same time I catch little bugs and warnings, misconfigurations etc when regularly monitoring logs. I definitely feel more confident in the security and overall "health" of a more consistently monitored system. Where do you guys draw that line between consistent monitoring and checking logs retrospectively once something breaks? What tools do you use? (Don't limit yourselves to ebuilds. If you have trained a monkey or some other "offline" tool or trick to do this task I would be very interested in hearing about it.)