Sponsored Content
Full Discussion: I want the Best FREEBSD
Operating Systems BSD I want the Best FREEBSD Post 52440 by RTM on Friday 18th of June 2004 09:16:58 AM
Old 06-18-2004
This is the second post you have made to these forums - please read the rules

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

need help with FreeBSD!!!

Hi I want to write to my output_file using: if((fptr = creat(output_file, _S_IWRITE)) == -1) { printf("output_file..."..); return (1); } for(...) { _write(fptr, buffer, BUF_SIZE); } It says "_S_IWRITE" undeclared!!! Anybody knows what function I can use for that and what I... (3 Replies)
Discussion started by: lacasa
3 Replies

2. UNIX for Dummies Questions & Answers

FreeBSD

I am on AOL now,and i am using 56 k,i was gonna install FreeBSD,but i dont know if aol works on BSD,or my modem. Do they work on BSD? (2 Replies)
Discussion started by: kita
2 Replies

3. UNIX for Dummies Questions & Answers

Freebsd 4.5

i am new at unix and am VERY confused about the compression processes. what progs do i need to unzip and zip files? there must be a standard one similar to winzip? (1 Reply)
Discussion started by: Mindscan
1 Replies

4. UNIX for Dummies Questions & Answers

FreeBSD

What is FreeBSD, who does use Free? (3 Replies)
Discussion started by: cyberangel
3 Replies

5. BSD

FreeBSD 5.2.1

I want someone tell me the positives and negatives points of FreeBSD 5.2.1, if someone help me, i thanks a lot! (4 Replies)
Discussion started by: israel
4 Replies

6. BSD

Having problem with FreeBSD 5.3

I just download the FreeBSD 5.3 i386 iso files. And I have a problem now, I can't copy the 5.3-RELEASE-i386-disc2.iso to the cd, I try a lot of times, even change lots of blank cd to try but still cannot. But I can copy the other three iso files, i.e. 5.3-RELEASE-i386-bootonly.iso,... (4 Replies)
Discussion started by: GarbageKing
4 Replies

7. BSD

please help me in FreeBSD

Hi to all, Iam doing a project in Free BSD and i am stuck with a puzzle. Please any one of you clarify my doubt : How to add a mechanism to check the status of the file system which alerts the root user via. email if any single partition is greater than 90% full. This alert should include the... (3 Replies)
Discussion started by: tadakamalla
3 Replies

8. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies

9. Fedora

FreeBSD

I'm using Windows mostly and the only *nix thing I used during my life was cygwin (I like command line :)). But currently I have (by an occasion) a DVD with latest FreeBSD. I don't know why, but I want to install it... But probably, this OS is too difficult for a beginner. I heard, it's used on... (3 Replies)
Discussion started by: TeenageWerewolf
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 11:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy