RHEL 5 - choosing packages for a minimal embedded system
Linux - NewbieThis forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I am charged with getting RHEL 5 set up for our embedded system (a VersaLogic Cheetah VL-EPM-32v). I have two basic questions - are there some good references for determining what packages we should choose when installing? Should I un-check everything, and just add in the few things I need (like ntp, ftp, nfs, vim, etc)? The manifest seemed like a good start towards understanding what all of these packages are for, but holy cow - there are a lot of them - how do I know what the OS needs. Can I assume the OS doesn't need any of them? We do need some stuff, at least enough to build our application, do some primitive debugging, and whatever resources to get information to/from the stack.
Second question - is there a best way to automatically spawn our embedded program on startup? Currently, we use mingetty, monkey with the runtime-level stuff, spawn our application as a daemon, and use a lock file so only one gets spawned, etc. It seems like it works well, but I thought I would poke around and check for better ways. Is there a preferred way using something which already exists in RHEL 5?
I don't konw of any specific references that might be particularly good in your situation. It has been a while since I did a fresh Redhat 5 install, but if they have gotten rid of the pre generated minimal configuration, I would suggest going through and unchecking everything that you don't need. The installer will resolve any dependency issues for you.
As to your second question, your current setup for launching the program sounds like the correct approach to me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.