stark

Lesson 1 - The First Boot

After a successful installation and reboot, you are first greeted by GRUB (a blue/black menu in which you can choose a distro to boot) and then, usually, by a login prompt. This screen is also called a TTY, and we are usually in TTY1 after a successful boot.

The default runlevel in LinuxBBQ, just for your information, is runlevel 2. We'll need it later, or never, depends on you.

Tip: You can switch between the TTYs by pressing Alt and the cursor keys left and right. {: .callout .info}

stark

Lesson 2 - Editing files

By default, LinuxBBQ comes with the GNU nano editor. It is good enough for most of the tasks, quick enough for most of the users, and powerful enough to make even editing of multiple files possible.

Let's edit the configuration file of wmii.

Open up a terminal, and type:

nano ~/.wmii/wmiirc_local

stark

Lesson 3 - Package Management I: Fill it up

You probably want to do more than looking at the prompt of your shell.

Only a few tools are added to the Academy distro, one of them is ceni, a very helpful little program that sets up the wired or wireless connection for you.

ceni needs to be run as root. {: .callout .warning}

So open a terminal and Enter:

stark

Lesson 4 - X Startup Customization

Whenever you start your computer and boot into Linux, a series of files are read and executed in a certain order.

We will cover the boot process a tad later in this document, but let us take a look at the part where you enter your username and password and everything thereafter.

This is where the shell starts, as the first interactive environment of your system. After entering username and password, the files ~/.bash_profile and ~/.bashrc are read or sourced.

Let's take a look at ~/.bash_profile first:

stark

Lesson 5 - Terminal I: Configuration

Just recently a fellow griller asked a very good question:

"How can I change the colors of my terminal?"

Read the answers here: http://ow.ly/NkUt4

We should mention, though, that this only works for the terminals xterm and rxvt and it's modifications. More about this later. We recommend to stay with the default terminal emulator (xterm in the Academy release), at least for a few days. It has it strengths, especially in size, speed, dependency count and customization.

stark

Lesson 7 - Terminal III: Productivity without overhead

Most daily tasks, like reading and answering emails, listening to music, reading some RSS feeds, calculating the BMI, creating and extracting zip archives, surfing the internet, copying files from one computer to the other or checking the weather forecast can be accomplished in the terminal.

Some of the people here at the BBQ even say, that this is the preferred way of doing something.

Why?

To answer this question, check the links at the end of this lesson.

stark

Lesson 8 - Package Management II: Housekeeping

Actually, this could be the continuation of the previous lesson.

A real griller keeps his dependency count as low as possible.

And of course a real griller also checks the number of processes running on his system.

He or she enters:

stark

#!/usr/bin/env perl -w
use strict;
use utf8;

sub quote_cb {
	my ($data, $mod, $mod_data, $msg) = @_;
	
	if ($msg =~ /^>/) {
		$msg="\x03" . int(rand(15)) . $msg;
	}

stark

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

stark

Hello there! You are currently visiting gopherspace through a
proxy. To learn more about gopher and how to browse it, read this.
______________________________________________________________________

###################################################################
          Writing C software without the standard library
                           Linux Edition
###################################################################
There are many tutorials on the web that explain how to build a
simple hello world in C without the libc on AMD64, but most of them