Make New Entry,
Make Followup Entry
User name R. Michaels
Log entry time 07:38:59 on August 19, 2009
Entry number 284937
This entry is a followup to: 284924
keyword=why boot from adev ?
Last I checked, all the crates boot from adev. The reason is that the adev's login scripts
are owned by "root" and no user can dork with it. If people do the wrong thing in the login
script, the vxWorks will not boot and it can take a long time to figure out why.
There are a few solutions to this problem
1. Let the boards boot from apar. But then you must make sure all the cpus are in ~/.rhosts
and promise not to do illegal things in the login script and don't "echo" there.
2. (Better, IMHO): Wherever you have file-permission problems, make the directory owned
by a common Unix group with group access. Type "groups", I think both apar and adev are
in "a-adaq" and "a-online". Do the "chmod" thing on a directory ...
A copy of this log entry has been emailed to: paschke,mercado,silwal,dalton