Linux Workgroup

From Voidwarranties - Hackerspace Antwerp, Belgium
(Difference between revisions)
Jump to: navigation, search
(Knowledge Jobj)
 
(43 intermediate revisions by 10 users not shown)
Line 3: Line 3:
 
|Category=Coding
 
|Category=Coding
 
|Logo=Linux.gif
 
|Logo=Linux.gif
|Participants=Tom, Jeffrey, Jobj, Wim, Koert,  
+
|Participants=Tom, Jeffrey, Jobj, Wim, User:Ivom, Firemonkey, Skawouter
 
|Locations=Den Bunker,
 
|Locations=Den Bunker,
 +
|Events=Linux workshop nummer 1,Linux workshop numero due, Linux Workshop number three, Linux Workshop number 4, Linux Workshop number 5,
 
|Short description=We teach our selves linux
 
|Short description=We teach our selves linux
 
}}
 
}}
==About==
+
=About=
Workgroup on Linux..
+
  
If you have sugestions, feel free to use the Discussion page of this project
+
The goal in this project is: "To study the in- and outs of the GNU/Linux system and discuss your findings at regular bi-weekly saturday evenings". On the one hand it can help you prepare for the LPI certifications, but it can prove  valuable to exchange you personal knowledge with others in the space.
 +
 
 +
We use study material related to LPIC-1 and LPIC-2 directly taken from the LPI people. For your convenience the detailed objectives are listed below. Feel free to jump in or out, when you feel like:
 +
* the ''Junior Level Linux Professional'' [http://www.lpi.org/eng/certification/the_lpic_program/lpic_1/exam_101_detailed_objectives LPIC-1 101],
 +
* the ''Junior Level Linux Professional'' [http://www.lpi.org/eng/certification/the_lpic_program/lpic_1/exam_102_detailed_objectives LPIC-1 102]
 +
* the Advanced Level Linux Professional [http://www.lpi.org/eng/certification/the_lpic_program/lpic_2/exam_201_detailed_objectives LPIC-2 201],
 +
* the Advanced Level Linux Professional [http://www.lpi.org/eng/certification/the_lpic_program/lpic_1/exam_202_detailed_objectives LPIC-2 202]
 +
 
 +
The most recent version of the study material can be found [http://www.nongnu.org/lpi-manuals/manual/ here].
 +
 
 +
Please note, that not all documentation is very up-to-date compared to the current objectives. By reading the course material you might sometimes be taken on some sort of historical safari. The documentation was last updated since 2005. With the objectives more recent, you might argue we are not reading the right documents, but let's see what the LPI publishes this year, and then ask them for the ''What's new'' documents :)
 +
 
 +
==Course structure==
 +
 
 +
After three meetings the group has stabilised to 3 people attending and following the subjects. Feel free to join any time however. When you do, please study the chapters in advance as planned for the upcoming meeting. --[[User:Ivom|Ivom]] 13:03, 17 April 2011 (CEST)
 +
 
 +
==Who is the tutor?==
 +
Nobody is! Current practice is to study the planned course material in advance and mark questions for yourself that come up during studying the material. This seems to work for us.
 +
 
 +
==Meeting structure==
 +
When the meeting starts the chapters are mentioned and the emphasis is chosen depending on the demand to discuss questions surrounding the subject. For every chapter the questions at the end are solved together as well. Also, the intent is to round off the meeting with all the planned chapters covered.
 +
 
 +
= Schedule =
 +
We meet on saturday on a bi-weekly schedule (yes, you are hard-pressed to keep up to speed).
 +
 
 +
The schedule is as follows:
 +
== First class LPIC-1 101==
 +
* Introduction
 +
* Installation
 +
* Hardware Configuration
 +
* Managing Devices
 +
 
 +
== Second class LPIC-1 101==
 +
* The Linux Filesystem
 +
Check [http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS] for an up to date list of the regular file system layout you will likely find in GNU/Linux and the UNIX distributions
 +
 
 +
== Third class LPIC-1 101==
 +
* The Command Line
 +
 
 +
== Fourth class LPIC-1 101==
 +
* File Management
 +
* Process Management
 +
* Text Processing
 +
* Software Installation
 +
 
 +
== Fifth class LPIC-1 101==
 +
* Advanced Text Manipulation
 +
* Using VI (the roman numeral)
 +
* The X Environment
 +
 
 +
So for LPIC-101 That means reading through a 150 page book in 10 weeks. After that the LPI-2 is the next set of books to be studied. Debating whether this structure is a good idea is open to discussion. Please vent experiences on the talk page.
 +
 
 +
Please help update this part of the wiki page, with short notes and info that emerge during the meetings. Don't add to much per subject to keep the structure readable.
 +
 
 +
=Z participants=
  
 
==Knowledge Jeffrey==
 
==Knowledge Jeffrey==
Line 73: Line 127:
 
* What I need to know I look up
 
* What I need to know I look up
 
* I'm not an expert, but a strong believer in "google is your friend"
 
* I'm not an expert, but a strong believer in "google is your friend"
* due to the ease of use of ubuntu (GUI and apt-get and howto's on the net I'm not realy stimulated to go dig deeper, and I'd like to change that.  
+
* due to the ease of use of ubuntu (GUI and apt-get and howto's on the net) I'm not realy stimulated to go dig deeper, and I'd like to change that.  
 
* Atm I'm using Ubuntu, before that I used slackware, because it doesn't have fancy let-me-do-all-that-for-you-automagically-gui's and scripts and stuff, and so forced me to learn how to do stuff myself more
 
* Atm I'm using Ubuntu, before that I used slackware, because it doesn't have fancy let-me-do-all-that-for-you-automagically-gui's and scripts and stuff, and so forced me to learn how to do stuff myself more
*the biggest issue is that once you have configured somting in Linux you dont have to bother for it anymore so when you do need it again you forgot how to do it (Configure grub in a correct way for dual boot after a new install)
+
*the biggest issue is that once you have configured someting in Linux you don't have to bother for it anymore so when you do need it again you forgot how to do it (Configure grub in a correct way for dual boot after a new install)
 
**therefore I think it might be handy to build a knowledgebase of what we discover ..
 
**therefore I think it might be handy to build a knowledgebase of what we discover ..
  
Line 90: Line 144:
 
* when something goes wrong I usually know how to fix it.
 
* when something goes wrong I usually know how to fix it.
 
* a lot of other stuff :)
 
* a lot of other stuff :)
 +
 +
==Knowledge [[User:Ivom|Ivom]]==
 +
* Been using Linux since about the year 2000 (linuxppc, gentoo for a while, currently stuck with ubuntu). Using, means working with the basic tools that are in the GUI domain to read and communicate
 +
* Programming knowledge: java, python, shell-scripting, C (rather rusty, as I don't need it much)
 +
* The basic sysadmin jobs under Linux I know how the get done, usually by means of trawling the web and see how other do things
 +
* Choose to virtualise some services at home for stability reasons.
 +
* For what I understand the workshop goes further than the kernel alone. I propose to look at how the kernel works and how the low level stuff is attached to the rest (I am thinking of udev, kernel modules, filesystems and the like). In that domain is stuff I definetly haven't delved too much.
 +
 +
==Knowledge Quentin==
 +
*Been playing with linux for years using various distributions
 +
*Using Ubuntu as my main OS for 5 years
 +
*Thinking about moving away from Ubuntu, preferably to a rolling release distro (Debian Testing, Arch)
 +
*Am interested in the inner workings of the Linux/GNU system in general and in manual configuration and troubleshooting of desktop systems specifically
 +
*Seems my current approach (googling when I encounter problems) is too ad-hoc since I often have to search for the same things time and time again. A comprehensive introduction might help, as would documenting solutions on my side
 +
 +
==Knowledge Firemonkey==
 +
*I have been using linux/unix for servers around 10 years. And linux desktop environment for about 2 years.
 +
*Most experience with Ubuntu, Redhat, BSD and CentOS
 +
*Scripting knowledge: Bash, Perl, PHP, Yaml, ...
 +
*Programming knowledge: c, c++, Dynamic c.
 +
*Good knowledge about LAMP, MAIL, DNS and PKI configurations.
 +
*I know most apps/commands like vi, tail, grep, piping, cat, ... (Sysadmin stuff)
 +
*Created public terminals with costum linux distro (Touch screen interfaces @ technopolis).

Latest revision as of 19:52, 29 July 2011


Linux Workgroup
What:
We teach our selves linux
Linux.gif
Participants:
Tom, Jeffrey, Jobj, Wim, User:Ivom, Firemonkey, Skawouter
Category:
Coding
Locations:
Den Bunker
Events:
Linux workshop nummer 1, Linux workshop numero due, Linux Workshop number three, Linux Workshop number 4, Linux Workshop number 5

Contents

About

The goal in this project is: "To study the in- and outs of the GNU/Linux system and discuss your findings at regular bi-weekly saturday evenings". On the one hand it can help you prepare for the LPI certifications, but it can prove valuable to exchange you personal knowledge with others in the space.

We use study material related to LPIC-1 and LPIC-2 directly taken from the LPI people. For your convenience the detailed objectives are listed below. Feel free to jump in or out, when you feel like:

The most recent version of the study material can be found here.

Please note, that not all documentation is very up-to-date compared to the current objectives. By reading the course material you might sometimes be taken on some sort of historical safari. The documentation was last updated since 2005. With the objectives more recent, you might argue we are not reading the right documents, but let's see what the LPI publishes this year, and then ask them for the What's new documents :)

Course structure

After three meetings the group has stabilised to 3 people attending and following the subjects. Feel free to join any time however. When you do, please study the chapters in advance as planned for the upcoming meeting. --Ivom 13:03, 17 April 2011 (CEST)

Who is the tutor?

Nobody is! Current practice is to study the planned course material in advance and mark questions for yourself that come up during studying the material. This seems to work for us.

Meeting structure

When the meeting starts the chapters are mentioned and the emphasis is chosen depending on the demand to discuss questions surrounding the subject. For every chapter the questions at the end are solved together as well. Also, the intent is to round off the meeting with all the planned chapters covered.

Schedule

We meet on saturday on a bi-weekly schedule (yes, you are hard-pressed to keep up to speed).

The schedule is as follows:

First class LPIC-1 101

Second class LPIC-1 101

Check FHS for an up to date list of the regular file system layout you will likely find in GNU/Linux and the UNIX distributions

Third class LPIC-1 101

Fourth class LPIC-1 101

Fifth class LPIC-1 101

So for LPIC-101 That means reading through a 150 page book in 10 weeks. After that the LPI-2 is the next set of books to be studied. Debating whether this structure is a good idea is open to discussion. Please vent experiences on the talk page.

Please help update this part of the wiki page, with short notes and info that emerge during the meetings. Don't add to much per subject to keep the structure readable.

Z participants

Knowledge Jeffrey

I've been messing around with Linux for years, and usually I get the things done with some research.

Everything I know I've learned by myself (by experience). Hence I wouldn't call myself an expert.

I think I'm still missing some global background, so some extra education is welcome.

Examples of things I've done before:

Things I want to learn more about:

Knowledge Tom

I've been using Linux for 2 years now. I've got Linux installed on 2 laptops and one netbook, and it's on my desktop in a vm. (reason for that is that i need Win7 for school). The goal would be to make the switch, after finnishing school.

I would describe myself as a novice.

I received some teachings @ CVO (module netwerkbeheer 2), about linux, but they covered mostly basic stuff.

As there was;

I'm reading and learning about Linux on my own for now. (the progress i make, depends on how much work i have to do for school) I have some knowledge about vim (i know how to use it, but that's it, didn't want to go for emacs..Looks a bit scary..)

The things i would like to learn more about are mostly the same as Jeffrey's.

Knowledge Jobj

Knowledge Wouter(antwerp)

Knowledge Ivom

Knowledge Quentin

Knowledge Firemonkey

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Content Creation
Belgian Spaces