From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: module locations
Date: Tue, 13 Jun 2017 16:20:34 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1706131618480.12240@southernprince> (raw)
In-Reply-To: <20170613205635.GA2882@buffalo.yelavich.home>
Mark here, again...
I got modinfo to work. I forgot to put sudo in front of it. Rather than read the file, I just used the info it gave me to see what other modules were
there in case I decided to go on a quest for another older synth.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> Luke here, reply inline.
> On Wed, Jun 14, 2017 at 06:18:54AM AEST, Linux for blind general discussion wrote:
> > Where do I find speakup_ltlk? I want to actually look inside the file to see what it looks like.
>
> The modinfo command can help you find it.
>
> As for looking at it, you won't find much that you would recognise, other
> than text strings. If you really want to look at it, you are better off
> looking at the relevant files as part of the kernel source.
> --
> Please check out my Patreon campaign and spread the word.
> https://patreon.com/lukefoss
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
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
` Linux for blind general discussion
` Linux for blind general discussion [this message]
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=alpine.DEB.2.21.1.1706131618480.12240@southernprince \
--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).