|
|
Sponsored Content
Contact Us
Post Here to Contact Site Administrators and Moderators
For Kelam_Magnus
Post 57904 by woofie on Tuesday 9th of November 2004 04:43:51 PM
11-09-2004
I'm not a mod so what I got to say probably shouldn't be said here 
But if I was to post a homework question (I don't do a course though I'm all self taught) I would say at the start of the post that it was a homework question. Also I would state that I had spent x time on the question and looked through the book several times (Which I would have) as well.
That way if it was a homework question at least you have let people know it is a homework question. Also though you have let the people know that you have tried to do to solve the problem yourself and couldn't.
Another thing you could have done is post what you thought may be the answer/solution, then people could point you in the correct direction for a answer.
They don't like homework questions posted as this board is for learning and sharing what you know. I've been to boards were people do post homework, they are no where near as good as this board. It also shows you are not willing to put the hard yards in to learn, so why should someone spend their time answering your homework questions? We are all here to learn, not to answer someone's homework.
Anyway that's my 2 cents where I probably shouldn't have left them
But if I was to post a homework question (I don't do a course though I'm all self taught) I would say at the start of the post that it was a homework question. Also I would state that I had spent x time on the question and looked through the book several times (Which I would have) as well.
That way if it was a homework question at least you have let people know it is a homework question. Also though you have let the people know that you have tried to do to solve the problem yourself and couldn't.
Another thing you could have done is post what you thought may be the answer/solution, then people could point you in the correct direction for a answer.
They don't like homework questions posted as this board is for learning and sharing what you know. I've been to boards were people do post homework, they are no where near as good as this board. It also shows you are not willing to put the hard yards in to learn, so why should someone spend their time answering your homework questions? We are all here to learn, not to answer someone's homework.
Anyway that's my 2 cents where I probably shouldn't have left them
|
|
We Also Found This Discussion For You
1. Post Here to Contact Site Administrators and Moderators
Why did you close all my threads? I undstand that since you may be an advanced unix user, that my questions seem dumb. Hey, they probably are. But the title of the forum is " UNIX for Dummies Questions & Answers" and it says "All UNIX Newbies Welcome !!"
So what is the prob?
I dont think... (7 Replies)
Discussion started by: LANSTARR.COM
7 Replies
LEARN ABOUT DEBIAN
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 is not a question of just shutting up cc, it is a question about avoiding the things it complains about. To put it bluntly, do not 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 is not generally applied though. We would appreciate if people would pay attention to it, and at least not violate it blatantly. We do not 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 do not 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