palica
-
Posts
294 -
Joined
-
Last visited
-
Days Won
11
Content Type
Profiles
Forums
Blogs
Posts posted by palica
-
-
probably missing ipv6 connectivity on the second one
-
well, lxd init should actually propose to create a lxdbr0 interface that will be used for network inside containers. if you have missed or skipped that part I recommend to go back and try again as it is the easiest thing to do.
so basically you need a bridge interface in the host so the containers can attach to it and you should get internet through your host.
if you need any help contact me on IRC
-
checkout icecream - distributed compiling
-
rm -rf /var/git/meta-repo
ego sync
-
13 hours ago, sibok said:
The problem about switching to a branch is that one first has to know that branch exists. I was wondering if Funtoo got the right portage/kits/system package tools to deal with packages and these kind of things.
most of the stuff gets announced https://forums.funtoo.org/forum/5-news-and-announcements/
available are always only the branches that are part of the release. 1.3-release is now release as beta quality. so test it out and report any bugs that you encounter.
some of the branches get named after the release some are named after the version of the software they are incorporating like kde-5.12 gnome-3.26 perl-5.26 python-3.7 ... and others just have many different software and are simply named 1.3-release. there is no other description visible using currently available funtoo tools.
stability can be found here:
https://github.com/funtoo/kit-fixups/blob/master/modules/fixups/foundations.py#L5-L12
class KitStabilityRating(Enum): PRIME = 0 # Kit is enterprise-quality NEAR_PRIME = 1 # Kit is approaching enterprise-quality BETA = 2 # Kit is in beta ALPHA = 3 # Kit is in alpha DEV = 4 # Kit is newly created and in active development CURRENT = 10 # Kit follows Gentoo currrent DEPRECATED = 11 # Kit is deprecated/retired
switching to kde-kit from 1.3-release while still on 1.2-release will fail when doing ego sync, but can be done manually (although not recommended and definitely not supported).
You could manually switch to kde-kit from 1.3-release by checking out the appropriate sha hash of the commit as listed here: https://github.com/funtoo/meta-repo/blob/1.3-release/metadata/kit-sha1.json
but this has to be done after every ego sync.
-
thank you for your positive and friendly answers.
I explained to you that 1.3-release branches will show up once you switch to 1.3-release, 5.12-prime is there from 1.2-release and master branch is a remnant of 1.0-release (at that time called 1.0-prime)
here are the definitions that are used for kit generation, maybe that will answer your question
https://github.com/funtoo/kit-fixups/blob/master/modules/fixups/foundations.py
there is not a simple way of switching to a different branch of a kit (1.3-release for kde-kit) without actually switching the whole release = all kits to the 1.3-release.
from the user perspective you should edit /etc/ego.conf and add in [global] section release = 1.2 (1.3) and perform ego sync ego will then switch the kit branches for you. There is a reason you cannot see all branches of a kit on a single release as these are untested and will probably not work.
if there are multiple branches supported they are listed in ego kit list output and they can be switched using /etc/ego.conf with a value for example xorg-kit=1.20-release inside [kits] section.
if you want to go your own way (switching a single kit to a different branch that is not supported for a given release) - you will probably not receive any official help from funtoo. (and definitely not from me ? )
-
2 hours ago, sibok said:
Looking at github or playing with git locally one can see kde-kit has the following branches:
- master
- 1.3-release
- 5.12-prime
I wonder if it's possible to get that info through ego or any other specific GNU/Funtoo Linux command?
so you looked at github and explored git locally - no sign of ego kit list here. You wonder if there is a way to do it with ego or any funtoo specific command -> ego kit list
1.3-release will show once you switch to 1.3-release in ego.conf
[global]
release = 1.3
the stability tag:
current - tracking gentoo
prime - somehow seen as good for production
anything else - alpha, beta, dev => not good for production if you are not a developer
-
~ ❯❯❯ ego kit list kit is active? branch stability core-kit active 1.2-prime prime core-hw-kit active master current security-kit active 1.2-prime prime xorg-kit 1.17-prime prime active 1.19-prime prime 1.20-release dev gnome-kit active 3.20-prime prime 3.26-prime prime kde-kit active 5.12-prime prime media-kit active 1.2-prime prime perl-kit active 5.24-prime prime python-modules-kit active master current python-kit active 3.6-prime prime php-kit active master current java-kit active 1.2-prime prime ruby-kit active 1.2-prime prime haskell-kit active 1.2-prime prime ml-lang-kit active 1.2-prime prime lisp-scheme-kit active 1.2-prime prime lang-kit active 1.2-prime prime llvm-kit active 1.2-prime prime master dev dev-kit active 1.2-prime prime xfce-kit active 4.12-prime prime desktop-kit active 1.2-prime prime editors-kit active master current net-kit active master current text-kit active master current science-kit active master current games-kit active master current nokit active master current NOTE: This information comes from /etc/ego.conf and meta-repo metadata. After making changes to ego.conf, be sure to run ego sync in so that the individual kit repositories on disk are synchronized with the kit branches shown above. -
-
open a bug report on bugs.funtoo.org
-
no problem, glad we sorted it out.
-
there is no stable anymore
try
./ego profile build current
and try to resume from there
-
1 hour ago, lego12239 said:
well actually he is using live master of ego
can you from cloned ego folder do "ego profile "
-
-
try to find a log file inside VM dir somewhere, without it it is reading from a crystal ball.
-
good plan. let us know what you find out.
-
running as what user? are you in the "virtualbox" group if not root?
-
lsmod | grep vbox -
it is not that much about software becoming incompatible with older release, it is more of any patches and fixes that didn't make it into 4.9-lts branch that you probably used, at the time of creation of the system, some BTRFS features that were in 4.14 branch and are not in 4.9.
so creating a loop device btrfs system with 4 disks and creating a raid10 with 4.14 and then turning on all the flags like compress and such on the fs and putting some dummy data on there, and afterwards downgrading the kernel and mounting the filesystem and comparing for example the checksums of the dummy data or performing a scrub could give you information about if this downgrade is safe for your server, but also don't take this for granted and have backups!!!
couple of ideas how to test without 4 harddrives can be found here: https://www.funtoo.org/BTRFS_Fun
-
all the setup commands are run as root. there is no "own profile" there is only "system profile". changing profile requires being root or using sudo.
-
https://btrfs.wiki.kernel.org/index.php/Changelog#By_feature
don't know how much debian backports btrfs fixes (or new features)
changelog here:
downgrade could be problematic if you use ZSTD as your compression for example, but not limited to this probably.
IMHO - test the downgrade on a separate pc or disk. (and never touch a running system)
at least for those running btrfs this kernel switch should be done with extreme caution.
-
so I don't know why you can update on one as normal user - but that should not be the normal behaviour. I think that setting profile is a admin's (root) job and should be limited to root or sudoers. there has to be a difference other then one being mac and the other amd, what stage did you use for both of them, how did you extract them. I am just guessing here as I don't know what could cause this behaviour, but what I am trying to say, try to go back in your setup procedure and give any differences between the two machines. Also I don't think that you should be allowed to change system's profile as a normal user. So actually I find the mac performance strange.
I have never encountered this as I always setup the core OS as root. How did you emerge packages, also as denis user?
-
paste /etc/sudoers from both
-
paste
"groups denis" from both pc
2nd Generation Funtoo Compute Infrastructure and Plan Upgrades
in Funtoo Hosting
Posted
@ennui sorry don't have access to funtoo infrastructure anymore. you'll have to wait for drobbins to answer this one.