Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Yesterday
  2. hackbyte

    Outdated Desktop Environments

    I actually found that gentoo upstream ebuilds actually provide LxQt 0.14.1 including pcmanfm-qt and qterminal and stuff. Now, i actually need to find out how to/manage to get them together with my fresh built funtoo 1.3-kit. (Well, at least, having a funtoo within funtoo is sorta fun.. chroot ftw. ;)) P.s.: The linked git repo from shadow53 seems to be down sadly. 😞
  3. safulkin

    Outdated Desktop Environments

    This overlay for funtoo 1.2 updated up to Mate 1.20.4 Good choice for arm boards, all my asus tinkerboards with Mate DE 1.20 since august 2018. Next version Mate 1.22 (release month ago) in different new overlay for funtoo 1.3 and funtoo 1.2 https://github.com/safulkin/mate-122 Work in progress. few issues. Declared new features not tested (wayland, elogind)
  4. Fresh install of Funtoo I began getting Fetch Failed, 502 Bad Gateway and 404 Not Found errors emerging tcp-wrappers the first in the series of actually emerging KDE. After a fair amount of frustration \ research, I emerged mirrorselect and then ran mirrorselect -i -c usa Now everything is emerging with no errors. i hope this helps others. Enjoy, Scott A. Guthrie drazahoib
  5. Last week
  6. I also getting the same error message in my funtoo container # docker run --rm -it alpine sh docker: Error response from daemon: unable to find "systemd" in controller set: unknown. @drobbins, if you could fix it it would be great. Also it would good to know the cause and the fix for this issue.
  7. hackbyte

    Outdated Desktop Environments

    I'm happy to see that there is at least some base to start from. I actually have a problem with pcmanfm-qt 0.13.0 not remembering that i always want to see all (including hidden) files and just got slapped over there that 0.13.0 is outdated (for today there is 0.14.1 already). So i cannot promise anything at all but will right now go and find out how to get lxtq-base/* and x11-base/pcmanfm-qt up to the newer versions. Thanx for your work! And don't feel bad, we all have some sort of real life. 😉 Hacky P.s.: Sorry for full-quote, i don't know how to cut it down properly right now.. 😉
  8. mlinuxgada

    Funtoo release model

    @lazlo.vii You know, it will be much better if you at least try to be polite, right? @drobbins Back to the topic - if you want to get more and more involved into funtoo dev - isnt it better to have current/dev branch? If you want devs, isnt it a must to have at least dev branch,where they can work with ?! I mean, some of the major distros release based models have that : - Debian has unstable/sid -> testing ... -> stable release major/minor releases - FreeBSD has current -> release -> .. stable I still don't get it with removing current branch. Do releases, implement whatever process you think its best for you. But keep the current. Or, explain how it can be done.
  9. Also, the 3 kernel config warnings you see on emerge don't appear to be problematic. I think they can be safely ignored.
  10. Just for everyone else, I resolved this for @skygunner -- If you ever have an issue running docker in your container, just let me know and I'll take care of it.
  11. drobbins

    Funtoo release model

    Hey I just want to jump in and say it's OK, I understand if there are some people that are disappointed about us not having pure rolling releases anymore. It's fine to express your opinions here. I think that's totally understandable, frankly. Now yes, these changes were totally needed and like I said earlier, there is a strategy that is being very successful so far even though it's in its early stages. The strategy is that I support our users (with things like YouTube videos, code.funtoo.org, fchroot) to be contributors to Funtoo. So yes, right now I think it's fair to say we are playing a bit of catch-up with Oleg moving on to other things -- BUT, considering we just started this effort, I also think it's fair to say that in time we will likely catch up and even go beyond what we were capable of before. And that means that we can push ahead more with many more updates and possibly even a more up-to-date release (betas?) or a true rolling release again. In the mean time, I ask @lazlo.vii and others to be supportive of those expressing disappointment since I want people to have a place to vent their disappointment -- I don't see it being overboard or in poor taste at all -- and in my experience, the worst thing for a community is if any disappointment is bottled up and never expressed (and then we need to guess why people are unhappy) so I would much rather have people share how they feel. As long as they understand the reason for the decision, it's fine to share feedback and vent a bit.
  12. lazlo.vii

    Funtoo release model

    It seems as though you two do not understand that isn't something the our BDFL just decided to do. There are important reasons for this change. Don't take it personally that change has come you favorite distro. Complaining about the changes is bad for our signal to noise ratio and confuses the issue. Everything changes. If you can work hard enough maybe you can change it back. Again, there are important reason for this change. The biggest reason is that the one person that was maintaining the vast majority of Funtoo ebuilds is no longer doing it. If either of you can take his place go for it. Otherwise if we going to get updated packages between upstream snapshots it's going to take a few people doing a lot or a lot of people doing a little. If you two have any better ideas about how to keep Funtoo running smoothly then please share your plans with us.
  13. mlinuxgada

    Funtoo release model

    About doing smth, well, some do, me included. Small, but here and there. The question is more about the direction things are going. We all know release model is much easier than rolling distro. One of the reasons I jumped on Gentoo/long time ago/ then on Funtoo is the rolling model. Some of the others are that its source based, slots, alot of customisation/flags ... etc. My point is - today you decide to switch from rolling to release, eg no current, just freezed releases. Tomorrow nothing stops you from source based to package/bin oriented ? Maybe Debian clone /one of dozens/ ? Dont get me wrong. I use funtoo not geeky weekends, where I can spend whole day install/reinstall/fiddle with this or that. My workstation is build on Funtoo. My work depends on Funtoo. If some1 decides to flip a coin and make a decision, when I am not sure about the general direction ... I can install a Debian/Manjaro in minutes, but I dont want to. I want Funtoo as it was for years - just to have current.
  14. zogg

    Funtoo release model

    You are correct regarding contribution. Though my point was not about missing packages, but in general in the idea of switching to rolling release. It's obviously that after all @drobbins is doing amazing job, it's just the current idea of future updates does not suit me or/and some others. For me rolling release is the reason I was on Gentoo and after that Funtoo for about 15 years and it is natural that such change is something that would make me consider if this is the way I want to go. And I did contribution to Funtoo , small but still... As today I have less timne and opportunity to hack around and break my work setup especially :(
  15. bcowan

    Pulseaudio installation breaks

    PR was merged last night, so this should be fixed with an ego sync hopefully 🙂
  16. lazlo.vii

    Funtoo release model

    Do something! Submit patches, file bug reports, write wiki articles, donate a few dollars to Funtoo on a monthly basis. Something is usually better than nothing. If you are annoyed with the changes in the short term just remember that these are only the first steps in a new direction. It will take time for the momentum to shift but all of us can reduce that time by doing something. You have adequately expressed your displeasure with the current state of the distro and more over you have had a direct response from the only person who can make a decision based on your input. Rehashing your arguments and cherry picking examples to make to your points isn't going to do a single thing to make Funtoo better.
  17. Earlier
  18. sacviper

    Pulseaudio installation breaks

    Thank you for your help
  19. zogg

    Funtoo release model

    To be fair enuf, it seems little bit confusing "new technologies" and slow updates. In order to maintain own packages (hello also dependencies of those packages) by yourself + few pull requests from other people vs gentoo community - it would be funny to maintain yourself whole distro (are we LFS now?). Or to bump you for each build and wait for your response. (after all we'll get messy yaourt as in arch with lists of half dead overlays with duplicated and conflicting packages - yay stability \o/ ) It's pity that new distro technology comes as price for new packages and up-to-date software. In other words - it is sad chapter and i think in order to gain stability for end user you would lose actually people who has enuf knowledge for people who is know how to copy paste from instructions without understanding 😄 here is from top of my head as I wanted to check AV1 support lately Funtoo / Ubuntu mpv 0.27.2/0.29.0(AV1 support comes here) chromium 71.0.3578.30/73.0.3683.86 Seems like for the past few months only update I saw in funtoo was vim version bumps 😛
  20. tbill

    Getting KDE to start

    Yes, dbus is enabled. I use consolekit; elogind in not installed. I'm going to try gnome. I've always used KDE in the past, but I think there is, right now, an issue with KDE's display manager. (Besides, I really enjoy starting an install from scratch....) Thanks for responding, Otakku!
  21. Hi, In my funtoo hosting container, I tried out docker following this page https://www.funtoo.org/Package:Docker After emerge I got this message output * Unable to find kernel sources at /usr/src/linux * Unable to calculate Linux Kernel version for build, attempting to use running version * CONFIG_MEMCG_SWAP_ENABLED: is not set when it should be. * CONFIG_CGROUP_HUGETLB: is not set when it should be. * CONFIG_RT_GROUP_SCHED: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. Should I worried about this? The symbolink /usr/src/linux is pointing to linux-debian-sources-lts-4.9.130, but the host seems to running 4.9.110 I removed the old symbolink, copied linux-debian-sources-lts-4.9.110 from host folder to there and made a new symbolink When I tried to run the hello world docker image docker run --detach --name app carinamarina/hello-world-app I got this problem: docker: Error response from daemon: unable to find "systemd" in controller set: unknown. I know funtoo by default is not using systemd. What settings/change should I make to the system to use docker for my development? Thank you.
  22. bcowan

    Pulseaudio installation breaks

    I submitted a pull request to fix this, the patch is missing for the ebuild. Drobbins will hopefully fix when he gets some time :)
  23. sacviper

    Pulseaudio installation breaks

    Trying to install pulseaudio but emerge fails please have a look [32;01m * [39;49;00mPackage: dev-cpp/eigen-3.3.5-r1 [32;01m * [39;49;00mRepository: dev-kit [32;01m * [39;49;00mUSE: amd64 elibc_glibc kernel_linux openmp userland_GNU [32;01m * [39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking eigen-3.3.5.tar.bz2 to /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/work >>> Source unpacked in /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/work >>> Preparing source in /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/work/eigen-3.3.5 ... [32;01m*[0m Applying eigen-3.3.5-fix-prototype.patch ... /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/temp/environment: line 1338: /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/files/eigen-3.3.5-fix-prototype.patch: No such file or directory [A[182C [34;01m[ [31;01m!![34;01m ][0m [31;01m*[0m ERROR: dev-cpp/eigen-3.3.5-r1::dev-kit failed (prepare phase): [31;01m*[0m patch -p1 failed with /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/files/eigen-3.3.5-fix-prototype.patch [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 92: Called src_prepare [31;01m*[0m environment, line 3126: Called cmake-utils_src_prepare [31;01m*[0m environment, line 1092: Called default_src_prepare [31;01m*[0m phase-functions.sh, line 933: Called __eapi6_src_prepare [31;01m*[0m environment, line 245: Called eapply '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/files/eigen-3.3.5-fix-prototype.patch' [31;01m*[0m environment, line 1403: Called _eapply_patch '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/files/eigen-3.3.5-fix-prototype.patch' [31;01m*[0m environment, line 1341: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/dev-cpp/eigen-3.3.5-r1/files/eigen-3.3.5-fix-prototype.patch' [31;01m*[0m isolated-functions.sh, line 121: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m die "$@" [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=dev-cpp/eigen-3.3.5-r1::dev-kit'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-cpp/eigen-3.3.5-r1::dev-kit'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/work/eigen-3.3.5' [31;01m*[0m S: '/var/tmp/portage/dev-cpp/eigen-3.3.5-r1/work/eigen-3.3.5' Any suggestion please let me know ?
  24. Otakku

    Getting KDE to start

    dbus is enabled and do you use consolekit or elogind ? and show some screens
  25. tbill

    Getting KDE to start

    Core system working well, including X. Problem is getting KDE to start; it doesn't. Tried sddm first - followed suggestions, adding it to /etc/conf.d/xdm DISPLAYMANAGER="sddm". That caused the system to hang when rc started xdm - got a blank screen with the mouse cursor, but nothing worked beyond that. Rebooted with the sysresqcd to log onto the system and delete xdm (with sddm as displaymanager) from the rc-update default setting. I've heard good things about gdm, but found no mention of someone using it to start KDE, and no instructions for how to aim the displaymanager at KDE, much less any other desktop environment. BTW, I followed what directions I could find as far as setting up sddm, including other users experiences with the frozen login screen. I'm stumped! (Again!)
  26. Note to all -- this kernel has been unmasked and is ready for general use.
  27. Hey Everyone, @temptorsent has graced us with completely rewritten-from-scratch nvidia-drivers and related ebuilds that will be serving to replace the ones we are currently using from Gentoo. Please help us out and test them! See the instructions here for how to start using them for testing: https://www.funtoo.org/Package:NVIDIA_Linux_Display_Drivers#TemptorSent's Experimental NVIDIA ebuilds These ebuilds will be enhanced to support our upcoming GPU accelerated container support. Best, Daniel
  28. erikr

    Networking concept help

    Thanks for some good hands on tips lazlo.vii and the area is both as full of different advices as it is lacking good resources. When it comes to files systems I do BTRFS mostly but on the server I do ZFS. I once had problems with ZFS where I removal of a zfs from the pool messed things up. I solved it with a FreeBSD live-cd where I imported the pool, removed the zfs and exported the pool. It worked like a charm and since long the bug is fixed. I still have a "thing" for ZFS though and decided to go for it some time ago (I participated in another forum post here about ZFS some time ago). I already have the pools setup on my current installation and will reuse them in the new server. The current network setup plan is as follows: AppServer on DMZ FileServer on HomeNetwork An intermediate physical network between AppServer and FileServer with fixed IPs and just a switch. This way I can make a really narrow IP-filter on the FileServer side for this particular network and I will rely on ZFS export mechanism to export the right stuff. I will try to block unexpected IPs from on the FileServer preventing the AppServer acquire access the nfs-exports meant for the home-network ( nfs will use the IP to determine export rules - faked IP meaning wrong nfs access). Most likely I will look into SELinux, a new area for me. Containers are new for me (from hosting point of view) as well but I will learn eventually 🙂 Cheers, Erik
  1. Load more activity
×