Free pearpc 0.4 cdrom software for linux

PearPC is an architecture-independent PowerPC platform emulator capable of running most PowerPC operating systems.

This release fixes an ugly partition mapping bug which prevented PearPC to boot OpenDarwin. But the fix might cause regressions: so if your image is no longer booting and you can compile pearpc yourself, please talk to the pearpc-devel mailing list.

Installation:

-Get the Mandrake Installations CDs from a near mirror.
-Read the getting started document first.
-Join the club.
-Make sure you have configured with a big harddisk (3 GiB should do) and a CDROM with the Mandrake 9.1 PPC CD1 inserted. Select a 15 bit video mode. (ppc_start_resolution to 1, 4 or 7)
-Boot and you should get the yaboot menu.
-Press enter and wait.
-At some point, a graphical installer will show up.
-I wont partition your disk for you so you have to do it on your own
create 2 partitions: Apple bootstrap and a Linux onecontinue install.
It will ask you to insert another CD. Click "Change CD" and choose a different .iso or simply insert a different CD. Continue.
-Something bad may happen in the end of the install. Nevermind.

While the CPU emulation may be slow (1/500th or 1/15th, see above), the speed of emulated hardware is hardly impacted by the emulation; the emulated hard-drive and CDROM e.g. are very fast, especially with OS that support bus-mastering (Linux, Darwin, Mac OS X do).

Because the author has only access to a little-endian machine, PearPC will most likely only run on little-endian architectures. This shouldnt be hard to fix and the author would fix this himself if he such hardware. (You can donate some big-endian hardware to get this fixed!)

Equally, PearPC will probably only run on 32-bit architectures. This shouldnt be hard to fix either. (You can donate...)
A lot of unimplementated features are fatal (i.e. will abort PearPC).
Timings are very still a little bit inaccurate. Dont rely on benchmarks made in the client.

PearPC lacks a save/restore machine-state feature.
No Altivec support yet but being worked on.
No LBA48 (but LBA). Currently no support for hard disks greater than 128 GiB. Disks > 4GiB are not tested very well.

OraRep is a PL/SQL snippet (embedded in a shell script) which creates a well-formatted HTML report on a given database instance, providing you with an overview on your instance(s), some hints for performance tuning, and more.
It has been tested with Oracle 8.1.7, 9.0.1, and 9.2. The script easily fits into a cron task to be run on a regular basis. Sample output (HTML) is included.
OSPRep does the same job for Oracle StatsPack Reports based on SnapShot Levels up to 7, and provides additional "plugins" for more detailed reporting on special issues.
The project also optionally creates a separate page with charts to visualize the results and more.
Enhancements:
- This release has working Oracle 10g support.

cdspeed is an application that can decrease the speed of you cdrom. Modern cdrom drives are too fast. It can take several seconds on a 60x speed cdrom drive to spin it up and read data from the drive. The result is that these drives are just a lot slower than a 8x or 24x drive. This is especially true if you are only occasionally (e.g every 5 seconds) reading a small file. This utility limits the speed, makes the drive less noisy and the access time faster. cdspeed is also very good if you prefer to listen to the musik on your mp3 CDs rather then the noise of your CD drive.
Note: recent versions of the eject command include the functionallity of cdspeed (via the -x option).
Installation instructions:
to compile type:
make
to install cdspeed to /usr/bin type:
make install
You can copy the script cdmount to /usr/bin,it will first reduce the speed and then mount the cd. See the explanations inside the cdmount script for further details.
Enhancements:
- 2004-03-31 Roberto Foglietta added the init script for Mandrake distributions

mysqlWisp is a project which provides a standalone or mysqlISP-controlled subsystem.
mysqlWisp provides a standalone or mysqlISP-controlled subsystem for managing one or hundreds of hotspots with access controlled by iptables, MAC addresses, IP addresses, and passwords.
Access points are connected to a second NIC, and all traffic is initially redirected to a login page.
mysqlWisp provides a mysqlISP family standalone or mysqlISP controlled subsystem for managing 1 or 100s of hotspots with full iptables/MAC+IP+Login+Passwd controlled access.
Easy on the end-user -and the hotspot staff- wide open WAPs are supported. The WAP -or LAN of WAPs- is connected to a 2nd NIC (like eth1 for example, or via a WAP capable card for low cost and very flexible linux WAP/Gateway box.) The model used is the captive portal: "redirect all traffic to hotspot login page -unless logged in" on the WAP/Gateway controlled by a local instance of mysqlWisp.
The gateway linux server running mysqlWisp usually will also provide dhcpd, named, and two instances of apache2: One for the webmin and the other the login page. After hotspot user logs in, she then is allowed through the WAP/Gateway, via advanced iptables SNAT, DNAT and REDIRECT rules managed by mysqlWisp.
Started adding accounting and QoS control along with mysqlCart provided online credit card processing support.
Enhancements:
- Adding mysqlISP external job queue handling.
- Adding more WISP AAA/NOC support based on Chicago installation.
- Use tUser.cProfile for cMAC and cIP if exists (fixed users.)
- Add cProfile dictionary to tConfiguration to check new user addition.

Mounttero automatically mounts most storage devices such as USB drives and cameras, DVDs, CDROMs, hard disks, and floppies.

Devices are mounted when users opens their directory, such as /mnt/auto/cdrom, and are unmounted when the directory remains unused for four seconds.

Usage

For example, when user opens directory /mnt/auto/usb/, digital camera is automatically mounted and all the pictures shown in the directory. After four seconds of inactivity, device is unmounted and can be detached.

Manual Configuration

The rest of this document describes manual configuration of mounttero. If you installed the rpm, it did all this configuration automatically and you dont need manual configuration. The scripts below contain some latest and greatest version 0.5 improvements that have not made it to rpm yet, namely more usb partitions.

Create the directories used by the automounter. The directory is the one mentioned in /etc/auto.master:

# mkdir -p /mnt/auto/autofs

Create auto.master to tell autofs daemon that /mnt/auto/autofs directory is handled according to auto.tero

# /etc/auto.master
# mountpoint map options # see also: man 8 autofs
/mnt/auto/autofs /etc/auto.tero --timeout=4

List the actual mountpoints and devices in the automounter map

# /etc/auto.tero
# http://iki.fi/karvinen/linux/doc/automatic-mounting-autofs.html
# mountpoint_key options location_device # man 5 autofs
cdrom -fstype=auto,ro,nosuid,nodev,user :/dev/cdrom
cdrom1 -fstype=auto,ro,nosuid,nodev,user :/dev/cdrom1
usb -fstype=auto,nosuid,nodev,noexec,user,gid=100,umask=000 :/dev/sda1
# second and third partitions in usb device:
usb2 -fstype=auto,nosuid,nodev,noexec,user,gid=100,umask=000 :dev/sda2
usb3 -fstype=auto,nosuid,nodev,noexec,user,gid=100,umask=000 :dev/sda3
floppy -fstype=auto,nosuid,nodev,noexec,user,gid=100,umask=000 :/dev/fd0

hda1 -fstype=auto,nosuid,nodev,user :/dev/hda1
hda2 -fstype=auto,nosuid,nodev,user :/dev/hda2
hda3 -fstype=auto,nosuid,nodev,user :/dev/hda3
hda4 -fstype=auto,nosuid,nodev,user :/dev/hda4

hdb1 -fstype=auto,nosuid,nodev,user :/dev/hdb1
hdb2 -fstype=auto,nosuid,nodev,user :/dev/hdb2
hdb3 -fstype=auto,nosuid,nodev,user :/dev/hdb3
hdb4 -fstype=auto,nosuid,nodev,user :/dev/hdb4

hdc1 -fstype=auto,nosuid,nodev,user :/dev/hdc1
hdc2 -fstype=auto,nosuid,nodev,user :/dev/hdc2
hdc3 -fstype=auto,nosuid,nodev,user :/dev/hdc3
hdc4 -fstype=auto,nosuid,nodev,user :/dev/hdc4

hdd1 -fstype=auto,nosuid,nodev,user :/dev/hdd1
hdd2 -fstype=auto,nosuid,nodev,user :/dev/hdd2
hdd3 -fstype=auto,nosuid,nodev,user :/dev/hdd3
hdd4 -fstype=auto,nosuid,nodev,user :/dev/hdd4

# Serial ATA (SATA) disks are IDE emulated in Linux 2.6
hde1 -fstype=auto,nosuid,nodev,user :/dev/hde1
hde2 -fstype=auto,nosuid,nodev,user :/dev/hde2
hde3 -fstype=auto,nosuid,nodev,user :/dev/hde3
hde4 -fstype=auto,nosuid,nodev,user :/dev/hde4

# (c) 2003, 2004-05-29, 2004-09-19 Tero.Karvinen atta iki.fi

# /etc/init.d/autofs restart

Now drives are automatically mounted when you try to access them. You can test it by inserting a cdrom, and cd /mnt/auto/autofs/cdrom. The CDROM is automatically mounted, and ls should show you contents of the cd. When you cd to another directory, such as home directory (cd), CDROM is umounted in four seconds and the eject button in the drive starts working.

To see which drives are mountable (have discs in drive), you can create symlinks (similar to shortcuts) to the mountpoints. You can create the symlinks manually for each drive, for example

# cd /mnt/auto/
# ln -s autofs/cdrom cdrom

FIRE is a portable bootable cdrom based distribution with the goal of providing an immediate environment to perform forensic analysis, incident response, data recovery, virus scanning and vulnerability assessment.
Also provides necessary tools for live forensics/analysis on win32, sparc solaris and x86 linux hosts just by mounting the cdrom and using trusted static binaries available in /statbins.
Main features:
Forensics workstation/Data Recovery
- Instantly deploy a forensics workstation with tct, tctutils, mac-robber, and autopsy also provides perl 5.6.1 compiled with Large File Support.
Live System Incident Response
- Binaries are available for Incident Response on a live machine.
Virus Scanning
- Utilizing F-Prot 3.11beta http://www.f-prot.com you can scan for virii, worms, trojans, and all around harmful code.
- Just mount the filesystems that you want to scan and execute f-prot .
- Any filesystem you can mount, you can scan. mount and scan fat/ntfs/ext2/ext3/reiserfs partitions
- Scan your windows machines offline for virii that may not be detected with an "after the fact" anti-virus
- software installation.
Pen-Testing Platform
- I should NOT have to explain this portion: If the tools you would like to use are not in the distribution please make a request!

hamsterdb is a database engine written in ANSI C. hamsterdb supports a B+Tree index structure, uses memory mapped I/O (if available), and can create in-memory databases.
Main features:
- B+Tree index with variable length keys
- Configurable page size and cache size
- ANSI-C implementation, should be portable on all platforms, also embedded
- Uses memory mapped I/O for fast disk access (but falls back to read/write if mmap is not available)
- Uses 64bit file pointers
- Endian-independent (not tested, though)
- Support for in-memory-databases
Enhancements:
- This release implements "record number" databases; these databases behave like "auto-increment" tables in SQL.
- The keys of new records are automatically assigned and incremented with each insert.
- Also, a few minor bugs were fixed, and some optimizations took place; the generated database files are much smaller now.

WmCdrom is a dock application for WindowMaker. When launched WmCdrom creates a 48 x 48 pixel showing an icon (centered in a 64 x 64 pixel tile). To dock WmCdrom, left-click on the border of the tile and drag the tile to the dock area.
By clicking the icon you can mount,unmount,eject and launch a filemanager.
- The first left-click will mount the media.
- The second left-click will launch a filemanager on the mount point.
- The first right-click will unmount the media.
- The second right-click will eject the media (when supported).
Installation:
- Unpack the archive: tar xjf wmcdrom-0.x.tar.bz2
- Verify the PREFIX setting in the Makefile. wmcdrom will install to /usr/X11R6/bin
- Type make
- As root, type make install
- Launch wmcdrom and then drag the icon to the dock
You can test wmcdrom before install it by lunching (from source directory):
./wmcdrom -i cd /dev/hdc
(supposing your cdrom device is /dev/hdc)
WARNING: use the same device of your fstab ("less /etc/fstab" to verify)