Skip to main content

Using Linux on a Chromebook + Relearning Linux

Also posted here.

  Remember that second hand Chromebook I bought for a client years ago?

They upgraded and gave it back, so let's put Linux or Ubuntu on it.

I'm going to see if I can put a distro in there and switch between Chrome OS and Linux.

It took longer to find the correct package to install than anything else. Out of the proverbial Chrome Development Mode box, it doesn't recognize apt, apt-get, or yum.  Nor does it recognize any attempts to install them.

The Chromebook's Linux option installs Penguin, the default Linux Container on Chrome OS. It struggled to start, so I deleted the Linux container and tried again with success.

Most instructions say to enable your Chromebook’s Developer Mode then open a certain terminal; Instead, I found you enable Linux Penguin through Chrome OS (Easy, check your settings) and use that containerized version.

When you do this, Crostini is already installed, which is a more secure form of Crouton. Crouton is outdated. Crostini creates a Linux container within Chromebook OS, and they both have neat bread names.

But now it's time to reacquaint myself with actually using Linux. I couldn't get a full Ubuntu setup to replace Chromebook, apparently a security issue, but I can at least use the penguin container, which is Linux running in a little box in Chrome OS.

The edition is 6.6.50, and even after updating, it's still that. No problem, but some commands do no work. I know there are different Linux distros, but I thought most commands were the same.

I wrote my first Bash script thanks to the Learn Linux For Beginners Book on FreeCodeCamp.org that tells me the date and the files and folders in a directory of my choosing;

 

 

The container uses a side google account of mine.

 

I also parsed log information with commands like 'sort', 'awk', 'cut' and 'sed', managed background processes with ['&', 'fg', 'jobs', and 'kill'] commands, and managing cron, a time-based scheduler.


I'm continuing to learn and am posting updates on BlueSky.




Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an...
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that ...
Post a Comment
Read more