public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] New idea for proxy wiki
Date: Mon, 09 Jan 2012 15:04:59 +0100	[thread overview]
Message-ID: <D35B801D-2800-4688-B205-311BCBFF5119@ipfire.org> (raw)
In-Reply-To: <1326074932.1891.35.camel@hughes.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 2802 bytes --]

Thank you both for the positive response, so i will return to develop this site out.
@ Daniel
this is a quiet good addition, i will add "overall memory usage" to the list as another parameter.

So may you both have an idea how we can reach experienced user to fill up this list with information, should we post it in the forum or in the Planet ?

Greetings to all

Erik

Am 09.01.2012 um 03:08 schrieb Michael Tremer:

> Hey,
> 
> I love this idea, too.
> 
> Getting the information by example is much better than formulating
> general guidelines. That's difficult for the author and hard to
> understand for the reader.
> 
> When walking through examples, the user gets an intuition about the
> problem and can grab the important things for his own needs.
> 
> - Michael
> 
> On Sun, 2012-01-08 at 21:53 +0100, WhyTea wrote:
>> Hi Erik!
>> 
>> I think this is a great idea! What about "overall memory usage"? 
>> In my opinion it is a good way to prevent all the "What hardware I
>> need for..."-questions.
>> 
>> Mayby we may create further list for snort or something else.
>> 
>> Daniel
>> 
>> 
>> 
>> Am 08.01.2012 19:42, schrieb Erik K.: 
>>> Hi all, 
>>> i want to introduce a new idea for the proxy wiki and i´am quiet
>>> unsure if this is a good idea, so i need your help and assessment if
>>> we should go for this or better not. 
>>> The idea is:
>>> The "cache management" in squid is a kind of difficult so i thought
>>> that i create a side with example konfig´s from user, in hope that
>>> some experienced guys are filling something in :-) . 
>>> 
>>> 
>>> The categories of configuration examples are:
>>> How many clients Bandwith Amount of fildescriptors: Memory cache
>>> size (MB): Min object size (KB): Number of level-1 subdirectories:
>>> Memory replacement policy: Cache replacement policy: Harddisk cache
>>> size (MB): Max object size (KB):
>>> 
>>> 
>>> So this site can be overviewed in here
>>> --> http://wiki.ipfire.org/nonpublic/de/configuration/network/proxy/example_conf . 
>>> 
>>> 
>>> Supplements and opinions are highly appreciated...
>>> 
>>> 
>>> What do you think about this ?
>>> 
>>> 
>>> Greetings to all
>>> 
>>> 
>>> Erik
>>> 
>>> 
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/documentation
>> 
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation


  reply	other threads:[~2012-01-09 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F0A0255.1030907@ipfire.org>
2012-01-09  2:08 ` Michael Tremer
2012-01-09 14:04   ` Erik K. [this message]
2012-01-12  7:59     ` Erik K.

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=D35B801D-2800-4688-B205-311BCBFF5119@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=documentation@lists.ipfire.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