Raspberry Pi – Configuration lessons learned

When I first started out with my Raspberry Pi, I mostly used SecureCRT since it was integrated with GNS3 where I do a fair amount of my network simulations on when I am working on a problem or a new network design. When I ran into what I think is a terminal emulation issue between Raspian and Minicom, I switched over ZOC that I first used when I got my MacBook Pro and SecureCRT didn’t have a Mac client. I have been exchanging emails with the ZOC developer and how to have an idea of what the problem may be. I was given some very good troubleshooting info for a problem that wasn’t ZOC’s to deal with. I will also get with SecureCRT to see if there is something that I can do with that app to finally resolve the problem. I know there are some other terminal client options to work with such as iTerm2 and I will be trying those over time just for familiarity if nothing else.

Another change that I have worked with is learning to work with nano. I had some experience over the years with vi, so that is one that I went to first. Finally decided to take th plunge and deal solely with nano. Wish I had started working with it from the beginning. The nearest thing I can relate it so is the edit program from DOS that I first remember seeing on DOS 4.0. The editing process is much simpler with nano. You don’t have to start the X11 environment to use it and the commands/keystrokes are very close to what I was used to in DOS, so that has helped the learning curve.

For those who have been following my Raspberry Pi series, I have a roadmap that I am anxious to see play out. Although Linux isn’t my first language, between Raspian and the Raspberry Pi, I see a lot of potential for use as a troubleshooting tools for network engineers or admins. When I have worked on network problems over the years, I periodically ran into a situation where I was either dealing with a network firewall or other issue where it would have been handy to a server that could provide http, ftp or other network service to work with instead of risking the use of a production system or having an independent test source to work with to verify if the firewall or server in question was the problem. I hope that this will be useful to other network engineers/admins who don’t have a lot of linux experience.

To see more of my posts about the Raspberry Pi, please go to http://www.ronnutter.com/category/raspberry-pi/

Send to Kindle
This entry was posted in Blog Entries, Raspberry Pi and tagged . Bookmark the permalink.