NSLU2-Linux
view · edit · print · history

Optware.X11 History

Hide minor edits - Show changes to markup

July 26, 2005, at 07:41 PM by sigfpe --
Changed line 5 from:
  • First, obviously the slug has no screen, mouse or keyboard. You will need to have an X server running on a seperate machine (I will call this your "X server system"). If you have a gnu/linux based desktop system, you almost certainly are running an X server already; X server software is also available for windows and MacOS?.
to:
  • First, obviously the slug has no screen, mouse or keyboard. You will need to have an X server running on a separate machine (I will call this your "X server system"). If you have a gnu/linux based desktop system, you almost certainly are running an X server already; X server software is also available for windows and MacOS?.
March 12, 2005, at 11:06 AM by bobtm --
Changed line 8 from:
  • Fourth, if you are using openssh, you need to edit /opt/etc/openssh/sshd_config on your slug and add a line saying "X11Forwarding? yes". Restart openssh after doing this. Now is probably a good time to completely reboot your slug.
to:
  • Fourth, if you are using openssh, you need to edit /opt/etc/openssh/sshd_config on your slug and add a line saying "X11Forwarding yes". Restart openssh after doing this. Now is probably a good time to completely reboot your slug.
February 27, 2005, at 08:21 AM by jp30 --
Added lines 49-50:
xpmX pixmap library
xawAthena widgetset
February 24, 2005, at 06:39 AM by jp30 --
Changed line 1 from:

I've done some work on packaging the x11 libraries and gtk+ for unslung. Not all the packages are ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources.

to:

Yes, it is possible to have a graphical user interface on your slug!

Changed line 3 from:

For a native build, you will need these package versions: automake 1.9.4-1, libtool 1.2.10-2, pkgconfig 0.15.0-1, crosstool-native 0.28-rc37-5. They need to be actually installed on your slug before you start building any of the other packages listed below.

to:

Here is how to do it:

Changed lines 5-9 from:

The packages in question are:

to:
  • First, obviously the slug has no screen, mouse or keyboard. You will need to have an X server running on a seperate machine (I will call this your "X server system"). If you have a gnu/linux based desktop system, you almost certainly are running an X server already; X server software is also available for windows and MacOS?.
  • Second, you need to install the right software on your slug: "ipkg install vte xdpyinfo xauth" as root should do it.
  • Third, you will need to connect from your X server system to your slug with the ssh protocol. And you will need ssh software that understands how to forward the X protocol on both the X server system, and on the slug. Both openssh and dropbear can do this; I use openssh. If you aren't running an ssh server on your slug already, "ipkg install openssh" and check that you can log in with it.
  • Fourth, if you are using openssh, you need to edit /opt/etc/openssh/sshd_config on your slug and add a line saying "X11Forwarding? yes". Restart openssh after doing this. Now is probably a good time to completely reboot your slug.
  • Fifth, you are now ready for slugvision! Log into your slug with "ssh -X"; once you are logged in, try running "gtk-demo" or "vte". These graphical programs are running on your slug, but displaying on your X server system.
Changed lines 11-51 from:
PackageNotesStatus
atkgtk+ dependency(in feed)
fixesextprotocol headers(in feed)
fontconfigclient-side font library(in feed)
freetypeclient-side font library(in feed)
gtk+gtk+ 
pangogtk+ dependency(in feed)
recordextprotocol headers(in feed)
renderextprotocol headers(in feed)
ttf-bitstream-verafree truetype font for use with freetype(in feed)
x11X client library(in feed)
xauX client library(in feed)
xcursorX client library(in feed)
xdmcpX client? library(in feed)
xdpyinfoutility(in feed)
xextX client library(in feed)
xextensionsprotocol headers(in feed)
xfixesX client library(in feed)
xftX client library(in feed)
xprotoprotocol headers(in feed)
xrenderX client library(in feed)
xtransprotocol headers(in feed)
xtstX client library(in feed)
iceX client library(in feed)
smX client library(in feed)
xtX client library(in feed)
xmuX client library(in feed)
xauthutility(in feed)

Packages marked (in feed) should be available from the package feed. Packages marked (testing) are currently under submission to be included in the feed. Other packages are in unslung CVS, but not yet in a feed, probably because they need more work.

FAQ

  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version 3.8p1-3 of the openssh package. You will also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug, with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
  • How else can I get a display? If you can't get your ssh daemon of choice to forward X11 for you, there's always the Old Way. You can set the DISPLAY environment variable on the slug to point to an X server that is listening for connections on the network (e.g. DISPLAY=mydesktop:0). There are various gotchas involved in this that are beyond the scope of this wiki page. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need to reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications.
  • Is there any other way to get a display? Maybe it would be nice to have http://www.realvnc.com vnc on a slug? Anyone want to port it?
  • What can I run? I haven't packaged any real apps yet, so you're limited to xdpyinfo and gtk-demo, which should be enough for testing. The packages listed above should install a full native development environment for gtk+. Build your favourite app and contribute it.
to:

If these instructions do not work for you, or you can think of a way to make them clearer, please edit them.

Changed line 13 from:

Known issues

to:

If you would like to contribute an X11-based or gtk+-based application, and want help, feel free to come ask questions on the #nslu2-linux irc channel, or send email to the yahoo list.

Changed line 15 from:
  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The missing modules are installed by the gconv-modules package, which also puts a symlink from /lib/gconv to /opt/lib/gconv. Unfortunately this symlink would be removed by a firmware upgrade - if this has happened to you, you need to reinstall the gconv-modules package.
to:

X11-related packages

Changed line 17 from:
  • athena widgets I haven't ported Xaw. It should not be difficult to do, if anyone wants it.
to:

This is a list of the X11-related packages now available:

Changed lines 19-48 from:

-- jp30

to:
PackageNotes
atkgtk+ dependency
fixesextprotocol headers
fontconfigclient-side font library
freetypeclient-side font library
gtk+gtk+
pangogtk+ dependency
recordextprotocol headers
renderextprotocol headers
ttf-bitstream-verafree truetype font for use with freetype
x11X client library
xauX client library
xcursorX client library
xdmcpX client? library
xdpyinfoutility
xextX client library
xextensionsprotocol headers
xfixesX client library
xftX client library
xprotoprotocol headers
xrenderX client library
xtransprotocol headers
xtstX client library
iceX client library
smX client library
xtX client library
xmuX client library
xauthutility
vteterminal widget for gtk+
February 21, 2005, at 04:10 AM by jp30 --
Changed line 1 from:

I've done some work on packaging the x11 libraries and gtk+ for unslung. Not all the packages are ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources. My aim is to have them all build both cross and native, and I am interested in hearing bug reports if you can't get them to build.

to:

I've done some work on packaging the x11 libraries and gtk+ for unslung. Not all the packages are ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources.

Changed lines 9-14 from:
atkgtk+ dependency(testing)
fixesextprotocol headers(testing)
fontconfigclient-side font library(testing)
freetypeclient-side font library(testing)
gtk+gtk+(testing)
pangogtk+ dependency(testing)
to:
atkgtk+ dependency(in feed)
fixesextprotocol headers(in feed)
fontconfigclient-side font library(in feed)
freetypeclient-side font library(in feed)
gtk+gtk+ 
pangogtk+ dependency(in feed)
Changed lines 16-17 from:
renderextprotocol headers(testing)
ttf-bitstream-verafree truetype font for use with libxft(testing)
to:
renderextprotocol headers(in feed)
ttf-bitstream-verafree truetype font for use with freetype(in feed)
Changed line 20 from:
xcursorX client library(testing)
to:
xcursorX client library(in feed)
Changed lines 25-26 from:
xfixesX client library(testing)
xftX client library(testing)
to:
xfixesX client library(in feed)
xftX client library(in feed)
Changed line 28 from:
xrenderX client library(testing)
to:
xrenderX client library(in feed)
Changed line 37 from:

Packages marked (in feed) should be available from the package feed. Packages marked (testing) are currently under submission to be included in the feed. Other packages are in unslung CVS, but not yet in a feed.

to:

Packages marked (in feed) should be available from the package feed. Packages marked (testing) are currently under submission to be included in the feed. Other packages are in unslung CVS, but not yet in a feed, probably because they need more work.

February 21, 2005, at 12:24 AM by jp30 --
Changed line 1 from:

I've done some work on packaging the x11 libraries and gtk+ for unslung. The packages are not yet ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources. My aim is to have them all build both cross and native, and I am interested in hearing bug reports if you can't get them to build.

to:

I've done some work on packaging the x11 libraries and gtk+ for unslung. Not all the packages are ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources. My aim is to have them all build both cross and native, and I am interested in hearing bug reports if you can't get them to build.

Deleted lines 4-5:

"I" here refers to Josh Parsons (jp30 at sourceforge)

Changed lines 9-35 from:
atkgtk+ dependency 
fixesextprotocol headers 
fontconfigclient-side font library 
freetypeclient-side font library 
gtk+gtk+ 
pangogtk+ dependency 
recordextprotocol headers(testing)
renderextprotocol headers 
ttf-bitstream-verafree truetype font for use with libxft 
x11X client library(testing)
xauX client library(testing)
xcursorX client library 
xdmcpX client? library(testing)
xdpyinfoutility(testing)
xextX client library(testing)
xextensionsprotocol headers(testing)
xfixesX client library 
xftX client library 
xprotoprotocol headers(testing)
xrenderX client library 
xtransprotocol headers(testing)
xtstX client library(testing)
iceX client library(testing)
smX client library(testing)
xtX client library(testing)
xmuX client library(testing)
xauthutility(testing)
to:
atkgtk+ dependency(testing)
fixesextprotocol headers(testing)
fontconfigclient-side font library(testing)
freetypeclient-side font library(testing)
gtk+gtk+(testing)
pangogtk+ dependency(testing)
recordextprotocol headers(in feed)
renderextprotocol headers(testing)
ttf-bitstream-verafree truetype font for use with libxft(testing)
x11X client library(in feed)
xauX client library(in feed)
xcursorX client library(testing)
xdmcpX client? library(in feed)
xdpyinfoutility(in feed)
xextX client library(in feed)
xextensionsprotocol headers(in feed)
xfixesX client library(testing)
xftX client library(testing)
xprotoprotocol headers(in feed)
xrenderX client library(testing)
xtransprotocol headers(in feed)
xtstX client library(in feed)
iceX client library(in feed)
smX client library(in feed)
xtX client library(in feed)
xmuX client library(in feed)
xauthutility(in feed)
Changed line 53 from:
  • libjpeg libjpeg version 6b-2 is required by gtk+
to:
  • athena widgets I haven't ported Xaw. It should not be difficult to do, if anyone wants it.
Changed line 55 from:
  • missing libraries I haven't yet ported Xaw.
to:

-- jp30

February 18, 2005, at 01:12 AM by jp30 --
Deleted line 10:
gconv-modulesmissing bits of glibc needed by gtk+ 
Changed line 17 from:
recordextprotocol headers 
to:
recordextprotocol headers(testing)
Changed lines 20-21 from:
x11X client library 
xauX client library 
to:
x11X client library(testing)
xauX client library(testing)
Changed lines 23-26 from:
xdmcpprotocol headers 
xdpyinfoutility 
xextX client library 
xextensionsprotocol headers 
to:
xdmcpX client? library(testing)
xdpyinfoutility(testing)
xextX client library(testing)
xextensionsprotocol headers(testing)
Changed line 29 from:
xprotoprotocol headers 
to:
xprotoprotocol headers(testing)
Changed lines 31-37 from:
xtransprotocol headers 
xtstX client library 
iceX client library 
smX client library 
xtX client library 
xmuX client library 
xauthutility 
to:
xtransprotocol headers(testing)
xtstX client library(testing)
iceX client library(testing)
smX client library(testing)
xtX client library(testing)
xmuX client library(testing)
xauthutility(testing)
Changed line 39 from:

Packages marked (in feed) should be available from the package feed. Other packages are in unslung CVS, but not yet in a feed.

to:

Packages marked (in feed) should be available from the package feed. Packages marked (testing) are currently under submission to be included in the feed. Other packages are in unslung CVS, but not yet in a feed.

Changed line 43 from:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version 3.8p1-3 of the openssh package. You may also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
to:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version 3.8p1-3 of the openssh package. You will also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug, with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
February 15, 2005, at 08:21 PM by jp30 --
Changed line 3 from:

For a native build, you will need these package versions: automake 1.9.4-1, libtool 1.2.10-2, pkg-config 0.15.0-1, crosstool-native 0.28-rc37-5. They need to be actually installed on your slug before you start building any of the other packages listed below.

to:

For a native build, you will need these package versions: automake 1.9.4-1, libtool 1.2.10-2, pkgconfig 0.15.0-1, crosstool-native 0.28-rc37-5. They need to be actually installed on your slug before you start building any of the other packages listed below.

Added line 11:
gconv-modulesmissing bits of glibc needed by gtk+ 
Deleted line 17:
pkgconfigneeded for native build environment(in feed)
Changed line 54 from:
  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The solution is to add a symlink from /lib/gconv to the gconv modules distributed as part of crosstool. The gtk+ ipkg does this on installation, but its effect would be reversed by a firmware upgrade. If you see errors like this, try reinstalling gtk+ (what about a separate package, that copies the gconv modules from crosstool tree in it's own tree? e.g. see the libstd++ package.)
to:
  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The missing modules are installed by the gconv-modules package, which also puts a symlink from /lib/gconv to /opt/lib/gconv. Unfortunately this symlink would be removed by a firmware upgrade - if this has happened to you, you need to reinstall the gconv-modules package.
Changed line 56 from:
  • libjpeg The unslung libjpeg package (as of version 6b-1) does not install headers or a shared library. This means that jpeg support in gtk+ is probably broken at present. (fixed as of libjpeg version 6b-2)
to:
  • libjpeg libjpeg version 6b-2 is required by gtk+
February 15, 2005, at 12:39 PM by pTweety --
Changed line 54 from:
  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The solution is to add a symlink from /lib/gconv to the gconv modules distributed as part of crosstool. The gtk+ ipkg does this on installation, but its effect would be reversed by a firmware upgrade. If you see errors like this, try reinstalling gtk+
to:
  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The solution is to add a symlink from /lib/gconv to the gconv modules distributed as part of crosstool. The gtk+ ipkg does this on installation, but its effect would be reversed by a firmware upgrade. If you see errors like this, try reinstalling gtk+ (what about a separate package, that copies the gconv modules from crosstool tree in it's own tree? e.g. see the libstd++ package.)
February 15, 2005, at 07:44 AM by jp30 --
Changed line 44 from:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version the openssh package version 3.8p1-3. You may also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
to:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version 3.8p1-3 of the openssh package. You may also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
February 15, 2005, at 07:42 AM by jp30 --
Changed line 3 from:

For a native build, you will need automake (at least 1.9.4-1) and libtool (at least 1.2.10-2) installed on your slug, in addition to the crosstool-native packages.

to:

For a native build, you will need these package versions: automake 1.9.4-1, libtool 1.2.10-2, pkg-config 0.15.0-1, crosstool-native 0.28-rc37-5. They need to be actually installed on your slug before you start building any of the other packages listed below.

Changed lines 44-48 from:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). There are various gotchas involved in this that are beyond the scope of this webpage. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need to reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications. At a later date I would like to get openssh on the slug to forward the X protocol stream, which will avoid these complications.
to:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). The easiest and safest way to do this is to use openssh. You will need version the openssh package version 3.8p1-3. You may also need to edit /opt/etc/openssh/sshd_config appropriately to enable X11 forwarding, and you need to have the xauth package installed. After that "ssh -X myslug" from an xterm on your desktop will connect you to the slug with an X connection forwarded back to your local display. You might also be able to get dropbear to do the same thing, though I have not tried it.
  • How else can I get a display? If you can't get your ssh daemon of choice to forward X11 for you, there's always the Old Way. You can set the DISPLAY environment variable on the slug to point to an X server that is listening for connections on the network (e.g. DISPLAY=mydesktop:0). There are various gotchas involved in this that are beyond the scope of this wiki page. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need to reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications.
  • Is there any other way to get a display? Maybe it would be nice to have http://www.realvnc.com vnc on a slug? Anyone want to port it?
February 08, 2005, at 08:02 PM by jp30 --
Changed line 17 from:
pkgconfigneeded for native build environment(production)
to:
pkgconfigneeded for native build environment(in feed)
Added lines 34-38:
iceX client library 
smX client library 
xtX client library 
xmuX client library 
xauthutility 
Changed line 40 from:

Packages marked (production) should be available from the package feed. Other packages I am still working on.

to:

Packages marked (in feed) should be available from the package feed. Other packages are in unslung CVS, but not yet in a feed.

Changed line 54 from:
  • missing libraries I haven't yet ported Xt, Xaw, Xmu, libSM, or libICE.
to:
  • missing libraries I haven't yet ported Xaw.
February 08, 2005, at 08:07 AM by jp30 --
Changed lines 9-31 from:
  • atk
  • fixesext
  • fontconfig
  • freetype
  • gtk+
  • pango
  • pkgconfig (production)
  • recordext
  • renderext
  • ttf-bitstream-vera
  • x11
  • xau
  • xcursor
  • xdmcp
  • xdpyinfo
  • xext
  • xextensions
  • xfixes
  • xft
  • xproto
  • xrender
  • xtrans
  • xtst
to:
PackageNotesStatus
atkgtk+ dependency 
fixesextprotocol headers 
fontconfigclient-side font library 
freetypeclient-side font library 
gtk+gtk+ 
pangogtk+ dependency 
pkgconfigneeded for native build environment(production)
recordextprotocol headers 
renderextprotocol headers 
ttf-bitstream-verafree truetype font for use with libxft 
x11X client library 
xauX client library 
xcursorX client library 
xdmcpprotocol headers 
xdpyinfoutility 
xextX client library 
xextensionsprotocol headers 
xfixesX client library 
xftX client library 
xprotoprotocol headers 
xrenderX client library 
xtransprotocol headers 
xtstX client library 
February 08, 2005, at 07:56 AM by jp30 --
Changed line 33 from:

Packages marked (production) are available from the package feed. Other packages I am still working on.

to:

Packages marked (production) should be available from the package feed. Other packages I am still working on.

February 08, 2005, at 07:55 AM by jp30 --
Changed line 15 from:
  • pkgconfig
to:
  • pkgconfig (production)
Added lines 33-34:

Packages marked (production) are available from the package feed. Other packages I am still working on.

Changed line 37 from:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). There are various gotchas involved in this that are beyond the scope of this webpage. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications. At a later date I would like to get openssh on the slug to forward the X protocol stream, which will avoid these horrors.
to:
  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). There are various gotchas involved in this that are beyond the scope of this webpage. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need to reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications. At a later date I would like to get openssh on the slug to forward the X protocol stream, which will avoid these complications.
Changed line 45 from:
  • libjpeg The unslung libjpeg package does not (currently) install headers or a shared library. This means that jpeg support in gtk+ is probably broken at present.
to:
  • libjpeg The unslung libjpeg package (as of version 6b-1) does not install headers or a shared library. This means that jpeg support in gtk+ is probably broken at present. (fixed as of libjpeg version 6b-2)
February 08, 2005, at 02:19 AM by jp30 --
Added lines 44-45:
  • missing libraries I haven't yet ported Xt, Xaw, Xmu, libSM, or libICE.
February 08, 2005, at 02:07 AM by jp30 --
Changed line 37 from:
  • What can I run? I haven't built any real apps yet, so you're limited to xdpyinfo and gtk-demo, which should be enough for testing. The packages listed above should install a full native development environment for gtk+. Build your favourite app and contribute it.
to:
  • What can I run? I haven't packaged any real apps yet, so you're limited to xdpyinfo and gtk-demo, which should be enough for testing. The packages listed above should install a full native development environment for gtk+. Build your favourite app and contribute it.
Added lines 42-43:
  • libjpeg The unslung libjpeg package does not (currently) install headers or a shared library. This means that jpeg support in gtk+ is probably broken at present.
February 08, 2005, at 02:03 AM by jp30 --
Changed lines 1-41 from:

Describe {{X11}} here.

to:

I've done some work on packaging the x11 libraries and gtk+ for unslung. The packages are not yet ready for distribution through the packages feed, but the adventurous may wish to build and install them from the unslung CVS sources. My aim is to have them all build both cross and native, and I am interested in hearing bug reports if you can't get them to build.

For a native build, you will need automake (at least 1.9.4-1) and libtool (at least 1.2.10-2) installed on your slug, in addition to the crosstool-native packages.

"I" here refers to Josh Parsons (jp30 at sourceforge)

The packages in question are:

  • atk
  • fixesext
  • fontconfig
  • freetype
  • gtk+
  • pango
  • pkgconfig
  • recordext
  • renderext
  • ttf-bitstream-vera
  • x11
  • xau
  • xcursor
  • xdmcp
  • xdpyinfo
  • xext
  • xextensions
  • xfixes
  • xft
  • xproto
  • xrender
  • xtrans
  • xtst

FAQ

  • How do I get a display? The slug (obviously) doesn't have a screen, so has no display of its own. At the moment you must connect over the network to an X server running on a different machine (e.g. your gnu/linux desktop). There are various gotchas involved in this that are beyond the scope of this webpage. A quick checklist: 1) set DISPLAY on your slug; 2) make sure the X server on your desktop box is listening for TCP connections - it will not be doing so by default on many modern gnu/linuces - you may need reconfigure xdm / gdm; 3) give the slug access to the server with xhost; 4) make a hole in your desktop box's firewall to let X11/TCP connections in. Do not do 2, 3, or 4 on an internet-connected machine unless you understand the security implications. At a later date I would like to get openssh on the slug to forward the X protocol stream, which will avoid these horrors.
  • What can I run? I haven't built any real apps yet, so you're limited to xdpyinfo and gtk-demo, which should be enough for testing. The packages listed above should install a full native development environment for gtk+. Build your favourite app and contribute it.

Known issues

  • gconv The glibc distributed with the NSLU2, and with unslung, was built to support character encoding conversions, but the necessary "gconv" modules were not distributed as part of the firmware. This problem manifests itself with errors like this: "Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'". The solution is to add a symlink from /lib/gconv to the gconv modules distributed as part of crosstool. The gtk+ ipkg does this on installation, but its effect would be reversed by a firmware upgrade. If you see errors like this, try reinstalling gtk+
view · edit · print · history · Last edited by sigfpe.
Based on work by bobtm, jp30, and pTweety.
Originally by jp30.
Page last modified on November 16, 2006, at 01:34 AM