Re: Complete Linux Recording Package Ready To Roll.

From: Jona Vark (noemail_at_all.com)
Date: 08/14/05


Date: Sun, 14 Aug 2005 20:00:21 GMT


"Dallas Bob" <dallas_holms@yahoo.com> wrote in message
news:1124046570.005643.121220@o13g2000cwo.googlegroups.com...
I have a complete, fully configured Linux in a box recording package
for sale. This system is based on the Agnula project
http://www.agnula.org/ and includes a complete Linux recording system
for both audio and video.

The heart of the system is an IBM Thinkpad T-23 complete with a an RME
interface.
http://www.sweetwater.com/store/detail/Cardbus/

Software included with the rhmudi package as listed here:
How to install Rehmudi-2.0
--------------------------

A) Install From CDROM
   -----------------

If you had already installed Fedora Core 1

1. insert cdrom Rehmudi-2.0 into the CDROM Drive
2. be root and execute "mount /mnt/cdrom" (mouting cdrom)
3. execute "cd /mnt/cdrom" (enter in the directory where there is
Rehmudi trees)
4. execute "./install.sh" (install Rehmudi)
5. After installation : reboot your machine
6. during reboot kudzu will detect you materiels, click "OK" or
"Configure" for all periphericals detected (all configuration will be
done automatically)
7. you can test for example alsaplayer

nb : if you don't have any sound, check your sound mixer
nb : not sound after checking your mixer , reboot your machine to take
alsa driver effect
nb : after reboot, always not sound, use alsaconf to configure manually
alsa drivers that will update your /etc/modules.conf file ... reboot

B) If your machine is blank (not OS installed in you machine)

1. insert first cdrom Fedora Core 1, boot on this cdrom
2. follow anaconda instructions ....
3. anaconda will ask you to insert the 2nd and 3th cdrom
4. after installation , follow instructions of A) How to
install from CDROM

nb : Test was done with "Desktop Installation" option of Fedora Core 1
installation ..... i will advice you to install complete distribution
of Fedora Core 1 to avoid dependencies problems Rehmudi-2.0

More about installation of Fedora Core 1 before installing Rehmudi
------------------------------------------------------------------

1. first, you have to install all Fedora Core 1 with KDE or GNOME
graphical interface. If you have already installed Fedora Core 1 full
release, see next

I advice you to install the full distro of Fedora Core 1 because of all
dependencies of Agnula Packages ...

If you did not install the full distro of Fedora Core 1, so update
your Fedora Core 1 for full distro (it will only add all packages that
were not installed during your latest install).

If you are still on Red Hat Linux 7.3, So update you machine on Red Hat
Linux 8.0 , 9.0 and Fedora Core 1 in final

2. download "Rehmudi-2.0" (iso, tar.bz2 ) from
http://download.agnula.org/rehmudi as "anonymous" user

3. mount /mnt/cdrom
   cd /mnt/cdrom
   ./install.sh

"install.sh" script will prepare your system/hardware environment ....
by installing kernel in Low Latency, alsa module (alsa-kernel), kudzu
(for automatic detecting sound cards)

4. reboot your machine for the first time (it will configure all sound
card, mouse,network interface etc ... devices ) and allow you to boot
from the new kernel. Please boot on the "2.4.22-6.ll" or on the
"2.4.22-6.ll.smp" kernel not on your old kernel.

   During the reboot, kudzu will redetect all your hardwares, please
click on OK for all kudzu detects

5. After rebooting your machine, test if you have sound with alsa
drivers (execute xmms or alsaplayer)

If you don t have any sound check :
mixer (alsamixergui)
sound card connecting with your speakers
In final, execute "alsaconf" for configuring alsa drivers detecting
(/etc/module.conf)

nb : theorically, kudzu detect your sound card and update your
/etc/module.conf

6. Make the final reboot now to take Alsa sound devices effects.

Technical specification
-----------------------

contain of agnula_installer tree :

Bonus
Changelog
docs
errors
install.py
install.sh
list_packages
oldconfig
RPM-GPG-KEY-fedora
RPMS
SRPMS
uninstall.sh

* Bonus contains some alsa packages and kernel with newer version and
jdk for Jmax, you can find back install.py.old that is version 1.1 of
rehmudi installer ... if you usually use it, feel free to use it back

~/list_packages/install.in contain the list of Agnula packages for
install.py script it's now in ~/list_packages
~/list_packages/g_*.rpm list of group dependances of packages for
install
~/list_packages/u_g_*.rpm list of group dependances of packages for
uninstall

* docs contains documentations of rehmudi-2.0, all descriptions of each
RPM package

* errors, some errors compiling during rehmudi building, those RPMS
will be not in rehmudi-2.0, just for developpers who want to contribute
in our projetc and offer us patches ... thank you by advanced

olfconfig initially empty, but after installation ... it contains your
old system configuration like /etc/modules.conf and
/etc/sysconfig/hwconf .... this directory is used for restoring your
old configuration

install.sh install kernel Low Latency and pmw packages and call
install.py for GUI installer

install.py GUI installer which install all Agnula packages

nb : the particularity of rehmudi-2.0 is : When Gui installeur is
displayed, this allow you to select the packages that you want, by
default all packages are choosen (set 1).
nb : At line 168, you can switch button.set_active(1) or
button.set_active(0) for select all or deselect all .

install.log is created by install.sh during the install process

docs/INSTALL is this file

RPMS contains all binary

SRPMS contains all SOURCES RPMS

Alsa drivers
------------

I've only substituted the PCI OSS drivers by the PCI ALSA drivers, if
never you have an ISA sound card again, please configure it bye
"redhat-config-soundcard".

If your ALSA soundcard driver is in the alsa-drivers-0.9 package, but
it was not loaded in the memory (see bye "lsmod"), please add it into
the /etc/modules.conf manually and see www.alsa-project for detailed
support, or mail me on users@lists.agnula.org, i'll try to reply you as
soon as possible. Check if alsasound service is UP if not execute
"chkconfig alsasound on" Or execute "alsaconf".

How to boot by default on the new kernel
----------------------------------------

By default, the OS boot on your new kernel .... in Low Latency ... if
not :

You can configure /boot/grub/grub.conf by setting default=<value> ("0"
if the new kernel is on the first line, or "1" is it is on the second
line ...) to boot you machine automatically on the new kernel

for example :

in my /boot/grub/grub.conf

default=1 # boot on the 2.4.22-6.ll kernel by default
timeout=10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.22-6.ll)
        root (hd0,0)
        kernel /boot/vmlinuz-2.4.22-6.ll ro root=/dev/md0 hdd=ide-scsi
        initrd /boot/initrd-2.4.22-6.ll.img
title Red Hat Linux (2.4.22-6.llsmp)
        root (hd0,0)
        kernel /boot/vmlinuz-2.4.19-1.llsmp ro root=/dev/md0
hdd=ide-scsi
        initrd /boot/initrd-2.4.19-1.llsmp.img
title Red Hat Linux (2.4.18-3smp)
        root (hd0,0)
        kernel /boot/vmlinuz-2.4.18-3smp ro root=/dev/md0 hdd=ide-scsi
        initrd /boot/initrd-2.4.18-3smp.img

default=1 --> means that i'll boot on the "(2.4.21-1.llsmp)" kernel
because my machine is 4 processors

Ardour
------

Before executing "ardour" (/usr/bin/ardour) do not forget to copy from
/usr/ardourrc to $HOME/.ardourrc

"cp /usr/ardourrc $HOME/.ardourrc"
"/usr/bin/ardour"

nb: don t forget to run jackd before executing ardour ("jackd -d alsa")

Jmax

----
Name        : jmax-agnula-java             Relocations: (not
relocateable)
Version     : 4.0.2                             Vendor: (none)
Release     : 2                             Build Date: Tue 14 Oct 2003
11:17:28 AM CEST
Install Date: (not installed)               Build Host:
localhost.localdomain
Group       : Applications/Multimedia       Source RPM:
jmax-agnula-4.0.2-2.src.rpm
Size        : 1356317                          License: GPL
Signature   : (none)
Packager    : Patrice Tisserand
Summary     : Java gui for jMax
Description :
Java Graphical User Interface for jMax
IMPORTANT WARNING: Even though the <jmax-java> package itself is
licensed as Free Software under the GNU General Public License (GPL),
it depends upon a proprietary Java runtime environment, so in order
to be able to use it, you would also have to find, install and run
proprietary software.
The AGNULA consortium only provides the package for completeness
reference or reimplementation purposes.
There are freedom-preserving alternatives to this package and we
encourage you to choose those instead, namely the <jmax-bindings>
Python bindings.
Should you choose to proceed, information about the Java Runtime
Environments is available at
 http://www.ircam.fr/jmax
Information about the Java situation and its problems along with
the efforts to finally Free Java are available at
 http://fsfeurope.org/projects/agnula/java.html
so What you have to do to make Jmax running :
cd /mnt/cdrom/Bonus
./j2sdk-1_4_2-nb-3_5_1-bin-linux.bin
<choose> PATH to instal jdk for ex /opt/j2sdk-1_4_2-nb-3_5_1
export PATH=/opt/j2sdk-1_4_2-nb-3_5_1/j2sdk1.4.2/bin
/usr/bin/jackd -d alsa # if jackd is not started, start it because Jmax
need it
/usr/bin/jmax
((The T-23 has 512mb ram and a 20 gigabite hard drive.))
I am asking $3,150.00 for the entire package and that includes shipping
 and insurance to anyplace in the world.
Please email me for more details and thank you for your consideration.
dallas_holms@yahoo.com
Oh.. Yeah.. Seems easy enough. Doh!


Relevant Pages

  • unsubscribe
    ... > Subject: debian newbie... ... If I need to recompile the kernel, ... Also, what other additional packages, ... >> The package you're trying to install presumably ...
    (Debian-User)
  • SUSE Security Announcement: Linux Kernel (SuSE-SA:2004:001)
    ... installable through rpm, because of a bug in RPM (update of ... the kernel source is not ... sources that the binary kernel rpm packages are made from. ... are being offered to install from the maintenance web. ...
    (Bugtraq)
  • [Full-Disclosure] SUSE Security Announcement: Linux Kernel (SuSE-SA:2004:001)
    ... installable through rpm, because of a bug in RPM (update of ... the kernel source is not ... sources that the binary kernel rpm packages are made from. ... are being offered to install from the maintenance web. ...
    (Full-Disclosure)
  • SUSE Security Announcement: kernel (SuSE-SA:2004:010)
    ... The update packages for the SuSE Linux Enterprise Server 7 ... contain any binary kernel in bootable form. ... sources that the binary kernel rpm packages are made from. ... are being offered to install from the maintenance web. ...
    (Bugtraq)
  • [Full-Disclosure] SUSE Security Announcement: kernel (SuSE-SA:2004:010)
    ... The update packages for the SuSE Linux Enterprise Server 7 ... contain any binary kernel in bootable form. ... sources that the binary kernel rpm packages are made from. ... are being offered to install from the maintenance web. ...
    (Full-Disclosure)