Date: Thu, 17 Jul 2003 09:41:02 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Luigi Rizzo <rizzo@icir.org> Cc: freebsd-arch@freebsd.org Subject: Re: Things to remove from /rescue Message-ID: <20030717164102.GA47198@dragon.nuxi.com> In-Reply-To: <20030717091700.B2145@xorpc.icir.org> References: <20030717080805.GA98878@dragon.nuxi.com> <p05210671bb3c1bf6b8fd@[128.113.24.47]> <20030717033620.B51802@xorpc.icir.org> <200307170906.51902.jhb@FreeBSD.org> <20030717160942.GB46923@dragon.nuxi.com> <20030717091700.B2145@xorpc.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? If I'm repairing /, I'm not running services for someone to break into -- not to mention your system is so FUBAR if you're repairing /, maybe the attacker would take pity on you and fix things for you (for the simple price of storing some juarez for him). ;-) -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717164102.GA47198>