1 |
Hello, |
2 |
|
3 |
I cannot seem to find detailed document/manual on using bash robustly |
4 |
in a programming environment. Maybe I need to purchase a good book? |
5 |
Mostly I'm an old csh hack. I like bash, but it seems porting over C code |
6 |
from a csh (or embedded) to a bash environment gives me trouble that is mostly |
7 |
due to my lack of in-depth knowledge of bash. Simple things like paths |
8 |
to libraries and other software modules inside of the ported code I |
9 |
either screw up or it seems like I solve the problems differently each |
10 |
time. |
11 |
|
12 |
Often the code I'm porting was not written for any type of unix |
13 |
or pre-emptible kernel, so I have features and functions that are |
14 |
instantiated in assembler or ansi C, that I have to figure out |
15 |
if there is a library I can use (acceptable similarity) or if |
16 |
I need to port the native micro code to a linux module or library. |
17 |
I seem to get these things to eventually work, but, well, I feel stupid |
18 |
and inept, as I should not be having the difficulty with these |
19 |
efforts that I am experiencing. Productivity must increase, and the |
20 |
only thing I can figure out, is I need to read and learn from a document |
21 |
or somebody that has figured out more 'rote methodologies' that I do |
22 |
not posess (if this sounds confusing, it's because I frustrated |
23 |
and not sure what I'm missing or deficient in). |
24 |
|
25 |
Any suggestions and examples where I may read and look at examples |
26 |
or a suitable forum to ask questions would be appreciated. Bash trickery |
27 |
is definately a weak point for me, but, that may not be my only |
28 |
area where I need to improve my knowledge and skills, related to |
29 |
software porting and development. Most of my code does involve hardware |
30 |
and or device drivers. Things like embeding code into the |
31 |
kernel or a module, thus avoiding bash all together with the 'driver' |
32 |
portion of the (hardware) code, and then making the other part of the |
33 |
code user accessible, via a shell. Some robust, detailed examples |
34 |
would be keen. I'm sufficient at getting chips and device drivers |
35 |
working in a micro environment, it's making these hardware and software |
36 |
items accessible via the (linux) shell environment where I struggle the most. |
37 |
|
38 |
|
39 |
|
40 |
James |
41 |
|
42 |
-- |
43 |
gentoo-user@g.o mailing list |