Attachment 1431 Details for Bug 811 – [FIXED_X11R68x] Part three - update the generated Xprt.html file (patch for 2004-11-30-trunk)

[patch] [FIXED_X11R68x] Part three - update the generated Xprt.html file (patch for 2004-11-30-trunk)

patch.gudiff (text/plain), 12.01 KB, created by Roland Mainz on 2004-11-30 15:41:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Mainz

Created: 2004-11-30 15:41:59 UTC

Size: 12.01 KB

patch

obsolete

>Index: xc/ChangeLog
>===================================================================
>RCS file: /cvs/xorg/xc/ChangeLog,v
>retrieving revision 1.552
>diff -u -2 -0 -r1.552 ChangeLog
>--- xc/ChangeLog	30 Nov 2004 08:38:44 -0000	1.552
>+++ xc/ChangeLog	30 Nov 2004 23:30:08 -0000
>@@ -1,20 +1,26 @@
>+2004-11-30 Roland Mainz <roland.mainz@nrubsig.org>
>+ * xc/programs/Xserver/Xprint/Xprt.html
>+ Bugzilla #811 (https://freedesktop.org/bugzilla/show_bug.cgi?id=811):
>+ Updating generated Xprt.html which was forgotten during the
>+ previous work.
>+
> 2004-11-30 Egbert Eich <eich-at-freedesktop-dot-org>
> 
> 	* config/cf/xorgsite.def:
> 	Make Xorg the default server to install.
> 	
> 	* programs/Xserver/hw/xfree86/drivers/ati/Imakefile:
> 	* programs/Xserver/hw/xfree86/drivers/ati/atiprobe.c: (ATIProbe):
> 	Avoid PIO access on IA64. Some IA64 machine check if legacy ports
> 	outside the VGA range are accessed. The ATi driver however does 
> 	this to	probe for ISA Mach8/32/64. 
> 	Since no IA64 has ISA slots this restriction should not be
> 	relevant to the user.
> 
> 	* programs/Xserver/hw/xfree86/os-support/bus/Pci.c: (xf86scanpci):
> 	Avoid recursive calls of xf86scanpci(). This function normally 
> 	detects that it has been called before by checking if the PCI
> 	structure is filled out. So far if this was not the case 
> 	(because PCI probing has failed for some reason) the function
> 	is traversed again. With the chipset specific PCI bus probing
> 	this can lead to an endless recursive loop as the post-probing
>Index: xc/programs/Xserver/Xprint/Xprt.html
>===================================================================
>RCS file: /cvs/xorg/xc/programs/Xserver/Xprint/Xprt.html,v
>retrieving revision 1.1
>diff -u -2 -0 -r1.1 Xprt.html
>--- xc/programs/Xserver/Xprint/Xprt.html	25 Nov 2004 22:42:51 -0000	1.1
>+++ xc/programs/Xserver/Xprint/Xprt.html	30 Nov 2004 23:30:55 -0000
>@@ -6,41 +6,41 @@
> clients such as mozilla.
> Xprint is a very flexible, extensible, scaleable, client/server
> print system based on ISO 10175 (and some other specs) and the X11 
> rendering protocol. 
> Using Xprint an application can search, query and use devices like 
> printers, FAX machines or create documents in formats like PDF. 
> In particular, an application can seek a printer, query supported 
> attributes (like paper size, trays, fonts etc.), configure the printer 
> device to match it's needs and print on it like on any other X device 
> reusing parts of the code which is used for the video card Xserver.
> </div><div xmlns:ns1="" class="refsect1" lang="en"><a name="id2805117"></a><h2>USAGE</h2>
> Although Xprt may be invoked from the command line, it is
> preferable to run it as a daemon via the init script
> <tt class="filename">/etc/init.d/xprint</tt> (where this script exists).
> Client programs such as mozilla will require environment
> variable <tt class="envar">${XPSERVERLIST}</tt> to be set, identifying the
> &quot;display&quot; on which Xprt is running. This variable may be set
> for all users via <tt class="filename">/etc/profile</tt> (or similar), using
> <tt>/etc/init.d/xprint get_xpserverlist</tt>:
> <div class="informalexample"><pre class="programlisting">export XPSERVERLIST=`/etc/init.d/xprint get_xpserverlist`</pre></div></div><div class="refsect1" lang="en"><a name="id2805150"></a><h2>OPTIONS</h2>Many of Xprt's command line options are shared in common
>- with the usual X servers (see Xserver(7)).
>+ with the usual X servers (see Xserver(1x)).
> Commonly used options include:<div class="variablelist"><dl><dt><tt class="option">:<tt>display</tt></tt></dt><dd> The X server runs on the given display. If multiple X
> servers are to run simultaneously on a host, each must
> have a unique display number. Note that the standard X
> server (for video displays) typically runs on display
> :0. If <tt class="filename">/etc/init.d/xprint</tt> is used
> to invoke Xprt, it may be configured to automatically assign an available
> display number.</dd><dt><tt class="option">-ac</tt></dt><dd>disables host-based access control mechanisms. Enables access
> by any host, and permits any host to modify the access control
> list. Use with extreme caution. This option exists primarily
> for running test suites remotely.</dd><dt><tt class="option">-audit <tt>level</tt></tt></dt><dd>sets the audit trail level. The default level is 1, meaning
> only connection rejections are reported. Level 2 additionally
> reports all successful connections and disconnects. Level 4
> enables messages from the SECURITY extension, if present,
> including generation and revocation of authorizations and
> violations of the security policy. Level 0 turns off the audit
> trail. Audit lines are sent as standard error output.</dd><dt><tt class="option">-fp <tt>fontpath</tt></tt></dt><dd>sets the search path for fonts. This path is a comma
> separated list of directories which Xprt searches for
> font databases.</dd><dt><tt class="option">-pn</tt></dt><dd>permits the server to continue running if it fails to
> establish all of its well-known sockets (connection
> points for clients), but establishes at least
>@@ -88,28 +88,28 @@
> for any print jobs. For example, which paper tray to
> use, what default resolution, etc.
> </dd><dt><tt class="filename">${XPCONFIGDIR}/${LANG}/print/attributes/job</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/attributes/job</tt></dt><dd>
> The `job' file specifies the initial job values for any
> print jobs. For example, &quot;notification-profile&quot; can be
> set so that when a print job is successfully sent to a
> printer, e-mail is sent to the user.
> </dd><dt><tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/model-config</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf</tt></dt><dd>
> The `model-config' file has attributes that describe the
> printer model's capabilities and default settings.
> Printer model fonts may also be present. The model-config
> file also identifies the print ddx driver to be used.
> 
> For each printer model supported, a complete hierarchy of
> files should exist. In most cases, these files do not
> need to be modified.
> </dd><dt><tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pdf</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/pcl</tt>, <tt class="filename">${XPCONFIGDIR}/C/print/ddx-config/raster/postscript</tt></dt><dd>
> The print ddx drivers can have highly specific
> configuration files to control their behavior. In most
> cases, these files do not need to be modified.
>- </dd></dl></div></div><div class="refsect1" lang="en"><a name="id2805584"></a><h2>SEE ALSO</h2>Xprint(7), X11(7), xplsprinters(7), xprehashprinterlist(7), xphelloworld(7), xpxmhelloworld(7), xpawhelloworld(7), xpxthelloworld(7), xpsimplehelloworld(7), Xserver(7), libXp(3x), libXprintUtils(3x), libXprintAppUtils(3x), XmPrintShell(3x), XawPrintShell(3x), Xprint FAQ (<a href="http://xprint.mozdev.org/docs/Xprint_FAQ.html" target="_top">http://xprint.mozdev.org/docs/Xprint_FAQ.html</a>), Xprint main site (<a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>)</div><div class="refsect1" lang="en"><a name="id2805757"></a><h2>AUTHORS</h2>
>+ </dd></dl></div></div><div class="refsect1" lang="en"><a name="id2805584"></a><h2>SEE ALSO</h2>Xprint(7), X11(7), xplsprinters(1x), xprehashprinterlist(1x), xphelloworld(1x), xpxmhelloworld(1x), xpawhelloworld(1x), xpxthelloworld(1x), xpsimplehelloworld(1x), Xserver(1x), libXp(3x), libXprintUtils(3x), libXprintAppUtils(3x), XmPrintShell(3x), XawPrintShell(3x), Xprint FAQ (<a href="http://xprint.mozdev.org/docs/Xprint_FAQ.html" target="_top">http://xprint.mozdev.org/docs/Xprint_FAQ.html</a>), Xprint main site (<a href="http://xprint.mozdev.org/" target="_top">http://xprint.mozdev.org/</a>)</div><div class="refsect1" lang="en"><a name="id2805757"></a><h2>AUTHORS</h2>
> This manual page was written by 
> Drew Parsons <tt class="email">&lt;<a href="mailto:dparsons@debian.org">dparsons@debian.org</a>&gt;</tt> and
> Roland Mainz <tt class="email">&lt;<a href="mailto:roland.mainz@nrubsig.org">roland.mainz@nrubsig.org</a>&gt;</tt>,
> with some help from the man page at
> <a href="http://www.sins.com.au/unix/manpages/Xprt.html" target="_top">http://www.sins.com.au/unix/manpages/Xprt.html</a> and the XFree86
> man page for Xserver(1).
> </div></div></body></html>

Flags:

roland.mainz: 6.8-branch+

Actions: View | Splinter Review

Attachments on bug 811: 1374 | 1379 | 1431

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.