I'm basically building my own base.tgz.  Maybe once I have that smoothed out
I'll start thinking about router-specific configuration options as defaults
(maybe in etc.tgz?), but for now I just need to slim things down.

The biggest problem I'm seeing is that base.tgz is excessive for what I
need.  I'm just going around removing things I don't think I need.

Things I need that aren't in base: 
   gated, sshd

Things i don't need that are in base:
   most of /usr/libexec
   half of /bin, /sbin/, /usr/bin, /usr/sbin (maybe more)
   a ton of stuff in /usr/share

Then there are other things that would be nice like 3rd party monitoring
tools.

Starting from a stripped down, secure base.tgz we be sweet.

I'm trying to slim everything down to fit on a 20MB flash IDE disk.

EJR


On Tue, 18 May 1999, Jonathan Stone wrote:

> 
> >I'm putting together a tarball for a less-than-10MB NetBSD base installation
> >so I can use it in routers and stuff.
> 
> Sounds like a cool idea.  Thor Lancelot Simon did a lot of work to put
> together a `secure' distribution (readonly root, securelevels, etc)
> which may also be applicable to an `exposed' machine like a router.
> But how did you intend to put this `distribution' together?
> If you could do it as a subset of `base', that'd be neat; a `router'
> distribution could get rebuilt automagically.
> 
> There's also an ongoing project to pkg-ize the existing sets. So the
> very best thing would be to get in touch with Jim Wise and the people
> on tech-install who are woring on this.  Ideally, a `router'
> configuration would become a pkg-ized subset of a normal distribution;
> maybe even a standard install-time option.
> 
> >If anybody else is working on or has already done this, and would like to
> >coordinate with me, please let me know!
> 
> Hope the above helps.
>