The more complicated answer: many people need to write shell scripts which will be portable across many systems. That is why POSIX specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell, and because several important programming interfaces ( make(1), system(3), popen(3), and analogues in higher-level scripting languages like Perl and Tcl) are specified to use the Bourne shell to interpret commands.

You can use any shell you want, as long as it's listed in the /etc/shells file. Traditionally, academia seems to use the csh (C-shell) or its updated modern variant, tcsh. However, this is probably through inertia rather than anything else and having a knowledge of the sh family of shells, in particular the bash shell is probably more widely useful: much of the internals of Linux/*nix systems is based on portable sh-type scripts.

Eterm DOES NOT read any shell profile/rc file for any shell. Ever. Never has, never will. Neither does any other terminal program. You are confused. When Eterm starts up, it is provided with the environment of its parent process, be it your window manager, your X startup file, your panel/launcher application, or whatever. Eterm, in turn, spawns a subprocess which inherits its environment from Eterm itself. This subprocess is usually a shell, but can be anything you specify with the -e option.

It was in /etc/shells because it ships with Darwin. I've heard it was removed from OSX because bash is GNU license which isn't compatible with the BSD license.

To build a minimal synthesizer system you'll need some basic modules to create and modify waveforms. See our ideas on building your own custom synthesizer system. A typical minimal system would consist of the following items: If you will be using your system mostly for modifying sounds from a guitar, microphone or other instrument, add a Q118 Instrument Interface in place of one of the Q106 Oscillators.

There's a fairly simple way to do this, but there is no official way to do this for a variety of reasons. The solution is to add these lines to the end of your .login file: if ( $SHELL == "/bin/csh" ) then foreach i ($path) if ( -x $i/tcsh ) then setenv SHELL $i/tcsh set shell=$i/tcsh exec $i/tcsh -l endif end endif If you really need tcsh to be the login shell, then you should start it with the -l flag as it is done above.

Briefly, FreeBSD is a UNIX® like operating system for the i386™, IA-64, PC-98, Alpha/AXP, and UltraSPARC® platforms based on U.C. Berkeley's ''4.4BSD-Lite'' release, with some ''4.4BSD-Lite2'' enhancements. It is also based indirectly on William Jolitz's port of U.C. Berkeley's ''Net/2'' to the i386, known as ''386BSD'', though very little of the 386BSD code remains. A fuller description of what FreeBSD is and how it can work for you may be found on the FreeBSD home page.

Sh originated from a larger research project called SMASH, which involved exploring not only software programmability of GPUs, but also hardware features. Sh was to form the software layer of the SMASH system. Eventually it was discovered that the name SMASH was already in use by a related project, so the two main parts were split into Sm (for the simulator) and Sh (for the language), conveniently making SMASH an acronym for "Sm and Sh".

Yes. The speed sensor is reading the revolution of the countershaft, therefore the speedo vs tacho readings will be always the same. However, with a shorter sprocket ratio, higher rpm is needed for the same real speed, i.e. the speedo error is increased.

You need a telnet program to access the shell (like Better Telnet). To transfer files back and forth, use FTP, and ftp to the same address you telnet to. To run irc, try typing 'irc' and see if a p rogram loads. If not, you'll need to either get a binary for your system (precompiled program) or get the source and compile it yourself. To find out what kind of system your shell is on type 'uname -a' on your shell, you'll get some feedback like this: This shows you the name of the machine 'nowhere.

There are two basic problems you might run into. One is the fact that /bin/sh is really ash, and is missing some features you might expect in /bin/sh, particularly if you are used to /bin/sh actually being bash (Linux) or ksh (Tru64). For example: Or, it could be a permission problem, and Cygwin doesn't understand that your script is executable. Because 'chmod' may not work (see FAQ entry above), Cygwin must read the contents of files to determine if they are executable.

This is a security precaution to prevent scripts from gaining unauthorized access to other parts of the system. In the future we may allow other programs to be executed (for example, MediaWiki uses texml for it's math symbols) but currently it is not possible to execute programs. Sockets and other types of remote connections are disabled because they use extra system resources and are generally unnecessary for most users.

Your .bashrc is read from your home directory specified by the HOME environment variable. It uses /.bashrc if HOME is not set. So you need to set HOME correctly, or move your .bashrc to the top of the drive mounted as / in Cygwin.

Job control will be turned off since your shell can not obtain a controlling terminal. This happens since the debug port essentially is â??/dev/consoleâ?? and hence the kernel will not provide a controlling terminal. This is the normal behaviour for the shell on the debug port which implies a few restrictions, e.g., Control-C will not work. When working with the developer board it is recommended that you run a shell on a normal tty or login remote using telnet or ssh.

Fossil Shell Dust® is applied by sprinkling the dust onto any surface that may contain mites, including carpets, wall cracks and crevices. A pesticide duster may be used for application of this product even though it is not a pesticide. Be careful not to inhale the dust.

Heinz Peter Hippenstiel) Add the following lines to .inputrc in your Cygwin home directory (e.g. /home/harold/): set meta-flag on set output-meta on # to show 8-bit characters set convert-meta off # to show it as character, not the octal representation # Mapping for German umlauts "\M-a": "ä" "\M-A": "Ä" "\M-o": "ö" "\M-O": "Ö" "\M-u": "ü" "\M-U": "Ü" "\M-s": "ß" # (TODO: Mapping for accents?)

OpenSSH 3.8 enables untrusted X11 forwarding by default when connecting to an ssh server that supports untrusted X11Forwarding. Most ssh servers for GNU/Linux are versions of OpenSSH that do support untrusted X11Forwarding, so using OpenSSH 3.8 from Cygwin will result in a connection that uses untrusted X11Forwarding by default.

The current Sh backends for shaders target programmable floating-point GPUs. For fragment programs, this means NVIDIA GeForce FX 5200 and up or ATI Radeon 9600 and up (a variety of 3DLabs cards are also supported). For vertex programs, a variety of older hardware is supported (any hardware that supports ARB_vertex_program on OpenGL should work). For stream programs, Sh also includes a CPU backend that generates C code and compiles and links it at runtime.

No. Sh is plain ISO standard C++, and is provided simply as a set of header files to include and a shared library (DLL on Windows, .so on other platforms) to link with. No preprocessor or separate compiler is necessary. No. Template metaprogramming is a technique that allows arbitrary computations to be performed at C++ compile time using C++ templates. Sh does not need to use any such techniques. Sh code is compiled dynamically at runtime (similar to a just-in-time compiler).

This is because Grex is running a real sh, and that is a feature not supported by sh. What some Unix systems call sh is actually bash, an enhanced version of the sh shell which does this. If you would like to use bash instead, you should change your shell on Grex to bash. You can do that by running the change command. Bash, ksh and tcsh do support previous line editing. It may not be working the way you expect because a different default editing mode is in use.

The answer is, unfortunately, ''It depends''. These mice with additional features require specialized driver in most cases. Unless the mouse device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse.

You should use it because it is a BSD! Aside from that reason, here are a few helpful pointers that can help with making that decision. If it ain't broke, don't fix it": If you already use an open source operating system, and you are happy with it, there is probably no good reason to change. BSD systems, in particular FreeBSD, can have notably higher performance than Linux. But this is not across the board. In many cases, there is little or no difference in performance.

KPilot is developed on FreeBSD 6-STABLE on an amd64, most of the time. So use 6-STABLE, that is easiest. You will need the following settings: devfs rules to allow you to read and write to the device for the handheld. The following works for me in /etc/devfs.rules: [localrules=10] add path 'ttyU*' mode 0660 group operator usbd rules to set up the link from /dev/pilot to the device created when the HotSync starts (optional). See the FAQ entry above for details.

The Open Group has released the source code to Motif 2.1.30. You can install the open-motif package, or compile it from ports. Refer to the ports section of the Handbook for more information on how to do this. Note: The Open Motif distribution only allows redistribution if it is running on an open source operating system. In addition, there are commercial distributions of the Motif software available.

CooptIn can be run with any modern browser: Netscape version 6 and higher, Explorer Version 5 and higher, Mozilla Firefox and higher. To import the Outlook address book, only Microsoft Explorer is available.