Το νήμα του Gentoo, version 1.0

[NicM1]

Τυχαία διάβασα διάφορα στο ρεντιτ για το Gentoo x86-64-v3 αναφέροντας τα εξής

Running v3 optimized code on a v3 capable CPU is typically 10-15% more performant or power efficient than basic x86-64.

Έχετε αντιληφθεί διαφορές ;

[famous-walker]

Αν υποθεσουμε πως ενα μεσο pc περνα την συντριπτικη πλειοψηφια της ωρας που λειτουργει σε idle η λιγο παραπανω, τοτε το κερδος μαλλον θα ειναι ελαχιστο. Αν βαλεις μεσα και το compile, αναλογα το ποσο συχνα ανανεωνονται και ποσα ειναι τα πακετα, το πιο πιθανο ειναι να βγαινει χασουρα.

[tsigarid]

Λίγη προσοχή εδώ:

2024-03-12-debianutils-installkernel
Title installkernel is no longer implicitly installed
Author Andrew Ammerlaan <andrewammerlaan@gentoo.org>
Posted 2024-02-26
Revision 1

/sbin/installkernel is a script called by the kernel's "make install"
as well as by the distribution kernel's post-install phase. If you are
reading this then chances are you use and rely on installkernel[1] and
what follows is essential for you.

Previously sys-kernel/installkernel was implicitly installed on many
systems via a dependency in sys-apps/debianutils. This dependency was
toggled by the "installkernel" USE flag, and enabled by default.

Until recently, sys-apps/debianutils was in turn pulled in by
app-misc/ca-certificates, an essential package installed on many
systems. However, this dependency of app-misc/ca-certificates on
sys-apps/debianutils was removed[2]. As a result many users may find
that sys-apps/debianutils and therefore sys-kernel/installkernel are no
longer part of the dependency graph and will therefore be cleaned up by
"emerge --depclean".

Removing sys-kernel/installkernel from your system WILL change the way
kernels are installed by "make install"! Instead of the versioned
/boot/vmlinuz-x.y.z that you are used to, "make install" will simply
copy bzImage (or equivalent for your arch) into /boot. This image may
not be picked up by your bootloader or its configuration tools.

To avoid surprises from such implicit dependencies from happening again
in the future, the dependency on sys-kernel/installkernel in
sys-apps/debianutils is removed. And as such, sys-kernel/installkernel
is only installed on the system if it is either explicitly selected or
pulled in via the distribution kernels (e.g. gentoo-kernel(-bin)).


User Action Required (all users)
====================

Users who currently have sys-kernel/installkernel installed, must
ensure that it is explicitly selected by emerging it:

emerge --noreplace sys-kernel/installkernel

Users who find that sys-kernel/installkernel has already been cleaned
from their systems and are therefore affected by the change in kernel
installation described above should re-install sys-kernel/installkernel
and then re-install their kernel.

emerge sys-kernel/installkernel
cd /usr/src/linux # (or other location of the kernel sources)
make install

Note that this re-installation is not required for users of the
distribution kernels (e.g. gentoo-kernel(-bin)).


[1] https://wiki.gentoo.org/wiki/Installkernel
[2] https://gitweb.gentoo.org/repo/gento...5d72ddae0131e6

[GoofyX]

Χθες έκανα sync και σήμερα που μπήκα, βλέπω ότι δεν υπάρχει το keyboard language switcher στο KDE. Τελοσπάντων, αφού το βρήκα και το ξαναέβαλα, είδα ότι δεν υπάρχει πλέον το Greek extended variant:



Έχω χάσει κάτι;

Και επιπλέον:

2024-03-22-new-23-profiles
Title Profile upgrade to version 23.0 available
Author Andreas K. Huettel <dilfridge@gentoo.org>
Posted 2024-03-22
Revision 1

A profile upgrade to version 23.0 is available for your architecture.
The new 23.0 profiles enable some toolchain hardening features and
performance enhancements by default, and standardize settings.
You can find the list of changes on the wiki tracking page [1].

We strongly advise to precisely follow the upgrade instructions found
below. The 17.0, 17.1, 20.0, and 22.0 profiles will be marked deprecated
in 2 months and removed a year later. The exact dates may depend on the
architecture, see [2].

Upgrade instructions

Note 1: The use of binary packages is completely optional, and also not
as much tested as the source-based upgrade path yet. If you prefer to
only use the traditional source-based installation, omit the "--getbinpkg"
parameter in all emerge invocations.

Note 2: If you have manually changed your CHOST to a value different from
what the stages and profiles set, you may have to do that in the future too.
In that case you should know what you are doing, hopefully; please read the
instructions with a critical eye then.

1. Ensure your system backups are up to date. Please also update
your system fully and depclean before proceeding.
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.

2. If you are still using one of the long-deprecated amd64 17.0 profiles
(other than x32 or musl), then first complete the migration to the
corresponding 17.1 profile. Instructions can be found at [3].

3. If you are currently using systemd in a split-usr configuration, then first
complete the migration to the corresponding merged-usr profile of the
same profile version. Details on how to do this can be found in the news
item [4].
If you are currently using openrc, migrate to 23.0 first, keeping your disk
layout. If you want to move from split-usr to merged-usr, do that afterwards.

4. Run "emerge --info" and note down the value of the CHOST variable.

5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
remove it. Also delete all lines defining CHOST_... variables.

6. Select the 23.0 profile corresponding to your current profile, either using
"eselect profile" or by manually setting the profile symlink.
Note that old profiles are by default split-usr and the 23.0 profiles by
default merged-usr. Do NOT change directory scheme now, since this will
mess up your system!
Instead, make sure that the new profile has the same property: for example,
OLD default/linux/amd64/17.1
==> NEW default/linux/amd64/23.0/split-usr
(added "split-usr")
OLD default/linux/amd64/17.1/systemd/merged-usr
==> NEW default/linux/amd64/23.0/systemd
(removed "merged-usr")
A detailed table of the upgrade paths can be found at [5]. Please consult it.
In some cases (hppa, x86) the table will tell you to pick between two choices.
What you need should be obvious from your *old* CHOST value (from step 4).

7. Delete the contents of your binary package cache at ${PKGDIR}
rm -r /var/cache/binpkgs/*

8. In the file or directory /etc/portage/binrepos.conf (if existing), update
the URI in all configuration such that they point to 23.0 profile binhost
directories. The exact paths can be found in the table at [5], too.

9. Rebuild or reinstall from binary (if available) the following packages in
this order, with the same version as already active:
emerge --ask --oneshot --getbinpkg sys-devel/binutils
(you may have to run binutils-config and re-select your binutils now)
emerge --ask --oneshot --getbinpkg sys-devel/gcc
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
that; instead, abort and try again with --nodeps added to the command line.)
(you may have to run gcc-config and re-select your gcc now)
and the C library, i.e. for glibc-based systems
emerge --ask --oneshot --getbinpkg sys-libs/glibc
or for musl-based systems
emerge --ask --oneshot --getbinpkg sys-libs/musl

10. Re-run "emerge --info" and check if CHOST has changed compared to step 3.

If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,

11. Recheck with binutils-config and gcc-config that valid installed versions
of binutils and gcc are selected.

12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
refer to the *OLD* CHOST value, and remove them.
Examples how to do this can be found in the similar procedure at [6].

13. Run env-update && source /etc/profile

14. Re-emerge libtool:
emerge --ask --oneshot --getbinpkg libtool

15. Just for safety, delete the contents of your binary package cache at
${PKGDIR} again:
rm -r /var/cache/binpkgs/*

16. Rebuild world:
emerge --ask --emptytree --getbinpkg @world


[1] https://wiki.gentoo.org/wiki/Project...ile_transition
[2] https://wiki.gentoo.org/wiki/Project...ofile_timeline
[3] https://www.gentoo.org/support/news-...ow-stable.html
[4] https://www.gentoo.org/support/news-...-usrmerge.html
[5] https://wiki.gentoo.org/wiki/Project...0_update_table
[6] https://wiki.gentoo.org/wiki/Changin...ng_things_work

[imitheos]

Χθες έκανα sync και σήμερα που μπήκα, βλέπω ότι δεν υπάρχει το keyboard language switcher στο KDE. Τελοσπάντων, αφού το βρήκα και το ξαναέβαλα, είδα ότι δεν υπάρχει πλέον το Greek extended variant:

Έχω χάσει κάτι;

https://www.adslgr.com/forum/threads...27#post7537427
https://www.adslgr.com/forum/threads...56#post7537356

[GoofyX]

Πω...

[alfaeffe]

Εκανα τη μεταβαση στο profile 23.0 χωρις καποιο προβλημα στα 15 πρωτα βηματα και τωρα αφηνω το pc ανοικτο να ξαναχτισει τον κοσμο ολο....

 16. Rebuild world:
emerge --ask --emptytree --getbinpkg @world

[GoofyX]

Μας έσκισε. Τι το θέλουν το world rebuild, έλεος...

[NicM1]

Τι το θέλουν το world rebuild.

Να ζεσταθούν λίγο οι μηχανές

[pap]

Τελείωσα και εγώ με την μετάβαση στο νέο προφίλ χωρίς προβλήματα, νομίζω, μου έμεινε όμως η απορία του βήματος που έλεγε να σβήσουμε την μεταβλητή chost, εγώ την έκανα σχόλιο δεν την έσβησα και όλα πήγαν κατ'ευχην αλλά τώρα κάνω δεύτερες σκέψεις μήπως έκανα λάθος. Πάντως όλα παίζουν κανονικά.

[tsigarid]

Τελείωσα και εγώ με την μετάβαση στο νέο προφίλ χωρίς προβλήματα, νομίζω, μου έμεινε όμως η απορία του βήματος που έλεγε να σβήσουμε την μεταβλητή chost, εγώ την έκανα σχόλιο δεν την έσβησα και όλα πήγαν κατ'ευχην αλλά τώρα κάνω δεύτερες σκέψεις μήπως έκανα λάθος. Πάντως όλα παίζουν κανονικά.

Όταν την κάνεις σχόλιο είναι ακριβώς ισοδύναμο με το να τη σβήνεις.

[alfaeffe]

Ναι σαν σχολιο το αφησα και εγω το CHOST στο make.conf μου. Για να θυμαμαι τις παλιες μερες
Ολα καλα και εδω με το world rebuild μετα το new profile.
Το χειροτερο μου ηταν οτι οταν τελειωσε εκανα νεο sync και μου εβγαλε version bump στην qtwebengine οποτε αλλο ενα rebuild για αυτο το τερας μετα το βραδινο build του...

[GoofyX]

Ναι σαν σχολιο το αφησα και εγω το CHOST στο make.conf μου. Για να θυμαμαι τις παλιες μερες
Ολα καλα και εδω με το world rebuild μετα το new profile.
Το χειροτερο μου ηταν οτι οταν τελειωσε εκανα νεο sync και μου εβγαλε version bump στην qtwebengine οποτε αλλο ενα rebuild για αυτο το τερας μετα το βραδινο build του...

Το binary βάλε, μην χάνεις χρόνο με αυτό το πακέτο.

[Gentoo]

Μας έσκισε. Τι το θέλουν το world rebuild, έλεος...

Εγώ δεν το έκανα. Επίσης είχα θέμα με το installation μετά τα βήματα που περιγράφονται στα news (αυτό που περιγράφει ο OP σε αυτό https://forums.gentoo.org/viewtopic-t-1168016.html)

και ακολούθησα αυτό:

https://wiki.gentoo.org/wiki/Merge-usr

Όλα δουλεύουν κομπλέ τώρα.

Αντί για world rebuild έκανα μόνο emerge -uDN @world

και ξαναέχτισε όσα πακέτα είχαν split-usr USE flag.

Σε 2 συστήματα, κανένα θέμα.

Btw καλά που διάβασα το νήμα και ενημερώθηκα για το migration γιατί ξεχνάω να διαβάζω τα news του gentoo

[NicM1]

Και εγώ έκανα την ενημέρωση στο προφίλ με

emerge -uDN @world

36 πακέτα ενημέρωσε χωρίς πρόβλημα.