Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] lighttpd.conf error in cerowrt-3.10.50-1
Date: Tue, 29 Jul 2014 08:04:42 -0600	[thread overview]
Message-ID: <CAK-n8j7OnHhHa-EuUArCgLRXCWgi0Bj+-cgNMB_yMHVvT-s8Gw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5D+bLyUSVYDFuwAYzXhmhGicawxRJMebHNGmxxdO2OSQ@mail.gmail.com>

On Mon, Jul 28, 2014 at 10:12 PM, Dave Taht <dave.taht@gmail.com> wrote:

> I cut a new version of 3.10.50-1 just now.

Thanks for fixing this so quickly.

> those of you with the old version can either comment out simple_vhost
> or do an
> opkg update; opkg install lighttpd-mod-simple-vhost
> on your existing install.

I could not do the latter, got this error:

root@cerowrt:~# opkg update; opkg install lighttpd-mod-simple-vhost
Downloading http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.36-4/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/toronto.
Unknown package 'lighttpd-mod-simple-vhost'.
Collected errors:
 * opkg_install_cmd: Cannot install package lighttpd-mod-simple-vhost.

(was it supposed to be '_' instead of '-' characters?)

So I modified the lighttpd.conf file instead.  This allowed me to
reboot and get to the GUI to re-flash with the new version of
3.10.50-1

NOTE:  If you modify lighttpd.conf then re-flash, mod_simple_vhost
will *still* be commented out after re-flashing.  You will have to
edit the file again to undo the change, then reboot.

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

      parent reply	other threads:[~2014-07-29 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  3:55 Will Strang
2014-07-29  4:12 ` Dave Taht
2014-07-29  4:53   ` Will Strang
2014-07-29 14:04   ` Jim Reisert AD1C [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

  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=CAK-n8j7OnHhHa-EuUArCgLRXCWgi0Bj+-cgNMB_yMHVvT-s8Gw@mail.gmail.com \
    --to=jjreisert@alum.mit.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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