Package: debian-handbook Version: 6.0+20120509 Severity: minor Hi Raphaël, I've just completed the reading of chapter 12. What follows is my usual list of suggestions/corrections.
Section 12.1.1.1. Different RAID Levels --------------------------------------- Typo? s/differenciated/differentiated/ Section 12.1.2.3. LVM Over Time ------------------------------- At the beginning of the first command transcript, the output of # df -h /srv/files/ seems to be misformatted: there should be a linebreak between "on" and "/dev/mapper/vg_critical-lv_files" Section 12.2.1. Xen ------------------- Typo? s/virtualizaton/virtualization/ Typo? s/distibution/distribution/ | the routing mode I am not sure about this: the three possibilities had been previously called "network models", so maybe s/the routing mode/the routing model/ Similarly s/the NAT mode/the NAT model/ Typo? s/three networking nodes/three networking models/ | After rebooting to make sure the bridge is automatically created Isn't there any less extreme method to let the system create the bridge? I don't know, something like some /etc/init.d/$SERVICE restart or some ifdown/ifup trick? Section 12.2.2. LXC ------------------- Typo? s/It takes advantages/It takes advantage/ Section 12.2.2.2. Network Configuration --------------------------------------- | The "bridge" configuration makes the Ethernet frames on all the | bridged interfaces, which includes the physical eth0 as well as | the interfaces defined for the containers. Maybe I am misreading the sentence, but it seems to me that something is missing. The configuration makes the Ethernet frames on all the bridged interfaces. What does it mean? I would have expected something like + The "bridge" configuration lets the Ethernet frames reach all the + bridged interfaces, which includes the physical eth0 as well as + the interfaces defined for the containers. | The network can then be either be set up statically in the containers, | or dynamically with DHCP server running on the host. I think that this sentence should be rephrased better, maybe as in: + The network can then be set up either statically in the containers, + or dynamically with a DHCP server running on the host. Section 12.2.3. Virtualization with KVM --------------------------------------- It would be worth mentioning a simple command to check that a given CPU has the necessary hardware support to run KVM. Something like $ grep --color 'vmx\|svm' /proc/cpuinfo if I understand http://www.linux-kvm.org/page/Processor_support correctly. Also, the above-cited page seems to state that KVM may be used on some PowerPC and S390 architecture CPUs, as well. It is probably a good idea to update the sentence that says "that KVM only works on i386 and amd64 processors". Section 12.2.3.1. Preliminary Steps ----------------------------------- | apt-get install qemu-kvm libvirt-bin virtinst virtual-manager virt-viewer Typo? s/virtual-manager/virt-manager/ Section 12.2.3.3. Installation with virt-install ------------------------------------------------ Typo? s/differenciating/differentiating/ | The default behaviour for the associated VNC server is no only | listen on the local interface Typo? s/is no only/is to only/ | If not, or if we operate remotely, virt-viewer can be used to run it: | | $ virt-viewer --connect qemu+ssh://root@server/system | root@server's password: | root@server's password: This part is not too clear to me. First of all, "if not" means "if the previous operation was not run from a graphical desktop environment" (correct?); OK, should we issue the following command from a graphical desktop environment? What if we operate remotely? Should we issue the following command from a graphical environment on the host from which we connect to the system where kvm runs? How does the command line change between the two cases (if it changes at all)? Moreover, should "server" be typed literally or replaced by some hostname? Which one? Which root password should be typed in? Why twice? Are we setting a new root password for something here? I think that all these details should be clarified, otherwise the reader may really mess things up during this step... Section 12.2.3.4. Managing Machines with virsh ---------------------------------------------- It is not too clear to me how one can start a virtual machine and connect to it through VNC (immediately or later). "get the connection instructions for the graphical console" looks like an obscure sentence: what does it mean? Is this the command to use to graphically connect to a started virtual machine? What if I want to see it booting from the very beginning? I think these subtleties should be clarified. Section 12.4.1.1. Configuring Hosts To Monitor ---------------------------------------------- | An administrator will usually add a similar line containing | the IP address of the grapher host What if this IP address is not static? Moreover, from a security standpoint: may the host-grapher communication be protected through public key encryption and authentication (using TLS/SSL, for instance)? Section 12.4.1.2. Configuring the Grapher ----------------------------------------- | Each machine is listed as a full section with a name matching the | machine and at least an address entry giving the corresponding | IP address. Again: what if this IP address is not static? Section 12.4.2.2. Configuring ----------------------------- Typo? s/informaton/information/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
