Jump to content

nrc

Members
  • Posts

    86
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by nrc

  1. I made a good faith effort to answer your questions. I'm really not interested in arguing about it.
  2. It seems like you're missing the point. Yes, 1.4 was a while ago. The point is that the quoted release notes explained that Funtoo was transitioning from a Gentoo-style rolling release distro to a more curated, kit-based distro. The objective of Funtoo is to create reliable software that works for its users. In a project this size that means keeping change at a manageable level and focusing on fixes and updates that matter to the users. Prior to 1.4 Funtoo was not reliable because Gentoo was not reliable. Now Funtoo is very stable and reliable. If whatever innovation you're looking for is more important to you than that, then Funtoo isn't for you. It's very friendly to the users who don't want their systems broken by updates that provide no benefit to them. It helps Funtoo focus their effort in areas where it will most benefit users who care enough to participate. You keep talking about "innovation" but it sounds like you're really just wanting latest software releases. Funtoo may not be the best option for that if you're not looking to participate. If you don't consider Funtoo's change in direction to being a more stable, kit-driven distro to be "innovation" that's fine. Maybe that's not what you're looking for. But I'm curious what innovations you're seeing in Gentoo that you feel are lacking in Funtoo?
  3. Autogeneration of ebuilds only exists because the process and infrastructure to do it are being developed. Nobody has entered an RFE to update xfce4. Why would they make that a priority if nobody cares enough to request it? Funtoo doesn't just mirror the Gentoo tree the way they once did. That was creating too many stability problems. From the 1.4 release notes: https://www.funtoo.org/Release_Notes/1.4-release If that doesn't sound like the right distro then Gentoo may be a better option for you. The Gentoo forums are probably a better place for tips on how to migrate to Gentoo.
  4. If you check the Jira bug tracker or Discord site things are reasonably active. I think the "roadmap" is "keep making Funtoo more current and more maintainable." All the work that has gone into kits and now autogen packages has made a big difference in that respect. @drobbins pondered whether a forum was still necessary and relevant the last time he revamped the site. I felt at the time it was still important to provide that visible, easy gateway into the community for new people. But it just doesn't seem to be the kind of center of activity for the project that forums used to be so maybe it doesn't represent the project well.
  5. Ugh. Google is so bad. For anyone looking for a chromium based browser with independent sync and strong privacy features, I recommend vivaldi. #emerge www-client/vivaldi
  6. nrc

    Steam flatpak install

    Thanks. Problem was that that it was failing to extract the tarball. Not clear why. Manually extracting the tarball allowed everything to start normally.
  7. I swear that I had Steam working via flatpak for a short while. It stopped working so I removed everything and started over. No luck. When I run the app this is what I get. >> flatpak -v run com.valvesoftware.Steam F: No installations directory in /etc/flatpak/installations.d. Skipping F: Opening system flatpak installation at path /var/lib/flatpak F: Opening user flatpak installation at path /home/nrc/.local/share/flatpak F: Opening user flatpak installation at path /home/nrc/.local/share/flatpak F: Opening user flatpak installation at path /home/nrc/.local/share/flatpak F: Unknown feature type per-app-dev-shm F: Cleaning up unused container id 832053680 F: Allocated instance id 1835788086 F: Add defaults in dir /com/valvesoftware/Steam/ F: Add locks in dir /com/valvesoftware/Steam/ F: Xdg dir xdg-music is $HOME (i.e. disabled), ignoring F: Allowing wayland access F: Allowing x11 access F: Allowing pulseaudio access F: Pulseaudio user configuration file '/home/nrc/.config/pulse/client.conf': Error opening file /home/nrc/.config/pulse/client.conf: No such file or directory F: Failed to run in transient scope: No systemd user session available, cgroups not available F: Running '/usr/libexec/flatpak-bwrap --args 36 /usr/libexec/flatpak-dbus-proxy --args=38' F: Running '/usr/libexec/flatpak-bwrap --args 36 steam-wrapper' INFO:root:https://github.com/flathub/com.valvesoftware.Steam/wiki INFO:root:Will set XDG dirs prefix to /home/nrc INFO:root:Overriding TZ to EST5EDT Running Steam on org.freedesktop.platform 20.08.9.2 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/nrc/.local/share/Steam/ubuntu12_32/steam .local/share/Steam doesn't exist. If that's supposed to be created during the 'flatpak install' it's not. I thought maybe I had broken this by running the install part as root at some point but I can't find any ownership or permissions that would seem to block the install and there are not complaints during install. Suggestions?
  8. Sounds like once upon a time you were trying to get updates while DNS wasn't working for some reason.
  9. 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 corporations. It was foolish of me to think that was compatible with operating out of AWS. I appreciate the thoughts that you shared on the Twitters. Sadly, common sense is lost in a gale of hatred and stupidity on social media.
  10. 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.
  11. 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.
  12. 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 as the default init - a definite no for me.
  13. 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 expect to see Funtoo maintain that direction?
  14. 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.
  15. 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.
  16. 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
  17. 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.
  18. 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.
  19. 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.
  20. 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 you specify the server in the pacat command line it works as expected. pacat -s unix:/run/user/1111/pulse/native /dev/urandom So looking at where the default server is defined when not overridden by $PULSE_SERVER I find that /etc/pulse/client.conf contains a default setting. # Connect to the host's server using the mounted UNIX socket default-server = unix:/run/user/1000/pulse/native This will work if the userid launcing pulseaudio is 1000, but not otherwise. I changed it to hard code my UID but it could probably be dynamic for any UID using the environment variable. I'll report a bug on this.
  21. 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 the container, installed PA, and reinstalled the container. But I it appears that the Steam install persists now. Is it possible that steam is remembering the ghost of alsa-utils past? I see a line in my log that says PulseAudio access denied but I followed the config instructions to set anonymous access and pacat works. PulseAudio connect failed (used only for Mic Volume Control) with error: Access denied ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned err or: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [1230/211250.330147:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [1230/211250.331123:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory Is there a prescribed process for starting the container storage from scratch other than just removing SteamData? error.log
  22. Ok, I'll create a ticket on this but I wanted to close the loop on this thread. I confirmed that following the install instruction creates a USB drive that won't boot on my UEFI boot Alienware Alpha or BIOS boot Latitude 13. These are older systems (2015 and 2010) so maybe that's part of it. The problem is that following the install instructions creates a device that is a bootable ISO 9660 CD-ROM image with no partitioning. Maybe newer systems are smart enough to treat that as a USB CDROM but no settings on my systems would boot with it. Copying the sysrescueCD ISO file, by comparison, creates a partitioned device which includes an EFI boot partition and boots on both systems with no problem. The problem is that the Funtoo Live CD image is not a hybrid mode ISO. The solution is to convert it to hybrid mode with isohybrid: isohybrid -u funtoo-livecd-area31-5.1-beta.iso This is actually mentioned on the Funtoo LiveCD page here: https://www.funtoo.org/LiveUSB
  23. Alienware Steam Machine which is the Alienware Alpha shipped with SteamOS. Let me verify that this is still an issue. In resolving the problem that I was trying to use a rescue boot for, I discovered that something writing dumps to /sys/firmware/efi/efivars had filled the efivars storage. So it's not out of the question that the USB boot problem was related to EFI being borked in general.
  24. Has anyone been able to boot the new Funtoo LiveCD from USB under UEFI? I've created a sysrescuecd USB using essentially the same instructions and it boots under UEFI with no problem. My first attempt with the Funtoo LiveCD on USB using the 'dd' copy wasn't recognized as bootable under UEFI. I mounted the ISO and used the included script 'usb_install.sh" to install it on the USB drive. The result was recognized as bootable by UEFI but when attempting to boot it fails silently and then moves on to the next option.
×
×
  • Create New...