From: Fred Stratton <fredstratton@imap.cc>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] development build 3.10.17-2 released
Date: Mon, 21 Oct 2013 14:50:34 +0100 [thread overview]
Message-ID: <5265312A.5030409@imap.cc> (raw)
In-Reply-To: <CAMybZqyHjmaZK3GAu5rmhLy9j+E_02fCkT6Pkxz_kR+_S8fs6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
I have installed this build, but cannot access the web interface. Am
presently trying to determine how to reinstall the configuration file
from the cli, other than item by item, so I can attempt to rebuild the
build from within. Have reverted to earlier build for now to regain
internet access.
On 21/10/13 13:22, David Personette wrote:
> I'm not sure what's changed but 3.10.17-2 is working for me, so far.
>
> Was anyone paying attention to nftables (iptables replacement)? I just
> saw that it was merged into net-next. On the LTS 3.10.x it won't have
> any impact for now, and apparently there's a backwards compatibility
> utility to still process iptables rules...
>
> --
> David P.
>
>
> On Mon, Oct 21, 2013 at 5:26 AM, David Personette <dperson@gmail.com
> <mailto:dperson@gmail.com>> wrote:
>
> FYI: direct changes to the /overlay aren't noticed by the kernel,
> you have to reboot first. I can't say that I'm an expert, I've
> just poked around at it. I just deleted the whole directory (IE:
> rm -rf /overlay/etc/uci-defaults). Upon reboot the entire
> directory is reverted to the contents of /rom.
>
> --
> David P.
>
>
> On Mon, Oct 21, 2013 at 12:11 AM, Michael Richardson
> <mcr@sandelman.ca <mailto:mcr@sandelman.ca>> wrote:
>
>
> David Personette <dperson@gmail.com
> <mailto:dperson@gmail.com>> wrote:
> > you have made a change, then it's read from the overlay.
> A change that you can
> > make is deleting a file that exists on the /rom image,
> and that can be stored
> > on the overlay as well (the file will be not be visible
> in the merged /). You
> > can purge changes that you have made by removing the
> corresponding file(s) and/
> > or directory(s) in the /overlay filesystem.
>
> How do I see/delete the mark in the /overlay that marks the
> file in the /rom as
> deleted?
>
> --
> ] Never tell me the odds! | ipv6
> mesh networks [
> ] Michael Richardson, Sandelman Software Works |
> network architect [
> ] mcr@sandelman.ca <mailto:mcr@sandelman.ca>
> http://www.sandelman.ca/ | ruby on rails [
>
>
>
[-- Attachment #2: Type: text/html, Size: 6411 bytes --]
next prev parent reply other threads:[~2013-10-21 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 5:41 [Cerowrt-devel] development build 3.10.17-1 released Dave Taht
2013-10-20 8:35 ` Fred Stratton
2013-10-20 13:12 ` Fred Stratton
2013-10-20 13:17 ` David Personette
2013-10-20 13:41 ` Fred Stratton
2013-10-20 13:55 ` David Personette
2013-10-21 4:11 ` Michael Richardson
2013-10-21 9:26 ` David Personette
2013-10-21 12:22 ` David Personette
2013-10-21 13:50 ` Fred Stratton [this message]
2013-10-21 14:46 ` [Cerowrt-devel] development build 3.10.17-2 released David Personette
2013-10-21 15:39 ` Fred Stratton
2013-10-21 16:38 ` Fred Stratton
2013-10-21 17:18 ` David Personette
2013-10-21 18:23 ` Dave Taht
2013-10-21 1:22 ` [Cerowrt-devel] development build 3.10.17-1 released Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5265312A.5030409@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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