From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why I can't I build systemd without ipv6?
Date: Sat, 14 Oct 2017 08:00:50 -0700 [thread overview]
Message-ID: <65246d85-df9f-8023-044f-6c9e384677b5@gmail.com> (raw)
In-Reply-To: <CAOdo=SzS-k_d_micJWN=uejVN-LUL2=Kpza9g9kzsOc3Nj9ydw@mail.gmail.com>
On 10/14/2017 12:37 AM, Tom H wrote:
> On Fri, Oct 13, 2017 at 5:58 PM, Daniel Frey <djqfrey@gmail.com> wrote:
>> On 10/13/2017 11:05 AM, Canek Peláez Valdés wrote:
>>>
>>> Have you tried to boot the systems with the "disable_ipv6=1" kernel
>>> parameter?
>>
>> I just tried this, and it doesn't seem to help.
>>
>> # cat /proc/cmdline
>> disable_ipv6=1 root=/dev/md126p3 rd.auto=1 quiet rootfstype=ext4
>> init=/usr/lib/systemd/systemd
>>
>> But:
>>
>> # dmesg | grep -i ipv6
>> [ 22.218113] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 22.241260] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 26.421072] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
> it's "ipv6.disable_ipv6=1" not "disable_ipv6=1".
>
Argh, I shouldn't have assumed that it was the full parameter. Oh well,
on that machine, I managed to switch back to openrc. That didn't go real
smoothly, portage couldn't figure out how to do it on it's own after
switching profiles, it was blindly removing and rebuilding some packages
manually that eventually made it work and not want to pull in systemd again.
After that, I was able to reconfigure the kernel without ipv6 at all...
rebooted... and openrc Just Worked(tm) with my network issue gone.
For the other two, I'll try again but this time with the proper kernel
parameter. That could've saved me a lot of time, but oh well.
Dan
next prev parent reply other threads:[~2017-10-14 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 17:29 [gentoo-user] Why I can't I build systemd without ipv6? Daniel Frey
2017-10-13 17:41 ` Jack
2017-10-13 19:21 ` Daniel Frey
2017-10-13 17:41 ` daniel
2017-10-13 19:23 ` Daniel Frey
2017-10-13 17:50 ` [gentoo-user] " Grant Edwards
2017-10-13 19:38 ` Daniel Frey
2017-10-13 18:05 ` [gentoo-user] " Canek Peláez Valdés
2017-10-13 19:33 ` Daniel Frey
2017-10-13 21:58 ` Daniel Frey
2017-10-14 7:37 ` Tom H
2017-10-14 15:00 ` Daniel Frey [this message]
2017-10-13 18:34 ` Mike Gilbert
2017-10-13 19:02 ` Rich Freeman
2017-10-13 19:42 ` Daniel Frey
2017-10-13 19:32 ` Daniel Frey
2017-10-13 20:58 ` Vadim A. Misbakh-Soloviov
2017-10-13 21:48 ` [gentoo-user] " Grant Edwards
2017-10-13 21:55 ` Daniel Frey
2017-10-14 11:05 ` Mick
2017-10-14 15:03 ` Daniel Frey
2017-10-14 15:08 ` [gentoo-user] " Daniel Frey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65246d85-df9f-8023-044f-6c9e384677b5@gmail.com \
--to=djqfrey@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox