public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: Sungem with iMac Rev-B
Date: Sun, 28 Apr 2002 19:05:17 -0800	[thread overview]
Message-ID: <20020428190517.H21791@plato.local.lan> (raw)
In-Reply-To: <20020429004945.83544.qmail@web14804.mail.yahoo.com>; from aurel_wisse@yahoo.com on Sun, Apr 28, 2002 at 05:49:45PM -0700


On Sun, Apr 28, 2002 at 05:49:45PM -0700, Aurel Wisse wrote:
>
> This is terribly frustrating as Apple is obviously
> able to do it with their Duplex tool hack. Hence, it
> *can* be done. Why can't they just send us their
> sourcecode for the Duplex tool? Does anybody have a
> direct line to Apple?

yes: mknod apple c 1 3

--
Ethan Benson
http://www.alaska.net/~erbenson/

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

  parent reply	other threads:[~2002-04-29  3:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29  0:49 Sungem with iMac Rev-B Aurel Wisse
2002-04-29  3:03 ` Kevyn Shortell
2002-04-29  3:05 ` Ethan Benson [this message]
2002-04-29  4:59 ` David A. Gatwood
2002-04-29 13:26 ` Benjamin Herrenschmidt
2002-04-30 17:07   ` Michael Schmitz
2002-04-30 18:20     ` benh

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=20020428190517.H21791@plato.local.lan \
    --to=erbenson@alaska$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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