Free sco software for linux

jcsound is a command line wrapper for csound that makes it a jack and alsa-sequencer client.
Currently jcsound is somewhat jack-transport aware:
- If slave mode is set to 1 , it will only play if the jack transport is rolling, playing silence when it is not.
- It will _not_ reposition, and it will still quit at the end of the score.
(see the TODO)
You can also set it to 2: jcsound will then reload the orc/sco if it has changed on disk when you start the transport again.
- If you made an error, it will (try to) put out silence.
Or you can set it to both by setting to slave mode to 3 (1+2)
Type jcsound --help to see the available options.
NOTE:
csound4 does not deal with event extending opcodes if you specify the "-t" flag. So jcsound wont either.
If you use midi input (-M) dont use the -t flag!
The -p option may need a little explanation:
csound currently does most of its memory assignment in the first audio buffer of its performance.
This is the time that it loads its function tables etc.
To prevent (posibly massive) xruns jcsound normally performs this first buffer in silence, discarding the audio.
Since its intended use is as a live (midi) instrument that seemed ok to me.
But if you have a score that you want to record into ardour f.i., you can override this behaviour by specifying the -p or --inprocess flag at the command line.
Enhancements:
- removed wrong default flag when calling csoundlib fixed unitialized variable fixed dirty output buffer

skill sends signals to processes given any combination of user names, ttys, commands, and pids and snice changes the priority of processes (given the same).
They are similar to kill(1) and renice(8), but the commandline is order-independent. There are also verbose, search, and interactive modes of operation.
Both programs run under a variety of operating systems, including:
Apple Darwin 5.4
AT&T SysVR4, SysVR4.2, SysVR4.2MP
4.2BSD, 4.3BSD, 4.4BSD (and many PC variants)
Cygwin 1.5 (uses Linux)
Mach 2.6, 3.0
DEC Ultrix 2.2, 4.1-2
DEC AXP OSF/1
DEC/Compaq Tru64 Unix V3.2D-2, T3.2F-1, V4.0, V5.0-1B
Encore UMAX 4.2
FreeBSD 2.0-2, 3.1, 4.4-11, 5.0-3, 6.0-1
HP-UX 6.5, 7.0, 8.0, 9.0-5, 10.1-20, 11.0-23
IBM AIX 3.1-2, 4.1, 5.2
IBM AOS 4.3
Linux 1.0-2, 2.1, 2.2, 2.4
MIPS UMIPS 2.1
NeXT OS 1.0, 2.1
NetBSD 1.3-5
OpenBSD 2.6, 3.0
Pyramid OSx 4.0
SCO UnixWare 7.0.1
SGI Irix 3.3, 4.0, 5.2, 5.3, 6.2, 6.5
Sequent Dynix 3.0-1
SunOS 2, 3, 4.0-1, 5.1-10
Enhancements:
- skill and snice now act on each process only once (for systems like BSD that return the same Process ID multiple times, once for each instantiated thread).
- Support has also been added for FreeBSD 6.2 and HP-UX 11.31.

uucpm provides networked uucp services on older systems that otherwise lack this capability, but do have TCP/IP networking support. This includes systems such as SCO Xenix and NCR Towers.

The package includes two programs. The uucpm daemon converts a pseudo-tty (pty) into a device that can communicate across a TCP/IP network. A System V.2-ish port of the BSD uucpd daemon also is included. These two daemons implement, respectively, the originating and answering portions of the transfer.

There are two programs in this package. The first is a port of the Berkeley `uucpd daemon (version 5.9 6/1/90) to System V. This daemon is normally run out of `inetd. It authenticates incoming uucp requests and starts up a uucp session to talk to the remote system.

The second program is a new program called `uucpm. It is a daemon turns a pseudo-terminal (pty) into a device that can be used for network communications. The daemon sits on the master end of the pty. It allows `uucico to connect to the slave end of the pty and issue requests to connect to systems across the network. Once `uucpm is installed, it takes a simply one-line modification to the Systems and Devices files to implement TCP/IP capability.

Here is a schematic diagram of how the pieces fit together:

+---------+
| uucico |
+---------+
|
|
|/ /dev/ttyXX
+---------+
| pty |
+---------+
| /dev/ptyXX
|
|/
+---------+ +---------+ +---------+ +---------+
| uucpm | | inetd |-->| uucpd |-->| uucico |
+---------+ +---------+ +---------+ +---------+
| /|
| socket |
`--------------

When `uucico connects to the pty, the `uucpm daemon issues a `host: prompt. The originating system then sends the name of the remote machine. The `uucpm daemon establishes a socket to the well known uucp port on that system, and from there on a standard uucp login is performed.

FreeBSD is an advanced operating system for x86 compatible (including Pentium and Athlon), amd64 compatible (including Opteron, Athlon 64, and EM64T), IA-64, PC-98, Alpha/AXP and UltraSPARC architectures.
It is derived from BSD, the version of UNIX developed at the University of California, Berkeley. It is developed and maintained by a large team of individuals. Additional platforms are in various stages of development.
FreeBSD offers advanced networking, performance, security and compatibility features today which are still missing in other operating systems, even some of the best commercial ones.
FreeBSD makes an ideal Internet or Intranet server. It provides robust network services under the heaviest loads and uses memory efficiently to maintain good response times for thousands of simultaneous user processes.
The quality of FreeBSD combined with todays low-cost, high-speed PC hardware makes FreeBSD a very economical alternative to commercial UNIX workstations. It is well-suited for a great number of both desktop and server applications.
FreeBSD can be installed from a variety of media including CD-ROM, DVD-ROM, floppy disk, magnetic tape, an MS-DOS partition, or if you have a network connection, you can install it directly over anonymous FTP or NFS.
While you might expect an operating system with these features to sell for a high price, FreeBSD is available free of charge and comes with full source code.
It is easy to contribute to FreeBSD. All you need to do is find a part of FreeBSD which you think could be improved and make those changes (carefully and cleanly) and submit that back to the Project by means of send-pr or a committer, if you know one. This could be anything from documentation to artwork to source code.
Even if you are not a programmer, there are other ways to contribute to FreeBSD. The FreeBSD Foundation is a non-profit organization for which direct contributions are fully tax deductible.
Main features:
- A merged virtual memory and filesystem buffer cache continuously tunes the amount of memory used for programs and the disk cache. As a result, programs receive both excellent memory management and high performance disk access, and the system administrator is freed from the task of tuning cache sizes.
- Compatibility modules enable programs for other operating systems to run on FreeBSD, including programs for Linux, SCO UNIX, and System V Release 4.
- Soft Updates allows improved filesystem performance without sacrificing safety and reliability. It analyzes meta-data filesystem operations to avoid having to perform all of those operations synchronously. Instead, it maintains internal state about pending meta-data operations and uses this information to cache meta-data, rewrite meta-data operations to combine subsequent operations on the same files, and reorder meta-data operations so that they may be processed more efficiently. Features such as background filesystem checking and file system snapshots are built on the consistency and performance foundations of soft updates.
- File system snapshots, permitting administrators to take atomic file system snapshots for backup purposes using the free space in the file system, as well as facilitating background fsck, which allows the system to reach multiuser mode without waiting on file system cleanup operations following power outages.
- Support for IP Security (IPsec) allows improved security in networks, and support for the next-generation Internet Protocol, IPv6. The FreeBSD IPSEC implementation includes support for a broad range of accelerated crypto hardware.
- Out of the box support for IPv6 via the KAME IPv6 stack allows FreeBSD to be seamlessly integrated into next generation networking environments. FreeBSD even ships with many applications extended to support IPv6!
- Multi-threaded SMP architecture capable of executing the kernel in parallel on multiple processors, and with kernel preemption, allowing high priority kernel tasks to preempt other kernel activity, reducing latency. This includes a multi-threaded network stack and a multi-threaded virtual memory subsystem. With FreeBSD 6.x, support for a fully parallel VFS allows the UFS file system to run on multiple processors simultaneously, permitting load sharing of CPU-intensive I/O optimization.
- M:N application threading via pthreads permitting threads to execute on multiple CPUs in a scaleable manner, mapping many user threads onto a small number of Kernel Schedulable Entities. By adopting the Scheduler Activation model, the threading approach can be adapted to the specific requirements of a broad range of applications.
- Netgraph pluggable network stack allows developers to dynamically and easily extend the network stack through clean layered network abstractions. Netgraph nodes can implement a broad range of new network services, including encapsulation, tunneling, encryption, and performance adaptation. As a result, rapid prototyping and production deployment of enhanced network services can be performed far more easily and with fewer bugs.
- TrustedBSD MAC Framework extensible kernel security, which allows developers to customize the operating system security model for specific environments, from creating hardening policies to deploying mandatory labeled confidentiality of integrity policies. Sample seucrity policies include Multi-Level Security (MLS), and Biba Integrity Protection. Third party modules include SEBSD, a FLASK-based implementation of Type Enforcement.
- GEOM pluggable storage layer, which permits new storage services to be quickly developed and cleanly integrated into the FreeBSD storage subsystem. GEOM provides a consistent and coherrent model for discovering and layering storage services, making it possible to layer services such as RAID and volume management easily.
- FreeBSDs GEOM-Based Disk Encryption (GBDE), provides strong cryptographic protection using the GEOM Framework, and can protect file systems, swap devices, and other use of storage media.
- Kernel Queues allow programs to respond more efficiently to a variety of asynchronous events including file and socket IO, improving application and system performance.
- Accept Filters allow connection-intensive applications, such as web servers, to cleanly push part of their functionality into the operating system kernel, improving performance.

AutoGen is a tool designed to simplify the creation and maintenance of programs that contain large amounts of repetitious text. AutoGen project is especially valuable in programs that have several blocks of text that must be kept synchronized.

AutoGen can now accept XML files as definition input, in addition to CGI data (for producing dynamic HTML) and traditional AutoGen definitions.

A common example where this would be useful is in creating and maintaining the code required for processing program options. Processing options requires multiple constructs to be maintained in parallel in different places in your program.

Options maintenance needs to be done countless times. So, AutoGen comes with an add-on package named AutoOpts that simplifies the maintenance and documentation of program options.

AutoGen is known to work on GNU/Linux, BSD, Apples OS/X, SVR4-5, HPUX, SCO OpenServer and Solaris. It is expected that it will work on any reasonably modern UNIX system with an ANSI-compliant C compiler. It also runs under WinNT, provided you have CygWin ** and Guile loaded.

RetroForth is a compact, open source Forth development system. RetroForth can be used under FreeBSD, Linux, BeOS, Windows, SCO OpenServer, or as an operating system.
It is easy very easy to learn, use, and extend with standard libraries like SDL, and it can also be used to create tight, stand-alone applications.
Main features:
- Small: Size RetroForth was designed to be a small Forth. As such, the source code is about 20 kilobytes in size, and most binaries take about 5 kilobytes.
- Portable: Despite being written in assembly language, RetroForth is very easy to port to new operating systems. As noted elsewhere, it runs on at least five major operating systems, and can be used as an OS. Thanks to optional use of libc, many other x86 operating systems should be able to use RetroForth with nothing more than a recompile of the source.
- Simplicity: A major aspect of our design philosophy is simplicity. We have designed RetroForth to be easy to learn and use, while not sacrificing its usefulness.
- Documentation: We provide a manual with every recent release. This is included in ASCII text and NoteBook formats. Other formats, including HTML, PDF, and PostScript will be supported in the near future.
- Support: Options We try to help developers using RetroForth as much as possible. We provide a Forum, Wiki, IRC channel, and a mailing list. Were quite willing to answer questions and listen to suggestions

PXES project is a micro Linux thin client distribution. PXES will boot a real thin client or will help to convert in minutes any compliant hardware (see list bellow) into a versatile thin client.
They will be capable of accessing any XDM server presenting the graphical login screen or any Microsoft Terminal Server through RDP protocol. The actual configuration of clients is made with an easy to use graphical configuration tool, allowing the specification of clients parameters or the server to access to.
You can recover hardware that is useless running current desktop OS or office package and give it a second chance. This thin client boots from the network with PXE (Intel Pre-Execution Environment specifications) so neither boot diskette nor boot eprom is needed.
The linux kernel and an initial root filesystem is transmitted over the network (the compressed size as of version 0.4 is about 4M).
Main features:
Supported servers and protocols
- Unix/Linux supporting XDM
- Microsoft Terminal Server using RDP
- Citrix using ICA
- VNC using TightVNC
- LOCAL local graphical session with simple desktop
- LTSP or K12LTSP
- IBM Host using 3270 or 5250 emulation (soon)
- Telnet emulating ANSI terminal
- SSH
- Tarantella using proprietary protocol
- NoMachine using NX
- Thinlinc
Boot methods
- PXE network card included in most modern PC hardware
- Etherboot to boot from diskette or EPROM
- CD-ROM
- Hard disk
- DOC DiskOnChip and DOM DiskOnModule
- USB Storage
- For Hard Disk, DOC, DOM or other flash memory installation you may also use PXES HD/DOM Installer (http://pxes.sourceforge.net/enterprise/install-dom.shtml) which is part of Enterprise Edition (http://pxes.sourceforge.net/enterprise/index.php).
- You can also see the detailed information about Boot Methods.
Hardware requirements
- Processor: x86 architecture (i486, i586, i686, VIA C3, Geode, Vortex86, Transmeta Crusoe, etc.)
- BUS: PCI recommended (although ISA works)
- RAM: 32 Mb recommended (16 Mb minimum)
- NIC: see supported network card list
- Video: see supported video card list
Local devices
- Diskette
- Hard disk
- CD-ROM
- Printers parallel, serial and USB
- Serial devices (bar code reader, etc.)
- Audio
- Flash memory / USB storage
Supported operating system
- Linux
- Solaris
- AIX
- SCO
- BSD
- HP-UX
- Microsoft Windows NT4
- Microsoft Windows 2000
- Microsoft Windows 2003
- Microsoft Windows XP
Enhancements:
- Support for different boot loaders was added.
- Support for GRUB on ISO images was added.
- A correction was made in the kernel and image path in isolinux.
- A message telling the user to run "pxesconfig --updatefstab" was added.
- updatefstab was added in post.
- Support for 2.4.32 and 2.6.15 kernels was added.
- Automated owner and permission changing on specific files was added, so now the whole pxes-base tree can be checked out as a normal user.

QoS (or Quality-of-service) is traffic shaper replacement for Internet Service Providers (ISP). Dump your vintage hard-wired routers/shapers (C|sco, etc.) in favour of powerful open source and free solution !
Prometheus QoS generates multiple nested HTB tc classes with various rate and ceil values, and implements optional daily traffic quotas and data transfer statistics (as HTML). It is compatible with NAT, both asymetrical and symetrical, yet still provides good two-way shaping and prioritizing, both upload and download.
Prometheus QoS was written in C<<less