cvs commit: hints svnc-x_terminal.txt

timothy at linuxfromscratch.org timothy at linuxfromscratch.org
Wed May 7 09:42:34 PDT 2003


timothy     03/05/07 12:42:34

  Modified:    .        svnc-x_terminal.txt
  Log:
  Removed gpm instructions. Changes to svgalib and several descriptions.
  
  Revision  Changes    Path
  1.2       +83 -90    hints/svnc-x_terminal.txt
  
  Index: svnc-x_terminal.txt
  ===================================================================
  RCS file: /home/cvsroot/hints/svnc-x_terminal.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- svnc-x_terminal.txt	13 Apr 2003 02:14:26 -0000	1.1
  +++ svnc-x_terminal.txt	7 May 2003 16:42:33 -0000	1.2
  @@ -8,7 +8,7 @@
   	low-end computers to X terminals. We also describe a possible
   	minimalistic server + client (X terminal) configuration.
   
  -VERSION:	0.1
  +VERSION:	0.1.1
   
   CONTENTS
   
  @@ -16,9 +16,8 @@
    What do we need?
   Completing the bootfloppy
    Installing more of uClibc
  - Installing gpm
    Installing svgalib
  - Installing the svncviewer
  + Installing svncviewer
    Creating the bootdisk
   Setting up the network environment
    Setting up general server programs
  @@ -32,6 +31,14 @@
   
   PREFACE
   
  +* For the most recent version check out 
  +
  +http://www.renyi.hu/~ekho/lowlife/svnc-x_terminal.txt
  +
  +* See changelog at 
  +
  +http://www.renyi.hu/~ekho/lowlife/Changelog
  +
   * Comments, ideas, critics, flames are welcome.
   
   * (If you are an LFS user, you can skip this.) Although this document is
  @@ -59,18 +66,18 @@
   2) How to make them silent?
   
   Concerning 2), the possible sources of noise are fans and HD. In case
  -of old PC (486s and old Pentiums) the CPU needs no fan -- if there is
  -any fan, you can find it at the power supply, and it's not a big risk
  -to plug that out. This is where oldness becomes a feature. To make
  -the HD quiet, you should not use it. An alternative is using a
  -ramdisk to carry your root filesystem. The most easy way to make the
  -kernel mount a ramdisk as root filesystem is booting from a floppy.
  -This is why I use a bootfloppy.
  -
  -This design implies that we will be tight on memory on an old PC. One
  -kind of reaction to this circumstance is trying to trim down X for the
  -floppy. I chose an other way, namely, displaying X via vnc: we put
  -svgalib + the svga vncviewer on the floppy.
  +of old PC's (486s and old Pentiums) the CPU needs no fan -- if there
  +is any fan, you can find it at the power supply, and it's not a big
  +risk to plug that out. This is where oldness becomes a feature.
  +Concerning the HD: to make the it quiet, you should avoid using it.
  +An alternative is using a ramdisk for carrying your root filesystem.
  +The most easy way to make the kernel mount a ramdisk as root
  +filesystem is booting from a floppy. This is why I use a bootfloppy.
  +
  +This design implies that in case of an old PC, we will be tight on
  +memory. One kind of reaction to this circumstance is trying to trim
  +down X for the floppy. I chose an other way, namely, displaying X via
  +vnc: we put svgalib + the svga vncviewer to the floppy.
   
   This hint is a continuation of the uclibc-bootfloppy hint (
   
  @@ -89,23 +96,21 @@
   decreased by using older stuff; why do I insist on being at the
   bleeding edge? See the answer in the uclibc-bootfloppy hint.
   
  -This hint,additional info and downloadable bootdisk image with svnc can be found
  -at my homepage:
  +This hint,additional info and downloadable bootdisk image with svnc
  +can be found at my homepage (or at its mirror):
   
   http://www.renyi.hu/~ekho/lowlife/
  -
  -(However, the less downloads of the image the happier I'm as it is
  -LFS... ;)
  -
  -and I mirror it at
  -
   http://www.personal.ceu.hu/students/01/Csaba_Henk/lowlife/
   
  -In this hint the assumption of using an x86 PC (both for making and booting
  -the floppy) and gcc is set. You may try to port it to another architecture /
  -compiler. Doing it on another architecture should not be hard. Doing it with
  -another compiler depends on how well does uClibc can cooperate with that
  -compiler.
  +In this hint we the assume that you use an x86 PC (both for making and
  +booting the floppy) with gcc. You may try to port it to another
  +architecture / compiler. Doing it on another architecture should not
  +be hard. Doing it with another compiler depends on how much does
  +uClibc support that compiler.
  +
  +If you copy command from this hint to your shell, be careful
  +that line-terminating backslashes (\) will keep their position (no
  +whitespace characters should follow them).
   
   What do we need?
   ----------------
  @@ -115,7 +120,7 @@
   described in the sequel.
   
   Generally you are encouraged to use the most update versions of the
  -programs (and your favorite distributions, if there are more of it).
  +programs (and your favorite distributions, if there are more of them).
   Still there are some items where I have some additional comment on the
   version/distribution; these are marked with (!). You can find the
   version notes at the end of this hint. 
  @@ -158,26 +163,12 @@
   Installing more of uClibc
   -------------------------
   
  -For gpm and svgalib we need the math libraries of uClibc. So do the
  -following:
  +For svgalib we need the math libraries of uClibc. If you installed gpm         
  +to the floppy filesystem correctly, you already have them. If you don't        
  +have them on the floppy filesystem, type:
   
   cd /usr/i386-linux-uclibc/lib/ &&
  -cp -a libm-* libm.so.0 ~/loop/lib
  -
  -Installing gpm
  ---------------
  -
  -Install gpm by running the following commands:
  -
  -export LDFLAGS="-lm" &&
  -./configure &&
  -make &&
  -strip src/gpm &&
  -mkdir -p $HOME/loop/{usr/sbin,var/run}
  -cp src/gpm $HOME/loop/usr/sbin &&
  -unset LDFLAGS
  -
  -[The /var/run directory is needed for gpm at runtime.]
  +cp -a libm-* libm.so.0 ~/rfloppy/lib
   
   Installing svgalib
   ------------------
  @@ -206,7 +197,9 @@
   your needs. By carefully choosing the few drivers you need, you can
   decrease the size of the binary with about 100 kb or maybe more! However, 
   our filesystem is big enough for the svga library with all default drivers
  -compiled in. 
  +compiled in. If the kernel release you use for the bootfloppy is not the
  +same as the one used on your development platform, also set the
  +KERNELRELEASE, INCLUDEDIR variables according to this.
   
   Then run 
   
  @@ -224,21 +217,21 @@
   
   cd kernel/svgalib_helper &&
   make all &&
  -cp svgalib_helper.o $HOME/loop/lib/modules &&
  -cd ../../sharedlibs &&
  +cp svgalib_helper.o $HOME/rfloppy/lib/modules &&
  +cd ../../sharedlib &&
   for q in "" gl; do 
   strip libvga$q.so.1.9.*
   ln -s libvga$q.so.1.9.* libvga$q.so.1 
   ln -s libvga$q.so.1 libvga$q.so
   done &&
  -mkdir -p $HOME/loop/usr/lib && 
  -cp -a libvga* $HOME/loop/usr/lib
  +mkdir -p $HOME/rfloppy/usr/lib && 
  +cp -a libvga* $HOME/rfloppy/usr/lib
   
  -Also create the file $HOME/loop/etc/vga/libvga.config, and put into it
  +Also create the file $HOME/rfloppy/etc/vga/libvga.config, and put into it
   your mouse type at least. Eg., my libvga.config looks like:
   
  -mouse Microsoft 
  -mdev /dev/tts/0
  +mouse IMPS2
  +mdev /dev/misc/psaux
   
   We will need the svgalib libraries to link against them. For this aim,
   we put them to a place where the linker will find them. Now we need to 
  @@ -265,7 +258,7 @@
   in the svgalib source directory. You will find the executables in the
   demos and threeDKit directories.  
   
  -Installing the svncviewer
  +Installing svncviewer
   -------------------------
   
   To get svncviewer compiled, we need the libvncauth.a library form the
  @@ -274,7 +267,7 @@
   running make. 
   
   However, xmkmf will not work with uClibc (unless we build X against
  -uClibc, which we don't want to do). Therefore we do the following:
  +uClibc, and we don't want to do that). Therefore we do the following:
   
   * run xmkmf using glibc on both of libvncauth and svncviewer;
   
  @@ -304,14 +297,14 @@
   cd ../svncviewer &&
   make &&
   strip svncviewer &&
  -mkdir -p $HOME/loop/usr/bin &&
  -cp svncviewer $HOME/loop/usr/bin
  +mkdir -p $HOME/rfloppy/usr/bin &&
  +cp svncviewer $HOME/rfloppy/usr/bin
   
  -If you happen to do this compilation in an environment without X (ie.,
  -you don't have xmkmf), then try to compile libvncauth.a and svncviewer with the
  -help of the following scripts (they are simply the output of the
  -respective make commands; I give away these and not the Makefiles
  -because xmkmf-made Makefiles are huge and illegible):
  +If you intend to compile svncviewer in an environment without X (ie.,
  +you don't have xmkmf), then try to compile libvncauth.a and
  +svncviewer with the help of the following scripts (they are simply
  +the output of the respective make commands; I give away these and not
  +the Makefiles because xmkmf-made Makefiles are huge and illegible):
   
   http://www.renyi.hu/~ekho/lowlife/make_uclibc-libvncauth 
   http://www.renyi.hu/~ekho/lowlife/make_uclibc-svncviewer 
  @@ -319,7 +312,8 @@
   Creating the bootdisk
   ---------------------
   
  -Proceed on as it is described in the uclibc-bootdisk hint.
  +Proceed on as it is described in the similarly named chapter of the
  +uclibc-bootdisk hint.
   
   
   Setting up the network environment
  @@ -353,9 +347,9 @@
   $SERVER=192.168.0.2
   $CLIENT=192.168.0.1
   
  -Then you should install xinetd (or alternatively, inetd), some telnet
  -daemon, and some tftp daemon. These are covered by the BLFS book
  -(available at
  +(its an example and not a command!). Then you should install xinetd
  +(or alternatively, inetd), some telnet daemon, and some tftp daemon.
  +These are covered by the BLFS book (available at
   
   http://beyond.linuxfromscratch.org
   
  @@ -365,7 +359,8 @@
   list of those users/groups which can write to $TRANSFER.
   
   Configure xinetd to run telnetd and tftpd bound to $SERVER like this
  -(the names of the executables may be different on your system):
  +(the names of the executables may be different on your system; and
  +consider that by the settings below tftp is ran by a specific user):
   
   echo "
   	service telnet
  @@ -402,7 +397,7 @@
   
   (It's your homework to find out how to get it executed at startup.)
   
  -And now restart xinetd; in an "official" LFS/BLFS system it is done with
  +Restart xinetd; in an "official" LFS/BLFS system it is done with
   
   /etc/rc.d/init.d/xinetd restart
   
  @@ -446,7 +441,7 @@
   The java viewer is shipped with the tightvnc source code in a
   precompiled form; however, if you want to act according to LFS spirit,
   *do not* install it, rather download the tightvnc-1.2.*_javasrc package
  -from the tightvnc side, and compile it yourself. That's pretty
  +from the tightvnc site, and compile it yourself. That's pretty
   straightforward.  
   
   Connecting from client to server 
  @@ -469,7 +464,7 @@
   * Transferring files between the server and client is as follows:
   
   - downloading the file foo from server to client: on the server, put foo
  -into $TRANSFER, make it word-readable, then on the client: get sure that
  +into $TRANSFER, make it world-readable, then on the client: get sure that
   foo does not exist in the current directory, then type:
   
   tftp -g -r foo $SERVER 
  @@ -510,7 +505,7 @@
   * pass the "-compatiblekbd" option to the vnc server if you want to use
   non-standard characters; eg., this way typing Alt+i in an xterm gives
   you an acuted e. This is the way to go for people whose language uses
  -special latin characters, as vnc does not support xmodmap well.
  +nonstandard characters, as vnc does not support xmodmap well.
   
   There is a more tricky way of using vnc: with the help of ssh tunneling
   you can reach any vnc server from the client which is reachable from the
  @@ -569,16 +564,13 @@
   The list below is about both of the uClibc-bootfloppy and the
   svnc-x_terminal hints. 
   
  -* Its weird that we need to create a 
  -
  -/usr/i386-linux-uclibc/lib/ -> ../../lib
  -
  -symlink. However, its not really a problem.
  +The following weirdnesses are probably due to the respective programs
  +and not to doing something wrong in these hints.
   
   * Sometimes when switching to another terminal and then back to the
  -svga vncviewer the keyboard gets screwed up. Sometimes the keyboard
  -gets screwed up without any obvious reason. However, after restarting
  -the viewer, things behave normally again.
  +svga vncviewer the keyboard gets screwed up. Using serial mouse,
  +sometimes the keyboard gets screwed up without any obvious reason.
  +However, after restarting the viewer, things behave normally again.
   
   * Using libvgagl-dependent programs (like svncviewer) on my 486
   laptop, I see a horizontal white line at half height of the screen.
  @@ -590,14 +582,8 @@
   * Find the appropriate environment variable settings / Makefile hacks
   for svga demoprogs and svncviewer which let us link against the svga
   libs without putting them to /usr/lib (I made some weak attempts but
  -those didn't suceed and it would be not worth to delay this 0.1
  -release because of this.
  -
  -* Test different vnc distributions (I tried both realvnc and
  -tightvnc; I have the feeling that with realvnc the keyboard get
  -screwed up only when changing terminals away and back. But it's
  -just a vague feeling yet, keyboard screw-ups need to be examined
  -more precisely -- to see exactly what actions provoke it).
  +those didn't succeed and it would be not worth to delay this 0.1
  +release because of this.)
   
   Credits
   -------
  @@ -605,6 +591,7 @@
   I gathered information from the following sources:
   
   LFS mailing lists
  +busybox mailing list
   uClibc mailing list archives
   vnc mailing list archives
   "Creating a custom bootdisk" chapter of the BLFS book
  @@ -612,6 +599,12 @@
   PLIP-install HOWTO
   http://ebusiness.gbdirect.co.uk/case_studies/xterminal.html
   the LODS project (http://www.khk.net/lods/index.html)	
  -the tomsrtbt project
  +the tomsrtbt project (http://www.toms.net/rb/)
  +
  +Contributions
  +-------------
  +
  +Archaic had some useful advice.
   
   
  +END of "Setting up a minimalistic X terminal using the svga vncviewer" hint
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe hints' in the subject header of the message



More information about the hints mailing list