Command line class redesigned

This page contains a proposed redesign that is not taking place. Instead, the Knowledge Bees committee is breaking command line into 2 classes and working with Reuse Program Coordinators and command line instructors to create the curriculum.

2 hour class (simply not enough time otherwise)

In order to cover the suggested topics, we really should have a system where we can run sudo. It would also be good to be able to mount a drive, or run a utility like "fsck". I suggest we fit the classroom terminals with small hard drives, then for the class, boot from a live cd and then be able to mount, format, fsck or whatever with the drives. The normal boot for the terminals would remain network and ltsp.

topics covered (initial list taken from ticket 15108):

process control

• top
• kill, killall
• sudo, root

hardware support

• lspci
• modprobe
• /proc (temperature, etc)
• bat_check and wc bat-time (part of the normal build/qc process)
• rmmod

linux filesystem structure

• using gedit or nano or whatever text editor is necessary
• changing permissions
• groups

• grub & yaboot commands
• grub menu changes

• grep
• basic piping and redirection ( |, > , >>, etc.)

networks

• ifconfig
• iwconfig and other wireless stuff
• dhclient

apt

• apt-get install
• apt-cache
• dpkg-reconfigure, dpkg --configure -a

practical stuff

• dpkg-reconfigure xserver-xorg
• mount, cfdisk, fsck
• sudo lshw -xml >printme.xml
• apt-get upgrade
• config file syntax

-level 1 (these are things that builders should ideally learn) basic structure becoming comfortable tab completion up arrow ls (listing files, looking at content) editing - nano, including some configuration file syntax

-post build iwconfig wireless stuff - configuring networks dhclient reading logs dmesg apt-get apt-cache more detail about the file system piping and redirection top conifg file syntax modprobe grub and yaboot commands command line to run printme