From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Valdis.Kletnieks@vt.edu
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.36-4 released
Date: Thu, 10 Apr 2014 18:48:20 +0200 [thread overview]
Message-ID: <878urdku5n.fsf@toke.dk> (raw)
In-Reply-To: <5006.1397148038@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Thu, 10 Apr 2014 12:40:38 -0400")
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
Valdis.Kletnieks@vt.edu writes:
> I'd like to at least try to figure out why the sysupgrade path is busted
> before I throw factory.img at it, which will probably wipe out all evidence.
>
> Any hints where to start looking?
You could try manually scp'ing the image over and running sysupgrade via
the command line?
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2014-04-10 16:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 6:45 Dave Taht
2014-04-10 6:46 ` Dave Taht
2014-04-10 17:33 ` Dave Taht
2014-04-11 18:25 ` Jim Gettys
2014-04-10 13:48 ` Valdis.Kletnieks
2014-04-10 14:06 ` Robert Bradley
2014-04-10 14:32 ` Toke Høiland-Jørgensen
2014-04-10 15:18 ` Robert Bradley
2014-04-10 15:21 ` Toke Høiland-Jørgensen
2014-04-10 17:29 ` Dave Taht
2014-04-10 17:57 ` Toke Høiland-Jørgensen
2014-04-10 19:06 ` Sebastian Moeller
2014-04-11 12:34 ` Robert Bradley
2014-04-10 16:40 ` Valdis.Kletnieks
2014-04-10 16:48 ` Toke Høiland-Jørgensen [this message]
2014-04-10 16:51 ` Valdis.Kletnieks
2014-04-10 16:54 ` Toke Høiland-Jørgensen
2014-04-10 18:02 ` Sebastian Moeller
2014-04-13 0:22 ` Jim Reisert AD1C
2014-04-13 0:30 ` Sebastian Moeller
2014-04-13 0:44 ` Jim Reisert AD1C
2014-04-10 16:46 ` Jim Gettys
2014-04-10 17:31 ` Dave Taht
2014-04-10 17:35 ` Jim Gettys
2014-04-11 9:50 ` David Personette
2014-04-11 10:43 ` Aaron Wood
2014-04-12 11:45 ` Neil Shepperd
2014-04-12 19:04 ` Dave Taht
[not found] ` <CANp2as81TR_kCR8a_sZs045tXFGADL1W4CFtNEJiJrjutmL7cg@mail.gmail.com>
2014-04-11 16:31 ` 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=878urdku5n.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Valdis.Kletnieks@vt.edu \
--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