1. Go to java.com.
2. Download the linux RPM installer for your cpu type.
3. sh /path/to/downloaded.rpm.bin
4. follow the bouncing ball.

And that’s it.


[mycentosvm:~] root# java -version
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode)


== blank passphrase

1) generate private/public keys on A
$ ssh-keygen -t dsa
press enter when it asks for the filename
press enter when it asks for the passphrase (yes, a blank passphrase)
this will generate two files: ~/.ssh/id_dsa and ~/.ssh/id_dsa.pub

2) put ~/.ssh/id_dsa.pub from A into ~/.ssh/authorized_keys2 on B
$ cat ~/.ssh/id_dsa.pub | ssh B ‘cat >> ~/.ssh/authorized_keys2′

3) make sure all files are not writable or readable except by owner
do this on A and B
$ chmod a-x,go-w,o-r ~/.ssh/*

4) verify it works
$ ssh B ls -la

== single-logon

1) generate private/public keys on A
$ ssh-keygen -t dsa
press enter when it asks for the filename
enter a passphrase
this will generate two files: ~/.ssh/id_dsa and ~/.ssh/id_dsa.pub

2) put ~/.ssh/id_dsa.pub from A in ~/.ssh/authorized_keys2 on B
$ cat ~/.ssh/id_dsa.pub | ssh B ‘cat >> ~/.ssh/authorized_keys2′

3) make sure all files are not writable or readable except by owner
do this on A and B
$ chmod a-x,go-w,o-r ~/.ssh/*

4) use ssh-agent to manage passphrases
$ eval $(ssh-agent)

5) make agent aware of passphrases
$ ssh-add # enter the appropriate passphrase for each remote host

6) verify everything works
$ ssh B ls -la

user# find . -name "*searchstring*" -exec rm {} ;

Probably a good idea to run it without

-exec rm {} ;

first to see what you’d be deleting.

Oh, and the space after the {} really is important – the command won’t do anything unless it’s there…

6. Check to see what’s currently installed, if any.
# rpm -q bcm5700

If an old version of the package exists, the RPM package should be
removed.

# rpm -e bcm5700

Then remove the loaded bcm5700 module.

# rmmod bcm5700

Verify that the old bcm5700 package has been removed as follows:

# rpm -q bcm5700
7. Install the new rpm
# rpm -ivh RPMS/i386/bcm5700-< version >.i386.rpm –force
8. Ensure that the /etc/modules.conf file is configured similar to the
example listed below. The example below is presented as if more
than one adapter is present. If so, one eth# instance should exist
for each ethernet port. Refer to the modules.conf man page for more
information.

alias eth0 bcm5700
alias eth1 bcm5700
alias eth# bcm5700
9. You can now reboot your server. Upon reboot the network should
start with the bcm5700 driver loaded and the correct network
configuration. To verify that the bcm5700 driver is loaded, use
the following command.

# lsmod

If bcm5700 is listed then the bcm5700 driver loaded. If not and /etc/modules.conf lists the wrong driver for ethX, ifdown the interfaces, rmmod wrong_alias_name, edit /etc/modules.conf, replacing with alias ethX bcm5700, insmod bcm5700, and ifup the interfaces (or just edit /etc/modules.conf and reboot…)

Getting MythTV running on Fedora – couldn’t get much more focused than that, huh? Pretty cool…

~If you want/need to set the MAC address on your VLAN interface, include the parameter MACADDR=XX:XX:XX:XX:XX:XX in your /etc/sysconfig/network-scripts/ifcfg-eth* file.

~If you’d like to keep you traffic confined on it’s respective interface, you’ll probably want source-based routing. Look at http://lartc.org/howto/lartc.rpdb.multiple-links.html and extrapolate/leave out what you don’t need. One caveat is that when using ip link set and ip address add (wether called by hand, homebrew script, or by Peter’s nasty ifup), the kernel will add a route for you that you (probably) don’t want in this scenario, since you’ll be creating separate routing tables for each interface.

~Here’s a patch for ifup-post (my system is kernel 2.4.21-9.EL on RedHat ESv3, YMMV) that will fixup (read: delete) the kernel added route if you define ‘ALLOW_KERNEL_ROUTE = no’ in your /etc/sysconfig/network-scripts/ifcfg-eth* file:

--- ifup-post.distro    2004-01-30 22:08:55.000000000 -0600
+++ ifup-post   2004-01-30 22:11:11.000000000 -0600
@@ -14,6 +14,12 @@

 /etc/sysconfig/network-scripts/ifup-routes ${DEVICE} ${DEVNAME}

+if [ "$ALLOW_KERNEL_ROUTE" = no ] ; then
+  expand_config
+  if ! ip ro del ${NETWORK}/${PREFIX} dev ${DEVICE}; then
+    echo "Sorry, but I wasn't able to delete the kernel added route..."
+  fi
+fi
 if [ "$PEERDNS" != "no" -o -n "$RESOLV_MODS" -a "$RESOLV_MODS" != "no" ]; then
   [ -n "$MS_DNS1" ] && DNS1=$MS_DNS1
   [ -n "$MS_DNS2" ] && DNS2=$MS_DNS2