From owner-freebsd-stable@FreeBSD.ORG Wed Dec 21 21:40:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 EB6B716A433 for ; Wed, 21 Dec 2005 21:40:46 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 8A8FD43D60 for ; Wed, 21 Dec 2005 21:40:35 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 35064 invoked by uid 399); 21 Dec 2005 21:12:07 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 21 Dec 2005 21:12:07 -0000 Message-ID: <43A9C51F.5040408@FreeBSD.org> Date: Wed, 21 Dec 2005 13:11:59 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: "O. Hartmann" References: <43A98E89.9060205@mail.uni-mainz.de> In-Reply-To: <43A98E89.9060205@mail.uni-mainz.de> Content-Type: multipart/mixed; boundary="------------090405070104090301020007" Cc: freebsd-stable Subject: Re: FreeBSD6.0-STABLE got wicked up since today's cvsupdate (Xorg/X11, USB) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2005 21:40:47 -0000 This is a multi-part message in MIME format. --------------090405070104090301020007 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit O. Hartmann wrote: > Hello. > I did today (21st December) the last cvsupdate (did yesterday cvsupdate > before) with a lot of new entries in /etc/rc.d. > Since then I ran into massif problems with X11. I use the lastes Xorg > stuff from the ports, only for your information. I'm sorry that you're having these problems. It's not very likely that the rc changes caused this problem, but it's worth exploring. I need you to do two things. First, copy /etc/rc to a convenient directory, and then apply the attached patch. DON'T patch /etc/rc, or your system won't boot. :) Then run '/bin/sh rc'. This should generate 3 files, rc.early[12] and rc.late. If the rc.early files are different (they should not be) then please send them both. Otherwise, please send one of the rc.early files and the rc.late file. Second, please enable console logging in /etc/syslog.conf, if you have not already. You should have a line in there that looks like this, without the comment at the front: console.info /var/log/console.log Then do 'touch /var/log/console.log', reboot, and send that log together with the files created by the patched rc above. Thanks, Doug -- This .signature sanitized for your protection --------------090405070104090301020007 Content-Type: text/plain; name="rc-debug.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="rc-debug.diff" --- r6/src/etc/rc Tue Dec 20 23:11:33 2005 +++ rc Wed Dec 21 11:18:34 2005 @@ -81,7 +43,8 @@ files=`rcorder ${skip} /etc/rc.d/* 2>/dev/null` for _rc_elem in ${files}; do - run_rc_script ${_rc_elem} ${_boot} + #run_rc_script ${_rc_elem} ${_boot} + echo $_rc_elem >> rc.early1 case "$_rc_elem" in */${early_late_divider}) break ;; @@ -102,14 +65,18 @@ _skip_early=1 for _rc_elem in ${files}; do case "$_skip_early" in - 1) case "$_rc_elem" in + 1) + echo $_rc_elem >> rc.early2 + + case "$_rc_elem" in */${early_late_divider}) _skip_early=0 ;; esac continue ;; esac - run_rc_script ${_rc_elem} ${_boot} + echo $_rc_elem >> rc.late + #run_rc_script ${_rc_elem} ${_boot} done echo '' --------------090405070104090301020007--