Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lipck
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
osak
lipck
Commits
eef7c3f3
Commit
eef7c3f3
authored
9 years ago
by
Christopher Spinrath
Browse files
Options
Downloads
Patches
Plain Diff
README: HowTo & Tips
parent
ea65e1d0
Branches
Branches containing commit
No related tags found
1 merge request
!1
New Readme
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+58
-0
58 additions, 0 deletions
README
with
58 additions
and
0 deletions
README
+
58
−
0
View file @
eef7c3f3
...
...
@@ -8,6 +8,7 @@ Content
1. About
2. Requirements
3. HowTo
4. Tips
License
-------
...
...
@@ -73,3 +74,60 @@ And, optionally,
HowTo
-----
In short: run
$ make WORKSPACE=/media/drivewithspace config
# make image
# make repo #build offline repository (optionally)
# make IMAGE_FILE=/somewhere/myfinalimage.img image_deploy
# make IMAGE_FILE=/somewhere/myfinalimage.img image_deploy_vmdk
where the first command should be executed as user (the owner of the lipck git)
and all others as root. /media/drivewhitspace should provide enough disk space
to store the basic isos, the extracted rootfs/initramfs, etc. (~40G should
suffice). image_deploy will assemble the final (raw) image. The last command
is optional again (note that IMAGE_FILE should have the same value as in the
previous line).
In practise, you may want to edit some configuration files/patches prior to
invoking make as described above:
- the most important config file is config/Makefile.conf where, among others,
the base iso can be configured. See config/examples for more details.
- contrib/rootfs/{hold_packages,pre_installed_packages*} lets you control the
packages that will be installed preinstalled in the rootfs.
- contrib/rootfs/offline_repo.json defines all packages available in the
offline repository.
- Files in contrib/rootfs/{modprobe.d,skel,sysctl.d} will be copied as is
to the corresponding folders in the rootfs.
- patches/{initrd,iso,rootfs} contains patches for the initramfs,
iso/images root, and the rootfs. Probably they have to be adapted for
new iso base images. Unfortunaly, version/iso specific patches are not
supported yet.
Lastly, you may want to spawn a shell in the rootfs being remastered with
# make rootfs_console
to debug stuff.
Tips
-----
- If the rootfs_remaster target failed, it may the neccessary to execute the
next make command two times (the first time a dirty state will be discovered
and fixed).
- code executed in the rootfs is located in scripts/, you may need to execute
# make rootfs_finalize
to trigger a reload of this code.
Happy hacking!
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment