From: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
To: gentoo-user@lists.gentoo.org
Cc: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Subject: [gentoo-user] Re: new linux router
Date: Fri, 6 Mar 2015 12:29:58 +0100 [thread overview]
Message-ID: <20150306112958.GB2459@vidovic.ultras.lan> (raw)
In-Reply-To: <loom.20150306T021214-849@post.gmane.org>
On Fri, Mar 06, 2015 at 02:03:48AM +0000, James wrote:
> > For the distribution, I'd recommend Alpine:
> > http://www.alpinelinux.org/about
>
> Why would that be better than putting lilblue (gentoo) on
> the board. Maybe somebody who has success with booting off
> of usb (and that definitely is not me) could test lilblue
> on an alix2d3 board?
I don't know much Lilblue but it looks like a somewhat recent project.
Alpine started back in 2005. It's based on portage to build the
distribution but uses the apk-tools that fit better for embedded
systems, IMHO.
Also, Alpine comes with a very lightweight minimal installation,
reliable toolchain to build the distribution and uses openrc. The well
known debian-like configuration files allow new maintainers to quickly
be comfortable with the device.
The recent move to musl over uClibc is a good thing too, FMPOV.
I expect Alpine to have a wider community than Lilblue.
> How did you have your make.conf files (or similar under Alpine) set up?
You don't have make.conf on the target. Embedded devices are bad at
compiling. With Alpine, you cross-compile the target from your
desktop/server/VM.
> If I go this route, I'd really rather run gentoo or something
> quite similar, rather than a distro I not familiar with.
On the target device, apk-tools are very easy to use and requires MUCH
less time/ressources than emerge.
Quiet frankly, Alpine doesn't require specific skills. I've started with
the binary provided by the maintainers and never had to compile any
package myself.
> > That's the combo I used in a recent past and it worked quiet fine
> > (802.1q VLAN, traffic shaping with tc, advanced firewall with scripted
> > iptables rules, ethernet cards controlled with ethtool (I could fix
> > speed/duplex for incompatible network hardware), ssh, etc).
>
> I'm not familiar with Alpine linux. How many of your scripts would be
> useful on gentoo? If what you did is sensitive, just drop to me privately.....
Sorry, I can't. I don't have them anymore while I'm sure they are still
used in production.
It's something easy to do, though. The scripts themselves are
distribution agnostic. E.g. my ipfilter service only used $IPTABLES. The
only thing to update are the service files for openrc, systemd, upstart,
whatever.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2015-03-06 11:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 15:10 [gentoo-user] new linux router James
2015-03-04 16:18 ` whytlze
2015-03-04 21:10 ` [gentoo-user] " James
2015-03-04 20:37 ` [gentoo-user] " Bruce Schultz
2015-03-04 21:24 ` [gentoo-user] " James
2015-03-05 1:12 ` Bruce Schultz
2015-03-05 4:21 ` James
2015-03-05 18:59 ` Nicolas Sebrecht
2015-03-06 2:03 ` James
2015-03-06 8:02 ` Neil Bothwick
2015-03-06 17:37 ` James
2015-03-06 21:55 ` Neil Bothwick
2015-03-07 17:31 ` James
2015-03-08 17:08 ` Neil Bothwick
2015-03-06 11:29 ` Nicolas Sebrecht [this message]
2015-03-06 17:01 ` James
2015-03-28 18:57 ` lee
2015-03-07 9:37 ` [gentoo-user] " thegeezer
2015-03-07 10:16 ` Marc Stuermer
2015-03-12 15:51 ` [gentoo-user] " Hans
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150306112958.GB2459@vidovic.ultras.lan \
--to=nicolas.s-dev@laposte.net \
--cc=gentoo-user@lists.gentoo.org \
/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