public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Doug Smith <savant-technopath@cyber-wizard.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: need some accessible command-line tools
Date: Wed, 19 Jun 2013 17:37:17 -0400	[thread overview]
Message-ID: <20130619213717.GB6929@Enterprise> (raw)
In-Reply-To: <0a742a51-6e1a-4a13-af6d-afb50e79daa4@default>



Ok, here's the best answer I can give you.  As far as pdftotext, it is in the poppler-utils package.  I do not know of any kind of command line word 
processor, but there is LaTeX, if that is the way you want to go.  I have never found any kind of good command line network management tool.  That is, 
none of what I have tried has worked.  I have tried wicd-cli, but it refused to even allow the networks in this building to be scanned.  At this time, 
I am using ifupdown suite to do this: 

Each connection you have, make a copy of your /etc/network/interfaces for that connection, editing the critical data such as essid and password.  When 
you are at a different location, and you know which connection works best do this: 

ifdown wlan0; ifup -i file-for-working-connection wlan0

This uses dhclient to get the addresses and bind to connect it all up.  This is not anything like it's done in the gui world, but I have found no 
network tool that will even work.  Nmcli, for example does not have all the functionality you might need unless someone knows how to use it, and that 
might be of help.  I have never gotten wicd-cli to scan networks and that would help me a lot if that worked, but it doesn't.  



Hope this helps. 




-- 
Doug Smith: Special Agent
S.W.A.T  Spiritual Warfare and Advanced Technology
Forever serving our LORD and SAVIOUR, JESUS CHRIST.


  reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Don Raikes
 ` Doug Smith [this message]
   ` Brian Buhrow
   ` Willem van der Walt
 ` Gregory Nowak
   ` Adam Myrow
   ` Sean Murphy
     ` Mike Ray
       ` Jason White
     ` Don Raikes

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=20130619213717.GB6929@Enterprise \
    --to=savant-technopath@cyber-wizard.com \
    --cc=speakup@linux-speakup.org \
    /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).