- openSUSE Documentation

[opensuse-doc] Hunting annoying relics from times long gone by: DOS linebreaks
by Jana Jaeger 19 Jun '07

19 Jun '07

Hi fellow-LfLers, just started working on some LfL stuff again (three cheers for the folks who made SLE 10 SP1 finally disappear from our plates) and got pretty annoyed by ^M marks all over the files. It doesn't break files, but visually pollutes them and makes editing XML even less fun than it already is ;) So can we please agree to use editing tools that don't add DOS linebreaks or to run tr -d '\15' < file > clean_file to clean up the files before checking them in? jedit would be a good choice for editors working on any platform, because it can be easily configured to use linebreaks other than DOS. Thanks a million! Jana -- Jana Jaeger jjaeger(a)suse.de SUSE LINUX Products GmbH Documentation Maxfeldstr. 5 +49 (0) 911 74053-0 D-90409 Nuernberg http://www.novell.com/linux SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

1 0

[opensuse-doc] Indexing question
by Clayton 19 Jun '07

19 Jun '07

This is just a general question about indexing. I am working on a large document that is being ported over to Wiki format. One of the printed doc features that has fallen off with the port to Wiki is the index. In traditional documentation, a good index was important. As we move more and more away from traditional doc techniques and go to web based docs we rely on search engines to fill the gap where indexes and index tagging (in traditional tools like Framemaker) are missing. How important are people finding the index in newer doc methods? What can be done to fill that missing indexes for online docs? Especially for online docs (such as Wiki) that can be converted to PDF to deliver a traditional book for people who prefer to read off line? C. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

3 3

[opensuse-doc] Would be "Introduction to PC hardware" suitable for LfL ?
by Alexey Eremenko 09 Jun '07

09 Jun '07

hi all ! I'm thinking: Would be "Introduction to PC hardware" suitable for LfL ? I want to photo individual computer components, explain their functions, write a bit of history, explain some standards such as: PCI, VGA, PC Color'99, ... I can also make very generic recommendation about buying Linux compatible hardware, and explain how-to identify such hardware. This topic is definitely of interest to people, who want to be serious about computers and operating-systems generally. But I don't know if LfL is intended to be software-specific or not... Of course some components I know better than others, so I will explain 'em better. What do you think ? -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

3 2

[opensuse-doc] [STYLE] Virtualization Terminology
by Rebecca Walter 06 Jun '07

06 Jun '07

We have a request from management to standardize our terminology for virtualization technology. They, with input from in-house experts, propose the following terminology. Does anyone know of any reason these terms should not become the standard? I need feedback by the end of the day on 4 June so I can get back to management about implementation. If there are no objections, we can start standardizing on these terms immediately. "virtual host server"--A system running virtualization software that makes it able to host virtual machines. "NetWare virtual machine" "management virtual machine"--The virtual machine used to control the other virtual machines. "hypervisor"--The monitor for virtual machines. "virtual machine"--Not domain or guest. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

4 8

[opensuse-doc] Fwd: Re: More
by Rebecca Walter 06 Jun '07

06 Jun '07

I sent your concerns back to the requestor. He responds with the following. ---------- Forwarded Message ---------- Subject: Re: More Date: Monday 04 June 2007 11:58 From: Marcus Kraft <mkraft(a)suse.de> To: Rebecca Walter <rwalter(a)suse.de>, "Alexey Eremenko" <al4321(a)gmail.com> Am Samstag 02 Juni 2007 21:10 schrieben Sie: Alexey , Rebecca, :) Thats why we try to get to a clear terminology. Alexey favors simple terminology like 'host', which I favour too in verbal communications. However, to provide written documentation and even tables where we display tested and verified combination (for eg. Novell YES certification), I feel the need for precise but still technology agnostic terms. Xen is a Hybrid Hypervisor/VMM, it needs both hypervisor layer and operating system to do its job (and IntelVT / AMD-V for fulvirtualization). Sometimes there is a need to distinguish all of these (hw/vmm/os), and yes, there is a need to be not bounded to the Xen terminology in hopefully all the documents we write for product doc, FAQs, product flyers, support bulletins, certification bulleting, presentations etc ... 'host' and 'virtualization host' will work for most people familiar with virtualization - however if one states 'virtualization host server' it takes the physical hardware into account IMHO - sometimes you what to express that you use a (phys) machine (server) to be the virtualization host. I admit that Linux term server usually refer to network services, but its also used for machine providing the server. Let me add some examples where we would use this terminology, too: virtualzation host server virtual machine x86 + Xen x86 machine + Xen + OS OS in VM IBM POWER PPC + DLPAR OS in VM IBM System z mainframe + LPAR + zVM OS in VM x86 + KVM x86 + Linux + KVM OS in VM x86 + openVZ x86 + Linux + openVZ OS in VM (container) x86 + VMware ESX x86 + ESX (incl. OS) OS in VM x86 + VMware WS x86 + Linux + WS OS in VM (I left out x86-64 and Itanium to reduced list) Hope that make things more clear. Regards Marcus > ---------- Forwarded Message ---------- > > Subject: Re: [opensuse-doc] [STYLE] Virtualization Terminology > Date: Saturday 02 June 2007 12:01 > From: jdd <jdd(a)dodin.org> > To: > Cc: opensuse-doc(a)opensuse.org > > Alexey Eremenko wrote: > > anything, let's as wild as Playstation, for emulation case - usually > > this would be x86 PC) > > usually, not necessarily, gamebox emulators are prosent for age here :-) > > good guess to don't forget them :-) > > jdd > > -- > http://www.dodin.net > http://gourmandises.orangeblog.fr/ > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-doc+help(a)opensuse.org > > ------------------------------------------------------- > > > ---------- Forwarded Message ---------- > > Subject: Re: [opensuse-doc] [STYLE] Virtualization Terminology > Date: Saturday 02 June 2007 11:34 > From: "Alexey Eremenko" <al4321(a)gmail.com> > To: opensuse-doc(a)opensuse.org > > According to my basic terminology: > *Host > > Your real computer, on which the emulator/virtualizer software runs. > > Host means both your real hardware and the operating system that > controls that hardware. > In some cases there can be only hardware without operating system, > like VMware ESX. > > The term "Host" describes both hardware and OS. > > This can be devided to: > *Host Hardware - your real hardware > *Host Operating System - the operating system that controls that real > hardware. > > *Guest (also known as VM=Virtual Machine) > > Your emulated computer, virtual machine, or VM for short, this is > what you are trying to emulate. Your target. It can be the same, or > very different from your real system. > > For example, your host can be a Pentium III PC, while your guest > can be a Sony Playstation. Of course, VirtualBox cannot emulate > Playstations, so look at different software. It's just important that > you understand those two basic concepts. > > -This means both your virtual hardware _and_ an operating system that > runs on your virtual hardware. > > This can be devided to: > Guest Hardware - your virtual hardware (can be > anything, let's as wild as Playstation, for emulation case - usually > this would be x86 PC) > Guest Operating System - your OS, that runs on the virtual hardware. > (can be anything, let's as wild as Playstation BIOS - but usually > this would be Windows or Linux OS) > > *Hyperviser/Virtualizer > Software that does (Full/Para) virtualization. > > *Hypercall > Just like there are system calls, For para-virtual cases there are > hyper calls. Actually a language between the para-virtualizer > (hyperviser) and guest. > Other types of virtualization doesn't use hypercalls. > > Your term "virtual machine server" would be confusing. This is because > the "server" term has usually something to do with networking, while > virtualization can work nicely without networks, listening TCP ports, > etc... > Let's leave the term "server" to the programs that listen to TCP ports. > Now if I understand you correctly, your term "virtual machine server" > equals to my term "Host hardware" or "Host". > > Additionally, those terms I just described are a LOT shorter than your > terms, plus they are more accurate. > It's a lot better to have accurate and short terms at once. > > -- > -Alexey Eremenko "Technologov" > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-doc+help(a)opensuse.org > > ------------------------------------------------------- > > > ---------- Forwarded Message ---------- > > Subject: Re: [opensuse-doc] [STYLE] Virtualization Terminology > Date: Saturday 02 June 2007 08:42 > From: jdd <jdd(a)dodin.org> > To: > Cc: opensuse-doc(a)opensuse.org > > Rebecca Walter wrote: > >> Virtual machine 1, virtual machine 2 two different (virtualized) > >> computers guest: Linux, XP, W98, dos, freebsd... > > > > there wouldn't be "guest" used here, if I have understood properly. It > > would be a virtual machine running whatever OS. > > I think the "guest" concept is important, mostly if the host OS and > the virtual machine OS are the same. > > It's difficult to say anytime "openSUSE 10.3 on the host", "openSUSE > 10.3 on the virtual machine" > > in fact, I don't know what make difference between various guests fir > the virtual machine, but as VMware as Virtual box asks for what guest > you want at creation time (even is you can change mind afterward) > > jdd > > -- > http://www.dodin.net > http://gourmandises.orangeblog.fr/ > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-doc+help(a)opensuse.org > > ------------------------------------------------------- -- Mit freundlichen Gruessen / Best regards, Marcus Kraft (mkraft(a)novell.com) -- Marcus Kraft, Product Manager, SUSE Linux Enterprise, Virtualization fon: +49 911 74053-171 - fax: +49 911 74053-483 - email: mkraft(a)novell.com SUSE® Linux Enterprise 10 - Your Linux is ready - http://www.novell.com/linux/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 4

[opensuse-doc] LfL doesn't compiles on openSUSE 10.3 a4!
by Alexey Eremenko 25 May '07

25 May '07

Hi all ! LfL doesn't compiles on openSUSE 10.3 alpha 4! Packages: alexey@opensuse103a4:~/LfL/books/en> rpm -q susedoc susedoc-4.2_20070321-1 alexey@opensuse103a4:~/LfL/books/en> rpm -q fop fop-0.20.5-121 alexey@opensuse103a4:~/LfL/books/en> rpm -qa | sort | grep -i java java-1_5_0-sun-1.5.0_update11-15 java-1_5_0-sun-plugin-1.5.0_update11-15 I got the full LfL: svn checkout https://forgesvn1.novell.com/svn/lfl/trunk LfL I did: make html The error: Writing html/lessons4lizards/ln-id2583250.html for legalnotice runtime error: file file:///usr/share/xml/docbook/stylesheet/nwalsh/1.72.0/lib/lib.xsl line 212 element value-of Internal error in xsltValueOf(): failed to cast an XPath object to string. make: *** [html/lessons4lizards/index.html] Error 10 Anybody has the same problem ? -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 3

[opensuse-doc] [STYLE] Installation Source vs. Repository
by Rebecca Walter 23 May '07

23 May '07

Here is a reminder of the pros and cons of the two primary options. Although we had some other suggestions, none seemed to offer any improvement over these two choices: Installation Source ------------------- Advantages ---------- Likely to be understandable to new users (installation source=source of installation=what you install from) Applicable to any acceptable installation media or other format, including future development Familiar to long-time SUSE users Less work to implement (already used in documentation and in large parts of YaST) Disadvantages ------------- Possible confusion with program sources Repository or Software Repository --------------------------------- Advantages ---------- Used in some non-SUSE tools Familiar to users from other distros Disadvantages ------------- Possible confusion with SVN or CVS repository Meaning not clear to users coming from Windows or MacOS or that are new to computers Connection to one specific type (there are valid options that don't have repo directories) Requires extensive changes in documentation and software Would conflict with YaST source code (this _is_ a real disadvantage because it makes the code more confusing and it is a goal to have readable YaST code) Definitions don't seem very applicable to CD and DVD media ***** It is pretty clear from this list that "installation source" is the best option we have at this time. Of the many repositories available online, some are valid installation sources for SUSE but some are not. To help users familiar with the repository terminology or looking for installation sources, I recommend that we mention repositories as one of possible types of installation sources in help texts of the relevant applications and in the manuals. "Installation source" should be used to refer to all resources that serve as valid sources for installation of the entire system or packages using the standard package management systems of SUSE Linux and openSUSE. It is the only term for these resources that should be used in the UI of applications. I will make the appropriate changes to the style guides. Unfortunately, 10.3 is likely to be a transitional release, so we may have inconsistencies in this version. If other terms appear in our applications or documentation for 10.3 betas and later, please file enhancement or minor bug reports to remind the developers to fix these issues. Alpha versions are very unlikely to have the changes. Sincerely, Rebecca Walter Style Guide Maintainer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

1 0

[opensuse-doc] LfL: Roles
by Thomas R. Jones 22 May '07

22 May '07

Hello all, I have been reviewing the LfL project over the last few days. It seems the project is in its infancy but shows promise. How has the process of editing been handled? I have noticed a considerable amount of broken English --- as is commonly the case when an individual writes in a secondary language. Although I can understand the meanings, the sentence presentation makes it rather difficult for a reader to comprehend. How would I be able to extend to the community my hand as an editor? I feel very comfortable wearing both the author and editorial hats; but definitely would like to refrain from "stepping on any toes" so to speak. Also, there are a few topics that I began to write for fedora that I would like to go ahead and present to the opensuse community as well: Securing Filesystems Host Integrity Monitoring Installation of OVAL Installation of XSDL OVAL Administration Digitally signed and encrypted firewall rulesets If anyone would like to work in conjunction with me on these topics or similar topics, just email me. Thanks you all for your time. Thomas

4 4

[opensuse-doc] lfl: New chapter on digikam magic
by Jana Jaeger 21 May '07

21 May '07

Hey fellow LfLers, I am planning on writing a sort of digikam tutorial to complement the digikam chapter we have in the openSUSE docs which is much more of an overview than a tutorial. Question is - what to include to make this worthwile. So far I have: Importing Images download from camera, import folders, scanner Fixing and Tweaking hot pixels, red eyes, some distortion correction Managing Colors some theory on Histograms, Color curves, white balance etc. plus how to use those to make your images work Applying Effects Composition and Cropping Some general blurb on composition, a few links for the gory details (I'd be grateful if any of you sent me some I might not know) plus digikams cool crop assistant Batch Processing Images RAW Image Conversion Exporting Your Image Collection flickr etc. What else should I add to make this a comprehensive walkthrough to image processing with digikam? Any ideas? Cheers, Jana -- Jana Jaeger jjaeger(a)suse.de SUSE LINUX Products GmbH Documentation Maxfeldstr. 5 +49 (0) 911 74053-0 D-90409 Nuernberg http://www.novell.com/linux SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

5 14

[opensuse-doc] How-to emulate mouse via keyboard ?
by Alexey Eremenko 20 May '07

20 May '07

Anybody knows anything about Mouse emulation in X ? (via keyboard) I was able to find this: http://club.mandriva.com/xwiki/bin/view/KB/XwinXmouse But it lacks ability to right-click and no ability to change mouse speed. This is important to find, because I would like to document this feature of Linux. I sometimes work with very bad mice. -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 1