给大家看看这几年 glibc 在 Gentoo 上疯狂的升级：

Sat Apr 9 03:28:49 2016 >>> sys-libs/glibc-2.22-r4
merge time: 11 minutes and 36 seconds.

Sat Jan 7 03:29:09 2017 >>> sys-libs/glibc-2.23-r3
merge time: 11 minutes and 49 seconds.

Sat Jun 24 03:28:29 2017 >>> sys-libs/glibc-2.23-r4
merge time: 11 minutes and 16 seconds.

Sat Nov 4 03:26:04 2017 >>> sys-libs/glibc-2.25-r8
merge time: 8 minutes and 49 seconds.

Sat Nov 18 03:25:38 2017 >>> sys-libs/glibc-2.25-r9
merge time: 8 minutes and 23 seconds.

Sat Feb 10 03:25:51 2018 >>> sys-libs/glibc-2.25-r10
merge time: 8 minutes and 37 seconds.

Sat Mar 31 03:26:10 2018 >>> sys-libs/glibc-2.25-r11
merge time: 8 minutes and 55 seconds.

定制后的 Gentoo 的稳定性 /可靠性比其它发行版强的太多，现在配置服务器都是 host 为 gentoo，各种服务全部扔到 qemu/kvm 里的 ubuntu centos fedora 上

Microsoft 不打算多捐点钱给 OpenBSD 么，他们可是穷的响当当

https://www.openbsdfoundation.org/campaign2018.html

把数据倒出来，做一次安全擦除速度就恢复了

首先排除希捷，其次没人手维护不选 RAID 是可以理解的，RAID 一旦出现故障或有硬盘出错，恢复起来不比开盘省事，如果数据重要，不要考虑移动硬盘，邮寄用 HDD 硬盘的风险有点大，用 SSD 对数据安全比较有保障，虽然成本有点高

启用 zram 吧

@cnt2ex 说句实话，有没有 systemd，Linux 一样生存的好好的，还可能会更好些

@lfzyx 问题不在于 Requires Before After，这玩意纸面上很好看，出了问题排查起来那个困难，你 google 一下吧，要不 ubuntu 也不会留着 syslog 不放，光靠 systemd 的二进制 log，出一次问题能让你有把 systemd 的作者拎出来砍几刀的冲动

gnome without systemd

https://wiki.gentoo.org/wiki/GNOME/GNOME_Without_systemd
https://github.com/dantrell/gentoo-project-gnome-without-systemd

请点赞支持

把无线路由的天线换成扇形天线或其它定向天线

C

@tailf 我的感觉正相反，systemd 太复杂了，再简单的服务管理起来都变得不容易，就像要通过 systemd 的 log 来解决问题一样，在 systemd 下是相当烦人的

systemd 的所谓启动速度其实有相当的欺骗性，很多时候系统看上去已经启动完了，但有些服务其实还在后台继续启动中，有时候这会造成依赖关系的崩溃，我就是这个原因在自己的定制系统中不得不放弃了 systemd

用 Gentoo 可以彻底远离 systemd

https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet_router.html

Lastly configure the firewall. In SuSEfirewall2, you need to set FW_ROUTE="yes" (otherwise it will also reset forwarding sysctl again) and define the interfaces in the FW_DEV_INT, FW_DEV_EXT (and FW_DEV_DMZ) zone variables as needed, perhaps also FW_MASQUERADE="yes" and FW_MASQ_DEV.

以前的 suse 机器已经退役，手头上没有现成的 suse 来测试

几年前就讨论过：
The SuSeFirewall service overwrites network related sysctl settings. I suppose this is a bug. Do you know if there is a way to tell the firewall scripts to leave untouched sysctl parameters ?
I had a look to SuSeFirewall yast graphic configuration mask and to /etc/sysconfig/SuSEFirewall* files, without any success.

Is someone of you so kind to do a very simple test just to double check if this behavior is common to all 12.2 installations and it's not related someway with my particular configuration. ?

The test could be very simple:
1) modify something network related using /etc/sysctl.conf, for example add some lines like this:
net.ipv4.conf.default.log_martians = 0
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.br0.log_martians = 0
net.ipv4.conf.eth0.log_martians = 0
Please note that the value you are modifying must be different from kernel default
2) enable SuSEFirewall service
3) reboot
4) verify that your modifications are reverted to default

cat /proc/sys/net/ipv4/conf/eth0/log_martians
1

5) disable SuSEFirewall service
6) reboot
7) verify taht your modifications are in place

cat /proc/sys/net/ipv4/conf/eth0/log_martians
0

It was not a bug! the FW_KERNEL_SECURITY parameter in /etc/sysconfig/ allows you to stop SuSeFirewall from automatically setting several sysctl network related parameters.

https://forums.opensuse.org/showthread.php/483021-networking-settings-in-sysctl-conf-not-applyed-or-overwritten

Jave 已经够慢的了，还来个更慢的 Scala ?

@standin000 Gentoo 升级编译有依赖关系检查，通不过就不让编译，编译失败算是升级失败，但不会导致系统挂掉