i got this archive file on sticky bit mode. somehow i could not remove the sticky bit. i could not even copy or view the view using file user account or root account.
-rw-r--r-T 1 mark support 875166720 Mar 23 2005 file_mig.dat
anybody encounter this type of problem?
i have done running... (11 Replies)
Hi Admins,
I know that VCS supports Solaris x86-64bit only...and I need vcs for Solaris 32 bit-x86..running on vmware workstation.. I need to run vcs on vmware workstation...And my laptop support only 32bit... Please suggest..
Thanks.. (1 Reply)
:confused:
how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6.
also i want to know the difference between 32 bit and 64bit os.
any help will be much appreciated as i am in urgent need of this information (6 Replies)
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
I had previous implemented the following in my menu.lst to be able to get to 32-bit operations.
#
title Solaris 10 32-bit
root (hd0,0,a)
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
</code>
Now, it is not working as I get the following error :
... (0 Replies)
Hello
1) How can I find what bit of OS I am running on? 16 bit, 64 bit?
2) What is the difference in having different bits?
3) Below is the output of /etc/release/ what are all these components meaning?
$ more /etc/release
Solaris 10 11/06 s10x_u3wos_10 X86
$
Thank... (7 Replies)
Dear All,
This is Viswanadhan, new to Sun Solaris domain.
In Sun Solaris ( SPARC ) has 32 bit and 64 bit OS. While insallation of OS there no specific option for 32 / 64 bit OS .On which basis OS installs for 32 / 64 bit OS ?
Regards,
Viswanadhan. (1 Reply)
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