For those looking for a way to set persistent custom system and user variables, here are some guidelines for doing so in openSUSE and SLES / SLED.
Other Linux distributions follow a similar approach but the filenames can differ.

NOTE: Export is a command to be used to set your desired setting. Entering ' export ' on the command line will show you the environment variables that have been set. ' env ' will give you a complete list of your environment parameters.

Where and what to place?

Looking for more information on Novell Teaming?

Ok.. so you've setup your Teaming server and had a stab at it...
If your thinking to yourself 'how can I get more out of this?', here are a couple of places to start:

There is an interesting blog over at blog.wilmsenit.nl comparing NSS disk performance on VMWare VMFS vs RAW disk access (RDM).
Surprisingly for NSS there is a big performance drop when using VMFS in combination with iSCSI.

Bottom line:

Download the latest iPrint client (you need at least the 4.38 version found here.)

Needed dependancy package:
Before installing the iPrint rpm, make sure you have the glitz package installed as this is a dependency requirement.

For those waiting to have and test the NCL on openSUSE 11.1 (or SLED11 if you have it), here is the download link for the Beta:

Novell Client for Linux 2.0 SP1 Beta for SLED 11 and OpenSUSE 11.1
For some reason it's not published on the Novell Public Beta site, but so far I have the client working on my 11.1 rig.

Quickest way to get things setup:
1) Download the iso (32 or 64 bit)
2) open a console and elevate to root ( su - )
3) mount the iso ( mount -o loop /path/.iso /mnt )

Often I get questions on SLP, what it exactly does and how to implement it.

To answer the first question. SLP stands for ' Service Location Protocol '.

What it does is already in it's name: It's a service running on one or more systems, that hands out a list of services to your clients specifying what services can be found on your network - instantly, without the need to have the clients ' go out and look '.

It can loosely be compared to DNS, which also helps to centrally resolve. With DNS you can resolve system names and certain services (the mail MX for example) to ip addresses and visa versa.
SLP on the other hand, is specific to making it easy for your networked clients to find out where a service is running they are looking for (e.g. location of printer services, timeserver, authentication sources like eDirectory, etc). The service list is built up dynamically and has more detail.

As of this week, Novell has launched OES2 SP1.
See the announcement

OES2 SP1 is packed with powerful features and makes for an excellent replacement for your Netware systems.

One *very* cool feature that's included in OES2 SP1, is DSfW.

For those feeling forced to migrate to Windows, mostly because there is high demand for some form of application integration that is only available on AD... DSfW might be your ticket to getting best of both worlds!

NOTE: Looking how to install Nagios on openSUSE?

Petr Šimek has created a very nice add-on for Firefox that keeps you informed about the status of one or more Nagios systems.

The plugin can be customized in many ways, visual and sound alerts as also what should be checked when and in which situation.

It's a great way to keep an eye out on the status while surfing the web!

Get your copy at Firefox - Nagios Checker

After getting some requests for a howto on installing ZenWorks on top of SLES, here's a quick writeup.

NOTE: To avoid issues with certain services install ZenWorks 7 on a SLES 10 32 bit version. For those successfully running Zen7 on 64bit, I'd appreciate your feedback
--UPDATE (07-06-2009) : Zen7 SP1 IR4 fixes this issue, see http://www.diwi.nl/node/45 for more info--

Read more on installing a SLES 10 base including eDirectoy 8.8.3

An old post, but still useful when cloning / imaging, so I tough I'd just post it here also.

Note: This should work with (open)SUSE 10 and later (as also other distro versions with slight modification).

A couple of months ago I came across a situation where I wanted to P2V a relay server from a small desktop to a VMWare ESX server. Making and restoring the image was no problem but after restoring and editing the relevant files, I thought I was on a roll until at boot up I got the message :
' waiting for /dev/sda3 to appear ...'.
Until now I had apparently been lucky enough to have a similar chipset when imaging from one system to another.

For those that might hit the same issue, here's my two cents for ya..
This can also be of use when swapping out vital components in your existing system.