From owner-freebsd-hackers Sat May 31 14:27:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14356 for hackers-outgoing; Sat, 31 May 1997 14:27:52 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14351 for ; Sat, 31 May 1997 14:27:32 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.8.5/8.8.5) with SMTP id OAA05065; Sat, 31 May 1997 14:26:49 -0700 (PDT) X-Authentication-Warning: misery.sdf.com: tom owned process doing -bs Date: Sat, 31 May 1997 14:26:48 -0700 (PDT) From: Tom Samplonius To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: LINT and GENERIC - between a rock and a generic place. In-Reply-To: <9876.865110612@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 31 May 1997, Jordan K. Hubbard wrote: > More and more people are trying to use GENERIC as a template for their > own kernels and they're losing, of course, because generic sets many > limits (like max children or open files) too low. Now that we have login.conf this is pretty much a dead issue isn't it? Why heavily customize the kernel config file, when you can do it with login.conf? In fact the stock login.conf already has a "news" class for news server. I'm already working on removing all the customizations out of my kernel config files, in order to use the more generic login.conf system. Besides the login.conf allows these to be set on a user by user basis. You can't do this with the kernel config. This is real important with dual-use servers. Tom