How to enable, disable displaying by page and change the number of lines by page in various OS’es

[read more…]

After hitting this bug (yes, again and again) I had to unmount the broken file system and run fsck (twice). But then I apparently hit anoter bug (or a feature?) - I could not mount the file system back.

Neither pwdx not lsof showed any processes using /export/docs. The solution was to recreate the directory:

Snv_92 has been entertaining me since I upgraded from quite stable snv_88. I’m hitting a bug after a bug. (See here).

This is the latest - unkillable process, which can’t be killed with kill -9 or zone reboot. Reboot just hangs. Truss ends up with:

dtrace shows nothing. The only workaround is to reboot the entire system.

See also:

Revenge of the unkillable process
Unkillable process
Bug ID 6455727

What to choose for a home server? The most important difference is not the accelerometers or MTBF but whether the disks will be used in RAID’s.

An excerpt from Western-Digital FAQ:

When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).

Western Digital RAID edition hard drives have a feature called TLER (Time Limited Error Recovery) which stops the hard drive from entering into a deep recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This means that the hard drive will not be dropped from a RAID array.

If you install a RAID edition hard drive in a desktop computer, the computer system may report more errors than a normal desktop hard drive (due to the TLER feature). Western Digital does not recommend installing RAID edition hard drives into a desktop computer environment.

Source: What is the difference between Desktop edition and RAID (Enterprise) edition hard drives?

After upgrading from snv_88 to snv_92 (Solaris 11 or Nevada b92) my home server started spewing  the following errors:

[read more…]

In order to upsample 16/44.1 stream to, for example, 24/96 and play it on the Transporter you need:
[read more…]

After upgrading to Nevada b92 SqueezeCenter refused to start with the following error:

But the actual problem is Scalar::Util. To solve the problem reinstall Scalar::Util and then Compress::Zlib. Use force install if CPAN says that the latest version is already installed:

Sources: whirlpool.net.au and Usenet forums.

Just a brain dump.

• Firefox for Solaris can be downloaded from Contributed Releases
• 3.0 (release) is actually 3.0rc2 for Solaris
• 3.0 eats less resources than 2.x
• Font anti-aliasing is broken (also, see here)
• 3.0 looks faster than 2.x
• 3.0 is EXTREMELY slow if x-forwarded (I tried to forward from a non-global zone to a global one). I heard that the reason might be Xrender lib. Related bug 6699647?
• X-forwarding crashes Nevada b92
• Most of useful extensions are not (yet?) ported to 3.0 (e.g. adblock(updated), tabmixplus (here’s a dev version), X-Ray)
• 3.0 is not included into b93 (see here)
• Field Guide to Firefox 3
• Firefox 3 Revealed - Free PDF book
• BadGC with flash in non-current tab on Solaris (This bug should be fixed in Flash Player 9.0.125.0. See announcement)
• 3.0 becomes an unkillable process if started from a zone

The idea was to use “bare” SqueezeCenter without bundled CPAN (the CPAN directory was moved away) modules, Solaris 11 (or Nevada build 88) and supplied with Solaris PERL and MySQL.

Then if you start slimserver.pl the errors will let you know which CPAN modules to install. For example:

To install a module run the following:

The only exception is Encode/Detect/Detector.pm or Encode::Detect::Detector. It’s has not being touched by the developer for many years and is not recommended for use. The module can be compiled with c++ or g++ (instead of used by default cc or gcc), but with a lot of pain and manual intervention. The easiest way is to get rid of it completely:

• Remove Encode::Detect::Detector from modules.conf (in the root directory of SqueezeCenter)
• Remove or comment the following line in Slim/Utils/Unicode.pm:
  use Encode::Detect::Detector;

For the first time I did not have to do anything special to compile wine. Just configure and gmake. The rest is pretty the same: Picasa runs at 100% CPU load, Firefox 3b5 crashes every 5 minutes ;-)