old-www/HOWTO/Kiosk-HOWTO-2.html

39 lines
1.5 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Kiosk HOWTO : Overview</TITLE>
<LINK HREF="Kiosk-HOWTO-3.html" REL=next>
<LINK HREF="Kiosk-HOWTO-1.html" REL=previous>
<LINK HREF="Kiosk-HOWTO.html#toc2" REL=contents>
</HEAD>
<BODY>
<A HREF="Kiosk-HOWTO-3.html">Next</A>
<A HREF="Kiosk-HOWTO-1.html">Previous</A>
<A HREF="Kiosk-HOWTO.html#toc2">Contents</A>
<HR>
<H2><A NAME="s2">2. Overview</A></H2>
<P>Setting up Linux for use as a web-based kiosk is similar to setting up
Linux as a graphical workstaion, with a few extra considerations. If
the machine is to be a standalone unit, it must boot straight into
kiosk mode. Furthermore, the browser environment must be modified in
to disable standard dialog screens and to eliminate parts of the
browser that allow inappropriate interaction, such as the Location Bar
in Netscape.
<P>Essentially a kiosk website is self-contained. Users navigate through
the site via clicks with a pointing device. The pointing device can be
a touchscreen, a trackball, or a mouse. Mice are difficult to secure
in a public area.
<P>A Linux kiosk can be connected back to a home site via a direct
network or PPP link, requesting pages from the home site, or it can be
a self-contained website, running Apache and any corresponding CGI
modules.
<P>
<HR>
<A HREF="Kiosk-HOWTO-3.html">Next</A>
<A HREF="Kiosk-HOWTO-1.html">Previous</A>
<A HREF="Kiosk-HOWTO.html#toc2">Contents</A>
</BODY>
</HTML>