ubuntu 12 interfaces file

because, well, yeah.

auto eth0
iface eth0 inet static
        address 10.100.100.184
        netmask 255.255.255.0
        network 10.100.100.0
        broadcast 10.100.100.255
        gateway 10.100.100.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 10.100.100.100
        dns-search whatevs.local

auth eth1
iface eth1 inet static
        address 192.168.100.184
        netmask 255.255.255.0
        network 192.168.100.0
        broadcast 192.168.100.255
        mtu 9000

look mom, those are some jumbo frames.

vmware esxi 5.0 jumbo frames conf

just because i got really really mad.

Enabling Jumbo Frames for all portgroups or ports

You can configure the MTU value of a vDS switch so that all portgroups and ports use Jumbo Frames.

Note: Any new ports created after adjusting the setting use Jumbo Frames. Existing ports are not affected.
 
To configure Jumbo Frames on a vDS using vSphere Client on vCenter 5.1 and earlier:
From vCenter Server click, click Home > Inventory > Networking.
Right-click the vDS and choose Edit Settings.
On the Properties tab, select the Advanced option.
Change the Maximum MTU value from the default value of 1500 to 9000. This enables Jumbo Frames on all portgroups and ports.
To configure Jumbo Frames on a vDS in vSphere Web Client for vCenter 5.1 and vCenter 5.5:
Browse to a distributed switch in the vSphere Web Client navigator.
Click the Manage tab, and click Settings > Properties.
Click Edit.
Click Advanced and set the MTU property to a value greater than 1500 bytes.

Note: You cannot set the MTU size to a value greater than 9000 bytes.

Click OK.
Enabling Jumbo Frames on a VMkernel port from the vCenter server

To enable Jumbo Frames on a VMkernel port from vCenter Server 5.1 and earlier:

Click Home > Hosts and Clusters > Host > Configuration > Networking.
Navigate to the vSphere Distributed Switch tab.
Click the VMkernel port (eg: vmk1)
Click Manage Virtual Adapters.
Select the vmk interface and click Edit.
Under the NIC settings, change the MTU value to 9000.
Click OK. 
To enable Jumbo Frames on a VMkernel port using vSphere Web Client in vCenter 5.1 and vCenter 5.5:
In the vSphere Web Client, navigate to the host.
Under Manage, select Networking and then select VMkernel adapters.
Select a VMkernel adapter from the adapter table.

The properties of the adapter appear.

Click the name of the VMkernel adapter.
Click Edit.
Select NIC settings and set the MTU property to a value greater than 1500.

Note: You can increase the MTU size up to 9000 bytes.

Click OK.
Enabling Jumbo Frames on a VMkernel port in ESX/ESXi 4.1 and ESXi 5.x from SSH/console:

If you have existing VMkernel ports and you want to enable Jumbo Frames on them from SSH, follow instructions below.
 
This example shows how to enable Jumbo frames on VMkernel port vmk1 in a vDS called NewLAN-DVS:
Get the vDS name and DVPortID for the VMkernel port with the command:

# esxcfg-vswitch -l

The output looks similar to (truncated for readability):

DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
NewLAN-DVS 256 23 256 1500 vmnic3,vmnic2,vmnic15

DVPort IDIn UseClient
115 1 vmk1

Get network information (IP, Netmask, and PG/DV port name) for the VMkernel port with the command:

# esxcfg-vmknic -l

The output looks similar to (truncated for readability):

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSSEnabled Type
vmk1 115 IPv4 172.32.10.71 255.255.255.0 172.32.10.255 00:50:56:7d:ee:1e 1500 65535 true STATIC

Note: You see this output if Jumbo Frames is not enabled because the MTU is set to 1500.

Run this command to change the MTU size for the individual port group:

# esxcfg-vmknic -m 9000 -v  -s 

For example:

# esxcfg-vmknic -m 9000 -v 115 -s "NewLAN-DVS"


Confirm that VMkernel port vmk1 is configured with Jumbo Frames enabled, run the command:

# esxcfg-vmknic -l

The output looks similar to:

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSSEnabled Type
vmk1 115 IPv4 172.32.10.71 255.255.255.0 172.32.10.255 00:50:56:7d:ee:1e 9000 65535 true STATIC
Enabling Jumbo Frames on a VMkernel port in ESX/EXi 4.0 from SSH/console:

You can only enable Jumbo Frames on VMkernel ports when they are being created. If the vDS does not have Jumbo Frames enabled, you can only configure this setting for a VMkernel port from a console or SSH/Putty session.
 
If you have existing VMkernel ports and you want to enable Jumbo Frames on them, you have to delete and recreate them.
 
This example shows how to delete the VMkernel port vmk1 in a vDS called NewLAN-DVS and recreate it with Jumbo Frames support enabled:
Get the vDS name and DVPortID for the VMkernel port with the command:

# esxcfg-vswitch -l

The output looks similar to (truncated for readability):

DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
NewLAN-DVS 256 23 256 1500 vmnic3,vmnic2,vmnic15

DVPort IDIn UseClient
115 1 vmk1

Get network information (IP, Netmask, and PG/DV port name) for the VMkernel port with the command:

# esxcfg-vmknic -l

The output looks similar to (truncated for readability):

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSSEnabled Type
vmk1 115 IPv4 172.32.10.71 255.255.255.0 172.32.10.255 00:50:56:7d:ee:1e 1500 65535 true STATIC

Note: You see this output if Jumbo Frames is not enabled because the MTU is set to 1500.

Delete the VMkernel port for vmk1 with the command:

# esxcfg-vmknic -d -s  -v  

To delete VMkernel port vmk1 that is defined in the output in step 2, run the command:

# esxcfg-vmknic -d -s "NewLAN-DVS" -v 115 115
Note: In the example above, the DVPort Name is named as 115.

Create the new VMkernel port for vmk1 with Jumbo Frames (MTU 9000) with the command:

# esxcfg-vmknic -a -i  -n  -m 9000 - s  -v  

To recreate vmk1 with the same configuration and Jumbo Frames enabled, run the command:

# esxcfg-vmknic -a -i 172.32.10.71 -n 255.255.255.0 -m 9000 -s "NewLAN-DVS" -v 115 115

Confirm that VMkernel port vmk1 is configured with Jumbo Frames enabled, run the command:

# esxcfg-vmknic -l

The output looks similar to:

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSSEnabled Type
vmk1 115 IPv4 172.32.10.71 255.255.255.0 172.32.10.255 00:50:56:7d:ee:1e 9000 65535 true STATIC

global linux perms change

 Wholescale ownership change  
 So you need to change the gid on all files owned by user. Do the following as root:  
 find / -uid 1500 -gid 100 -exec chown 15038:101 {} \;  
 A breakdown is as follows:  
 find / -uid 1500 -gid 100 -exec chown 1500:101 {} \;  
 ^  ^   ^    ^    ^  
 |  |   |    |    |  
 |  |   |    |    |   
 |  |   |    |    |  
 |  |   |    |    do this chown userid:new group {all files found}  
 |  |   |    |  
 |  |   |    user's primary group  
 |  |   |  
 |  |   userid  
 |  |  
 |  filesystem  
 |  
 command  

from where did that c compiler come from

Sun Studio 10: CC Sun C++ 5.7 2005/01/07
Sun Studio 11: CC Sun C++ 5.8 Patch 121017-10 2007/02/21
Sun Studio 12: CC Sun C++ 5.9 SunOS_sparc Patch 123863-01 2007/07/25
Solaris Studio 12.3: CC Sun C++ 5.12 SunOS_sparc 2011/11/16

sun studio 11 installation failure.

 Installing Sun Studio Software  
 Exception in thread "Thread-27" java.lang.NoClassDefFoundError: com/sun/install/panels/ComponentSelectionListener  
     at java.lang.Class.getDeclaredMethods0(Native Method)  
     at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)  
     at java.lang.Class.getDeclaredMethod(Class.java:1935)  
     at java.awt.Component.isCoalesceEventsOverriden(Component.java:5973)  
     at java.awt.Component.access$500(Component.java:169)  
     at java.awt.Component$3.run(Component.java:5927)  
     at java.awt.Component$3.run(Component.java:5925)  
     at java.security.AccessController.doPrivileged(Native Method)  
     at java.awt.Component.checkCoalescing(Component.java:5924)  
     at java.awt.Component.<init>(Component.java:5893)  
     at java.awt.Container.<init>(Container.java:251)  
     at javax.swing.JComponent.<init>(JComponent.java:570)  
     at javax.swing.JPanel.<init>(JPanel.java:65)  
     at javax.swing.JPanel.<init>(JPanel.java:92)  
     at javax.swing.JPanel.<init>(JPanel.java:100)  
     at com.sun.wizards.core.WizardComponent.<init>(WizardComponent.java:159)  
     at com.sun.wizards.core.WizardComponent.<init>(WizardComponent.java:145)  
     at com.sun.wizards.core.WizardLeaf.<init>(WizardLeaf.java:78)  
     at com.sun.install.panels.ComponentPanel.<init>(ComponentPanel.java:144)  
     at com.sun.install.products.CreateSimpleUninstaller.createSimpleUninstallerTree(CreateSimpleUninstaller.java:42)  
     at com.sun.install.products.UninstallArchiveCreator.writeArchiveFile(UninstallArchiveCreator.java:537)  
     at com.sun.install.products.UninstallArchiveCreator.writeArchive(UninstallArchiveCreator.java:317)  
     at com.sun.install.products.UninstallUnit.install(UninstallUnit.java:740)  
     at com.sun.install.products.Product.performInstallation(Product.java:649)  
     at com.sun.install.tasks.ProductTask.perform(ProductTask.java:153)  
     at com.sun.wizards.core.Sequence.perform(Sequence.java:343)  
     at com.sun.wizards.core.SequenceManager.run(SequenceManager.java:226)  
     at java.lang.Thread.run(Thread.java:662)  
 really?  
 # mv /usr/java /usr/java.orig  
 # ln -s /usr/jdk/jdk1.5.0_30 /usr/java  

yeah. so, jdk1.6 is a no go.

clearcase note

 1  
 From my past installations on Solaris, you have to:  
 install it on global zone (for the mvfs part to install properly and be available for all the ngz)  
 install it on the non-global zones you need ClearCase  
 ClearCase won't be able to access all the paths it needs during the installation in an ngz, hence the first install on global zone.  
 See, for instance for CC8.0: "Installing Rational ClearCase to support non-global zones."  
 Install and configure Rational ClearCase on the global zone before you install and configure it on any non-global zones.  
 If you plan to run dynamic views on a non-global zone, the MVFS must be installed on the global zone on that computer. Specifically, this means that you cannot choose the ClearCase Server-only Installation option when installing Rational ClearCase on the global zone.  
 I never experienced a lack of performance because of being in an ngz, provided you reserve the appropriate quantity of resource (disk, memory) to each ngz.  
 I never used ClearCase in a global zone only, since I needed to start/stop ClearCase in each ngz independently. Hence my requirement for having CC in ngz, not just in global zone.  

sol 8 nis client tasks

 Edit /etc/hosts to include entries for the NIS master and all slaves.  
 # domainname yourdomain  
 # domainname > /etc/defaultdomain  
 # ypinit -c  
 Add the following hosts:  
 nis_master  
 nis_slave  
 nis_other_slave  
 nis_master-a   (other interface, if available)  
 nis_slave-a   (other interface, if available)  
 nis_other_slave-a   (other interface, if available)  
 If one of the NIS slave servers is closer on the network , add it first in the list, then the next closest (slave or master), etc.  
 Start NIS  
 # cp /etc/nsswitch.nis /etc/nsswitch.conf   (edit the original /etc/nsswitch.nis beforehand as described earlier)  
 # /usr/lib/netsvc/yp/ypstart   (normally called from /etc/init.d/rcp)  
 # ypwhich should return  
 nis_master  
 Also the following commands:  
 # ypcat hosts  
 # ypcat passwd  
 should return lots of relevant data.  

clear that arp cache

arp that arp cache. oh yes.

 #!/bin/sh  
 for i in `awk -F ' ' '{ if ( $1 ~ /[0-9{1,3}].[0-9{1,3}].[0-9{1,3}].[0-9{1,3}]/ ) print $1 }' /proc/net/arp` ; do arp -d $i ; done  

axfr and bind9 acls

okay chump.

root@captainwalker # dig thunderdome.com @blaster axfr

barfs? captainwalker is your axfr host. did you check this:

 Master (blaster) :  
    acl "captainwalker" {  
         10.10.10.12;  
     };  
     zone "thunderdome.com" IN {  
         type master;  
         file "db.thunderdome.com";  
         notify yes;  
         allow-update { none; };  
         allow-query { any; };  
         allow-transfer { captainwalker; };  
     };  
 Slave (captainwalker) :  
     zone "thunderdome.com" IN {  
         type slave;  
         masters { blaster; };  
         file "db.thunderdome.com";  
         notify no;  
         allow-query { any; };  
         allow-transfer { none; };  
     };