From: Alan Braslau <braslau.list@comcast.net>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: currently supported platforms
Date: Fri, 19 Jul 2019 08:19:02 -0600 [thread overview]
Message-ID: <20190719081902.0eca0b25@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <CALBOmsb9TmoBu0faO0YjdXyQKtr5yVFbrceb0r7606ODC+cLOA@mail.gmail.com>
On Fri, 19 Jul 2019 14:21:40 +0200
Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
> > In the wiki it says kfreebsd would be still supported via Debian -
> > is this still true?
>
> No clue. Probably nobody ever tested for ages.
I'm gnu-less...
From https://www.debian.org/ports/kfreebsd-gnu/
"Debian GNU/kFreeBSD is not an officially supported architecture. It has
been released with Debian 6.0 (Squeeze) and 7.0 (Wheezy) as a
technology preview and the first non-Linux port. Since Debian 8
(Jessie) it is though no more included in official releases."
The situation is, despite its exploration into non-linux kernels,
Debian remains a GNU-anchored system and this diverges from a
GNU-independent base or core that freeBSD represents.
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-07-19 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 10:51 Henning Hraban Ramm
2019-07-19 12:21 ` Mojca Miklavec
2019-07-19 14:19 ` Alan Braslau [this message]
2019-07-24 19:17 ` Henning Hraban Ramm
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=20190719081902.0eca0b25@poo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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).