public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn at home" <GlennErvin@cableone.net>
To: "Janina Sajka" <janina@rednote.net>
Cc: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: frustrated
Date: Fri, 31 Dec 2004 14:39:57 -0600	[thread overview]
Message-ID: <003601c4ef78$e4aa0c40$6a00a8c0@desktop> (raw)
In-Reply-To: <20041231203049.GC7071@rednote.net>

Well I don't want to recompile the kernel, but I am forced to go to the 
internet and do searches for help, and perhaps it is old info, but it does 
indicate a recompile will fix the problem.
Or I found some info on get-cache for this, but I find little help with man 
on this.
Glenn
----- Original Message ----- 
From: "Janina Sajka" <janina@rednote.net>
To: "Glenn at home" <GlennErvin@cableone.net>; "Speakup is a screen review 
system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, December 31, 2004 2:30 PM
Subject: Re: frustrated


Recompiling isn't going to fix your problem, Glenn. Sorry.

While many of us were forced into learning to compile kernels in the
early days of Speakup, kernel compilation isn't beginner work.
Statements like "recompile" and "hard for beginner" suggest to me you're
just digging yourself deeper into a hole.

Also, statements like:

"I apparently need to recompile my kernel because Alsa cannot control my
> sound card, because Debian has hold of it," further confirm my
> opinion.

But, if you insist, you are certainly free to do as you wish. But, don't
be surprised if some of us stop trying to help you.

Sorry. This isn't exactly a cheery "Happy New Year" kind of message. I
really mean no offense.

Glenn at home writes:
> Why is it so hard to get help/info on using Linux?
> I have Debian.
> I apparently need to recompile my kernel because Alsa cannot control my
> sound card, because Debian has hold of it, but I need to get Debian to not
> control it.
> I have spent all day looking on the internet for help, and can find non on
> recompiling the kernel, some examples would be nice.
> man pages are often useless for a beginner, as they are too cryptic.
> Any help appreciated, as I am about ready to quit Linux.
> Glenn
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Janina Sajka, Chair
Accessibility Workgroup
Free Standards Group (FSG)

janina@freestandards.org Phone: +1 202.494.7040

If Linux doesn't solve your computing problem, you need a different problem.



  reply	other threads:[~ UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 frustrated Glenn at home
 ` frustrated Buddy Brannan
 ` frustrated Janina Sajka
   ` Glenn at home [this message]
     ` frustrated Lorenzo Prince
       ` frustrated Glenn at home
         ` frustrated David Bruzos
           ` frustrated Janina Sajka
             ` frustrated Glenn at home
               ` frustrated Chuck Hallenbeck
                 ` frustrated Janina Sajka
               ` frustrated Janina Sajka
                 ` frustrated Glenn at home
                   ` frustrated Janina Sajka
     [not found]                     ` <00a001c4f036$1c1e3b20$6a00a8c0@desktop>
                       ` frustrated Janina Sajka
                         ` frustrated Glenn at home
                           ` frustrated Janina Sajka
                             ` frustrated Glenn at home
                           ` frustrated Sean McMahon
                   ` frustrated Sean McMahon
               ` frustrated Sean McMahon
           ` frustrated Gregory Nowak
             ` frustrated Glenn at home
               ` frustrated Janina Sajka
               ` frustrated Gregory Nowak
         ` frustrated Lorenzo Prince
         ` frustrated Sean McMahon
       ` frustrated Buddy Brannan
 ` frustrated Gregory Nowak
 ` frustrated Kenny Hitt
 ` frustrated Sean McMahon

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='003601c4ef78$e4aa0c40$6a00a8c0@desktop' \
    --to=glennervin@cableone.net \
    --cc=janina@rednote.net \
    --cc=speakup@braille.uwo.ca \
    /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).