From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: minix 3
Date: Fri, 14 Dec 2018 07:49:55 -0500 [thread overview]
Message-ID: <CADj8JxeJC9-F+VR_QahvpPwbnGOSyhCURoY9Qk2fP7B+a7p0oA@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.21.1812140734530.22332@panix1.panix.com>
I read about it and looks interesting. Its supposed to be compatible
with the stuff from netbsd but I don't know how it differs from the
linux kurnel.
On 12/14/18, Linux for blind general discussion <blinux-list@redhat.com> wrote:
> No clue on accessibility, but yes I have heard of minix in one of its
> earlier incarnations. For a while I worked in a Naval Research facility
> and the management in the department in which I work decided to install
> minix base-wide. The result was disasterous and nearly got our
> department shut down.
>
> On Fri, 14 Dec 2018, Linux for blind general discussion wrote:
>
>> Date: Fri, 14 Dec 2018 07:11:50
>> From: Linux for blind general discussion <blinux-list@redhat.com>
>> To: blinux-list@redhat.com
>> Subject: minix 3
>>
>> Has anyone here ever used or installed minix 3 and how accessible is it?
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> --
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
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=CADj8JxeJC9-F+VR_QahvpPwbnGOSyhCURoY9Qk2fP7B+a7p0oA@mail.gmail.com \
--to=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).