10-20-2011
Of course the error is the same; the code hasn't changed after all...
Unlike an IDE though, a shell does not have total control of its environment, meaning, debugging could cause radically different behavior (input meant for the script ending up in the 'wait till enter for next line' function, etc.) You're trying to build an IDE out of a shell.
Hmm. Thinking on it.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HI
I am new to unix and need to install sco unix on a new server - could anybody help me with the steps I need to take - the hd is a 9gb scsi drive (pretty old machine)
Thanks (1 Reply)
Discussion started by: porikamu
1 Replies
2. UNIX for Dummies Questions & Answers
I am new to unix and server at my job crashed due to hardware problem. I'm now opted to install sco unix on a new server - could anybody help me with the steps I need to take (pretty old machine)
Thanks & Regards
Nancy :( (0 Replies)
Discussion started by: nensee7
0 Replies
3. Shell Programming and Scripting
Hi all,
The following script is fine when I work via command line
m=1
c=0
while
do
echo $m
gnokii --getsms IN $m > out.txt;
m=`expr $m + 1`;
cat out.txt >> message_log;
############
read first crap< <(sed -n '/Text:/{n;p;}' out.txt);
read message< <(sed -n '/Text:/{n;p;}'... (2 Replies)
Discussion started by: whamchaxed
2 Replies
4. UNIX for Dummies Questions & Answers
Hello all
i was searching the net for simple but effective tutorial to show me how debug c++ in emacs with not much luck.
im not new to unix but new to emacs , i looking for tutorial that
shows how to debug ( if possible ) c++ programs .
LIike IDE suppose to , break points step in/out variable... (0 Replies)
Discussion started by: umen
0 Replies
5. Solaris
Hi all.
This may be a stupid question but here goes:
I lost a disk on my Sun-Fire 480-r and want to replace it. I don't care about the data, I just need to get a new disk in.
Can anyone supply me with step by step procedure please. I am not an expert by any means and it is a dev box so I... (1 Reply)
Discussion started by: jamie_collins
1 Replies
6. Linux
Thank all of you.
May you explain step by step where and how I will add pseudo code
Note : I have Linux 2.6.24-26-server on x86_64
dears kindly help me (3 Replies)
Discussion started by: nonowa
3 Replies
7. What is on Your Mind?
FYI,
I'm slowly removing a lot of the bold font-styles from titles of discussions, forum titles, etc
I'm not removing bold for the entire site because we do need bold from time to time, especially in posts and sometimes in other places.
However, the original forum style had way too much... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT DEBIAN
hotswaprc
HOTSWAPRC(5) File Formats Manual HOTSWAPRC(5)
NAME
hotswaprc - configuration file for hotswap
DESCRIPTION
/etc/hotswaprc is the global configuration file for the hotswap utility.
It allows system administrators to specify arbitrary shell scripts to be run after a device is inserted, as well as before and after it is
removed. Scripts are selected according to the model name retrieved from the device. This is particularly helpful for automatic configura-
tion of CD-RW drives, which require SCSI emulation and bypass normal access via the IDE subsystem.
hotswaprc is implemented as an Extensible Mark-up Language (XML) application. XML documents are structured using elements of the form
<tag-name> content <tag-name>. A Document Type Definition (DTD) describes the possible content of each element.
Please refer to the XML specification for more information. The hotswap distribution also contains an example file, doc/hotswaprc.example,
which includes the DTD for the configuration file format.
ELEMENTS
<hotswap>
This is the root element of the document. Each valid hotswaprc must contain exactly one <hotswap> element. The <hotswap> element may
contain an arbitrary number of <device> elements.
<device>
The configuration file contains one <device> element for every device for which scripts are defined. The <device> element is com-
posed of the following elements in this order: <name>, <post-insert>, <pre-remove>, <post-remove>. All but <name> are optional.
<name> The content of this element is the model identification string of the IDE device the current <device> element refers to.
<post-insert>
Contains the shell script that is to be executed after the device has been inserted and registered with the kernel.
<pre-remove>
Contains the shell script that is to be run before hotswap attempts to unregister the device.
<post-remove>
Contains the shell script that is to be run after the device had been unregistered.
REPORT BUGS
Report bugs to t.stadelmann1@physics.ox.ac.uk.
AUTHOR
Written by Tim Stadelmann.
SEE ALSO
hotswap(1), xhotswap(1).
COPYRIGHT
Copyright (c) 2002-2003 Tim Stadelmann.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License (GPL), Version 2 or
any later version published by the Free Software Foundation.
26th November 2002 HOTSWAPRC(5)