public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: dhcpcd: Update to 6.9.3 - with or without '10-mtu'?
Date: Fri, 09 Oct 2015 15:31:41 +0200	[thread overview]
Message-ID: <5617C1BD.7060005@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Hi list,

I'd like to have a small problem, so I'm asking here before something 
goes bork...: ;-)

I found this update for 'dhcpcd' to 6.9.3. So I decided to test it. 
Building was ok, but I'm not sure if the result would fit into our 
current IPFire builds.

First, I had to disable a 'sed'-line in lfs-file, the file '10-mtu' is 
no longer included:

...
sed -i -e "s|-ge 576|-gt 576|g" $(CONFIG_ROOT)/dhcpc/dhcpcd-hooks/10-mtu
...

This is intentional by the programmer, source says in 
'/dhcpcd-hooks/Makefile':

...
	# We need to remove the old MTU change script if we at all can.
	rm -f ${DESTDIR}${SCRIPTSDIR}/10-mtu
...

Accordingly, building stopped with a file-not-found error. After 
commenting the 'sed'-line, everything went ok, but 
'/var/ipfire/dhcpc/dhcpcd-hooks/10-mtu' is now missing.

My questions:

Do we really need this missing '10-mtu' file?
Sorry if this is a dumb question, but I'm just not sure about the 
relationsships.

Is a complete reboot required during an eventual upgrade? Or would it be 
sufficient to disconnect / connect / reboot network, whatever...?

Thanks for any hints!

Regards
Matthias

             reply	other threads:[~2015-10-09 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 13:31 Matthias Fischer [this message]
2015-10-10  9:24 ` Arne Fitzenreiter

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=5617C1BD.7060005@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.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