Date: Wed, 4 Apr 2001 12:16:43 -0400 (EDT) From: Chet Hosey <chosey@nidhog.com> To: "Drew J. Weaver" <drew.weaver@thenap.com> Cc: "'freebsd-isp@freebsd.org'" <freebsd-isp@FreeBSD.ORG> Subject: OT: RE: Chasing the kiddies (was: Named Keep crashing) Message-ID: <Pine.BSF.4.31.0104041207590.32350-100000@web1.nidhog.com> In-Reply-To: <B1A7D9973EBED3119ADD009027DC8649180F7F@mailman.thenap.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From what I've seen, RH has GUI tools for a lot of things (Linuxconf, I think?). RH seems much simpler to run (as an end user) than FreeBSD. You can download RPMs for everything, including the kernel. I know RedHat users who've never touched gcc. Even using ports requires slightly more knowledge than "Using Netscape, download coolproggie.rpm, open an xterm, and run rpm -i coolproggie.rpm". Under Debian, upgrading Bind for the security fix is a matter of "apt-get update; apt-get install bind". Hell, upgrading *everything*, system libs, init, X, name-your-vi-clone, emacs, bind, lynx, etc., is just "apt-get update; apt-get dist-upgrade". The RedHat way of doing things allows one to avoid understanding. It seems that FreeBSD allows less ignorance. ________________________________________________________________________ Chet Hosey <chosey@nidhog.com> ________________________________________________________________________ On Wed, 4 Apr 2001, Drew J. Weaver wrote: > Just an off topic note here, FreeBSD, BSDi/OS and RedHat are all of > equal "difficulty" to administer, I run all 3 and none of them make me > shiver in my boots. Not sure what point you're attempting to make here? > > --- quoth the raven, --- > > Everybody should start with a *nix running on a publicly accessable box. > (Note: Linux doesn't count here, except possibly really old versions of > Slackware. Damned RH makes things too easy. No X either - CLI, people!) > > ________________________________________________________________________ > > Chet Hosey > <chosey@nidhog.com> > ________________________________________________________________________ > > On Wed, 4 Apr 2001, Bill Vermillion wrote: > > > On Wed, Apr 04, 2001 at 05:45:48PM +1000, Enno Davids thus spoke: > > > > > | > Is there any way to trace who is doing it? | > Running tcpdump > > > with certain filter settings to avoid logging everything and > > > filling the disk? > > > > > > > | Dont bother... Just install the fixed version of bind... > > > | Every kid with a script and an internet connection is probably > > > | doing this to you!!! > > > > > This response kind of bothers me. There was a time > > > when everytime I could sanely trace spammers I emailed > > > abuse@wherever.was.relevant to advise them. Similarly, when people > > > probed Apache I'd send off adivsory emails. > > > > If you find a way this works let me know. I've given up doing this > > because except for the most well known, I've received rejects from > > all mail addresses at the offending provider, root,abuse, > > postmaster, webmaster, etc. So I just gave up and put the in > > the REJECT list. > > > > Those days responsible people, and not quick buck artists, we're > > keeping the 'net running. > > > > > There was a time when if you probed the Apache on my machine it > > > winnuke'd you back. Moral issues aside, there _was_ a great deal > > > of satisfaction there... Needless to say, there's little mileage > > > in this now (damned M$ service packs!). :) > > > > I never was into 'revenge' or 'tit-for-tat'. > > > > Bill > > -- > > Bill Vermillion - bv @ wjv . com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0104041207590.32350-100000>