|
|
Sponsored Content
Contact Us
Post Here to Contact Site Administrators and Moderators
Proper Forum Etiquette
Post 27650 by tarballed on Wednesday 4th of September 2002 04:29:12 PM
09-04-2002
You aren't going to change a thing
To be honest, I was never trying to change anything. I was just voicing my opinion.
All I was trying to say is that, it doesnt seem to me that most people take the time to read up on anything. Whether it be documentation for their system or forum rules.
They are involved with their problem and just want it fixed.
Seems to be a common occurance.
Second case: They did read the rules but still forget that there is more than one OS out there. Made an assumtion that all of us know exactly what is going on with everything.
Seems to happen all the time.
When I first started learning UNIX, you had to read the manual and any other documentation available. Heavin forbid you asked a simple question on a mailing list of some sort where the usually response was "RTFM!"
I always took the approach as very respectful and polite. Just my style and more of a courtesy to others to show im sincere and not just "looking for the answer right now!" sort a speak.
Like I said, I was not trying to change anything, nor start a problem here. I was just voicing a opinion.
Tarballed
To be honest, I was never trying to change anything. I was just voicing my opinion.
All I was trying to say is that, it doesnt seem to me that most people take the time to read up on anything. Whether it be documentation for their system or forum rules.
They are involved with their problem and just want it fixed.
Seems to be a common occurance.
Second case: They did read the rules but still forget that there is more than one OS out there. Made an assumtion that all of us know exactly what is going on with everything.
Seems to happen all the time.
When I first started learning UNIX, you had to read the manual and any other documentation available. Heavin forbid you asked a simple question on a mailing list of some sort where the usually response was "RTFM!"
I always took the approach as very respectful and polite. Just my style and more of a courtesy to others to show im sincere and not just "looking for the answer right now!" sort a speak.
Like I said, I was not trying to change anything, nor start a problem here. I was just voicing a opinion.
Tarballed
|
|
6 More Discussions You Might Find Interesting
1. IP Networking
I have a series of new machines that are internet facing (have IP's that are accessible via the 'net) and it has internal facing interfaces. I need to be able to communicate back to the internal network to a specific server which processes monitoring and e-mail traffic. I've been told that I should... (3 Replies)
Discussion started by: BOFH
3 Replies
2. UNIX for Dummies Questions & Answers
My goal was to find any directories inside of any directory called "09_Client Original" not modified in the last 30 days.
$ find /Volumes/Jobs_Volume/ -type d -name "09_Client Original" -exec find {} -mtime +30 -type d -maxdepth 1 \;
The results of this find are passed along in a perl script... (1 Reply)
Discussion started by: guriboy
1 Replies
3. Post Here to Contact Site Administrators and Moderators
I got the following message
I tried to send the following reply:Please excuse me for not being more familiar with this forums conventions. I was not aware that I included a personal message. Please help me by:
1. So that I can avoid this problem in the future, please let me know what part of my... (2 Replies)
Discussion started by: lmjennings44094
2 Replies
4. UNIX for Dummies Questions & Answers
I'm new to Unix, and just had a quick question.
I'm writing a bash script, and I was wondering what proper programming etiquette was for piping. How many pipes is too many pipes?
OLDEST=$(find . -maxdepth 1 -type d -newermt 2012-07-01 ! -newermt
2012-07-30 | xargs ls -1td | tail -2)
echo... (1 Reply)
Discussion started by: jrymer
1 Replies
5. What is on Your Mind?
Just a quick update; to speed up the forums, I have disabled the forum statistics on the home page for non registered users.
No changes for registered users. (0 Replies)
Discussion started by: Neo
0 Replies
6. What is on Your Mind?
For mobile users, I have just added a "first beta" Advanced Forum Statistics to the home page on mobile using CSS overflow:auto; so you can swipe if you need to see more. Google Search Console mobile usability says this page is "mobile friendly" so perhaps this will be useful for some of our... (12 Replies)
Discussion started by: Neo
12 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