thebackroomtech » Sles http://thebackroomtech.com serving up the info back room techs everywhere find interesting Sat, 20 Nov 2010 03:13:09 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Howto: Mount a Windows share on SLES linux using cifs http://thebackroomtech.com/2009/02/19/howto-mount-a-windows-share-on-sles-linux-using-cifs/ http://thebackroomtech.com/2009/02/19/howto-mount-a-windows-share-on-sles-linux-using-cifs/#comments Thu, 19 Feb 2009 13:42:30 +0000 admin http://thebackroomtech.com/?p=1491

This post is mainly for my own benefit.  I mount Windows shares on my SuSE linux box so infrequently, I have to dig through past notes to remind myself what the syntax is.

To mount a Windows share on SLES linux using cifs:

mount -t cifs -o username=jsmith //po5/gwdompri /mnt/po5/gwdompri

where:
  • jsmith is the user account to authenticate as
  • //po5/gwdompri is the Windows server and share you wish to mount
  • /mnt/po5/gwdompri is the location to mount the share, or where you access it on the local Linux box.
Note:
  •  you will be prompted for the password 
  • /mnt/po5/gwdompri must exist

Related Posts

]]> http://thebackroomtech.com/2009/02/19/howto-mount-a-windows-share-on-sles-linux-using-cifs/feed/ 0 Fix for ConsoleOne Error -634 The target server does not have a copy of what the source http://thebackroomtech.com/2009/02/05/fix-for-consoleone-error-634-the-target-server-does-not-have-a-copy-of-what-the-source/ http://thebackroomtech.com/2009/02/05/fix-for-consoleone-error-634-the-target-server-does-not-have-a-copy-of-what-the-source/#comments Thu, 05 Feb 2009 14:24:06 +0000 admin http://thebackroomtech.com/?p=1457

Error seen when attempting to authenticate to eDirectory in ConsoleOne on SLES 10 Linux: 

(Error-634) The target server does not have a copy of what the source
server is requesting. Or, the source server has no objects that match
the request and has no referrals on which to search for the object.

 The SLES Linux box does not have eDirectory installed on it.
 
The solution is, instead of specifying a tree name, specify the IP address of a server with a RW replica to authenticate to.  Specify the IP address in the tree field of the Novell Client login screen.

Related Posts

]]> http://thebackroomtech.com/2009/02/05/fix-for-consoleone-error-634-the-target-server-does-not-have-a-copy-of-what-the-source/feed/ 3 Fix for make install / compiler issues with Intel e1000 NIC driver in SLES 10 http://thebackroomtech.com/2008/11/03/fix-for-make-install-compiler-issues-with-intel-e1000-nic-driver-in-sles-10/ http://thebackroomtech.com/2008/11/03/fix-for-make-install-compiler-issues-with-intel-e1000-nic-driver-in-sles-10/#comments Mon, 03 Nov 2008 09:16:46 +0000 admin http://thebackroomtech.wordpress.com/?p=1143

How I was able to make and install the Intel e1000 NIC driver in SLES 10 Linux:

Steps 1 through 3 of the e1000-8.0.6.tar.gz readme file are simple enough to follow when making the Intel e1000 network card driver on SLES 10 SP2.  
 
1. Move the base driver tar file to the directory of your choice.  For example, /usr/local/src/e1000
 
2. From a terminal prompt, untar archive:
 
    tar zxf e1000-8.0.6.tar.gz
 
3. Change to the driver src directory:
 
    cd e1000-8.0.6/src/
 
Step 4 was where I started having problems
 
4.  make install
 
should have compiled the driver module.  Instead, I received the following error:
 
Linux kernel source not found in any of these locations:
*** Install the appropriate kernel development package, e.g.
*** kernel-devel, for building kernel modules and try again. Stop.
 
I opened YaST and searched for kernel-devel, but that package was not listed.  I did see a kernel-source package, which I installed.  I then ran make install again, and this time I received a different error message:
 
Makefile:131: *** Compiler not found.  Stop.
 
I went back into YaST, installed the gcc compiler, which added glibc-devel and libmudflap packages as dependencies, and ran make install once again.  This time it compiled successfully.
 
The binary was installed as /lib/modules/2.6.16.60-0.21-bigsmp/kernel/drivers/net/e1000/e1000.ko
 
5.  Make sure to remove any older existing drivers before loading the new driver:
 
rmmod e1000
 
6.  The module was then loaded using the following syntax:
 
insmod /lib/modules/2.6.16.60-0.21-bigsmp/kernel/drivers/net/e1000/e1000.ko
 
Once you assign an IP address, you should be able to use the interface.

Related Posts

]]> http://thebackroomtech.com/2008/11/03/fix-for-make-install-compiler-issues-with-intel-e1000-nic-driver-in-sles-10/feed/ 0 Howto: Install rdesktop on SLES 10 SP2 Linux http://thebackroomtech.com/2008/09/26/howto-install-rdesktop-on-sles-10-sp2-linux/ http://thebackroomtech.com/2008/09/26/howto-install-rdesktop-on-sles-10-sp2-linux/#comments Fri, 26 Sep 2008 13:26:08 +0000 admin http://thebackroomtech.wordpress.com/?p=973

rdesktop is software that allows a Linux client to connect to a Microsoft Windows server via RDP, much like mstsc.exe, which is Microsoft’s Remote Desktop Connection (RDC) program.

More precisely, rdesktop.org describes the software as:

rdesktop is an open source client for Windows Terminal Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. Supported servers include Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows XP, Windows Vista and Windows NT Server 4.0.

rdesktop currently runs on most UNIX based platforms with the X Window System.

To install rdesktop on SLES 10 SP2: 

1) Make sure all pre-requisites are installed on the system.  If they are not, add with YaST or download them.
 
2) Extract the rdesktop package. From a terminal window run
gzip -d rdesktop-1.6.0.tar.gz
tar -xvf rdesktop-1.6.0.tar
 
3) From the directory you extracted rdesktop run
./configure
 
4) From the directory you extracted rdesktop run
make
 
5) From the directory you extracted rdesktop run
make install
 
rdesktop will be installed by default to /usr/local
 
to run from a terminal
rdesktop [options] server
 
for example
 
rdesktop -u admin -p passwd 192.168.1.1
 
Would establish a RDP connection to server 192.168.1.1 using admin’s credentials
 
The most commonly used  options are:
 
–u username specifies the user name for authentication on the server.

–p password provides a password for authentication on the server. To keep others from seeing the password supplied on the command line, use –p – to read the password from stdin.

–g geometry allows you to specify the desktop geometry. This can be given as a resolution, such as 1024×768 or as a percentage of the entire screen, as in 70%.

–r device enables device redirection, allowing you to redirect a device, such as sound from the remote machine to the local one. This feature requires Windows XP or newer.

Fixes for known issues when compiling and installing rdesktop
 
“ERROR: Could not find X Window System headers/libraries
To specify paths manually, use the options –x-includes and –x-libraries”
 
FIX: add the X-windows development tools though YaST to compile successfully – x-org-x11-devel
 
ERROR: Could not find OpenSSL headers/libraries.
To specify a path manually, use the –with-openssl option
 
FIX: add the OpenSSL development tools through YaST to compile successfully – openssl-devel

Related Posts

]]> http://thebackroomtech.com/2008/09/26/howto-install-rdesktop-on-sles-10-sp2-linux/feed/ 4 novell-scrub.sh – use when you really, really, really want to get rid of eDirectory http://thebackroomtech.com/2008/09/09/novell-scrubsh-use-when-you-really-really-really-want-to-get-rid-of-edirectory/ http://thebackroomtech.com/2008/09/09/novell-scrubsh-use-when-you-really-really-really-want-to-get-rid-of-edirectory/#comments Tue, 09 Sep 2008 12:21:25 +0000 admin http://thebackroomtech.wordpress.com/?p=823

Earlier I detailed a method for re-installing eDirectory from a difficult SLES 10 SP2 server.  Sometimes even this method doesn’t work, and you have to resort to using novell-scrub.sh to totally remove eDirectory from the server before it can be reinstalled.

WARNING:  THIS SCRIPT WILL REMOVE EDIRECTORY AND ALL IT’S COMPONENTS (CONSOLEONE, GROUPWISE, ETC) SO USE WITH EXTREME CAUTION.  YOU NEED TO UNDERSTAND THE RAMIFICATIONS OF USING THIS SCRIPT IN FULL.

The script will remove all packages and configuration for Novell products. It does NOT deconfigure anything. In the case of eDirectory, you will want to remove the NCP Server object from the tree, once eDirectory has been removed from the UNIX system

TID 2969195 explains how to install and use novell-scrub.sh:

Installation Procedure:

1) Download the tarred compressed file to your UNIX system.

2) Extract the file using the following command:

gzip -dc ./scrub_1_2_12.tgz | tar xvf -

3) Change to the ./scrub_1_2_12 directory where the ./novell-scrub.sh script was extracted.

4) Type ./novell-scrub.sh [options] as the root user.

The script can take the following options:

-s –show
Show which hardcoded Novell packages are installed and not installed on the system.

-d –dyn-show
This is the same as –show but Novell packages are found dynamically.

-i –dibsonly
Removes only DIB files and does not remove packages.

-n –noansi
Disable the use of ANSI colours.

–IAgreeToTheTermsAndConditions
Accepts the agreement and does not prompt for “I Agree”.

-h –help
Displays this command line help.

Related Posts

]]> http://thebackroomtech.com/2008/09/09/novell-scrubsh-use-when-you-really-really-really-want-to-get-rid-of-edirectory/feed/ 0 Simple script to backup Groupwise 7 configuration files on SLES Linux http://thebackroomtech.com/2008/09/08/simple-script-to-backup-groupwise-7-configuration-files-on-sles-linux/ http://thebackroomtech.com/2008/09/08/simple-script-to-backup-groupwise-7-configuration-files-on-sles-linux/#comments Mon, 08 Sep 2008 08:25:55 +0000 admin http://thebackroomtech.wordpress.com/?p=807

I’m about to upgrade our Groupwise infrastructure, and I wanted to write a simple script that would backup and archive important Groupwise configuration files.  I’m not proficient at scripting, but here’s what I came up with.  Please recommend additional files to include if I have overlooked anything.

[sourcecode language='cpp']
####################################
### Begin gwbkup.sh
### script to backup Groupwise configuration files
### /home/backups/gw7cfg is the directory to backup files to
### backup Groupwise agent configuration files
cp /opt/novell/groupwise/agents/share/* /home/backups/gw7cfg/
cp /etc/opt/novell/groupwise/gwha.conf /home/backups/gw7cfg/
### backup Apache web server configuration files
cp /etc/apache2/httpd.conf /home/backups/gw7cfg/
cp /etc/apache2/conf.d/gw* /home/backups/gw7cfg/
### Backup WebAccess configuration files
cp /opt/novell/groupwise/webaccess/webacc.cfg /home/backups/gw7cfg/
cp /opt/novell/groupwise/webaccess/commgr.cfg /home/backups/gw7cfg/commgr.cfg.webacc
cp /opt/novell/groupwise/webaccess/spellchk.cfg /home/backups/gw7cfg/
### Backup WebPublisher configuration files
cp /opt/novell/groupwise/webpublisher/webpub.cfg /home/backups/gw7cfg/
cp /opt/novell/groupwise/webpublisher/commgr.cfg /home/backups/gw7cfg/commgr.cfg.webpub
cp /opt/novell/groupwise/webaccess/ldap.cfg /home/backups/gw7cfg/
### Backup Tomcat configuration files
cp -r /etc/tomcat5/base/* /home/backups/gw7cfg/
### backup gwia files specific to each gateway
### may have more than one gwia per Groupwise system, so append gateway
### name to end of file
cp /mail/gwiado/wpgate/gwia703/exepath.cfg /home/backups/gw7cfg/exepath.cfg.gwia703
cp /mail/gwiado/wpgate/gwia703/gwac.db /home/backups/gw7cfg/gwac.db.gwia703
cp /mail/gwiado/wpgate/gwia703/gwauth.cfg /home/backups/gw7cfg/gwauth.cfg.gwia703
cp /mail/gwiado/wpgate/gwia703/mimetype.cfg /home/backups/gw7cfg/mimetype.cfg.gwia703
### backup webaccess files specific to each gateway
### may have more than one gwia per Groupwise system, so append gateway
### name to end of file
cp /mail/webdo/wpgate/webac703/comint.cfg /home/backups/gw7cfg/comint.cfg.webac703
cp /mail/webdo/wpgate/webac703/commgr.cfg /home/backups/gw7cfg/commgr.cfg.webac703
cp /mail/webdo/wpgate/webac703/gwac.db /home/backups/gw7cfg/gwac.db.webac703
cp /mail/webdo/wpgate/webac703/mimetype.cfg /home/backups/gw7cfg/mimetype.cfg.webac703

### Backup Groupwise monitor files
cp /opt/novell/groupwise/gwmonitor/gwmonitor.cfg /home/backups/gw7cfg/gwmonitor.cfg
cp /opt/novell/groupwise/gwmonitor/default/gwmonitor.cfg /home/backups/gw7cfg/gwmonitor.cfg.default
cp /opt/novell/groupwise/gwmonitor/default/gwmonitor.xml /home/backups/gw7cfg/gwmonitor.xml
### tar configuration files and label archive with today’s date
tar -pcvzf /home/backups/$(date +%m-%d-%Y).tar.gz /home/backups/gw7cfg/
### Remove old configuration files rm -r /home/backups/gw7cfg/* 
### End gwbkup.sh ####################################
[/sourcecode]

Related Posts

]]> http://thebackroomtech.com/2008/09/08/simple-script-to-backup-groupwise-7-configuration-files-on-sles-linux/feed/ 0 Howto: Minimize all Windows and show the Desktop in SLES Linux http://thebackroomtech.com/2008/09/05/howto-minimize-all-windows-and-show-the-desktop-in-sles-linux/ http://thebackroomtech.com/2008/09/05/howto-minimize-all-windows-and-show-the-desktop-in-sles-linux/#comments Fri, 05 Sep 2008 07:41:43 +0000 admin http://thebackroomtech.wordpress.com/?p=802

On my Windows machines I frequently use the Windows Key + D shortcut to minimize all open Windows to quickly access the desktop.  I had been meaning to find the equivalent key combination in SuSE Linux Server Enterprise 10′s Gnome desktop, and finally found out how to do it yesterday.

The shortcut key combination to minimize all open Windows and view the desktop is CTRL+ALT+D

Related Posts

]]> http://thebackroomtech.com/2008/09/05/howto-minimize-all-windows-and-show-the-desktop-in-sles-linux/feed/ 0 Howto: Determine the version of SLES Linux http://thebackroomtech.com/2008/09/03/howto-determine-the-version-of-sles-linux/ http://thebackroomtech.com/2008/09/03/howto-determine-the-version-of-sles-linux/#comments Wed, 03 Sep 2008 08:11:13 +0000 admin http://thebackroomtech.wordpress.com/?p=781

To determine the version of SuSE Linux Enterprise Server (SLES), type the following in a terminal window:

cat /etc/SuSE-release

or

SPident

To determine which kernel version is in use, type the following in a terminal window:

rpm -qf /boot/vmlinuz

Related Posts

]]> http://thebackroomtech.com/2008/09/03/howto-determine-the-version-of-sles-linux/feed/ 3 Fix for path not found (8209) when loading Groupwise POA http://thebackroomtech.com/2008/08/28/fix-for-path-not-found-8209-when-loading-groupwise-poa/ http://thebackroomtech.com/2008/08/28/fix-for-path-not-found-8209-when-loading-groupwise-poa/#comments Thu, 28 Aug 2008 14:12:37 +0000 admin http://thebackroomtech.wordpress.com/?p=758

My error was path not found (8209) \\nw1\vol1\logs\testpo when trying to load a POA on a SLES 10 SP1 Groupwise 7.0.3 server.  I had just migrated the POA named testpo from Netware to SLES manually rather than use the Groupwise Server Migration Utility since I wanted to have a good understanding what had to happen behind the scenes before I tried migrating my live system.

The path to \\nw1\vol1\logs\testpo was the POA log file location on the old Netware Groupwise server.  I knew that I needed to fix that path, but couldn’t find where Groupwise was pulling it from.  Things I tried to resolve the problem included:

  • Verified /log path to location reported was not specified in testpo.poa file on the SLES server
  • Verified in ConsoleOne that the POA object for testpo did not have the Netware path in question specified in the Groupwise > Log Settings > Log File Path
  • Deleted and recreated POA object for testpo
  • Deleted testpo.poa file and re-ran Groupwise install from SLES box, specifying post office named testpo and path to testpo database on the SLES server
  • Verified path to old Software Distribution Directory on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Software Directory Management 
  • Verified path to old restore area on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Restore Area Management 
  • Used gnome-search-toolto search the entire SLES server for files containing the text \\nw1\vol1\logs\testpo
    no files containing that text were found on the SLES server

The Fix ended up being rebuilding the testpo post office.  To do this:

ConsoleOne > Tools > Groupwise Utilities > System Maintenance > Rebuild Database

Related Posts

]]> http://thebackroomtech.com/2008/08/28/fix-for-path-not-found-8209-when-loading-groupwise-poa/feed/ 0 Howto: Mount a USB device in SuSE Linux http://thebackroomtech.com/2008/08/11/howto-mount-a-usb-device-in-suse-linux/ http://thebackroomtech.com/2008/08/11/howto-mount-a-usb-device-in-suse-linux/#comments Mon, 11 Aug 2008 08:12:01 +0000 admin http://thebackroomtech.wordpress.com/?p=583

I have a Kingston USB flash drive that does not automatically mount itself on my SLES server on occasion.  TID 7000951 explains how to mount the drive manually:

1) From a terminal, run:

lsmod |grep usb  make sure usb_storage is loaded.  If it is not, run:

modprobe usb-storage

2) Plug the USB device in and run dmesg.  The results will look like:

USB Mass Storage support registered.
scsi 6:0:0:0: Direct-Access CRUCIAL USB Flash Disk 2.00 PQ: 0 ANSI: 2
ready
sd 6:0:0:0: [sdd] 1017856 512-byte hardware sectors (521 MB)
sd 6:0:0:0: [sdd] Write Protect is off
sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
sd 6:0:0:0: [sdd] Assuming drive cache: write through
sd 6:0:0:0: [sdd] 1017856 512-byte hardware sectors (521 MB)
sd 6:0:0:0: [sdd] Write Protect is off
sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
sd 6:0:0:0: [sdd] Assuming drive cache: write through
sdd: sdd1 <– THIS IS THE DEVICE NAME
sd 6:0:0:0: [sdd] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete

Look for the kernel device name, in this case, /dev/sdd, with a partition on /dev/sdd1

3) Mount volume manually by running:

mount /dev/sdd1 /mnt

Access the USB drive at /mnt

To unmount the USB drive run:

umount /mnt

Related Posts

]]> http://thebackroomtech.com/2008/08/11/howto-mount-a-usb-device-in-suse-linux/feed/ 4