public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: fedora 28 speakup
Date: Wed, 21 Nov 2018 09:29:51 -0500	[thread overview]
Message-ID: <20181121142951.GK9676@rednote.net> (raw)
In-Reply-To: <3da33803-415d-de39-e9be-47bdb6a2dd0b@slint.fr>

Hi, Didier:

I think the answer is usually familiarity with how things work. Yes,
it's all Linux, but the config files in /etc can be very different. And,
of course, package management is very different, e.g. dnf for Fedora,
apt for Debian, pacman for Arch, etc., etc.

I would further hazard there may be applications that are well
maintained on one platform and not another. Is it just my Arch where
Linphone has been so horribly broken for over a year?

I'm actually thinking of running multiple virtual machines to try and
get certain apps working again, perhaps using different OS environments
in each vm.

Janina

Janina

Linux for blind general discussion writes:
> What people have in Fedora that they can't have with Debian, Arch or Slint?
> 
> Just curious,
> 
> Best,
> Didier
> --
> Didier Spaier
> Slint distribution http://slint.fr
> 
> On 20/11/2018 16:39, Linux for blind general discussion wrote:
> > About a year or so ago Vinux announced they would be building on Fedora.
> > That would require they solve this problem, but I have not seen a
> > release.
> > 
> > Personally, this problem is what got me to switch to Arch Linux for the
> > machines I work with directly. My Linode hosted server still runs
> > Fedora, but it doesn't need speakup because it's accessed only over ssh.
> > 
> > PS: If you still want to look for a way to stay with Fedora, you might
> > have better luck compiling Fenrir, though you'll still have to create a
> > rpm spec file if you intend to create Fenrir rpms.
> > 
> > Best,
> > 
> > Janina
> > 
> > Linux for blind general discussion writes:
> >>  I am wondering the very same thing? Are there currently any fully built by
> >> Dora distribution ISOs that have speak up already in them? The reason why I
> >> ask, is that I have Fedora in a virtual machine, but it has no speak up  in
> >> it. And the only way to install it would mean working with the sighted
> >> person, who has no idea of what Lenox is. So if they make a mistake typing
> >> the stuff I tell them to type, I am simply  not going to get speak up and
> >> installed properly. Kim’s the reason why I’m looking for an ISO image that’s
> >> already enabled what speak up?
> >>
> >> Sincerely Maurice  Mines
> >> Amateur call kd0iko.
> >>
> >> On 19 Nov 2018, at 13:08, Linux for blind general discussion wrote:
> >>
> >>> If that's the case, what is the easiest way to get Speakup on Fedora?
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: blinux-list-bounces@redhat.com
> >>> [mailto:blinux-list-bounces@redhat.com]
> >>> On Behalf Of Linux for blind general discussion
> >>> Sent: Monday, November 19, 2018 10:39 AM
> >>> To: Linux for blind general discussion <blinux-list@redhat.com>
> >>> Subject: Re: fedora 28 speakup
> >>>
> >>> Not since Bill Acker died some years ago.
> >>>
> >>> Fedora is still not packaging staging modules, afaik.
> >>>
> >>> Janina
> >>>
> >>> Linux for blind general discussion writes:
> >>>> anny rpm for this?
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Blinux-list mailing list
> >>>> Blinux-list@redhat.com
> >>>> https://www.redhat.com/mailman/listinfo/blinux-list
> >>>
> >>> -- 
> >>>
> >>> Janina Sajka
> >>>
> >>> Linux Foundation Fellow
> >>> Executive Chair, Accessibility Workgroup:	http://a11y.org
> >>>
> >>> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> >>> Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> >>>
> >>> _______________________________________________
> >>> 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
> >>
> >> _______________________________________________
> >> 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

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion [this message]
     ` 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=20181121142951.GK9676@rednote.net \
    --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).