From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Shorewall config problem
Date: Tue, 13 Nov 2018 19:06:03 +1100 [thread overview]
Message-ID: <CAC=wYCHsEU5hDnTKnndS0wS37Bz=0rkbYqOhgPU2Ka4Zi67R+Q@mail.gmail.com> (raw)
In-Reply-To: <9528270e-79bf-c9b0-7c04-18b07ed9f035@iinet.net.au>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
>
> > Yep, grepped my .config archive and its gone in 4.19 so the shorewall
> > ebuild (at least) will need an update. Checked bugzilla?
>
>
> Grepping .config will only work sometimes - If its enabled it will be
> there, if not it "may or may not be"
>
My .config hasnt changed, other than from setting the new options via make
oldconfig;
/usr/src/configs # grep CONFIG_NF_CONNTRACK_IP config-2018-10-29
config-2018-11-13
config-2018-10-29:CONFIG_NF_CONNTRACK_IPV4=y
config-2018-10-29:CONFIG_NF_CONNTRACK_IPV6=y
/usr/src/configs # head -n3 config-2018-10-29 config-2018-11-13
==> config-2018-10-29 <==
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.18.16-gentoo Kernel Configuration
==> config-2018-11-13 <==
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.19.0-gentoo Kernel Configuration
/usr/src/configs #
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
next prev parent reply other threads:[~2018-11-13 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 10:11 [gentoo-user] Shorewall config problem Peter Humphrey
2018-11-12 10:19 ` J. Roeleveld
2018-11-12 10:54 ` Peter Humphrey
2018-11-13 4:09 ` Adam Carter
2018-11-13 6:02 ` Bill Kenworthy
2018-11-13 8:06 ` Adam Carter [this message]
2018-11-14 15:33 ` Peter Humphrey
2018-11-14 22:03 ` Adam Carter
2018-11-15 9:38 ` Peter Humphrey
-- strict thread matches above, loose matches on Subject: below --
2015-05-06 15:20 Peter Humphrey
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='CAC=wYCHsEU5hDnTKnndS0wS37Bz=0rkbYqOhgPU2Ka4Zi67R+Q@mail.gmail.com' \
--to=adamcarter3@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