08-13-2012
A question about Unix Architecture.
I want to know the memory capacity and types of memories, processor and more...
What kind of aplications this OS attends?
Archicture/system classification (Hybrid, monolithic, multitasking, micro-kernel, layered, Another..?
Explain it to me... I really need to understand and know that.
Any question, just ask me. Thank you all.
Explain the máximo possible
5 More Discussions You Might Find Interesting
1. IP Networking
hi there i'm a new bie
just got few simple questions to ask.
I got expert in windows configuration but totally new to unix environment . I want to make sure a com port (com1) is working, so I connect a 9-pin cable (CB9) for both PC using Unix environment (unix to unix).
The question are (1)... (1 Reply)
Discussion started by: typsam
1 Replies
2. UNIX for Dummies Questions & Answers
I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
Discussion started by: deckard
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am becoming very curious as to why viruses attach only Windows system and not any UNIX and Linux.
Does that has to do something with the architecture or something else. (11 Replies)
Discussion started by: vibhor_agarwali
11 Replies
4. UNIX for Dummies Questions & Answers
Hi Gurus,
I am new to UNIX environment. We have our DataStage tool installed on UNIX box.We have Dev,test and Prod environments.The architecrue is as given below.
Now my problem is I am not able to know what is meant by Physical name,Logical name,Cluster etc. also we need to do failover in case a... (5 Replies)
Discussion started by: pratyusha
5 Replies
5. Ubuntu
I noticed dpkg reporting architecture as AMD64, but the h/w is Intel, see below:
~$ uname -a
Linux XXX 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
~$ lshw | grep -i xeon
WARNING: you should run this program as super-user.
PCI (sysfs)
... (2 Replies)
Discussion started by: migurus
2 Replies
LEARN ABOUT OPENDARWIN
intro
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