netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Meelis Roos <mroos@linux.ee>
Cc: kernel list <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc))
Date: Wed, 31 May 2006 16:25:10 -0400	[thread overview]
Message-ID: <447DFBA6.1010607@tmr.com> (raw)
In-Reply-To: <Pine.SOC.4.61.0605261532140.26383@math.ut.ee>

Meelis Roos wrote:
>>> Unfortunatlety, 2.6.15 does not boot on this machine so I'm locked out
>>> remotely at the moment.
>>
>> Here it my paranoid boot setup:
> 
> Thanks, but it's not much use here, since the machine is a PReP powerpc 
> machine that can boot one kernel from disk (directly loaded from boot 
> partition, no fancy bootloader) or netboot via serial console for test 
> kernels. However, if the test kernel hangs, it hangs and I would need 
> remote power cycling device that I do not have.
> 
I did a lot of this at one time, and used lilo in just the way 
described. I did have a remote reboot device, however, an operator (1st 
shift), janitor (2nd shift), or security guard (3rd/wkend shift) who had 
been instructed to push the clearly marked reset button on demand "when 
the weird guy in New York tells you."

IBM rack units, like x345 and such, can have an "RSA" card which allows 
remote hardware monitor and reboot with a separate IP address for 
control. Worth its weight in gold! The latest will let you do remote 
console as well.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.

  reply	other threads:[~2006-05-31 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605251004.k4PA4Lek007751@fire-2.osdl.org>
2006-05-25 14:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Andrew Morton
2006-05-25 18:52   ` Patrick McHardy
2006-05-25 19:12     ` Meelis Roos
2006-05-25 20:15     ` Meelis Roos
2006-05-26  7:11     ` Meelis Roos
2006-05-26 12:29       ` Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)) Ingo Oeser
2006-05-26 12:34         ` Meelis Roos
2006-05-31 20:25           ` Bill Davidsen [this message]
2006-05-26 12:42         ` Michael Tokarev
2006-05-26 12:42         ` Andi Kleen
2006-05-26 13:21           ` Ingo Oeser
2006-06-01  7:03     ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Meelis Roos
2006-06-01 17:44       ` Patrick McHardy
2006-06-01 20:50         ` Meelis Roos
2006-06-02 13:08           ` Patrick McHardy
2006-06-02 13:18             ` Meelis Roos
2006-06-02 13:56               ` Patrick McHardy
2006-06-04 12:39                 ` Meelis Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447DFBA6.1010607@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).