From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: Core Update 140/141 (testing) report
Date: Sun, 09 Feb 2020 13:36:51 -0500 [thread overview]
Message-ID: <4d0fba2a-5cbf-d10d-05cc-21b2f0b058d9@rymes.com> (raw)
In-Reply-To: <206cc60b-491b-16e0-b17a-6795f7640004@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
I just downloaded Core 141, and all seems to have gone well. DNS was
migrated to the new setup page, and all seems to be working after some
basic testing.
However, I do not see rfkill. There is a new file /dev/rfkill, but I
receive a "Permission Denied" error when I try to execute it. Adding
execute privileges does not help.
Also, I wonder if we should add a note "DNS is configured in the Web
Interface" or similar to the setup program for anyone who is used to
configuring that in Setup and who did not get the message.
Tom
prev parent reply other threads:[~2020-02-09 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 17:54 Peter Müller
2020-02-09 18:36 ` Tom Rymes [this message]
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=4d0fba2a-5cbf-d10d-05cc-21b2f0b058d9@rymes.com \
--to=trymes@rymes.com \
--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