04-13-2011
The important question isn't the CPU but the everything else...
8 More Discussions You Might Find Interesting
1. Programming
Hi,
I know very little about C and Unix. I have written a program to use threads. The program needs to get some values from a very large database.
I wrote a simple program and compiled but got the following errors.....
cc mythread.c -lthread
"/usr/include/pthread.h", line 120:... (3 Replies)
Discussion started by: reddyb
3 Replies
2. Filesystems, Disks and Memory
How can I check if a Sun Ultra 10 workstation supports 40GB IDE drives?
Thanks! (6 Replies)
Discussion started by: oti
6 Replies
3. Solaris
I realise this is an odd request - but I need advice please..
I have two server - in different geographical locations..
The have 2 local 72gb disks which are mirrored. I need to get storage added to increase both to 300gb in total each and this needs to be mirrored in case of failure. The... (2 Replies)
Discussion started by: frustrated1
2 Replies
4. Hardware
Before posting questions about Linux hardware, it is a good idea to check the Linux Hardware HOWTO guide (Last Update: 2007-05-22)
However, this HOWTO has not been maintained since 2007 and it out-of-date. (0 Replies)
Discussion started by: Neo
0 Replies
5. Hardware
Hi all,
I've got an issue with my PC and was wondering what you thought might be the issue.
The problem manifests it'self in two ways (at least I'm assuming it's related).
1. I turn the power on at the wall and press the on button, but nothing happens. I have to wait for several seconds to... (3 Replies)
Discussion started by: DougyC
3 Replies
6. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
7. Solaris
Hi
Can i use Solaris LIVE CD to verify that ubuntu has all drivers present for a certain desktop PC?
which Live CD should i use ? there any many varities out there
Before i purchase this expensive PC i want to ensure Solairs has all drivers for it.
Specs are :
Processor Intel Core i7... (1 Reply)
Discussion started by: kashif_islam
1 Replies
8. AIX
Hello Everyone,
Hope you all are doing great!
As you can see by the title on top, we are in the process of migrating alot of our servers from Power5 (physical) to Power8 (Virtual). Now it's turn for servers with HACMP Cluster on it. Let me lay out the environment like:
OLD ENVIRONMENT:
... (12 Replies)
Discussion started by: uzair_rock
12 Replies
INTRO(9) BSD Kernel Developer's Manual INTRO(9)
NAME
intro -- introduction to system kernel interfaces
DESCRIPTION
This section contains information about the interfaces and subroutines in the kernel.
PROTOTYPES ANSI-C AND ALL THAT
Yes please.
We would like all code to be fully prototyped.
If your code compiles cleanly with cc -Wall we would feel happy about it. It is important to understand that this isn't a question of just
shutting up cc, it is a question about avoiding the things it complains about. To put it bluntly, don't hide the problem by casting and
other obfuscating practices, solve the problem.
INDENTATION AND STYLE
Believe it or not, there actually exists a guide for indentation and style. It isn't generally applied though.
We would appreciate if people would pay attention to it, and at least not violate it blatantly.
We don't mind it too badly if you have your own style, but please make sure we can read it too.
Please take time to read style(9) for more information.
NAMING THINGS
Some general rules exist:
1. If a function is meant as a debugging aid in DDB, it should be enclosed in
#ifdef DDB
#endif /* DDB */
And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine.
SCOPE OF SYMBOLS
It is important to carefully consider the scope of symbols in the kernel. The default is to make everything static, unless some reason
requires the opposite.
There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea
here either.
For device drivers and other modules that don't add new internal interfaces to the kernel, the entire source should be in one file if possi-
ble. That way all symbols can be made static.
If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using
the number of global symbols as your guide. The fewer the better.
SEE ALSO
style(9)
HISTORY
The intro section manual page appeared in FreeBSD 2.2.
BSD
December 13, 1995 BSD