From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: printing-howto.xml
Date: Mon, 26 Jan 2009 07:40:20 +0000 [thread overview]
Message-ID: <E1LRM4y-0003zm-6I@stork.gentoo.org> (raw)
nightmorph 09/01/26 07:40:20
Modified: printing-howto.xml
Log:
looks like the entropy generation failure is back, so re-adding the note to the printing guide. bug 254867
Revision Changes Path
1.73 xml/htdocs/doc/en/printing-howto.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.73&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.73&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?r1=1.72&r2=1.73
Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- printing-howto.xml 16 Jun 2008 01:08:44 -0000 1.72
+++ printing-howto.xml 26 Jan 2009 07:40:20 -0000 1.73
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.72 2008/06/16 01:08:44 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.73 2009/01/26 07:40:20 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -24,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>3.1</version>
-<date>2008-06-15</date>
+<version>3.2</version>
+<date>2009-01-25</date>
<chapter>
<title>Printing and Gentoo Linux</title>
@@ -586,6 +586,13 @@
administrative tasks.
</p>
+<note>
+If you use an HTTPS connection to CUPS, the first time you access the interface
+it <e>may</e> take a very long time before the site comes up. This is because the
+first request triggers the generation of the CUPS SSL certificates which can be a
+very time-consuming job.
+</note>
+
<p>
Go to <e>Administration</e> and enter your root login and password information
at the box. Then, when you have reached the administrative interface, click on
next reply other threads:[~2009-01-26 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 7:40 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-14 9:54 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: printing-howto.xml Joshua Saddler (nightmorph)
2009-12-29 19:31 Joshua Saddler (nightmorph)
2010-02-17 7:28 Joshua Saddler (nightmorph)
2010-02-17 18:06 Joshua Saddler (nightmorph)
2010-02-23 11:04 Jan Kundrat (jkt)
2010-03-17 8:21 Joshua Saddler (nightmorph)
2010-09-10 4:35 Joshua Saddler (nightmorph)
2011-02-14 6:33 Jan Kundrat (jkt)
2011-03-02 8:59 Joshua Saddler (nightmorph)
2012-12-25 19:00 Sven Vermeulen (swift)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LRM4y-0003zm-6I@stork.gentoo.org \
--to=nightmorph@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox