In the JDeveloper IDE, right click on the resources folder in your project structure (applications navigator window).  Select “New…” from the window and “File” from the general category.  Name the new file “database.properties”.

database.username=username
database.password=password
database.class=oracle.jdbc.OracleDriver
database.url=jdbc:oracle:thin:@host:port:sid

Place the above in the file (substitute values in italics) and save your project.

I am working now on Ubuntu Karmic Koala.

As I said in my previous post, Qemu is a complete platform emulator that can emulate the Integrator ARM machine platform (CPU and devices!).

In Karmic Koala the latests Qemu version (0.11.0) is shipped within Ubuntu repositories so with this line we can install it:

# sudo apt-get install qemu qemu-kvm qemu-kvm-extras

ARM test images

From the Qemu home page we can download a Linux 2.6 ARM example image builded by Paul Brook and extracting it in $PRJROOT/images, we can find the README file where it is written how to launch the test platform:

# cp DownloadDirectory/arm-test-0.2.tar.gz $PRJROOT/images
# cd $PRJROOT/images
# tar -xvf arm-test-0.2.tar.gz
# cd arm-test
# cat README

So, with or without the graphical interface we can test the qemu arm installation with the followings:

# qemu-system-arm -kernel zImage.integrator -initrd arm_root.img
or
# qemu-system-arm -kernel zImage.integrator -initrd arm_root.img \
  -nographic -append "console=ttyAMA0"

A suitable Linux config file

Over the test purpose , executing the test image can give the kernel configuration file stored in /proc/config.gz ! so:

# qemu-system-arm -kernel zImage.integrator -initrd arm_root.img \
  -nographic -append "console=ttyAMA0"
Uncompressing Linux...............................................
........................... done, booting the kernel.
Linux version 2.6.17-rc3 (paul@wren) (gcc version 4.1.0 (CodeSourcery ARM))
 #53 Thu May 4 15:05:18 BST 2006
CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
Machine: ARM-IntegratorCP
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-through cache
CPU0: I cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets
CPU0: D cache: 65536 bytes, associativity 4, 32 byte lines, 512 sets
Built 1 zonelists
Kernel command line: console=ttyAMA0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total

...

Log in as root with no password.
qemu login: root
# cp /proc/config.gz .
# tar -xvf config.gz
# vi config.gz

With this file we can configure the mainline linux kernel! (copying from screen, copying within net, scrolling the options with a near mainline make menuconfig window).

ARMv5te Toolchain to build the kernel

The machine emulated by qemu-arm is based on the core ARMv5te , so I need the correct toolchain for build all the necessary code.

The Pengutronix OSELAS environment can do that in the OSELAS toolchain project. Similarly at what described in Initializing a Linux Embedded Development Host Machine moving in $PRJROOT/build-tools/OSELAS.Toolchain-1.99.3.4/ we can select the suitable ptxdist configs with:

# cd $PRJROOT/build-tools/OSELAS.Toolchain-1.99.3.4/
# ls ptxconfigs/
arm-1136jfs-linux-gnueabi_gcc-4.1.2_glibc-2.5_binutils-2.17_kernel-2.6.18.ptxconfig
arm-1136jfs-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.19_kernel-2.6.27-sanitized.ptxconfig
arm-1136jfs-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.19_kernel-2.6.27-sanitized.ptxconfig.old
arm-cortexa8-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
armeb-xscale-linux-gnueabi_gcc-4.1.2_glibc-2.5_binutils-2.17_kernel-2.6.18.ptxconfig
armeb-xscale-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
...
arm-v4t-linux-gnueabi_gcc-4.1.2_glibc-2.5_binutils-2.17_kernel-2.6.18.ptxconfig
arm-v4t-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
arm-v5te-linux-gnueabi_gcc-4.1.2_glibc-2.5_binutils-2.17_kernel-2.6.18.ptxconfig
arm-v5te-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
arm-v5te_vfp-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
arm-xscale-linux-gnueabi_gcc-4.1.2_glibc-2.5_binutils-2.17_kernel-2.6.18.ptxconfig
arm-xscale-linux-gnueabi_gcc-4.2.3_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
...
# ptxdist select ptxconfigs/\
  arm-v5te-linux-gnueabi_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
# ptxdist menuconfig

In the menuconfig, all can live as it is but in “misc->prefix for installation” we can choose $PRJROOT/tools where $PRJROOT must be manually extended. So with:

# ptxdist go

A part from minor dependencies that we can solve installing software with apt-get, the toolchain is built and the correct prefix will be:

CROSS_COMPILE_OSELAS_v5=$PRJROOT/tools/OSELAS.Toolchain-1.99.3/arm-v5te-linux-gnueabi/\
   gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/bin/arm-v5te-linux-gnueabi-

If we assign the environmental variable CROSS_COMPILE=CROSS_COMPILE_OSELAS_v5 the kernel configured by the upper config file and compiled with this toolchain is a good kernel to execute within the qemu-system-arm emulator!

A suitable Root Filesystem

Ok we have a good kernel ad a small initrd filesystem, but we have to develop application to run in the emulated device!

We can use the OSELAS.BSP Phytec phyCORE project installed following the description in Initializing a Linux Embedded Development Host Machine.

Download the platform_config file platformconfig-qemu and the ptxconfig one ptxconfigThiny (that is the normal ptxconfig removing all graphic subsystem for a speedier compilation)

Every two configuration file must be placed in $PRJROOT/build-BSP/OSELAS.BSP-Phytec-phyCORE-12-1/configs so with:

# cd $PRJROOT/build-BSP/OSELAS.BSP-Phytec-phyCORE-12-1/
# ptxdist select configs/ptxconfigThiny
# ptxdist platform configs/platformconfig-qemu
# ptxdist toolchain $CROSS_COMPILE_OSELAS_v5
# ptxdist go
# ptxdist images

In  $PRJROOT/build-BSP/OSELAS.BSP-Phytec-phyCORE-12-1/platform-phyCORE-qemu/images/ we will find the root.ext2 image, ready to be the SD/MMC image of the qemu device!

Running qemu

If in the $PRJROOT directory we create the images/phyCORE directory and we put all the necessary:

# cd $PRJROOT
# mkdir -p images/phyCORE
# cp (kernel_path)/arch/arm/boot/zImage images/phyCORE/
# cp $PRJROOT/build-BSP/OSELAS.BSP-Phytec-phyCORE-12-1/platform-phyCORE-qemu/images/root.ext2\
  images/phyCORE/

then we can start qemu:

# qemu-system-arm -kernel images/phyCORE/zImage -sd images/phyCORE/root.ext2 \
  -nographic -append "console=ttyAMA0 root=/dev/mmcblk0"

Results

In results we have a complete developing environment: emulator, toolchain, kernel, software ecosystem.

Kernel modification that do not deal with the hardware abstraction layer can be well developed in the emulator and tested by ad-hoc software inserted in the phyCORE-qemu distribution!

Merhabalar,

CRM’de veriler girildikten sonra toplu birden fazla kaydın seçilip bu kayıtlardaki bazı alanların toplu olarak değiştirilmesi gerekebilir. Ancak CRM arayüzünde tüm varlıklar için gözükmemektedir.

CRM’de bazı varlıklar için default olarak bulunan Bulk Edit→Toplu Düzenle butonu aktivite, fatura gibi varlıklarda yoktur. Bu özellik ISV.config’te değişiklik yaparak değiştirilebilir.Ayarlar→Özellikleri Ver→ISV.Config dosyasını kaydettikten sonra notepad yada Visual Studio ile düzeltmeler yapıldıktan sonra Özellikleri Al ile kaydedilen konum gösterilerek özellikler alınır.Ve refresh edildikten sonra buton gözükür. Ancak bir ayar daha yapılması gerekir. Tüm diğer custom eklenen ISV butonlarının gözükmesi için bu ayar yapılmalıdır.

Ayarlar→Yönetim→Sistem Ayarları→Özelleştirme tabında Özel menüler ve Araç çubuklarından istemcileri kullanıma bağlı olarak istediğiniz kombinasyonu ancak Web’ten genel olarak kullanıldığı için Web seçeneğini sağ kutuya alıp tamam’ı tıklayarak kaydetmeniz gerekmektedir. ISV.config’de yaratılan bazı butonlar Client attribute’ünde belirtilip Web,Outlook,Outlook Offline şeklinde belirtilmektedir.
İstediğiniz varlık’ın altına <Grid> tagleri arasında CRM’in çağırdığı şekilde yani doAction(‘crmGrid’, ‘1088′, ‘bulkedit’); şeklinde yazılır. 1088 objecttypecode’dur,isteğiniz entity’nin altına kodu yazarak bu kodu değiştirmeniz yeterlidir.

 NOT:ISV.Config tagleri hakkında bilgi için ISV.Config’i inceleyelim… makalelere bakabilirsiniz.

 <Entity>

<Grid>

<MenuBar>

<Buttons>

<Button Icon=”/_imgs/ico_18_debug.gif” JavaScript=”doAction(‘crmGrid’, ‘4201′, ‘bulkedit’);” Client=”Web”>

<Titles>

<Title LCID=”1033″ Text=”Bulk Edit” />

</Titles>

<ToolTips>

<ToolTip LCID=”1033″ Text=”Bulk Edit.” />

</ToolTips>

</Button>

</Buttons>

</MenuBar>

</Grid>

</Entity>

En esta Oportunidad les Traigo una recopilación de lo q yo concidero son los comandos más, utiles, importantes y usados tanto en Ubuntu como en muchas otras distros linux

• Adduser: Se utiliza para añadir un usuario.

Uso: adduser <nombreusuario>

• Alias (este esta bien explicado en un post anterior)
  

Uso: alias nombrequeledamos=’comando’

• apt-get install nombredelprograma =  instala el paquete.

• apt-get remove nombredelprograma = Borra el paquete. Con la opción –purge borra tambien la configuración del paquete instalado.

• apt-get update = Actualiza la lista de paquetes disponibles para instalar.

• apt-get upgrade  = Instala las nuevas versiones de los diferentes paquetes disponibles.

• cd = Cambia el directorio.

Uso: cd nombredirectorio

Continuar leyendo el resto de comandos:

• chmod: Cambia los permisos de los archivos.

r:lectura w:escritura x:ejecución
+: añade permisos -:quita permisos
u:usuario g:grupo del usuario o:otros
Uso: chmod permisos nombrearchivo

• chown: Cambia el propietario de un archivo.

Uso: chown <nombrepropietario> <nombrearchivo>

• cp:Copia archivos en el directorio indicado.

Uso: cp archivoorigen archivodestino

• deluser: Elimina una cuenta de usuario

Uso: deluser <nombreusuario>

• exit: Cierra las ventanas o las conexiones remotas establecidas

• fsck: Sirve para chequear si hay errores en nuestro disco duro.

Uso: fsck -t <fs_typo> <dispositivo>

• ftp: Protocolo de Transferencia de Archivos, permite transferir archivos de y para computadores remotos.

Uso: ftp <maquina_remota>

• grep: Su funcionalidad es la de escribir en salida estándar aquellas líneas que concuerden con un patrón. Busca patrones en archivos.

grep: grep <patronabuscar> <nombrearchivos>

• ifconfig: Obtener información de la configuración de red

• kill: Termina un proceso

Uso: kill numeroPID

• ls:Lista los archivos y directorios dentro del directorio de trabajo.

• make: Crea ejecutables a partir de los archivos fuente.

• man: muestra el manual de un programa o comando si este esta disponible

Uso: man <nombredelcomando>

• mkdir: Crea un nuevo directorio.

Uso: mkdir nombredirectorio

• mount: Monta una unidad.

Uso: mount -t< sistema_de_archivo> <dispositivo> <nombredirectorio>

• mv: Este comando sirve para renombrar un archivo.

Uso: mv <nombrearchivo> <nuevonombrearchivo>

• netstat:Muestra las conexiones y puertos abiertos por los que se establecen las comunicaciones.

• poweroff: Apaga el ordenador.

• ps: Muestra información acerca de los procesos activos.

• rlogin: Conecta un host local con un host remoto.

Uso: rlogin <maquina_remota>

• rm: Remueve o elimina un archivo.

Uso: rm <rutaynombrearchivo>

• rmdir: Elimina el directorio indicado, el cual debe estar vacío.

Uso: rmdir nombredirectorio

• sudo o su: Con este comando accedemos al sistema como root.

• umount: Desmontar unidades montadas anteriormente

Uso: umount <nombredirectorio>

• wc:Cuenta los caráteres, palabras y líneas del archivo de texto.

Uso: wc nom_archivo

• whereis: Devuelve la ubicación del archivo especificado, si existe.

Uso: whereis nomb_archivo

Larga vida a la consola!!

Most people are good about making backup copies of their configuration before changes, but everyone makes mistakes eventually. To me the risk is not worth it, so this will be dedicated to automating Cisco TFTP backups of configurations. Most server administrators have automated tasks using either Cron (Linux/Unix) or Windows Scheduler. Cisco IOS also has the ability to schedule tasks.

I am very picky when it comes to my Cisco devices. A lot of information I read on this had the schedule execute “copy running-config startup” and would only backup one configuration. This is not a good thing, especially when there are multiple device managers. Below will go through setting up two jobs that backup both the running and saved configurations to different files daily.

Note: This assumes that you already have a TFTP server running on the network.

After logging into the switch, move into configuration mode

FiberSw01# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.

Enable the scheduler

FiberSw01(config)# scheduler enable

Crate a job named “backup_running”

FiberSw01(config)# scheduler job name backup_running

Enter the syntax used to copy the running configuration to your TFTP server

FiberSw01(config-job)# copy running-config tftp://172.0.0.22:69/config/FiberSw01_running

Exit configuration mode

FiberSw01(config-job)# end

Now that we have a job defined, make sure it is listed with the scheduler

FiberSw01# show scheduler job
Job Name: backup_running
------------------------
   copy running-config tftp://172.0.0.22:69/config/FiberSw01_running
==============================================================================

With the job defined, we can go back in and set when we want it executed

FiberSw01# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.

Define a new schedule name and set execution time(s)

FiberSw01(config)# scheduler schedule name Backup_Running
FiberSw01(config-schedule)# time daily 23:00
FiberSw01(config-schedule)# job name backup_running
FiberSw01(config-schedule)# end

Now the schedule(s) can be listed with names, execution times, and status

FiberSw01# show scheduler schedule
Schedule Name       : Backup_Running
------------------------------------
User Name           : user
Schedule Type       : Run every day at 23 Hrs 0 Mins
Last Execution Time : Yet to be executed
-----------------------------------------------
     Job Name            Last Execution Status
-----------------------------------------------
    backup_running                        -NA-
==============================================================================

Since the running configuration was backed up previously, we can go in configure the startup configuration backup. All commands are close to above except the tftp file name

FiberSw01# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.
FiberSw01(config)# scheduler job name backup_startup
FiberSw01(config-job)# copy startup-config tftp://172.0.0.22:69/config/FiberSw01_startup
FiberSw01(config-job)# end

FiberSw01# config t
Enter configuration commands, one per line.  End with CNTL/Z.
FiberSw01(config)# scheduler schedule name Backup_Startup
FiberSw01(config-schedule)# time daily 23:05
FiberSw01(config-schedule)# job name backup_startup
FiberSw01(config-schedule)# end

Check the schedule once more and both jobs show up

FiberSw01# show scheduler schedule
Schedule Name       : Backup_Running
------------------------------------
User Name           : user
Schedule Type       : Run every day at 23 Hrs 0 Mins
Last Execution Time : Yet to be executed
-----------------------------------------------
     Job Name            Last Execution Status
-----------------------------------------------
    backup_running                        -NA-
==============================================================================
Schedule Name       : Backup_Startup
------------------------------------
User Name           : user
Schedule Type       : Run every day at 23 Hrs 5 Mins
Last Execution Time : Yet to be executed
-----------------------------------------------
     Job Name            Last Execution Status
-----------------------------------------------
    backup_startup                        -NA-
==============================================================================
Now that the configuration is done, save the current (running) configuration so the schedules will not be lost on reboot
FiberSw01# copy running-config startup-config
[########################################] 100%
Notes: The above was done on Cisco MDS Switches but should work on most other Ciso IOS versions.  Also, the Execution Status will change after the job is executed.

Perhaps you have a web application which not only has a database in which it stores its content but also has one to hold logging data (Exceptions, Log Entries).

This can be a common practice used to keep unrelated data separate and to off load the load created by logging data for purely health monitoring reasons.

If you are using Castle ActiveRecord as your ORM (Object Relational Mapping) layer and are familiar with setting it up for one database you may not be familiar with configuring it to handle more than one database for your objects.

ActiveRecord decides which database to send an object to based on a combination of a Abstract base class which inherits from ActiveRecordBase and a separate configuration section for each of those base classes. Each of those base classes must also be registered with ActiveRecord at application startup just like any Entity you plan on using within the application.

Below are the steps you need to take to properly setup your ASP.net web application to use 2 databases.

1. Create a ActiveRecordBase class for each of the databases you will be using. Each entity which inherits from that base class will be mapped to the corresponding database.

public abstract class ApplicationActiveRecordBase<T> : ActiveRecordBase<T>{}

public abstract class LoggingActiveRecordBase<T> : ActiveRecordBase<T>{}

2. Initialize each of the base classes so that ActiveRecord is aware of the classes

        static ActiveRecordInitializer()

        {

            IConfigurationSource source = ActiveRecordSectionHandler.Instance;

            ActiveRecordStarter.Initialize(

                source,

                typeof(LoggingActiveRecordBase<>),

                typeof(ApplicationActiveRecordBase<>));

        }

3. All entities belonging to a specific database should inherit from the base class associated with that database in the configuration.

    [DataContract]

    [ActiveRecord(Table = "exceptionentry")]

    public class ExceptionEntry : LoggingActiveRecordBase<ExceptionEntry>

    {

4. Add configuration sections to the ActiveRecord configuration for each database specifying the ActiveRecordBase class that will be used to identify the database.

  <activerecord isWeb="true" isDebug="false" threadinfotype="Castle.ActiveRecord.Framework.Scopes.HybridWebThreadScopeInfo, Castle.ActiveRecord">

    <config type="ActiveRecord.BaseClasses.ApplicationActiveRecordBase`1, Data.Core, Version=1.0.0.0, Culture=neutral">

      <add key="hibernate.connection.provider" value="NHibernate.Connection.DriverConnectionProvider" />

      <add key="hibernate.dialect" value="NHibernate.Dialect.MySQLDialect" />

      <add key="hibernate.connection.driver_class" value="NHibernate.Driver.MySqlDataDriver" />

      <add key="hibernate.connection.connection_string" value="Server=localhost; Database=YOURAPPLICATIONDATABASE; User Id=YOURUSER; Password=YOURPASSWORD" />

    </config>

    <config type="ActiveRecord.BaseClasses.LoggingActiveRecordBase`1, Data.Core, Version=1.0.0.0, Culture=neutral">

      <add key="hibernate.connection.provider" value="NHibernate.Connection.DriverConnectionProvider" />

      <add key="hibernate.dialect" value="NHibernate.Dialect.MySQLDialect" />

      <add key="hibernate.connection.driver_class" value="NHibernate.Driver.MySqlDataDriver" />

      <add key="hibernate.connection.connection_string" value="Server=localhost; Database=YOURLOGGINGDATABASE; User Id=YOURUSER; Password=YOURPASSWORD" />

    </config>

  </activerecord>  

Pour avoir un thème de couleur vert reposant les yeux dans emacs il suffit de mettre ceci dans un fichier .Xresources puis relancer sa session X :

emacs*Background: DarkSlateGray
emacs*Foreground: Wheat
emacs*pointerColor: Orchid
emacs*cursorColor: Orchid
emacs*bitmapIcon: on
#emacs*font: -adobe-helvetica-*-r-*-*-14-*-*-*-*-*-*-*
emacs*font: -*-fixed-bold-r-*-*-15-*-*-*-*-*-*-*
emacs.geometry: 125x40

In this article I have not described more advanced setups, such as clusters, replication, etc. This article is designed as an overview of a basic, one-server, OLTP environment.

I have categorized configuration options into server options, disk configuration and startup options.

sp_configure 'show advanced options', 1
go
reconfigure
go
sp_configure
go

Or

select * from sys.configurations
go

affinity mask

affinity io mask

cost threshold for parallelism

fill factor

index create memory

locks

max degree of parallelism

max worker threads

min and max server memory

min memory per query

priority boost

recovery interval

Startup Options

-g memory_to_reserve

-T trace flag

-x

SQL Server Configuration – The Basics.

Wpis ten otwiera nowy dział w etmain: configi najlepszych graczy et. Na pierwszy ogień poszedł config gracza o nicku butchji. Kojarzycie?

Nazwa: cfg – butchji

Wielkość: 13.3 KB

Download:  butchji.rar(uploading.com)

An application is considered an isolated application if all of its components are side-by-side assemblies. A side-by-side assembly is a collection of resources—a group of DLLs, windows classes, COM servers, type libraries, or interfaces—available for an application to use at runtime. Typically, a side-by-side assembly is one to several DLLs. For example, the C Runtime Library assembly contains three DLLs—msvcr90.dll, msvcm90.dll and msvcp90.dll—and is used by applications when they are built using functions from the CRT library.

A side-by-side assembly can be either shared or private. Shared side-by-side assemblies may be used by multiple applications that specify, in their manifests, a dependence on the assembly. Multiple versions of side-by-side assemblies can be shared by different applications running at the same time. A private assembly is an assembly that is deployed with an application and is available for the exclusive use of that application. Private assemblies are installed in the folder containing the application’s executable file or one of its subfolders.

A private assembly is an assembly that is deployed with an application and is available for the exclusive use of that application. That is, other applications do not share the private assembly. Private assemblies are one of the methods that can be used to create isolated applications. For more information, see About Isolated Applications and Side-by-Side Assemblies.

Private assemblies must be designed to work side-by-side with other versions of the assembly on the system. For more information, see Guidelines for Creating Side-by-side Assemblies.

Note that the steps for creating a private assembly are identical to those for creating a shared assembly with two exceptions:

• A private assembly is not required to be signed, and publickeyToken is not required in the <assemblyIdentity> element of the assembly manifest.
• Private assemblies can be installed into the application’s folder using any installation technology. Private assemblies are not required to be installed using the Windows Installer.

Private Assemblies (Windows).

To configure session timeout in an app’s config file, use the session-properties element in sun-web.xml.

To configure it in the Glassfish console, go to Configurations > config-name > Web Container > Session Properties.

Here’s a great table for all your snd-hda-intel needs: Ubuntu Wiki audio_intel_da.

Una vez que tengamos instalado nuestro servidor DNS, podemos utilizar un segundo servidor modificando solamente algunos parámetros de nuestra configuración anterior. Para ello tomaremos del ejemplo anterior el servidor que lleva por nombre webserv, con IP 192.168.17.4 y le instalamos Bind9 como se muestra en el tutorial anterior. Por ahora lo dejamos como está y pasamos a configurar el servidor primario.

En el servidor primario abrimos el fichero /etc/bind/named.conf.local, buscamos estas líneas:

zone “tudominio.com” IN {
type master;
file “/var/cache/bind/tudominio.com.lan.zone”;
allow-query { any; };
allow-update { servidores-lan; };
allow-transfer { 192.168.17.1; };
notify yes;
};

zone “17.168.192.in-addr.arpa” IN {
type master;
file “/var/cache/bind/17.168.192.in-addr.arpa”;
allow-query { any; };
allow-update { servidores-lan; };
allow-transfer { 192.168.17.1; };
notify yes;
};

Y lo único que tenemos que hacer es modificar la línea:

allow-transfer { 192.168.17.1; };

Y poner la IP de nuestro servidor secundario.

Ahora vamos a los ficheros de zonas y nos quedarían de esta forma.

;——— Configuración Local —————–
;—————————————————
$TTL 10m ; Tiempo de vida de la Zona
$ORIGIN tudominio.com. ; Nombre del dominio
@ IN SOA ns1.tudominio.com. admin.tudominio.com. (
2009100401     ; Serial y modificación del archivo
10m            ; ref = Tiempo para refrescar
30m            ; ret = Tiempo de reintento para actualizacion
1d             ; ex = Tiempo de expiracion
10m            ; min = minimo
)

;——– Registros Principales ———-
;—————————————–

@    IN                 NS    ns1
@    IN                 NS    ns2
@    IN                 MX    10    mx
@    IN                  A    192.168.17.1

;——– Registros Extras —————
;—————————————–

@    IN TXT    “Nombre de tu Red”
@    IN TXT    “v=spf1 a mx a:mx.tudominio.com include:tudominio.com ~all”
@    HINFO     “Dell PowerEdge 2850″ “Debian GNU/Linux”

;——— Registros A ——————-
;—————————————–

mx          IN                 A    192.168.17.2
IN               TXT    “Mail (Work Server)”
IN               TXT    “v=spf1 a -all”
mail        IN                 A    192.168.17.2

ns1         IN                 A    192.168.17.1
pdc         IN                 A    192.168.17.1

proxy       IN                 A    192.168.17.3

ns2         IN                 A    192.168.17.4
webserv     IN                 A    192.168.17.4

tudominio.com. IN              A    192.168.17.1
tudominio.com. IN              A    192.168.17.4

@           IN                 A    192.168.17.1

;——– Registros CNAME —————————–
;——————————————————

www                  IN     CNAME   proxy

webmail              IN     CNAME   mail

foro                 IN     CNAME    webserv
ftp                  IN     CNAME   webserv

; ——- Registro para el Jabber ———————
;——————————————————
$ORIGIN tudominio.com.
@                       A       192.168.157.155
$ORIGIN _tcp.jabber.tudominio.com.
_jabber                 SRV     5 0 5269 tudominio.com.
_xmpp-server            SRV     5 0 5269 tudominio.com.
_xmpp-client            SRV     5 0 5222 tudominio.com.

Como pueden ver hemos agregado un nuevo servidor DNS ( los cambios están en rojo). Ahora hacemos lo mismo con el fichero de zona inversa:

;——— DOMINIO – LAN —————–
;—————————————–
$TTL 10m ; Tiempo de vida de la Zona
$ORIGIN 17.168.192.IN-ADDR.ARPA. ; Rango de la Red
@ IN SOA ns1.tudominio.com. admin.tudominio.com. (
2009030401          ; Serial y modificación del archivo
10m         ; ref = Tiempo para refrescar
30m         ; ret = Tiempo de reintento para actualizacion
1d          ; ex = Tiempo de expiracion
10m         ; min = minimo
)

;——– Servidores DNS —————–
;—————————————–
@ IN         NS     ns1.tudominio.com.
@ IN         NS     ns2.tudominio.com.

;———— IP HOST ——————–
;—————————————–
1                 IN         PTR     ns1.tudominio.com.
IN         PTR     pdc.tudominio.com.
2                 IN         PTR     mx.tudominio.com.
IN         PTR     mail.tudominio.com.
3                 IN         PTR     proxy.tudominio.com.
4                 IN         PTR     ns2.tudominio.com.
IN         PTR     webserv.tudominio.com.

Una vez que hemos terminado copiamos los mismos archivos al servidor secundario. Ahora solamente tenemos que modificar en nuestro servidor secundario el fichero /etc/bind/named.conf el cual nos quedaría de esta forma:

zone “tudominio.com” IN {
type slave;
file “/var/cache/bind/tudominio.com.lan.zone”;
allow-query { any; };
masters { 192.168.17.1; };
notify yes;
};

zone “17.168.192.in-addr.arpa” IN {
type slave;
file “/var/cache/bind/17.168.192.in-addr.arpa”;
allow-query { any; };
masters { 192.168.17.1; };
notify yes;
};

Como ven hemos declarado que tipo de servidor es (en este caso secundario o esclavo) y cual es el servidor primario o maestro.

Algo importante a tener en cuenta es que cuando modificamos estos ficheros, debemos modificar también el número de serie del mismo. En el ejemplo yo utilizo 2009030401 que viene siendo: año/mes/dia/numero de modificacion.

So I am visiting some colleagues who have a CUPS server and insist that it is “Apple crap” and should work with my Macbook; but it doesn’t. So I have to add the printer using the hardware driver which annoys my colleague since he doesn’t want users messing up the hardware (understandably). Since I just wanted to print I just do it anyway and print the paper I wanted.

That was yesterday, since I don’t like annoying people I figure I will see what the net has to say about it. Turns out that by default OS X 10.5 doesn’t look for CUPS shared printers because CUPS has been replaced with Bonjour sharing. But it is extremely easy to turn on; In a terminal window enter the following:

sudo cupsctl BrowseProtocols='"cups dnssd"'

This command tells the printer browser to look for dnssd(Bonjour) AND cups shared printers (sudo is needed since you are editing configuration files with this command so care should be taken). Then you have to wait for a bit as CUPS servers only send information periodically. Voila, you should see all the printers shared in the “Default” tab of the add printer settings.

If you want to revert back to the original Bonjour ONLY browsing then run the command:

sudo cupsctl BrowseProtocols='"dnssd"'

Apple has a little info on this on their website but it doesn’t really advertise that it works with many linux/unix systems.
Link

Alienware announced refreshes to both the design and the technology of its high-end Area-51 and Aurora gaming desktops. A new angular look replaces the familiar rounded alien-head shape of the old models, and features like motorized air vents and specialized hard drive layout give Alienware some unique selling points. Alienware is also the previously unnamed OEM who purchased the first batch of AMD’s Radeon HD 5800 cards, so other system vendors can blame Dell/Alienware for their short supply and delayed order shipping.
Essentially Alienware has two systems to announce today, the full tower Area-51 and the micro-ATX-based Aurora. Each system also has a more expensive ALX edition that features liquid cooling, a wider array of case lighting, and other tweaks.

The most unique feature of the new case that’s common to both the Area 51 and the Aurora is the motorized air vents, which Alienware calls its Active Venting louver system. As Alienware describes it, when the temperature inside the case reaches a certain level, fins on the top of the case will open up automatically to increase airflow. We have a hunch Alienware doesn’t mind the theatrics of this venting system, either.
Unfortunately missing from our Alienware PR shots is an image of the Area 51’s hard drive array. Rather than inserting the drives into main cavity, Alienware has carved out a series of six flat-lying drive bays on the opposite side of the Area 51. The benefits of this design are more apparent than the venting system, in that it lets you add more internal storage than you could normally, allows for easy drive installation, and also frees up room air flow inside the main case compartment. No other vendor that we know of offers such a design.

Wanting to make changes to the wifi and DNS settings of the new routers that Cincinnati Bell (CB) is routinely installing now, I went about researching and using trial and error. The goal was to implement WPA2 wifi security and OpenDNS at a router level, so as to help clients be a bit more secure.

Overview of high speed modem/router

Near as I can tell, Cincinnati Bell is using its installed fiber in urban locations to offer a high speed internet, combined with television channels via internet, so-called IPTV. Westell has long been a provider of equipment to our local phone company and this device is meant to offer “Advanced, dual-core processing power with Ethernet, MoCA, or VDSL2 WAN interface for fiber-to-the-home and fiber-to-the-curb networks.” (link) These are hunka-chunka, white bricks and I’ll leave it to others to show us what’s actually inside them and perhaps explain their hugeness.

Getting access to advanced settings

As made clear on Westell’s web site their stuff is marketed to ISP’s, not thru retail / wholesale channels. As such, finding a manual is like pulling teeth. I must give credit to others’ posts on for helping me just figure out the interface and that you need to click on menus up top AND on the left.)

First: Set wifi to WPA2

Cincinnati Bell routinely sets up WEP, even though it’s known to be useless in the face of hacks. (To their credit, they used to always be setup as unsecured / open!) But, WEP lets customers use older equipment, especially gaming systems, so I suppose it cuts down on support calls.  Setup was pretty straightforward. Just point to the IP of the gateway (seems like CB or Westell has a tradition of making this 192.168.200.1) and input the default admin password of  (you guessed it) “admin” and “password”.    Using wireless button, wireless settings menu option (on left) set to WPA2, with PSK (Pre-Shared Key) and using AES encryption algorithm.

Westell conveniently locates all wifi setting in one spot.

On to OpenDNS

I won’t go into all the benefits of OpenDNS, but will just talk about configuring it on the UltraLine Series3 . Note that OpenDNS usually does a pretty good job of explaining this stuff at their site, but it didn’t have anything about this device when I last visited.

1.    OpenDNS
a.    OpenDNS setup with account (not described here)
b.    OpenDNS software (not described here)
c.    Westell Router settings:
i.    On top, My Network
ii.    On left, Network Connection
iii.    Click WAN VDSL, either the main link or the pencil
iv.    On left, click Settings
v.    Change DNS Server option
1.    From Obtain DNS Server Addresses Automatically
2.    To settings Use the following DNS server addresses
a.    207.68.222.222 and
b.    207.68.220.220
vi.    Test by resetting router (Advance menu and Reboot) and resetting computer’s network connection.
d.    Save Westell configuration
i.    At top, Advanced
ii.    Do you want to proceed? Yes
iii.    Configuration file option
iv.    At bottom, Save Configuration File
v.    Downloads a file called Wireless Broadband Configuration.conf. Put this someplace safe.

Here’s a pic of the Settings page: