- INITIALIZATION FILE [85]Top [86]Contents [87]Next [88]Previous
-
- In its default configuration, C-Kermit executes commands from a file called
- .kermrc in your home directory when it starts, unless it is given the -Y or -y
- command-line option. Custom configurations might substitute a shared
- system-wide initialization file. The SHOW FILE command tells what
- initialization file, if any, was used. The standard initialization file
- "chains" to an individual customization file, .mykermc, in the home directory,
- in which each user can establish her/his own preferences, define macros, and
- so on.
-
- Since execution of the initialization file (at least the standard one) makes
- C-Kermit take longer to start, it might be better not to have an
- initialization file, especially now that Kermit's default startup
- configuration is well attuned to modern computing and networking -- in other
- words, you no longer have do anything special to make Kermit transfers go
- fast. So instead of having an initialization file that is executed every time
- Kermit starts, you might consider making one or more kerbang scripts (with
- names other that .kermrc) that do NOT include an "exit" command, and invoke
- those when you need the settings, macro definitions, and/or scripted actions
- they contain, and invoke C-Kermit directly when you don't.
-
- To put it another way... We still distribute the standard initialization file
- since it's featured in the manual and backwards compatibility is important to
- us. But there's no harm in not using it if you don't need the stuff that's in
- it (services directory, dialing directory, network directory, and associated
- macro definitions). On the other hand, if there are settings or macros you
- want in effect EVERY time you use Kermit, the initialization file (or the
- customization file it chains to) is the place to put them, because that's the
- only place Kermit looks for them automatically each time you start it.
-
- [89]Kermit Home [90]C-Kermit Home [91]C-Kermit FAQ
- MODES OF OPERATION [92]Top [93]Contents [94]Next [95]Previous
-
- Kermit is said to be in Local mode if it has made a connection to another
- computer, e.g. by dialing it or establishing a Telnet connection to it. The
- other computer is remote, so if you start another copy of Kermit on the remote
- computer, it is said to be in Remote mode (as long as it has not made any
- connections of its own). The local Kermit communicates over the communications
- device or network connection, acting as a conduit between the the remote
- computer and your keyboard and screen. The remote Kermit is the file-transfer
- partner to the local Kermit and communicates only through its standard input
- and output.
-
- At any moment, a Kermit program can be in any of the following states. It's
- important to know what they are and how to change from one to the other.
+INITIALIZATION FILE
+
+ [85]Top [86]Contents [87]Next [88]Previous
+
+ In its default configuration, C-Kermit executes commands from a file
+ called .kermrc in your home directory when it starts, unless it is
+ given the -Y or -y command-line option. Custom configurations might
+ substitute a shared system-wide initialization file. The SHOW FILE
+ command tells what initialization file, if any, was used. The standard
+ initialization file "chains" to an individual customization file,
+ .mykermc, in the home directory, in which each user can establish
+ her/his own preferences, define macros, and so on.
+
+ Since execution of the initialization file (at least the standard one)
+ makes C-Kermit take longer to start, it might be better not to have an
+ initialization file, especially now that Kermit's default startup
+ configuration is well attuned to modern computing and networking -- in
+ other words, you no longer have do anything special to make Kermit
+ transfers go fast. So instead of having an initialization file that is
+ executed every time Kermit starts, you might consider making one or
+ more kerbang scripts (with names other that .kermrc) that do NOT
+ include an "exit" command, and invoke those when you need the settings,
+ macro definitions, and/or scripted actions they contain, and invoke
+ C-Kermit directly when you don't.
+
+ To put it another way... We still distribute the standard
+ initialization file since it's featured in the manual and backwards
+ compatibility is important to us. But there's no harm in not using it
+ if you don't need the stuff that's in it (services directory, dialing
+ directory, network directory, and associated macro definitions). On the
+ other hand, if there are settings or macros you want in effect EVERY
+ time you use Kermit, the initialization file (or the customization file
+ it chains to) is the place to put them, because that's the only place
+ Kermit looks for them automatically each time you start it.
+
+ [89]Kermit Home [90]C-Kermit Home [91]C-Kermit FAQ
+
+MODES OF OPERATION
+
+ [92]Top [93]Contents [94]Next [95]Previous
+
+ Kermit is said to be in Local mode if it has made a connection to
+ another computer, e.g. by dialing it or establishing a Telnet
+ connection to it. The other computer is remote, so if you start another
+ copy of Kermit on the remote computer, it is said to be in Remote mode
+ (as long as it has not made any connections of its own). The local
+ Kermit communicates over the communications device or network
+ connection, acting as a conduit between the the remote computer and
+ your keyboard and screen. The remote Kermit is the file-transfer
+ partner to the local Kermit and communicates only through its standard
+ input and output.
+
+ At any moment, a Kermit program can be in any of the following states.
+ It's important to know what they are and how to change from one to the
+ other.