Home
Username:
Password:
CompTIA Linux+ Certification 2009 Tutorials

Package Management & Repositories / Source Code & More




Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com’s entire library of video tutorials.


Learn More

Subtitles of the Movie

Source Code and More. Before the development of the Red Hat and Debian Package Management Systems Linux was distributed as compilable source code. Such code is generally made available in compressed archives. Examples of such archives are associated with the Linux Kernel and are available from Kernel.org. As shown here kernels are made available in the tar.gz and tar.bz2 formats, also known as the gzip and bzip formats. I typically download Linux Kernels to the user/source directory and as an example I've downloaded a bzip Linux source code which I can then uncompress with the bzip2 -d command. In contrast, if I had downloaded a gzip compressed kernel I could uncompress it with a gzip -d command. You can then unpack the archive with the appropriate tar command with the x switch it would extract the files from the archive but it's a lot more convenient to combine the commands. The tar command can uncompress from both gzip and bzip2 compressed archives. For example, the tar xzf command applied to a gzip compressed archive would both uncompress and unpack or unarchive that particular file. If you have a bzip archive just substitute a j for the z. Once such source code is unpacked, configuration scripts are frequently made available in that directory with names like install or configure. Generally they are configured with executable permissions and such executables are normally configured or created with package tools available from the autoconf package. If you don't see one of these files in the unpacked directory there's an alternative. You can compile the code manually with various make tools. The Make command by itself would compile the code but you shouldn't compile anything unless the current "underlying" source code is clean. I would demonstrate some of this but with the Linux Kernel such compiling can take as long as several hours, so just in general to make sure that the underlying source code is clean you should first run the make clean command. If there are dependencies associated with this particular package, as is true with the Linux Kernel, the next appropriate command is make dep to properly connect any required dependencies. Then you can compile the source code with the make command and then process what was compiled for installation with the make install command in that order. Well, that's the scoop associated with the management of Source Code. Thank you and you're ready for another video.

Tutorial Information

Course: CompTIA Linux+ Certification 2009
Author: Michael Jang
SKU: 34070
ISBN: 1-935320-91-2
Release Date: 2009-12-22
Duration: 6.5 hrs / 82 lessons
Captions: Available on CD and Online University
Compatibility: Vista/XP/2000, OS X, Linux
QuickTime 7, Flash 8

VTC Sign up & Benefits

  • Unlimited Access
  • 98,729 Video Tutorials (23,265 free)
  • Video Available as Flash or QuickTime
  • Over 1026 Courses
  • $30 for One Month Access
  • Multi-User Discounts Available