Skip to content
Snippets Groups Projects
Commit 2bc3b35a authored by Danny McDonald's avatar Danny McDonald
Browse files

host image on gitlab (danny trying out the gitlab ide)

parent ea266fee
No related branches found
No related tags found
No related merge requests found
...@@ -7,8 +7,9 @@ I solved it by using a third party software, even though sadly it wasn't open so ...@@ -7,8 +7,9 @@ I solved it by using a third party software, even though sadly it wasn't open so
### Second Update (22:40) ### Second Update (22:40)
- ![And we're live](https://paste.pics/7ea975d5d5034961602ae19453da027c) ![And we're live](live.png "And we're live")
- Though I haven't figured out how to embed this picture
... Though I haven't figured out how to embed this picture. Hmm, this seems to be how
### First impressions ### First impressions
...@@ -71,8 +72,8 @@ To have Dannys work not be in vain, I'll be adding some of his "better-written" ...@@ -71,8 +72,8 @@ To have Dannys work not be in vain, I'll be adding some of his "better-written"
Since you might find yourself inside the Terminal (command prompt) more often on Linux, do try to document which commands you find yourself using, and what they do. You'll probably paste a few in from Google/stack overflow answers. Some of the common commands: Since you might find yourself inside the Terminal (command prompt) more often on Linux, do try to document which commands you find yourself using, and what they do. You'll probably paste a few in from Google/stack overflow answers. Some of the common commands:
* `ls` -> show contents of directory (ls -alh, show it more readably) * `ls` -> show contents of directory (`ls -alh`, show it more readably)
* `cd` -> change directory (learn cd /, cd ~, cd .. for moving around using relative, rather than absolute paths to things) * `cd` -> change directory (learn `cd /`, `cd ~`, `cd ..` for moving around using relative, rather than absolute paths to things)
* `find` -> print paths to files/folders matching some criteria * `find` -> print paths to files/folders matching some criteria
* `grep` -> use regular expressions to find lines in files that match some search string * `grep` -> use regular expressions to find lines in files that match some search string
* `cat <file.txt>` -> print contents of file to terminal * `cat <file.txt>` -> print contents of file to terminal
...@@ -110,7 +111,9 @@ echo "Finished! I am now a computer programmer" ...@@ -110,7 +111,9 @@ echo "Finished! I am now a computer programmer"
The first line of the script, called a shebang, tells your system which language the program is written in (bash, the default language of your terminal). You'd save this as `update.sh`, then you'd tell Linux you want to be able to execute the file with: The first line of the script, called a shebang, tells your system which language the program is written in (bash, the default language of your terminal). You'd save this as `update.sh`, then you'd tell Linux you want to be able to execute the file with:
```chmod +x update.sh``` ```bash
chmod +x update.sh
```
You can then do ./update.sh to run your script. If it prints the Finished line, it worked, and you're a programmer now. You can even move the file to /usr/bin, and then you can run it from any directory at any time just by typing update.sh! But, since you're a programmer now, you actually make a repository containing all your cool scripts, and you keep this and other scripts that you write under version control in that repository. That way you can improve it over time, while keeping its history, blah blah. You can then do ./update.sh to run your script. If it prints the Finished line, it worked, and you're a programmer now. You can even move the file to /usr/bin, and then you can run it from any directory at any time just by typing update.sh! But, since you're a programmer now, you actually make a repository containing all your cool scripts, and you keep this and other scripts that you write under version control in that repository. That way you can improve it over time, while keeping its history, blah blah.
...@@ -118,16 +121,24 @@ You can then do ./update.sh to run your script. If it prints the Finished line, ...@@ -118,16 +121,24 @@ You can then do ./update.sh to run your script. If it prints the Finished line,
Open a terminal and use the following command to install telnet: Open a terminal and use the following command to install telnet:
```sudo apt install telnet``` ```bash
sudo apt install telnet
```
And then use this command to watch Star Wars in ASCII art. And then use this command to watch Star Wars in ASCII art.
```telnet towel.blinkenlights.nl``` ```bash
telnet towel.blinkenlights.nl
```
One other thing you'll want to do quite quickly, install Atom and/or Sublime Text, and then set those in terminal as your default editor, so that files are opened for editing using those apps, rather than in the terminal's default (terminal-based) editor (nano or vim, both of which require some practice). One other thing you'll want to do quite quickly, install Atom and/or Sublime Text, and then set those in terminal as your default editor, so that files are opened for editing using those apps, rather than in the terminal's default (terminal-based) editor (nano or vim, both of which require some practice).
https://askubuntu.com/questions/777410/how-to-set-atom-editor-to-main-editor https://askubuntu.com/questions/777410/how-to-set-atom-editor-to-main-editor
These instructions tell you something really valuable, that you can add lines to this `~/.bashrc file`. This file contains your terminal preferences and shortcuts and so on. For example, I add: These instructions tell you something really valuable, that you can add lines to this `~/.bashrc file`. This file contains your terminal preferences and shortcuts and so on. For example, I add:
```alias la="ls -alh"```
And then do `source ~/.bashrc` to reload the settings. This gives me a new command, `la`, which is just the same as doing `ls -alh` but shorter. So yeah, back to the *point*, you use this same preferences file to store your preferred text editor, so that when you do things in terminal requiring a text editor, it'll open the file with Atom, much easier than learning `vim` right now. ```bash
\ No newline at end of file alias la="ls -alh"
```
And then do `source ~/.bashrc` to reload the settings. This gives me a new command, `la`, which is just the same as doing `ls -alh` but shorter. So yeah, back to the *point*, you use this same preferences file to store your preferred text editor, so that when you do things in terminal requiring a text editor, it'll open the file with Atom, much easier than learning `vim` right now.
projects/Henrik/Linux Journey/live.png

226 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment