public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user]  OT: bash details
@ 2005-08-12 14:25 James
  2005-08-12 14:33 ` Frank Schafer
                   ` (2 more replies)
  0 siblings, 3 replies; 9+ messages in thread
From: James @ 2005-08-12 14:25 UTC (permalink / raw
  To: gentoo-user

Hello,

I cannot seem to find  detailed document/manual on using bash robustly
in a programming environment. Maybe I need to purchase a good book? 
Mostly I'm an old csh hack. I like bash, but it seems porting over C code 
from a csh (or embedded) to a bash environment gives me trouble that is mostly
due to my lack of in-depth knowledge of bash. Simple things like paths
to libraries and other software modules inside of the ported code I 
either screw up or it seems like I solve the problems differently each
time. 

Often the code I'm porting was not written for any type of unix
or pre-emptible kernel, so I have features and functions that are
instantiated in assembler or ansi C, that I have to figure out
if there is a library I can use (acceptable similarity) or if
I need to port the native micro code to a linux module or library.
I seem to get these things to eventually work, but, well, I feel stupid
and inept, as I should not be having the difficulty with these
efforts that I am experiencing. Productivity must increase, and the
only thing I can figure out, is I need to read and learn from a document
or somebody that has figured out  more 'rote methodologies'  that I do
not posess (if this sounds confusing, it's because I frustrated
and not sure what I'm missing or deficient in).

Any suggestions and examples where I may read and look at examples
or a suitable forum to ask questions would be appreciated. Bash trickery
is definately a weak point for me, but, that may not be my only
area where I need to improve my knowledge and skills, related to
software porting and development. Most of my code does involve hardware
and or device drivers. Things like embeding code into the
kernel or a module, thus avoiding bash all together with the 'driver'
portion of the (hardware) code, and then making the other part of the
code user accessible, via a shell.  Some robust, detailed examples
would be keen. I'm sufficient at getting chips and device drivers
working in a micro environment, it's making these hardware and software
items accessible via the (linux) shell environment where I struggle the most.



James

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2005-08-15 13:23 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-12 14:25 [gentoo-user] OT: bash details James
2005-08-12 14:33 ` Frank Schafer
2005-08-12 15:01   ` [gentoo-user] " James
2005-08-12 15:26     ` Ciaran McCreesh
2005-08-12 16:02     ` Uwe Thiem
2005-08-12 22:09     ` Nick Rout
2005-08-15 13:19     ` Marco Matthies
2005-08-12 14:37 ` [gentoo-user] " Matthew Cline
2005-08-12 14:53 ` Ciaran McCreesh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox