Install Icevast with apt-get package management

apt-get install icecast-server
service icecast-server stop

Download MP3-Info, MP3-Icecast and MP3-Icecast-Simple Perl modules

wget http://search.cpan.org/CPAN/authors/id/D/DA/DANIEL/MP3-Info-1.24.tar.gz http://search.cpan.org/CPAN/authors/id/A/AL/ALLENDAY/MP3-Icecast-0.02.tar.gz http://search.cpan.org/CPAN/authors/id/G/GR/GREGORY/MP3-Icecast-Simple-0.2.tar.gz

Install each package

perl Makefile.PL
make
sudo make install

Create file streaming.pl and use this code:

#!/usr/bin/perl
use MP3::Icecast::Simple;

$icy = MP3::Icecast::Simple->new(
description => “Station”,
server => ’127.0.0.1:8000′,
password => ‘password’,
local_port => 1234, # port for stream
bitrate => 96 # bit rate for stream
);
$icy->play(“/Mp3/”); # directory where is locate your mp3 that you want stream

Now you can listen via http://youripadd:1234
Use XMMS, mplayer, Winamp, or something like that

Features and limitations

We designed the VM from the ground up for extremely limited devices. Where other JVMs often require at least several hundreds kB of RAM, Darjeeling can run meaningful programs in as little as 2kB. In order to achieve this we dropped several features from the Java language.

Features:

* Precise, compacting garbage collection
* A 16-bit instruction set to reduce stack space consumption
* Threads with ad-hoc stack space allocation (linked stack) and synchronisation
* A simple method for calling with native C code from Java
* Uses a static linking model to reduce code footprint

Limitations:

* Does not support reflection
* Does not support 64-bit and floating point types
* No support for multi-dimensional arrays
* Does not call static class initialisers in lazy order
* Supports a limited subset of the Java class library

Source:
http://darjeeling.sourceforge.net

Lets go… Obviously, we need to install first (this isn’t a topic of installation):
DAHDI
Asterisk

For setup the card OpenVox A400P we need to disable these modules (we need use wctdm module of DAHDI):

hisax
netjet

So well, we just add these next lines into /etc/modprobe.d/blacklist.conf and next boot there won’t be more conflicts between these modules.

blacklist netjet
blacklist hisax

And that’s all, now we can configure/start the Asterisk IP PBX.

Features

* Windows compatible FAT file system.
* Platform independent. Easy to port.
* Very small footprint for code and work area.
* Various configuration options:
o Multiple volumes (physical drives and partitions).
o Multiple ANSI/OEM code pages including DBCS.
o Long file name support in ANSI/OEM or Unicode.
o RTOS support.
o Multiple sector size support.
o Read-only, minimized API, I/O buffer and etc…

Source:
http://elm-chan.org/fsw/ff/00index_e.html

Prex Design The Prex microkernel provides only fundamental features for task, thread, memory, IPC, exception, and synchronization. The other basic OS functions – process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to utilize existing *NIX applications. This design allows the system to perform both of the native real-time task and the generic POSIX process simultaneously without degrading real-time performance. It also helps platform designers to construct OS by choosing suitable system servers for their target requisition.

License:

Prex is royalty-free software released under Revised BSD License.

Prex has the following features:

* Task & Thread Control: preemptive priority scheduling with 256 priority levels
* Memory Management: memory protection, virtual address mapping, shared memory, MMU or MMU-less configuration
* IPC: object name space, synchronous message passing between threads
* Exception: fault trapping, framework for POSIX signal emulation
* Synchronization: semaphores, condition variables, and mutexes with priority inheritance
* Timers: sleep timers, one-shot or periodic timers
* Interrupt: nested interrupt service routines, and prioritized interrupt service threads
* Device I/O: minimum synchronous I/O interface, DPC (Deferred Procedure Call)
* Security: task capability, pathname-based access control, I/O access permission.
* Real-time: low interrupt latency, high resolution timers and scheduling priority control
* Power Management: power policy, idle thread, DVS (Dynamic Voltage Scaling)
* Debugging Facility: event logging, kernel dump, GDB remote debug
* File Systems: multi-threaded, VFS framework, buffer cache, ramfs, fatfs, arfs, etc.
* POSIX Emulation: pid, fork, exec, file I/O, signal, pipe, tty, pthread, etc.
* Libc: C library fully optimized to generate a small executable file
* CmdBox: a small binary that includes tiny versions of many UNIX utilities.
* Networking: (plan) TCP/IP stack, BSD socket interface

Source:
http://prex.sourceforge.net

As of now, HelenOS is being developed mostly by faculty members, and former and contemporary students of Faculty of Mathematics and Physics at Charles University in Prague. Nonetheless, the project is open for everyone, so we also have developers with different backgrounds from various places around the world. The source code is open and available under the BSD license. Some third party components, and components based on GPL software, are licensed under GPL.

Source:
http://www.helenos.org

The inconvenient for me went when I tried to execute a bash script, and I only got to see:

/bin/sh: bad interpreter: Permission denied

And I asked me: WTF? I checked first the script, then the permissions but all were ok, so again I asked me: WTF? so I looked the PATH variable and it was ok… and it was the moment when I decided to ask to san google xD

And I found the solution!!, the partition was mounted with noexec option and that’s why I couldn’t execute my bash script.

So the lesson for me was: If you want to execute something, don’t forget use exec option when mount the partition

Have a nice execution!!

usermod -d /new/home username

For more info about what other things we could do with this command look the man page.

First we need to make the image partikle.img that will content the .prtk file:

dd if=/dev/zero of=partikle.img bs=1M count=130

Once we made the img, is time to make the loop association with the image and make the partition:

losetup -f --show partikle.img
fdisk /dev/loop0
p
1
enter (default settings)
enter (default settings)
w

Because we need to map the partition tables as device, for easy access, we need to use kpartx:

kpartx -a /dev/loop0

Now we mount the partition and copy the .prtk and files that grub needs for install it:

mkdir tmp
mkfs.reiserfs /dev/mapper/loop0p1
mount /dev/mapper/loop0p1 tmp
cp hello_world.prtk tmp/
mkdir -p tmp/boot/grub
cp /usr/lib/grub/i386-pc/stage[1,2] tmp/boot/grub
cp /usr/lib/grub/i386-pc/reiserfs_stage1_5 tmp/boot/grub/

For install grub into image, we need to map hd0 to partikle.img and then install grub:

echo "(hd0) partikle.img" > map
grub --device-map=map
>root (hd0,0)
>setup (hd0)

Once installed grub it’s time to create cfg file for grub editing tmp/boot/grub/menu.lst and put this:

default 0
timeout 10
title partikle
root (hd0,0)
kernel /hello_world.prtk

After all, run sync command and you’re right for run QEMU like we know to run

Sources:
http://www.e-rtl.org/partikle
http://wiki.qemu.org/Main_Page

ctrl + r

RTAI supports several architectures:

* x86 (with and without FPU and TSC)
* x86_64
* PowerPC
* ARM (StrongARM; ARM7: clps711x-family, Cirrus Logic EP7xxx, CS89712, PXA25x)
* m68k (supporting both MMU and NOMMU cpus)

The RTAI distribution includes RTAI-Lab, a tool chain to convert block diagrams into RTAI executables and to monitor their operation on various targets.

Source:
http://www.rtai.org

Source:
http://www.voiceroute.org

The board is built around two chips: a Silabs 3210, that implements all telephony functions, and a PIC (a 18F2550 for the time) that interfaces between the 3210 and the USB and implements the board’s routine tasks, like passing around PCM I/O data. All the intelligence lies on the PC side, which drives the board by setting registers on the 3210 and performs audio I/O.

Source:
http://code.google.com/p/openusbfxs

HAProxy is known to reliably run on the following OS/Platforms :

* Linux 2.4 on x86, x86_64, Alpha, SPARC, MIPS, PARISC
* Linux 2.6 on x86, x86_64, ARM (ixp425), PPC64
* Solaris 8/9 on UltraSPARC 2 and 3
* Solaris 10 on Opteron and UltraSPARC
* FreeBSD 4.10 – 6.2 on x86
* OpenBSD 3.1 to -current on i386, amd64, macppc, alpha, sparc64 and VAX (check the ports)

Source:
http://haproxy.1wt.eu