From: Sumeet Singh Parmar <sparmar@veraznet.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ideal router distribution
Date: Sat, 15 Nov 2003 02:36:29 +0000 [thread overview]
Message-ID: <marc-lartc-106886394702054@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
I have acquired a dual 10/100 intel nic for my router (yay!). I have a
question: What would characterise the ideal distribution for router + mini
file server sort of work? Personally I use gentoo and I like it because I
can take advantage of constantly updating s/w packages by compiling from
source.
However for a router, I think one would want a stable, secure/hardened
distribution that handles patches well and any changes to kernel and/or
packages can be rolled back in case an upgrade goes wrong.
Any advice/suggestion is most appreciated!
Thanks a lot!!
-Sumeet
ps I don't know if someone has experimented with a back-up system images
i.e. an initrd based system, so the root fs is always in the initrd and an
upgrade is a matter of swapping out kernel and/or initrd image?
[-- Attachment #2: Type: text/html, Size: 1253 bytes --]
next reply other threads:[~2003-11-15 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 2:36 Sumeet Singh Parmar [this message]
2003-11-15 10:47 ` [LARTC] ideal router distribution Stef Coene
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=marc-lartc-106886394702054@msgid-missing \
--to=sparmar@veraznet.com \
--cc=lartc@vger.kernel.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