1 |
On Fri, Oct 13, 2017 at 11:34 AM, Mike Gilbert <floppym@g.o> wrote: |
2 |
> On Fri, Oct 13, 2017 at 1:29 PM, Daniel Frey <djqfrey@×××××.com> wrote: |
3 |
>> |
4 |
>> So *why* on earth is it a dependency when (from what I've been reading after |
5 |
>> discovering this) many ISPs don't seem to support it properly yet? |
6 |
>> |
7 |
>> And is there a way to build systemd without ipv6? Or am I going to have to |
8 |
>> revert these three systems back to openrc? |
9 |
> |
10 |
> Instead of stripping IPv6 out of your kernel, I would suggest that you |
11 |
> simply disable it on any network interfaces. How you do this would |
12 |
> depend on the method you use to manager your network config. |
13 |
> |
14 |
> If you really want to remove IPv6 from your kernel, simply disable the |
15 |
> GENTOO_LINUX_INIT_SYSTEMD config option, and enable the other other |
16 |
> dependencies manually. |
17 |
> |
18 |
> https://gitweb.gentoo.org/proj/linux-patches.git/tree/4567_distro-Gentoo-Kconfig.patch#n106 |
19 |
> |
20 |
|
21 |
Just to expand a bit on this - the Gentoo-added service manager kernel |
22 |
options are purely for convenience. If you don't use gentoo-sources |
23 |
you won't see them at all, because they're not part of the upstream |
24 |
kernel. All they do is pull in a bunch of other options. Back in the |
25 |
"good old days" people would look at the wiki (or pre-wiki) page for |
26 |
openrc, see a list of mandatory kernel options, and set those options |
27 |
when building their kernel. Then somebody had the clever idea that it |
28 |
would be easier for users to not shoot themselves in the foot if we |
29 |
just gave a one-click option that set all the requirements |
30 |
automatically. However, the kernel configuration settings doesn't |
31 |
really have any concept of "optional dependencies" - so we're stuck |
32 |
with either not pulling in ipv6, which mostly works, or pulling it in, |
33 |
which always works. |
34 |
|
35 |
It is completely safe to answer no to whether you use systemd and |
36 |
openrc, and then just manually answer yes to the things that you need. |
37 |
Just keep in mind that you may run into issues if you don't enable |
38 |
something that is truly mandatory, or you might have diminished |
39 |
functionality. It also means that you need to keep your ears open for |
40 |
when the requirements change, since there won't be a Gentoo automagic |
41 |
kernel config setting to change things for you. That said, running an |
42 |
upstream kernel isn't really that big a deal - I do that since I run |
43 |
btrfs and zfs and want to have a bit more control over which series |
44 |
I'm running to mitigate the bugs. |
45 |
|
46 |
-- |
47 |
Rich |