[OpenAFS] Future of maemo port?
Ted Creedon
tcreedon@easystreet.net
Thu, 22 Dec 2011 21:55:05 -0800
--bcaec5015da3fed9d304b4bc0e8d
Content-Type: text/plain; charset=ISO-8859-1
AFS as an add on to he Dllink would suit me fine and allow shutting down 3
servers
If a larger capacity circuit board is needed, that's not a a problm.
maybe I'll have time after Jan 1.
tedc
On Thu, Dec 22, 2011 at 7:20 PM, Jason Edgecombe <jason@rampaginggeek.com>wrote:
> Hi Ted,
>
> Other ARM devices, like the D-Link, that run Linux have a good chance to
> run OpenAFS. debian-arm does exist. I'm just wanted to formally deprecate
> the maemo code, which has been unmaintained for a while.
>
>
> On 12/22/2011 01:02 PM, Ted Creedon wrote:
>
>> The Dlink DNS-320 NAS has an 800 MHz ARM + 128M of memory
>>
>> If it could be ported, that would be ideal
>>
>> I've requested the GPL build tree from Dlink
>>
>> I would not be adverse to sponsoring part of a project to provide a
>> replacement board for same.
>>
>> tedc
>>
>> On Thu, Dec 22, 2011 at 9:32 AM, Jason Edgecombe<jason@rampaginggeek.**
>> com <jason@rampaginggeek.com>>wrote:
>>
>> Hi Everyone,
>>>
>>> Are there any objections to removing the maemo port project from the
>>> wiki?
>>> Should it be replaced by something else? Maemo is dead and I have no clue
>>> about Meego, its successor. I haven't touched the Maemo port in a couple
>>> of
>>> years, and I have no device to develop or test on.
>>>
>>> What mobile platforms does it make sense to (hopefully) spend effort on?
>>>
>>> Insights? Comments?
>>>
>>> Thanks,
>>> Jason
>>> ______________________________****_________________
>>> OpenAFS-info mailing list
>>> OpenAFS-info@openafs.org
>>> https://lists.openafs.org/****mailman/listinfo/openafs-info<https://lists.openafs.org/**mailman/listinfo/openafs-info>
>>> <**https://lists.openafs.org/**mailman/listinfo/openafs-info<https://lists.openafs.org/mailman/listinfo/openafs-info>
>>> >
>>>
>>>
> ______________________________**_________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/**mailman/listinfo/openafs-info<https://lists.openafs.org/mailman/listinfo/openafs-info>
>
--bcaec5015da3fed9d304b4bc0e8d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
AFS as an add on to he Dllink would suit me fine and allow shutting down 3 =
servers<br><br>If a larger capacity circuit board is needed, that's not=
a a problm.<br><br>maybe I'll have time after Jan 1.<br><br>tedc<br>
<br><div class=3D"gmail_quote">On Thu, Dec 22, 2011 at 7:20 PM, Jason Edgec=
ombe <span dir=3D"ltr"><<a href=3D"mailto:jason@rampaginggeek.com">jason=
@rampaginggeek.com</a>></span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Ted,<br>
<br>
Other ARM devices, like the D-Link, that run Linux have a good chance to ru=
n OpenAFS. debian-arm does exist. I'm just wanted to formally deprecate=
the maemo code, which has been unmaintained for a while.<div class=3D"im">
<br>
<br>
On 12/22/2011 01:02 PM, Ted Creedon wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
The Dlink DNS-320 NAS has an 800 MHz ARM + 128M of memory<br>
<br>
If it could be ported, that would be ideal<br>
<br>
I've requested the GPL build tree from Dlink<br>
<br>
I would not be adverse to sponsoring part of a project to provide a<br>
replacement board for same.<br>
<br>
tedc<br>
<br>
On Thu, Dec 22, 2011 at 9:32 AM, Jason Edgecombe<<a href=3D"mailto:jason=
@rampaginggeek.com" target=3D"_blank">jason@rampaginggeek.<u></u>com</a>>=
;wrote:<br>
<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
Hi Everyone,<br>
<br>
Are there any objections to removing the maemo port project from the wiki?<=
br>
Should it be replaced by something else? Maemo is dead and I have no clue<b=
r>
about Meego, its successor. I haven't touched the Maemo port in a coupl=
e of<br>
years, and I have no device to develop or test on.<br>
<br>
What mobile platforms does it make sense to (hopefully) spend effort on?<br=
>
<br>
Insights? Comments?<br>
<br>
Thanks,<br>
Jason<br></div>
______________________________<u></u>**_________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org" target=3D"_blank">OpenAFS-info@=
openafs.org</a><br>
<a href=3D"https://lists.openafs.org/**mailman/listinfo/openafs-info" targe=
t=3D"_blank">https://lists.openafs.org/**<u></u>mailman/listinfo/openafs-in=
fo</a><<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-inf=
o" target=3D"_blank"><u></u>https://lists.openafs.org/<u></u>mailman/listin=
fo/openafs-info</a>><br>
<br>
</blockquote></blockquote><div><div></div><div class=3D"h5">
<br>
______________________________<u></u>_________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org" target=3D"_blank">OpenAFS-info@=
openafs.org</a><br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" target=
=3D"_blank">https://lists.openafs.org/<u></u>mailman/listinfo/openafs-info<=
/a><br>
</div></div></blockquote></div><br>
--bcaec5015da3fed9d304b4bc0e8d--