public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Øyvind Vågen Jægtnes" <lorrides@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Routing 600+ vlan's via linux problems (looks like arp problems)
Date: Fri, 4 May 2007 22:27:07 +0200	[thread overview]
Message-ID: <20070504202707.GE943@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.61.0705040947170.18504@yvahk01.tjqt.qr>

Hi Jan,

On Fri, May 04, 2007 at 09:53:31AM +0200, Jan Engelhardt wrote:
> 
> On May 4 2007 02:11, Willy Tarreau wrote:
> >> 
> >> Haha. Would you be happy if it ran on a CF card instead? :>
> >
> >Yes, because at least when you design a system to run on a CF card, you
> >ensure never to write on it because you know that would kill it. Then
> >since you never write on it, it does not wear out and has no problem
> >running for years (unless you bought cheap end-user CF of course).
> 
> Funny, I just installed a 'full' Linux distro on a CF, like with a
> regular harddisk, and it runs in full rw mode. Packing it up in a
> squashfs and running the thing with aufs did not seem worth
> the hassle of setting up a specialized initrd. And then, when you
> need to make one change (firewall), it's faster than recreating the
> sqfs image.
> Will see how it long that lasts.

This is acceptable for a single machine. I do have something similar
(though mostly read-only and with home dirs on NFS) at home as an
always-on browser. But managing a lot of remote machines that way is
often a difficult work, and the risk of losing remote machines increases
with the number of machines, the frequency of updates and the write
rates on the flash.

Packaging an easily upgradable and remotely testable system really
is worth it even for a few tens of machines.

Cheers,
Willy


  reply	other threads:[~2007-05-04 20:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 20:25 Routing 600+ vlan's via linux problems (looks like arp problems) Øyvind Vågen Jægtnes
2007-05-03 20:34 ` Jan Engelhardt
2007-05-03 20:53 ` Willy Tarreau
2007-05-03 20:55   ` Willy Tarreau
2007-05-03 20:55   ` Jan Engelhardt
2007-05-03 21:12     ` Øyvind Vågen Jægtnes
2007-05-03 22:23       ` Willy Tarreau
2007-05-03 22:50         ` Jan Engelhardt
2007-05-04  0:11           ` Willy Tarreau
2007-05-04  7:53             ` Jan Engelhardt
2007-05-04 20:27               ` Willy Tarreau [this message]
2007-05-04  3:48         ` Øyvind Vågen Jægtnes
2007-05-04  5:30           ` Willy Tarreau
2007-05-04  7:08           ` Miquel van Smoorenburg
2007-05-04  8:28             ` Andi Kleen
2007-05-04  8:05           ` Jan Engelhardt
2007-05-03 20:53 ` Sam Ravnborg
2007-05-03 21:38   ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2007-05-04 14:02 Paul Slootman

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=20070504202707.GE943@1wt.eu \
    --to=w@1wt.eu \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorrides@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