Date: Fri, 13 Sep 2002 14:47:01 -0400 From: Alan E <alane@geeksrus.net> To: Jeremy Lea <reg@FreeBSD.ORG> Cc: FreeBSD Ports List <ports@FreeBSD.ORG>, FreeBSD Gnome Team <gnome@FreeBSD.ORG> Subject: Re: fork bombs registering packages using GNOMENG Message-ID: <20020913184701.GA75702@wwweasel.geeksrus.net> In-Reply-To: <20020913175115.GA90567@shale.csir.co.za> References: <20020913173752.GA53609@wwweasel.geeksrus.net> <20020913175115.GA90567@shale.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 13, 2002 at 07:51:15PM +0200, Jeremy Lea wrote: >Hi, > >On Fri, Sep 13, 2002 at 01:37:52PM -0400, Alan E wrote: >> If you set USE_GNOME on the make command line, > >And if you hold down the power button it turns the whole machine off... >What's your point? I fail to see the analogy. If setting USE_GNOME (it was an attempt to get rid of esound) on the command line is going to have such catastrophic results, then bsd.gnomeng.mk ought to detect it and stop the make and issue a diagnostic message indicating that what you've done is wrong. I don't think it is reasonable that something as innocuous as attempting to override a variable on the make command line can bring the machine to its knees (although, to its credit, the kernel did not fall over). Personally, I thik a fork bomb coming out of a port make for *any* reason whatsoever is indicative of a severe design or implementation error. It just should *not* happen. -- Alan Eldridge Unix/C(++) IT Pro, 20 yrs, seeking new employment. (http://wwweasel.geeksrus.net/~alane/resume.txt) KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020913184701.GA75702>