For those of you like me who have a worn-off sticker on the device, you can do a factory reset (button in small pinhole on bottom), and the default WIFI password is the MEID of the device.
Note: It begins with 091
For those of you like me who have a worn-off sticker on the device, you can do a factory reset (button in small pinhole on bottom), and the default WIFI password is the MEID of the device.
Note: It begins with 091
/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 208.85.x.x
netmask 255.255.255.x
gateway 208.85.x.x
auto eth0:1
iface eth0:1 inet static
address 208.85.x.x
netmask 255.255.255.x
For PV ethernet support in the guest, you’ll need these drivers now available from the Fedora project:
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/
Blackberry (RIM) data and email service confirmed down since 2:00AM Eastern 01/29/2011, with no ETA in sight. Looks like all carriers are affected, with AT&T and Verizon confirmed.
SAM4 has a slightly different database format and filesystem layout than SAM3. You should not try an in-place upgrade, or bad things can happen. The best way to upgrade if you have a large or refined playlist, is to install SAM4 along side SAM3 and copy the playlist tables over. This way you can leave SAM3 running while you install and set up SAM4’s settings and encoders, then make a clean cutover without losing your audience.
1. First, install SAM4 in it’s own location, separate from SAM3. For example, c:\program files\spacial audio\SAMBC4
2. When launching SAM4 for the first time, you MUST define custom MySQL database settings. Change the default database name from SAMDB to SAMDB4
3. Dump your SAM3 playlist with the following command (mysql/bin must be in your path):
mysqldump -u root --database SAMDB --table songlist --table category --table categorylist --skip-extended-insert --complete-insert --no-create-db --no-create-info > SAM3_songs.sql
4. Import the playlist into SAM4:
mysql -u root SAMDB4 < SAM3_songs.sql
5. Now, press F5 on the SAM4 playlist window to see your songs. Be sure to run ‘Tools -> Mass Tagger -> Load ALL Tags’
6. Configure all settings and encoders, set encoders to auto connect. Start one of the decks.
7. Shut down SAM3.
Now SAM4 should connect and take over your streams.
A quick non-destructive test of disk write performance on Linux. Useful for testing cheap HDD’s (write will almost always be worse than read):
dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
If compiling a Vanilla kernel for CentOS, you may encounter the following after rebooting:
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
[...]
Kernel panic - not syncing: Attempted to kill init!
To resolve the booting issues, be sure to modify .config to include the following and recompile the kernel:
CONFIG_SYSFS_DEPRECATED_V2=y
It can also be found in menuconfig:
General Setup --> Enable Deprecated Sysfs Features
To validate the database:
gfix -v -f database_file
To (attempt to) repair the database:
gfix -mend database_file
Sometimes an email account goes over quota and the quota can’t be adjusted due to the following error:
Error invalid maildir size file
The following commands ran as root will resolve most email quota issues for a Cpanel account, including incorrect quota calculations. Substitute <cpaneluser> with the Cpanel user which owns the email account having issues.
cd /home/<cpaneluser>/mail/
rm -f maildirsize
/scripts/generate_maildirsize --confirm --allaccounts --verbose <cpaneluser>
cd ../.cpanel
rm -f email_accounts
rm -f email_accounts*
If the file is not in the %systemroot%\system32\dns directory, the full path to the zone file will be shown on the General tab.
Since most zone data is held in the registry, restoring the %systemroot%\system32\dns from backup isn’t enough – you’ll need to manually populate the DNS zones in the DNS console, and choose the ‘specify location’ option for the zone file on each domain to get the records back.