Documentation February 2015

documentation@lists.ipfire.org

5 participants
7 discussions

Xen IPFire
by R. W. Rodolico 20 Feb '15

20 Feb '15

I have created a whole section on virtualization. It is all in English (sorry). If you will start at: http://wiki.ipfire.org/en/start and click on the Virtualization entry (bottom entry), I would appreciate any comments on it. I intend to collect the other virtualization articles into this one container. Markus, I would love to see your article and do what I can to translate it. I have a friend who speaks/reads/writes German (I don't know how well), and I can work out some of it. Rod -- "Rod" Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net

2 3

Re: AW: Xen Documentation
by Michael Tremer 20 Feb '15

20 Feb '15

Hi Markus, your emails are rejected by the list because you are sending them from a different email address you are not subscribed with. It sent you an invitation for the other email address. On Fri, 2015-02-20 at 09:17 +0100, Markus Helmke wrote: > Michel, i'm right with you. I've still some Ubuntu PV working, but > everything else I transverred to HVM and I can not mention that this > isn't felt slower than PV. On plus - Its easyer to handle things like > pci-passthrough. And on top there are spezial drivers, for example for > Windows they can be downloaded from Univention, which speeds up > Network- and Disk-Performance There are still some Benchmarks where pv > is working faster. Great that you can deliver some facts to my assumptions. The only downside I forgot to mention is that you will need a CPU that supports virtualization. I guess that nowadays nobody is using a processor that doesn't support that because they are slow and consume too much energy. -Michael > > > > > > > Viele Grüße, > > Markus Helmke > > Mail: markus(a)helmke.at <mailto:markus@helmke.at> > > > > -----Ursprüngliche Nachricht----- > > Von:Michael Tremer <michael.tremer(a)ipfire.org> > > Gesendet: Fre 20 Februar 2015 02:05 > > An: R. W. Rodolico <rodo(a)dailydata.net> > > CC: documentation(a)lists.ipfire.org >> Wiki Mailingliste <documentation(a)lists.ipfire.org> > > Betreff: Re: Xen Documentation > > > > Hi, > > > > On Tue, 2015-02-17 at 16:48 -0600, R. W. Rodolico wrote: > > > FYI, a brief (and hopefully accurate) reply to your questions. > > > > > > paravirtualization (PV) uses the kernel from the underlying DOM0 (the OS > > > running on the bare machine, which runs everything else). > > > > > > Hardware virtualization (HVM) is completely divorced from the underlying > > > operating system. Instead, it uses its own kernel and some fake hardware > > > exported by the underlying system. > > > > > > PV's are much faster since one kernel controls everything. The kernel is > > > able to direct resource usage without any intermediate layer. However, > > > you must keep the virtual and the underlying system in sync. One thing I > > > remember is every time you upgrade the kernel on the DOM0, you must copy > > > the new lib's to every virtual. Obviously, you can not run non-Linux > > > systems on a PV. To move a PV from one DOM0 to another, the kernel's and > > > libraries must match, or you need to copy the libraries to the virtual > > > before running it. > > > > > > HVM's have a layer between them and the underlying kernel. I think that > > > is QEMU, but I don't remember. Since it has to go through a second > > > translation layer, it uses more resources. However, you can have a 2.4 > > > kernel on the DOM0, and be running the latest kernel on the virtual, or > > > even Windows, BSD or OSX. HVM's can be moved between DOM0's with little > > > or no modification (generally a small line in the config file). > > > > All the hypervisors we have base on QEMU. VMware put it in their kernel. > > VirtualBox is still using userspace but have added lots of graphics > > features. The Xen project put it in a micro kernel. Of course lots of > > development has been put in all of these projects and therefore they > > diverged a lot. > > > > > For IPFire, I prefer HVM's because you have spent so much time making > > > sure the kernel and libraries are secure. Thus, even on an older DOM0, I > > > can have a very secure firewall/router. However, some things such as > > > automated shutdown of the IPFire instance are not available since IPFire > > > does not include the HVM device drivers (they use a generic device > > > driver when IPFire is installed). That can cause a problem during server > > > shutdown, since the backup is to "destroy" the virtual, ie pull the plug. > > > > I think that we should have a short mentioning that the HVM version is > > the preferred one then. It is actually not that much slower any more. > > CPUs do everything in regards of their jobs. Some devices needs to be > > emulated which causes a bit more overhead yes. In perspective though > > IPFire does not read or write a lot of data from/to disk so that there > > will never be a bottleneck on that end. The virtual network drivers have > > also a negligible overhead. > > > > The PV approach comes with way more difficulties and I guess that HVM is > > most used any way. > > > > > As far as I know, tying a physical piece of hardware to a single DOMU is > > > still supported, though I have not used that since 3.x, > > > http://wiki.xenproject.org/wiki/XenPCIpassthrough indicates it is still > > > available. > > > > Maybe someone else can contribute this later. > > > > > > > > Rod > > > > > > On 02/17/2015 10:05 AM, Michael Tremer wrote: > > > > Hi, > > > > > > > > if I may send you a little wishlist: > > > > > > > > There are many many guides about how to set up a Xen server with Debian. > > > > I am not sure about the state of all of them. Some of them are based on > > > > outdated versions of Debian. I suppose it is best to merge them all > > > > together and delete the rest. > > > > > > > > http://wiki.ipfire.org/start?do=search&id=xen > > > > > > > > Maybe it is a good idea to start a little virtualisation section > > > > (http://wiki.ipfire.org/en/virtualization/start) with subsections for > > > > Xen (http://wiki.ipfire.org/en/virtualization/xen/start), KVM and all > > > > the rest. > > > > > > > > Explaining an installation of the IPFire system from scratch should not > > > > be necessary but the differences to using Xen should be pointed out > > > > somewhere. > > > > > > > > I personally am always confused about the HVM and PV thing. What should > > > > people use? What are the advantages/disadvantages? > > > > > > > > There was also this: > > > > > > > > http://planet.ipfire.org/post/dropping-support-for-xen-3-x-deprecation-warn… > > > > http://planet.ipfire.org/post/bye-bye-xen-legacy-kernel > > > > > > > > Many people use the feature where you can hand over the physical > > > > hardware to the guest machine. Does this actually still work? What are > > > > the benefits of that? > > > > > > > > All this information should be out there somewhere in the wiki. Putting > > > > it all together in a nice section with small pages which are easy to > > > > find would be really great :) > > > > > > > > -Michael > > > > > > > > On Tue, 2015-02-17 at 03:10 -0600, R. W. Rodolico wrote: > > > >> David, > > > >> > > > >> It would be great if you could get some notes on this. Even if they are > > > >> rough, it would be better than nothing. Having never messed with KVM > > > >> (I'm Debian/Xen for the most part), I really don't know much about it, > > > >> though I do engage in "religious wars" over KVM vs Xen vs Virtual Box > > > >> with from friends/associates of mine. > > > >> > > > >> Anyway, if you had some brief notes, it would be great to include them. > > > >> > > > >> Rod > > > >> > > > >> On 02/16/2015 11:07 PM, David J. Allen wrote: > > > >>> On 02/16/2015 08:11 PM, R. W. Rodolico wrote: > > > >>>> I am in the process of creating documentation for a Xen virtual IPFire > > > >>>> install. If anyone else is doing it also, please let me know so we can > > > >>>> collaborate. I'm hopeful to have it complete Friday 20 Feb. > > > >>>> > > > >>>> I am trying an install using the scon image. Assuming that works, should > > > >>>> I also write documentation on how to do it from a standard "installer" > > > >>>> installation? > > > >>>> > > > >>>> Again, if anyone else is doing this, please let me know so we do not > > > >>>> duplicate efforts. > > > >>>> > > > >>>> Rod > > > >>> > > > >>> I am not writing docs on doing so* but I have been running Ipfire in a > > > >>> VM under KVM on Scientific Linux 6.x for a couple of years now. I think > > > >>> setting up Ipfire was easier than getting the KVM set up right. > > > >>> > > > >>> The VM host box has 2 onboard NICs, but I'm using a dual-NIC card in the > > > >>> box which is dedicated to the Ipfire VM. The tricky part was figuring > > > >>> out how to give Ipfire exclusive access to the WAN NIC without it being > > > >>> accessible to the KVM host and the other VM guests. > > > >>> > > > >>> > > > >>> * Although I should do it at least for myself - had to redo my > > > >>> installation a while back after moving and had left no notes for myself. > > > >>> Which of course resulted in re-inventing my own wheel! ;) > > > >>> > > > >>> > > > >>> _______________________________________________ > > > >>> 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 > >

1 0

Xen Documentation
by R. W. Rodolico 20 Feb '15

20 Feb '15

I am in the process of creating documentation for a Xen virtual IPFire install. If anyone else is doing it also, please let me know so we can collaborate. I'm hopeful to have it complete Friday 20 Feb. I am trying an install using the scon image. Assuming that works, should I also write documentation on how to do it from a standard "installer" installation? Again, if anyone else is doing this, please let me know so we do not duplicate efforts. Rod -- "Rod" Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net

3 6

Replacement for Dokuwiki
by R. W. Rodolico 20 Feb '15

20 Feb '15

I have a tech who is wanting additional hours, and she is a fairly good researcher. I'd like to put her on the project of finding a replacement for Dokuwiki. However, before I do, I'd really like to know what we want it to do. Here are my thoughts. Please feel free to say "yes" or "no" to anything. My feelings will not be hurt. But, I do want Brandy (the tech) to have a clear cut set of requirements before she puts in the time. Requirements: * HTML * Multilevel tree menu * Keyword searchable * Full text searchable * User management * Multi-language capable Nice to have * WYSIWYG editor * Export all or part to PDF or HTML * Comments on articles (similar to php.net) Anyway, anyone want to add/remove/modify the above? Also, does anyone have a favorite package I should have her look into? Rod -- "Rod" Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net

2 3

Re: AW: AW: Xen Documentation
by Michael Tremer 19 Feb '15

19 Feb '15

@Markus: Please make sure that you always reply to the list as well. I am not entirely sure why this post is so broken, but one of the reason is that you linked some images from other posts. I recovered some of them and will send the privately to you to avoid too much traffic on the list. Maybe you can still use them. -Michael On Wed, 2015-02-18 at 08:46 +0100, Markus Helmke wrote: > First Draft was to write it down in the Forum > > > > http://forum.ipfire.org/viewtopic.php?f=14&t=10888 > > > > > > > Viele Grüße, > > Markus Helmke > > Mail: markus(a)helmke.at <mailto:markus@helmke.at> > > > > -----Ursprüngliche Nachricht----- > > Von:Michael Tremer <michael.tremer(a)ipfire.org> > > Gesendet: Die 17 Februar 2015 17:47 > > An: Markus Helmke <markus(a)helmkeweb.de> > > CC: R. W. Rodolico <rodo(a)dailydata.net>; documentation(a)lists.ipfire.org > > Betreff: Re: AW: Xen Documentation > > > > Hi, > > > > about which page are you talking? I could not find the right one I > > think. > > > > -Michael > > > > On Tue, 2015-02-17 at 17:30 +0100, Markus Helmke wrote: > > > My Dokumentation was made for the actual Ubuntu Server 14.04 LTS > > > version. > > > > > > There where some changes in order to the implemented XEN-Version. The > > > letest Debian stable (wheezy) is layouted with XEN 4.0 or 4.1 (im not > > > shure). > > > In Ubuntu some of the latest packet-changes was to implement the new XEN 4.4 The default stack is now xl (4.0 was xm) so there are some changes in the configs. Now it is possible to use the configfiles in the /etc/default section to start the xen-kernel or to implement boot-parameters. > > > > > > But everything from the new Xen-Version is explained in my doku. Since the forum was replaced to the new forum-software the links to images are lost. > > > > > > So if I can do somthing Or write something new - I can do that. But the challenge to write that down in english is to big for me. It will takes to much time for me. But perhaps there will be found someone else how can translate that. > > > > > > Viele Grüße, > > > > > > Markus Helmke > > > > > > Mail: markus(a)helmke.at <mailto:markus@helmke.at> > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von:Michael Tremer <michael.tremer(a)ipfire.org> > > > > Gesendet: Die 17 Februar 2015 17:06 > > > > An: R. W. Rodolico <rodo(a)dailydata.net> > > > > CC: documentation(a)lists.ipfire.org > > > > Betreff: Re: Xen Documentation > > > > > > > > Hi, > > > > > > > > if I may send you a little wishlist: > > > > > > > > There are many many guides about how to set up a Xen server with Debian. > > > > I am not sure about the state of all of them. Some of them are based on > > > > outdated versions of Debian. I suppose it is best to merge them all > > > > together and delete the rest. > > > > > > > > http://wiki.ipfire.org/start?do=search&id=xen > > > > > > > > Maybe it is a good idea to start a little virtualisation section > > > > (http://wiki.ipfire.org/en/virtualization/start) with subsections for > > > > Xen (http://wiki.ipfire.org/en/virtualization/xen/start), KVM and all > > > > the rest. > > > > > > > > Explaining an installation of the IPFire system from scratch should not > > > > be necessary but the differences to using Xen should be pointed out > > > > somewhere. > > > > > > > > I personally am always confused about the HVM and PV thing. What should > > > > people use? What are the advantages/disadvantages? > > > > > > > > There was also this: > > > > > > > > http://planet.ipfire.org/post/dropping-support-for-xen-3-x-deprecation-warn… > > > > http://planet.ipfire.org/post/bye-bye-xen-legacy-kernel > > > > > > > > Many people use the feature where you can hand over the physical > > > > hardware to the guest machine. Does this actually still work? What are > > > > the benefits of that? > > > > > > > > All this information should be out there somewhere in the wiki. Putting > > > > it all together in a nice section with small pages which are easy to > > > > find would be really great :) > > > > > > > > -Michael > > > > > > > > On Tue, 2015-02-17 at 03:10 -0600, R. W. Rodolico wrote: > > > > > David, > > > > > > > > > > It would be great if you could get some notes on this. Even if they are > > > > > rough, it would be better than nothing. Having never messed with KVM > > > > > (I'm Debian/Xen for the most part), I really don't know much about it, > > > > > though I do engage in "religious wars" over KVM vs Xen vs Virtual Box > > > > > with from friends/associates of mine. > > > > > > > > > > Anyway, if you had some brief notes, it would be great to include them. > > > > > > > > > > Rod > > > > > > > > > > On 02/16/2015 11:07 PM, David J. Allen wrote: > > > > > > On 02/16/2015 08:11 PM, R. W. Rodolico wrote: > > > > > >> I am in the process of creating documentation for a Xen virtual IPFire > > > > > >> install. If anyone else is doing it also, please let me know so we can > > > > > >> collaborate. I'm hopeful to have it complete Friday 20 Feb. > > > > > >> > > > > > >> I am trying an install using the scon image. Assuming that works, should > > > > > >> I also write documentation on how to do it from a standard "installer" > > > > > >> installation? > > > > > >> > > > > > >> Again, if anyone else is doing this, please let me know so we do not > > > > > >> duplicate efforts. > > > > > >> > > > > > >> Rod > > > > > > > > > > > > I am not writing docs on doing so* but I have been running Ipfire in a > > > > > > VM under KVM on Scientific Linux 6.x for a couple of years now. I think > > > > > > setting up Ipfire was easier than getting the KVM set up right. > > > > > > > > > > > > The VM host box has 2 onboard NICs, but I'm using a dual-NIC card in the > > > > > > box which is dedicated to the Ipfire VM. The tricky part was figuring > > > > > > out how to give Ipfire exclusive access to the WAN NIC without it being > > > > > > accessible to the KVM host and the other VM guests. > > > > > > > > > > > > > > > > > > * Although I should do it at least for myself - had to redo my > > > > > > installation a while back after moving and had left no notes for myself. > > > > > > Which of course resulted in re-inventing my own wheel! ;) > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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 > > > > > >

1 0

Re: AW: Xen Documentation
by Michael Tremer 17 Feb '15

17 Feb '15

Hi, about which page are you talking? I could not find the right one I think. -Michael On Tue, 2015-02-17 at 17:30 +0100, Markus Helmke wrote: > My Dokumentation was made for the actual Ubuntu Server 14.04 LTS > version. > > There where some changes in order to the implemented XEN-Version. The > letest Debian stable (wheezy) is layouted with XEN 4.0 or 4.1 (im not > shure). > In Ubuntu some of the latest packet-changes was to implement the new XEN 4.4 The default stack is now xl (4.0 was xm) so there are some changes in the configs. Now it is possible to use the configfiles in the /etc/default section to start the xen-kernel or to implement boot-parameters. > > But everything from the new Xen-Version is explained in my doku. Since the forum was replaced to the new forum-software the links to images are lost. > > So if I can do somthing Or write something new - I can do that. But the challenge to write that down in english is to big for me. It will takes to much time for me. But perhaps there will be found someone else how can translate that. > > Viele Grüße, > > Markus Helmke > > Mail: markus(a)helmke.at <mailto:markus@helmke.at> > > > > -----Ursprüngliche Nachricht----- > > Von:Michael Tremer <michael.tremer(a)ipfire.org> > > Gesendet: Die 17 Februar 2015 17:06 > > An: R. W. Rodolico <rodo(a)dailydata.net> > > CC: documentation(a)lists.ipfire.org > > Betreff: Re: Xen Documentation > > > > Hi, > > > > if I may send you a little wishlist: > > > > There are many many guides about how to set up a Xen server with Debian. > > I am not sure about the state of all of them. Some of them are based on > > outdated versions of Debian. I suppose it is best to merge them all > > together and delete the rest. > > > > http://wiki.ipfire.org/start?do=search&id=xen > > > > Maybe it is a good idea to start a little virtualisation section > > (http://wiki.ipfire.org/en/virtualization/start) with subsections for > > Xen (http://wiki.ipfire.org/en/virtualization/xen/start), KVM and all > > the rest. > > > > Explaining an installation of the IPFire system from scratch should not > > be necessary but the differences to using Xen should be pointed out > > somewhere. > > > > I personally am always confused about the HVM and PV thing. What should > > people use? What are the advantages/disadvantages? > > > > There was also this: > > > > http://planet.ipfire.org/post/dropping-support-for-xen-3-x-deprecation-warn… > > http://planet.ipfire.org/post/bye-bye-xen-legacy-kernel > > > > Many people use the feature where you can hand over the physical > > hardware to the guest machine. Does this actually still work? What are > > the benefits of that? > > > > All this information should be out there somewhere in the wiki. Putting > > it all together in a nice section with small pages which are easy to > > find would be really great :) > > > > -Michael > > > > On Tue, 2015-02-17 at 03:10 -0600, R. W. Rodolico wrote: > > > David, > > > > > > It would be great if you could get some notes on this. Even if they are > > > rough, it would be better than nothing. Having never messed with KVM > > > (I'm Debian/Xen for the most part), I really don't know much about it, > > > though I do engage in "religious wars" over KVM vs Xen vs Virtual Box > > > with from friends/associates of mine. > > > > > > Anyway, if you had some brief notes, it would be great to include them. > > > > > > Rod > > > > > > On 02/16/2015 11:07 PM, David J. Allen wrote: > > > > On 02/16/2015 08:11 PM, R. W. Rodolico wrote: > > > >> I am in the process of creating documentation for a Xen virtual IPFire > > > >> install. If anyone else is doing it also, please let me know so we can > > > >> collaborate. I'm hopeful to have it complete Friday 20 Feb. > > > >> > > > >> I am trying an install using the scon image. Assuming that works, should > > > >> I also write documentation on how to do it from a standard "installer" > > > >> installation? > > > >> > > > >> Again, if anyone else is doing this, please let me know so we do not > > > >> duplicate efforts. > > > >> > > > >> Rod > > > > > > > > I am not writing docs on doing so* but I have been running Ipfire in a > > > > VM under KVM on Scientific Linux 6.x for a couple of years now. I think > > > > setting up Ipfire was easier than getting the KVM set up right. > > > > > > > > The VM host box has 2 onboard NICs, but I'm using a dual-NIC card in the > > > > box which is dedicated to the Ipfire VM. The tricky part was figuring > > > > out how to give Ipfire exclusive access to the WAN NIC without it being > > > > accessible to the KVM host and the other VM guests. > > > > > > > > > > > > * Although I should do it at least for myself - had to redo my > > > > installation a while back after moving and had left no notes for myself. > > > > Which of course resulted in re-inventing my own wheel! ;) > > > > > > > > > > > > _______________________________________________ > > > > 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 > >

1 0

Restructuring of the hardware section (i.e. removing duplicate/obsolete stuff)
by Michael Tremer 17 Feb '15

17 Feb '15

Hello, I am writing this to you just because things need to be said. It might be that not everyone who reaches this email is the right person who should read this, but nevertheless I am annoyed. I am deeply annoyed with the state the wiki is in and I have been annoyed for a long long time. There is so much documentation in there that is either in a bad state, is completely outdated or is now just wrong. I often stated that I am willing to tolerate if there is information missing in one or the other of all the languages, but when it comes to a point where people are more confused by the documentation than it helps them... we need to do something. Last night, I restructured the entire hardware section. It was really bad. Especially information about the various ARM hardware that is supported was all over the place. Some pages have been there twice with completely different things on them. Some had their own section. The result of that is that the landing page of the hardware section (http://wiki.ipfire.org/en/hardware/start) was stripped to the bare essentials in my opinion. What are the requirements? What hardware should I use? Examples? Done. Some things that have been on the very long page before were just moved to a sub-page. I find it very important to explain why certain decisions where made and what reasons are behind something. But having all that on the first page is not helping. People don't read long texts if they are searching for a particular thing. If someone is interested in more detail he or she will search for that any way. So the landing page shows the recommended hardware specification. All other information about that can be found over here: http://wiki.ipfire.org/en/hardware/requirements Then I created a section which just handles the ARM hardware: http://wiki.ipfire.org/en/hardware/arm/start As mentioned before, there is no new information. This is just all the information collected from the rest of the wiki and restructured. The key element here is a table with all the hardware we support (or explicitly do not support). I figured that this is the most important information that the users are searching for. If you click on one of the boards, you will find additional information. Those pages are not the best and explain how to install an ARM board over and over again. That is good for now, but needs to be cleaned up as well in the near future. I am telling you this because I want you (who ever is interested) to understand what I have in mind when I write these things. It may not the best thing, but I have some points why I am doing it like I do it and may be you can adopt some of them, too. Clean design and clear structure is hugely important. This wiki holds so much information about IPFire that almost every questions can be answered. The problem with that is that it is very hard to find at times. If you know what you are searching for you will find the right page very quickly. If you are searching for something for the first time with no background information, you are practically screwed. So to bring this all to a point: I am very much inclined to delete huge parts of the documentation. I find it much better to have no information at all instead of providing the users with wrong information. Wrong could also mean just outdated or obsolete. A few examples: We don't need pages which say "English version coming soon". This has been there since 2013. http://wiki.ipfire.org/en/addons/virtualisation/howto/debian_wheezy_xen_4.1 We also do not need installation guides for outdated software (here Debian). If anybody is going to install a virtualization host, they should certainly start with the current stable version. So either this needs to be updated or removed. http://wiki.ipfire.org/en/addons/virtualisation/howto/debian_xen_4.x Why did someone even start writing a separate page for Wheezy (only in German) when there was already a page about the same topic with Squeeze? I imagine this has happened because the author was unaware of the existence of the one page. This is just one of the many examples I can bring here and I should point out that I am not at all disappointed with the work many people have done here. There is only something massively wrong with how it is maintained. Outdated information isn't worth a penny. There is a third page about the same topic handling Debian Lenny. Someone added a notes that this page is outdated. At this point I cannot imagine something else but deleting all of this. http://wiki.ipfire.org/de/addons/virtualisation/howto/debian_als_dom0_xen The other topic that is the missing translation is the firewall section. Since almost a year now there is a completely rewritten firewall GUI. Nothing looks the same any more and some parts have become more difficult to use. Hence we wrote a very decent firewall documentation which no one ever translated into any other language. It has been pointed out several times on the forums and many people made promises to actually do something about it. No one ever did. It was not even started. I cannot help it thinking that there is just no interest in having a German translation. Many people argue often that it is important to keep documentation accessible in various languages and I completely agree with that. But if nobody cares doing the work I can not take you and your point serious. I am especially picking on the German translation as we have a huge community of people who are speaking German. The translations of the other languages are not very much advanced so that people don't read these at all and even if they do, there is not so much outdated information in there (the installation works the same since years for instance). So in the end there must be consequences. I am not sure about what is the right way - quite possibly is there no right way of doing this. But seriously guys, we cannot keep doing this in this way we are doing it right now. That is dangerous. I wonder if someone has something to say about this matter. I would be happy to hear from you all. There are over 50 people subscribed to this list. So I will take silence as an answer. Best, -Michael

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Documentation February 2015