Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
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.
What is the difference between boot image and kenel image?
In some literatures I have read jargon called 'boot device' what does it mean?
Does it mean device where operating system resides?
or
Does it mean where boot loader resides???
For example,
In embedded systems, bootloader (say uboot) resides on inbuilt flash where as kernel or application code resides on harddisk or other external memory... at that time what is meant by boot device?
You seem to be presenting elementary questions alot. Most of your queries could be answered via <Linux> - Google Search or LQ Search with good search keys.
'How to Ask Questions the Smart Way' would be one link you should look at to help us to help you in the future. You really need to start doing some work on your part instead of querying on a whim without even attempting anything on your part. There's enough information on the web to fulfill your elementary questions. Not to say you shouldn't post but make some effort. If you don't understand something it's one thing but to just flippantly post is just not right.
Loads of information for reference and guidance from;
Your behavior is rude. You have not bothered to reply to most of your threads.
Not just rude. After going through the post history, you can find out that the way question is asked is not to find the solution for the issue or understanding the matter, but to check or question the members' knowledge. And most of the posts have still not been marked solved.
I really cant understand Why are you people pointing that too often even I understood my mistake and apologized for that???
Being new to linux environment, having got right answer by you people I feel asured due to lack of confidence and knowledge and that led me to browse more... That doesnt mean that by not telling thanks or go it I am being rude or anything like that.
Seniors should not supervise juniors... and MUST not compell them to say "Thanks" and "Sorries"... There should be enough space and freedom... without that its rather difficult to spread the wings and fly in the horizon of knowledge.
Distribution: Debian 5 - Slackware 13.1 - Arch - Some others linuxes/*BSDs through KVM and Xen
Posts: 329
Rep:
Quote:
Originally Posted by priyadarshan
Thanks David
Seniors should not supervise juniors... and MUST not compell them to say "Thanks" and "Sorries"... There should be enough space and freedom... without that its rather difficult to spread the wings and fly in the horizon of knowledge.
Yes, they may do it if they want, and you *should* thank for all the help - or apologize, whatever fits the situation.
Seeing your previous posts, it seems more like you want us to spread your wings and beat them for you to save you the effort. Next time you post, instead of saying something like "tell me what is FooFile", you should say "I found in google a definition for FooFile which if I understood correctly is (blah blah blah), can somebody confirm or correct this?"
I would suggest, you check OP's posting history before replying to his threads.
It is my policy to judge each post independently, based on its own merits.
My advice to you is that if you are not going to answer the post or point out a violation of the forum rules, do not post. Zero information posts are the only real problem that this site has.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.