Jeffery,
Here's my attempt to address your questions.
Someone else may do a better job who is more familiar with Raspbian (debian)
but hopefully this will give you a quick and easy / usable set of answers to
work with until a better set of answers come along.
1. No, your ssh command syntax will remain the same. Depending on your router,
it may be more reliable to use the IP address of the pi you're trying to ssh
into. The typical raspian installation has pi as the default user and I believe
the default password is raspberry.
If you don't find this to work, try pi with password pi, but almost certain the
former is the working password.
So, ssh -l pi@192.168.0.10 or ssh -l pi@10.0.1.10 for example. If one of those
were your IP address on the pi.
2. The hostname for your pi is located in /etc/hostname. You can use cat to
show what it is or use the hostname command to show it.
You can put a new hostname in this file (of course as root or using sudo before
either the echo command or nano or editor of your choice) and reboot afterward
to have it take effect... or possibly do sudo hostname <new value>
But in the latter case the change won't stick and it won't show up on your
login prompt without logging out and relogging in, so it won't look like it's
taken effect.
Combo answer: 2. / 3.
Package needed, you will need the git package to obtain Mike's pSpeakup code.
Sudo apt-get install git
Should obtain it.
3. You will definitely want to change your password and the root password with
the passwd command.
Syntax: passwd
You can do sudo -I to become root and then use passwd, or do sudo passwd root
to change root's password
See previous answer on the packages. As far as I can remember, no other
packages were needed for Mike's code.
4. From Mike's guide on the history and fix to the TTS stuttering issue on the
website located at http://raspberryvi.org/stories/stuttering.html
$ git clone https://github.com/cromarty/ttsprojects.git
This will create a directory called ttsprojects below your current working
directory.
Compile and Install the Library
Currently the code is built using a static Makefile rather than using autoconf
to create it. I think this is quite OK because the code is specific to the
Raspberry Pi and autoconf is, after all, concerned with solving the issue of
creating working make files for different platforms.
First, cd to the right directory to build the library:
$ cd ttsprojects/raspberry-pi/libilctts/src
Now make the library:
$ make
Install it:
$ sudo make install
Note that this is entirely dependent on the presence of the right libraries in
/opt/vc. At the time of writing the Raspbian images based on Debian Jessie
available for [download][download] from the Raspberry Pi Foundation have this
code already installed and compiled.
Now we need to build and install the forked version of espeakup, which I have
called piespeakup.
From ttsprojects/raspberry-pi/libilctts/src, cd to the right directory for the
build:
$ cd ../../piespeakup
Now build with:
$ ./build.sh
This should build and install piespeakup.
If you go into the above listed guide, you'll note I've left out some
directions after what Ii've pasted in here. That's because Mike has done some
work on his scripts since he posted that guide, and it doesn't appear you need
to follow all of those instructions any longer.
Feel free to look through the guide though if you have issues.
Hope this helps!
- Greg
-----Original Message-----
From: raspberry-vi-bounce@xxxxxxxxxxxxx
[mailto:raspberry-vi-bounce@xxxxxxxxxxxxx] On Behalf Of Jeffery Mewtamer
Sent: Tuesday, August 30, 2016 9:01 AM
To: raspberry-vi@xxxxxxxxxxxxx
Subject: [raspberry-vi] Manually installing Mike's code, what's my next step.
*** This is an EXTERNAL email. Please exercise caution. DO NOT open attachments
or click links from unknown senders or unexpected email. - STS-Security***
I already have my Pi talking using the Jessie image on the Raspberry VI
website, but being in the last semester of obtaining my BS in Computer Science,
I've decided I should try setting things up manually at least once, especially
since the class's semester project in my Net Centric class involves building a
Raspberry Pi Cluster.
Anyways, I've already downloaded the latest Jessie-lite image from the
Raspberry Pi Foundation, unzipped it and used dd to put it on a spare MicroSD.
I presume my next step is to boot with the newly imaged card and ssh into the
Pi, but while I have prior experience with ssh, this will be my first time
trying to ssh into a device on a network I've set-up myself rather than to
access my network drive on a university network.
The physical set-up I'll be using will have my Linux desktop and the Pi
connected to my home network's router via Cat6 Ethernet and every thing on the
desktop's side will be done from the command line.
In the past, I've used an ssh command of the form:
ssh username@remoteHost
and was prompted for my password. My specific questions at this point are:
1. Will I need to modify the format of my ssh command in anyway?
2. How do I determine username and remoteHost for my Pi? In the event they
aren't already installed, what Debian packages provide the commands needed for
this job?
3. Once I've successfully ssh'd into my Pi, are there any tasks I need to
perform(first boot administrative tasks, installing dependencies,
etc.) before attempting to download and install Mike's code?
4. Speaking of which, anyone mind reposting the directions for downloading and
installing Mike's code so I don't have to go archive diving for them?
If it matters, my current Pi is a Pi2B, though I hope to get at least one Pi3
by the end of September.
Thanks in advanced for any help that can be provided.
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of the
Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of the
Foundation.
Mike Ray, list creator, January 2013
