CMIT 291 is UMGC's introduction to administering the Linux operating system from the command line.
UMGC describes it as a study of Linux with the goal of configuring and managing processes, user interfaces, device files, print facilities, file systems, task automation, the boot and shutdown sequence, disk storage, network connectivity, system security, and users and groups.
It is designed to help prepare for the Linux Professional Institute Certification 1 (LPIC-1) and CompTIA Linux+ exams.
Students coming from Windows often find the command line intimidating at first. The breakthrough comes when you understand that most administration is just reading and editing text files with a handful of commands.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Course code | CMIT 291 |
| Level | Undergraduate, 3 credits |
| Prerequisite | CMIT 202 or CMIT 265 |
| Certification link | Designed to help prepare for LPIC-1 and CompTIA Linux+ |
| Credit overlap | Credit for only one of CMIS 390, CMIS 398U, CMIT 291 or CMIT 391 |
What CMIT 291 Covers
| Area (from UMGC's list) | Typical tools and ideas |
|---|---|
| Processes | ps, top, kill, job control |
| File systems and storage | Partitions, mounting, the directory hierarchy |
| Users and groups | useradd, passwd, groups, sudo |
| Task automation | Shell scripts, cron |
| Boot and shutdown | Boot loader, systemd targets |
| Networking | ip, ping, name resolution |
| Security | Permissions, updates, basic firewalling |
Key Concepts Explained
File Permissions
Every file has read, write and execute permissions for its owner, its group and everyone else. Numeric notation adds 4 (read), 2 (write) and 1 (execute) for each.
Example: chmod 750 backup.sh gives the owner 7 (read, write, execute), the group 5 (read, execute) and others 0 (nothing). The script can be run by its owner and group members but is hidden from other users.
Everything Is a File
Linux exposes devices as files under /dev and system information under /proc. This is why UMGC lists device files as a topic: the same tools that read text can inspect hardware and processes.
Automating with Cron
Cron runs commands on a schedule using five time fields: minute, hour, day of month, month and day of week.
Example: 30 2 * * 0 /home/admin/backup.sh runs the backup script at 02:30 every Sunday.
A First Shell Script
Task automation is one of UMGC's listed goals, and short Bash scripts are the usual starting point. A good script states its interpreter, uses variables and checks for errors.
Example: A script that archives a home directory might set SRC=/home/student and DEST=/backup/home-$(date +%F).tar.gz, run tar -czf "$DEST" "$SRC", then test $? and print "Backup complete" or "Backup failed". Scheduled with cron, it becomes a simple nightly backup job.
Quote variables, make the file executable with chmod +x, and test with harmless paths before pointing a script at anything important.
Getting the Most from Linux Labs
Linux courses are lab-heavy, and the labs reward a careful habit: read the man page, run the command, check the result. When something fails, the error message usually says why.
- Use
manand--helpbefore searching online. - Check your current directory and user before running anything destructive.
- Copy configuration files before editing them.
- Keep a personal cheat sheet of commands that worked.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Command-line labs | Practical administration | Show commands and output, then explain |
| Shell scripts | Task automation | Comment each section and test edge cases |
| Configuration tasks | Users, storage, networking | Verify the change and record proof |
| Quizzes | Command and concept recall | Practice in a terminal, not only from notes |
Where Students Get Stuck
- Permissions errors. Many failures come from running as the wrong user.
- Paths. Relative versus absolute paths cause many "file not found" errors.
- Distribution differences. Package managers and some tools vary between distributions.
- Script syntax. Spaces matter in shell tests and assignments.
Study Tips for CMIT 291
- Install a Linux virtual machine and use it daily, even briefly.
- Practice permissions until numeric and symbolic forms are second nature.
- Read the LPIC-1 or Linux+ objectives to see what to prioritize.
- Write one small script a week that automates something real.
How We Help with CMIT 291
Send the lab instructions, rubric and your terminal output or scripts. A Linux tutor can explain commands, debug a script with you, or review your lab write-up. For presenting technical work, see our lab report guide.
GradeEssays is independent of the University of Maryland Global Campus, the Linux Professional Institute and CompTIA. We tutor and explain; we never take quizzes or certification exams, or log in to your classroom or lab systems.
Get Comfortable with Linux for CMIT 291
Share the assignment and your output. A Linux tutor prepares worked command walkthroughs you can learn from.
Start My CMIT 291 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
UMGC lists CMIT 202 or CMIT 265.
UMGC says it is designed to help prepare for LPIC-1 and CompTIA Linux+. The exams are taken separately.
UMGC states credit is allowed for only one of CMIS 390, CMIS 398U, CMIT 291 or CMIT 391.
UMGC lists it as a 3-credit undergraduate course.
No. Basic shell scripting is covered as part of task automation.
Yes. Send the script, the task and the error, and we explain the problem and the fix.