linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stephen R Marenka <stephen@marenka.net>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Tom Rini <trini@kernel.crashing.org>,
	benh@kernel.crashing.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Crash on BenH's latest rsync (2.4.6-pre3)
Date: Wed, 27 Jun 2001 11:25:42 -0500	[thread overview]
Message-ID: <20010627112542.A486@marenka.net> (raw)
In-Reply-To: <20010626173123.13f2b3bf.toe@unlserve.unl.edu>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

On Tue, Jun 26, 2001 at 05:31:23PM -0500, Takashi Oe wrote:
> 
> On Tue, 26 Jun 2001 15:13:46 -0700, Tom Rini wrote:
> 
> > On Tue, Jun 26, 2001 at 04:29:13PM -0500, Takashi Oe wrote:
> >
> > > BootX support on your rsync tree and linuxppc_2_4_devel tree is
> > > broken.  I guess no one with BootX bothered to try
> > > linuxppc_2_4_devel..
> >
> > Does this work as well?
> 
> It sure does, though we might as well do:
> 
> 	if (boot_infos) {
> 		_machine = _MACH_Pmac;
> 		relocate_nodes();
> 	}
> 
> or similar as calling intuit_machine_type() is silly on BootX ;)

If I understand correctly, this failed for me because this causes 
relocate_nodes to get called again if have_of.

The following does work for me.

 	if (boot_infos) {
 		_machine = _MACH_Pmac;
                if ( !have_of )
 		    relocate_nodes();
 	}

Thanks,

Stephen

-- 
Stephen R. Marenka     If life's not fun, you're not doing it right!
<stephen@marenka.net>

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

      parent reply	other threads:[~2001-06-27 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 20:29 Crash on BenH's latest rsync (2.4.6-pre3) Michel Lanners
2001-06-26 19:10 ` Tom Rini
2001-06-26 20:38   ` Michel Lanners
2001-06-26 20:51   ` Benjamin Herrenschmidt
2001-06-26 21:29     ` Takashi Oe
2001-06-26 22:13       ` Tom Rini
2001-06-26 22:31         ` Takashi Oe
2001-06-26 22:43           ` Tom Rini
2001-06-27 16:25           ` Stephen R Marenka [this message]

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=20010627112542.A486@marenka.net \
    --to=stephen@marenka.net \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    --cc=trini@kernel.crashing.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).