Automation, Innovation, and Linux…
Here are the PS1‘s I use for my daily driver. Feel free to take them and change them up.
I use different colors, so one doesn’t accidentally login or run something as root (which is in red, users are yellow).
To use these, simply copy and paste them into either the root user; or regular user’s .bashrc.
Alternatively you can add them to /etc/profile to make them enforced system wide.
For MAC, it is the same; however the PS1 is a little different. See below.
Root
User
Fan of nano? Like having pretty colors to see where you messed up? Of course we do!
Much like many of us, I use nano. Its quick, easy, and readily available. However, I like to see the highlighting of my language. As many of you know, there are “nanorc” files, that will tell nano how to handle language highlight.
They are usually located in /usr/share/nano/ (at least in ubuntu); and you can make your own under your home directory with a .nanorc file. I can post about that later…
For now let get markdown working in nano!
You will need to create a file called markdown.nanorc by doing the following:
sudo touch /usr/share/nano/markdown.nanorc
Now that the file is created, we just need to populate it with the following below text, in a pastebin for your convenience. Just copy that text, and paste it into the aformentioned file. Once a new session is started, you will be able to start using markdown.
https://pastebin.com/raw/tHkBqdef
Just a little note as well; if you have a need for another language, you can follow the same instructions with their pre-reated files. Take a look here, to see other nanorc files. Also, nano has just been updated after a very long while, please take a look at the new support when you can.
Just another thing that I helping with lately. If anyone need help with a new idea for a Raspberry PI, or IoT device message me. I have been through several POC’s (proof of concepts).
Keep in mind, if you are working on a new product; or sensitive information I keep all client info secret, and have no issues with an NDA.
Happy to just answer questions; or see what I can do to help. Just contact me.
I am building a robot (named aptly: Kill Switch) from old parts I had laying around, and it is powered by hub motors from a ‘hover-board’. The stats were pretty strong for small kids; so I am building a lot of safety into it.
This will include software, and hardware measures to ‘take over’ the device, and even limit speed. Eventually I will be able to return him back to a certain spot with playtime is over. I hope to automated charging as well eventually. There are a lot of features I have ready; however I am still building out the hardware.
This can be difficult to do and keep extremely safe. So for starters I am testing it only; and I have 2 kill switches I am putting in to ensure safety. One the person will have to keep his foot on constantly for the buggy to run. The other is a simple quick kill switch. (Eventually these will be automated).
The Device already has an RPI3 with a small motor-controller for future automation’s. This will control other aspects of the vehicle via software. Such as speed limitations, power usage, GPS, WIFI, BT. I will also be using a pico router to establish a LAN around the device. This is for media, as the vehicle will have speakers/screen to watch/host media on the LAN.
Hardware Safety Features:
Once testing is completed, and it works; I will go through how I set it up. However, this will be piece by piece as I do it. I have even considered some youtube videos. However, that will depend on my success in doing this on a budget. I am also using completely reclaimed parts, minus a couple bolts I bought. So its been free so far.
On that note, I have been building the chassis, but if anyone in the Dallas, TX area has an old go-cart frame that rolls/steers, I am looking. I think it would make it a lot lighter. Shoot me a message, info is on my contact me page.
MUCH More to come… Please keep an eye on the series…
-M
This is kept under the Linux Learning Project and Learning Resources section of the site, and is updated occasionally with new links. Feel free to suggest one by contacting me directly.
Help/Chat:
Resources:
First, I would like to say thank you to the community members for helping out. I have gotten a lot of input on the new image. This has also given me better feel for what the community wanted in an image. Which leads me to the next bit of news.
Some of you are undoubtedly wondering why I have not released my Jasper v1.6 image as of yet. Well, I can assure you there are very good reasons.
Firstly, I have had some severe family/health issues come up as of late which take priority. I am also in the middle of moving a family of 5. Combine that with the other reasons below, and I feel that most will feel the wait to be worth it.
This leads me to the next bit of news, however shocking it may be.
FAQ (COMING SOON)
I have recently had a large number of people wanting to know the exact release date for the v1.6 image. I will release it without the installer, and release the installer separately so it can be used on images that are not mine.
I would highly suggest that if there is annoyance; or fix for the next release that it be reported ASAP to the room in our SLACK.
Thanks for your patience,
Matthew Curry
Hello All,
First, I want to thank everyone that has been patient with me so far in getting these things done one at a time…
I know it is not easy to get some of these things completed without good documentation. So, with the help of a few community members, I have started what is a very rough draft of our documentation. It is neither complete, or ready…. However, we are adding information as we go, so keep a close eye. Even feel free to clone it, and contribute. There will be documentation on how to do both of those coming as well. Feel free to watch here, the repository, or the Support Forums/Slack for updates. I update them all.
If you have items you would like to see added to the documentation, I would run it by myself, or d34dman first. If we have not already written it (there are some not committed yet); then we will just let you know to put in a PR (aka Pull Request). Once we have both reviewed it and give it a thumbs up. We will merge it.
Alright, all that said… Here is the link to the documentation!
Thanks,
Matthew Curry
These kits will arrive and be ready to use the moment you power them up. They will be customized to the user, and an image will be provided so they can restore any time they like.
They will include the following:
If you are interested in one of these kits, feel free to contact me or start the process by purchasing one below:
They are updating now; this includes a few fixes and features.
I apologize for the delays recently, I have had some personal issues come up.