headers
Bruce Dubbs | 2 Apr 2007 19:51
Picon

spam on blfs-book

I removed the spam from the tickets.  Removing from the mailman archive
is a little more difficult.

  -- Bruce
--

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Bruce Dubbs | 2 Apr 2007 20:17
Picon

Re: spam on blfs-book

Bruce Dubbs wrote:
> I removed the spam from the tickets.  Removing from the mailman archive
> is a little more difficult.

But the procedure is documented (by me) and the spam is now removed from
the pipermail archives.

  -- Bruce
--

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Bruce Dubbs | 7 Apr 2007 19:03
Picon

Spam in trac tickets

I deleted spam from lfs-book and blfs-book, both mail and trac tickets,
this morning.  Do we need to make the books ticket system so only
authorized (vice registered) users can create or modify tickets?

  -- Bruce
--

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 8 comments |
headers
M.Canales.es | 7 Apr 2007 19:07

[new XSL] Ready for inputs.

Hi,

Looks like the stylesheets revision for LFS is done for now, until have 
DocBook-xsl-1.72.1 available.

The unique visible change in the XHTML output is that chapters TOC has been 
added, as was suggested. An on-line version is available here:

http://www.lfs-es.info/new-lfs-book/

In PDF output there are several changes. To can compare it, both the current 
PDF and the new one can be downloaded from here:

http://www.lfs-es.info/new-lfs-book/fop0-lfs-book.pdf      current PDF

http://www.lfs-es.info/new-lfs-book/fop1-lfs-book.pdf      new PDF

I'm awaiting your comments, sugestions and complaints, not only about the 
outputs look but also about the documentational comments in the stylesheets, 
before start working on the BLFS stylesheets update.

-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
(Continue reading)

Permalink | Reply | 26 comments |
headers
Jeremy Huntwork | 8 Apr 2007 03:40
Picon
Favicon
Gravatar

Fighting spam via greylisting

Greetings All,

Inspired by an email from Richard Downing, I decided to look into using
greylisting to help fight spam. If you haven't heard of it before see:
http://www.greylisting.org

The basic idea is that whenever a new MTA (one that is not in the
greylisting database) attempts to deliver mail, the mail is
automatically rejected. If the MTA is a valid MTA, it will retry to
deliver the mail after a few minutes. At this point the greylisting
server recognizes the MTA from a previous attempt and assumes that it is
valid mail. The address of the sending MTA is added to the database and
future messages from that server are automatically allowed (at least for
a while).

I tried a Postfix implementation called Postgrey on my own personal
server and the results were very good. (See
http://postgrey.schweikert.ch/). Based on those results it was decided
to implement this service on Quantum.

Quantum already had SpamAssassin installed and it uses some nice Postfix
reject rules to keep a good deal of spam at bay. Combine that with the
fact that the mailing lists require a valid subscription to post and the
result is that most spam never reaches the end users. Even so, a good
deal of spam gets past SpamAssassin and Postfix and hits Mailman. And
therein lies the problem we wish to avoid. Even though mailman rejects
the message, the processing time mailman spends is expensive. Our hope
is to eliminate a good deal of spam before it even 'enters' the system,
so to speak.
(Continue reading)

Permalink | Reply | 45 comments |
headers
Jeremy Huntwork | 8 Apr 2007 03:43
Picon
Favicon
Gravatar

Re: [new XSL] Ready for inputs.

On Sat, Apr 07, 2007 at 07:07:32PM +0200, M.Canales.es wrote:
> http://www.lfs-es.info/new-lfs-book/

It looks nice. :) I can't really see a difference, apart from the 'Up'
links.

Guess that's all I have to say about that.

--
JH
--

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Bruce Dubbs | 8 Apr 2007 04:28
Picon

Re: [new XSL] Ready for inputs.

M.Canales.es wrote:
> Hi,
> 
> Looks like the stylesheets revision for LFS is done for now, until have 
> DocBook-xsl-1.72.1 available.
> 
> The unique visible change in the XHTML output is that chapters TOC has been 
> added, as was suggested. An on-line version is available here:
> 
> http://www.lfs-es.info/new-lfs-book/
> 
> In PDF output there are several changes. To can compare it, both the current 
> PDF and the new one can be downloaded from here:
> 
> http://www.lfs-es.info/new-lfs-book/fop0-lfs-book.pdf      current PDF
> 
> http://www.lfs-es.info/new-lfs-book/fop1-lfs-book.pdf      new PDF
> 
> I'm awaiting your comments, sugestions and complaints, not only about the 
> outputs look but also about the documentational comments in the stylesheets, 
> before start working on the BLFS stylesheets update.

I took a look at both the html and the pdf versions.  Both look very
nice.  I have no issues with the html version at all, but I do have two
issues about the pdf version that I think are worthy of discussion.

I think of the pdf version as being targeted for printing on paper.
When looking at the divisions, each section starts on its own page.  I
think that this is proper for html, but I'm not certain it is right for
a paper version.  The place I first noticed it is in the preface where
(Continue reading)

Permalink | Reply | 24 comments |
headers
Jeremy Huntwork | 8 Apr 2007 08:16
Picon
Favicon
Gravatar

Re: Fighting spam via greylisting

Jeremy Huntwork wrote:
> Be advised that your first post to a mailing list might be delayed by a
> few minutes. If it takes a considerably long time, or if you receive an
> undeliverable message from your MTA, please let us know at server-admin
> AT linuxfromscratch DOT org so that we can adjust our whitelisting
> files.

Er. If you're having trouble mailing because of greylisting, then 
obviously a message to another mailing list on the same server isn't 
going to get through either. In that case, please send a message to my 
gmail account. My username is quadrata.

--
JH

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
M.Canales.es | 8 Apr 2007 17:33

Re: [new XSL] Ready for inputs.

El Domingo, 8 de Abril de 2007 04:28, Bruce Dubbs escribió:

Please, try to keep the CC to lfs-dev.

>
> I do think that each section in Chapters 5 and 6 that install a new
> package should start on a new page, but places like Chapters 8 and 9 and
> possibly 1, 2, 3, 4, and 7 should 'flow'.

Yes, I was thinking also about that. The code was committed some hours ago. 
Now the PDF have only 254 pages:

http://www.lfs-es.info/new-lfs-book/fop1-try2-lfs-book.pdf   

> It would also be nice to solve the problem of long urls that cause ugly
> spacing when the text is fully justified.  Examples are: page 13
> (section 1.5), page 14, page 206 (section 7.5), page 217 (7.12.1).
>
> The last paragraph on page 224 (8.2) also suffers from the
> long-name-spacing-problem.
>
> These word spacing issues vary a bit in 'badness', but it would be nice
> if there were optional (zero width space) breaks at slash ('/') and
> underscore ('_') characters.

The URLs hyphenation support on the old stylesheets and FOP-0.20 was very 
ugly. I will test if the current one is more usable and, if true, trying to 
extend the support also to filenames. 

--

--
(Continue reading)

Permalink | Reply | 22 comments |
headers
Randy McMurchy | 8 Apr 2007 19:26
Picon
Favicon

Cups-1.2.10

Hi all,

Currently, the book has CUPS-1.2.7. 1.2.10 is the current version.

However, the current version fails the test suite miserably. It is
a known bug, and fixed in SVN. I made a very small patch that updates
the 1.2.10 'test' directory to SVN, and all but 1 test passes (there
are 9 that fail before the patch).

Note that you must run the dbus-uuidgen program first, or you will
get additional failures.

I cannot figure out which other file(s) needs changing to get all the
tests to fail, so I created a patch that bumps the current version
(1.2.10) to current SVN. It builds, and tests just fine. Here are
the files changed using the bigger patch:

patching file CHANGES.txt
patching file backend/usb-darwin.c
patching file backend/usb-unix.c
patching file backend/usb.c
patching file conf/mime.convs
patching file conf/mime.types
patching file config-scripts/cups-common.m4
patching file configure
patching file cups/cups.h
patching file cups/language.c
patching file cups/localize.c
patching file cups/ppd.c
patching file cups/request.c
(Continue reading)

Permalink | Reply | 7 comments |

Gmane