Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
10-26-2009, 09:56 PM
|
#1
|
|
LQ Newbie
Registered: Oct 2009
Posts: 13
Rep:
|
Are programs like sys_open( ) ,sys_read( ) et al examples of system level programs ?
Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right ? Is there any difference of hierarchy between the programs that implement system calls and system level programs like that implement thread library, process management , memory managemnt etc..
Hope you understood my qstn
Last edited by kashyapa; 10-26-2009 at 09:59 PM.
Reason: to include tags
|
|
|
|
10-26-2009, 10:11 PM
|
#2
|
|
Senior Member
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,153
Rep: 
|
Actually, those are functions, not programs. They interact with the OS through system calls (to system functions). Does that help?
|
|
|
|
10-26-2009, 11:10 PM
|
#3
|
|
LQ Newbie
Registered: Oct 2009
Posts: 13
Original Poster
Rep:
|
Quote:
Originally Posted by Quakeboy02
Actually, those are functions, not programs. They interact with the OS through system calls (to system functions). Does that help?
|
are the programs that implement the library functions system level programs ?
|
|
|
|
10-26-2009, 11:32 PM
|
#4
|
|
Senior Member
Registered: Sep 2009
Location: Washington U.S.
Distribution: Damn Small Linux, KateOs, M$ Ickdows Vista, My own OS
Posts: 2,136
Rep: 
|
i smell home work.
|
|
|
|
10-27-2009, 12:00 PM
|
#5
|
|
Senior Member
Registered: Nov 2006
Distribution: Debian Squeeze 2.6.32.9 SMP AMD64
Posts: 3,153
Rep: 
|
Quote:
Originally Posted by kashyapa
are the programs that implement the library functions system level programs ?
|
There are no programs that implement the library functions. This may seem like a fine distinction, but it must be made, nonetheless. A program is a self-contained unit having a "main()" function. Note the word "function". Programs are made of code and calls to functions, not the reverse. Functions are self-contained bits of code that may call other functions. They do not contain a "main()" function. You really need to discuss with your instructor the difference between a function and a program.
|
|
|
|
10-27-2009, 08:20 PM
|
#6
|
|
LQ Newbie
Registered: Oct 2009
Posts: 13
Original Poster
Rep:
|
I got this cleared ..Here goes the clarification
" Functions like open() , printf() , scanf() , read() are library function implemented on top of their sys_* counterparts so they can be used for any Application development. On the other hand sys_open, sys_close, sys_read etc are implemented as-part-of-system commonly known as kernel. On top of this, system programs like thread library, compilers, linkers are implemented which helps other application development. Hope this clears the difference between system, system programs and application programs. "
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 07:50 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|