Difference between revisions of "User:Lynnae"
Line 3: | Line 3: | ||
− | Laptop As-Is Build Guide Update | + | ==Laptop As-Is Build Guide Update== |
Grabbed a Pentium II thinkpad, installed a 10GB HDD with Debian Squeeze installed with basic packages only, and no desktop environment. Created a user. Installed bsdgames. Sean did something so that the game paths are linked to the user home directory. | Grabbed a Pentium II thinkpad, installed a 10GB HDD with Debian Squeeze installed with basic packages only, and no desktop environment. Created a user. Installed bsdgames. Sean did something so that the game paths are linked to the user home directory. | ||
Line 30: | Line 30: | ||
User: root | User: root | ||
Password: freegeek | Password: freegeek | ||
+ | |||
+ | |||
+ | ==Laptop Build Teaching Module== | ||
+ | |||
+ | Next steps: | ||
+ | *writing example for each section | ||
+ | |||
+ | for every section have identifiable instructor and builder goals | ||
+ | have two versions: one for new builders, and a reminder help sheet for experienced builders to guide them along | ||
+ | |||
+ | each module has specific exercises to be completed that double in function as a testing step | ||
+ | |||
+ | after the builder completes some guided builds and demonstrates needed skills, they can use the abbreviated testing steps | ||
+ | |||
+ | Physical Parts check | ||
+ | power supply | ||
+ | HDD install | ||
+ | check keeper label | ||
+ | |||
+ | Intro to BIOS and POST | ||
+ | what these acronyms stand for | ||
+ | why they are important | ||
+ | what they do | ||
+ | common POST troubleshooting steps | ||
+ | BIOS boot order, and general functional categories to look out for in BIOS | ||
+ | |||
+ | Intro to networking and wireless | ||
+ | parts required: card and driver | ||
+ | helpful terminal commands: rfkill, lspci, iwconfig | ||
+ | BIOS config | ||
+ | |||
+ | Basiccheck | ||
+ | introduction to our homebrew scripts and the freegeek-extras package | ||
+ | |||
+ | Optical Disk Testing | ||
+ | intro to disk utility, terminal and GUI | ||
+ | mount, eject, dmesg | ||
+ | what to do when a disk isn't recognized | ||
+ | ISO burning | ||
+ | |||
+ | Installing programs: | ||
+ | |||
+ | In Linux, software comes in '''packages''', that is a bunch of files bundled into one folder (or '''directory''' as it is called in Linux) with an installation script, that copies the files to the appropriate places in your system for the software to run. '''Repositories''' are places where software packages are stored that you can download via an Internet connection. A '''package manager''' is a program that handles the ins and outs of downloading and installing software from various repositories. There are two package managers we will be using for testing: '''apt-get''' or Aptitude, and a graphical program called the '''Ubuntu Software Center'''. There is another package manager installed on your system called '''Synaptic''', that we will not cover in this lesson. Apt-get is the most powerful of package managers in Ubuntu, followed by Synaptic, but these managers require a bit of background knowledge to be really useful. We're just covering a little bit to get you started. The Ubuntu Software Center is a fairly straightforward way to add or remove software, but is pretty limited when something goes wrong. | ||
+ | |||
+ | Exercises: | ||
+ | Installing programs via the Terminal | ||
+ | Installing programs via the Software Center | ||
+ | |||
+ | Running Updates: | ||
+ | We can run updates for Ubuntu in a couple of different ways. These updates not only provide security updates, fixes, and patches for your operating system, but also updates for programs you have installed. Most sources recommend that you update your system every week or so. Via the command line, we can use the package manager '''apt-get''' to download and install necessary system updates, or a graphical tool called the '''Update Manager'''. Update Manager is similar to the Ubuntu Software Center in that it provides an easy point-and-click environment for apt-get functions, but is less flexible for troubleshooting errors. | ||
+ | |||
+ | Depict the kernel, Aptitude and GUI front-end stuff in goofy cartoon | ||
+ | |||
+ | Exercises: | ||
+ | System updates via the Terminal | ||
+ | System updates via the Update Manager | ||
+ | |||
+ | Keywords: | ||
+ | Package | ||
+ | Repository | ||
+ | Package Manager | ||
+ | Update | ||
+ | |||
+ | https://help.ubuntu.com/community/AptGet/Howto | ||
+ | |||
+ | https://help.ubuntu.com/community/InstallingSoftware | ||
+ | |||
+ | Port and keyboard testing | ||
+ | check usb testing | ||
+ | intro to lsusb (show how ports are show, and how we can see that a device is connected) | ||
+ | download keyboard testing program, test keyboard and trackpad | ||
+ | |||
+ | Printme and final cleaning |
Revision as of 14:52, 23 August 2012
meep. meep.
Laptop As-Is Build Guide Update
Grabbed a Pentium II thinkpad, installed a 10GB HDD with Debian Squeeze installed with basic packages only, and no desktop environment. Created a user. Installed bsdgames. Sean did something so that the game paths are linked to the user home directory.
Tentative plan: Eliminate scraptops, new As-Is spec would be Pentium ii-iii ish with harddrives and light OS installed. Maybe a basic readme with instructions, but no further support ("My First Linux") Machines in the As-Is category that POST with working screens Install 30GB or less HDD, with headless Squeeze install ("proof of concept OS") Install bsdgames or other silly packages, maybe with basic instructions, could have a display store box
selection process: boxes that are aesthetically appealing in some way (not super chunky, cute, whatever) working screen working keyboard and trackpad
next category up (P4 lowend stuff) would include lightweight desktop environment and wireless
New As-Is Label information
Processor Speed HDD y/n If y, size
This Laptop is sold AS-IS, no returns, no warranty. It may be missing parts. We verify that the machine will turn on, and boots Debian (6.0.3 Squeeze). No further testing has been done. See the readme file for basic instructions. User: root Password: freegeek
Laptop Build Teaching Module
Next steps:
- writing example for each section
for every section have identifiable instructor and builder goals have two versions: one for new builders, and a reminder help sheet for experienced builders to guide them along
each module has specific exercises to be completed that double in function as a testing step
after the builder completes some guided builds and demonstrates needed skills, they can use the abbreviated testing steps
Physical Parts check power supply HDD install check keeper label
Intro to BIOS and POST what these acronyms stand for why they are important what they do common POST troubleshooting steps BIOS boot order, and general functional categories to look out for in BIOS
Intro to networking and wireless parts required: card and driver helpful terminal commands: rfkill, lspci, iwconfig BIOS config
Basiccheck introduction to our homebrew scripts and the freegeek-extras package
Optical Disk Testing intro to disk utility, terminal and GUI mount, eject, dmesg what to do when a disk isn't recognized ISO burning
Installing programs:
In Linux, software comes in packages, that is a bunch of files bundled into one folder (or directory as it is called in Linux) with an installation script, that copies the files to the appropriate places in your system for the software to run. Repositories are places where software packages are stored that you can download via an Internet connection. A package manager is a program that handles the ins and outs of downloading and installing software from various repositories. There are two package managers we will be using for testing: apt-get or Aptitude, and a graphical program called the Ubuntu Software Center. There is another package manager installed on your system called Synaptic, that we will not cover in this lesson. Apt-get is the most powerful of package managers in Ubuntu, followed by Synaptic, but these managers require a bit of background knowledge to be really useful. We're just covering a little bit to get you started. The Ubuntu Software Center is a fairly straightforward way to add or remove software, but is pretty limited when something goes wrong.
Exercises: Installing programs via the Terminal Installing programs via the Software Center
Running Updates: We can run updates for Ubuntu in a couple of different ways. These updates not only provide security updates, fixes, and patches for your operating system, but also updates for programs you have installed. Most sources recommend that you update your system every week or so. Via the command line, we can use the package manager apt-get to download and install necessary system updates, or a graphical tool called the Update Manager. Update Manager is similar to the Ubuntu Software Center in that it provides an easy point-and-click environment for apt-get functions, but is less flexible for troubleshooting errors.
Depict the kernel, Aptitude and GUI front-end stuff in goofy cartoon
Exercises: System updates via the Terminal System updates via the Update Manager
Keywords: Package Repository Package Manager Update
https://help.ubuntu.com/community/AptGet/Howto
https://help.ubuntu.com/community/InstallingSoftware
Port and keyboard testing check usb testing intro to lsusb (show how ports are show, and how we can see that a device is connected) download keyboard testing program, test keyboard and trackpad
Printme and final cleaning