Status Updates From How Linux Works: What Every...

ngl im a weird nerd so i knew a lot of this already

Gives you info on a way that is straightforward

I've been running linux as a hobby for 18 years now and I thought it was time to finally read the manual. You can pick up a lot "on the job" but I didn't realize how much detail I missed.

I know Linux, bruh

Enjoying this a lot.

Working on my ultimate Dev PC!

58-282
+ bash

Just finished chapter 02, which ends with a general overview of the hierarchy of the filesystem. So far, a great book, super easy to understand and to follow along.

When you encounter a problem on a Unix-like system such as Linux, you must read the error message. Unlike messages from other operating systems, Unix errors usually tell you exactly what went wrong.

If you’re impatient, ask a friend—or pay someone to be
your friend so that you can ask him or her.

Axis360 Ebook 11/437

Axis360 Ebook 65/493

Amazing ! So far I have learned more about Linux in this book than I have in school over the last 3 months!

Very interesting, very good introduction to Linux.

I forgot about sys calls.... have to read this book again

Unlike other operating systems, Linux treats EVERYTHING AS A FILE from directores to whole drives. While it allows us, users, to easily manipulate the I/O contained within them, it does take a while before it actually sinks into your mind.

Upstart is fascinating.

I didn't know systemd is that complex. However, I found socket units interesting.

OverDrive Kindle

It's not a first look book, it requires a little knowledge of everything before you can get really into it. This book and the linux command line are great together

Great book for things beyond reference. As he says it's not meant to be a exhaustive reference but a narrative that fills in the gaps sometimes left by strict and comprehensive references. Use this at work all the time. Will never probably be "done" with it!

So much data!

Getting Online Help: man ls; man -k keyword; man -5 passwd; command --help or -h; ls --help; info command; some pkgs dump avail docs into /usr/share/docs with no regard for online manual systems like man of info.

Special Chars: Perl uses nearly all of them, *.!|/\$'`"^~#[]{}_; Jargon File, http://www.catb.org/~esr/jargon/html/, The New Hacker's Dictionary[Raymond]; Command-Line Editing: Ctrl-B,Ctrl-F,Ctrl-P,Ctrl-N,Ctrl-A,Ctrl-E,Ctrl-W,Ctrl-U; Text Editors: vi; emacs; Learning the vi Editor[Lamb] book; For emacs, start emacs from prompt, type Ctrl-H and then type t. GNU Emacs Manual[Stallman]

passwd - change password, chsh - change shell; Dot Files, .bashrc, .login, .[^.]* or .??* to get all dot files except the current and parent dirs; Environment and Shell Variables, PS1 controls the prompt, STUFF=blah, LESS env var, many man pages contain a section marked ENVIRONMENT that describes env vars, assign env var by export STUFF; PATH=dir:$PATH;

more and less
less --help
pwd (print working dir)
diff (option -c)
file
find
find dir -name file -print
head and tail
head /etc/inittab shows first 10 lines
tail /etc/inittab shows last 10 lines
sort (options -n -r)

Further References:
Mastering Regular Expressions[Friedl]
regex chapter of Programming Perl[Wall]
Introduction to Automata Theory, Languages, and Computation[Hopcroft](*like math)

See Appendix A for large list of cmds
grep root /etc/passwd
grep root /etc/*
-i and -v options
egrep
regex vs wildcard-style patterns
regex .* match any number of chars like * in wildcards
regex . match one arbitrary char
grep(1) man page describe regex

Intermediate Cmds: grep

/bin/sh
shell window / terminal windown
prompt $
cat
stdin / stdout
Ctrl D / Ctrl C
Basic cmds: ls, cp, mv, touch, rm, echo
* echo cmd is useful for finding expansions of shell wildcards and variables
/ . and .., absolute and relative pathnames
Directory Cmds: cd, mkdir, rmdir, rm -rf
Shell Wildcards
echo *
echo *dfkdsafh
?
single quotes to escape, echo '*', will find handy in grep and find cmds