Re: [gentoo-user] emerge a binary package no longer in tree

[Johannes Rosenberger]

On 20.02.2017 07:50, Raffaele Belardi wrote:
> I'd like to try and update a package I masked long time ago due to
> performance problems. Upstream the problem does not seem completely
> addressed and solved so I'd like to be able to go back to the old
> version just in case. But the old version is no longer in the tree. If
> I quickpkg it will I be able to reinstall it anyway?
>
> thanks,
>
> raffaele
>
> # cat /etc/portage/package.mask
> # version 1.8.3 uses 20% CPU for no reason
> >net-misc/rdesktop-1.8.2
>
> # eix -I rdesktop
> [?] net-misc/rdesktop
>  Available versions:  1.8.3 (~)1.8.3-r1 (~)1.8.3-r2 {alsa ao debug
> ipv6 kerberos libressl libsamplerate oss pcsc-lite xrandr}
>
> # quickpkg net-misc/rdesktop
>  * Building package for net-misc/rdesktop-1.8.2 ...
>[ ok ]
>
>  * Packages now in '/usr/portage/packages':
>  * net-misc/rdesktop-1.8.2: 157

Yes, you will be.

Re: [gentoo-user] /etc/portage/profile vs. /etc/portage/make.profile

[Johannes Rosenberger]

On 20.02.2017 03:37, meino.cra...@gmx.de wrote:
> Hi,
>
> I am a little confused...
>
> In search for the reason my new root has no /etc/portage/profile
> but an /etc/portage/make.profile on this documemnt:
> https://dev.gentoo.org/~zmedico/portage/doc/man/portage.5.html
> I found this ywo lines
>
> /etc/portage/make.profile/ or /etc/make.profile/
> site-specific overrides go in /etc/portage/profile/
>
> (My profile is set correctly)
> Does this mean that make.profile is totally identical to
> make.profile, but if you want site-specific overrides you need
> to have profile instead of make.profile?
>
> Do I need to create /etc/portage/profile if it is not there?
>
> Nonetheless the listing below implies, that they are equivaltent.
> Or ?
>
> Cheers
> Meino
make.profile is a symlink to your profile, so you shouldn't edit
anything in there. It is managed by 'eselect profile' and i guess that
/etc/make.profile is the old location, like with make.conf which used to
be in /etc but is now in /etc/portage.
If you want to manually override anything in your profile that is not
covered by the other files in /etc/portage, e.g. unmask useflags, then
you use /etc/portage/profile. Everything there has higher precedence
than things in make.profile.

Re: [gentoo-user] How to keep my system from (nearly) freezing?

[Johannes Rosenberger]

On 19.02.2017 14:41, meino.cra...@gmx.de wrote:
> Helmut Jarausch  [17-02-19 14:04]:
>> Hi,
>>
>> sometime I have some memory hungry ebuilds in the background, when I 
>> start (e.g.) Chromium which needs very much memory if you have a lot of 
>> open tabs.
>>
>> In that case my system nearly freezes. I cannot even kill chrome.
>> What can I do in that case. (Remote login doesn't work either)
>>
>> Can I have any additional program (like Chromium) die if there is not 
>> enough memory.
>>
>> Many thanks for a hint,
>> Helmut
>>
> Hi Helmut,
>
> I know that situation very well...additionally I have Blender
> open...
>
> But I think that the "freeze" of the system is not due to the memory
> amount but due to the heavy I/O while swapping.

I think so, too.

> May be a tool like ionice could help you to keep the possibility
> of killing certain processes. Ionice the emerge itself and additinally
> nice it also.
> The emerge may take longer, but a frozen system is even slower...
> ;)
>
> HTH!
> Cheers
> Meino

You can also use a compressed swap partition in RAM via zram
(Instructions: https://wiki.gentoo.org/wiki/Zram).
Then your system is still responsive enough to kill chromium when you
realize that your memory fills up.

It should also be possible to somehow dynamically set memory quotas but
I've not tried it yet. It might work via cgroups (which portage can use
natively).

Re: [gentoo-user] package.provided syntax for overlay

[Johannes Rosenberger]

On 19.02.2017 11:20, Mick wrote:
> Hi All,
>
> Given sddm is not working for my setup, as per bug #608690, I thought of 
> trying entrance from the bar overlay.  It wants to pull in enlightenment, 
> which I have already installed from the main tree and would like to keep it 
> as 
> such:
>
> # emerge -uaDv entrance
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild U ~] x11-wm/enlightenment-:0.17/::bar 
> [0.20.6:0.17/0.20.6::gentoo] USE="eeze%* nls pam ukit -doc -egl% -pm-utils% -
> static-libs -systemd -wayland (-spell%*)" ENLIGHTENMENT_MODULES="appmenu 
> backlight battery bluez4 clock conf-applications conf-bindings conf-dialogs 
> conf-display conf-interaction conf-intl conf-menus conf-paths 
> conf-performance 
> conf-randr conf-shelves conf-theme conf-window-manipulation conf-window-
> remembers connman contact%* cpufreq everything fileman fileman-opinfo gadman 
> ibar ibox lokker mixer msgbus music-control notification pager pager16%* 
> quickaccess shot start syscon systray tasks teamwork temperature tiling 
> winlist wizard xkbswitch -access% -packagkit% -wl-desktop-shell* -wl-drm* -wl-
> fb% -wl-x11* (-conf%*) (-geolocation%*) (-packagekit%*) (-pager-plain%*) (-
> policy-mobile%*) (-wl-text-input%*) (-wl-weekeyboard%*) (-wl-wl%*) (-
> xwayland%*)" 0 KiB
> [ebuild  N*] x11-plugins/entrance-::bar  USE="consolekit pam -grub -
> systemd -vkbd" 0 KiB
>
>
> So I tried in /etc/portage/package.provided any combination of these:
>
> x11-wm/enlightenment-:0.17/::bar
>
> =x11-wm/enlightenment-:0.17
>
> x11-wm/enlightenment-
>
> None of which can stop portage dragging in 'x11-
> wm/enlightenment-:0.17/::bar'.  What is the correct syntax to block 
> this version of enlightenment from emerging?
>
According to the portage manpage 'x11-wm/enlightenment-' should be
the correct syntax.

But I think, package.provided is the wrong file at all. The correct way
to accomplish what you want to is masking
'x11-wm/enlightenment-:0.17/::bar'. The problem with this
package is that it is keyworded incorrectly as '~amd64 ~x86'  despite
being a live ebuild.
If you already have enlightenment:0.17 installed this should suffice,
since entrance only depends on this and not the live ebuild.

Re: [gentoo-user] Total recall

[Johannes Rosenberger]

On 18.02.2017 20:00, meino.cra...@gmx.de wrote:
> Hi,
>
> while building my new root I got this:
>
>
>
> 
> Total: 783 packages (770 new, 6 in new slots, 7 reinstalls, 1 uninstall), 
> Size of downloads: 1,710,373 KiB
> Conflict: 3 blocks (1 unsatisfied)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
> 
> >=dev-libs/openssl-1.0.1h-r2:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  (>=dev-libs/openssl-1.0.1h-r2:0[abi_x86_64(-)]) required by 
> (gnome-base/gnome-vfs-2.24.4-r5:2/2::gentoo, ebuild scheduled for merge)
> dev-libs/openssl:0/0=[abi_x86_64(-)] required by 
> (app-arch/libarchive-3.2.2-r1:0/13::gentoo, installed)
> dev-libs/openssl:0= required by (dev-lang/python-3.4.5:3.4/3.4m::gentoo, 
> installed)
> dev-libs/openssl:0 required by 
> (dev-perl/Crypt-OpenSSL-RSA-0.280.0-r3:0/0::gentoo, ebuild scheduled for 
> merge)
> dev-libs/openssl:0= required by (dev-lang/python-2.7.12:2.7/2.7::gentoo, 
> ebuild scheduled for merge)
> 
> >=dev-libs/openssl-1.0.1h-r2:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  (>=dev-libs/openssl-1.0.1h-r2:0[abi_x86_64(-)]) required by 
> (dev-libs/libevent-2.1.8:0/2.1-6::gentoo, installed)
> dev-libs/openssl:0/0= required by 
> (kde-frameworks/kdelibs-4.14.29:4/4.14::gentoo, installed)
> dev-libs/openssl:0 required by 
> (dev-perl/Crypt-OpenSSL-DSA-0.190.0:0/0::gentoo, ebuild scheduled for merge)
> dev-libs/openssl:0/0= required by 
> (dev-python/cryptography-1.7.2:0/0::gentoo, installed)
> dev-libs/openssl:0[bindist=] (dev-libs/openssl:0[bindist]) required by 
> (dev-qt/qtnetwork-5.7.1:5/5.7::gentoo, installed)
> >=dev-libs/openssl-1.0.1:0/0= required by 
> (app-crypt/qca-2.1.3:2/2::gentoo, installed)
> dev-libs/openssl:0= required by 
> (app-emulation/virtualbox-5.1.14:0/0::gentoo, installed)
> dev-libs/openssl:0= required by (dev-lang/ruby-2.1.10:2.1/2.1::gentoo, 
> ebuild scheduled for merge)
> 
> >=dev-libs/openssl-1.0.1h-r2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  (>=dev-libs/openssl-1.0.1h-r2[abi_x86_64(-)]) required by 
> (media-video/rtmpdump-2.4_p20161210:0/0::gentoo, ebuild scheduled for merge)
> dev-libs/openssl:0/0= required by (dev-vcs/git-2.11.1:0/0::gentoo, 
> installed)
> dev-libs/openssl:0/0= required by (net-misc/wget-1.19.1:0/0::gentoo, 
> installed)
> dev-libs/openssl:0 required by 
> (dev-perl/Crypt-OpenSSL-Random-0.110.0:0/0::gentoo, ebuild scheduled for 
> merge)
> 
> dev-libs/openssl:0=[static-libs?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  (dev-libs/openssl:0=[abi_x86_64(-)]) required by 
> (net-misc/curl-7.52.1-r1:0/0::gentoo, installed)
> 
> >=dev-libs/openssl-1.0.1h-r2:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>  (>=dev-libs/openssl-1.0.1h-r2:0[abi_x86_64(-)]) required by 
> (dev-qt/qtcore-4.8.7-r2:4/4::gentoo, installed)
> dev-libs/openssl:0[static-libs?] (dev-libs/openssl:0) required by 
> (app-text/mupdf-1.10a-r1:0/1.10a::gentoo, installed)
> dev-libs/openssl:0 required by (www-client/dillo-3.0.5-r1:0/0::gentoo, 
> ebuild scheduled for merge)
> dev-libs/openssl:0= required by (mail-mta/msmtp-1.6.6:0/0::gentoo, ebuild 
> scheduled for merge)
> dev-libs/openssl:0= required by (media-video/gpac-0.6.1-r2:0/0::gentoo, 
> ebuild scheduled for merge)
> >=dev-libs/openssl-1:0= required by 
> (media-libs/liblrdf-0.5.0-r1:0/0::gentoo, ebuild scheduled for merge)
> >=dev-libs/openssl-0.9.6 required by 
> (net-mail/fetchmail-6.3.26-r3:0/0::gentoo, ebuild scheduled for merge)
> dev-libs/openssl:0= required by (net-misc/ntp-4.2.8_p9:0/0::gentoo, 
> ebuild scheduled for merge)
> >=dev-libs/openssl-0.9.8f:0[bindist=] 
> (>=dev-libs/openssl-0.9.8f:0[bindist]) required by 
> (net-misc/openssh-7.4_p1:0/0::gentoo, installed)
> dev-libs/openssl:0 required by (dev-lang/php-7.1.1:7.1/7.1::gentoo, 
> ebuild scheduled for merge)
> dev-libs/openssl:0 required by (net-misc/openssh-7.4_p1:0/0::gentoo, 
> installed)
> dev-libs/openssl:0= required by 
> (net-wireless/aircrack-ng-1.2_rc4-r1:0/0::gentoo, ebuild scheduled for merge)
> dev-libs/openssl:0= required by (net-misc/rdesktop-1.8.3-r2:0/0::gentoo, 
> ebuild scheduled for merge)
> dev-libs/openssl:0/0= required by 
> (dev-perl/Net-SSLeay-1.800.0:0/0::gentoo, 

Re: [gentoo-user] ffmpeg and libav: a slot conflict

[Johannes Rosenberger]

On 18.02.2017 12:21, gevisz wrote:
> Yet, a week ago, I updated my system without any problem but just now,
> trying to update my system,
>  I have got the following error message:
>
> # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask
> world --verbose-conflicts --exclude chromium
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N ] dev-libs/tinyxml-2.6.2-r2  USE="stl -debug -doc -static-libs"
> [ebuild U  ] app-shells/push-2.0 [1.6]
> [ebuild  N ] app-shells/quoter-3.0_p2
> [ebuild U  ] app-dicts/myspell-en-20170101 [20160901]
> [ebuild U  ] dev-libs/libxslt-1.1.29-r1 [1.1.29]
> [ebuild U  ] app-text/iso-codes-3.74 [3.70]
> [ebuild U ~] net-misc/youtube-dl-2017.02.17 [2017.02.07] USE="offensive*"
> [ebuild U  ] dev-python/ssl-fetch-0.4 [0.3]
> [ebuild U ~] app-shells/zsh-completions-0.23.0 [0.22.0]
> [ebuild U  ] net-dns/bind-tools-9.11.0_p3 [9.11.0_p2]
> [ebuild U  ] app-portage/eix-0.32.4 [0.31.7-r1]
> [ebuild U  ] gnome-base/gnome-common-3.18.0-r1 [3.18.0]
> [ebuild U  ] media-libs/gstreamer-1.10.3 [1.8.3] USE="(-unwind)"
> [ebuild U  ] dev-libs/libgee-0.18.1 [0.18.0]
> [ebuild U  ] gnome-base/libgtop-2.34.2 [2.34.1]
> [ebuild  N ] x11-themes/gnome-themes-standard-3.20.2-r1
> [ebuild U  ] media-libs/libmediaart-1.9.0-r1 [1.9.0]
> [ebuild U  ] app-text/rarian-0.8.1-r3 [0.8.1-r2]
> [ebuild U  ] app-arch/libarchive-3.2.2-r1 [3.2.2]
> [ebuild U  ] app-doc/gnucash-docs-2.6.15 [2.6.13]
> [ebuild U  ] net-libs/libproxy-0.4.13-r2 [0.4.13-r1]
> [ebuild   R] sys-apps/portage-2.3.3  USE="native-extensions*"
> PYTHON_TARGETS="(-python3_6)"
> [ebuild U  ] media-libs/gst-plugins-base-1.10.3 [1.8.3-r1]
> [ebuild U  ] gnome-base/dconf-0.26.0-r1 [0.26.0]
> [ebuild U  ] media-libs/gst-plugins-good-1.10.3 [1.8.3]
> [ebuild U  ] media-libs/gst-plugins-ugly-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-cdparanoia-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-mad-1.10.3 [1.8.3]
> [ebuild  N ] virtual/imagemagick-tools-0  USE="jpeg png svg tiff -perl"
> [ebuild U  ] media-plugins/gst-plugins-flac-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-dvdread-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-x264-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-a52dec-1.10.3 [1.8.3]
> [ebuild U  ] gnome-extra/libgsf-1.14.41-r1 [1.14.41]
> [ebuild U  ] x11-libs/gtk+-2.24.31-r1 [2.24.31]
> [ebuild  N ] x11-themes/gtk-engines-adwaita-3.20.2  ABI_X86="32 (64) 
> (-x32)"
> [ebuild U  ] x11-libs/vte-0.28.2-r208 [0.28.2-r207]
> [ebuild U  ] dev-util/gtk-builder-convert-2.24.31-r1 [2.24.31]
> [ebuild U  ] app-text/ghostscript-gpl-9.20-r1 [9.15-r1]
> [ebuild U  ] media-libs/gst-plugins-bad-1.10.3 [1.8.3-r1]
> [ebuild U  ] dev-libs/gjs-1.46.0 [1.45.4]
> [ebuild U  ] dev-libs/appstream-glib-0.6.7 [0.6.3]
> [ebuild U  ] media-plugins/gst-plugins-resindvd-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-dts-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-faad-1.10.3 [1.8.3]
> [ebuild U  ] net-libs/webkit-gtk-2.14.5 [2.12.5]
> [ebuild U  ] media-libs/clutter-gst-3.0.22 [3.0.20]
> [ebuild U  ] app-portage/layman-2.4.2 [2.0.0-r3] USE="(-g-sorcery)
> -gpg% -sqlite% -squashfs% -sync-plugin-portage%"
> PYTHON_TARGETS="python3_4%* (-python3_5)"
> [ebuild U  ] media-sound/pulseaudio-10.0 [9.0]
> [ebuild U  ] media-plugins/gst-plugins-pulse-1.10.3 [1.8.3]
> [ebuild  N ] media-libs/libsdl2-2.0.4  USE="X alsa dbus joystick
> opengl pulseaudio sound threads udev video (-altivec) (-custom-cflags)
> (-fusionsound) -gles -haptic -nas -oss -static-libs -tslib -wayland
> -xinerama -xscreensaver" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="3dnow
> mmx sse sse2"
> [ebuild U  ] media-video/ffmpeg-3.2.4 [2.8.10] USE="-chromaprint%
> -ebur128% -gcrypt% -gmp% -kvazaar% -libilbc% (-mmal) -nvenc%
> -openh264% -rubberband% -zimg%" CPU_FLAGS_X86="-aes%"
> [ebuild U  ] media-plugins/gst-plugins-libav-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-mpeg2dec-1.10.3 [1.8.3]
> [ebuild U  ] media-plugins/gst-plugins-meta-1.10.3 [1.8.3]
> [ebuild   R] www-client/firefox-45.7.0  USE="(-gstreamer-0%)"
> [ebuild U  ] media-plugins/gst-plugins-meta-0.10-r11 [0.10-r10]
> [ebuild U  ] x11-misc/colord-1.3.4 [1.3.3]
> [ebuild U  ] sys-block/gparted-0.27.0 [0.26.1]
> [ebuild U  ] app-office/gnucash-2.6.15 [2.6.13]
> [ebuild U  ] app-misc/tracker-1.8.3-r1 [1.8.0] USE="seccomp%*"
> [ebuild U  ] gnome-extra/nautilus-tracker-tags-1.8.3 [1.8.0]
> [ebuild U  ] media-gfx/gthumb-3.4.4.1 [3.4.3]
> [ebuild U  ] gnome-base/nautilus-3.20.4 [3.20.3]
>
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> 

Re: [gentoo-user] To emerge openbox or gparted...that is the question...(William Tuxpeare)

[Johannes Rosenberger]

On 18.02.2017 12:14, meino.cra...@gmx.de wrote:

> Hi,
>
> I am confused...
>
> For my new gentoo root I want openbox AND gparted.
> But emerge says this:
>
> # required by x11-libs/pango-1.40.3::gentoo
> # required by x11-wm/openbox-3.6.1::gentoo
> # required by openbox (argument)
>> =x11-libs/cairo-1.14.8 X
> and
>
> # required by dev-cpp/cairomm-1.12.0-r1::gentoo
> # required by dev-cpp/pangomm-2.40.1::gentoo
> # required by dev-cpp/gtkmm-2.24.5::gentoo
> # required by sys-block/gparted-0.27.0::gentoo
> # required by sys-block/gparted (argument)
>> =x11-libs/cairo-1.14.8 -X
>
> Do I really need a virtualbox image just to play around with
> gparted separeted from openbox? ;)
>
> Can't be...or?
>
> Any way around this?
>
> Cheers
> Meino
>
>
>
>

A look at the ebuild shows that dev-cpp/cairomm-1.12.0-r1::gentoo
depends on ' >=x11-libs/cairo-1.12.10[aqua=,svg=,X=,${MULTILIB_USEDEP}]'
x11-libs/pango-1.40.3::gentoo depends on
'>=x11-libs/cairo-1.12.14-r4:=[X?,${MULTILIB_USEDEP}]'.

>From the manpage of ebuild(5), section "Atom USE", subsection
"Conditional USE Dependencies":

Compact Form   Equivalent Expanded Form
─
foo[bar?]  bar? ( foo[bar] ) !bar? ( foo )
foo[!bar?] bar? ( foo ) !bar? ( foo[-bar] )
foo[bar=]  bar? ( foo[bar] ) !bar? ( foo[-bar] )
foo[!bar=] bar? ( foo[-bar] ) !bar? ( foo[bar] )

So you must have the X use flag enabled for pango but disabled for
cairomm. Try enabling it for cairomm and all should be fine.

Regards
Johannes

Re: [gentoo-user] kernel config setting for console scroll back

[Johannes Rosenberger]

On 17.02.2017 04:11, Harry Putnam wrote:
> In make menuconfig, under:
>  Device Drivers → Graphics support → Console display driver support
> (700)   Scrollback Buffer Size (in KB)
>
> I think the default was 64 but I like a big scrollback buffer.
>
> As you see I set 700 but really didn't have much of an idea what that
> would be in lines.
>
> Can any one offer a close guestimate what 700 kb would be in lines.
>
> That is pretty close to 1 mb isn't it?... but still what is that in
> lines?  I'm guessing 1 MB might be around 10,000 lines.  Is that even
> roughly close... if so I probably should have went higher.
>
>

Your estimate is probably pretty good: I think 'the norm line' used to
be 80 chars. Now, that's not really the case anymore but you won't
probably get an average line length over 80-100 chars (except if you
only compile/emerge on the terminal). There's also a variable '$COLUMNS'
which tells you how many columns your terminal has.
1 char usually needs 1 Byte (ascii/utf8), so you can store about
1M/100=10k lines in 1MB. Colors add some Bytes (about 4-8 Bytes per
color change), but I guess, the average should not exceed 100 chars/line.

But why don't you use tmux or the like? There you also have a scrollback
buffer, but you can also search and copy there, you have a terminal
window manager (multiplexed) with different possible layouts and
detached sessions, means that e.g. when you log in remotely and lose the
connection, you just relogin and type 'tmux attach' and you're back.

Re: [gentoo-user] How to force a rebuild?

[Johannes Rosenberger]

On 15.02.2017 19:10, Bertram Scharpf wrote:
> Hi,
>
> I did not find this by Google. Maybe I asked the wrong
> terms.
>
> The package "virtualbox-modules" contains some kernel
> modules. When I built the package they landed in the
> directory
>
>   # equery f app-emulation/virtualbox-modules 
>   
>   ...
>   /lib/modules/4.4.39-gentoo/misc/vboxdrv.ko
>   /lib/modules/4.4.39-gentoo/misc/vboxnetadp.ko
>   ...
>
> After a kernel update the VirtualBox won't find them any
> more and do not expect that at all.
>
> I could delete the package and build-install it again, but
> then the old kernels modules would disappear. I just want
> to install the new ones.
>
> I could do a sequence of "ebuild" commands. Is there a
> front end "emerge" command, too? Something like the -U flag? 
>
> Thanks in advance.
>
> Bertram
>
>

emerge @module-rebuild

(find out via 'emerge --list-sets')

Re: [gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files

[Johannes Rosenberger]

On 15.02.2017 18:48, Mike Gilbert wrote:
> On Tue, Feb 14, 2017 at 6:08 PM, Johannes Rosenberger <gen...@jorsn.eu> wrote:
>> On 15.02.2017 00:00, scootergrisen wrote:
>>> When i download Gentoo Linux the file name might be called something
>>> like:
>>> livedvd-amd64-multilib-20160704.iso
>>>
>>> This might be fine if you just want that file and want to use it
>>> straight away.
>>>
>>> But lets say like i just did downloaded multiple linux distributions
>>> because i want to test them out so i have like 10-20 iso files or what
>>> ever.
>>>
>>> Then later one when i see the file name
>>> livedvd-amd64-multilib-20160704.iso i have no idea what distribution
>>> that was.
>>>
>>> The other distributions i have downloaded all seem to start with the
>>> name of the distribution in the file name. I Think Gentoo Linux is the
>>> only one yet that does not.
>>>
>> So you can identify it uniquely. ;-)
>>> So would it not be better to use a file name like this?:
>>> gentoo-livedvd-amd64-multilib-20160704.iso
>>>
>> Could be nice. But not important.
>> You can always run 'wget -O  '.
>>
>> You could write a GLEP? But then, you could just file a bug/ask somebody
>> responsible for the naming.
> A GLEP seems like overkill for something like this. I would suggest
> filing a bug for the release engineering team.
>
That's the broad hint my rethoric should give.
But maybe I ought to be somewhat more clear in what I mean, on mailing
lists.

Re: [gentoo-user] Perhaps add "gentoo-" in beginning of file name for iso files

[Johannes Rosenberger]

On 15.02.2017 00:00, scootergrisen wrote:
> When i download Gentoo Linux the file name might be called something
> like:
> livedvd-amd64-multilib-20160704.iso
>
> This might be fine if you just want that file and want to use it
> straight away.
>
> But lets say like i just did downloaded multiple linux distributions
> because i want to test them out so i have like 10-20 iso files or what
> ever.
>
> Then later one when i see the file name
> livedvd-amd64-multilib-20160704.iso i have no idea what distribution
> that was.
>
> The other distributions i have downloaded all seem to start with the
> name of the distribution in the file name. I Think Gentoo Linux is the
> only one yet that does not.
>
So you can identify it uniquely. ;-)
> So would it not be better to use a file name like this?:
> gentoo-livedvd-amd64-multilib-20160704.iso
>
Could be nice. But not important.
You can always run 'wget -O  '.

You could write a GLEP? But then, you could just file a bug/ask somebody
responsible for the naming.

Re: [gentoo-user] Re: package.provided?

[Johannes Rosenberger]

On 14.02.2017 21:22, Harry Putnam wrote:
> Johannes Rosenberger <gen...@jorsn.eu> writes:
>
>>> Can anyone offer suggestions about this... is it even the right way to
>>> proceed?
>>>
>>>
>> Hello!
>>
>> I have portage-2.3.3 installed and in my portage manpage it is mentioned:
>>
>> The file shall reside in etc/(make.profile|portage/(make.)?profile) and
>> the syntax is
>> /- without the '=' in the front.
> Thanks for that.  I'm not at all sure what that line means.
>
> something like /etc/  (then either make a directory named `profile' or
> one named `portage' if necessary) / (then make `profile' if
> necessary.)

That line is a regular expression (like in grep, sed, awk, vim,…):
Parentheses always group something into an atom and pipes mark an
alternative. '?' means that the preceding atom occurs zero or one time.
So the expression means 'etc/' (I missed out the preceding slash),
followed by alternatively 'make.profile' or 'portage/(make.)?profile'.
The latter means 'portage/profile' with an optional 'make.' in between.

As you (hopefully) see, the expression resolves to the three 
alternatives mentioned in the man page.

>
> So, /etc/portage/profile/package.provided
>
> I followed a newish dictum of using the package part as a directory
> name. So /etc/portage/profle/package.provided/FnameAndContentHere
> It worked... thanks again.


I find  the package.*-dirs very nice, too. Unfortunately, the tools like
emerge, flaggie etc. seem to not always use the same file to write to,
so the files get messed up over time.


>
> It worked.. still not getting everything installed but that
> part worked...

Well, that's not too astonishing… ;-)
Especially if you do anything uncommon: I'm trying to build a
musl-clang-4.0.0_rc1 system at the time, currently. And it took me some
days to hack out how to let clang compile itself with incompatible
symbols produced by gcc and clang…

> Something else about this entry in `man portage':
>
> [...]
> SYNOPSIS
>/etc/portage/make.profile/ or /etc/make.profile/
>   site-specific overrides go in /etc/portage/profile/
>   deprecated
>   [...]
>
> So is the plan to do away with package.provided or just relocate it?

No. "deprecated" is one of the files that reside in the profile, just
like "make.profile". It marks a profile as deprecated and contains the
successing profile and optionally upgrading instructions.

Re: [gentoo-user] package.provided?

[Johannes Rosenberger]

On 14.02.2017 16:09, Harry Putnam wrote:
> Setup:
>
>Installing X on Vbox vm runnning gentoo (amd64 not strict).  Host
>is win10 (64bit)
>
> Installing the xorg-server is calling for the installation of
> app-emulation/virtualbox-guest-additions-5.0.32
>
> However, my version of vbox is for a windows host (5.1.14).  And
> actually has the guest additions for that version already installed.
>
> Also before I noticed what was getting installed emerge had tried and
> failed to install the cited above package.
>
> I noticed the version that matches my vbox version (5.1.14) is
> available but masked unless setting ~amd64.  I'm trying for a stable
> setup so, put this in /etc/portage/package.accept_keywords:
>
>   =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64
>
> I tried to emerge it directly with:
>emerge app-emulation/virtualbox-guest-additions
>
> And sure enough emerge selected the right version but again the
> install failed.  I did not understand the failure from the build log.
>
> But since I have the proper version and am able to install it with the
> regular method vbox expects (mount the additions and install with
>
>  sh VBoxLinuxAdditions.run
>
> And since that method uses the currently installed kernel for its
> installation. Seems I can just reinstall the addtions using that
> method and tell gentoo about it with package.provided.
>
> Ok, `man portage' does not appear to mention where that file should
> reside.  Googling about it I find /etc/portage/profile is mentioned.
> Is that still correct?
>
> I ask because I put /etc/portage/profile/package.provided:
>
>  =app-emulation/virtualbox-guest-additions-5.0.32
>
> (removed the prior /etc/portage/package.accept_keywords/
>  virtualbox-guest-additions:
> =app-emulation/virtualbox-guest-additions-5.1.14 ~amd64)
>
> in place, but emerge still tries to install it so, either the syntax
> if faulty or the location is, I guess.
>
> I moved package.provided to /etc/portage/package.provided but still
> emerge trys to install the guest-additions.
>
> Can anyone offer suggestions about this... is it even the right way to
> proceed?
>
>

Hello!

I have portage-2.3.3 installed and in my portage manpage it is mentioned:

The file shall reside in etc/(make.profile|portage/(make.)?profile) and
the syntax is
/- without the '=' in the front.

Greetz

Johannes

Re: [gentoo-user] Building a new root for my Gentoo: Permission denied?

[Johannes Rosenberger]

On 14.02.2017 03:12, meino.cra...@gmx.de wrote:
> Johannes Rosenberger <gen...@jorsn.eu> [17-02-14 02:43]:
>> On 13.02.2017 19:20, meino.cra...@gmx.de wrote:
>>> Johannes Rosenberger <gen...@jorsn.eu> [17-02-13 19:04]:
>>>> On 13.02.2017 17:57, meino.cra...@gmx.de wrote:
>>>>
>>>>> Hogren <hog...@iiiha.com> [17-02-13 17:06]:
>>>>>> On 13/02/2017 04:42, meino.cra...@gmx.de wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> got a mysterious error message this morning (still building a new 
>>>>>>> root...)
>>>>>>>
>>>>>>> One of the updates was gnutls:
>>>>>>> It ends with:
>>>>>>> ...
>>>>>>> checking for i686-pc-linux-gnu-pkg-config... 
>>>>>>> /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>>> checking pkg-config is at least version 0.9.0... 
>>>>>>> /var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9/configure: 
>>>>>>> line 5020: /usr/bin/i686-pc-linux-gnu-pkg-config: Permission denied
>>>>>>> no
>>>>>>> checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
>>>>>>> checking whether the C compiler works... yes
>>>>>>> checking for C compiler default output file name... a.out
>>>>>>> checking for suffix of executables... 
>>>>>>> checking whether we are cross compiling... configure: error: in 
>>>>>>> `/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9-abi_x86_32.x86':
>>>>>>> configure: error: cannot run C compiled programs.
>>>>>>> If you meant to cross compile, use `--host'.
>>>>>>> See `config.log' for more details
>>>>>>> ...
>>>>>>>
>>>>>>> I tried:
>>>>>>> computer# ldd /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>>> not a dynamic executable
>>>>>>> computer# /usr/bin/i686-pc-linux-gnu-pkg-config 
>>>>>>> zsh: permission denied: /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>>>
>>>>>>> computer# file /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>>> /usr/bin/i686-pc-linux-gnu-pkg-config: ELF 32-bit LSB executable, Intel 
>>>>>>> 80386, version 1 (SYSV), dynamically linked, interpreter 
>>>>>>> /lib/ld-linux.so.2, for GNU/Linux 2.6.32, stripped, with debug_info
>>>>>>>
>>>>>>> I choosed multilib right from the beginning of this adventure ...
>>>>>>>
>>>>>>> How can I check, whether the problem is caysed by gnutls or by the 
>>>>>>> system setup (regarding 32bit)?
>>>>>>>
>>>>>>> Cheers
>>>>>>> Meino
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Can you give us more details of what do you want to do, what do you
>>>>>> already do, etc.
>>>>>>
>>>>>> Does /usr/bin/i686-pc-linux-gnu-pkg-config have the x (executable) 
>>>>>> permission ? (ls -l /usr/bin/i686-pc-linux-gnu-pkg-config)
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hogren
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> More mysterious hickups:
>>>>>
>>>>>>>> Regenerating /etc/ld.so.cache...
>>>>> /sbin/ldconfig: File /lib64/ld-linux.so.2 is empty, not checked.
>>>>>
>>>>> Did it screwed up my new root?
>>>>>
>>>>> Cheers
>>>>> Meino
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Maybe. But maybe it is fixable. /lib64/ld-linux.so.2 is a symlink to
>>>> glibc. But glibc cannot be wholly broken because if it were, then
>>>> nothing would work at all.
>>>>
>>>> I'd first investigate if only the symlink needs to be fixed (should
>>>> point to /lib/ld-.so).
>>>>
>>>> Have you updated glibc recently?Or any other important package/package
>>>> from @system?
>>>> Have you tried if 'revdep-rebuild' finds any 

Re: [gentoo-user] Building a new root for my Gentoo: Permission denied?

[Johannes Rosenberger]

On 13.02.2017 19:20, meino.cra...@gmx.de wrote:
> Johannes Rosenberger <gen...@jorsn.eu> [17-02-13 19:04]:
>> On 13.02.2017 17:57, meino.cra...@gmx.de wrote:
>>
>>> Hogren <hog...@iiiha.com> [17-02-13 17:06]:
>>>> On 13/02/2017 04:42, meino.cra...@gmx.de wrote:
>>>>> Hi,
>>>>>
>>>>> got a mysterious error message this morning (still building a new 
>>>>> root...)
>>>>>
>>>>> One of the updates was gnutls:
>>>>> It ends with:
>>>>> ...
>>>>> checking for i686-pc-linux-gnu-pkg-config... 
>>>>> /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>> checking pkg-config is at least version 0.9.0... 
>>>>> /var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9/configure: line 
>>>>> 5020: /usr/bin/i686-pc-linux-gnu-pkg-config: Permission denied
>>>>> no
>>>>> checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
>>>>> checking whether the C compiler works... yes
>>>>> checking for C compiler default output file name... a.out
>>>>> checking for suffix of executables... 
>>>>> checking whether we are cross compiling... configure: error: in 
>>>>> `/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9-abi_x86_32.x86':
>>>>> configure: error: cannot run C compiled programs.
>>>>> If you meant to cross compile, use `--host'.
>>>>> See `config.log' for more details
>>>>> ...
>>>>>
>>>>> I tried:
>>>>> computer# ldd /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>   not a dynamic executable
>>>>> computer# /usr/bin/i686-pc-linux-gnu-pkg-config 
>>>>> zsh: permission denied: /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>>
>>>>> computer# file /usr/bin/i686-pc-linux-gnu-pkg-config
>>>>> /usr/bin/i686-pc-linux-gnu-pkg-config: ELF 32-bit LSB executable, Intel 
>>>>> 80386, version 1 (SYSV), dynamically linked, interpreter 
>>>>> /lib/ld-linux.so.2, for GNU/Linux 2.6.32, stripped, with debug_info
>>>>>
>>>>> I choosed multilib right from the beginning of this adventure ...
>>>>>
>>>>> How can I check, whether the problem is caysed by gnutls or by the 
>>>>> system setup (regarding 32bit)?
>>>>>
>>>>> Cheers
>>>>> Meino
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Hello,
>>>>
>>>> Can you give us more details of what do you want to do, what do you
>>>> already do, etc.
>>>>
>>>> Does /usr/bin/i686-pc-linux-gnu-pkg-config have the x (executable) 
>>>> permission ? (ls -l /usr/bin/i686-pc-linux-gnu-pkg-config)
>>>>
>>>>
>>>>
>>>> Hogren
>>>>
>>>>
>>>>
>>>>
>>> More mysterious hickups:
>>>
>>>>>> Regenerating /etc/ld.so.cache...
>>> /sbin/ldconfig: File /lib64/ld-linux.so.2 is empty, not checked.
>>>
>>> Did it screwed up my new root?
>>>
>>> Cheers
>>> Meino
>>>
>>>
>>>
>>>
>> Maybe. But maybe it is fixable. /lib64/ld-linux.so.2 is a symlink to
>> glibc. But glibc cannot be wholly broken because if it were, then
>> nothing would work at all.
>>
>> I'd first investigate if only the symlink needs to be fixed (should
>> point to /lib/ld-.so).
>>
>> Have you updated glibc recently?Or any other important package/package
>> from @system?
>> Have you tried if 'revdep-rebuild' finds any broken libraries?
>>
>> If glibc is really broken you can
>>
>> 1. chroot into a stage3
>> 2. build a binpkg (type 'quickpkg glibc')
>> 3. copy the binpkg from
>> '/usr/portage/packages/sys-libs/glibc-*.tbz2' in the stage3 to
>>the same directory in your new root
>> 4. install the binary glibc ('emerge ')
>>
>> Then you should have a clean glibc install.
>>
>> If you suspect an update of breaking anything you can always build
>> binary packages ahead. They are built from the installed package, so you
>> don't have any additional compiling. Then you can roll back quickly if
>> anything is damaged.
>>
>> If you have a working glibc then you could also try re-emerging pkg-config.
>>
>> Regards
>> Johannes
>>
>>
> Hi Johannes,
>
> thanks for your offered help! :)
>
> I fixed that symlink but I ran into more weird problems... :(
> Normally I alway run a revdep-rebuild cycle after each 
> update...
>
> How did you set ABI_X86 in make.conf?
> Do you use multilib or a pure 64bit setup?
>
> Cheers
> Meino
>

Hi Meino,

you are welcome!

With the portage FEATURE 'preserve-libs' (active by default) you don't
need to revep-rebuild, normally. Just emerge @preserved-rebuild after
every update.

Does pkg-config work, now? Can you describe your "weird problems"? Have
you emerged any potentially broken and important (e.g. from @system)
packages recently?

Since I use a pure 64bit setup with abi_x86_32 activated selectively for
399 packages (mostly graphics related, because i still have flash
installed), i have no ABI_X86 var in my make.conf but use a pure amd64
profile (where this var is set).
What do you need 32bit for? 3rd-party binaries?

Regards
Johannes

Re: [gentoo-user] Building a new root for my Gentoo: Permission denied?

[Johannes Rosenberger]

On 13.02.2017 17:57, meino.cra...@gmx.de wrote:

> Hogren  [17-02-13 17:06]:
>> On 13/02/2017 04:42, meino.cra...@gmx.de wrote:
>>> Hi,
>>>
>>> got a mysterious error message this morning (still building a new 
>>> root...)
>>>
>>> One of the updates was gnutls:
>>> It ends with:
>>> ...
>>> checking for i686-pc-linux-gnu-pkg-config... 
>>> /usr/bin/i686-pc-linux-gnu-pkg-config
>>> checking pkg-config is at least version 0.9.0... 
>>> /var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9/configure: line 
>>> 5020: /usr/bin/i686-pc-linux-gnu-pkg-config: Permission denied
>>> no
>>> checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables... 
>>> checking whether we are cross compiling... configure: error: in 
>>> `/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9-abi_x86_32.x86':
>>> configure: error: cannot run C compiled programs.
>>> If you meant to cross compile, use `--host'.
>>> See `config.log' for more details
>>> ...
>>>
>>> I tried:
>>> computer# ldd /usr/bin/i686-pc-linux-gnu-pkg-config
>>> not a dynamic executable
>>> computer# /usr/bin/i686-pc-linux-gnu-pkg-config 
>>> zsh: permission denied: /usr/bin/i686-pc-linux-gnu-pkg-config
>>>
>>> computer# file /usr/bin/i686-pc-linux-gnu-pkg-config
>>> /usr/bin/i686-pc-linux-gnu-pkg-config: ELF 32-bit LSB executable, Intel 
>>> 80386, version 1 (SYSV), dynamically linked, interpreter 
>>> /lib/ld-linux.so.2, for GNU/Linux 2.6.32, stripped, with debug_info
>>>
>>> I choosed multilib right from the beginning of this adventure ...
>>>
>>> How can I check, whether the problem is caysed by gnutls or by the 
>>> system setup (regarding 32bit)?
>>>
>>> Cheers
>>> Meino
>>>
>>>
>>>
>>>
>>>
>> Hello,
>>
>> Can you give us more details of what do you want to do, what do you
>> already do, etc.
>>
>> Does /usr/bin/i686-pc-linux-gnu-pkg-config have the x (executable) 
>> permission ? (ls -l /usr/bin/i686-pc-linux-gnu-pkg-config)
>>
>>
>>
>> Hogren
>>
>>
>>
>>
> More mysterious hickups:
>
 Regenerating /etc/ld.so.cache...
> /sbin/ldconfig: File /lib64/ld-linux.so.2 is empty, not checked.
>
> Did it screwed up my new root?
>
> Cheers
> Meino
>
>
>
>
Maybe. But maybe it is fixable. /lib64/ld-linux.so.2 is a symlink to
glibc. But glibc cannot be wholly broken because if it were, then
nothing would work at all.

I'd first investigate if only the symlink needs to be fixed (should
point to /lib/ld-.so).

Have you updated glibc recently?Or any other important package/package
from @system?
Have you tried if 'revdep-rebuild' finds any broken libraries?

If glibc is really broken you can

1. chroot into a stage3
2. build a binpkg (type 'quickpkg glibc')
3. copy the binpkg from
'/usr/portage/packages/sys-libs/glibc-*.tbz2' in the stage3 to
   the same directory in your new root
4. install the binary glibc ('emerge ')

Then you should have a clean glibc install.

If you suspect an update of breaking anything you can always build
binary packages ahead. They are built from the installed package, so you
don't have any additional compiling. Then you can roll back quickly if
anything is damaged.

If you have a working glibc then you could also try re-emerging pkg-config.

Regards
Johannes

Re: [gentoo-user] Kernel modules: initramfs vs. /lib/modules

[Johannes Rosenberger]

On 13.02.2017 12:34, Rich Freeman wrote:
> On Mon, Feb 13, 2017 at 5:53 AM, marco restelli  wrote:
>> Could you suggest any reference about how an initramfs can help making
>> it easier to identify the correct root filesystem? Does this
>> functionality overlap with what grub can do, or is something
>> different?
>>
> The dracut references are fairly extensive, but they probably assume
> that you already know about something like this.  Keep in mind that on
> virtually all other distros end-users aren't expected to set up their
> own kernels or initramfs so there isn't a lot of general documentation
> out there.  And even within Gentoo a lot of people seem to avoid an
> initramfs, so our own docs may not be as extensive as they could be.
>
> [...]

There is some very good documentation about crafting your own initramfs
it the Gentoo wiki:
https://wiki.gentoo.org/wiki/Custom_Initramfs
https://wiki.gentoo.org/wiki/Early_Userspace_Mounting

Re: [gentoo-user] Re: Need help interpreting kernel panic

[Johannes Rosenberger]

On 11.02.2017 21:18, Harry Putnam wrote:
> Johannes Rosenberger <gen...@jorsn.eu> writes:
>
>> On 11.02.2017 20:47, Rich Freeman wrote:
>>> On Sat, Feb 11, 2017 at 2:12 PM, Harry Putnam <rea...@newsguy.com> wrote:
>>>> Again I get a kernel panic but this time its different.  It seems to
>>>> mount the disks ok but then fails to find a working `init' command.
>>>>
>>>> Checking that with sysrescueCD I see /sbin/init does exist on that new vm.
>>>> and is executable.
>>>>
>>>> The disk setup is sda1=/boot sda2=swap sda3=/home sda4=/
>>>>
>>> My guess is that it is mounting the wrong filesystem as root.  It
>>> might be detecting /dev/sdb as /dev/sda.  Also, the root device might
>>> be named /dev/xda4 depending on the kernel/etc.  Systemrescuecd isn't
>>> using the same kernel/etc so it might not see the disks the same way.
>>>
>>> An initramfs with root=UUID="505f850e-b26a-4d0f-a02f-6ba573a48ad8" (or
>>> a label) would be a more reliable way to handle this, or you can
>>> probably just fiddle with the device names until you stumble on the
>>> right one.
>>>
>>>
>> Well, if you look at the kernel messages you see that the init is found
>> but not executable (error -8). I don't know what the error number means, but
>> have you set CONFIG_BINFMT_ELF and CONFIG_BINFMT_SCRIPT in your .config?
>> Is /bin/sh executable?
> Error means ENOEXEC I think from browsing a bit on google
>
> About BINFMT
>
> Yes. (grepping from chroot at /usr/src/linux/)
>   grep BINFMT .config
>
>   CONFIG_BINFMT_ELF=y
>   CONFIG_BINFMT_SCRIPT=y
>   # CONFIG_BINFMT_AOUT is not set
>   # CONFIG_BINFMT_MISC is not set
>
>
> I just chrooted and re-emerged sysvinit but no help.  From chroot, I
> ran /sbin/init 3 and it did try to go to runlevel 3 (just brought me
> out of chroot), so it appears to be working.
>
> The stuff about `runaway loop' at modprobe (in the kernel messages)
> seems like it might mean something. 
>
> I think I'll test about modprobe for that module binfmt-46-4c
>
>
>
>
>

I found something interesting:
>  request_module: runaway loop modprobe binfmt-464c
> Short answer: If you are getting this error right after linux kernel
> initialization, you are likely booting a 32-bit kernel with a 64-bit OS.
>
> Long answer: If you boot a 32-bit kernel with a 64-bit OS, when the
> kernel tries to start /sbin/init (a 64-bit binary), it won't recognize
> the binary format, and it'll try to load the binfmt-464c kernel
> module, which is ELF support. (ELF support is generally compiled into
> the kernel, not built as a module, by the way.)
>
> The reason for the loop error is that the kernel is trying to invoke
> modprobe to load the module, and modprobe is itself an ELF binary,
> resulting in a recursion loop... 
--
http://saalwaechter-notes.blogspot.de/2008/10/requestmodule-runaway-loop-modprobe.html

I hope it helps.

Re: [gentoo-user] Need help interpreting kernel panic

[Johannes Rosenberger]

On 11.02.2017 20:47, Rich Freeman wrote:
> On Sat, Feb 11, 2017 at 2:12 PM, Harry Putnam  wrote:
>> Again I get a kernel panic but this time its different.  It seems to
>> mount the disks ok but then fails to find a working `init' command.
>>
>> Checking that with sysrescueCD I see /sbin/init does exist on that new vm.
>> and is executable.
>>
>> The disk setup is sda1=/boot sda2=swap sda3=/home sda4=/
>>
> My guess is that it is mounting the wrong filesystem as root.  It
> might be detecting /dev/sdb as /dev/sda.  Also, the root device might
> be named /dev/xda4 depending on the kernel/etc.  Systemrescuecd isn't
> using the same kernel/etc so it might not see the disks the same way.
>
> An initramfs with root=UUID="505f850e-b26a-4d0f-a02f-6ba573a48ad8" (or
> a label) would be a more reliable way to handle this, or you can
> probably just fiddle with the device names until you stumble on the
> right one.
>
>
Well, if you look at the kernel messages you see that the init is found
but not executable (error -8). I don't know what the error number means, but
have you set CONFIG_BINFMT_ELF and CONFIG_BINFMT_SCRIPT in your .config?
Is /bin/sh executable?

Re: [gentoo-user] Different build options for specific packages

[Johannes Rosenberger]

On 11.02.2017 12:22, Dale wrote:
> Johannes Rosenberger wrote:
>> On 11.02.2017 10:39, Dale wrote:
>>> Mick wrote:
>>>> This is how I have configured per package FEATURES here and it seems to 
>>>> work.  
>>>> For example configuring ccache for large packages which take days to 
>>>> emerge on 
>>>> an old PC:
>>>>
>>>> # cat /etc/portage/env/ccache.conf 
>>>> FEATURES="ccache"
>>>>
>>>> Now I need to point particular package(s) to it:
>>>>
>>>> # cat /etc/portage/package.env 
>>>> app-office/libreoffice ccache.conf
>>>> www-client/firefox ccache.conf
>>>> www-client/chromium ram_limit.conf ccache.conf
>>>>
>>>> If I want more packages to use ccache.conf I add their name/version in the 
>>>>  
>>>> /etc/portage/package.env file.
>>>>
>>> I just tried copying your way, except for the setting I want, and it
>>> didn't work.  I'm wondering if it just won't do this particular setting
>>> for some reason. 
>>>
>>> I've tried having package.env as a file and as a directory.  It didn't
>>> like either way.  Either it can't do this or I'm missing something
>>> really simple here. 
>>>
>>> Thanks. 
>>>
>>> Dale
>>>
>>> :-)  :-) 
>>>
>> I think the problem is that you can change FEATURES but not emerge
>> arguments while emerging since ebuild(1) is invoked fore every package
>> but emerge(1) once for all.
>>
>> So I see two possible solutions here:
>>
>> 1. Dump the list of packages to install via emerge -p. Then split the
>> list up and chain
>>emerge invocations (possibly with arg --nodeps) such that the
>> non-parallel
>>packages will be invoked separately.
>> 2. Use emerge options -j and --load-average so that no new ebuilds are
>> started
>>while one uses much cpu load. In my experience this does not
>> unparallellize
>>reliably but I am trying out to use higher job  and load limits in
>> MAKEOPTS
>>than in emerge args so single packages that can utilize the whole cpu
>> do so before
>>emerge intervenes and starts another ebuild.
>>
>> I hope this helps
>>
>> Johannes
>>
>>
>>
> Based on this and Neil's reply, I may just have to tell it to exclude
> updating those when I do my regular updates.  Then go back and tell it
> to do them later one at a time. 
>
> The biggest reason I needed to do this is that I usually have portage's
> work directory on tmpfs.  I just don't have enough memory to do them all
> at the same time, one at a time would work tho.  If I ever get around to
> upgrading to 32GBs, then this won't matter. 
>
> Thanks.
>
>
> Dale
>
> :-)  :-) 
>

What about using zram with lz4 for the work directory
(https://wiki.gentoo.org/wiki/Zram)?
Could be a good compromise. I'm using it (8GB RAM) but haven't
benchmarked against tmpfs.

Re: [gentoo-user] Different build options for specific packages

[Johannes Rosenberger]

On 11.02.2017 10:39, Dale wrote:
> Mick wrote:
>> This is how I have configured per package FEATURES here and it seems to 
>> work.  
>> For example configuring ccache for large packages which take days to emerge 
>> on 
>> an old PC:
>>
>> # cat /etc/portage/env/ccache.conf 
>> FEATURES="ccache"
>>
>> Now I need to point particular package(s) to it:
>>
>> # cat /etc/portage/package.env 
>> app-office/libreoffice ccache.conf
>> www-client/firefox ccache.conf
>> www-client/chromium ram_limit.conf ccache.conf
>>
>> If I want more packages to use ccache.conf I add their name/version in the  
>> /etc/portage/package.env file.
>>
> I just tried copying your way, except for the setting I want, and it
> didn't work.  I'm wondering if it just won't do this particular setting
> for some reason. 
>
> I've tried having package.env as a file and as a directory.  It didn't
> like either way.  Either it can't do this or I'm missing something
> really simple here. 
>
> Thanks. 
>
> Dale
>
> :-)  :-) 
>

I think the problem is that you can change FEATURES but not emerge
arguments while emerging since ebuild(1) is invoked fore every package
but emerge(1) once for all.

So I see two possible solutions here:

1. Dump the list of packages to install via emerge -p. Then split the
list up and chain
   emerge invocations (possibly with arg --nodeps) such that the
non-parallel
   packages will be invoked separately.
2. Use emerge options -j and --load-average so that no new ebuilds are
started
   while one uses much cpu load. In my experience this does not
unparallellize
   reliably but I am trying out to use higher job  and load limits in
MAKEOPTS
   than in emerge args so single packages that can utilize the whole cpu
do so before
   emerge intervenes and starts another ebuild.

I hope this helps

Johannes

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Johannes Rosenberger]

On 05.02.2017 08:34, J. Roeleveld wrote:
> On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
>> Hi,
>>
>> since my old Gentoo installation seems to be screwed up (regarding
>> the update process) beyond repair I decided to install a new one
>> instead of waiting for help.
>>
>> I already made space at a certain of my harddisk and installed the
>> stage3 there.
>> Chrooting is one of the first steps to check, whether what I have
>> done so is valid.
>>
>> But before deleting the old root and install the new one at its
>> place I would like to do a atmost identical boot into the new
>> root.
>>
>> As far as I know the kernel only allows to boot into a partition
>> (instead of a directory on a partition containing the root
>> installation) and I am still using devices to boot from instead
>> of GPT.
>>
>> Is there any neat trick to do a real boot into the new root via
>> the normal boot process (grub2) nevertheless ?
>>
>> Cheers
>> Meino
> If I understand correctly. The answer is no. (Unless you write some clever 
> initramfs)
>
> Afaik, the kernel takes the entire partition and mounts it at '/'. If you 
> want it to use a directory (which would then be at '/newinstall') you need to 
> get the kernel to chroot into that directory and run init in there.
>
> Only option I see is to use an extra disk. Maybe a USB drive and use that.
>
> --
> Joost


Hi!

If I understand correctly, the answer is YES! You even needn't write an
initramfs, although that wouldn't have to be very clever: An initramfs
simply loads the necessary kernel modules for mounting the root
partition, mounts it and in the end does this:

exec switch_root   

The manpage for switch_root says that  must be the root of a
mount and gives a trick for mounting arbitrary dirs: Just run a 'mount
--bind  ' before.
So, assuming your system is installed to /newinstall, you can just place
the following shell script  in e.g.  /newinstall/switch_root.sh:

#!/bin/sh

ROOT=/newinstall

mount --bind "$ROOT" "$ROOT"
exec switch_root "$ROOT" /sbin/init

#EOF

Then run 'chmod +x /newinstall/switch_root.sh'.

Now you add 'init=/newinstall/switch_root.sh' to your kernel commandline
(grub.cfg) and just boot  ist.
If you have some esoteric mount setup and need to use fstab in the
initramfs, then it is probably better to do it in an initramfs. I can
post a link to some easy initramfs setup, if you like. I'd need to
comment mine a bit so that everybody understands why I do what.

I haven't tried this specific script but have once created my own
initramfs for a special btrfs setup with some subvolumes.
If you try this, please let me know if it works!

Sorry for replying so late, i sent this mail last Sunday but from the
wrong email address. So it was probably dropped.


Cheers

Johannes