Sponsored Content
Full Discussion: build kernel ,question?
Operating Systems BSD build kernel ,question? Post 50397 by sheep on Friday 23rd of April 2004 05:09:15 AM
Old 04-23-2004
build kernel ,question?

# cd /usr/src/sys/i386/conf
# cp GENERIC LOVEPP
# cd /usr/src
# make buildkernel KERNCONF=LOVEPP
make:don't know how to make buildkernel. Stop

Any suggestions?
(I am using Freebsd4.8)
 

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
BINMISCCTL(8)						    BSD System Manager's Manual 					     BINMISCCTL(8)

NAME
binmiscctl -- manage binary image activators SYNOPSIS
binmiscctl add name --interpreter path --magic magic --size size [--mask mask] [--offset offset] [--set-enabled] binmiscctl remove name binmiscctl disable name binmiscctl enable name binmiscctl lookup name binmiscctl list DESCRIPTION
The binmiscctl utility is the management utility for configuring miscellaneous binaries image activators in the kernel. It allows adding, deleting, disabling, enabling, and looking up interpreters. Also, all the interpreters can be listed. The first argument on the command line indicates the operation to be performed. Operation must be one of the following: add name --interpreter path --magic magic --size size [--mask mask] [--offset offset] [--set-enabled] Add a new activator entry in the kernel. You must specify a unique name, interpreter path and its arguments path, header magic bytes that uniquely identify a suitable binary for the activator, and the size of the magic in bytes. Optionally you may specify a mask to do a bitwise AND with the header bytes. This effectively allows you to ignore fields in the binary header that do not uniquely indentify the binary file's type. An offset may be specified for the magic bytes using the --offset option. By default the offset is zero. To enable the activator entry the --set-enabled option is used. The activator default state is disabled. The interpreter path may also contain arguments for the interpreter including #a which gets replaced by the old argv0 value in the interpreter string. remove name Remove the activator entry identified with name. disable name Disable the activator entry identified with name. enable name Enable the activator entry identified with name. lookup name Look up and print out the activator entry identified with name. list Take a snapshot and print all the activator entries currently configured. EXAMPLES
Add an image activator to run the LLVM interpreter (lli) on bitcode compiled files: # binmiscctl add llvmbc --interpreter ''/usr/bin/lli --fake-argv0=#a'' --magic ''BCxc0xde'' --size 4 --set-enabled #a is replaced with the old argv0 value so that 'lli' can fake its argv0. Set its state to enabled. Set the state of the llvmbc image activator to disabled: # binmiscctl disable llvmbc Set the state of the llvmbc image activator to enabled: # binmiscctl enable llvmbc Delete the llvmbc image activator: # binmiscctl remove llvmbc Look up and list the record for the llvmbc image activator: # binmiscctl lookup llvmbc Add QEMU bsd-user program as an image activator for ARM AARCH64 binaries: # binmiscctl add arm64 --interpreter "/usr/local/bin/qemu-aarch64-static" --magic "x7fx45x4cx46x02x01x01x00x00x00 x00x00x00x00x00x00x02x00xb7x00" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxfexffxffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for ARM little-endian binaries: # binmiscctl add armelf --interpreter "/usr/local/bin/qemu-arm-static" --magic "x7fx45x4cx46x01x01x01x00x00x00 x00x00x00x00x00x00x02x00x28x00" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxfexffxffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for ARM big-endian binaries: # binmiscctl add armebelf --interpreter "/usr/local/bin/qemu-arm-static" --magic "x7fx45x4cx46x01x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x28" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for MIPS32 binaries: # binmiscctl add mips32 --interpreter "/usr/local/bin/qemu-mips-static" --magic "x7fx45x4cx46x01x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x08" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for MIPS64 binaries: # binmiscctl add mips64 --interpreter "/usr/local/bin/qemu-mips64-static" --magic "x7fx45x4cx46x02x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x08" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for PowerPC binaries: # binmiscctl add powerpc --interpreter "/usr/local/bin/qemu-ppc-static" --magic "x7fx45x4cx46x01x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x14" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for PowerPC64 binaries: # binmiscctl add powerpc64 --interpreter "/usr/local/bin/qemu-ppc64-static" --magic "x7fx45x4cx46x01x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x15" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Add QEMU bsd-user program as an image activator for SPARC64 binaries: # binmiscctl add sparc64 --interpreter "/usr/local/bin/qemu-sparc64-static" --magic "x7fx45x4cx46x02x02x01x00x00x00 x00x00x00x00x00x00x00x02x00x2b" --mask "xffxffxffxffxffxffxffx00xffxff xffxffxffxffxffxffxffxfexffxff" --size 20 --set-enabled Create and use an ARMv6 chroot on an AMD64 host Use an existing source tree to build a chroot host with architecture overrides: D=/path/to/chroot cd /usr/src mkdir -p $D make world TARGET=arm TARGET_ARCH=armv6 DESTDIR=$D make distribution TARGET=arm TARGET_ARCH=armv6 DESTDIR=$D With emulators/qemu-user-static from the FreeBSD Ports Collection, the emulator must be copied into the jail path specified in the binmiscctl command. Using the example above: mkdir $D/usr/local/bin cp /usr/local/bin/qemu-arm-static $D/usr/local/bin Now the user can chroot into the environment normally, as root: chroot $D SEE ALSO
lli(1), execve(2), jail(8) HISTORY
The binmiscctl command was added in FreeBSD 10.1. It was developed to support the imgact_binmisc kernel module. AUTHORS
Stacey D Son BSD
December 30, 2014 BSD
All times are GMT -4. The time now is 10:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy