Difference between revisions of "Clean Up the Pidora Kickstart File"
(→Blogs) |
(→Goals by Release) |
||
Line 42: | Line 42: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
− | * 0.1 - Identify all the packages listed in the recent version of a kickstart file and remove unnecessary packages. Create a dependent sub-file containing the packages and link it with | + | * 0.1 - Identify all the packages listed in the recent version of a kickstart file and remove unnecessary packages from the kickstart file. Create a dependent sub-file containing the packages and link it with the kickstart file. |
* 0.2 - Keep removing unnecessary packages on the kickstart file. | * 0.2 - Keep removing unnecessary packages on the kickstart file. |
Revision as of 14:23, 18 November 2013
Contents
Clean Up the Pidora Kickstart File
Project Description
The kickstart file allows Pidora to be installed with the pre-setup configuration, unattended. The goal of this project is to prevent the unnecessary packages from being installed, which contributes the small storage maximization. Also, by configuring SELinux in the kickstart file, it will boost up the booting speed of Pidora that is not as powerful as the regular computer is.
Project Leader
Yonghoon Shin
Project Contributor(s)
Project Details
Assignment
- Minimize the number of packages and create the kickstart-dependent sub-file, which will also potentially enhance the boot speed
Project Plan
Tracking
Key contacts
Andrew Greene
Goals by Release
Goals for each release and plans for reaching those goals:
- 0.1 - Identify all the packages listed in the recent version of a kickstart file and remove unnecessary packages from the kickstart file. Create a dependent sub-file containing the packages and link it with the kickstart file.
- 0.2 - Keep removing unnecessary packages on the kickstart file.
- 0.3 - Fix some critical bugs when necessary and re-package it.
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
Non-Seneca Participants
Planets
Project News
Oct. 9th / 2013 - Start!
Nov. 8th / 2013 - A package list has been separated as a file named pkg.ks.
Nov. 15th / 2013 - An updated gg script to find dependencies of packages has been created and updated.
Nov. 18th / 2013 - My kickstart file with a package list file is going to be released as version 0.1.