Skip to content
/ CLIP Public
forked from sshimko/CLIP

Spencer's Dev Playground for CLIP (you probably want QuarkSecurity/CLIP which is where my stuff gets merged)

Notifications You must be signed in to change notification settings

qswain2/CLIP

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Here is a quick list of the things you need to do to get started.

Big Hint/Suggestion: if you use Quark Security's build VM you can skip steps 1-4. Why not make your life easier by downloading it: Quark Security's CLIP build VM

  1. Add your user to /etc/sudoers (required since mock and livecd creator use chroots).

Note that this line is required to generate media.

  1. CHANGE THE DEFAULT PASSWORD IN YOUR KICKSTART (kickstarts/clip-minimal/clip-minimal.ks)! CLIP intentionally ships with an unencrypted default password! It is "neutronbass".
    DO NOT LEAVE THIS PASSWORD LINE INTACT!

  2. Go back and re-read #2.

  3. Run "./bootstrap.sh".

  4. After you have run bootstrap once you do not have to run it again. Roll an ISO by running "$ make clip-minimal-inst-iso". This will generate an installable ISO. Alternatively, run "$ make clip-minimal-live-iso" to generate a live media ISO.

Note: for a complete list of targets available please run "$ make help".

After you have successfully rolled an installation ISO it is time to move on to customizing the image. Each topic related to customizing the image is discussed in Help-*.txt files in the root of the CLIP repo.

For general questions please reference Help-FAQ.txt. For more detailed instructions, you may reference the following:

  1. Help-Adding-Existing-Binary-Packages-to-Image.txt

    Assistance for adding binary packages to a rolled ISO.

  2. Help-Adding-Source-Packages.txt

    Assistance for adding source packages to the build system.

  3. Help-Build-System.txt

    Assistance in setting up the build system.

  4. Help-Generating-Live-Media.txt

    How to generate live media.

  5. Help-Known-Issues.txt

    A list of currently known issues and how to get past them.

  6. Help-Releases.txt

    Help in getting a CLIP release out.

  7. Help-Use-Cases.txt

    How to best use CLIP for specific scenarios.

About

Spencer's Dev Playground for CLIP (you probably want QuarkSecurity/CLIP which is where my stuff gets merged)

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Roff 73.4%
  • Python 11.5%
  • Makefile 9.2%
  • Shell 2.3%
  • M4 1.9%
  • C 1.4%
  • Other 0.3%