-
Notifications
You must be signed in to change notification settings - Fork 0
a2o/kernel
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
############################################################################### # # Workflow # ############################################################################### Naming convention for branches ------------------------------ a2o <--- main branch of kernel config files cmpny <--- main branch for certain company cmpny/mchn <--- machine specific branch Naming convention for config files ---------------------------------- config64-2.6.35.5 <--- 64bit config for kernel version 2.6.35.5 config32-2.6.35.5 <--- x86 config for kernel version 2.6.35.5 Naming convention for kernels ----------------------------- kernel64-2.6.35.5-asdf33 <--- asdf33 is the signature of git commit kernel32-2.6.35.5-asdf34 <--- 32bit, asdf34 is the signature of git commit How to make changes to kernel ----------------------------- - checkout appropriate branch - pull commits from a2o branch - create new config, don'commit just yet - compile kernel and test it - commit - push - if change should be adopted to other systems as well, merge it to a2o branch and push - other branches should be synced when appropriate kernel are upgraded How to port configuration to new kernel --------------------------------------- - untar kernel - copy latest config64 (or config) to it - make menuconfig - save the configuration - compare old and new config: ---> sort the config64 in repo (commit is not needed, but use scripts) ---> sort the .config in kernel source ---> make diff of the sorted files ---> check what is changed, if anything relevant, fix - move it to repo as config64 - commit - push - start doing changes, wash, rinse, repeat:)
About
Linux kernel configuration for servers
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published