Sponsored Content
Full Discussion: build kernel ,question?
Operating Systems BSD build kernel ,question? Post 65236 by echan on Thursday 3rd of March 2005 05:48:38 PM
Old 03-03-2005
 

10 More Discussions You Might Find Interesting

1. HP-UX

A kernel question

Hi, I have one boot disk (root disk) that is made for an HP visualize 132. Then I want to use this boot disk with his original installation in a visualize 180. Of course it doesnt work!! I was thinking to fix the problem what I have to do is to make a new kernel for the visualize 180. Does I am... (4 Replies)
Discussion started by: pmoren
4 Replies

2. UNIX for Dummies Questions & Answers

Some simple question abt Unix kernel

Dear all, I got some questions abt how does the Unix kernel work with the work with the other components. (step by step) Can any body tell me some info abt that? if can provide a example for each question that gonna be perfect! Thank you!!! 1. How file management system work together... (2 Replies)
Discussion started by: melbdavid
2 Replies

3. Shell Programming and Scripting

question to build a shell script

Hi All, I want to develope a script. can you please give me solution to this script? Several Processes Reporting Status back to a Master Write two programs that communicate using message queues. One program (the master) will receive messages periodically sent by multiple copies of the... (5 Replies)
Discussion started by: vishalpatel03
5 Replies

4. SCO

Installation error for Kernel Re-build

Hi All, While installing a Service Pack on my Unix Solaris machine, i got the following error: UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME" UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies

5. UNIX for Advanced & Expert Users

Kernel Question

Hello, I am reading a book during my leisure time and it has the following question which I cannot find in the book: -How are data transferred between a process and the kernel? What alternatives are available? If you could provide some feed back it would be greatly appreciated. Thanks! ... (2 Replies)
Discussion started by: andriod
2 Replies

6. UNIX Benchmarks

FreeBSD 7.2 build kernel benchmarks

Just for fun: CPU/Speed: 2x AMD Opteron Model 2384 (2.7GHz/512KB) quad core processor Ram: 4 x2GB ECC DDR2-667 single rank memory in RAID 0 mode (strip 128KB, Read Caching enabled, Write Caching disabled) with 2 HDD, CPUTYPE=opteron, CFLAGS= -O2 -fno-strict-aliasing -pipe, CXXFLAGS+=... (0 Replies)
Discussion started by: Success_Tree
0 Replies

7. Linux

Linux Shared Library build question...

I'm a bit new to Linux systems programming. I've been programming at the systems level for over 20 years on various other platforms, but I'm not as familiar with the GCC toolchain as I'd like to be (but I'm learning quickly)...;)... Our target is an ARM-based Linux Embedded system. We're using... (3 Replies)
Discussion started by: jcossette
3 Replies

8. UNIX for Dummies Questions & Answers

Adding SDK Build on Kernel Source Build

Hi, So I downloaded this kernel source and was able to build it successfully. But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself. I added the SDK in the main Makefile: init-y := init/ #added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies

9. Linux

Create a bootable PXE image from build kernel source code

Hi, Can i just ask how I can create a bootable PXE image from the built kernel source. What files do I need to get? Thanks! (1 Reply)
Discussion started by: h0ujun
1 Replies

10. BSD

A question about BSD kernel and driver

I have an old hppa workstation install Openbsd on it,suppose i want to use bktr driver on it,i see bktr is configured on some archs(amd64,i386,ppc) but not on hppa,can i use the bktr driver line from amd64 or i386 in Generic kernel or custom kernel config? (3 Replies)
Discussion started by: Linusolaradm1
3 Replies
NANOBSD(8)						    BSD System Manager's Manual 						NANOBSD(8)

NAME
nanobsd.sh -- utility used to create a FreeBSD system image suitable for embedded applications SYNOPSIS
nanobsd.sh [-bhknw] [-c config-file] DESCRIPTION
The nanobsd.sh utility is a script which produces a minimal implementation of FreeBSD (called NanoBSD), which typically fits on a small media such as a Compact Flash card, or other mass storage medium. It can be used to build specialized install images, designed for easy installa- tion and maintenance. The following options are available: -b Skip the build stages (both for kernel and world). -c config-file Specify the configuration file to use. -h Display usage information. -k Skip the buildkernel stage of the build. -n Do not cleanup before each build stage. This suppresses the normal cleanup work done before the buildworld stage and adds -DNO_CLEAN to the make command line used for each build stage (world and kernel). -w Skip the buildworld stage of the build. The features of NanoBSD include: o Ports and packages work as in FreeBSD. Every single application can be installed and used in a NanoBSD image, the same way as in FreeBSD. o No missing functionality. If it is possible to do something with FreeBSD, it is possible to do the same thing with NanoBSD, unless the specific feature or features were explicitly removed from the NanoBSD image when it was created. o Everything is read-only at run-time. It is safe to pull the power-plug. There is no necessity to run fsck(8) after a non-graceful shutdown of the system. o Easy to build and customize. Making use of just one shell script and one configuration file it is possible to build reduced and customized images satisfying any arbitrary set of requirements. NanoBSD Media Layout The mass storage medium is divided into three parts by default (which are normally mounted read-only): o Two image partitions: code#1 and code#2. o The configuration file partition, which can be mounted under the /cfg directory at run time. The /etc and /var directories are md(4) (malloc backed) disks. The configuration file partition persists under the /cfg directory. It contains files for /etc directory and is briefly mounted read-only right after the system boot, therefore it is required to copy modified files from /etc back to the /cfg directory if changes are expected to persist after the system restarts. BUILDING NanoBSD A NanoBSD image is built using a simple nanobsd.sh shell script, which can be found in the src/tools/tools/nanobsd directory. This script creates a bootable image, which can be copied on the storage medium using the dd(1) utility. The necessary commands to build and install a NanoBSD image are: cd /usr/src/tools/tools/nanobsd sh nanobsd.sh cd /usr/obj/nanobsd.full dd if=_.disk.full of=/dev/da0 bs=64k CUSTOMIZING NanoBSD This is probably the most important and most interesting feature of NanoBSD. This is also where you will be spending most of the time when developing with NanoBSD. Customization is done in two ways: o Configuration options. o Custom functions. With configuration settings, it is possible to configure options passed to both the buildworld and installworld stages of the NanoBSD build process, as well as internal options passed to the main build process of NanoBSD. Through these options it is possible to cut the system down, so it will fit on as little as 64MB. You can use the configuration options to trim down the system even more, until it will consist of just the kernel and two or three files in the userland. The configuration file consists of configuration options, which override the default values. The most important directives are: NANO_NAME Build name (used to construct the working directory names). NANO_SRC Path to the source tree used to build the image. NANO_KERNEL Name of the kernel configuration file used to build the kernel. NANO_ARCH Machine processor architecture to build. Defaults to output of uname -p. NANO_BOOT0CFG Controls the options passed to boot0cfg(8); these dictate boot0's behaviour. NANO_BOOTLOADER The boot0 loader to use relative to the NANO_WORLDDIR variable. This defaults to boot/boot0sio and should be overridden to boot/boot0 to provide a VGA console. CONF_BUILD Options passed to the buildworld stage of the build. CONF_INSTALL Options passed to the installworld stage of the build. CONF_WORLD Options passed to both the buildworld and installworld stages of the build. FlashDevice Defines the type of media to use. Check the FlashDevice.sub file for more details. For more configuration options, please check the nanobsd.sh script. To build NanoBSD image using the nanobsd.conf configuration file, use the following command: sh nanobsd.sh -c nanobsd.conf It is possible to fine-tune NanoBSD using shell functions in the configuration file. The following example illustrates the basic model of custom functions: cust_foo () ( echo "bar=topless" > ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo There are a few pre-defined customization functions ready for use: cust_comconsole Disables getty(8) on the virtual syscons(4) or vt(4) terminals (/dev/ttyv*) and enables the use of the first serial port as the system console. cust_allow_ssh_root Allow root to log in via sshd(8). cust_install_files Installs files from the nanobsd/Files directory, which contains some useful scripts for system administration. FILES
src/tools/tools/nanobsd Base directory of the NanoBSD build script. EXAMPLES
Making persistent changes to /etc/resolv.conf: vi /etc/resolv.conf ... mount /cfg cp /etc/resolv.conf /cfg umount /cfg A more useful example of a customization function is the following, which changes the default size of the /etc directory from 5MB to 30MB: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size SEE ALSO
make.conf(5), boot(8), boot0cfg(8), picobsd(8) HISTORY
The nanobsd.sh utility first appeared in FreeBSD 6.0. AUTHORS
NanoBSD was developed by Poul-Henning Kamp <phk@FreeBSD.org>. This manual page was written by Daniel Gerzo <danger@FreeBSD.org>. BSD
May 20, 2010 BSD
All times are GMT -4. The time now is 05:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy