06-04-2010
Friend,
1.Stick to your basics.
2.Put only things that you have done in your company in your resume. Interviewers make it a point to ask things that you have done and how good you are at it (rather than what you don't know).
3.Prepare well on topics like Boot procedure,crontabs,Users and profile creation and OS installation.
4. If you don't know something be candid about it.
5. It's your attitude and willingness to learn that matters more than your knowledge.(What good is knowledge for if they feel u don't have the attitude to work!!)
And Don't worry about the size of your comapny's production environment.Your production environment(inside you...) is more important than that.
All the best.
HG
8 More Discussions You Might Find Interesting
1. Solaris
hi everybody,
my name is samir, i m from delhi,india. i m a student in solaris. just few days ago i had completed my course. can anybody tell me the possible interview questions in solaris. (1 Reply)
Discussion started by: samir_sinu
1 Replies
2. Solaris
Hey,
My company is looking to bring on a Sr. UNIX Admin with Solaris 10 experience.
What are some solid interview questions I could ask about UNIX and Solaris 10 that would weed a good guy out from a bad?
Questions that don't involve long command lines would be the best.
Thanks (1 Reply)
Discussion started by: mikepatton21
1 Replies
3. UNIX for Dummies Questions & Answers
1, why Boot server should be in a network in jumpstart?
2, what is the different between patch and package?
3, how to list the avilable NIC in solaris9?
4, User complaing system is slow (solaris) what are the steps to check?
5, what is hardware error and software error and Transport Error? in... (5 Replies)
Discussion started by: suresh_krish
5 Replies
4. UNIX for Dummies Questions & Answers
6.nohup cmn is used to
Prot execn of pgm frm aborting when hangup s/g is rxd
Not hangup modem
Disconn a node frm s/m
Chng execn prev of pgm
.wat is the o/p? Cut -d”” -f3 file1/sort -r
Display 3rd col of file 1 in asc order
Disp 3rd col of file 1 in desc
Not ... (1 Reply)
Discussion started by: techguru
1 Replies
5. Solaris
Hi guys,
Interview Questions:-
1) There are 2 ways to create a slice in Solaris
1) we can create using format command but there say other than format 1more within sec. we can create a slice.
2) ?
2) How to create a temperory SWAP Space
3) How to check the Devices from the... (2 Replies)
Discussion started by: kurva
2 Replies
6. Solaris
I was not able to get answers for these interview questions. It will be appreciable and useful if any one answers this questions. (5 Replies)
Discussion started by: Sesha
5 Replies
7. Red Hat
hello,
I have some doubts .plz help
if i try to ping from a server, it doesnt ping & gives different ip address, and in nslookup i get different ip address, what is the problem ?
if u cant ssh to a server what will be ur steps ?
give full iptables command to open port 22
... (1 Reply)
Discussion started by: abhigrkist
1 Replies
8. Solaris
Hello :) !
i've few doubts.
1) how can we find the newly attached disk in SOLARIS ?
2) how to change port number of a service ?
3) how can we find that autofs is running in our system without using
svcs and prstat commands ?
4) we know that there are several types of dns servers in... (0 Replies)
Discussion started by: vamshigvk475
0 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