Jump to content

nrc

Members
  • Content Count

    83
  • Joined

  • Last visited

  • Days Won

    18

nrc last won the day on May 2 2019

nrc had the most liked content!

About nrc

  • Rank
    Advanced Member

Personal

  • Location
    Columbus, Ohio, USA

Recent Profile Visitors

1,524 profile views
  1. Sounds like once upon a time you were trying to get updates while DNS wasn't working for some reason.
  2. Thanks for the update. I probably won't look to update my image until I'm ready to migrate my crufty old vBulletin to something else. But given the recent unpleasantness I may look to move it to a Funtoo container when that happens. Not that I have any sympathy for those who are now rightfully being rounded up for their wrongdoing. It just appears that, like so many other corporations, Amazon cannot be trusted to operate in good faith in the face of an activist mob. Part of my motivation for supporting open source has always been to remain out from under the control of large
  3. I received a note from AWS yesterday saying that the official Funtoo images will no longer be offered on the AWS Marketplace. Just mentioning it to make sure that it's intentional and not something AWS does automatically because they haven't been touched in a while.
  4. As long as I can file a bug report if systemd artifacts stink up my system, I'm fine with that. :) You and the community have done a remarkable job of making everything work seamlessly when many swore that it would be impossible to sustain distros without systemd. Thank you for that.
  5. Since they're pulling gentoo packages I'm not sure how much difference the freshness of the ISO makes. I assume it's a stage4/installer package and you can build from there. For comparison, Funtoo 1.4 was released Sept '19. That's the interesting thing about this, if they have an easy installer and a more friendly package manager it could significantly extend Funtoo's reach. They are at least in the top 100 on distrowatch. That probably represents at least a doubling of users benefiting from Funtoo developments. The one concern for me is that Sabayon currently ships with systemd a
  6. I'm not familiar with Saybayon but looking through their site it looks like they could bring some valuable contributions to the Funtoo ecosystem. Simple installation and package management could open Funtoo up to a much broader audience. However, it looks like Saybayon installs systemd by default in their current incarnation. One of the key benefits of Funtoo for me has been that it is not just systemd-free, but openrc exclusive. That ensures that everything on Funtoo functions with openrc and it avoids the convoluted multi-init support documentation we see on Gentoo. Can we exp
  7. Once upon a time Funtoo just pointed to Gentoo packages. Those tend to be very fresh but created a lot of breakage. Now updates on most packages are curated to keep things more stable. Community members are encouraged to provide pull requests to rev packages if they like. The cool new thing is autogen packages which can automatically generate a new ebuild for a release. These are fairly easy and bulletproof for binary packages which is why some of those are fresher than the source packages.
  8. On --depclean, it doesn't really matter. It just cleans up packages that weren't explicitly installed or required by something that was. So it's a cleanup process to keep things tidy. On libtool, I've never seen that recommended, but usually on a x86-64bit system /usr/lib is a symlink to /usr/lib64.
  9. For the Funtoo live image make sure that you're using the version downloaded from the funtoo.org site. The 'file' utility should report it as having a DOS/MBR partition and not just and ISO-9660 file system. The ISO-9660 image that Area31 creates won't boot from a USB drive on some systems. # file funtoo-livecd-area31-5.1-beta-r1.iso funtoo-livecd-area31-5.1-beta-r1.iso: DOS/MBR boot sector; partition 1 : ID=0x17, active, start-CHS (0x0,0,1), end-CHS (0x3ff,63,32), startsector 0, 3217408 sectors
  10. I use Cyberpower UPSs and I run their utility. I installed from the tarball download and everything worked with no problem. I like the fact that it lets me turn off the UPS alarm which drives our dogs nuts. I must admit that I've never been around when it has reached the point of shutdown and I've never verified the shutdown from the log files.
  11. Run `ego sync` and then do a full update `emerge -auvDN @world` and try again. 2.4.0 is the current dev-python/testtools and it doesn't list a python_targets_python2_7 USE flag.
  12. I'm glad it was helpful. @drobbins had fixed the image on build.funtoo.org. I'm not sure if it regressed or if we just need to get the hackerspace folks to update theirs.
  13. I figured this out. I found that sound works in the container with pacat under the root account but not when I su to the steam account. Whenever I create an account I use the same UID which is not 1000. Using 1111 for this example. It seems like the root environment that you get when you attach to the container gets the environmental variable passed to the container at runtime that points to the correct pulseaudio socket. PULSE_SERVER=unix:/run/user/1111/pulse/native But when you su to the steam account that variable isn't set. So it's trying to use the default socket. If
  14. I'm having a similar issue. Steam is looking for ALSA. In my case restarting Pulse does not fix it. I assume this is on the host system since I don't see PA running in the container. Sound is fine from pacat in the container and it shows as a stream in pavucontrol. The steam client itself never shows up in pavucontrol. Background - I had to install PA (ptui!) since I've been an ALSA holdout. But first I tried tinkering around a bit trying to get ALSA working. Installed alsa-utils in the container and tried some different run options on the docker launch. No luck so I wiped th
×
×
  • Create New...