Changeset 3232 in MondoRescue for branches/3.2/mindi-busybox/INSTALL
- Timestamp:
- Jan 1, 2014, 12:47:38 AM (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/3.2/mindi-busybox/INSTALL
r2725 r3232 48 48 Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH 49 49 to be set appropriately, depending on whether or not /proc/self/exe is 50 available or not. If you do not have /proc, then point that config option50 available. If you do not have /proc, then point that config option 51 51 to the location of your busybox binary, usually /bin/busybox. 52 Another solution is to patch the kernel (see 53 examples/linux-*_proc_self_exe.patch) to make exec("/proc/self/exe") 54 always work. 52 55 53 56 Configuring Busybox: … … 71 74 "make allbareconfig" (enables all applets but disables all optional features), 72 75 "make allyesconfig" (enables absolutely everything including debug features), 73 and "make randconfig" (produce a random configuration). 76 and "make randconfig" (produce a random configuration). The configs/ directory 77 contains a number of additional configuration files ending in _defconfig which 78 are useful in specific cases. "make help" will list them. 74 79 75 80 Configuring BusyBox produces a file ".config", which can be saved for future … … 98 103 a list of all enabled applets.) The standalone shell can also call busybox 99 104 applets without links to busybox under other names in the filesystem. You can 100 also configure a standa one install capability into the busybox base applet,105 also configure a standalone install capability into the busybox base applet, 101 106 and then install such links at runtime with one of "busybox --install" (for 102 107 hardlinks) or "busybox --install -s" (for symlinks).
Note:
See TracChangeset
for help on using the changeset viewer.