Search Members Help

» Welcome Guest
[ Log In :: Register ]

Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic
 

[ Track this topic :: Email this topic :: Print this topic ]

reply to topic new topic new poll
Topic: Success story: DSL as rdesktop client, 100% working< Next Oldest | Next Newest >
2pac_Shaker Offline





Group: Members
Posts: 11
Joined: April 2005
Posted: May 05 2005,17:27 QUOTE

Hi there,

I'm going to share this story with the community, because I think it can be helpful for someone. A few weeks ago, I started a project about using a couple Windows 2000 servers and a few clients connected to them via remote desktop for a work center. For the servers, it was mandatory that they must be w2K servers, for several reasons not to be told here... but for the clients, no one has specified which OS they should be. Let's add the fact of the machines, much of them are Pentium II and even Pentiums, so they are slow even for windows NT. Here's when we started considering DSL.

First, we started with a normal DSL HDinstall. It worked great in much situations, but XVesa had some limitations for this kind of work. For instance, some of the windows apps at the server required Ctrl+Alt+Bckspc, others had problems with the € symbol, others with Num Lock, etc.. so I've started fixing things for DSL to work in this specific situation.

Here's the recipe on how to to have a fully working TS client with DSL:

- First of all, make a DSL HDinstall. No special requirements, just adjust the swapfile or the HD partitions to your personal preferences. Be sure to have at least a 300 MB free at the DSL partition. I did mine with 512 MB for /, 256 for swap and the rest of the disk partitioned and mounted apart for other stuff.

- Install the XFree86 DSL extension from control panel. Follow the instructions provided.

Now, there are two problems: one is to configure X without xsetup.sh, the other ones is to find a (reasonably) fast way to configure several machines at once without dealing with each one's particular properties. For this, I've created a XF86Config-4 file with the xf86config.dsl and modified to fit all the machines with zero-config.

Here's the file:

Code Sample

# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

   Load        "dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
   SubSection  "extmod"
     Option    "omit xfree86-dga"   # don't initialise the DGA extension
   EndSubSection

# This loads the Type1 and FreeType font modules
   Load        "type1"
   Load        "speedo"
#    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
   Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

   RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

#    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
   FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
   FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/freefont/"
   FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

   Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

   Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

   Identifier "Keyboard1"
   Driver "Keyboard"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

   Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option "Xleds"      "1 2 3"

   Option "LeftAlt"     "Meta"
   Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for XFree86
#    Option "XkbRules"    "xfree86"
#    Option "XkbModel"    "pc101"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

   Option "XkbRules" "xfree86"
   Option "XkbModel" "microsoft"
   Option "XkbLayout" "es"

EndSection

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

   Identifier "Mouse1"
   Driver "mouse"
   Option "Protocol"    "Auto"
   Option "Device"      "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate" "9600"
#    Option "SampleRate" "150"

# The following line is required for some wheel mices

   Option "ZaxisMapping" "4 5"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

   Option "ChordMiddle"

EndSection

# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

   Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

   HorizSync   31.5 - 57.0

#    HorizSync 30-64         # multisync
#    HorizSync 31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync 15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

   VertRefresh 40-150

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
   Identifier "Standard VGA"
   VendorName "Unknown"
   BoardName "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

   Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam 256

#    Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
   Identifier  "* Generic VESA compatible"
   Driver      "vesa"
   #VideoRam    16384
   # Insert Clocks lines here if appropriate
EndSection



# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.


Section "Screen"
   Identifier  "Screen1"
   Device      "* Generic VESA compatible"
   Monitor     "My Monitor"
   DefaultDepth 16

   Subsection "Display"
       Depth       16
       Modes       "1024x768"
       ViewPort    0 0
   EndSubsection
EndSection
Section "Screen"
   Identifier  "Screen2"
   Device      "* Generic VESA compatible"
   Monitor     "My Monitor"
   DefaultDepth 16

   Subsection "Display"
       Depth       8
       Modes       "1024x768"
       ViewPort    0 0
   EndSubsection
   Subsection "Display"
       Depth       16
       Modes       "1024x768"
       ViewPort    0 0
   EndSubsection
   Subsection "Display"
       Depth       24
       Modes       "1024x768"
       ViewPort    0 0
   EndSubsection
EndSection



# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
   Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

   Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

   InputDevice "Mouse1" "CorePointer"
   InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection


With this file, you have the following XFree working config:

- Standard Vesa video card at 1024x768, 16bit color depth
- it uses /dev/mouse, wich is detected at boot. It'll work both with PS/2 and COM mices and detect the protocol used.
- Mouse Wheel enabled, if present.
- Standard H/V sync for most monitors.
- Spanish Keyboard with € support (needless to say, but you should change it to your language ;) )

put this file in /etc/XF86Config-4 and change the content of /home/(username)/.xserverrc to this

Code Sample

exec /usr/X11R6/bin/XFree86 -nolisten tcp -screen Screen1 &>/dev/null


X should start with the configuration explained above. Make any changes to the file to adjust it to your personal needs.

Now, the problems of XVesa seem to be fixed. You can disable Ctrl+Alt+Bckspc or Ctrl+Alt+del to prevent X from being accidentally killed, you can disable Ctrl+Alt+F* to make the system more safer, Num Lock works fine.. but there is a new one. Seems like Alt Gr isn't working anymore, so you can not use @,#,€, or even \. After googleing a lot for this issue, I think I've found a solution... no so elegant, but it worked for me. The problem is that X is missing some files from *i'm-not-sure-what-is-it* named xkb

To fix it:

- Boot the machine with a Knoppix CD
- open a terminal
- mount your DSL partition
- locate the folder named xkb. In case you find more than one, get the one with a keycodes sub-folder inside.
- copy xkb with all of its contents to /etc/X11/ in your DSL mount point.
- Reboot the machine... the next time you startx, you should have Alt Gr working.

Now for a final retouch... most windows users use to lock their workstations with Ctrl+Alt+Del, specially when they are working in a common room and leave the seat. If you leave them without things like this, they start complaining about Linux and crying for a windows box. To fix this, just follow these three simple steps:

- install apt-get DSL extension
- from a terminal, type

Code Sample
apt-get install xlockmore


This will install xlock, an app which launches a random screensaver and asks for the user password to get the desktop back.

- add this line at the end of /home/(username)/.fluxbox/keys

Code Sample
Control Mod1 Delete :ExecCommand xlock -echokeys


This way, when the user presses Ctrl+Alt+Del it shows a nice screensaver and the computer is locked. Be sure to have the line

Code Sample
   Option "DontVTSwitch"    


uncommented in /etc/XF86Config-4 . Otherwise, the computer is locked but other users can open a new session with Ctrl+Alt+F*.




That's all. With this, you have a working terminal server client with some cool additional apps installed at the local machine. I wish all this information can be useful for someone who's trying to make a similar thing with DSL.

___

P.S: I would specially like to thank mikshaw for the xf86config script and to all the people who is sharing useful information in this forum... most of these problems have been solved by simply searching for the right keywords here.

DSL rules!  :cool:
Back to top
Profile PM 
Mazirian
Unregistered






Posted: May 05 2005,18:48 QUOTE

Unbeleivable!  You post this on the very day that I am setting up some old atticware pentium as a rdesktop client for my employer to use from his house.  What a coincidence!
Back to top
1 replies since May 05 2005,17:27 < Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

 
reply to topic new topic new poll
Quick Reply: Success story: DSL as rdesktop client

Do you wish to enable your signature for this post?
Do you wish to enable emoticons for this post?
Track this topic
View All Emoticons
View iB Code