Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: edwin <edwin@etorok.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] just when I thought it was safe to do a release
Date: Wed, 19 Feb 2014 22:21:00 +0200	[thread overview]
Message-ID: <5305122C.6070902@etorok.net> (raw)
In-Reply-To: <CAA93jw6+Hib-p2SY2XGQ_90Y=Lg2YJo3rvYcE8_SA3Ozc_qq1g@mail.gmail.com>

On 02/19/2014 06:29 PM, Dave Taht wrote:
> Does anyone care about cups?

Not on the router.

> (printing?)

Yes, but for that I run p910nd on the router and cups itself on my desktop/laptop.
Works well most of the time, I managed to break it occasionally only if I power-cycle the router/printer/laptop in the wrong order, nothing to be concerned about.

> It was one of those things that
> just barely works in the first place due to memory constraints and a PITA
> and I haven't shipped it in a while. Most printers are network capable
> these days, and what I tend to use the usb port for is odd devices
> and gps and the like. I'd like to have support for a 3g modem or two...



> 
> Two concerns of mine are that I killed off udev, which used to manage
> hotplugging. I'd like to know what, if anything, people are using the usb
> for, so as to be able to make sure losing udev doesn't break that...

I have this in /etc/config/p910nd:
config p910nd
        option bidirectional '1'
        option enabled '1'
        option device '/dev/usb/lp0'
        option port '9'

I'm still on 3.7.5-2 though, the 3.10.x builds looked rather experimental and I would not rather run them as my WNDR is my main router.

FWIW these are the packages that I installed on my 3.7.5-2:
kmod-leds-wndr3700-usb
kmod-usb-printer
luci-app-p910nd
p910nd
wifitoggle

Best regards,
--Edwin

  parent reply	other threads:[~2014-02-19 20:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 22:49 Dave Taht
2014-02-19 16:11 ` David Personette
2014-02-19 16:29   ` Dave Taht
2014-02-19 16:38     ` David Personette
2014-02-19 17:01       ` Dave Taht
2014-02-20  5:28       ` Fred Stratton
2014-02-20  9:05         ` Sebastian Moeller
     [not found]           ` <5305E875.9070508@imap.cc>
2014-02-20 11:35             ` Fred Stratton
2014-02-20 13:15               ` Sebastian Moeller
     [not found]                 ` <5306099C.1090604@xyz.am>
2014-02-20 13:57                   ` Fred Stratton
2014-02-20 14:38                     ` Sebastian Moeller
2014-02-20 17:24                       ` Fred Stratton
2014-02-20 20:08                         ` Sebastian Moeller
2014-02-20 20:42                           ` Fred Stratton
2014-02-20 22:18                             ` Sebastian Moeller
2014-02-21 13:12                               ` Rich Brown
2014-02-21 14:17                                 ` Fred Stratton
2014-02-20 17:49                       ` Dave Taht
2014-02-20 18:27                         ` Fred Stratton
2014-02-20 20:09                         ` Sebastian Moeller
2014-02-19 20:21     ` edwin [this message]
2014-02-19 20:32     ` Sebastian Moeller
2014-02-19 20:43       ` Dave Taht
2014-02-19 21:10         ` Sebastian Moeller

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=5305122C.6070902@etorok.net \
    --to=edwin@etorok.net \
    --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