Free stop dog barking whistle software for linux

DOG Data Organizer provides a bookmark organizer for various bookmark types.

DOG is a personal knowledge manager based on topic maps. It currently specializes in managing bookmarks.

It imports and exports Netscape, Mozilla, and KDE2 (XBEL) bookmark files, and it imports KDE1 bookmarks and Windows IE Favorites.

Yellow Dog Linux is the Premier Linux Operating System for PowerPC.
Proven world-wide as the preferred Linux OS for the Power architecture, v4.1 brings Terra Soft into its 8th year of Power Linux development and support. Yellow Dog Linux v4.1 marks a returning point in Terra Softs effort to again provide a leading desktop Linux OS.
Yellow Dog Linux combines the preferred desktops KDE and Gnome with the latest sound and graphic card support, leading (but not bleeding) edge kernels and stable, functional compilers for code development. And of course, the foundation applications and servers expected of all modern Linux operatings systems for web, database, email, and network services.
What will you do with your PowerMac after Apple switches to Intel?
We have an answer--Faster, more stable, and far more efficient as a desktop OS, Yellow Dog Linux is a solid replacement (not just an alternative) to OSX. Breath new life into your PowerPC G3 and G4, giving it a second wind as a personal workstation, or a new function as a web, email, or data server. Want to see how your G5 runs Linux? You may dual-boot both OSX and Yellow Dog Linux or take the leap and run Yellow Dog Linux alone, taking advantage of the multitude of included, freely available, and commercial applications.
Main features:
New or Improved Device Support
- Backlit keys.
- PCMCIA cell phone and modem support.
- Support for Atheros wi-fi cards.
- Dual head config via the GUI.
- Install direct to and boot from FireWire drives.
- USB device auto-mount under both KDE & GNOME.
- Greatly improved sound support.
- Graphical Up2Date package install and update tool.
- Support for the latest Apple Power Books.
- Beta support for Apple G5 PowerMacs with dual core CPUs.
- Beta Extreme driver will be available shortly after release, via YDL.net Enhanced accounts.
Enhancements:
- We are pleased to announce the release of Yellow Dog Linux 5.0.2, a single Install DVD with support for the Apple G4 and G5 computers, Sony PS3, and IBM System p servers, including the JS20/21, OpenPower, and current POWER5 systems. Yellow Dog Linux 5.0.2 offers: kernel 2.6.22-rc4; SDK v2.0 for Cell BE; more than 70 bug fixes and updates; continued support for both 32-bit and 64-bit systems; beta IBM System p support. The IBM Software Development Toolkit (SDK) for Cell Broadband Engine (Cell BE) is a complete package of tools which allows developers to program optimized applications for platforms built upon the Cell BE. The SDK is composed of development tool chains, software libraries, and sample source.

Blue Frog allows you to actively demand spammers to stop sending you spam. Blue Frog automatically and securely posts complaints and opt-out requests at spam sites asking spammers to remove Blue Community members from their mailing lists.
The Do Not Intrude Registry creates an incentive for spammers to stop sending unsolicited e-mail to members of the Blue Community.
Consumers and businesses may register their e-mail addresses or their entire e-mail domains, and receive less spam simply because spammers would remove them from their mailing lists.
Consumers and businesses alike can join the service, free of charge, by becoming active members of the Blue community. As an active member of the community, you download the Blue Frog client and actively complain and request to opt-out of spam. The Do Not Intrude Registry empowers you to exercise your right to opt out of spam safely and automatically.
Businesses may also subscribe with the Do Not Intrude Registry without being active members of the community. This paid subscription service allows you to register your e-mail domain in the Registry and receive less spam without installing software in your network.
The Blue Frog is a simple and straightforward solution to spam:
1. Users join the Blue Community
Blue Community members add their e-mail addresses or e-mail domains to the Registry. Active members install Blue Frog on their machines.
2. Spammers use mailing lists
Spammers are required to stop sending spam to all Blue Community members. Non-complying spammers maintain mailing lists that may contain addresses of Blue Community members.
3. Members receive spam
When a spammer sends bulk e-mail using his lists, some Blue Community members may receive this spam message to their mailboxes.
4. Members report their spam
Our experts identify the merchants using spam to advertise their sites and prepare scripts instructing Blue Frog how to post complaints. Additionally, Reports are sent to government agencies and ISPs asking them to take action against these sites.
5. Members complain about spam
Blue Frog clients, installed on active Community Members machines, automatically post complaints at spam sites by filling forms they contain. Posting complaints is safe and does not expose your identity.
6. Merchants process complaints
A single opt-out complaint is posted per each spam message received. Merchants process complaints posted by active community Members rather than process potential customers purchase orders.
7. Spammers comply with the Registry
Spammers and merchants choose to stop sending spam to the all Blue community members. It allows them to avoid receiving complaints and to stop sending spam to people who will never buy their products.
8. Members stop receiving spam
Blue Community members will no longer receive spam simply because spammers will stop sending it to them!
Enhancements:
- Linux compilation fixes
- Documentation changes

Enterprise File Exchange (EFX) slots in where email file attachment limits stop your users from sending those important files to a contact.

In the EFX world, the user visits the EFX site, uploads the file, enters the receivers email address and lets the system notify the receiver that theres a file waiting for them, via a simple email message.

Senders need to sign up, and the EFX system only allows transfers between internal users (those with addresses in an approved list) and external users, never external to external.

It is written in Python, using the Pylons framework.

This project is licensed under the GNU GPL version 3.

xmms-alarm is a plugin which allows XMMS to be used as an alarm clock.
Main features:
- alarm start time
- sleep time (so the alarm will stop after a while)
- volume fading time
- loading a seperate playlist for the alarm
- executing a shell command when the alarm goes off
- the option to choose a starting volume when fading

Apollo is an open-source developer test skeleton toolkit for Web Start. Apollo lets you turbo-charge Web Start apps without Web Start to speed up your compile/run/test/debug/goof-off cycle avoiding the hassle of stuffing, signing, uploading or downloading your jars every time you rearrange a comma in your source code.

Apollo is not a replacement for Web Start (OpenJNLP, NetX or any other app launcher). Apollo is more like a test emulator (such as POSE - Palm OS Emulator) helping you to speed up your development between full-blown, time-consuming, irreplaceable, real Web Start workouts.

Apollo cant fake every Web Start bell and whistle (e.g. download on demand) but outshines Suns Web Start dumb dev pack stubs that merely let you compile your source. Apollo lets you popup your household browser and more without calling in the Web Start machinery.

Apollo consists of a jar that you can use to replace Suns javax.jnlpx stubs residing in jnlp.jar that only allow you to compile your code and that ship with Suns Web Start dev pack.

Apollo is a thin wrapper around Suns javax.jnlpx services. If your app runs under Web Start Apollo will automatically detect it and pass all runtime service calls (such as poping up a browser window) on to the Web Start engine. If your app, however, runs without Web Start Apollo will kick in and mimick Web Starts runtime services.

To use Apollo replace all javax.jnlpx imports with apollo. Example:

import javax.jnlpx.*; // Web Start only
import apollo.*; // Web Start plus Apollo-propelled stand-alone launching

To spare you from learning yet another API set Apollo reuses all runtime service class and method names. The only exception is Apollos ServiceManager class that adds type-safe methods to lookup pre-defined runtime services (e.g. lookupBasicService()) avoiding unexpected runtime errors and reducing source code bloat. Example:

import javax.jnlp.*
...
BasicService bs = (BasicService) ServiceManager.lookup( "javax.jnlp.BasicService" );
bs.showDocument( new URL( "http://vamphq.com/times" ) );

becomes

import apollo.*;
...
BasicService bs = ServiceManager.lookupBasicService();
bs.showDocument( new URL( "http://vamphq.com/times" ) );

or

import apollo.*;
...
ServiceManager.lookupBasicService().showDocument( new URL( "http://vamphq.com/times" ) );

Apollo lets you configure the codebase or the online/offline status of your app if you want to run it without Web Start but still use BasicService.getCodeBase() or Basic.isOffline().

By default BasicService.isOffline() returns false (meaning your app is online). If you want to change the setting you can pass the property apollo.offline=true to your app. As an alternative you can also add apollo.properties to your classpath or bundle it with your apps jar in the root directory. Inside the apollo.properties file add the apollo.offline property to match your desired setting. Note, that all apollo properties only work if your app runs without Web Start.

By default BasicService.getCodeBase() uses the working directory returned by the system property user.dir. To use a different codebase pass the property apollo.codebase=your_url_here to your app. As an alternative you can also add the apollo.codebase property to the apollo.properties file in your apps root directory where Apollo picks it up if you run your app without Web Start.

dvbcut is a Qt application that allows you to select certain parts of an MPEG transport stream (as received via Digital Video Broadcasting, DVB) and save these parts into a single MPEG output file.
dvbcut follows a "keyhole surgery" approach where the input video and audio data is mostly kept unchanged, and only very few frames at the beginning and/or end of the selected range are re-encoded in order to obtain a valid MPEG file.
dvbcut needs to create index information on an MPEG file first. Therefore, when loading an MPEG transport stream file, it also asks you for a filename of an index file.
If you choose an existing file, it is loaded and used as index if suitable. (That means, that dvbcut performs some sanity checks on the index itself and also checks if the index describes the chosen MPEG file.) If you select a file which does not yet exist, dvbcut creates the necessary index in place.
After opening the MPEG file, you can navigate through the video by means of a linear and a log scale slider. While the first represents the whole video, the latter enables you to precisely select frames close to the current frame.
At any place in the video, you can add START, STOP, CHAPTER and BOOKMARK markers. Markers are shown in the list on the left. With the START and STOP markers you determine what parts of the video you want to write to a new file. dvbcut starts at the first START marker and proceeds until it encounters a STOP marker.
If there are more START markers after that STOP, it will continue at the next START marker, and so on. Every START marker, which follows a START with no STOP inbetween, is meaningless. So is a STOP marker before the first START or after another STOP (with no START inbetween).
dvbcut project supports AC3.
Please be aware, that at the moment, DVBCUT only works with MP2 audio.
Enhancements:
- New upstream version.

wifistatd is a script which generates a PNG graphing signal/noise/link levels on a selected wireless interface.

To install wifistatd on a UNIX machine untar the archive with program.
Then you must type:

./wifistatd.pl install

If everything went OK (it should), youll get the db.rrd database file in your current working directory.

To configure daemon edit the head part of wifistatd.pl.

getting_started
To start, just type:
./wifistatd.pl start

To stop, just type:
./wifistatd.pl stop