From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KvgTH-00014a-TB for garchives@archives.gentoo.org; Thu, 30 Oct 2008 22:58:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A3D5BE007A; Thu, 30 Oct 2008 22:58:31 +0000 (UTC) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 75CF9E007A for ; Thu, 30 Oct 2008 22:58:31 +0000 (UTC) Received: by wf-out-1314.google.com with SMTP id 29so873222wff.10 for ; Thu, 30 Oct 2008 15:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=b525D29bWL9QA5KWogO2jmy2UDt36sbPEZmRUaT+uXc=; b=tHUQ/jQmMSDziwKblpckQRiLtM5CVAgCse2p9ugMMt8Kct6a+g4jX/ml4RLbk24cDl DaC6ideehO/mSiixTour6zMojPbnCL/sPkYoEsbABJYTei2DrZ936OlZ4qtwdu9CcmVT +ruXM/1nOPIBS+Fs+M64dyn3YU2G0WURfXgc0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nAX1PY4dwavUX6lhOFpGWa3y2+sauubkSfx7WXlOC7lVxQofYjEEeY6N6zqMyyUbWr gQxpZw91zgrrdI4zUOkMBu07An9q5BKlmhXxfM5z88M+SNFTFk6wPo3CKYo3ZfGBdcqi Ja+QfWzU0dywabm0lUi+aT+v5LSBV83hEypTQ= Received: by 10.142.191.10 with SMTP id o10mr5015632wff.163.1225407509726; Thu, 30 Oct 2008 15:58:29 -0700 (PDT) Received: by 10.142.215.15 with HTTP; Thu, 30 Oct 2008 15:58:29 -0700 (PDT) Message-ID: <5bdc1c8b0810301558m5d7517f7g24d93332590a826c@mail.gmail.com> Date: Thu, 30 Oct 2008 15:58:29 -0700 From: "Mark Knecht" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] blocks to fix In-Reply-To: <756879.4765.qm@web65415.mail.ac4.yahoo.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5bdc1c8b0810281934y6b4370al84f174a1d11f6b87@mail.gmail.com> <20081029204913.53c484ff@digimed.co.uk> <5bdc1c8b0810291446i2492363v37824c167838b0d@mail.gmail.com> <200810302144.56446.wonko@wonkology.org> <756879.4765.qm@web65415.mail.ac4.yahoo.com> X-Archives-Salt: 66a46acc-be80-40dc-8dc1-fdf79267af7a X-Archives-Hash: d41fea3ca5ca1f6a7c8567724990271c Good ideas all. Thanks. I can do some work setting things up and then not test it until I have my dad sitting in front of the machine. He can hit Ctrl-D. We've seen that one before. Cheers, Mark On Thu, Oct 30, 2008 at 3:12 PM, BRM wrote: > That might work for some scenerios; however, it wouldn't likely for the recent e2fsprogs-lib/ss/com_err fiasco because the booting system would be unable to execute mount and wait until the user either entered the root password for maintenance mode or pressed "CTRL+D" to continue. (Yep, I hosed one of my systems over that issue!) So the system would not be either in a kernel panic nor able to run /etc/conf.d/local.start. So it wouldn't reboot without user intervention. > > In most cases that would likely work though. > > Ben > > > > ----- Original Message ---- > From: Alex Schuster > To: gentoo-user@lists.gentoo.org > Sent: Thursday, October 30, 2008 4:44:53 PM > Subject: Re: [gentoo-user] blocks to fix > > Mark Knecht writes: > >> Having a second install is a reasonable idea. I suppose I can probably >> install that remotely but I cannot test it remotely (AFAIK) without >> someone handy to choose the right line in the grub menu... > > You can use the grub-set-default command to boot another than the default > entry: > > default saved > fallback 0 > ... > title System A > kernel (hd0,0)/A > > title System B > kernel (hd0,1)/B > > > System A is your default system. When you have installed B, activate the 2nd > entry with "grub-set-default 1" (grub counts from 0). Put something > like "sleep 600 & reboot" into B's /etc/conf.d/local.start that will make > it reboot after a while, unless you are able to log in from remote and kill > the sleep command. > Now reboot. B will be started. Try to log in. If it fails, wait a little, > and try again. This time A should be up again. > > Unless you have a kernel panic, and the system is just halted. Does anyone > know if there is something one could do about that? > > Wonko > >