|
Related YoLinux Tutorials:
°UNIX vs DOS commands
°Linux and DOS floppies
°Linux Networking
°Linux Sys Admin
°YoLinux Tutorials Index
|
| Prerequisite and Basic Configuration: |
Install Sun SDK (1.4): See Java SDK download/install
Web Browser Configuration: Mozilla
GNOME Desktop Proxy configuration: (required by Ximian Evolution below)
-
See YoLinux GNOME Desktop tutorial: Proxy configuration
| Mounting/Integrating with the Microsoft File Servers: |
Accessing MS/Windows file servers:
MS/Windows file shares are accessed using a MS/Windows login and
password thus I mount the file systems in user directories as they are
user resources. Check to see if the proper SAMBA packages are
installed: rpm -qa | grep samba. The packages samba-common, samba-client and samba should be installed.
Mount points: The local Linux system mount point choice and method
of access is actually important. If it is a multiuser system and the file server
is using user privileges to mount and access the file then it might be prudent
to use a mount point local to the user.
If the system is owned and used solely by the user then I recommend creating a
directory in /mnt and using it as a mount point. In either case
a soft link (ln -s) to the $HOME/.gnome-desktop/ (RH 7-9) directory will
create a nice user interface icon for access purposes.
(Fedora Core 3: Use the directory $HOME/Desktop/)
[Potential Pitfall]: The mount point to the user's home directory MUST be recognized
by the admin as a potential pitfall. When removing a user from the system,
the command "userdel -r" will recursively delete files and directories
found below the home directory. The command "rm -R" will NOT follow sym
links thus sym links to $HOME/.gnome-desktop/ are safe. The directories
mounted to directories below the $HOME/ path may not be safe from mass deletion.
Create the desktop mount point which will provide a desktop icon and
app link to the Nautilus file manager to view files on the server:
- System mount point: /mnt/
[root]# mkdir $HOME/.gnome-desktop/MS-SERVER-NAME
[root]# mkdir /mnt/MS-SERVER-NAME
[root]# mkdir /mnt/MS-SERVER-NAME/MS-Windows-Share
[root]# ln -s /mnt/MS-SERVER-NAME/MS-Windows-Share $HOME/.gnome-desktop/MS-SERVER-NAME
Note Fedora Core 3: $HOME/Desktop/
or
- User mount point: $HOME/
[root]# mkdir $HOME/.gnome-desktop/MS-SERVER-NAME
[root]# mkdir $HOME/MS-SERVER-NAME
[root]# mkdir $HOME/MS-SERVER-NAME/MS-Windows-Share
[root]# ln -s $HOME/MS-SERVER-NAME/MS-Windows-Share $HOME/.gnome-desktop/MS-SERVER-NAME
See "Potential Pitfall" above before using your home directory as a mount point!!
Use one of the following methods: (I prefer method 1)
- Directly and upon system boot, mount MS/Windows file server:
Create file ~/.smbpassword (chmod 400 $HOME/.smbpassword)
-
username = ms-windows-login-name
password = ****
|
Edit file: /etc/fstab
(you need to be root to edit this file.)
and add the following line: (one line. May be shown here as word-wrapped)
-
|
//MS-SERVER-NAME/MS-Windows-Share /mnt/MS-SERVER-NAME/MS-Windows-Share smbfs credentials=/home/linux-user-id/.smbpassword,workgroup=MS-WINDOWS-DOMAIN,uid=linux-user-id,gid=linux-user-group-name 0 0
|
Mount: [root]# mount /mnt/MS-SERVER-NAME/MS-Windows-Share
Unmount: [root]# umount /mnt/MS-SERVER-NAME/MS-Windows-Share
Note: If the uid and gid are omitted you may only have
read access to the MS/Windows server. The uid/gid may be the
alphanumeric name or the system user/group numbers.
- Directly mount MS/Windows file server: (as root) (one line - may be shown wordwrapped)
-
[root]# mount -t smbfs -o username=ms-windows-user-id,workgroup=MS-WINDOWS-DOMAIN,uid=linux-user-id,gid=linux-user-group-name //MS-SERVER-NAME/MS-Windows-Share /mnt/MS-SERVER-NAME/MS-Windows-Share
password:
[root]# umount /mnt/MS-SERVER-NAME/MS-Windows-Share
- Use Samba smbmount: (as root) (one line - may be shown wordwrapped)
-
[root]#smbmount //MS-SERVER-NAME/MS-Windows-Share /mnt/MS-SERVER-NAME/MS-Windows-Share -o username=ms-windows-login-name,workgroup=MS-WINDOWS-DOMAIN
Password:
[root]#smbumount /mnt/MS-SERVER-NAME/MS-Windows-Share
- Use Samba shell: (non-root user)
smbclient //MS-SERVER-NAME/MS-Windows-Share -U MS-WINDOWS-DOMAIN/ms-windows-login-name
Password:
This places you in a shell mounted to the MS/Windows server.
You can enter commands such as ls, put and get like in an ftp client.
Type ? for a full list of commands.
- LinNeighborhood: Linux workstation gui tool.
Make your life simple and use the GUI/File Manager LinNeighborhood.
It uses smbmount, samba and smbclient to give you access to MS/Windows servers
and printers.
Uses GTK+ Libraries.
Note: If the share is a hidden share append a "$" to the name of the share.
i.e.: //MS-SERVER-NAME/MS-Windows-Share$
[Potential Pitfall]: If the Microsoft login password is changed, unmount the drive, change the $HOME/.smbpasswd password entry and remount the drive.
GUI Mount/Configuration Tools:
| List and Browse MS/Windows Shares: |
| Mounting a MS/Windows NTFS or DOS Hard Drive: |
This procedure is common for dual boot systems and for those who wish to
access legacy data. The NTFS file system is used with MS/Windows NT, 2000 and XP.
Read only access is available with the NTFS kernel module. The default Red Hat compiled kernels support these NTFS modules.
If compiling from source be sure to set the following in kernel-XXXXX.config: CONFIG_NTFS_FS=m (read-only NTFS support. Write support is at your own risk: CONFIG_NTFS_RW=y)
- Linux NTFS Home page
- Download the appropriate kernel module RPM (compiled binaries): Fedora Core and Red Hat NTFS kernel module RPMs - info help and instructions
The compiled RPM kernel modules are Linux kernel specific and processor specific.
The find the version of the kernel you are running, use the command: uname -r -p
or cat /proc/version.
Determine the target processor with the command uname -p
- Install rpm as root: rpm -ivh kernel-ntfs-2.4.XXX.iX86.rpm
- Load module: /sbin/modprobe ntfs
- Check for errors: dmesg | grep NTFS
- Verify: cat /proc/filesystems
- Create mount point: mkdir /mnt/windows
- Add line to /etc/fstab:
-
/dev/hda1 /mnt/windows ntfs ro,umask=0222,uid=Linux-Login-ID 0 0
|
- Uid is the Linux user login id which is allowed exclusive access to
MS/Windows drive. Remove this to allow all system users access to the drive.
- Device reflects that of the MS/Windows hard drive. First SCSI drive
would be /dev/sda1. See YoLinux SCSI tutorial for more info.
- mount /mnt/windows
or
mount -t ntfs -o nls=utf8 /dev/hdXX /mnt/windows
Note: DOS and MS/Windows 3.1, 95, 98 or 2000ME can be mounted for read/write
using file system types, msdos, umsdos, vfat with no additional kernel
module installation required. (NTFS requires extra module) Example for MS/Windows 95:
/dev/hda1 /mnt/win95 vfat defaults 0 0
For more information see the man pages for:
modprobe,
dmesg,
mount,
umount,
fstab,
dump and
fs.
| Interfacing with the Microsoft Exchange Mail Servers: |
Email, Calendar, Outlook and Microsoft Exchange: Use (1) MS/Outlook
on Linux, (2) MS/OWA webmail or (3) Linux Outlook clone, Ximian
- Run MS/Outlook on Linux:
Run the Codeweavers Crossover commercial version of Wine and run Microsoft
Outlook on Linux. See the YoLinux Tutorial on Installing Crossover and Outlook.
- MS/Exchange OWA webmail:
Use your browser: http://webmail.megacorp.com (Company specific)
Note: Java JVM must be installed and browser JVM support must be
configured as described above to enable full appointment calendar
functionality.
- Microsoft Exchange Access with Ximian Evolution email client and Ximian Connector: - Novell CONNECTOR REQUIRES EXCHANGE SERVER 2000! It does not work with MS/Exchange 5.5.
Install Instructions: http://www.novell.com/products/connector/
Red Hat Linux 8.0 comes with the Novell/Ximian/Evolution version 1.0
email client. The Novel MS/Exchange connector requires Evolution
version 1.2.
- Download Novell Red-Carpet, Novell/Ximian Evolution 1.2 and Novell/Ximian Connector:
- Red Carpet:
- Download Ximian Evolution 1.2 and Ximian Connector:
- Run: /usr/bin/red-carpet
- Configure HTTP Proxy if required.
- You will be presented with packages to update. Select "Update Now".
- Choose "Unsubscribed Channels"
- Select "Ximian Connector" + "Subscribe" button (lower right)
+ "Install" icon (upper right) + select the "check" box.
This will install the connector and update Ximian Evolution (V1.2).
- Select "OK" + "File" + "Exit".
- Install License:
- File: connector-key.txt
Place in directory: /home/user-dir/evolution/
- Ximian Evolution Configuration:
- Start Ximian Evolution email client: (Select envelope icon on the Linux desktop tool bar.)
- Select "Tool" + "Setting"
- Select the "Mail Accounts" icon (left hand panel) + "Add" button on right.
- Exchange OWA server: webmail.megacorp.com
Ximian Connector Notes:
- Uses webdav protocol to a OWA (Outlook Web Access) server to support email, address book and calendar functions.
- Ximian connector requires MS/Exchange server 2000 or better.
- KDE KMail and appointment calendar:
Use KDE KMail and appointment calendar which interface with MS/Exchange 2000 using webdav interface.
- OMC: Open Message and Collaboration - MS/Exchange 5.5+ connector and Brutus development MAPI to CORBA framework.
Lotus Notes:
On 07/10/2006, IBM announced Lotus Notes client for Linux.
Installation: Notes 7.0.1 client on Red Hat Enterprise 4/CentOS 4
- IBM customers can download the licensed C93D1NA.zip from the IBM "Partnerworld program", "Passport Advantage" to a working directory. i.e. Lotus7.0.1
- Perform this step as root - create target install directory: mkdir /opt/IBM/Workplace Managed Client
chmod +w /opt/IBM/Workplace Managed Client
- Uncompress: unzip C93D1NA.zip
Results in Personality.zip, readme.pdf, setuplinux.bin
- Uncompress: unzip Personality.zip
- Set permissions: chmod +x setup_wct_platform.bin setuplinux.bin
- cp setuplinux.bin updateSite/features/com.ibm.workplace.notesinstall.linux.feature_7.0.1.0000-0900/bin/linux/
- Run install program: ./setup_wct_platform.bin
- Accept license and specify target directory: /opt/IBM/Workplace Managed Client (default)
- Select "Finish"
Lotus Notes client start script:
-
#!/bin/bash
NOTESBIN=~/notes NOTESDATA=~/notes/data NOTESDIR=~/notes/data LD_LIBRARY_PATH=$NOTESBIN:$NOTESBIN/jvm/bin/classic:$NOTESBIN/jvm/bin:$LD_LIBRARY_PATH PATH=$NOTESBIN/jvm/bin:$NOTESBIN:$PATH CLASSPATH=./:$NOTESBIN/:$CLASSPATH export NOTESBIN NOTESDATA NOTESDIR LD_LIBRARY_PATH PATH CLASSPATH
# Command to start Lotus Notes: /opt/IBM/Workplace\ Managed\ Client/rcp/richclient \ -personality com.ibm.workplace.noteswc.standalone.linux.personality
|
Lotus Notes 7 documentation
SuSE users see SLED 10 patch
Lotus Sametime:
"Meanwhile" is an IBM/Lotus Sametime plugin which is available for the Linux IM client Gaim.
Use the following RPM packages:
Connect with the user id (LDAP format): CN=Joe R Blow/OU=US/O=MegaCorp and regular Sametime password.
Links:
Accessing The Local Microsoft Printer Network:
Configuring the lpr print command: (lprNG)
- As root run the GUI configuration tool command: /usr/bin/redhat-config-printer (RH 8.0+)
- Select the "New" icon + "Next".
- Give it a Queue name. (Make up your own name.)
Select "Windows Printer".
Select "Forward".
- Enter Ms/Windows info: (This example is for a Windows network printer.)
Share: \\MS-SERVER-NAME\MS-Windows-Print-Share
Host IP: XXX.XXX.XXX.XXX
Workgroup: WORKGROUP-NAME
User: Your MS/Windows login name
Password: Your MS/Windows password
- Select a driver: If it is not listed, pick the closest you
can find. Typically there will be an emulation mode for ljet4 or some
other popular mode.
- Select "Apply"
- Select "File" + "Save Changes".
- Select "File" + "Quit".
Find the "Host IP" address with the command:
When multiple printers have been defined, use this gui to select the
default.
the command "lpr file-name" will use the default printer.
Use the "-P queue-name" flag to specify a non-default
printer.
When sending print jobs directly to an HP network printer (instead of through
a MS/Windows print server), configure the queue to use TCP/IP port 9100.
The default Mozilla printer device specification: lpr
${MOZ_PRINTER_NAME:+'-P'}${MOZ_PRINTER_NAME} will print to the default
unless modified.
Printing uses the following configuration files:
- /etc/printcap - lpr config file (Generated by GUI. You don't
need to understand it.)
or $HOME/.printcap
-
joeshp:\ :ml#0:\ :mx#0:\ :sd=/var/spool/lpd/joeshp:\ :af=/var/spool/lpd/joeshp/joeshp.acct:\ :sh:\ :lp=|/usr/share/printconf/util/smbprint:\ :lpd_bounce=true:\ :if=/usr/share/printconf/util/mf_wrapper:
|
- /etc/printcap.local
- /usr/share/printconf/util/smbprint - Red Hat 8.0/9.0 shell script
Man pages:
Links:
Create a script to print:
- Use smbclient shell:
smbclient //MS-PRINT-SERVER/printer-share -U MS-WINDOWS-DOMAIN/ms-windows-login-name
Use the command: smb: \> print file-name
- Command line: smbclient //MS-PRINT-SERVER/printer-share
windows-login-password -N -U ms-windows-login-name -W MS-WINDOWS-DOMAIN -c "print
file-to-print.ps"
- Shell script to print a PostScript or printer ready file:
$HOME/bin/print
-
#!/bin/sh /usr/bin/smbclient //MS-PRINT-SERVER/printer-share windows-login-password \ -N \ -U ms-windows-login-name \ -W MS-WINDOWS-DOMAIN \ -c "print $1" echo "Printing file $1"
|
- Shell script to print a text file: $HOME/bin/printTXT
-
#!/bin/bash BASENAME=`/bin/basename $1` /usr/bin/enscript -o /tmp/$BASENAME.ps $1 /usr/bin/smbclient //MS-PRINT-SERVER/printer-share windows-login-password \ -N \ -U ms-windows-login-name \ -W MS-WINDOWS-DOMAIN \ -c "print /tmp/$BASENAME.ps" echo "Printing file $1"
|
Links:
| Granting MS/Windows users GUI access to your system: |
Granting X-Window access to your PC using Cygwin (or ReflectionX, HummingBird Exceed):
- Edit file:
- Red Hat: /etc/X11/xdm/Xaccess
- Suse: /usr/X11R6/lib/X11/xdm/Xaccess
Change from:
-
# * #any host can get a login window
|
To:
-
* #any host can get a login window
|
- Edit file: /etc/X11/xdm/xdm-config
Change last line from:
-
!DisplayManager.requestPort: 0
|
To:
-
DisplayManager.requestPort: 0
|
System default for RHEL4/FC3.
- Edit file:
- Red Hat Enterprise 3/4, CentOS 3/4, Fedora 1-6: /etc/X11/gdm/gdm.conf
- Red Hat Enterprise 5, CentOS 5: /etc/gdm/custom.conf
Change last line from:
-
To:
-
One can also use the GUI config tool gdmsetup.
- Restart X-Windows:
- [root]# init 3
- [root]# init 5
Note:
- You can use the config tool /usr/bin/gdmsetup to configure GDM.
- You can test the GDM login screen locally: X -query localhost :1
Using Cygwin on your PC to connect to full Linux GUI desktop:
- Download XFree86 for MS/Windows and install.
Be sure to select the "loop" graphic to change from "Default" to "Install"
to install all packages. The default is to exclude the X-window server.
Packages to install may be selected individually.
- Start Cygwin: Windows 2000 menu: "Start" + "Programs" + "Cygwin" + "Cygwin Bash Shell"
- Start MS/Windows X-Server:
- xwin -query Ip-address-of-Unix-computer
Used to display Linux desktop on MS/Windows PC.
- xwin -multiplemonitors -scrollbars -indirect Ip-address-of-Unix-computer
Used to display Linux desktop on MS/Windows with multiple monitors.
- xwin -ac -multiwindow Ip-address-of-Unix-computer
Starts X server but does not generate a desktop window. Each Linux
application will create its' own window. In a shell set your display
environment to the IP address of your PC and individual applications
will be displayed to your MS/Windows desktop.
In cygwin remote ssh or telnet shell: export DISPLAY=ip-of-local-pc:0.0
The local IP address can be obtained on MS/Windows through the DOS command: IPCONFIG
- [Potential Pitfall]:
If your Cygwin bash shell command
line prompt is "i have no name" then it is because your uid in the
file /etc/passwd is too large. It must be less than the 16 bit limit
of 65536. The uid is the third field demarked by the colon (":").
Change the uid to an integer value less than 65536. This will also fix
X/Server problems which arise when trying to connect to other computers using X.
Open Source MS/Windows PC X-Windows server software:
Commercial MS/Windows PC X-Windows server software:
| Granting remote shell access (telnet) and file transfer (ftp) access: |
To turn on telnet and ftp access, edit the files /etc/xinetd.d/telnet and
/etc/xinetd.d/ftp and change the line:
-
to:
-
Restart xinetd: service xinetd restart (or: /etc/init.d/xinetd restart)
Man pages:
Also see YoLinux.com: Xinetd services configuration
| Connecting to a Microsoft Windows Terminal Server (NT, 2000 or XP) using RDP: |
One may graphically connect to a Microsoft Windows Terminal NT Server,
server 2000 or a Microsoft Windows XP system (Professional and Home edition)
with a Microsoft Windows Terminal RDP (Remote Desktop Protocol) client for
Linux known as "rdesktop". Use version 1.2 or later (which comes with Red Hat
9.0). Version 1.1 which ships with Red Hat Linux 8.0 is buggy.
Note that Microsoft Windows XP uses RDP 5.2 (an extension to
the ITU-T T.128 application sharing protocol) using 24 bit color and
supports sound. The older RDP 4.0 only supported 8 bit color and did
not support sound.
If there is an active rdesktop session, MS/Windows XP will not allow
one to login at the console. You will get an error message
which states that the system is locked. Only one active MS/Windows desktop
is allowed. MS/Windows terminal server is required for more than one
simultaneous user login.
Use:
- Red Hat 9.0: Install RPM: rpm -ivh rdesktop-1.2.0-1.i386.rpm
Red Hat 8.0 or other distributions of Linux: Download source, untar, configure, make, make install.
- Configure MS/Windows XP to allow remote connections:
- Right click "My Computer" desktop icon.
- Select "Properties".
- Select "Remote" tab
Check "Remote Desktop": "Allow users to connect remotely to this computer".
OK
-
- Launch Linux desktop client:
rdesktop -u windows-user-id -p windows-password -g 1200x950 ms-windows-terminal-server-host-name
or
rdesktop -u windows-user-id -g 1240x992 ms-windows-terminal-server-host-name
| option |
Description |
| -a |
Color depth: 8, 16, 24 |
| -r |
Device redirection. i.e. Redirect sound on remote machine to local device.
i.e. -0 -r sound (MS/Windows 2003) |
| -g |
Geometry: widthxheight or 70% screen percentage. |
| -p |
Use -p - to receive password prompt. |
| -d |
Use -d - to specify a domain. No space is allowed between the "-d" and the domain name (V1.3.1). |
Note: I can also connect to my dual monitor MS/Windows
system from my dual monitor Linux system and display the full two
monitors. I use the following geometry directive: -g 2540x992
Links:
| Integrating with Citrix Winframe NT Application Servers: |
Citrix Winframe ICA Client for Linux:
(ICA: Independent Computing Architecture)
- Download: http://www.citrix.com/site/SS/downloads/index.asp
- Select "Clients" link from left hand side of page.
- Select "Citrix ICA Clients" - "Linux"
- Select English ".rpm" - "Version Details"
- Download:
- As root Install: [root]# rpm -ivh ICAClient-8.0-1.i386.rpm
- Run/Configure (as user) ICA Client Manager: /usr/lib/ICAClient/wfcmgr
Note: This tool allows full capabilities to configure and run the ICA Citrix winframe client.
- Select "Options" + "Settings..." [screenshot]
- Select from pull-down menu: "Server Locations"
- Network Protocol: TCP/IP
- Server Group: Primary
- Address List: (Auto-Locate)
- Select "Entry" + "New..."
- Select (default option showing: Network) radio button "Published Application"
- Select button to the right "...".
- Select "Citrix-App"
- Test Application:
- Select the "Lightning Bolt" icon to connect.
- This will bring up the Microsoft NT server login dialog box.
- User name: NT-Login-Name
- Password: NT-Password
- Domain: MS-WINDOWS-DOMAIN
- As a Linux user, run Citrix ICA Client only: First Citrix Application
This will bring up the specified ICA application
where the "description" is defined in $HOME/.ICAClient/appsrv.ini section heading. i.e. "Citrix-App"
You can also create a desktop launcher icon: right click on a free area of the desktop and select "New Launcher". Use icon /usr/lib/ICAClient/icons/citrix48.xpm
Application Command: /usr/lib/ICAClient/wfica -desc "Citrix-App" -username NT-Login-Name -password NT-Password -domain MS-WINDOWS-DOMAIN
- ICA Client: Second, Third,... Citrix Application
- Configure:
- Start ICA manager: /usr/lib/ICAClient/wfcmgr
- Select "New" Icon (or "Entry" + "New")
- Network:
- Network Protocol: TCP/IP
- Server Location: MS-NT-CITRIX-SERVER
- Select "Server" radio button
- Description: Application/Server Description
- Server: MS-NT-CITRIX-SERVER
- Login:
- Username: ms-windows-login-name
- Domain: MS-WINDOWS-DOMAIN
- Password:
- Select "Apply"
- Run Application:
- Launch command: # /usr/lib/ICAClient/wfica -desc "Application/Server Description" -username ms-windows-login-name -password your-password-goes-here -domain MS-WINDOWS-DOMAIN
Other password options:
- Option "-clearpassword" may need to be used instead.
- The password may also be held in the Citrix configuration.
Set the configuration with /usr/lib/ICAClient/wfcmgr
and select "Connection" + "Properties" + "login" to store the password.
- Use icon /usr/lib/ICAClient/icons/citrix48.xpm
- Links:
- FYI:
- Help: wfica -h
- If running programs where you have to share files with the Citrix Metaframe server, use SAMBA to export a MS/Windows NT share.
- ICA client product number for Linux client: 81/7
- Config files:
- $HOME/.ICAClient/*.ini
- /usr/lib/ICAClient/config/*.ini (not used)
- /usr/lib/ICAClient/.config/*.ini (not used)
- Launching from a browser: (Using ICA Citrix plug-in)
- Mime type: application/x-ica
- Application: /usr/lib/ICAClient/wfica -file %s
Where "%s" refers to the ".ica" file being passed.
- File: .mailcap: application/x-ica; /usr/lib/ICAClient/wfica -file %s; x-mozilla-flags=plugin:Citrix ICA
- Graphics capture utility: /usr/lib/ICAClient/util/xcapture
Select window (middle mouse button), select region (corner to corner
drag with left mouse button) or cancel (right mouse button).
- Uninstall: (rpm -e) Manually delete cache: /usr/lib/ICAClient/cache/
ICA Links
| Send/Receive a "WinPopup" Message: |
Send a WinPopup Message:
MS/Windows can send a message to another MS/Windows PC which will pop-up
(using "WinPopup" protocol) and
appear in a dialog box. This is used by admins for notification purposes.
The DOS command is:
NET SEND NetBIOS-computer-name "Message to send to user"
Linux can send the same message to a MS/Windows PC using the command:
[prompt]$ smbclient -M NetBIOS-computer-name Message to send to user
ctrl-d
Notes:
- Message limit is 1600 bytes.
- Alternate method: cat mymessage.txt | smbclient -M NetBIOS-computer-name
Receive a WinPopup Message:
To handle incoming " WinPopup" messages on Linux, set the "message command" parameter in the smb.conf.
message command = csh -c 'xedit %s;rm %s' &
This will use the application "xedit" to display the message.
The message is then removed.
- %s : The filename containing the message.
- %t : Message destination (computer or server to which it was sent.)
- %f : Message sender.
Default smb.conf config file is no message command.
Notes:
Also see LinPopUp available from LittleIgloo.org.
| Authenticating Linux with Microsoft Active Directory: |
This requires that the Microsoft Active Directory server have
its schema enhanced to support Unix/Linux systems, specifically the uid
and gid which are numerical representations of the user and group id.
This requires installing Microsoft's Unix services for Windows:
Info and download
On the Linux system it requires adding the following /etc/ldap.conf
file which defines the translation between native Linux LDAP attribute names and those used by Microsoft Active Directory:
-
host XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX base dc=megacorp,dc=com
binddn cn=SysAdmin,dc=megacorp,dc=com
bindpw bindPassword
scope sub
ssl no
nss_base_passwd ou=accounts,dc=megacorp,dc=com nss_base_shadow ou=accounts,dc=megacorp,dc=com nss_base_group ou=accounts,dc=megacorp,dc=com
nss_map_objectclass posixAccount user nss_map_objectclass shadowAccount user nss_map_objectclass posixGroup Group
nss_map_attribute uid sAMAccountName nss_map_attribute uidNumber msSFU30UidNumber nss_map_attribute gidNumber msSFU30GidNumber nss_map_attribute loginShell msSFU30LoginShell nss_map_attribute gecos name nss_map_attribute userPassword msSFU30Password nss_map_attribute homeDirectory msSFU30HomeDirectory nss_map_attribute uniqueMember msSFU30PosixMember nss_map_attribute cn cn
nss_login_attribute sAMAccountName pam_member_attribute msSFU30PosixMember
|
Note:
- The "host" statement lists the primary and failover AD servers.
The file /etc/pam.d/system_auth can be configured with the console tool /usr/bin/authconfig or the GUI configuration tool /usr/bin/system-config-authentication.
See the YoLinux LDAP authentication tutorial
Edit /etc/nsswitch.conf so that Linux will authenticate to the Active Directory server using LDAP.
-
.. ... passwd files ldap shadow files ldap group files ldap ... ..
|
This is the simplest authentication configuration. The
prefered configuration will include Kerberos and SSL. (not covered here
- yet)
Microsoft's Unix services for Windows also supports the use of Active
directory as an NIS server although the LDAP configuration is more
current and when used with SSL and Kerberos, it is also more secure.
Books: |
-
 |
"Linux in a Windows World"
by Roderick W. Smith
ISBN #0596007582, Oreilly
|
|
|