Archive for the ‘SuSE Linux’ Category
Posted by jpluimers on 2014/01/06
When configuring a fresh SUSE machine, I forgot one tiny detail resulting in Sendmail ok on 127.0.0.1 but not ip address.
Solution:
Please change in /etc/sysconfig/mail from SMTPD_LISTEN_REMOTE="no" to
SMTPD_LISTEN_REMOTE="yes"
then run SuSEconfig
and rcsendmail restart
–jeroen
via: Re: [SLE] Sendmail ok on 127.0.0.1 but not ip address.
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2014/01/02
Very interesting, especially since rdesktop.org works with Windows Server 2008 R2 and Windows 7 as well, and is stable on x64.
It provides three tools: rdesktop, rdpproxy and seamlessrdp.
Researching this, I also found about TSWindowClipper which allows you to seamlessly integrates remote apps on your client by integrating a DLL inside the MSTSC software using the official virtual channels.
Back to rdesktop: I really wish the documentation was better, but it contains some very interesting source code.
rdesktop is an open source client for Windows Remote Desktop Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. rdesktop is known to work with Windows versions such as NT 4 Terminal Server, 2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2.
rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.
rdesktop is released under the GNU Public Licence (GPL), version 3. Please send feedback, bug reports and patches to the appropriate mailing list. Patches can also be submitted to the SF patch tracker.
rdesktop is a project. See the Sourceforge rdesktop project info and the Wiki for more information.
Status
The latest stable version of rdesktop is 1.7.1 (edit: this was at the time of writing, for the current latest, check here). This versions solves major issues with 64bit version and smartcard support among a few minor fixes.
–jeroen
via rdesktop: A Remote Desktop Protocol client.
Posted in *nix, Development, Linux, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Software Development, SuSE Linux, Windows, Windows 7, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2013/12/24
I’ve been wanting this a very long time, so I’m going to install it Right Now ™ (:
Right before X-Mas, Scooter Software did the ANN: Beyond Compare 4.0 beta available on Windows, Linux, and OS X:
Posted: Dec 23, 2013 4:17 PM
Beyond Compare 4.0 beta is now available for testing on Windows, Linux, and OS X.
http://www.scootersoftware.com/beta
This version adds a number of new features: Read the rest of this entry »
Posted in *nix, Apple, Beyond Compare, Delphi, Development, Linux, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.7 Lion, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, OS X 10.8 Mountain Lion, Power User, Software Development, Source Code Management, SuSE Linux, Windows | Leave a Comment »
Posted by jpluimers on 2013/12/16
Thanks DevShed:
ls -l –time-style=full-iso
Emits full ISO 8601 time stamps and it works on:
- SuSE Linux
- Mac OS X
- Cygwin
–jeroen
via: list date with seconds from ls command – Dev Shed.
Posted in *nix, Cygwin, Linux, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2013/12/06
Like forgetting about the tar syntax, I usually forget which is the left parameter in an ln command (the file or link? it is the file!)
Thanks [WayBack] cyberciti.biz:
There are two types of links
- symbolic links: Refer to a symbolic path indicating the abstract location of another file
- hard links : Refer to the specific location of physical data.
To create a symbolic link in Unix or Linux, at the shell prompt, enter the following command:
ln -s {target-filename} {symbolic-filename}
–jeroen
via: How to: Linux / UNIX create soft link with ln command.
Posted in *nix, Cygwin, Endian, Linux, Power User, SuSE Linux | 2 Comments »
Posted by jpluimers on 2013/09/09
A while ago, I had to transfer a couple of files from a Linux machine where I did have console access, but no proper network access.
This was the sequence to get it connected and copy a directory to the USB flash drive:
- Stick the USB flash drive in a USB port (duh <g>) on the Linux system
- Run the fdisk command to see on which device it got loaded:
# fdisk -l
It will give you something like this:
Disk /dev/sdd: 8019 MB, 8019509248 bytes
20 heads, 16 sectors/track, 48947 cylinders
Units = cylinders of 320 * 512 = 163840 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 48948 7831512 b Win95 FAT32
- Create a
/mnt/USB directory to mount the device to using the mkdir command:
# mkdir /mnt/USB
- Use the
modprobe command to make sure the vfat file system support is loaded:
# modprobe vfat
- Use the
mount command to mount the device from the first step (/dev/sdd1) to the directory you created (/mnt/USB)
# mount /dev/sdd1 /mnt/USB
- Use the
rsync command to recursively (-p) copy a directory maintaining timestamps (-t) and showing progress (-v)
# rsync -rtv /home/user/directory/ /mnt/USB/directory/
- Use the
umount command to unmount the directory (and therefore the device)
# umount /mnt/USB
–jeroen
via: Simple mounting of FAT32 USB Flash Drive.
Posted in *nix, Linux, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2013/09/06
As Dave mentioned a couple of years ago in an article smbd_unable_to_connect_to_cups_server, even if you have printing disabled in Samba, you can get errors in /var/log/messages like these±
May 5 09:45:02 www smbd[<pid>]: [2008/05/05 09:45:02, 0] printing/print_cups.c:cups_connect(69)
May 5 09:45:02 www smbd[<pid>]: Unable to connect to CUPS server localhost:631 - Connection refused
This happens even if you disable the printers and print$ shares from within YaST2.
He proposed a 5-line change in the /etc/samba/smb.conf, but testing this on openSUSE 12.x, shows the actual diff is a lot smaller: just change the entry for printcap name, then add an entry for disable spoolss.
This is the diff of /etc/samba/smb.conf.printing versus /etc/samba/smb.conf: Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2013/09/02
When installing samba on a “minimal” server openSUSE 12.x can give you a funny error that the install process conflicts with a “patterns-openSUSE-minimal_base-conflicts” package as for instance described in OpenSUSE 12.2 Samba Standalone Server With tdbsam Backend | HowtoForge – Linux Howtos and Tutorials.
The first time I got that message, I was confused, and it took me a while to find out about the meaning of the base-conflicts package, as it was hard to get a Google search query with really meaningful result.
At last I found a Gitorious entry describing the minimal_base-conflicts package:
create a separate minimal_base-conflicts pattern
this allows to keep the minimal_base pattern upon installing a conflicting package. A better solution would be weak-conflicts but we don’t have that atm
From there I found the security request openFATE – #312150: weak conflicts/softlocks/no-recommends for patterns:
Installation of a pattern also draws in packages that are not in the pattern but only recommended by those listed in the pattern. For the “minimal” pattern this behavior is not desirable though as one really wants a minimal installation without the optional stuff.
So basically, the minimal_base-conflicts package allows the minimal_base package to reference package without pulling in a truckload of package (that would basically violate the idea of a “minimal_base” install).
If you want to install one of the truckload (samba is one of them), then you need to uninstall the minimal_base-conflicts package.
–jeroen
via: OpenSUSE 12.2 Samba Standalone Server With tdbsam Backend | HowtoForge – Linux Howtos and Tutorials.
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »
Posted by jpluimers on 2013/08/30
When VMware Workstation/Player does an Easy Install of SUSE Linux (and most other Linuxes), it does this:
- mount a CD drive with the autoinst.iso image
- mount a floppy drive with the autoinst.flp image
For Linux, both of them contain autoinst.xml files to automate the boot process.
It has a few drawbacks including a hardcoded boot partition size and unmount problems, so if you don’t want those, follow the guidelines at How to Stop Easy Install in VMware Workstation.
–jeroen
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Virtualization, VMware, VMware Workstation | Leave a Comment »
Posted by jpluimers on 2013/08/26
PDF User Manual for Avira AntiVir Server | Unix and Avira AntiVir Professional | Unix.
It is not completely up to date (as most installations are now RPM based), but gives great background information.
If you are using SUSE Linux, then note that as of openSUSE 11.3, there is a glitch when you use the SUSE security repository (see Bug 633771 – antivir cannot be installed because of missing libdazuko.so).
Basically there are two solutions to this:
- Ignore the dependency issue;
- Use the Avira repository.
The former seems to be a viable solution as per PDF User Manual, the installation proceeds as follows:
linking /usr/lib/AntiVir/guard/libdazuko.so to /usr/lib/AntiVir/guard/
libdazuko3compat2.so...
And indeed it does: these are the steps to follow, first for adding the security repository, then to install the package (click on images to view larger versions): Read the rest of this entry »
Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »