Linux Programming "to the Importance to C Programming"
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
Linux Programming "to the Importance to C Programming"
I've used Linux off and on for about 20 years, but didn't really get "into it," I just used it.
Since I've been getting into it more now, I wanted to learn it.
I was at a used book store and found, "Linux Programming in 24 Hours."
I looked inside and saw, the book was about programming in Linux, with "Importance to C Programming."
Looks like it's laid out quite good.
Since it was written in 1999, I was wondering how much has changed, or not applicable to today?
I didn't want to get the book and have someone after tell me they don't use C any more, that Linux quit using it 10 years a go, or something like that.
It's only $4.xx so I almost got in anyway, but didn't want a book that would throw me off, or go in a different direction.
How relevant is this book in today’s computer world?
Since it was written in 1999, I was wondering how much has changed, or not applicable to today?
I didn't want to get the book and have someone after tell me they don't use C any more, that Linux quit using it 10 years a go, or something like that.
There might be a few out of date things, but C is still definitely very much in use, and not going away.
I got the book. Looks like the 24"hour" lessons will take me longer. That's OK.
This book is laid out so nice. "Using a hands on approach..." "The carefully organized lessons cover the essential topics early and progress toward the more advanced features. Each lesson is is logically organized, full of examples, and has systematic instructions."
"After reading this book, you will be able to write professional applications, client programs, and server daemons that run under the Linux operating system."
I set a goal to make it so I understand, and can try and fix why my amd-apu, dual monitor doesn't work on any Linux distro or DE (about 15 of them).
Also, a long term goal I set is to, keep progressing long enough to make a init system, that is very good, and an not like systemd. Weather it's 6 months, 6 years, or 20, when you see a new distro named, "LinuxnosysdOS.amd-64.iso" that'll be me.
Thanks for the help, I'll keep you posted of my progress,
Chris.
Last edited by happydog500; 11-05-2016 at 10:34 PM.
I got the book. Looks like the 24"hour" lessons will take me longer. That's OK.
This book is laid out so nice. "Using a hands on approach..." "The carefully organized lessons cover the essential topics early and progress toward the more advanced features. Each lesson is is logically organized, full of examples, and has systematic instructions."
"After reading this book, you will be able to write professional applications, client programs, and server daemons that run under the Linux operating system."
I set a goal to make it so I understand, and can try and fix why my amd-apu, dual monitor doesn't work on any Linux distro or DE (about 15 of them).
Also, a long term goal I set is to, keep progressing long enough to make a init system, that is very good, and an not like systemd. Weather it's 6 months, 6 years, or 20, when you see a new distro named, "LinuxnosysdOS.amd-64.iso" that'll be me.
Thanks for the help, I'll keep you posted of my progress,
Chris.
I'm glad you're pleased with it. I agree with the format of that book. While I have the original Kernigan and Ritchie book from way back when, I really never got many other books because I learned from work necessity and thus immersion. I feel it is also a valid thing to consider, and that book also recommends it with the hands on approach. All programming is a combination of understanding the syntax, the options you have, and understanding what your code will really do once it is compiled. Getting involved in debugging code you have written, or even observing it in mixed source-assembly listing and following the path of execution using the debugger are all very helpful. It is also excellent to see what the optimizer does, where it takes advantage of data and pointers retained in a register.
I thought when it said, "When you only have time for the answers" I thought that meant it explains stuff, without wasting so much time on things that don't matter.
The book "gives you the answers," but I don't know the questions. It uses words that are loaded, but I don't understand them. This book is almost impossible to learn on.
Illustration;
Here is a book I wrote. At the end I have a test, where you can check your answers. Here is the book;
Try not get so very disappointed at a book you paid less than $5 for. It sounds as if you have a Linux distribution installed, so use GCC and GDB and start writing programs. Since your post already is in the Programming forum, you've found it. Look at the Sticky thread on C/C++ Tutorials at the top of this very forum. Look at the earlier posts, there are a lot of links.
there is no "this or that in 24 hours", not even 21 days, what is the other title that is used for selling promises.
Learning takes time and praxis, at the begin you might feel stupid, if there is no one around who can help you it becomes more hard to step through.
But: Today's situation is so much more better than 10 years ago and so much much more better than 20 or even more years ago.
Today there is the internet, online courses, for free, youtube video lectures, ....
all this stuff did not exist years ago,
so actually learning something new today is fun, but do not trust promises on book titles, use the internt to reaearch about the quality of books, and be prepared that there is nearly no development topic where one book solves most problems/questions. A good book will give you some start up help and the knowledge how to ask the right questions. An than you need praxis and time..
there is no "this or that in 24 hours", not even 21 days, what is the other title that is used for selling promises.
Learning takes time and praxis, at the begin you might feel stupid, if there is no one around who can help you it becomes more hard to step through.
But: Today's situation is so much more better than 10 years ago and so much much more better than 20 or even more years ago.
Today there is the internet, online courses, for free, youtube video lectures, ....
all this stuff did not exist years ago,
so actually learning something new today is fun, but do not trust promises on book titles, use the internt to reaearch about the quality of books, and be prepared that there is nearly no development topic where one book solves most problems/questions. A good book will give you some start up help and the knowledge how to ask the right questions. An than you need praxis and time..
Sorry, yes there is "this or that in 24 hours." Especially Linux programing. You see, the "24 hours" is in quotes. The "24 hours" is how long it takes to read the chapters. You can read chapter 1, in an hour. It gives you a hands on approach, things to do. If you read a chapter in an hour, you can work on that, for a week, a month, or even a year. If it took you a month to 'get' chapter 1, you did it by reading a chapter, that took an "hour" to read.
This does not mean you can read this book, and in 24 hours time, you can program.
"use the Internet to research about the quality of books." Thank you for this information. Yes, this is very good advice for me. Thats why I posted on this forum, to do Internet research about the quality of the book. If you notice, I did the research before I bought the book.
I'd have to admit, I haven't really gave the book a chance yet. I just started reading and it was not what I expected. If I make an adjustment, then put real effort into it, I may post back and say its the best book I've read on the subject.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.