From: Dan Williams <dcbw@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>, Jakub Kicinski <kuba@kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: Does anyone use Appletalk?
Date: Wed, 01 Nov 2023 15:27:27 -0500 [thread overview]
Message-ID: <79b7f88e3dd6536fe69c63ed3b4cc1f2c551ce8d.camel@redhat.com> (raw)
In-Reply-To: <5e3e52a48ba9cc0109a98cf4c5371c3f80c4b4cc.camel@physik.fu-berlin.de>
On Wed, 2023-11-01 at 13:26 +0100, John Paul Adrian Glaubitz wrote:
> Hi Geert,
>
> On Wed, 2023-11-01 at 13:19 +0100, Geert Uytterhoeven wrote:
> > > Isn't that a bit late?
> >
> > It can always be reverted...
>
> Sure, but I'd rather see such discussions before merging the removal
> patch. Best would have been to reach out to the netatalk project, for
> example and ask [1]. They just released version 3.1.18 of the
> netatalk
> server in October 2023.
>
> It's an incredibly cool project because it allows you to replace the
> expensive Apple TimeMachine hardware with a cheap Raspberry Pi ;-).
But... Time Machine debuted with 10.5 and AppleTalk got removed in
10.6; did the actual TimeCapsules ever support AppleTalk, or were they
always TCP/IP-based?
(also TimeMachine-capable Airport Extremes [A1354] are like $15 on
eBay; that's cheaper than a Raspberry Pi)
This patch only removes the Linux-side ipddp driver (eg MacIP) so if
Time Capsules never supported AppleTalk, this patch is unrelated to
TimeMachine.
What this patch *may* break is Linux as a MacIP gateway, allowing
AppleTalk-only machines to talk TCP/IP to systems. But that's like
what, the 128/512/Plus and PowerBook Duo/1xx? Everything else had a
PDS/NuBus slot or onboard Ethernet and could do native
MacTCP/OpenTransport...
Dan
next prev parent reply other threads:[~2023-11-01 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 10:23 Does anyone use Appletalk? Geert Uytterhoeven
2023-11-01 10:54 ` John Paul Adrian Glaubitz
2023-11-01 12:19 ` Geert Uytterhoeven
2023-11-01 12:26 ` John Paul Adrian Glaubitz
2023-11-01 20:27 ` Dan Williams [this message]
2023-11-01 22:29 ` Arnd Bergmann
2023-11-02 2:13 ` Finn Thain
2023-11-02 8:55 ` John Paul Adrian Glaubitz
2023-11-01 22:33 ` John Paul Adrian Glaubitz
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=79b7f88e3dd6536fe69c63ed3b4cc1f2c551ce8d.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kuba@kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--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