Ubuntu 10.10 initial steps

Just a few of the common extra packages and config settings I do.

Install ssh-server and kernel headers

apt-get install linux-generic linux-headers-generic linux-image-generic ssh

VirtualBox (if hardware can handle it)

echo "deb http://download.virtualbox.org/virtualbox/debian maverick contrib non-free" >> /etc/apt/sources.list
wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add - 
apt-get update
apt-get install virtualbox-4.0

Install beep (nice to have some audible feedback at times… and annoy people too)

apt-get install beep
modprobe -a pcspkr

Also add
modprobe -a pcspkr to /etc/rc.local

Fixing Ubuntu 10.10 motd

In /etc/update-motd.d are where the per login motd is generated.

First, if you want to add stuff, look at 99-footer

# motd.tail is reserved for the admin to append static
# trailing information to a dynamically generated
# /etc/motd.
#
# To add dynamic information, add a numbered
# script to /etc/update-motd.d/

I have custom .bash_profile, so some of this is redundant.

I can remove the help-text and the header

rm 00-header
rm 10-help-text

	

Install netatalk and avahi on Ubuntu 10.04

Quick setup of netatalk and avahi on Ubuntu 10.04.

Simply,

apt-get install netatalk avahi-daemon

Next configure services. netatalk first.

cd /etc/netatalk/

Enable the server options.

vi afpd.conf
ubuntu -tcp -ipaddr 0.0.0.0 -guestname nogroup \
 -admingroup admin -savepassword
Setup some shares.
vi AppleVolumes.default
~/ "$u Home Directory"  allow:$u rwlist:@admin options:usedots,upriv perm:0775 veto:/lost+found/
/path "shareName"   allow:@admin rwlist:@admin options:usedots,upriv perm:0775 veto:/lost+found/

Enable the server to run.

vi /etc/default/netatalk
CNID_METAD_RUN=yes
AFPD_RUN=yes
TIMELORD_RUN=yes
Avahi

Setup afpd to be broadcast.

vi /etc/avahi/services/afpd.service
<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
<name replace-wildcards="yes">%h</name>
<service>
<type>_afpovertcp._tcp</type>
<port>548</port>
</service>
<service>
<type>_device-info._tcp</type>
<port>0</port>
<txt-record>model=Xserve</txt-record>
</service>
</service-group>

Start the services:

/etc/init.d/netatalk restart
restart avahi-daemon
More details at the references.
References:
http://www.kremalicious.com/2008/06/ubuntu-as-mac-file-server-and-time-machine-volume/
http://netatalk.sourceforge.net/2.0/htmldocs/AppleVolumes.default.5.html

Best Product Review Ever

Last year, a fellow admin where I work had the opportunity to provide one of the best product reviews EVER. It did get some attention, the product manager did call and ask for us to take it down. We had hoped that the attention then would have gotten some problems with it resolved. But, no such luck yet. Anyway, here’s the text and the link has a pdf of the web page before it was removed.

Absolutely Horrendous
By Extremely Dissapointed from Wilmington, NC on 12/18/2009
Cons: Freezes Easily Describe Yourself: Tech Professional Primary use: Business Bottom Line: No, I would not recommend this to a friend
Our 7410 Cluster has been nothing but a problem. We’ve encountered all sorts of issues with it. The biggest of which is coming in on a Monday and seeing that the entire cluster is frozen and has been all weekend. Let me repeat this… BOTH heads were inoperable. Remember that a cluster is supposed to have the benefit of redundancy. Not one time has our cluster failed over in the manner it was supposed to. Not once.
So far, and by so far I mean a span of about a year, we have not been able to use this thing in a production environment as it is simply not reliable.
To add insult to injury, every time we’ve had to deal Sun support regarding our 7410, it has literally been a nightmare. Our average length of time to “resolution” has been around 4-5 days. I sarcastically quote resolution because we’ve yet to actually receive a resolution to the lockup problem. We’ve been told several times that a “workaround” is forthcoming. A “workaround”? Yeah, a “workaround”. Apathetic is how I would characterize the response I have received from Sun Support thus far.
With 22 firmware updates you would expect they would have resolved this massive bug by now. Yet they haven’t… Unreal.
I could go on and on but will simply wrap this up and tell you to stay far away from this product and from Sun Support. Sun does NOTHING to make me want to champion their hardware, software, support, and/or their all-around brand. I’m not sure I understand why Oracle would want to pick them up. Who knows, maybe they’re masochists?
I would rate this zero stars if it were possible.

Sun-Storage-7410-Unified-Storage-System