Jump to content


  • Content Count

  • Joined

  • Last visited

About zogg

  • Rank

Recent Profile Visitors

453 profile views
  1. Hi, same as steam requires 32bit, wine requires 32bit for some application(or games in that matter, e.g. Battle.Net) So I created docker (basically same way steam one if made) and it seems to work. It would require wrapper to launch it and proper ebuild. I'm not sure if I'm going to continue working on it, but if anyone want to take over or play starcraft 2 😛 https://github.com/funkycode/funtoo-wine-launcher - dockerfile https://quay.io/repository/funkycode/funtoo-wine-launcher - docker image to launch: # Make folder for steam data STEAM_DATA_FOLDER=~/wineData mkdir -p ${STEAM_DATA_FOLDER} # Update to your image if you want WINE_NVIDIA_IMAGE=quay.io/funkycode/funtoo-wine-launcher # Name of the container to be used WINE_CONTAINER=wine-nvidia-${USER} nvidia-docker run -ti --privileged --name ${WINE_CONTAINER} -e WINEPREFIX=/home/wine -e DISPLAY=$DISPLAY -e PULSE_SERVER=unix:${XDG_RUNTIME_DIR}/pulse/native -v /tmp/.X11-unix:/tmp/.X11-unix -v /dev/shm:/dev/shm -v ${XDG_RUNTIME_DIR}/pulse:${XDG_RUNTIME_DIR}/pulse -v ${STEAM_DATA_FOLDER}:/home/wine ${WINE_NVIDIA_IMAGE} bash #example of how to launch battle.net in container (if it's installed, if not just downlaod it and copy to steam data folder and run wine inside container on that file) wine /home/wine/drive_c/Program\ Files/Battle.net/Battle.net\ Launcher.exe
  2. I don't mind anyone checking my overlay or using it, but I'm not sure I want to maintain and take responsibility for that one, as I'm not sure I would keep using deepin or funtoo (already moved work laptop back to gentoo) P.S. I also update to latest LTS nvidia kernel modules (440.82) as I'm using 5.6 kernel from gentoo 😄
  3. I was able to adjust Gentoo overlay and using it as DE right now :) I have overlay, but I added some flags and packages manually and it might require some instructions
  4. If you need to report most of the things — it is kinda doing it yourself. It is fair to tell that it's homebrew distro and noone owns you anything. But if you advertise your distro asstable and that it can be used in production, regardless of it being free or not — you need to provide certain standards. There is a problem of small group of maintainers in Funtoo and it's logical that it would not have all fixes and there would still be problems. The question is the % of the user input vs maintainers work. If there is need for all users to always report - it's not everyday stable usage (at least if you use it not at home as desktop env) It's not about newer (and gentoo has 9999 ebuilds, they are just hard masked). No one asks for the latests software that was released yesterday, but as mentioned above except vim there were barely any ebuild updates for more that few months. Even ubuntu which is LTS has newer packages. The question is the proportions and what distro advertise itself as. Sure not everything in gentoo compatible and requires some manual changes (can it be automated?), but this is exactly the problem of "why use all power that is already not enuf for new features and break compatibility with gentoo which resources can be used? Would not it make Funtoo good as idea and innovation comparing to Gentoo, but it will stay as an idea, while it will always have not enuf users/maintainer" or maybe innovate less and work on automatic gentoo merge into funtoo till it has own maintainers and more users, so it can be more independent from gentoo and can be tweaked even more. It all comes back to the roadmap and the calculation of your resources vs your plans in more realistic way.
  5. I am not sure where and what builds were, but I trust 1.3 branch git commits history. And do not blame me of missing links to any bug report, as you obviously missed whole point of my post and cherry picking exactly things you want to answer to, while sticking to golang. I did contribute to Funtoo when I could (yes it was long time ago, when Funtoo just started and Martin and other guys was in core team), but currently I have less time and opportunity to do it. I did not report as I did not check what vulnerabilities golang or kubectl (somehow you did not comment on that one) have when I wrote the post (I work with those and I know there are some found this year). It was less important for me if they are vulnerable on Funtoo as in production I use golang docker images to build golang applications.
  6. wrote previous reply before read yours :) in general I do agree with you, but I do not compare with Gentoo, I suggest to co-exist as with any other useful resources that can be used, that's it.
  7. It was updated yesterday (I assume because of the post) to 1.12.x :D Before as I see from Januar 03 we had 1.11.4 which has vulnerability in link below, vulnerability was published at 24th of January, which gives us Feb, March + almost April till yesterday. https://www.cvedetails.com/vulnerability-list/vendor_id-14185/product_id-29205/version_id-280874/Golang-GO-1.11.4.html Though my point is not specific software, but that switching release model doesn't make automatically everything perfect and stable (secure is stable in my opinion at 2019). I think that Funtoo has less maintainers and people contributing vs same Gentoo and instead of switching, as a solution thinking it would take less time and power to maintain system, while keeping it stable, would not resolve the issue. And as all work done in Gentoo can be utilized as well, maybe instead of more and more breaking compatibility (after all most of us came from Gentoo, which was also Daniel's creation) it can be used as experimental, current can be more stable and stable would have releases maybe with some LTS tagged once. The basic same idea of stable, masked, hard masked. Where power is thrown to automate the process of merge from Gentoo with patching what is needed. At least till the user base grows. Anyway it's just my opinion and for sure anything can suit everyone, after all it would be fair to tell me - "you want something different — you can always make your own", as it's easier to give critics from the couch :P
  8. The latest update 5 months ago and latest version 1.13.2 — https://github.com/funtoo/nokit/tree/6f2923d531ffd96789bec3cebdb0249ec27bfe77/sys-cluster/kubectl As an example CVE that effects this version — https://www.cvedetails.com/cve/CVE-2019-1002101/ I assume if you want to search you can find more :D
  9. From my understanding anyone that is so concerned about stability should not use current masks and use stable ones instead. Telling that waiting for release for 6 months in case you need to fix something on your system (don't tell me that if it says stable it will be 100% perfect and bug free, especially if it's done by 1.5 person). As an example I have some 32 bit software I can't use with 1.3 release as no proper workaround is ready now, so it forces me to have chroot with new system I need to maintain as well for this 32bit software or being stuck on 1.2 which is broken (Oleg words btw) and just left to die as is. Meaning I have no security updates and using old system or I can update to half working which I never be sure when will be finished (if at all). So I'm not sure about what stability and "I don't want to fight with my computer systems, I want to use them" he was referencing. So what we have now is that latest Ubuntu LTS (binary based one) already has newer packages (including system/core ones). I'm not even sure if all critical CVEs are fixed by anyone on Funtoo (telling me I can do it - means exactly "fighting with your computer" btw). So it seems that stability means — don't touch as it is working? :D I really do not understand why not utilize Gentoo ebuilds that are built by much bigger community and reinvent new concept that requires much more man power and maintenance while much less people are now involved in any of this on Funtoo side. I mean, sure kits are great idea, but why not just prepare automation that patches/breaks gentoo portage into kits first and grow maintainers and contributors power first, instead of making plans for perfect release in long distance future ( if Funtoo will survive at all till then.) P.S. Community ebuilds - much worse than rolling release, as no QA there and look at yaourt as an example on Arch - it is such a mess of duplicated and messed packages with broken dependencies. So I'm not sure how stable and ebuilds done by community members who need tutorials to do it comes along
  10. 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 :(
  11. 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 ?
  12. I am with you. It's pity that even Ubuntu gets newer packages than funtoo :(
  13. Aren't you describing the whole idea of stable, masked and hard masked? or as in funtoo was stable, current and experimental? I think it was a reason I used gentoo and now funtoo. Current was stable enuf or you could always mask yourself the package till update with fix will come out. On other hand you could just easily unmask still not stable package and if needed resolve dependencies, flag updates and etc if needed. Otherwise if the point of snapshots to give stability, what's the point of being source based at all? :)
  14. Just happened to me on 1.3 o.O Moved /var/git/meta-repo and synced from scratch to resolve the issue
  • Create New...