Changed the kernel version to the most recent stable one. Updated all README files.
This commit is contained in:
parent
fe195af1ae
commit
e6b5e215f0
@ -2,7 +2,7 @@
|
||||
#
|
||||
# http://kernel.org
|
||||
#
|
||||
KERNEL_SOURCE_URL=http://kernel.org/pub/linux/kernel/v4.x/linux-4.4.6.tar.xz
|
||||
KERNEL_SOURCE_URL=http://kernel.org/pub/linux/kernel/v4.x/linux-4.5.2.tar.xz
|
||||
|
||||
# You can find the latest GNU libc source bundles here:
|
||||
#
|
||||
|
19
src/README
Normal file
19
src/README
Normal file
@ -0,0 +1,19 @@
|
||||
The easiest way to build "Minimal Linux Live" is to run the following script:
|
||||
|
||||
sh build_minimal_linux_live.sh
|
||||
|
||||
Note that the build process requires proper toolchain already installed and
|
||||
configured. Check the project's website for more information:
|
||||
|
||||
http://minimal.linux-bg.org
|
||||
|
||||
I only provide the build scripts. It's entirely up to you to configure and
|
||||
prepare your build environment. I use "Linux Mint" both 32 and 64 bit editions.
|
||||
Your distribution might have different build dependencies but most of the time
|
||||
there is a single meta-package which installs most of the stuff that you need.
|
||||
|
||||
The build proces is slow, so be prepared to wait. In the end you should have
|
||||
the ISO image file "minimal_linux_live.iso" in the same folder where you
|
||||
executed the build process. You can burn the ISO image on CD/DVD or (better)
|
||||
run it with PC emulator like QEMU or VirtualBox.
|
||||
|
@ -1,3 +0,0 @@
|
||||
TODO - add basic instructions about the build dependencies, how to run the build
|
||||
process and what to expect as final result.
|
||||
|
27
src/config_predefined/README
Normal file
27
src/config_predefined/README
Normal file
@ -0,0 +1,27 @@
|
||||
The build process allows you to use predefined configuration files for the
|
||||
kernel and for BusyBox. This is what you need to do in order to use your own
|
||||
predefined configuration files:
|
||||
|
||||
1) First of all you need to have ".config" configuration file. The assumption is
|
||||
that you already know what ".config" file is and how it is used during the
|
||||
kernel & BusyBox build process. Take the ".config", place it in this folder
|
||||
and finally rename the file. The predefined configuration file name is:
|
||||
|
||||
kernel.config - for kernel (obviously)
|
||||
busybox.config - for BusyBox (what a surprise)
|
||||
|
||||
2) Change the corresponding property in ".config" (that's the minimal's config
|
||||
file, you dumbass) to value "true":
|
||||
|
||||
USE_PREDEFINED_KERNEL_CONFIG - for kernel
|
||||
|
||||
USE_PREDEFINED_BUSYBOX_CONFIG - for BusyBox
|
||||
|
||||
3) That's it. Now during the build process instead of generating default
|
||||
".config" files, the predefined configuration files will be used, That's
|
||||
particularly useful if you want to experiment with many non-default config
|
||||
options. In this case it's easier to use configuration file instead of using
|
||||
the scripts in order to generate tons of options. Another useful scenario is
|
||||
when you distribute your OS based on "Minimal Linux Live" and you want to use
|
||||
non-default kernel and/or BusyBox options "out of the box".
|
||||
|
@ -1,5 +0,0 @@
|
||||
TODO 1- add documentation about this folder and the purpose of the predefined
|
||||
configuration file.
|
||||
|
||||
TODO 2 - Edit all comments and readme files to use maximum 80 chars per line.
|
||||
|
Loading…
x
Reference in New Issue
Block a user