02-06-2008
Yep, as I suspected, that's not at all a Solaris O/S.
This thread should be moved to the SCO forum.
10 More Discussions You Might Find Interesting
1. BSD
# 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) (2 Replies)
Discussion started by: sheep
2 Replies
2. UNIX for Advanced & Expert Users
Hi All
I am kinda wondering about the UX kernel parameters, how we configure and why do we configure ???.. especially the 'semaphores'. Could somebody throw some light on this and would really appreciate it. (1 Reply)
Discussion started by: Prince_Charming
1 Replies
3. Solaris
When I run the Oracle installer, following checks are failed:
Checking for shmsys:shminfo_shmmax=4294967295; found no entry. Failed <<<<
Checking for shmsys:shminfo_shmmni=100; found no entry. Failed <<<<
Checking for semsys:seminfo_semmni=100; found no entry. Failed <<<<
Checking... (1 Reply)
Discussion started by: aa_monster
1 Replies
4. UNIX for Dummies Questions & Answers
I'm getting the following Error:
prepare_pcap.c: In function `prepare_pkts':
prepare_pcap.c:127: error: dereferencing pointer to incomplete type
prepare_pcap.c:138: error: dereferencing pointer to incomplete type
====================================
This is the part of the relevant... (8 Replies)
Discussion started by: katwala
8 Replies
5. Solaris
I tried to install the kernel patch 118855-36 in my x86 machine which has Solaris 10 installed. Find below the error message....
#patchadd 118855-36
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
118855-36
Executing... (1 Reply)
Discussion started by: paventhan
1 Replies
6. UNIX 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. UNIX for Dummies Questions & Answers
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
8. Linux
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
9. Solaris
Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error.
Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies
10. SuSE
http://uploads.tapatalk-cdn.com/20160725/0174562490859032f68430fb0fa216cd.jpg
I have created a personally made SUSE-based distro using susestudio.com and it will install just fine on my laptops (32-bit Acer Aspire One ZG5 and MacBook 4,1). However, when installing on an old Emachine desktop, I... (6 Replies)
Discussion started by: TheOuterLinux
6 Replies
LEARN ABOUT OPENDARWIN
ddi_can_receive_sig
ddi_can_receive_sig(9F) Kernel Functions for Drivers ddi_can_receive_sig(9F)
NAME
ddi_can_receive_sig - Test for ability to receive signals
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
boolean_t ddi_can_receive_sig(void);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
PARAMETERS
None.
DESCRIPTION
The ddi_can_receive_sig() function returns a boolean value indicating whether the current thread can receive signals sent by kill(2).
If the return value is B_FALSE, then the calling thread cannot receive signals, and any call to qwait_sig(9F), cv_wait_sig(9F), or
cv_timedwait_sig(9F) implicitly becomes qwait(9F), cv_wait(9F), or cv_timedwait(9F), respectively. Drivers that can block indefinitely
awaiting an event should use this function to determine if additional means (such as timeout(9F)) may be necessary to avoid creating unkil-
lable threads.
RETURN VALUES
B_FALSE The calling thread is in a state in which signals cannot be received. For example, the thread is not
associated with a user process or is in the midst of exit(2) handling.
B_TRUE The calling thread may receive a signal while blocked on a condition variable. Note that this function
does not check to determine whether signals are blocked (see sigprocmask(2)).
CONTEXT
The ddi_can_receive_sig() function may be called from user, kernel, or interrupt context.
SEE ALSO
close(9E), cv_wait(9F), qwait(9F)
SunOS 5.10 15 Dec 2003 ddi_can_receive_sig(9F)