#find /etc -name “*ssh*.conf”
แล้วหาคำว่า PermitRoot  อะไรทำนองนี้อะ จำมะค่อยได้ save แล้วก็ restart ssh service หนึ่งครั้ง

ref: thaiadmin.org/board/index.php?topic=81368.0

du | sort -n ordina l'output numerico (dal file piu' piccolo a quello piu' grosso)

http://www.linfo.org/du.html

We’ve made some new additions to our website (www.LymphedemaDepot.com) adding loads of new functionality. Check our home page’s “What’s New?” section to see the changes. There is now a link to this, our blog page, for one thing.  There are quick and easy links to our Winter coupon and to our online videos.  There is also a link to our new Support Documents page, giving you the tools and information you need to get the information about the garments you need to your doctor and your insurance company.

The best thing, though, is the new link on the left-hand menu called “Documents Map.” It will take you directly to a page of every downloadable document on the website. This includes measuring forms, support documents, the catalogues of each product, and more. This new page makes the website work for you. You can browse through all the garments and garment documentation, videos and support documents easily and at your own pace.

Be sure to check our other link buttons for FaceBook, YouTube and LinkedIn. And, you can always send us an email (info@lymphedemadepot.com) or give us a call at 905-687-8500. Although, to tell the truth, it’s been a long time since we got  a postcard!

OK this is my first encounter with OpenSolaris Zones, so take all off the following with a grain of salt.

To make it (hopefully) easy to destroy the zone we create a ZFS Filesystem which will hold all of our zones:

$ pfexec zfs create rpool/zones
$ pfexec umount /rpool/zones/
$ pfexec zfs set mountpoint=/zones rpool/zones
$ pfexec zfs mount rpool/zones
$ pfexec chmod 0700 /zones/ # Necessary so that a later "verify" doesn't complain...

Great we have a file system to hold our zones, now let’s configure a new zone:

$ pfexec zonecfg -z testzone
zonecfg:testzone> create
zonecfg:testzone> commit
zonepath cannot be empty.
Zone testzone failed to verify
testzone: Required resource missing

Uh Oh, we failed miserably. So let’s set a path where the zone will be living:

zonecfg:testzone> set zonepath=/zones/testzone
zonecfg:testzone> commit
zonecfg:testzone> verify
zonecfg:testzone> end
The end command only makes sense in the resource scope.
zonecfg:testzone>

Looks all nice and fine, let’s verify again:

$ pfexec zoneadm -z testzone verify
WARNING: /zones/testzone does not exist, so it could not be verified.
When 'zoneadm install' is run, 'install' will try to create
/zones/testzone, and 'verify' will be tried again,
but the 'verify' may fail if:
the parent directory of /zones/testzone is group- or other-writable
or
/zones/testzone overlaps with any other installed zones.

Still some things to do.

$pfexec mkdir -p /zones/testzone
$ pfexec zoneadm -z testzone verify
/zones/testzone must not be group readable.
/zones/testzone must not be group executable.
/zones/testzone must not be world readable.
/zones/testzone must not be world executable.
could not verify zonepath /zones/testzone because of the above errors.
zoneadm: zone testzone failed to verify
$ pfexec chmod 0700 /zones/testzone

This looks a lot better now let’s install the zone. Note: We just configured the zone, we didn’t yet install it. So let’s start the installation:

$ pfexec zoneadm -z testzone  install
A ZFS file system has been created for this zone.
 Publisher: Using opensolaris.org (http://pkg.opensolaris.org/release/).
 Image: Preparing at /zones/testzone/root.
 Cache: Using /var/pkg/download.  
Sanity Check: Looking for 'entire' incorporation.
 Installing: Core System (output follows)
DOWNLOAD                                    PKGS       FILES     XFER (MB)
Completed                                  20/20   3021/3021   42.55/42.55 

PHASE                                        ACTIONS
Install Phase                              5747/5747
 Installing: Additional Packages (output follows)
DOWNLOAD                                    PKGS       FILES     XFER (MB)
Completed                                  37/37   5598/5598   32.52/32.52 

PHASE                                        ACTIONS
Install Phase                              7329/7329 

 Note: Man pages can be obtained by installing SUNWman
 Postinstall: Copying SMF seed repository ... done.
 Postinstall: Applying workarounds.
 Done: Installation completed in 2879.333 seconds.

 Next Steps: Boot the zone, then log into the zone console
 (zlogin -C) to complete the configuration process

Looks nice. Even some more instructions. So let’s boot the zone:

$ pfexec zoneadm -z testzone  boot

All nice and fine, let’s try to use the zone (You can escape from this by using “~.” – that’s a tilde and a dot – just hit “ENTER~.”):

$ pfexec zlogin -C testzone

[Connected to zone 'testzone' console]

You did not enter a selection.

What type of terminal are you using?

 1) ANSI Standard CRT
 2) DEC VT100
 3) PC Console
 4) Sun Command Tool
 5) Sun Workstation
 6) X Terminal Emulator (xterms)
 7) Other
Type the number of your choice and press Return: 6

Creating new rsa public/private host key pair
Creating new dsa public/private host key pair

Shock! There’s some curses (or whatever OpenSolaris uses) interface popping up! It will ask about hostname, time zone and root password. Enter the gritty details and try ESC-2 if it doesn’t continue with F2 (I chose “X Terminal Emulator (xterms)” – seems to be a bad choice).

Configuring network interface addresses:.
System identification is completed.

testzone.local console login: root
Password:
Nov 24 07:40:41 testzone.local login: ROOT LOGIN /dev/console
Sun Microsystems Inc.   SunOS 5.11      snv_111b        November 2008
root@testzone.local:~# uptime
 7:40am  up 5 min(s),  1 user,  load average: 0.17, 0.18, 0.18
root@testzone.local:~# ifconfig -a
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
 inet 127.0.0.1 netmask ff000000
lo0:1: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
 inet6 ::1/128
root@testzone.local:~# netstat -f tcp -an
tcp: unknown address family.
root@testzone.local:~# netstat -f inet -an

UDP: IPv4
 Local Address        Remote Address      State
-------------------- -------------------- ----------
 *.111                               Idle
 *.*                                 Unbound
 *.64049                             Idle
 *.111                               Idle
 *.*                                 Unbound
 *.38336                             Idle

TCP: IPv4
 Local Address        Remote Address    Swind Send-Q Rwind Recv-Q    State
-------------------- -------------------- ----- ------ ----- ------ -----------
 *.111                *.*                0      0 49152      0 LISTEN
 *.*                  *.*                0      0 49152      0 IDLE
 *.111                *.*                0      0 49152      0 LISTEN
 *.*                  *.*                0      0 49152      0 IDLE
 *.22                 *.*                0      0 49152      0 LISTEN
root@testzone.local:~# pkg search telnet
pkg: Some servers failed to respond appropriately:
 http://pkg.opensolaris.org/release/: node name or service name not known

Again to escape from the zlogin stuff hit: “ENTER~.” – that’s ENTER, tide, dot.

Very nice so far. We have uptime, a hostname and an IP Address, well kind of . Stay tuned for when I try to get network connectivity, which will hopefully be in the not too distant future.

A few minor notes on other tools that could be usefull:

Installing took quite a while on my system, since I could do some work in parallel I didn’t investigate. But I found the following command nice to see the status:

$ zoneadm -z testzone list -v
 ID NAME             STATUS     PATH                           BRAND    IP    
 - testzone         incomplete /zones/testzone                ipkg     shared

So let’s set up a nice terminal that watches the STATUS of our zone (the incomplete will go away as soon as the installation is finished). Of course we could watch the original terminal simply returning, but that would be kind of boring – wouldn’t it?

$ while true; do clear;zoneadm -z testzone list -v; zoneadm list -iv;sleep .8; done

Also the state of the zone after booting it:

$ zoneadm -z testzone list -v
 ID NAME             STATUS     PATH                           BRAND    IP    
 1 testzone         running    /zones/testzone                ipkg     shared

Shutting the zone down cleanly:

$ pfexec zlogin testzone shutdown # from the outside
# shutdown -y -i 0 # from inside the zone

Then looks like this:

$ zoneadm -z testzone list -v
 ID NAME             STATUS     PATH                           BRAND    IP    
 - testzone         installed  /zones/testzone                ipkg     shared

Happy working with your zone.

So I was looking how to install VirtualBox under OpenSolaris. My first thought was a simple

pkg install virtualbox

or similiar would be enough. It isn’t .

Looking around I found that the nice people from Sun provide an easy way to install VirtualBox. Note: I don’t really care about the newest and best features to be available but I like it when things are easy to manage – no really! Here’s how to get VirtualBox by simply using pkg with an official IPS repository.

1. Go to https://pkg.sun.com
2. Login with your Sun Account (yes unfortunately you need one) – If you don’t have an account register it
3. You’ll be presented with a “Certificate Requests” page, simply choose the OpenSolaris extras repository and request your certificate
4. Follow the instructions (copy stuff to /var/pkg/ssl, pkg set-authority)
5. pkg install virtualbox
6. wait
7. Be happy with a shiny new VirtualBox installation…

Logrotate is a Linux utility that renames and reuses system error log files on a periodic basis so that they don’t occupy excessive disk space.

The /etc/logrotate.conf File

This is logrotate’s general configuration file in which you can specify the frequency with which the files are reused.

o        You can specify either “weekly” or “daily” rotation parameter. In the case below the weekly option is “commented out” with a “#”, allowing for daily updates.

o        The “rotate” parameter specifies the number of copies of log files logrotate will maintain. In the case below the 4 copy option is “commented out” with a “#”, while allowing 7 copies.

o        The “create” parameter creates a new log file after each rotation

Therefore our sample configuration file will create daily archives of ALL the logfiles and store them for seven days. The files will have the following names with “logfile” being current active version:

logfile

logfile.0

logfile.1

logfile.2

logfile.3

logfile.4

logfile.5

logfile.6

Sample contents of /etc/logrotate.conf

# rotate log files weekly
#weekly

# rotate log files daily
daily

# keep 4 weeks worth of backlogs
#rotate 4

# keep 7 days worth of backlogs
rotate 7

# create new (empty) log files after rotating old ones
create

The /etc/logrotate.d Directory

Most Linux applications that use syslog will put an additional configuration file in this directory to specify the names of the log files to be rotated. It is a good practice to verify that all new applications that you want to use the syslog log have configuration files in this directory. Here are some sample files which define the specific files to be rotated for each application.

The /etc/logrotate.d/syslog File (For General System Logging)

/var/log/cisco/* /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {

sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true
endscript

}

The /etc/logrotate.d/apache File (For Apache)

/var/log/httpd/access_log /var/log/httpd/agent_log /var/log/httpd/error_log /var/log/httpd/referer_log {

missingok
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/httpd.pid 2>/dev/null` 2> /dev/null || true
endscript

}

The /etc/logrotate.d/samba File (for SAMBA)

/var/log/samba/*.log {

notifempty
missingok
sharedscripts
copytruncate
postrotate
/bin/kill -HUP `cat /var/lock/samba/*.pid 2> /dev/null` 2> /dev/null || true
endscript

}

Activating logrotate

The above logrotate settings will not take effect until you issue the following command to do so:

[root@bigboy tmp]# logrotate –f

If you want logrotate to reload only a specifc configuration file, and not all of them, then issue the logrotate command with just that filename as the argument like this:

[root@bigboy tmp]# logrotate -f /etc/logrotate.d/syslog

Should I ever want to switch between release and dev repositories this is just a quick note to the corresponding links:

• OpenSolaris Development Release Packaging Repository
• OpenSolaris Packaging Repository

So, I just switched to OpenSolaris on my workstation. In the sense of “Eating one’s own dog food” I may have a better argumentation on wether I should like it or not. So far everything seems to work althoug I don’t quite have a mirrored ZFS root pool in case one disk dies.

I also nearly immediately switched to the “OpenSolaris Development Release Packaging Repository” – actually that’s a lie. I’m switching to it right at this very moment….

$ pfexec pkg set-publisher -O http://pkg.opensolaris.org/dev opensolaris.org
$ pfexec pkg image-update
Creating Plan /

Maybe, just maybe I’ll stick to it….

Por fin, después de muchas peleas,  hemos puesto un  Solaris en el trabajo .

Si bien Solaris es un Unix, con muchas características comunes con Linux, la forma de trabajar cambiará completamente, al no disponer de nuestros comandos favoritos de Linux, y tener Solaris otra terminología, para los dispositivos conectados al sistema.La red, por supuesto, no podía ser una excepción, así que tenemos que olvidarnos del clásico eth0.

Recomiendo tomar nota del nombre de los dispositivos de red, al instalar el sistema, pero si no lo hemos hecho, podemos recurrir al siguiente comando, para saber cuál es nuestro dispositivo:

bash-3.00# kstat -c net | grep net
name:   bge0                            class:    net
name:   chipid                          class:    net
name:   driverinfo                      class:    net
name:   mii                             class:    net
name:   parameters                      class:    net
name:   phydata                         class:    net
name:   statistics                      class:    net
name:   dls_stat                        class:    net
name:   ip6stat                         class:    net
name:   ipdrop                          class:    net
name:   ipsec_stat                      class:    net
name:   ipstat                          class:    net
name:   ah_stat                         class:    net
name:   esp_stat                        class:    net
name:   lo0                             class:    net
name:   strstat                         class:    net
name:   tcpstat                         class:    net
name:   udpstat                         class:    net

Nuestro dispositivo es bge0
Como queremos saber qué hace este comando kstat, hacemos un man kstat,
"The kstat utility examines the available kernel  statistics,
 or  kstats, on the system and reports those statistics which
 match the criteria  specified  on  the  command  line.  Each
 matching statistic is printed with its module, instance, and
 name fields, as well as its actual value.
....."

bash-3.00# ifconfig bge0
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
 inet 10.150.10.205 netmask ffffff00 broadcast 10.150.10.255
 ether 0:18:8b:11:4f:59

Por defecto, y por cuestiones de seguridad, root no puede hacer login por ssh en un sistema Solaris 10.

Para permitir la entrada de root a través de este servicio, tenemos que editar el archivo /etc/ssh/sshd_config, y modificar la siguiente linea:

PermitRootLogin yes

Hecho esto, hemos de reiniciar el servicio ssh, con svcadm (service admin ?), que intuyo debe ser el comando que sustituye a los clásicos ’service ssh restart’ o ‘/etc/init.d/ssh restart’

#svcadm restart ssh

Para cambiar la distribución del teclado a Spanish(104-Key), editamos el  archivo /boot/solaris/bootenv.rc, y añadimos/modificamos la siguiente linea:

setprop kbd-type ‘Spanish’

Aparte, desde Lanzador/Preferencias/Preferencias del Escritorio/Teclado/Comportamiento, pestaña de Distribuciones, deberíamos también elegir la distribución de nuestro agrado.

Here are the list of useful commands frequently used during package management.

pkgadd

Adds software packages to the system

pkgrm

Removes software packages from the system

pkginfo

Displays software package information

pkgchk

Checks the accuracy of a software package installation

So, we’ll take an example to use above commands. I’ve a package called SUNWant.Z, which I want to install.

So I use the following syntax to add a package.

pkgadd -d SUNWant.Z

To check whether your package has been installed, you can use pkginfo and grep the output to find a specific package.

pkginfo | grep SUNWant

To check the accuracy of the package, you can use pkgchk command as:

pkgchk SUNWant

To remove above package, we have the pkgrm command to use:

pkgrm SUNWant

Refer the Sun documentation for further details.

O Open-solaris é um sistema operacional de código aberto mantido pela Sun e pela comunidade, ele é um sistema clone do Solaris (sistema proprietário da Sun ). A idéia é mais ou menos igual a da Red Hat que comercializa o RHEL e desenvolve junto com a comunidade o Fedora.
O Open- solaris é um sistema operacional derivado do solaris que por sua vez é derivados dos BSDs. As principais caracteristicas do Solaris 10 (tambem do open-solaris) são:

Para download do Open-solaris 2009 clique aqui>;

Sua instalação é facil, pois alem ser em liveCD ele vem com um instalador interativo.

Veja como é feita a instalação:

Basicamente esto es una copia/traducción de lo que hay en la www.oracle-base.com . Lo pongo aquí por comodidad.

La instalación de Solaris por defecto no tiene mayor pega, y podemos recurrir a esta guia si fuera necesario.

Finalmente, instalaremos Oracle Database siguien esta última guia

http://www.howtoforge.com/low-cost-san

Seit dem Linux-Kongress/OSDevCon 2009 in Dresden sind auch schon wieder drei Wochen ins Land gegangen. Trotzdem möchte ich noch kurz meine Eindrücke der Veranstaltung beschreiben.

Das Dorint-Hotel in Dresden war ein recht angenehmer Veranstaltungsort und auch die Abendveranstaltung in den Festungsmauern war sehr schön. Die Fahrt mit dem ICE von Frankfurt nach Dresden fiel dagegen eher in die Kategorie “mühsam”.

Doch nun zur Veranstaltung: Das beide Konferenzen parallel stattfanden und man beide Vorträgsreihen besuchen konnte, fand ich sehr gut.

Das Niveau der Vorträge war im Ganzen recht gut, aber von Andi Kleens Vortrag zu “Linux Multicore Scalability” hätte ich mir doch mehr als eine theoretische Behandlung der Materie erhofft. Die Keynote von Ted T’so und seinen Vortrag zu Filesystem Checks in Ext4fs dagegen fand ich sehr gut. Auch die Vorträge zu Userspace Application Tracing und System Call Tracing Overhead waren interessant.

Auf der (Open)Solaris-Seite habe ich mir zunächst einmal die Dtrace-Vorträge angehört. Linux-Entwickler können endlos über die vermeintlichen Schwachstellen von Dtrace diskutieren, es bleibt aber eine Tatsache das im täglichen Einsatz Dtrace alle anderen Tools um Längen schlägt!

Der Vortrag zu Sun Cluster brachte mir leider keine neuen Erkenntnisse. Dafür ist unser Cluster-Konzept wohl zu ausgefeilt und nutzt den Sun Cluster in einem Maße, daß selbst Sun-Entwickler beeindruckt sind. Die Vorstellung von “Immutable Service Containers” war dagegen technisches Neuland für mich und hat reichlich Stoff zum Nachdenken beschert.

Leider musste ich die letzten drei Vortragsslots des zweiten Tages auslassen, da die Rückfahrt doch rund sechs Stunden dauern sollte. Alles in allem hat sich die Teilnahme gelohnt und im nächsten Jahr werde ich wohl wieder dabei sein.

During the course of experimentation with 11gR2, I was given some space on a Sun Storage 7410 NAS.   In the past NAS meant using NFS with obscure mount options that seemed to vary from platform to platform.  So, at first I went scrambling for the “best practices” to use with Oracle NAS on Solaris.

There is a nice Metalink article Note:359515.1 with the latest information for all platforms.  This Metalink note does include the “tcp” option which is not necessary on Solaris.  So it boiled down to the following mount options for using Oracle data files on NAS devices with Solaris.

rw,bg,hard,nointr,rsize=32768,
wsize=32768,noac,
forcedirectio, vers=3,suid

But wait, what about the new 11g feature to use direct NFS “dNFS”?    More searching…

configuring dNFS on Solaris

This is a fairly simple process.  Although Oracle dNFS configuration is fairly well documented for Linux, I will post my interpretation and commentary to help other Solaris users that might want to configure dNFS.

First, create mount the NFS share just as you would have in the past.  Oracle still needs to see the file system from the OS point of view.  You don’t have to use the mount options as in the past, but you might want them anyway for OS tools may access the mount.  You would most likely place these options in the “/etc/vfstab” file, but I will just show the mount command.

mount -o rw,bg,hard,nointr,rsize=32768,\
wsize=32768,noac,forcedirectio,vers=3,suid \
toromondo.west:/export/glennf /ar1

Second, you have to link the direct NFS libraries in place of ODM.  This is a little clunky, but not terrible.

cd $ORACLE_HOME/lib
cp libodm11.so libodm11.so_stub
ln -s libnfsodm11.so libodm11.so

Third, create the “$ORACLE_HOME/dbs/oranfstab” file.  This file defines the various details Oracle needs to directly access the NFS share.  You can configure multiple paths, so that Oracle can multiplex access to the NFS share.  This is for redundancy and load balancing.  There is another Metalink article ID:822481.1 that details how to configure dNFS with multiple paths across the same subnet and force the OS to not route packets.  This is a great feature, which I will try once I get some more network plumbing.  For now, I just did the most simple configuration as shown below.

cat $ORACLE_HOME/dbs/oranfstab
server: toromondo.west
path: toromondo.west
export: /export/glennf mount:/ar1


Finally, you will be able to see if this takes effect by looking at the “alert.log” file.  When Oracle starts up it places debug information in the alert.log file so we can see if Oracle is using Direct NFS or not.

grep NFS alert_*.log
Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 2.0
Direct NFS: attempting to mount /export/glennf on filer toromondo.west defined in oranfstab
Direct NFS: channel config is:
Direct NFS: mount complete dir /export/glennf on toromondo.west mntport 38844 nfsport 2049
Direct NFS: channel id [0] path [toromondo.west] to filer [toromondo.west] via local [] is UP
Direct NFS: channel id [1] path [toromondo.west] to filer [toromondo.west] via local [] is UP

That’s all there is to it.  Hopefully, you will find this useful.

I love science fiction and I was very excited to hear that an intelligent and thought-provoking director like Steven Soderbergh was going to tackle outer space with the man who spawned the Terminator, James Cameron. With juggernauts like that and a very likeable leading man in George Clooney, what could this film not have going for it?

Soderbergh’s first journey into science fiction is a remake of a 1972 Russian film entitled, Solyaris. The original was dubbed “the Russian 2001″ and found a cosmonaut getting reacquainted with his long dead wife while orbiting the planet Solaris. It was deep, sensitive and even echoed some of the Russian ideals and thoughts of its time.

In the remake Clooney is Chris Kelvin (same name from the original film) an astronaut who comes to a nearly deserted space station to uncover a mystery. While investigating, Kelvin begins being haunted by his dead wife, Rheya (played by Natasha McElhone). Kelvin finds himself drifting away from reality as he comes face to face with why he maybe lost his wife.

The set-up and sentiment is sound in the remake but this isn’t a 1970s science fiction film that uses its characters to reflect on Russian morals and ideals during the Cold War. Instead we are stuck with Clooney and McElhone who seem like too oddest of couples because there is little or no chemistry between these fateful lovers.

The love between these actors is so forced I felt like I had just switched on a re-run of “Days of Our Lives”. Then the film’s photography finds itself panning and zooming into McElhone’s face as it tries to show her through Clooney’s eyes.

Well if it were me I think he would be thinking, “Hmmm, did I brush today?” or “Boy, is my butt cold!”

As the film drifted from the importance of solving the space station’s mystery and problems and focused on Clooney dealing with a distraught McElhone. I so wanted there to be some sort of space station disaster that would at least ignite some sort of release from the film’s continuous mediocrity. I have seen snails with more gusto than this film.

There has been a lot of talk about the film’s scenes involving Clooney’s naked posterior. If it were McElhone’s posterior the film would probably get a “PG-13″ rating but since it’s a “man’s” butt it has to get an “R”. They show more on NYPD Blue for cryin’ out loud.

I believe that Soderbergh’s sentiment for the subject matter is sound and that he did his best to bring forth passion in the space of the film’s waterlogged 90 minutes. Next time, Steve, I suggest you cast someone Clooney enjoys kissing.

1 out of 5

So Says the Soothsayer.

Written: November 29, 2002

M-Audio Solaris Review

Feature

Overview
M-Audio Solaris Solaris is a large-capsule condenser microphone that sounds as good as it looks. Beneath the stylish exterior lies the best-sounding solid-state electronics available at any price. Vintage design principles merge with incredibly tight manufacturing standards to yield no more than +/-1dB of deviation across the entire 20Hz-20kHz frequency range?perfect for matched-pair stereo miking. The industry-thinnest evaporated gold diaphragm also delivers incredible sensitivity. Multi-pattern architecture provides flexibility that makes it ideal for just about any recording situation. It?s like having three mics in one. Specifications: Frequency response: 20Hz-20kHz Sensitivity: 16 mV/Pa (-36 dBv) Max. SPL for 0.5% THD: 130dB Equivalent noise level: 14dB (A-weighted) Output impedance: 200 ? Recommended load impedance: > 1,000 ? Power requirement: 48-volt phantom power Connector: 3-pin male XLR Features: 1.1? evaporated gold diaphragm Ultra-sensitive 3-micron diaphragm Large all-brass capsule Cardioid, omni and figure 8 polar patterns 20Hz-20kHz frequency response +/-1dB tolerance across entire frequency range Class A FET electronics w/ output transformer -10dB attenuation pad Low frequency roll off switch (6dB per octave @ 125Hz) Includes shock mount and aluminum case
Specifications

Nov 18, 2009 02:00:09