From owner-freebsd-stable Sat Dec 29 11:23:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (clmboh1-smtp3.columbus.rr.com [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id 2D69037B405 for ; Sat, 29 Dec 2001 11:23:38 -0800 (PST) Received: from potentialtech.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id fBTJIrg10322; Sat, 29 Dec 2001 14:18:53 -0500 (EST) Message-ID: <3C2E18EE.5060902@potentialtech.com> Date: Sat, 29 Dec 2001 14:26:38 -0500 From: Bill Moran Organization: Potential Technology User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Bernie Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.5-PRERELEASE -- Pobs in compiling custom kernel References: <20011229185029.Y3777-100000@> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernie wrote: > 1. Is this the right list for this kind of stuff? or should i post in > freebsd-questions instead? Not unless you've determined that it only occurs with -STABLE. Otherwise, you should post to freebsd-questions. > 2. Is it ok to send attachment on lists? i have captured the stdout and > stderr of make (for the custom kernel) in different files. Can i send them > to the list togrther with the kernel config file? That's not good practice. Post snippits of the output that you think are important, and if someone asks you for the entire capture, send it to that person only. Sending large messages to the list will generally not be received well. > Thanx a lot. Thanks for being curteous enough to check before posting :) -- Bill Moran Potential Technology http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message