Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary update' #='/var/db update' @='/var/db move'
s='/var/db SLOT move' %='binary move' S='binary SLOT move'
p='update /etc/portage/package.*'
/var/git/meta-repo/kits/core-kit/profiles/updates/3Q-2019..
>>> No matching atoms found in "world" favorites file...
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.
--- Couldn't find 'debian-sources' to unmerge.
>>> No packages selected for removal by unmerge
localhost ~ # eselect kernel list
Available kernel symlink targets:
[1] linux-5.2.99-zen0
[2] linux-debian-sources-lts-4.19.37_p6
[3] linux-debian-sources-lts-4.19.98_p1 *
Now I need to delete the installed kernel by hand to keep it out but I am assuming that on the next update that trojan is going to be back.
I plan on upgrading my kernel to a newer one, I do not want an old kernel. I am keeping my funtoo functional in the hope that someday I can make it again my main system.
I am too busy with my work to have time to switch back to gentoo that still has 32 bit support.
I have been using arch linux for a few months because of the lack of 32 bit support. The TI yocto cannot be used without 32 bit support.
I am likely going to be stuck with ubuntu or arch until TI stops requiring 32 bit support. When I complain I am told that ubuntu and centos are the only supported platform.
It worked correctly on funtoo until the removing of 32 bit support
I am hoping that their self extracting files are the problem. I probably could find a work around if that is the only thing that requires 32 bit support.
Basically it was a major goof from the funtoo team to remove 32 bit support.
Question
minou666
I did a world update and now got a very old debian kernel
localhost ~ # dir /boot/
total 35800
drwxr-xr-x 4 root root 4096 31 déc 1969 .
drwxr-xr-x 23 root root 4096 11 fév 18:32 ..
-rwxr-xr-x 1 root root 0 4 aoû 2019 .keep
drwxr-xr-x 4 root root 4096 3 nov 20:36 EFI
-rwxr-xr-x 1 root root 3671764 11 fév 19:11 System.map-debian-sources-lts-x86_64-4.19.98_p1
-rwxr-xr-x 1 root root 4487982 6 aoû 2019 System.map-genkernel-x86_64-5.2.4-zen-catu+
drwxr-xr-x 6 root root 4096 11 fév 19:23 grub
-rwxr-xr-x 1 root root 7689728 11 fév 19:22 initramfs-debian-sources-lts-x86_64-4.19.98_p1
-rwxr-xr-x 1 root root 6409668 6 aoû 2019 initramfs-genkernel-x86_64-5.2.4-zen-catu+
-rwxr-xr-x 1 root root 5609344 11 fév 19:11 kernel-debian-sources-lts-x86_64-4.19.98_p1
-rwxr-xr-x 1 root root 8763776 6 aoû 2019 kernel-genkernel-x86_64-5.2.4-zen-catu+
How do I keep it from getting merged . I removed it when I install my zen kernel but it came back today
Removing it is impossible
localhost ~ # emerge --deselect debian-sources && emerge -C debian-sources
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary update' #='/var/db update' @='/var/db move'
s='/var/db SLOT move' %='binary move' S='binary SLOT move'
p='update /etc/portage/package.*'
/var/git/meta-repo/kits/core-kit/profiles/updates/3Q-2019..
>>> No matching atoms found in "world" favorites file...
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.
--- Couldn't find 'debian-sources' to unmerge.
>>> No packages selected for removal by unmerge
localhost ~ # eselect kernel list
Available kernel symlink targets:
[1] linux-5.2.99-zen0
[2] linux-debian-sources-lts-4.19.37_p6
[3] linux-debian-sources-lts-4.19.98_p1 *
Now I need to delete the installed kernel by hand to keep it out but I am assuming that on the next update that trojan is going to be back.
I plan on upgrading my kernel to a newer one, I do not want an old kernel. I am keeping my funtoo functional in the hope that someday I can make it again my main system.
I am too busy with my work to have time to switch back to gentoo that still has 32 bit support.
I have been using arch linux for a few months because of the lack of 32 bit support. The TI yocto cannot be used without 32 bit support.
I am likely going to be stuck with ubuntu or arch until TI stops requiring 32 bit support. When I complain I am told that ubuntu and centos are the only supported platform.
It worked correctly on funtoo until the removing of 32 bit support
I am hoping that their self extracting files are the problem. I probably could find a work around if that is the only thing that requires 32 bit support.
Basically it was a major goof from the funtoo team to remove 32 bit support.
Michel
Link to comment
Share on other sites
5 answers to this question
Recommended Posts