yum install kernel-headers kernel-devel gcc
and then run the guest installer script.
After the restart, if you have a shared folder, it may put it at /media/sf_sharename and have permissions issues. Add your user the vboxsf group and reboot should fix it for you.
Quick setup of netatalk and avahi on Ubuntu 10.04.
apt-get install netatalk avahi-daemon
Next configure services. netatalk first.
Enable the server options.
ubuntu -tcp -ipaddr 0.0.0.0 -guestname nogroup \
-admingroup admin -savepassword
Setup some shares.
~/ "$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.
Setup afpd to be broadcast.
<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
Start the services:
More details at the references.
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.
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.
I had a user need a new desktop installed with OpenSuSE 11.2 and get his ATI FirePro 2260 video card.
I am not a fan of SuSE, don’t use it. Too many oddities. For example:
Absolute path to 'ifconfig' is '/sbin/ifconfig', so running it may require superuser privileges (eg. root).
A command like ifconfig should always be in the regular PATH. I could fix it, but I shouldn’t have to.
admin@Sodium:~> sudo -s
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
What good is sudo if its going to ask for root’s password? Defeats the purpose of sudo. I am sure there may be a good reason. But not good enough.
But on to the original reason for this post. The proprietary river from ATI (currently distributed as FirePro_8.702_Linux_96418.zip) is broken. Running the installer script detects the OS and stuff but fails with a glibc error: double free or corruption or something similar. Turns out the script isn’t smart enough to know gcc, make or the kernel headers aren’t installed. Hey ATI! Try a simple trick: try the which command! Once those are installed with
zypper install make gcc
and all is good. (May need the headers and source, but I believe headers are installed by default.)
Here’s the introductory post on my blog for Adventures in System Administration.
I’ll post here notes, tips, etc on UNIX/Linux administration subjects.