Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
TB0ne,
Your post didn't help, but anyway thank you. I didn't write any program. Neither my board nor my Linux is a custom one (Linksys router WRT54GL with OpenWRT Linux WhiteRussian 9). I only used two standard "echo" and "cat". It is a good idea to ask questions before responding to posts. Of course this is needed if one is going to "help", which I think was not your purpose when answering me. You said "I am a high level specialist" by your post: Ok! You won the contest, bye, good luck!
Huh...this, that you wrote:
Quote:
I have an embedded board running Linux, and a servo motor controller called SSC-32 which has a strange issue when communicating with the board. I'm sure it could be regulated from the router side by programming, but I don't know how so I write here to get help.
Says nothing about your specific hardware or Linux OS. Only that it's an embedded board, running SOME version of Linux. And you say "programming", but don't say what language, or what you're trying to do.
Quote:
Please think why out of 4,959 post as a Senior Member from Jul 2003 up to 2010, you've been only thanked for 260 times!
Edit: Thanks feature has been launched in 2008
This is the point you will reach to, by thinking "first time". Then think deeper please.
You need to think, period. Post a decent question with details the first time, and you'll probably get decent answers the first time. And since you want to spout off about my time here, try reading some other posts as well. You'll find thousands on here, where people come and say "my program doesn't work"...but they don't post the program or say anything about it. After your first post, with no information, that's sure what it sounded like. Your follow-up posts provided the details that you should have included at the start.
Also, since you're such as expert on my posting history, try looking at how many threads where people have thanked me in the post, but NOT clicked the button. I don't post here to get button-clicks. If you don't like the answers you get, try thinking about why that is. You asked a vague question with no details.
Thread started with a clear question, and got a clear answer, read the post before!
If you don't know how to answer a post (and you think that information is not enough), you don't need to say something.
To know about commands that reset the serial port, I'll never provide details about my board, to not to take time of people! I give info enough WITH relation to my question (about flashing serial port).
Again, read posts before and you see all other people got the point with no need to know details.
I've read that and yet much better books on such kind of subject. Forum is not a church. It is not for moral lessons, it is to discuss information, bare information.
Please come out of the church, and just read his post again, applying logic to it (calculation, not moral!):
Quote:
You do not "command Linux" to reset the serial port. You fix the bugs in YOUR PROGRAM, that are not flushing the data correctly. This is your program, on a custom Linux setup, on a custom board. The only one who can fix this is the person who wrote the program.
Let's analyze:
YOUR PROGRAM is rude. Could use simply 'your program'. I asked for reset commands, and he could simply tell me about them, i.e. what you kindly did, or just nothing to say when he didn't have something to say. He "guessed" there is a program, he "guessed" it contains bugs, but he could "ask" questions, or if he needed only fully given information to start to support, just forget about my post (as it didn't have enough info). Those being "custom" are also guessed. He had right 4 "guesses" by this point, without any basis, which is what a professional always avoid. Finally, by teaching me "who is responsible" - a moral lesson in a tech forum - he made his 5th guess about me. 5 guesses in a small comment is not only "nonprofessional" but also childish relation. I recalled him this, but in a way so that he starts to "think", but he surprisingly didn't, he went to the church like you!
What you are doing now is also a "guess" about me (are you sure I needed more than those kind suggestions of Linux commands you gave? do you know if you knew who is writing these lines, ever continued this discussion?).
Finally, my suggestions please:
1. leave the church, think of logic/calculations in forums.
2. when you do mistakes, keep silence and just try not to repeat it.
3. don't make wild guesses in the absence of information.
4. ask, ask, ask: questions.
5. don't make forum a place for moral lessons.
6. don't force me to write moral lessons to the forum.
7. don't continue a solved thread.
8. don't try to solve me: don't hate the programmer, hate the code.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.