All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: BenH <bh40@calva.net>
Cc: Dan Bethe <dan_bethe@yahoo.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: the state of the linuxppc-dev community
Date: Wed, 09 Feb 2000 18:19:27 +0100	[thread overview]
Message-ID: <200002091719.SAA23840@appel.flower> (raw)


BenH writes:

>  - The primary source for the "current" up-to-date kernel source tree for
> powermac
>    is Paul Mackerras rsync tree. It can be retreived with rsync:
>
>       rsync -arvz linucare.com.au::linux-pmac-stable <dest_dir>
>
>    This tree contains all the latest fixes, features, etc... as long as
> they are
>    considered stable.

Similarly, I heard some time ago, that

    rsync -auvz linuxcare.com.au::linux-pmac-devel <dest_dir>

would give me a fairly recent development (2.3.x) kernel.
Jan 14, and Feb 1, I succeeded in building a kernel (2.3.39) from that,
jippie!  But since then, I'm getting silly permission errors:

    [root@appel linux]# rsync -auvz linuxcare.com.au::linux-pmac-devel .
    Welcome to the Linuxcare Australia rsync server
    For information about Linuxcare see http://linuxcare.com.au/

    receiving file list ... done
    ./
    arch/ppc/
    send_files failed to open Documentation/kernel-docs.txt: Permission denied
    send_files failed to open Documentation/sound/NM256: Permission denied
    wrote 123 bytes  read 110685 bytes  4345.41 bytes/sec
    total size is 71388166  speedup is 644.25

Greetings,

Jan.

--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-02-09 17:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-09 17:19 Jan Nieuwenhuizen [this message]
     [not found] <20000209100229.B5973@linuxcare.com>
2000-02-09 20:04 ` the state of the linuxppc-dev community Michael Schmitz
2000-02-09 22:14 ` Tom Rini
     [not found] <20000209014216.17047.qmail@web1001.mail.yahoo.com>
2000-02-09  9:22 ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2000-02-09  1:35 Dan Bethe
     [not found] <20000208233505.29535.qmail@web1003.mail.yahoo.com>
2000-02-09  0:09 ` Tom Rini
2000-02-09 11:30 ` Michael Schmitz
2000-02-08 23:37 Dan Bethe
2000-02-09  0:13 ` Tony Mantler
2000-02-09  0:26   ` Tom Rini
2000-02-09  0:46     ` Larry McVoy
2000-02-09  0:51       ` Tom Rini
2000-02-09  1:02         ` Larry McVoy

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=200002091719.SAA23840@appel.flower \
    --to=janneke@gnu.org \
    --cc=bh40@calva.net \
    --cc=dan_bethe@yahoo.com \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.