Things to remove from /rescue

[David O'Brien]

On Mon, Jul 21, 2003 at 03:15:53PM -0400, John Baldwin wrote:
> 
> On 19-Jul-2003 David O'Brien wrote:
> > On Thu, Jul 17, 2003 at 02:51:47PM -0400, John Baldwin wrote:
> >> 
> >> On 17-Jul-2003 David O'Brien wrote:
> >> > On Thu, Jul 17, 2003 at 09:17:00AM -0700, Luigi Rizzo wrote:
> >> >> whatever it is, certainly the purpose is not to show how good
> >> >> a sysadmin is in using a knife's blade as a screwdriver and a fork
> >> >> and a spoon. Heck, even swiss army knives have these extra
> >> >> tools.
> >> >> 
> >> >> I think that if something in /rescue can make the task faster
> >> >> and less error prone, removing it to save 10-50k of disk space
> >> >> would be a big mistake.
> >> > 
> >> > You must not have seen my other email that listed other things than just
> >> > disk space.  If I did need to get to the Internet to get bits, what does
> >> > ipfw do for me that "sysctl net.inet.ip.fw.enable=0" doesn't?
> >> 
> >> This doesn't handle ipfilter.  You've conveniently ignored that point it
> >> seems.
> > 
> > No, I have little ipfilter experience so I didn't speak to it.  My
> > language explicitly mentioned ipfw so I assumed readers would understand
> > I was only addressing ipfw in that email.
> 
> You've listed ipfilter tools such as ipnat, etc. on your list, so you
> have "spoken to it".  Perhaps you shouldn't blindly remove tools if
> you don't know how they work?

You seem to have another email in mind than the one you've been replying
to.  Please answer the question asked:

    If I did need to get to the Internet to get bits, what does ipfw do
    for me that "sysctl net.inet.ip.fw.enable=0" doesn't?

the reader should assume the user is using ipfw and not another packet
filter.

-- 
-- David  (obrien at FreeBSD.org)