Lately I stumbled upon a extension for the well known media server Firefly called Fireplay. It’s a easy to use flash based music player interface for Firefly which uses RSP (Roku Server Protocol). The player is able to list playlists, artists, albums, genres and play selections. Because it’s a flash based player, you can use it everywhere you like.
It has features like download tracks, cover art, generate XSPF-playlists and more. The included documentation states that future features include playlist generation/editing, shuffle mode, and faster browsing.
The following section describes how to install Fireplay.
# wget http://www.mellberg.org/FirePlay.zip --2009-06-12 23:50:18-- http://www.mellberg.org/FirePlay.zip Resolving www.mellberg.org... 188.8.131.52 Connecting to www.mellberg.org|184.108.40.206|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 104755 (102K) [application/zip] Saving to: `FirePlay.zip' 100%[======================================>] 104,755 114K/s in 0.9s 2009-06-12 23:51:04 (114 KB/s) - `FirePlay.zip' saved [104755/104755] #
2. Copy the zip file to the admin-root directory of Firefly and extract the zip file which contains (four files). The example shows the path for Debian Linux.
# cp FirePlay.zip /usr/share/mt-daapd/admin-root/ # unzip FirePlay.zip Archive: FirePlay.zip inflating: FirePlay.html inflating: FirePlay.readme.txt inflating: FirePlay.swf inflating: AC_RunActiveContent.js #
3. Open the usual Firefly URL in your browser followed by the Fireplay page
It is necessary to enter the Firefly admin password, set in the FireFly configuration file (mt-daapd.conf).
It is also possible to serve FirePlay using a webserver like Apache.
Have fun playing songs!
Recently I had to use a laptop for a course I was doing. This Fujisu Siemens Amilo Li 2727 laptop came with Windows Vista pre-installed. Since the installed OS didn’t matter for the course I installed the latest Ubuntu which is 9.04 (Jaunty). All worked well except for the wireless card (Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 04)). The network applet says “Wireless is disabled”. The ath5k driver for the wireless card is being correctly initialised, as you can see:
[ 12.170260] ath5k_pci 0000:08:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 12.170274] ath5k_pci 0000:08:00.0: setting latency timer to 64 [ 12.170439] ath5k_pci 0000:08:00.0: registered as 'phy0' [ 12.355693] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [ 264.864848] ath5k phy0: noise floor calibration timeout (2442MHz)
You can also use the following command to see if the device is blocked (not tuned on!):
$ sudo rfkill list 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes
It appears that the wireless card is enabled but not activated, so you’ll need to turn it on. Using Windows you use the Fn-F1 key combination to activate the wireless card, but this doesn’t work with Linux. The easiest way to get wireless going is by activating a kernel module called acer_wmi. As soon as you execute the following line you’ll notice the wireless led will light up. There are other ways, but this is by far the most easy and elegant way to do it.
$ sudo modprobe acer_wmi
The wireless card is now active! Wait a moment and you’ll see wireless networks appear in the NetworkManager if you’re in range. Just for the record I am using Ubuntu kernel 2.6.28-11-generic at the moment of writing.
To make this solution last on a reboot, you’ll have to add the module name ‘acer_wmi’ to ‘/etc/modules’.
$ echo "acer_wmi" | sudo tee /etc/modules
30 Apr 2010: I can confirm this work-around also works for Ubuntu 10.04 LTS (Lucid).
Version 3 of the Simple Network Management Protocol (SNMP) is developed with as main purpose securing the insecure SNMP protocol. Since I needed to setup SNMP for a monitoring tool I decided to do it the secure way, which is SNMP v3. This article will describe how to configure SNMPv3 on a Cisco device using Cisco IOS, in my case a broadband router.
The first task is to login at the console as a privileged user and switch to configuration mode.
router#conf t Enter configuration commands, one per line. End with CNTL/Z. router(config)#
The next task is to define a view. To keep it simple, we’ll create a view that allows access to the entire internet subtree:
#snmp-server view readview internet included
Next, create a group that uses the just created view. This command creates a group called readonly and v3 means that SNMPv3 should be used. The auth keyword specifies that the entity should authenticate packets without encrypting them. The read readview says that the view named readview should be used whenever members of the readonly group access the router.
#snmp-server group readonly v3 auth read readview
The following command creates a user called snmpro, who belongs to the readonly group. auth md5 specifies that the router should use MD5 to authenticate the user (sha is also possible). The next item is the user’s password or passphrase, which is limited to 64 characters. The last item priv des56 specifies the encryption of the SNMP packets.
#snmp-server user snmpro readonly v3 auth md5 password priv des56 passphrase
This configuration uses encryption to prevent passwords from being transferred in clear text and also encrypts the SNMP packets themselves, which may contain information that you don’t want available to the public.
End config mode with CNTL/Z or simple type ‘end’. And issue ‘write mem’ to save the current configuration to non-volatile memory to make this change permanent.
router(config)#end router#write mem Building configuration... [OK] router#
To verify if it’s working you can use snmpwalk. In the example below I use a Linux system to execute the snmpwalk command to request the system description (sysDescr.0) from a host called router.
$ snmpwalk -v 3 -u snmpro -l authPriv -a MD5 -A password -x DES -X passphrase \ router sysDescr.0 SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software, C870 Software (C870-ADVSECURITYK9-M), Version 12.4(15)T5, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2008 by Cisco Systems, Inc. Compiled Thu 01-May-08 02:31 by prod_rel_team $
As you can see the system description is returned successfully.
If you need to get rid of some table rows, in my case a Sun IDM logging table, you can use the following steps.
1. Create a backup in case you have done some thing wrong u can always revert back.
create table waveset.log_backup as select * from waveset.log;
2. Check if these are the records you want to keep and rest all delete.
select * from waveset.log_backup where repomod between'26-MAR-09' and '01-MAY-09';
3. Delete logging from timestamp type collumn ‘REPOMOD’ between dates:
delete from waveset.log_backup where repomod between'26-MAR-09' and '01-MAY-09';
4. if this works do the same on the real table instead of the backup table.
Optionally you can repeat the same trick on the waveset.syslog table, which also can grow to huge proportions.