Un computer cu configuratie echilibrata

Prezint aici o configuratie de calculator pe care personal o consider rezonabila in acest moment. Iata componentele folosite:

• carcasa Antec Sonata III, impreuna cu sursa inclusa in pachet, Antec EA500
• placa de baza Gigabyte EP45-UD3P
• procesor Core 2 Duo E8400, cooler stock
• 4 GB RAM DDR2, 2 module Corsair XMS2 C5C
• 2 hard disk-uri Western Digital Black de 640 GB configurate in RAID0 + RAID1 cu ajutorul MatrixRAID de la Intel, 1 hard disk de 320 GB Seagate 7200.10 SATA
• DVD writer LG SATA
• placa video PowerColor Radeon HD 5770 (se gaseste la Caro Group la un pret rezonabil)
• placa de sunet SoundBlaster X-Fi Titanium Fatal1ty Professional
• placa de retea wireless Asus 802.11G

Bineinteles, daca ar fi cazul sa o iau de la zero, probabil ca as folosi memorii DDR3, insa din motive de compatibilitate, am preferat la momentul respectiv sa folosesc module DDR2. De asemenea, voi schimba cat de curand si placa wireless cu una care suporta 802.11n.

Iata si galeria foto:

Asus adopts NVidia ION

NVidia announced recently that Asus will use the ION chipset to power some of it's products, including:

• ASUS Eee PC 1201N, a netbook built with: Atom N330 (Dual core), 2/3 GB RAM, 12" display @1366x768 pixels, 250/320 GB hard disk drive, Wireless B/G/N adapter, HDMI, SD Card reader, multitouch touchpad, webcam, 6-cell battery. It is expected to run up to 8 hours between battery charges.
• ASUS EeeTop PC ET2002T, a 20" stylish all-in-one PC with touchscreen
  
  
• ASUS EeeBox PC EB1012, a nettop oriented to HD media playback and casual gaming
  


• ASUS EeeBox PC EB1501, which is a nettop including a slot loading DVD burner and Windows 7 license
  
  
  


• ASUS AT3N7A-I, a mini-ITX motherboard built with the Atom 330 dual core processor.
  

The most interesting features of nVidia's ION are:
- Very low power consumption
- DirectX 10 support
- 1080p HD movie playback with 7.1 audio
- Faster 3D performance than competitor's integrated graphics solutions
- Adobe flash playback acceleration (from version 10.1)

FreeBSD build errors: libtool: link: `/usr/local/lib/libxcb-xlib.la' is not a valid libtool archive

I've tried to update a server recently, and I got stuck on build errors for many X11 related packages, with the following message:

libtool: link: `/usr/local/lib/libxcb-xlib.la' is not a valid libtool archive

Of course, I've missed reading /usr/ports/UPDATING, where I could find that on 2009-01-23:

Libxcb shared library version was bumped from 1 to 2. You need to
rebuild any consumer of libxcb.so.1 or some applications will be
linked against two versions of libxcb once libX11 is upgraded.

For portupgrade users:

# portupgrade -rf libxcb

CentOS Mail Server setup: Postfix, Dovecot, Virtual users, MySQL, SASL, Postfixadmin, TLS

I've compiled a cleaner guide for CentOS + Postfix + Virtual users + SASL + PostfixAdmin. At this moment it's not complete yet, it's missing SSL/TLS configuration for Dovecot and Postfix, i'll add it soon. Check the guide here.

CentOS Postfix + Dovecot + SASL auth + mySQL + Postfixadmin HowTo

This is a small guide, showing how to install postfix, dovecot and postfixadmin on a server running CentOS.

Main steps:
- install dovecot

# yum install dovecot

- configure dovecot: modify/replace /etc/dovecot.conf. The authentication is defined as sql, which dovecot supports by defaolt on CentOS contents with something similar to this:

protocols = imap pop3
listen =
ssl_disable = yes
mail_location = maildir:~/
mail_debug = no
verbose_proctitle = yes

# id of postfix
first_valid_uid = 89
last_valid_uid = 89

first_valid_gid = 89
last_valid_gid = 89

maildir_copy_with_hardlinks = yes

protocol imap {
mail_plugins = quota imap_quota
imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep
}

protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}

protocol lda {
postmaster_address = postmaster@elegance-net.eu
hostname =
auth_socket_path = /var/run/dovecot/auth-master
}

auth_executable = /usr/libexec/dovecot/dovecot-auth
auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@

auth_debug = no

auth default {
mechanisms = plain login
passdb sql {
args = /etc/dovecot-mysql.conf
}
userdb prefetch {
}
userdb sql {
args = /etc/dovecot-mysql.conf
}
user = nobody
socket listen {
client {
path = /var/spool/postfix/private/auth
mode = 0666
user = postfix
group = postfix
}
}
}

dict {
}

plugin {
quota = maildir
}

- configure SQL authentication backend for dovecot: create a file, name it dovecot-mysql.conf and place it in /etc:

# file /etc/dovecot-mysql.conf, ver 1.0.7 - 1.1.3 compatible
connect = host=127.0.0.1 port=3306 user=postfix password=mysecretpassword dbname=postfix
driver = mysql
default_pass_scheme = MD5-CRYPT
password_query = SELECT password,CONCAT('/mail/', maildir) AS userdb_home, '89' AS userdb_uid, '89' AS userdb_gid, NULL as allow_nets FROM mailbox WHERE username = '%u' AND domain = '%d' AND active = '1'
user_query = SELECT CONCAT('/mail/', maildir) AS home, '' as mail, '89' AS uid, '89' AS gid, ROUND ( quota / 1024 ) AS quota FROM mailbox WHERE username = %u AND domain = %d

In the above ecample, /mail is the base directory where I store e-mails. I've put 'NULL as allow_nets' because I want to make room for dovecot's 'allow_nets' restrictions support, so I may be able to restrict some user's connecting IP address to a small IP/subnet list. This field is not present on postfixadmin installation, but may be added later to the database structure by modifying 'mailbox' table structure with a tool like phpmyadmin. 89 is postfix's user id, specified statically in dovecot and postfix configuration.


- install development prerequisites: mysql-devel, pcre-devel, rpm-build

# yum install mysql-devel pcre-devel rpm-build

- fetch postfix source RPM from a CentOS mirror and install it

# wget ftp://ftp.iasi.roedu.net/pub/mirrors/centos.org/5.3/os/SRPMS/postfix-2.3.3-2.1.el5_2.src.rpm
# rpm --install -vh postfix-2.3.3-2.1.el5_2.src.rpm

- fetch the VDA (Virtual Delivery Agent) patch for the corresponding postfix version, from http://vda.sourceforge.net/ and move it to /usr/src/redhat/SOURCES, unpack it

# wget http://vda.sourceforge.net/VDA/postfix-2.3.3-vda.patch.gz
# cp postfix-2.3.3-vda.patch.gz /usr/src/redhat/SOURCES
# gzip -d postfix-2.3.3-vda.patch.gz

- copy this text and paste into a file, name it postfix.spec.diff

--- postfix_el5.spec 2008-08-11 14:27:21.000000000 +0300
+++ postfix.spec 2009-10-15 20:41:38.000000000 +0300
@@ -1,7 +1,8 @@
-%define LDAP 2
-%define MYSQL 0
+#%define LDAP 2
+%define MYSQL 1
%define PCRE 1
-%define SASL 2
+#%define SASL 2
+%define DOVECOT_SASL 1
%define TLS 1
%define IPV6 1
%define POSTDROP_GID 90
@@ -12,11 +13,16 @@
# requested but use the preferred SASL V2 if LDAP is not requested.
# Sometime soon LDAP will build agains SASL V2 and this won't be needed.

-%if %{LDAP} <= 1 && %{SASL} >= 2
+%if %{LDAP} && %{SASL} && %{LDAP} <= 1 && %{SASL} >= 2
%undefine SASL
%define SASL 1
%endif

+
+%if %{DOVECOT_SASL}
+%undefine SASL
+%endif
+
%if %{PFLOGSUMM}
%define pflogsumm_ver 1.1.0
%endif
@@ -84,6 +90,8 @@

# Optional patches - set the appropriate environment variables to include
# them when building the package/spec file
+Patch11: postfix-2.3.3-vda.patch
+

BuildRoot: %{_tmppath}/%{name}-buildroot

@@ -98,11 +106,16 @@
Requires: openldap >= 2.0.27
%endif

-%if %{SASL}
-BuildRequires: cyrus-sasl >= 2.1.10, cyrus-sasl-devel >= 2.1.10
-Requires: cyrus-sasl >= 2.1.10
+%if %{DOVECOT_SASL}
+#BuildRequires: dovecot >= 1.0.0, cyrus-sasl-devel >= 2.1.10
+Requires: dovecot >= 1.0.7-7
%endif

+#%if %{SASL}
+#BuildRequires: cyrus-sasl >= 2.1.10, cyrus-sasl-devel >= 2.1.10
+#Requires: cyrus-sasl >= 2.1.10
+#%endif
+
%if %{PCRE}
Requires: pcre
BuildRequires: pcre, pcre-devel
@@ -136,6 +149,7 @@
%patch8 -p1 -b .large-fs
%patch9 -p1 -b .cyrus
%patch10 -p1 -b .CVE-2008-2936
+%patch11 -p1 -b .vda

%if %{PFLOGSUMM}
gzip -dc %{SOURCE53} | tar xf -
@@ -182,19 +196,24 @@
CCARGS="${CCARGS} -DHAS_MYSQL -I/usr/include/mysql"
AUXLIBS="${AUXLIBS} -L%{_libdir}/mysql -lmysqlclient -lm"
%endif
-%if %{SASL}
- %define sasl_v1_lib_dir %{_libdir}/sasl
- %define sasl_v2_lib_dir %{_libdir}/sasl2
- CCARGS="${CCARGS} -DUSE_SASL_AUTH -DUSE_CYRUS_SASL"
- %if %{SASL} <= 1 - %define sasl_lib_dir %{sasl_v1_lib_dir} - AUXLIBS="${AUXLIBS} -L%{sasl_lib_dir} -lsasl" - %else - %define sasl_lib_dir %{sasl_v2_lib_dir} - CCARGS="${CCARGS} -I/usr/include/sasl" - AUXLIBS="${AUXLIBS} -L%{sasl_lib_dir} -lsasl2" - %endif +#%if %{SASL} +# %define sasl_v1_lib_dir %{_libdir}/sasl +# %define sasl_v2_lib_dir %{_libdir}/sasl2 +# CCARGS="${CCARGS} -DUSE_SASL_AUTH -DUSE_CYRUS_SASL" +# %if %{SASL} <= 1 +# %define sasl_lib_dir %{sasl_v1_lib_dir} +# AUXLIBS="${AUXLIBS} -L%{sasl_lib_dir} -lsasl" +# %else +# %define sasl_lib_dir %{sasl_v2_lib_dir} +# CCARGS="${CCARGS} -I/usr/include/sasl" +# AUXLIBS="${AUXLIBS} -L%{sasl_lib_dir} -lsasl2" +# %endif +#%endif + +%if %{DOVECOT_SASL} + CCARGS="${CCARGS} -DUSE_SASL_AUTH -DDEF_SERVER_SASL_TYPE=\\\"dovecot\\\"" %endif + %if %{TLS} if pkg-config openssl ; then CCARGS="${CCARGS} -DUSE_TLS `pkg-config --cflags openssl`" @@ -274,17 +293,17 @@ perl -i -pe 's:/cyrus/bin/deliver:/usr/lib/cyrus-imapd/deliver:' $RPM_BUILD_ROOT%{postfix_config_dir}/master.cf cat $RPM_BUILD_ROOT%{postfix_config_dir}/postfix-files -%if %{SASL} -# Install the smtpd.conf file for SASL support. -# See README-Postfix-SASL-RedHat.txt for why we need to set saslauthd_version -# in the v1 version of smtpd.conf -mkdir -p $RPM_BUILD_ROOT%{sasl_v1_lib_dir} -install -m 644 %{SOURCE100} $RPM_BUILD_ROOT%{sasl_v1_lib_dir}/smtpd.conf -echo "saslauthd_version: 2" >> $RPM_BUILD_ROOT%{sasl_v1_lib_dir}/smtpd.conf
-
-mkdir -p $RPM_BUILD_ROOT%{sasl_v2_lib_dir}
-install -m 644 %{SOURCE100} $RPM_BUILD_ROOT%{sasl_v2_lib_dir}/smtpd.conf
-%endif
+#%if %{SASL}
+## Install the smtpd.conf file for SASL support.
+## See README-Postfix-SASL-RedHat.txt for why we need to set saslauthd_version
+## in the v1 version of smtpd.conf
+#mkdir -p $RPM_BUILD_ROOT%{sasl_v1_lib_dir}
+#install -m 644 %{SOURCE100} $RPM_BUILD_ROOT%{sasl_v1_lib_dir}/smtpd.conf
+#echo "saslauthd_version: 2" >> $RPM_BUILD_ROOT%{sasl_v1_lib_dir}/smtpd.conf
+#
+#mkdir -p $RPM_BUILD_ROOT%{sasl_v2_lib_dir}
+#install -m 644 %{SOURCE100} $RPM_BUILD_ROOT%{sasl_v2_lib_dir}/smtpd.conf
+#%endif

mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/pam.d
install -m 644 %{SOURCE101} $RPM_BUILD_ROOT%{_sysconfdir}/pam.d/smtp.postfix
@@ -382,10 +401,10 @@

# Config files not part of upstream

-%if %{SASL}
-%config(noreplace) %{sasl_v1_lib_dir}/smtpd.conf
-%config(noreplace) %{sasl_v2_lib_dir}/smtpd.conf
-%endif
+#%if %{SASL}
+#%config(noreplace) %{sasl_v1_lib_dir}/smtpd.conf
+#%config(noreplace) %{sasl_v2_lib_dir}/smtpd.conf
+#%endif
%config(noreplace) %{_sysconfdir}/pam.d/smtp.postfix
%attr(0755, root, root) %config /etc/rc.d/init.d/postfix

- Apply this patch to the original .spec file to enable MySQL, Dovecot SASL, TLS and Virtual Delivery Agent support to this build:

# cd /usr/src/redhat/SPECS
# patch -p0 < /path/to/the_recently_created/postfix.spec.diff

- Build the package

# rpmbuild -bb /usr/src/redhat/SPECS/postfix.spec
# rpmbuild -bs /usr/src/redhat/SPECS/postfix.spec

- Install your new postfix package, now able to handle virtual users, postfixadmin, TLS and SASL authentication, with dovecot integration

# cd /usr/src/redhat/RPMS/{architecture}/
# rpm --install -vh postfix-2.3.3-2.1.i386.rpm

- Enable automatic startup of postfix, using the system-switch-mail tool, or using chkconfig

- Save a copy of the updated source RPM, you may need the patched .spec file later...

# cp /usr/src/redhat/SRPMS/postfix-2.3.3-2.1.src.rpm /to/your/backup/area/

- Install postfixadmin, set it up, and start administering your mailboxes
- Configure postfix to use the MySQL lookup tables
- Take care when updating system to avoid updating it with a non-compliant build, or add postfix to the protected/excluded packages form yum updates

Securizare rețea wireless, router Linksys WRT54G

Uzual, configurarea unui router wireless presupune următorii pași:

• configurarea modului de acces la internet
• configurarea parametrilor pentru rețeaua wireless
• configurarea securității rețelei wireless

Am să descriu procedura de configurare pentru situația în care folosiți router din seria Linksys WRT54G, dar procedura de configurare pentru alte modele, chiar și ale altor producători, este similară.
În unele cazuri este necesară configurarea "Port forwarding", pentru o mai bună funcționare a unor aplicații în mod server, cum ar fi uTorrent, DC++, oDC, Remote desktop, server web, radio online, etc.


Accesarea interfeței de administrare

Routerul Linksys WRT54GL are adresa pre-setată din fabrică 192.168.1.1, având serverul DHCP integrat activ. Cu alte cuvinte, dacă porniți routerul, apoi conectați și calculatorul la rețea, calculatorului i se va atribui o

Apache .htaccess: how to get rid of 'RewriteEngine not allowed here'

Apache error: RewriteEngine not allowed here

A friend of mine has changed his web hosting server, and since that moment one of it's web pages stopped showing. The page displayed instead was a generic page from the Apache web server, telling that there was an internal error and to check the logs.
Here's a line from the log:

[Tue Aug 25 17:07:39 2009] [alert] [client xx.xx.xx.xx] /usr/local/www/htdocs/.htaccess: RewriteEngine not allowed here

I tried to find the answer on the net, and after a short google search and after reading a little bit of apache docs, I found the answer.


How this appeared?

My friend's web site includes a file called .htaccess, which usually is populated with directives for the apache web server. In a default apache setup, this file is read on web page access, but only if the main configuration directives (from httpd.conf or vhost configuration file) allow this. This is specified by the 'AllowOverride AuthConfig' directive. Since I've seen the error, AllowOverride AuthConfig was 'On', so the .htaccess file was processed, but some of it's content is not permitted in this context.


How to allow RewriteEngine on directive in .htaccess

All I needed to do is to modify the apache configuration file referring to htdocs directory. In my case it was the virtual host definition file, but it may be the main apache config file, httpd.conf. I've changed the <directory> section from

<Directory /path/to/htdocs/>
Options +FollowSymLinks
AllowOverride AuthConfig
Order allow,deny
Allow from all
<Directory>

to

<Directory /path/to/htdocs/>
Options +FollowSymLinks
AllowOverride AuthConfig FileInfo
Order allow,deny
Allow from all
<Directory>

And it fixed the problem.

Program gratuit pentru defragmentare disc - Auslogics disk defrag

Despre defragmentarea fișierelor

Una dintre activitățile adesea omise, dar care pot oferi un câștig considerabil de performanță este defragmentarea hard disk-ului. Defragmentarea fișierelor este necesară deoarece, pe masură ce hard disk-ul se încarcă cu date, acestea nu mai pot fi dispuse pe zone continue de pe disc, ci sunt împraștiate în diverse arii. Ținând cont că timpul de acces este factorul care penalizează cel mai mult performanța unui hard disk, rezultă că defragmentarea fișierelor de pe hard disk poate oferi un spor de performanță apreciabil.



Programe pentru defragmentare


Foarte multe persoane adoră programele gratuite. Una e să dai 30 de dolari pe un program, alta e să obții gratuit un program cu funcționalitate comparabilă. Utilitarele de defragmentare incluse in Windows XP si Vista au probleme lor: Disk defragmenter inclus în Windows XP necesita privilegii de administrator pentru execuție (lucru care poate deranja pe unii administratori de rețea), și foarte rar execută complet defragmentarea. Versiunea inclusă în Vista aduce și o îmbunătățire, execuția defragmentării poate fi automatizată, fără a mai necesita intervenția utilizatorului, dar aduce și un inconvenient: rata de transfer a datelor este limitată, pentru a nu incomoda vizibil execuția altor programe care fac scrieri/citiri pe disc. Mai multe firme oferă programe complementare pentru defragmentare. Unul dintre ele este gratuit,


Auslogics Disk Defrag

Am dat peste numele "Auslogics" întâmplător, pe net. Programul este disponibil atât în varianta standard, care se instalează pe hard disk, dar și în variantă portabilă, care se poate copia și executa de pe un CD/DVD/stick. Interfața cu utilizatorul este cât se poate de simplă. Sunt vizibile partițiile din sistem, casetele unde se poate selecta ce partiții vor fi defragmentate, o grilă unde urmează a se afișa gradul de fragmentare și aria unde se lucrează. Este prezentă și o casetă care indică programului să inițieze închiderea sistemlui după finalizarea defragmentării.


După click pe butonul 'Defrag', se efectuează analiza stării actuale de fragmentare

După care începe defragmentarea propriu-zisă


apoi începe operația propriu-zisă de defragmentare. Este prezentă legenda care arată semnificatia culorilor din grilă.
După terminarea operației, sunt prezentate rezultatele defragmentării intr-o fereastră.


Setările programului permit specificarea nivelului de prioritate, lucru care compensează rata scăzută de transfer a programului inclus cu Vista.


Un aspect foarte important este că programul suportă execuția programată cu "Task scheduler" și/sau pornire din linie de comandă, lucru care poate rezolva problema defragmentării acolo unde utilizatorii nu au privilegiu de administrator. Un alt aspect, destul de important: nicăieri nu am găsit vreo restricție privind utilizarea programului în medii comerciale, ceea ce îl face foarte atractiv și pentru mediul "business".


Mai multe informații puteți găsi pe situl Auslogics. Tot de acolo puteți să descărcați ultima versiune.

SAS RAID controllers for VMWare ESXi

Entry level SAS/SATA RAID controllers for a small server or a fast workstation
This list contains the entry-level/value SAS/SATA RAID controllers with internal ports, as listed by VMWare I/O compatibility tool on 2009-08-13. If you use or intend to use a controller with external ports, or a controller from other vendors (HP, DELL, fujitsu, IBM etc) do a check on VMWare web site, I haven't listed here all the SAS/SATA RAID controllers. I need to have this nicely formatted, so I can find easy where to choose from if i need a SAS/SATA controller for a small server, or a workstation, since most controllers are compatible with Windows too. For Windows the list could be much longer, since not all SAS RAID controllers are tested by VMWare, I only put here the ones that may be useful for a VMWare ESXi server running on a DIY platform. There may be many other SAS/RAID controllers usable with VMWare, but these listed below are definitely usable for VMFS volumes.
Adaptec Entry level / value SAS/SATA RAID Controllers compatible with VMWare ESX

• Adaptec RAID 2405: Entry level SAS/RAID controller, 4 internal ports, low profile form factor, 800 MHz processor, PCI Express x8. Supports RAID levels 0, 1, 10, 128 MB DDR2 cache memory, up to 128 SAS or SATA drives using SAS expanders. Supports ESX / ESXi 4.0. Price: ~ $270 (US)
• Adaptec RAID 3405: Value line SAS/RAID controller, 4 internal ports, Low profile form factor, Intel 80333 500 MHz processor, PCI Express x4 bus interface. Supports RAID levels 0, 1, 1E, 5, 5EE, 6, 10, 50, 60, JBOD, using 128 MB cache memory. Supports up to 128 SATA or SAS drives using SAS expanders, optional battery backup. Supports ESX/ESXi 4. Price: ~ $400 (US)
• Adaptec RAID 3805: Value line SAS/RAID controller, 8 internal ports, Low profile form factor, Intel 80333 500 MHz processor, PCI Express x4 bus interface. Supports RAID levels 0, 1, 1E, 5, 5EE, 6, 10, 50, 60, JBOD, using 128 or 256 MB cache memory. Supports up to 128 SATA or SAS drives using SAS expanders, optional battery backup. Supports ESX/ESXi 4. Price: ~ $575 (US)
• Adaptec RAID 31205: Value line SAS/RAID controller, 12 internal ports, half-length/full-height form factor, Intel 80333 800 MHz processor, PCI Express x8 bus interface. Supports RAID levels 0, 1, 1E, 5, 5EE, 6, 10, 50, 60, JBOD, 256MB ECC cache, up to 128 SATA or SAS devices using SAS expanders, optional battery backup. Price: ~ $795 (US)
• Adaptec RAID 31605: Value line SAS/RAID controller, 16 internal ports, half-length/full-height form factor, Intel 80333 800 MHz processor, PCI Express x8 bus interface. Supports RAID levels 0, 1, 1E, 5, 5EE, 6, 10, 50, 60, JBOD, 256MB ECC cache, up to 128 SATA or SAS devices using SAS expanders, optional battery backup. Price: ~ $995 (US)

Intel Entry level / value SAS/SATA RAID Controllers compatible with VMWare ESX

• Intel® RAID Controller SRCSAS144E: Mid-range (Mainstream) PCI-E SAS controller, PCI Express x4 bus interface, 4 internal ports, 4 external ports, Low profile PCI: 7.71" x 2.535" form factor, Intel IOP 80333 processor at 500 MHz, LSI 1068 3.0 GB/s SAS/SATA IO controller, supports up to 32 devices via expanders, 128 MB embedded memory, audible alarm. Price: $549 at NewEgg, without cables.
• Intel® RAID Controller SRCSASRB: Mid-range (Mainstream) PCI-E SAS controller, Low profile, extended half-length (7.75" x 2.525") form factor, PCI Express x4 bus intreface, 256 MB ECC DDR2 cache memory, LSI1078 SAS ROC (RAID on Chip) at 500 MHz and dual-independent DMA controllers. Supports RAID Levels 0, 1, 5 and 6, 10, 60, 60, online capacity expansion, enclosure management, SMART. Supports up to 32 devices, through two SFF8087 mini-SAS 4i internal connectors. It uses Intel® Smart Battery AXXRSBBU4. Price: ~ $375.
• Intel® RAID Controller SASWT4I is a PCI-E SAS Controller, with 4 internal ports. It is built around LSI1064E chip, a well-known chip used by many server boards. It is able to use RAID levels 0,1,1E,10E. According to Intel's documentation, this controller is verified to work with ESX3 and ESXi3.

LSI Entry level / value SAS/SATA RAID Controllers compatible with VMWare ESX

• LSI MegaRAID SAS 8344 ELP SAS RAID Adapter: Mid-range (Mainstream) PCI-E SAS controller, PCI Express x4 bus interface, low profile form factor, 4 internal ports, 4 external ports, supports up to 32 devices via expanders, RAID levels 0, 1, 5, 10, 50, max. 32 drives (4 per port using expanders), 128 MB embedded cache memory, audible alarm. Price: unknown. This controller looks identically to Intel RAID Controller SRCSAS144E.
• LSI MegaRAID SAS 8708ELP: Value line eight-port PCI Express SAS Controller, low profile form factor, PCI Express x4, LSI SAS 1078 RAID on Chip (ROC) (500 MHz power-pc processor, hardware RAID 5 & 6 parity engines), 129 MB DDRII cache, optional battery backup unit, RAID levels 0, 1, 5, 6, 10, 50, 60, auto-resume (rebuild, reconstruction), online capacity expansion, online RAID level migration, single controller multipath, I/O load balancing, two Mini-SAS SFF-8078 x4 connectors.

HP SAS/SATA RAID controllers compatible with VMWare ESX

• HP SmartArray E200. This is a 8-port SAS/SATA RAID controller with PCI Express x4 bus interface. Form factor: SmartArray E200/64MB: full height PCI Express long card. RAID levels supported: 0,1,0+1. RAID 5 is available with 128MB Battery-Backed Write Cache (BBWC) upgrade option. It seems that HP prefers to put reliability first with this controller, because the controller disables a SATA hard disk drive's write cache, making it unable to write faster than 11 MB/sec at default settings. Fortunately, drive's write cache can be re-enabled by HP Array management tools. Yes... these tools may require a running operating system with HP smart Array tools installed (ESXi may not be suited for this task), but there is a solution. A second note regarding this card: it is a VERY long card (more than 30 cm), and it may require hard disk drive relocation or a new case, if not used in a system with E-ATX motherboard/case. I can confirm that it fits into Antec Sonata III 500, if used with a dual PCI-Express x16 motherboard, like Gigabyte EP45-UD3P, mounted on the second PCI-Express x16 slot.

IBM SAS/RAID controllers compatible with VMWare ESX

• IBM ServeRAID-BR10il SAS/SATA Controller v2 is a small form factor (MD2) controller built around LSI 1064E, PCI Express x4 bus interface and 2MB flash memory. RAID levels supported: 0,1, 1E. Stripe size is fixed, 64KB. The drives can be attached through an SFF 8087 mini-SAS connector, only internal drives, up to 14 disks.This controller does not support more than 2 logical volumes or SAS / SATA drive mixing.

You can check my Amazon Associates Store for availability and pricing.

There are some losses when using ESXi and some RAID controllers: it's possible to loose the advantages of using RAID configuration and monitoring tools like 'Adaptec Storage Manager', so you must check your arrays by other means.

Instanțe apache 2 multiple pe FreeBSD

Mi s-a întâmplat de câteva ori să am nevoie să rulez mai multe instanțe de server apache pe un server. Deși metoda folosirii virtualhost este adesea suficientă, unicitatea anumitor directive din fișierul de configurare httpd.conf face necesară rularea de instanțe multiple.
Una dintre metodele de a rula mai multe servere apache concomitent este folosirea conceptului FreeBSD 'jail', care conferă o multitudine de avantaje, cum ar fi posibilitatea de a instala doar extensiile php strict necesare respectivei instanțe și izolarea mai bună față de server, dar punerea pe picioare a unui jail poate dura destul de mult.

O variantă alternativă este folosirea de profile de instanță apache distincte, care partajează același set de librării și extensii php, însă folosind fișiere de configurare diferite, lucru facilitat chiar de scriptul de pornire a serverului instalat de pachetul apache22. Pentru fiecare profil configurat, urmează a se pune în execuție câte un proces apache, cu setări specifice.
Astfel, în fișierul global de configurare a sistemului, /etc/rc.conf, directivele referitoare la apache22 se extind față de directivele uzuale:

# directive apache22 clasice, comune
apache22_enable="YES"
apache22_http_accept_load="YES"
apache22_http_accept_enable="YES"

# Directive apache22 care permit folosirea de profile
apache22_profiles="default p1"
apache22_default_enable="YES"
apache22_default_http_accept_enable="YES"
apache22_default_configfile="/usr/local/etc/apache22/httpd.conf"
apache22_p1_enable="YES"
apache22_p1_http_accept_enable="YES"
apache22_p1_configfile="/usr/local/etc/apache22/httpd-p1.conf"

Acum voi detalia semnificația directivelor suplimentare

apache22_profiles="p1 p2 p3"

indică scriptului /usr/local/etc/rc.d/apache22 să folosească instanțe multiple, instanțe identificate prin lista separată cu spații. Pentru fiecare profil, fișierul /etc/rc.conf va trebui să includă câte un set de directive de forma "apache22_profil_directiva=valoare".

Directivele specifice fiecărui profil sunt:

apache22_profil_configfile="/cale/catre/fisier/configurare/httpd.profil.conf"
apache22_profil_enable="YES|NO"
apache22_profil_flags="alte_directive_pentru_httpd_specifice_pentru_acest_profil"
apache22_profil_http_accept_enable="YES|NO"
apache22_profil_limits_enable="YES|NO"
apache22_profil_limits_args="limits_args"
apache22_profil_fib="FIB"

Este strict necesară indicarea fișierului de configurare al respectivului profil, toate celelalte directive fiind opționale. O directivă interesantă este "FIB", care nu poate avea efect decât pe FreeBSD mai recent de 7.1, care se referă la 'Forward Information Base' (FIB) asociat cu respectiva instanță apache. Începând de la versiunea 7.1, FreeBSD poate folosi multiple FIB-uri, lucru care permite folosirea de tabele de rutare diferite pentru procese diferite.

În continuare, se crează fișierul de configurare httpd-profil.conf specific respectivului profil, probabil pornind de la o versiune salvată sau de la fișierul de configurare inclus în distribuția Apache22. Va trebui să ajustați câteva setări importante: adresa IP si portul folosit de profil, amplasarea DocumentRoot, si în mod special amplasarea log-urilor, pentru a nu fi scrise în același loc cu logurile altor profile. Atenție mare și la adresa IP/port, dacă sunt mai multe servicii configurate să foloseasca acelasi IP și același port, uul dintre ele nu va putea porni.

Pentru pornirea tuturor instanțelor apache nu mai rămâne de făcut decât:

/usr/local/etc/rc.d/apache22 start

X-Fi Titanium Fatal1ty Professional - Gaming performance

I've been digging the net for some X-Fi gaming performance benchmarks for a while, but I wasn't able to find anything more than Creative's own benchmark done with UT 2004. So... I began my own research.

What is an X-Fi card

Creative is using the X-Fi brand for their most recent product lineup targeted to the non-professional users. Since X-Fi launch, there were two processors capable of hardware acceleration: CA20K1 (a.k.a. EMU20K1), followed few years later by CA20K2 (a.k.a. EMU20K2). CA20K1 processor seems to be 24 times faster than the previous generation's processor (Audigy). A major difference between Audigy and X-Fi is the effects processor sampling rate and number of bits for audio resolution. Audigy was able to apply sound effects only at 48kHz/16 bit, so if the source signal wasn't 48kHz/16 bit, it needed to be resampled, and the resampling operation generates intremodulation distortion. CA20K1 is used in the first generation of X-Fi sound cards, connected through PCI slots, while CA20K2 is used on PCI Express based variants, Titanium family. Being a revised chipset, CA20K2 also fixes the 'Sound crackling and popping' issues.

But... these processors are not included in all X-Fi products. For example, the cheapest sound card from Creative branded X-Fi is 'X-Fi Extreme Audio', a card which looks like the previous generation cheap card, Audigy SE. It has a PCI Express counterpart, but this cannot accelerate in any way audio processing. This does not mean that X-Fi Extreme Audio is using an older processor for hardware acceleration, it means that Audigy SE does not use hardware acceleration at all. Since I wanted a card with hardware accelerated DSP/processing I've decided that a card from the X-Fi Titanium family should be enough for me, and I wanted to have available the 'Crystalyzer'.

After few days using it on a Logitech Z2300 speaker system, I wasn't sure if the sound quality was superior or below onboard ALC889 when listening music and/or watching movies, and googling over the net showed me that it's the DAC the most important chip, that Auzentec X-Fi prelude is better than X-Fi Titanium, that Asus Xonar D2X has superior DAC, that EAX is dying, and many things which made me ask myself if the X-Fi Titanium Fatal1ty is worth the money. In fact, EAX is not dying, but Creative is implementing EAX on vista through OpenAL extensions.

So i decided to measure gaming performance improvement on Unreal Tournament 3, a game which is using OpenAL, comparing X-Fi Titanium Fatal1ty gaming performance with onboard audio provided by an ALC889 chip. Since I didn't have another sound card for comparision, the results are limited, but I found some convincing results. If anyone do think that there are cards not using X-Fi CA20K2 with better performance, I accept him/her sending me such a card for performance comparision.

My test configuration:

CPU:
- Intel Core2 Duo E8400 @ 3.0 GHz, FSB 1333 (333 QDR)
- Intel Core2 Duo E8400 @ 3.6 GHz, FSB 1600 (400 QDR)
Motherboard: Gigabyte EP45-UD3P
Mem: 4 GB DDR2/800
Graphics card: ATI Radeon HD 3870 from Gigabyte, Catalyst 9.6
Sound cards:
- onboard ALC889
- Creative X-Fi Titanium, using drivers from june 2009


My tests were made with the UT3 Benchmark tool from Guru3D, with DirectX10, max quality, sound on, max display resolution (1440 x 900). I did 5 runs of DM-ShangriLa map, without bots, with each card. After the first set of results, I've overclocked the CPU to 3.6 GHz, and I did a second set of benchmark runs. The average FPS are shown below.


X-Fi Titanium vs. Onboard Realtek 889 benckmark results

So far, I can tell that there is a 15% FPS gain only by using X-Fi Titanium instead ALC-889, and another important thing is that there is a higher performance gained overclocking the CPU when using X-Fi, since the CPU soes not need to handle all the workload needed for rendering audio.

I tought that, these days, the CPU power needed by audio on games is negligible, but I was wrong. Games using UT3 engine and/or OpenAL need a lot of CPU cycles to render audio, and using a hardware accelrated platform does squeeze maximum performance from other subsystems such as CPU and graphics card. In my test configuration, all the time when I ran the benchmarks, the CPU usage was 100%, making a CPU the limiting factor on this case. So, overclocking the CPU or using some hardware acceleration would help increasing gaming performance.

Doing some math, results that I need to overclock a Core2Duo by 0.6 x 4 = 2,4 GHz to release from the CPU the workload needed by audio processing in the same way X-Fi does in hardware with it's CA20K2, only to gain the same 15% FPS improvement. Also, I achived a higher framerate increase by overclocking when I used X-Fi, by 7.42%, which twice the gain achieved by overclocking the CPU and using onboard ALC889. Combining using an X-Fi Titanium instead onboard audio with some light overclock yelds a total framerate increase by 23,99%, which I consider 'high performance improvement' and 'worthy'.

Conclusion
That degree of performance increase may not be noticed by someone using a high clocked quad core CPU, but it does a big difference when the CPU has some limits, and such improvements cannot be achieved by overclocking. I can say that X-Fi titanium Fatal1ty does worth the money, and probably any CA20K2 X-Fi based sound card does, especially for gamers wanting to squeeze the maximum FPS from their platform, including those using the latest CPUs. But keep in mind another important thing: Unreal Tournament 3 engine is using OpenAL for audio rendering, and games using software for rendering cannot benefit from the acceleration provided by X-Fi, using only the CPU for this task.

Securizare retea wireless, router DLink DI 524

Deoarece devin tot mai frecvente întrebările de forma: "Cum se securizează o rețea wireless?", "Cum îmi configurez routerul wireless?" și "Cum fac port forwarding pe routerul DLink DI 524?" am compilat acest mic ghid.

Din fabrică sau după resetare, routerul permite asocierea oricărui client fără a folosi nici o metodă de restricționare a clienților wireless. Acest lucru nu e tocmai sănătos, pentru că permite conectarea oricui se află în apropiere, și dorește să folosească această rețea wireless. Pentru a rezolva această gaură de securitate, trebuie configurat routerul.

Setările wireless
Parametrii wireless care trebuiesc ajustați se referă la criptarea transmisiei intre router și clientul wireless, iar în cazul în care este un număr mare de routere wireless în zonă, mai trebuie ajustată și frecvența de operare radio.
Securizarea routerului se face prin activarea criptării, folosind WPA. Trebuie să deschizi o fereastră de navigator web, și să introduci adresa IP a routerului în câmpul adresă al navigatorului. Va apărea o fereastră de autentificare asemănătoare cu cea de mai jos:


Introduceți numele de utilizator și parola pe care le-ați configurat, sau admin/admin în cazul în care routerul este nou sau a fost resetat. Atenție, este posibil ca autentificarea sa nu meargă de la prima încercare, mi s-a întâmplat frecvent sa mi se solicite de două ori combinația utilizator/parola. După autentificare apare ecranul principal al setărilor și statusului routerului:


Pentru a face modificările referitoare la securizarea wireless, dați click în partea stângă pe link-ul 'Wireless'. Va apărea fereastra următoare:


Aici faceți următoarele setări: numele rețelei, canalul de frecvență folosit, tipul de securizare. Sugerez folosirea WPA2-PSK sau WPA-PSK + WPA2-PSK (mixt WPA + WPA2). Pentru WPA/WPA2 trebuiesc setați doar 2 parametri: modul de codificare și cheia. După ce ati introdus acești parametri, salvează noile setări apasând butonul "Apply". Va trebui să introduci aceeași parola si pe calculatorul care urmează a se conecta wireless la acest router.


Alegerea algoritmului de criptare
O diferență majoră intre WPA-PSK și WPA2-PSK constă în tipul de algoritm folosit implicit la codificarea semnalului transmis. WPA folosește TKIP, iar WPA2 folosește AES. TKIP este implementat pe majoritatea routerelor și adaptoarelor wireless, fiind preferat ca mod de codificare implicit pe sistemele mai vechi. AES este implementat pe routere și adaptoare wireless mai recente, oferind o protecție mărită. În cazul în care se întâmplă să nu vă funcționeze asocierea unei stații mai vechi, încercați să vedeți dacă respectiva stație poate folosi AES și dacă are selectat acest algoritm, sau configurați routerul să folosească WPA + WPA2.


Port forwarding (DC++, torrent, etc)
Adesea este nevoie ca alte stații din internet să se poată conecta la un port deschis de o aplicație de pe calculatorul dvs. Exemple de aplicații: dc++ mod activ, clienți de torrent, jocuri, remote desktop, server web, remote admin sau alte aplicații de tip server.


Se completează casetele referitoare la: adresa ip a calculatorului pe care rulează aplicația server, adresa numărul de port pentru conexiunea externă, numărul de port folosit de aplicație, protocolul (tcp/udp), după care click pe 'apply'.

DLink are disponibilă o pagină cu un emulator unde puteți exersa setarea routerului. Această pagină este disponibilă pe situl www.dlink.com.

What is X-Fi MB

What is X-Fi MB
Is a software driver, which adds to your sound processing chain (only on selected chips) some capabilities. Here is the web page detailing Creative X-Fi MB. This is the second generation of software-only EAX implementation from Creative available to other manufacturers, following the first generation called Audigy MB. It seems that X-Fi MB is available only for some models from specific vendors (Dell, Gigabyte, Asus, etc). When it is installed, the driver will disable the current Dolby software, and installs the following applications: Alchemy (to provide EAX to OpenAL library call translation for older games on Vista), MediaSource (some media player/organizer), Audio Console (an application which provides access to Creative audio features), Console launcher (same thing as Audio console, but with a user-friendly interface), WaveStudio and VolumePanel (a system tray control application). After installation on Vista, these Creative features are available:
- EAX environment Effects (echo/reverb for standard applications)
- CMSS 3D (surround sound on headphones, 2 channel to n speakers, etc)
- Crystalizer (improves mp3/movie sound quality)
- OpenAL, supporting EAX up to level 4
- Another dolby encoder, replacing the one bundled by Gigabyte
On Vista, all hardware-accelerated operations are no longer handled by EAX and creative drivers directly, but through OpenAL library, which offers EAX4 compatibility.
The user has nothing to tune at the application level after installation, the software simply installs itself as a driver, all the sound post-processing is done at the driver level (no need to tune each application, and an equalizer is not the same as a DSP)

Why did I installed it
Because before my current motherboard, a Gigabyte EP45-UD3P, i've used a Intel Motherboard DG965OT built with Sigmatel sound chip, bundled with 'Intel Audio Studio' which includes some ddigital sound processing software from Sonic Focus. That piece of software totally changes the way the sound gets to the speakers. Since i've used to this kind of audition, it was difficult to me to 'adapt' to the flat sound coming from ALC889A, especially MP3 audio, and I started searching for methods to improve the sound quality. If you listen music/radio to a low-end speaker set, probably you won't notice any improvement, but Logitech Z2300 or z5500, Genius 6000 or better will do a difference.

It's good to know some other things...
1. Creative entry-level boards are not built with hardware processors like EMU20Kx and not even the older EMU10Kx, and probably nobody will notice any difference from the sound coming from ALC889A + X-Fi MB compared to X-Fi Xtreme Audio / Audigy SE. Even more, X-Fi Xtreme Audio which is very little different from Audigy SE and all the DSP / EAX is done in software on these boards too. So, X-FI MB or Audigy SE or X-Fi Xtreme Audio will offer comparable CPU usage and sound post-processing. I think i'm absolutely right when I say 'X-Fi Extreme Audio and Audigy SE are hardware licenses to use EAX drivers and applications'.

2. There are other implementations for sound post-processing, which offers remarcable sound improvement, I refer to Sonic Focus, which is bundled with the Intel motherboards, at least 9xx series. I've used this software DSP on Intel DP965LT and DG965OT, and the difference is like from moving from classic TV (PAL/NTSC) to HDTV, but translated into music improvement, and it seems to me comparable to Creative's 'Crystalizer'. Anyway, Crystalizer, the way it's implemented on X-Fi MB downloaded from Gigabyte (version 9.1.0.429) is inferior to Sonic Focus / Intel Audio Studio, Creative only offers a slider where you can select the 'Crystalizing' level, while Intel offers 3 or more, thus providing more flexibility.

3. By default, the 'Crystalizer' feature is enabled at level 50% on X-Fi MB, and I presume that it's the same on X-Fi Xtreme Audio. That's the main reason why Xtreme Audio owners are happy and they 'wont ever use onboard audio again!'.

The bad
- I don't like that Gigabyte is not bundling the licenses with their boards, or at least with performance/extreme series, it's a useful piece of software...
- On Gigabyte download page it is not listed Vista64, but the software for Vista32 is working absolutely fine on Vista64, and even including parts specifically for Vista64.

What other options are available
If you don't like to pay $29 to Creative for this software-only solution AND you want dynamics improvement AND EAX4 or higher, you can choose from
- A software (95%) + hardware (5%) solution for some extra $$$: X-Fi Xtreme Audio (these parts are fully licensed for EAX/Crystalizer,CMSS,etc) or Audigy SE, which is almost identical to X-Fi Xtreme Audio
- A software (5%) + hardware (95%) solution from Creative for much more $$$: X-Fi series with EMU20K1/2 chip, see X-Fi lineup.

If you don't care about EAX, you can use a Intel motherboard, but you may be missing some other useful features like overclocking or better CPU support (yes, better official CPU support!).
Don't blame me for not mentioning other boards, I did not use other boards and I don't want to talk about things I don't know about.