From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 23:36:14 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B39D916A4CF for ; Fri, 11 Mar 2005 23:36:14 +0000 (GMT) Received: from smtp810.mail.sc5.yahoo.com (smtp810.mail.sc5.yahoo.com [66.163.170.80]) by mx1.FreeBSD.org (Postfix) with SMTP id AAB4043D55 for ; Fri, 11 Mar 2005 23:36:13 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noacks@swbell.net@70.240.225.210 with login) by smtp810.mail.sc5.yahoo.com with SMTP; 11 Mar 2005 23:36:13 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 4AFE261AD; Fri, 11 Mar 2005 17:36:12 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 77666-11; Fri, 11 Mar 2005 17:36:09 -0600 (CST) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 5CAAA60CF; Fri, 11 Mar 2005 17:36:09 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.3/8.13.3) with ESMTP id j2BNa8SN012827; Fri, 11 Mar 2005 17:36:08 -0600 (CST) (envelope-from noackjr@alumni.rice.edu) Message-ID: <42322B68.7050008@alumni.rice.edu> Date: Fri, 11 Mar 2005 17:36:08 -0600 From: Jon Noack User-Agent: Mozilla Thunderbird 1.0 (X11/20050202) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bashar References: <422F250B.6030505@kuwaitnet.net> <20050309234141.L53915@carver.gumbysoft.com> <423040FE.8090305@kuwaitnet.net> <20050310225201.Y64217@carver.gumbysoft.com> <42324A79.6070302@kuwaitnet.net> <4231EE30.6010405@alumni.rice.edu> <4232142C.40407@kuwaitnet.net> In-Reply-To: <4232142C.40407@kuwaitnet.net> Content-Type: text/plain; charset=windows-1256; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at noacks.org cc: freebsd-stable@freebsd.org Subject: Re: from 5.4-PRERELEASE -> 5.3-RELEASE-p5 error? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2005 23:36:14 -0000 On 03/11/05 15:57, Bashar wrote: > Jon Noack wrote: >> Bashar wrote: >>> Doug White wrote: >>>> On Thu, 10 Mar 2005, Bashar wrote: >>>>> Doug White wrote: >>>>>> On Wed, 9 Mar 2005, Bashar wrote: >>>>>>> Hello, >>>>>>> i was wondering just right after the downgrade been facing some >>>>>>> issues >>>>>>> such as: >>>>>>> 1. server# /usr/local/bin/strace -f ps >>>>>>> PIOCSFL: Inappropriate ioctl for device >>>>>>> trouble opening proc file >>>>>>> 2. mounting ext2fs partition doesn't work unless i specify -ro or it >>>>>>> will give operation not permitted. >>>>>>> >>>>>>> any idea what might be causing this? >>>>>> >>>>>> How did you perform the downgrade? The strace error looks like you're >>>>>> still running the 5.3-STABLE binary. >>>>> >>>>> first i ran RELENG_5 and when i got the 5.4-PRERELEASE (which >>>>> incompatible with cPanel.net software) i had to run cvsup with >>>>> RELENG_5_3 >>>>> after than i started getting those errors >>>> >>>> You're leaving out important details, like what you did after you >>>> cvsup'd. >>> >>> the usual ,cvsup'ed then cd /usr/src && make buildworld && make >>> installworld && cd /sys/i386/conf && config mykernel && cd >>> ../compile/mykernel && make depend && make && make install && reboot >> >> This is the usual? You should read >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html#AEN27432 >> and /usr/src/UPDATING. >> >> The Canonical Way to Update Your System (for 5.x): >> 1) make buildworld >> 2) make buildkernel KERNCONF=YOUR_KERNEL_HERE >> 3) make installkernel KERNCONF=YOUR_KERNEL_HERE >> 4) >> 5) /etc/rc.d/preseedrandom >> 6) mergemaster -p >> 7) make installworld >> 8) mergemaster >> 9) > > Cant do this for remote system as you know I was merely pointing out what was the official take on "the usual". The general consensus for remote systems is to replace steps 4 and 5 with "shut down as many services as possible". This has never failed me for minor updates, but caution is advised for major ones. Jon