From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 114, Issue 4
Date: Wed, 17 Nov 2021 12:03:20 -0500 [thread overview]
Message-ID: <EC4E1AA0-7BD6-4E1F-AE5E-3E8E7502E508@gmail.com> (raw)
In-Reply-To: <mailman.1.1637168401.10503.cerowrt-devel@lists.bufferbloat.net>
I didn't respond to the list...
> Rich Brown <richb.hanover@gmail.com> writes:
>
>>> On Nov 16, 2021, at 12:00 PM, cerowrt-devel-request@lists.bufferbloat.net wrote:
>>>
>>> I've always been kind of a control freak and did manual updates. Are
>>> others confident enough in openwrt's process to use this?
>>>
>>> opkg update; opkg list-upgradable | cut -f 1 -d ' ' | xargs opkg install
>>
>> If that feels scary, then this might really give you the vapors... :-)
>>
>> https://github.com/aparcar/asu#luci-app
>>
>> In a five-out-of-five test, it has worked fine for me!
>> https://youtu.be/H7xcmhbYsX8
>
> Ah, I've been meaning to set this up! Are you using one of the public
> servers, or running your own?
>
In the "Config" tab of luci-app-attendedsysupgrade use https://sysupgrade.openwrt.org
Rich
parent reply other threads:[~2021-11-17 17:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.1.1637168401.10503.cerowrt-devel@lists.bufferbloat.net>]
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=EC4E1AA0-7BD6-4E1F-AE5E-3E8E7502E508@gmail.com \
--to=richb.hanover@gmail.com \
--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