Howto: Mount a Windows share on SLES linux using cifs


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

Fix for make install / compiler issues with Intel e1000 NIC driver in SLES 10


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.

Howto: Determine the version of SLES Linux


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

Posted in Linux. Tags: , . 3 Comments »

Howto: Mount a USB device in SuSE Linux


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

Posted in howto, Linux. Tags: , , , . 4 Comments »

Novell has released patches for DNS cache poisoning vulnerability


Novell has released patches for novell-bind on OES2 and named.nlm on Netware that address the deficiencies in the DNS protocol and common DNS implementations that facilitate DNS cache poisoning attacks described in CVE-2008-1447.   

Patches for bind running on SuSE Enterprise Linux Server (SLES) 9 and 10, plus openSUSE 10.2, 10.3, and 11.0 were released previously.   

See TID 7000912 for details. Security patches are available from the Novell download site.

These patches should be applied as soon as possible.  Metasploit exploits of this vulnerability are already available.

ConsoleOne error on SLES 10 SP2: Can’t find Java


So, the other day I wrote about my Java errors I experienced when trying to load VNC in Firefox on a brand new SuSE 10 SP2 server.  Today brought about a new Java error after I installed ConsoleOne 1.3.6f on the
same SLES 10 SP2 servers. I  received the following message while trying to start up ConsoleOne for the first time:

no java found

I figured it had to do with me not using the version of Java that shipped with C1.  Here’s what I did to fix the problem:

1) Browse to the /usr/ConsoleOne/bin/ConsoleOne file and right click on it.
2) Select the Permissions tab, and give Owner write access
3) Edit the /usr/ConsoleOne/bin/ConsoleOne file with gedit
4) Add the following line that points to our java installation directory:
export C1_JRE_HOME=/usr/java/jre1.6.0_07
5) Save the file and exit gedit
6) To run ConsoleOne execute: /usr/ConsoleOne/bin/ConsoleOne

Replace /usr/java/jre1.6.0_07 with the path to your Java installation. 

To the location of your version of Java, run the following from a terminal:
find / -name java

Howto: Fix VNC / Firefox plugin problems on SLES 10 SP2


Yesterday I installed two identical SuSE Linux Enterprise (SLES) 10 SP2 servers on their own private network.  Since this private network was completeky isolated, neither server received any updates or patches.  When I tried to connect from one server to the other through VNC at http://192.168.1.2:5801, I received the following message from Firefox:

Plugin Finder Service Window reports Firefox is now checking for available plugins
Click here to download plugin

I figured Firefox was trying to download the Java browser plugin from the Internet.  I had not installed Java during the base installation, so this is what I did to fix the problem:

1)      Downloaded the most recent version of Java,  1.6.0_07 available from http://java.com/en/download/manual.jsp
2)      Copied jre-6u7-linux-i586-rpm.bin to /usr/src/packages/RPMs/i586
3)      Opened a terminal and su root
4)      cd /usr/src/packages/RPMs/i586
5)      Typed chmod a+x jre-6u7-linux-i586-rpm.bin
6)      To start install type  ./ jre-6u7-linux-i586-rpm.bin
7)      Hit the space bar several times to view license agreement
8)      Press y to accept license agreement.  Java will be installed to /usr/java/jre1.6.0_07
9)      Link Java to plugin directory.  To do this type cd /usr/lib/browser-plugins
10)    Type  ln -s /usr/java/jre1.6.0_07/plugin/i386/ns7/libjavaplugin_oji.so

Firefox was then able to see the VNC login screen at
http://192.168.1.2:5801

Posted in Linux. Tags: , , , , . 2 Comments »