Meet me in freenode's fvwm IRC channel.
Automated rebuild of portage packages
This solution relies on the sys-process/cronie and the usage of anacron USE flag.
What does that anacron USE flag do, verify using the euse tool:
euse -i anacron
[- ] anacron (sys-process/cronie): Install the periodic anacron command scheduler.
it is a added feature or function to cronie. The anacron USE flag re-schedules missed cron jobs for machines that are not 24/7 online, like f.e. laptops, workstations. Apart from that it is working like an usual cron scheduler. This feature does not rely on the separate anacron package. Install cronie:
emerge --ask sys-process/cronie
Schedule daily rebuild by adding following file in the /etc/cron.daily/ directory:
#!/bin/sh # # Sync portage using eix-sync # -U Do not touch the database, do not show differences # -T Do not measure time /usr/bin/eix-sync -U -T if [ $? -eq 0 ]; then logger "eix-sync has finished." else logger "eix-sync has exited with error code: $?" fi # Now update the database /usr/bin/eix-update if [ $? -eq 0 ]; then logger "eix-update has finished." else logger "eix-update has exited with error code: $?" fi # Emerge system packages first emerge -uDN @system if [ $? -eq 0 ]; then logger "emerge --system has finished." else logger "emerge --system has exited with error code: $?" fi # Emerge world packages next. For skipping bugged ebuild, # add "EMERGE_DEFAULT_OPTS= --keep-going"* to make.conf file emerge -uDN @world if [ $? -eq 0 ]; then logger "emerge --world has finished." else logger "emerge --world has exited with error code: $?" fi # And keep everything working emerge @preserved-rebuild if [ $? -eq 0 ]; then logger "emerge @preserved-rebuild has finished." else logger "emerge @preserved-rebuild has exited with error code: $?" fi # Write a message to syslog portage rebuild has finished now. logger "daily cron portage update has finished with exit status: $?"
Make the /etc/cron.daily/portage file executable by adding the +x flag:
chmod +x /etc/cron.daily/portage
This will schedule run the eix-sync and ebuild jobs, at ~03:00 AM. And if the job has been missed because host was turned off, the job gets scheduled after a the host has been turned on again.
Now it would be nice to see, what has been rebuild and how it worked out without using any complex commands. Add a bash script to the ~/bin directory of the root user. The script runs 2 qlop commands showing the results from beginning of the day. qlop is part of app-portage/portage-utils ebuild.
#!/bin/sh qlop -H -s -d '1 day ago' qlop -H -m -u -d '1 day ago'
Make the /root/bin/emergelog.sh file executable by adding the +x flag:
chmod +x ~/bin/emergelog.sh
Because I am even to tazy to run that command manually, I add following lines to the /root/.profile file, this calls the upper /root/bin/emergelog.sh, each time the root user authenticates to this host. Additionally this lists the last 8 lines of the /var/log/emerge.log file:
echo "Last emerged packages:" sh ~/bin/emergelog.sh echo "" echo "Last emerge.log entries:" tail -n 8 /var/log/emerge.log echo ""
And this is the prompt how it looks like after successful authentication:
Last emerged packages: 2020-04-21T02:30:13 *** gentoo 2020-04-21T03:22:44 >>> dev-util/re2c 2020-04-21T03:32:45 >>> net-misc/whois 2020-04-21T08:20:39 >>> dev-libs/libpcre2 Last emerge.log entries: 1587455666: *** Finished. Cleaning up... 1587455669: *** exiting successfully. 1587455669: *** terminating. 1587455675: Started emerge on: Apr 21, 2020 09:54:34 1587455675: *** emerge --keep-going @preserved-rebuild 1587455687: *** Finished. Cleaning up... 1587455690: *** exiting successfully. 1587455691: *** terminating.
This is not a mandatory step, but could be useful on always on systems. For the update routine to be sane. The daemons that have changed libriaries would need a restart. Install following:
emerge --ask app-admin/needrestart
Default configuration needs to be adjusted to the own system. Do not rely on defaults. needstart needs further configuration. The list of all configuration files:
Now this solution works 99% of the time. If packages fail to build, this needs to be resolved manually by doing a world rebuild, and inspecting what has gone wrong.
laptop_mode laptop roaming howto
These packages are all needed to get it to rrun: *openrc — a dependency-based init system that maintains compatibility with the system provided init program - wit enabled USE flag netifrc *wpa_supplicant — a wifi supplicant to handle network authentication. *sys-apps/ifplugd - Brings up/down ethernet ports automatically with cable detection *dhcpcd — a popular DHCP client capable of handling both IPv4 and IPv6 configuration. *app-laptop/laptop-mode-tools - Linux kernel laptop_mode user-space utilities
Managing daemon status and interfaces reflecting the current powerlevel AC or running on battery. This can be accomplished by using sys-apps/openrc. Open-RC configuration and management is more complex compared to the app-laptop/laptop-mode-tools configuration approach, but also much more flexible. A simplified openrc configuration is needed. Dynamic services are handled by laptop-mode-tools. Overview of running daemons handled by openrc runlevel default, note laptop_mode daemon is started here:
Runlevel: default lm_sensors [ started ] sysklogd [ started ] sensord [ started ] alsasound [ started ] acpid [ started ] cupsd [ started ] cronie [ started ] chronyd [ started ] laptop_mode [ started ] local [ started ] sshd [ started ]
Following daemons need to be managed by laptop-tools:
net.eth0 [ started ] net.wlan0 [ started ] sshd [ started ] cupsd [ started ]
Remove the daemons from the open-rc default startup level
rc-update del net.eth0 default
rc-update del net.wlan0 default
rc-update del net.sshd default
rc-update del net.cupsd default
Verify the defautl startup of open-rc:
Runlevel: default lm_sensors [ started ] sysklogd [ started ] sensord [ started ] alsasound [ started ] acpid [ started ] cronie [ started ] chronyd [ started ] laptop_mode [ started ] local [ started ]
The laptop_mode tools dynamic configuration relies on default 2 ACPI levels: * laptop is running on AC power * laptop is running on battery laptop-mode tools has 2 according ACPI states named batt and lm-ac: * batt * lm-ac * nolm-ac The 3-rd state nolm-ac (laptop-mode tools daemon NOT running) is not used. Get an overview of the laptop-mode directory:
tree -L 1 /etc/laptop-mode
/etc/laptop-mode ├── batt-start ├── batt-stop ├── conf.d ├── laptop-mode.conf ├── lm-ac-start ├── lm-ac-stop ├── lm-profiler.conf ├── modules ├── nolm-ac-start └── nolm-ac-stop
Each of the 3 predefined states batt lm-ac and nolm-ac have a -start and -stop suffix in the directory structure. There is also a conf.d directory for services configuration that would be handled by laptop-mode and a modules directory for modules to be used explicitelly. The goal is reached when the laptop automatically determines which daemons need to be started and which need to be stopped depending on the ACPI battery level. There are 2 states in which the laptop is working: * laptop is docked, ac connected, wired access, printing available, ssh daemon running * laptop is not docked, battery, wireless access, no priting available, no ssh daemon runni Adjust the previosly removed daemons to laptop-mode. Change to the battery level. wlan is the only one service needed while running on battery. Change to the directory:
Create a symlink to daemons to be run while on battery:
ln -s /etc/init.d/net.wlan0 .
Change to the directory /etc/laptop-mode/batt-stop/:
Create a symlink to deamons to be stopped while on battery:
ln -s /etc/init.d/cupsd .
ln -s /etc/init.d/net.eth0 .
ln -s /etc/init.d/sshd .
Start and Stop daemons handled by the battery status after configuration:
tree -L 1 /etc/laptop-mode/batt-st*
tree -L 1 /etc/laptop-mode/batt-st* /etc/laptop-mode/batt-start └── net.wlan0 -> /etc/init.d/net.wlan0 /etc/laptop-mode/batt-stop ├── cupsd -> /etc/init.d/cupsd ├── net.eth0 -> /etc/init.d/net.eth0 └── sshd -> /etc/init.d/sshd
Start and Stop daemons handled by the battery status:
tree -L 1 /etc/laptop-mode/lm-ac-st*
/etc/laptop-mode/lm-ac-start ├── cupsd -> /etc/init.d/cupsd ├── net.eth0 -> /etc/init.d/net.eth0 └── sshd -> /etc/init.d/sshd /etc/laptop-mode/lm-ac-stop └── net.wlan0 -> /etc/init.d/net.wlan0
Docked laptop and service status:
Runlevel: default lm_sensors [ started ] sysklogd [ started ] sensord [ started ] alsasound [ started ] mpd [ started ] acpid [ started ] cronie [ started ] chronyd [ started ] laptop_mode [ started ] local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed/wanted net.eth0 [ started ] cupsd [ started ] Dynamic Runlevel: manual sshd [ started ]
Runlevel: default lm_sensors [ started ] sysklogd [ started ] sensord [ started ] alsasound [ started ] mpd [ started ] acpid [ started ] cronie [ started ] chronyd [ started ] laptop_mode [ started ] local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed/wanted net.wlan0 [ started ]
This is a ready, easy to use, running configuration.
Enable IPv6 privacy extensions (RFC4941)
IPv6 privacy extensions are disabled by default on GNU/linux, they lead to problems if users are not aware of this. To enable privacy extensions on gentoo permanently add following lines and reboot the system:
... # Enabling IPv6 privacy extensions for specified interfaces. # here eth0 and wlan0 # net.ipv6.conf.eth0.use_tempaddr = 2 # net.ipv6.conf.wlan0.use_tempaddr = 2 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 # Setting q shorter timeout for a temporary IPv6 prefix # default setting is one day net.ipv6.conf.eth0.temp_prefered_lft = 14400 net.ipv6.conf.wlan0.temp_prefered_lft = 14400
The setting net.ipv6.conf.all.use_tempaddr is used to propagate its value to all interfaces currently attached to the system. This setting might not work reliably for all interfaces. At least not on my own tested gentoo installations up to kernel 4.14.
There are two old bugs in the Linux kernel bugtracker for this issue:
Wiki templates for templates
Command sequence for old gentoo boxes to update after a long time
This is a basic sequence of commands for updating older gentoo boxes.
Divide and conquer: Update the toolchain first, then resolve the blocks manually afterwards.
Sync portage tree:
Update the portage application:
Sync portage again:
Emerge GCC first:
Show availabe GCC compilers:
eselect gcc list
Set the latest available GCC compiler in the list:
eselect gcc set <input>
Check if the desired GCC has been set, apply portage postinstall hint:
eselect gcc list
Emerge latest glibc
Check the latest gentoo related toolchain changes on the wiki, bugs, etc: https://wiki.gentoo.org/wiki/Project:Toolchain
Emerge latest binutils:
Show current availble binutils:
eselect binutils list
Set the latest binutils version:
eselect binutils set <input>
Verify binutils setting:
eselect binutils list
Emerge latest python
Emerge latest perl:
Emerge latest iproute2
Update the system with following command, resolve dependency errors:
emerge -vauDN system
Update the system with following command, resolve dependency errors:
emerge -vauDN world
Now it is done.