diff --git a/LDP/howto/docbook/Disk-on-Chip-HOWTO/Disk-on-Chip-HOWTO.xml b/LDP/howto/docbook/Disk-on-Chip-HOWTO/Disk-on-Chip-HOWTO.xml index e7735b27..f7aa9334 100644 --- a/LDP/howto/docbook/Disk-on-Chip-HOWTO/Disk-on-Chip-HOWTO.xml +++ b/LDP/howto/docbook/Disk-on-Chip-HOWTO/Disk-on-Chip-HOWTO.xml @@ -387,7 +387,7 @@ Fail safe Boot ROM [Disabled] Even though Step 1 and Step 2 seem to be the same, the only difference being that Step 1 is done from Linux and Step 2 from Windows XP, they both have to be done. -Step 3: Patch and Compile the kernel 2.4.18 +Step 3: Patch and Compile the kernel 2.4.18 This has to be performed in exactly the same manner as described in and . Also add an entry for the new kernel in /boot/grub/menu.lst as described in . @@ -506,7 +506,7 @@ fl: _init:registed device at major 62 Step 11: Compile lilo-22.3.2 We are going to use LILO as the boot loader since this is the only BootLoader that can read an INFTL device without many changes to be done to the BootLoader source code. -For more information on how LILO and other boot loaders operate, refer to . +For more information on how LILO and other boot loaders operate, refer to . We need to compile the lilo-22-3.2 source code to get the executable file for LILO. We will use the source code from linux_binary.5_1_4/doc-linux-5_1_4_20/lilo/lilo-22.3.2. Before starting the build we need to do the following: diff --git a/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml b/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml index 6c276077..161baded 100644 --- a/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml +++ b/LDP/howto/docbook/Font-HOWTO/Font-HOWTO.xml @@ -1,7 +1,7 @@ -
+
Optimal Use of Fonts on Linux @@ -15,12 +15,12 @@ Avi Alkalay - avi unix sh - Linux, Open Standards consultant :: IT and Software Architect IBM Linux Impact Team :: ibm.com/linux + Linux, Open Standards consultant :: IT and Software Architect + avi unix sh Donovan @@ -68,8 +68,10 @@ 2005-07-19 19 May 2005 avi - Renamed Microsoft Fonts to Webcore Fonts, and links updated. - Added X.org Subsystems section. + + Renamed Microsoft Fonts to Webcore Fonts, and links updated. + Added X.org Subsystems section. + 2005-05-25 @@ -81,25 +83,31 @@ 2005-05-10 10 May 2005 avi - Old section-based glossary converted to real DocBook glossary. - Modernized terms and explanations on the glossary. - Included concepts as charsets, Unicode and UTF-8 in the glossary. + + Old section-based glossary converted to real DocBook glossary. + Modernized terms and explanations on the glossary. + Included concepts as charsets, Unicode and UTF-8 in the glossary. + 2005-03-31 31 Mar 2005 avi - Desktop configuration guidelines improved for higher resolution screens. - Better layout for authors. + + Desktop configuration guidelines improved for higher resolution screens. + Better layout for authors. + 2005-02-18 18 Feb 2005 avi - Included BCI support status for Mandrake and Gentoo. - Added link to Firefox configuration hack. - Included link to Scribus site. - Removed broken and outdated info links. + + Included BCI support status for Mandrake and Gentoo. + Added link to Firefox configuration hack. + Included link to Scribus site. + Removed broken and outdated info links. + 2005-01-12 @@ -117,25 +125,31 @@ 2004-12-12 12 Dec 2004 avi - Typos correction by Scott Brayban (sgrayban borgnet us). - Finished links to msfonts and freetype RPMs. + + Typos correction by Scott Brayban (sgrayban borgnet us). + Finished links to msfonts and freetype RPMs. + 2004-12-05 5 Dec 2004 avi - Merged with FDU-HOWTO. - Finished RPM sections. - Added "need help" appendix. - Finished "About this doc" appendix. - Ready for peer revision. + + Merged with FDU-HOWTO. + Finished RPM sections. + Added "need help" appendix. + Finished "About this doc" appendix. + Ready for peer revision. + 2004-11-27 27 Nov 2004 avi - Created first sections. - Merged with Font-HOWTO. + + Created first sections. + Merged with Font-HOWTO. + @@ -222,7 +236,7 @@ Over time, fontconfig/Xft will replace the core X font subsystem. At the present time, applications using the Qt 3 or GTK 2 toolkits (which would include KDE and GNOME applications) use the fontconfig and Xft font subsystem; most everything else uses the core X fonts. In the future, Linux distributions may support only fontconfig/Xft in place of the XFS font server as the default local font access method. - An exception to the font subsystem usage outlined above is OpenOffice.org (which uses its own font rendering technology). + An exception to the font subsystem usage outlined above is OpenOffice.org (which uses its own font rendering technology).
@@ -544,7 +558,7 @@ myfonts/myfonts/font3.ttf To build an RPM package you'll have to create a .spec file that provides instructions to the package builder on how to organize the files, package description, author, copyright, etc. We provide a template here that you can use to start your work. The template looks like this: The <filename>.spec</filename> file template - + Name: myfonts Summary: Collection of My Funny Fonts @@ -701,7 +715,7 @@ rm -rf $RPM_BUILD_ROOT The evolution history of this package here. Must follow this layout. - + This file must be named as the name of the package - myfonts.spec in our example. And you must put it under the main directory of the package. So in the end we'll have something like this: @@ -745,7 +759,7 @@ myfonts/myfonts/font3.ttf Classifications of Typefaces
Fixed versus variable width - There are several classifications of typefaces. Firstly, there are fixed width fonts, and variable width fonts. The fixed width fonts look like typewriter text, because each character is the same width. This quality is desirable for something like a text editor or a computer console, but not desirable for the body text of a long document. The other class is variable width. Most of the fonts you will use are variable width, though fixed width can be useful also (for example, all the example shell commands in this document are illustrated with a fixed width font). The most well known fixed width font is Courier. + There are several classifications of typefaces. Firstly, there are fixed width fonts, and variable width fonts. The fixed width fonts look like typewriter text, because each character is the same width. This quality is desirable for something like a text editor or a computer console, but not desirable for the body text of a long document. The other class is variable width. Most of the fonts you will use are variable width, though fixed width can be useful also (for example, all the example shell commands in this document are illustrated with a fixed width font). The most well known fixed width font is Courier.
To serif or not to serif ? @@ -888,21 +902,21 @@ small caps fonts, and swash capitals (fancy, calligraphic letters).
Bitmap Fonts A bitmap is a matrix of dots. Bitmap fonts are represented in precisely this way -- as matrices of dots. Because of this, they are device dependent -- they are only useful at a particular resolution. A 75 DPI screen bitmap font is still 75 DPI on your 1200 DPI printer. - There are two types of bitmap fonts -- bitmap printer fonts, such as the pk fonts generated by dvips, and bitmap screen fonts, used by X and the console. The bitmap screen fonts typically have a bdf or pcf extension. Bitmap screen fonts are most useful for terminal windows, consoles and text editors, where the lack of scalability and the fact that they are unprintable is not an issue. + There are two types of bitmap fonts -- bitmap printer fonts, such as the pk fonts generated by dvips, and bitmap screen fonts, used by X and the console. The bitmap screen fonts typically have a bdf or pcf extension. Bitmap screen fonts are most useful for terminal windows, consoles and text editors, where the lack of scalability and the fact that they are unprintable is not an issue.
TrueType Fonts - TrueType fonts were developed by Apple. They made the format available to Microsoft, and successfully challenged Adobe's grip on the font market. True type fonts store the metric and shape information in a single file (usually one with a ttf extension). Recently, font servers have been developed that make TrueType available to X. And PostScript and ghostscript have supported TrueType fonts for some time. Because of this, TrueType fonts are becoming more popular on linux. + TrueType fonts were developed by Apple. They made the format available to Microsoft, and successfully challenged Adobe's grip on the font market. True type fonts store the metric and shape information in a single file (usually one with a ttf extension). Recently, font servers have been developed that make TrueType available to X. And PostScript and ghostscript have supported TrueType fonts for some time. Because of this, TrueType fonts are becoming more popular on linux.
Type 1 Fonts The Type 1 font standard was devised by Adobe, and Type 1 fonts are supported by Adobe's PostScript standard. Because of this, they are also well supported under linux. They are supported by X and ghostscript. Postscript fonts have traditionally been the choice of font for anything on UNIX that involves printing. - Typically, a UNIX Type 1 font is distributed as an afm (adobe font metric) file, and an outline file, which is usually a pfb (printer font binary) or pfa (printer font ascii) file. The outline file contains all the glyphs, while the metric file contains the metrics. - Type 1 fonts for other platforms may be distributed in different formats. For example, PostScript fonts for windows often use a different format (pfm) for the metric file. + Typically, a UNIX Type 1 font is distributed as an afm (adobe font metric) file, and an outline file, which is usually a pfb (printer font binary) or pfa (printer font ascii) file. The outline file contains all the glyphs, while the metric file contains the metrics. + Type 1 fonts for other platforms may be distributed in different formats. For example, PostScript fonts for windows often use a different format (pfm) for the metric file.
Type3 Fonts - These fonts are distributed in a similar manner to Type 1 files -- in groups of afm font metrics, and pfa files. While they are supported by the PostScript standard, they are not supported by X, and hence have limited use. + These fonts are distributed in a similar manner to Type 1 files -- in groups of afm font metrics, and pfa files. While they are supported by the PostScript standard, they are not supported by X, and hence have limited use.
Type 42 Fonts @@ -941,8 +955,8 @@ small caps fonts, and swash capitals (fancy, calligraphic letters). Type 1 Fonts and Metafont
Dealing With Mac and Windows Formats - Many foundries ship fonts with Windows and Mac users in mind. This can sometimes pose a problem. Typically, the ``Windows fonts'' are fairly easy to handle, because they are packed in a zip file. The only work to be done is converting the pfm file to and afm file (using pfm2afm). - Macintosh fonts are more problematic, because they are typically made available in .sit.bin format -- stuffit archives. Unfortunately, there is no tool for Linux that can unpack stuffit archives created with the newer version of stuffit. The only way to do it is run Executor (Mac emulator), or try running stuffit in dosemu or Wine. Once the sit.bin file is unpacked, the Macintosh files can be converted using t1unmac which comes with the t1utils package. + Many foundries ship fonts with Windows and Mac users in mind. This can sometimes pose a problem. Typically, the ``Windows fonts'' are fairly easy to handle, because they are packed in a zip file. The only work to be done is converting the pfm file to and afm file (using pfm2afm). + Macintosh fonts are more problematic, because they are typically made available in .sit.bin format -- stuffit archives. Unfortunately, there is no tool for Linux that can unpack stuffit archives created with the newer version of stuffit. The only way to do it is run Executor (Mac emulator), or try running stuffit in dosemu or Wine. Once the sit.bin file is unpacked, the Macintosh files can be converted using t1unmac which comes with the t1utils package. Unfortunately, some vendors only ship Type 1 fonts in Macintosh format (stuffit archives). However, according to font expert Luc Devroye, all major foundries make Type 1 fonts available for Mac and Windows.
@@ -1038,7 +1052,7 @@ small caps fonts, and swash capitals (fancy, calligraphic letters). There are several font packages for Linux. Many of them are obsolete, or you really will never have to use them. - chkfontpath is a utility for manipulating the xfs configuration file. + chkfontpath is a utility for manipulating the xfs configuration file. @@ -1054,7 +1068,7 @@ small caps fonts, and swash capitals (fancy, calligraphic letters). - pfm2afm is a utility for converting windows pfm font metric files into afm metrics that can be used for Linux. This is based on the original version available at CTAN, and includes modifications from Rod Smith to make it compile under Linux. + pfm2afm is a utility for converting windows pfm font metric files into afm metrics that can be used for Linux. This is based on the original version available at CTAN, and includes modifications from Rod Smith to make it compile under Linux. @@ -1066,11 +1080,11 @@ small caps fonts, and swash capitals (fancy, calligraphic letters). - ttfps converts .ttf TrueType font files into Type42 files. + ttfps converts .ttf TrueType font files into Type42 files. - ttfutils A package of utilities for handling TrueType fonts. This package requires ttf2pt1. Useful if not essential. + ttfutils A package of utilities for handling TrueType fonts. This package requires ttf2pt1. Useful if not essential. @@ -1078,11 +1092,11 @@ small caps fonts, and swash capitals (fancy, calligraphic letters). - xfstt is a TrueType font server for Linux. It's useful, but xfs is probably a better choice. + xfstt is a TrueType font server for Linux. It's useful, but xfs is probably a better choice. - xfsft The xfsft font server. Note that this is included in xfs. + xfsft The xfsft font server. Note that this is included in xfs. @@ -1321,7 +1335,7 @@ contains a lot of links to sites on PostScript and fonts. If your distribution appears in the list on but you can't find the binary package for your platform (for example x86_64), you can easily create the RPM compatible with your system following this steps: Have installed compiler and development packages on your system - Download the source RPM file (.src.rpm extension) for your distribution from . For example, on Fedora 5, the correct source package is this one. + Download the source RPM file (.src.rpm extension) for your distribution from . For example, on Fedora 5, the correct source package is this one. As root, do this command: bash# rpmbuild --rebuild [the .src.rpm file you just downloaded] diff --git a/LDP/howto/docbook/HighQuality-Apps-HOWTO/HighQuality-Apps-HOWTO.xml b/LDP/howto/docbook/HighQuality-Apps-HOWTO/HighQuality-Apps-HOWTO.xml index 75f320ff..8e1e87c7 100644 --- a/LDP/howto/docbook/HighQuality-Apps-HOWTO/HighQuality-Apps-HOWTO.xml +++ b/LDP/howto/docbook/HighQuality-Apps-HOWTO/HighQuality-Apps-HOWTO.xml @@ -156,7 +156,7 @@ Let's make some exercise with separation using as example a system called MySoftware, in which the business logic is in and the configuration is in . A Shell program referring an external configuration file - + &externalconf; @@ -172,17 +172,17 @@ After reading the configuration file, all content directories -- user's + product's -- goes together in the $CONTENT_PATH, that will be used from now on. - + File containing only the configurations for <acronym>MySoftware</acronym> - + &conffile; These are user defined parameters. - +
One Body, Many Souls @@ -531,7 +531,7 @@
Turning Your Software Into a Subsystem Your Software's files will spread across the filesystems, but you'll want to provide a simple and consistent interface to let the user at least start and stop it. Subsystems architecture promotes this ease-of-use, also providing a way (non obrigatoria) to be automatically started on system initialization. You just have to create your /etc/init.d script following a standard to make it functional. Skeleton of a Subsystem control program in <filename class="directory">/etc/init.d</filename> - + &initscript; @@ -554,7 +554,7 @@ Here you put your Software's specific command. - + The mysystem subsystem methods you implemented will be called by users with the service command like this example: <command>service</command> command usage diff --git a/LDP/howto/docbook/HighQuality-Apps-HOWTO/articleinfo.xml b/LDP/howto/docbook/HighQuality-Apps-HOWTO/articleinfo.xml index 97850409..c7e84133 100644 --- a/LDP/howto/docbook/HighQuality-Apps-HOWTO/articleinfo.xml +++ b/LDP/howto/docbook/HighQuality-Apps-HOWTO/articleinfo.xml @@ -5,12 +5,12 @@ Avi Alkalay + IBM Linux Impact Team :: ibm.com/linux + Senior IT and Software Architect :: Linux Market Developer
avi at br.ibm.com avi at unix.sh
- Senior IT and Software Architect :: Linux Market Developer - IBM Linux Impact Team :: ibm.com/linux @@ -20,9 +20,11 @@ 2.1 24 Aug 2002 avi - Rewrite of the /opt /usr/local section. - Cosmetics on graphical user interface and plugins sections. - Fixed screens and programlistings width. + + Rewrite of the /opt /usr/local section. + Cosmetics on graphical user interface and plugins sections. + Fixed screens and programlistings width. + 2.0 diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Definitions-Naming-HOWTO/Partition-Mass-Storage-Definitions-Naming-HOWTO.xml b/LDP/howto/docbook/Partition-Mass-Storage-Definitions-Naming-HOWTO/Partition-Mass-Storage-Definitions-Naming-HOWTO.xml index c3a0e7cd..a03c0040 100644 --- a/LDP/howto/docbook/Partition-Mass-Storage-Definitions-Naming-HOWTO/Partition-Mass-Storage-Definitions-Naming-HOWTO.xml +++ b/LDP/howto/docbook/Partition-Mass-Storage-Definitions-Naming-HOWTO/Partition-Mass-Storage-Definitions-Naming-HOWTO.xml @@ -25,10 +25,8 @@
- - - Partitions-Mass-Storage-Definitions-Naming-HOWTO, - copyright (c) 2009 Jean-Daniel Dodin + Partitions-Mass-Storage-Definitions-Naming-HOWTO + Copyright (c) 2009 Jean-Daniel Dodin
Copyright and Licence @@ -264,21 +262,21 @@ major minor #blocks name
Old IDE Names By convention, IDE drives where given device names - /dev/hdato - /dev/hdd. + /dev/hdato + /dev/hdd. Hard Drive A( - /dev/hda) is the first drive and + /dev/hda) is the first drive and Hard Drive C( - /dev/hdc) is the third. + /dev/hdc) is the third. A typical PC has two IDE controllers, each of which can have two drives connected to it. For example, - /dev/hdais the first drive (master) on the + /dev/hdais the first drive (master) on the first IDE controller and - /dev/hddis the second (slave) drive on the + /dev/hddis the second (slave) drive on the second controller (the fourth IDE drive in the computer). So, typically, a computer with IDE controller can @@ -501,7 +499,7 @@ major minor #blocks name brw-rw---- 1 root disk 8, 0 mars 9 07:56 /dev/sda]]> Shows permissions ( - brw-rw----), owner (root), group (disk), major + brw-rw----), owner (root), group (disk), major device number (8), minor device number (0), date (mars 9 - french, no year), hour (07:56) and device name (guess :-). @@ -522,8 +520,8 @@ brw-rw---- 1 root disk 8, 0 mars 9 07:56 /dev/sda]]> swap space, or even foreign file systems like (Microsoft) NTFS or (Sun) UFS. There is a numerical code associated with each partition type. For example, the code for ext2 is - 0x83and linux swap is - 0x82(0x mean hexadecimal). + 0x83 and linux swap is + 0x82 (0x mean hexadecimal).
Foreign Partition Types diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/Partition-Mass-Storage-Dummies-Linux-HOWTO.xml b/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/Partition-Mass-Storage-Dummies-Linux-HOWTO.xml deleted file mode 100644 index 194cfcfe..00000000 --- a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/Partition-Mass-Storage-Dummies-Linux-HOWTO.xml +++ /dev/null @@ -1,6 +0,0 @@ -
Partition-Mass-Storage-Dummies-Linux-HOWTO62009-04-05 08:38:51jddadding forgotten HOWTO header for wiki52009-04-05 08:35:01jddadding link to the Partitions-and-mass-storage-HOWTO42009-03-30 18:34:19jddremove headers to render to docbook32009-03-30 18:07:40jdd22009-03-30 17:58:09jdd12009-03-30 17:54:21jddtitle change from sub page to full page (done with copy/paste)
Partition-Mass-Storage-Dummies-Linux-HOWTOcopyright (c) 2009 Jean-Daniel Dodin This HOWTO is about partitionning usual mass storage that can be magnetic rotating hard drives or Solid State Drives (SSD - including flash cards or USB keys). Writing the Partition HOWTO, I noticed that, as of year 2009, at least, partitionning is very complicated. However, most partitionning tasks can be done very easily with the appropriate tools, so this HOWTO for any people that want to understand the partitionning without going too deeply inside. A more complete partition use description can be found on the Partitions-and-mass-storage-HOWTO, available for example here
LicenceGNU Free Documentation License
Definitions
DisksDisks are usually made of rotating plates, read by magnetic heads. Tracks are circular parts of the plates. As we may have several plates, a stack of plate is seen as a cylinder. All the heads are moved at the same time, reading each it's track. All the tracks read at the same time are a cylinder as well. Each track is divided as sectors that can be 512 or 4k bytes long. So Mass Storage disks are nearly always described as "CHS", that is Cylinders number, Heads number, Sectors by track number, and the product of all these numbers gives the visible disk size. However, this have no meaning for SSD and even with true rotating hard drive, the CHS have absolutely no more any meaning! It keeps using only by inertia... so don't worry too much about these numbers, and if possible ignore them.
PartitionsPartition is from "part". A partition is a part of a drive with some special attributes. Computers makers seems pretty dumb when seeing how they keep underestimating the possible next disk size, so each year they have to issue a new standard. Disks firmware are buggy, so the software tools have to fix them - and do quite well the job. That is to say that understanding fully why the Partitionning tool choose to create the partitions the way they do is very complex. It's explained fully (or mostly) on the Partitions-and-mass-storage-HOWTO, you probably won't read and don't have to now. Windows makes little use of partitions. One can install as many Windows version he wants on the same partition (and often do). It may even proove difficult to install Windows on just an other drive on the same computer. Nor Unix nor Linux have any such problem. Just on the contrary, Linux love to use at least three partitions. This mean you can have as many Linux on your drive as you want, each on it's special part(ition) of the drive, erase the partition without losing your data (backup first is still better) for example. The two main Linux partitions are used for the system ("/" or "root") and the users data ("home"). The third ("swap") is used to add some more memory and is written directly sector by sector by the system. You usually don't even see it.
Making Room for Linux
Using WindowsMost of the time, your computer come with a paid Windows. If you are not an experienced Linux User, it's probably better to keep this Windows, just for safety in case you have to show your computer to the vendor tech (If your vendor is Linux fiendly you are lucky!). So you have to make room for your prefered Linux. If You have Windows XP, little luck. Most XP computers come with only one partition on the disk and XP don't know how to make it smaller (If you have two, see the next paragraph). What you have to do is to "defragment" the drive (look in disk properties, you will probably have to "verify" the drive first) - if the computer is brand new and never used, this is not necessary. The "defragmentation" makes the work easier for the Linux partitionner. If you have Windows Vista, go to Control center, Administration tools, Disk tools to see the actual disk partitionning. If you have luck, may be there is yet a "data" partition. If so, you have just to look where is this partition located and what it's size is. It will be used for Linux. If not, clic right on the system disk partition rectangle, you will see a resize option. Use it. Keep some room for Vista (50Gb, for example) and OK, you have now several partitions on your drive. If you see in this screen a small partition (usually around 9Gb), be specially cautious. This is the "system restore partition" that holds the Windows Vista (or XP) original system. Your computer manual should explain how to copy this to two DVD's. Do this before any use of your computer. Make notice of the size and place of this partition (it can be at the very beginning of the drive or at the very end), try to not erase it right now. Don't erase it during the computer insurance time.
Using LinuxYou, as a dummy Linux user, have better use a very well known Linux Distribution. There are more than a hundred Linux distributions and I don't have used all of them, of course, so I can't be sure some of them couldn't erase your drive if ever you don't understand a question. However I'm rather sure Ubuntu, openSUSE, Mandiva, Red Hat Fedora, new Debian can be reasonably safe for a beginner. So launch the Linux install. Probably you will have to insert a Cd or DVD and run. May be you will install immediately or launch a live system (Linux working from memory, not from drive), then install froms there. Anyway, you will have to answer some basic questions and at a moment you will be asked if you want to keep windows or erase it. Beleive me, keep it for now, it will be easy to remove later. At this moment you will be presented a screen with a graphic of the proposed disk partitions. Scan it to verify the Windows partition is not touched - not formatted. It is probably labelled "NTFS" or "Windows". Verify also that the Windows system backup partition is not touched. It may not have any identified label. In some partitionner, the partition table may be called Disklabel. You may have to give Linux the name or position of the Vista partition created on the previous step. If your Windows is XP, you will be proposed to shrink the Windows Partition this is good. Then accept the partitionning sheme your distribution proposes. Do not try to be an expert. At install time, no good Linux Partition tool should erase a Windows system partition. If it does, write me, I will include a notice here. Modern Linux distributions are perfectly able to resize a Windows partition to make room to Linux. Let some room to Windows, though, if you plan to use it. So, in summary, trust your Linux install. Most install problems are user's problem, not Linux Distribution problems!! Do not try "LVM" or "RAID" for your first install. To use these things, read the hole Partitions-and-mass-storage-HOWTO.
Images of the partitionning tools
Windows XPHere you can see the XP tool for partitionning (french version). The partition is the dashed c: rectangle. You can see the contextual menu (right clic) with no resizing - the resizing option can be seen only in the Vista similar menu. XP partitionningIf the computer used Windows for a while, you will have to verify and defragment the disk. This is found in the disk context menu, tab "tools". Defragmenting is re-organising the files in the disk. On the picture below, you see a badly fragmented disk. Vertical lines are files. To be able to shrink the partition with the Linux tools, you must have a large blank on the right of the rectangle on the defrag window. Even only one file on the right prevents resizing. If you can't resize, you can only backup all your data, make the partitionning (with Parted magic, for example), deleting all the disk, reinstall XP then install Linux. Given you will probably have to reinstall Windows from time to time, you can use this moment to make room for Linux. Defragmenting
Parted MagicParted Magic is a CD or USB key utility extremely usefull if you have to deal with partitions (find it with web search Probably ). It allows repartitonning, resizing of partitions (if possible), and even search for lost partitions if you happen to have trashed your partition table (experts only). Do not confuse Parted Magic (free and open source) with the proprietary program Partition Magic (expensive). This tool is by far the more friendly. If you read this HOWTO you are probably not as Dummy as you may think, at least you are curious. So you may have benefits to use Parted magic at least to make one free partition the Linux installer will easily find and use (and certainly repartition again, that's normal). Here is the booting screen, you should be able to boot any computer with this CD. Parted MagicYou start a graphical screen, as usual. You have icons at the bottom of the screen, clic to use. The partitionning tool is gparted, a very friendly tool. Notice gparted gives you immediately the free space in the Windows partition (the images here is that of a very small disk - only 8Gb). Parted MagicRight clic on the desired partition gives you the needed options. Parted MagicIn the resizing window, you can resize with the mouse (moving the partition limit with the mouse), or give a numerical value. Parted MagicHere is a view of a much bigger disk. Parted MagicOn the same Parted Magic CD, you have also other tools, like "Testdisk". This one is much less friendly, but also very powerfull (and being so allow easily to destroy your disk). You will be able to use it sometime in the future, not now. Parted Magic
openSUSEopenSUSE is a friendly Linux Distribution, trying to reduce as much as possible the risk of removing accidentally files on the disk while installing. If you insert the openSUSE DVD in your drive when Windows is running, the DVD starts and propose to install Linux. It creates a special Windows starting menu and reboot to the install without any work to do for the user. On this first image, openSUSE warns that it's not possible to resize the XP disk, you have to remove it entirely if you want to install Linux. openSUSEAfter I did quite a long cleaning work (including removing of unusefull files) on the XP disk, from inside XP, the diagnostic is better: openSUSE
MandrivaMandriva is even simpler, the options are to remove Windows or to use part of the drive. MandrivaIf you choose this solution, you have a windows to select what part of the disk is for XP, what part for Linux, as usual. Mandriva
FedoraRed Hat was the first really handy Linux Distribution, but for many years now, it's no more aimed to John Doe but to professionals (with the associated support and price). It's average user conterpart is Fedoraproject. Fedora can be dowloaded as a live CD, you start it (no boot options) and then clic on an icon to begin the installation. On the partitionning screen, Fedora give a drop down list of the choices possible, one is resizing (here the french screen) FedoraThe following screen is for the size, as usual. Fedora
Ubuntu DesktopUbuntu also have a friendly screen to resize partitions, but one have to go to "manual" to find it, what can be a little scary. UbuntuIt's the "edit" button that allows resizing. Do not format the XP main partition! This would erase all the content. Ubuntu
DebianDebian is now as pretty as most distributions. The boot menu (first CD) gives more options than many - this is not a live CD. DebianThe partitionner. Choices are the same as Ubuntu does (Ubuntu is built upon Debian). Debian"Manual" have the resize option. DebianYou have to give a number - no slide, no view of the free space. Debian
OthersMany Linux distributions are availalble, for example from ibiblio. If any of these distributions uses gparted, it's possible very easily to partition a drive with them, as we could see with Parted magic. Here the example of Puppy Linux. PuppyThis distributions may be a bit more difficult to understand, but it installs is extremely low end hardware (256Mb ram for live cd, 2GB Hard drive).
\ No newline at end of file diff --git a/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/Partitions-Mass-Storage-Definitions-Naming-HOWTO.xml b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/Partitions-Mass-Storage-Definitions-Naming-HOWTO.xml deleted file mode 100644 index bec78963..00000000 --- a/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/Partitions-Mass-Storage-Definitions-Naming-HOWTO.xml +++ /dev/null @@ -1,609 +0,0 @@ - - -
- - - Jean-Daniel - Dodin - -
- jdd@dodin.org -
- - - - Partitions-Mass-Storage-Definitions-Naming-HOWTO - - - V0.1 - 2009-05-09 - jdd - - - - -
- - - Partitions-Mass-Storage-Definitions-Naming-HOWTO, - copyright (c) 2009 Jean-Daniel Dodin -
-
- Copyright and Licence - The copyright of this document is to the author, - Jean-Daniel Dodin, according to the following licence. - - - - - - GNU Free Documentation License - -
-
- Mass Storage Involved Here - Mass storage involved in the present HOWTO are rewritable - random access ones. Most of them are magnetic rotating disks - (floppies, Hard Drive) or flash memory (USB key or any kind of - memory card). - For example, cdroms and dvds are - notconcerned by this HOWTO ( - see - Wikipedia). Tapes are not either. - Mass storage are used by the kernel, so the basic doc can - be found on - - the kernel Web site - Reference site should be - the International Disk drive - Equipment and Materials Association. - Shouldbecause this Web site is not very - friendly. -
-
- Definitions -
- Warning - Many definitions about drives are only virtual. That is - they are used, but the hardware is often quite different from - the expected description. Usually this have no odd result, - any mass storage have to be seen as a - black box. -
-
- Bytes - Computers counts with binaries, 1 & 0, - 1111100001110... To be able to read this better, humans uses - nibbles (4 bits) often shown as Hexadecimal numbers from 0 to - f (0123456789abcdef). Nibbles are usually grouped by two and - this gives a byte. The most used memory unit is byte and it's - multiples, KiB (Kilo Bytes), MiB (Mega Bytes), GiB - (Gigabytes). The "i" denotes the binary use (0ne Ki is 1024, - not 1000), the uppercase "B" denotes Bytes, not bits. -
-
- Sectors - Sometime, the word - blockis used in place of - sectors. - Mass storage devices (at least the ones we are dealing - with here) store bytes in "Sectors" of 512 Bytes. This is - uneven, because any sector count have to be divided by two to - have the KiB number, so most partitonning software accepts - letters k (KiB), m (MiB), g... as options. Wise ones do not - make any case difference. - Sector size is the available byte count. The true - sector is bigger, as it have to include housekeeping data. - You don't have to worry about that. - Notice that as of 03-22-2006, the IDEMA annouced a new - sector size of 4kiB (4096 Bytes): - - - doc file, can be openned with OpenOffice.org. -
-
- Heads - Rotating mass storage devices uses - heads. True heads are the physical - electromechanical device that writes and read the magnetic - track. Drives being made of rotating plates, the plates have - two sides, so disks can have two head by plate. Having two - plates (frequent) you have four heads. - Heads are writing through very complex system, see - detailed info here: - . -
-
- Tracks - Plates are rotating. When a head is still, the plate - rotation and the width of the head are defining a - track. - Heads are moving from the external part of the plate to - the inner part, step by steps. Each step defines a new - track. -
-
- Cylinders - Heads are moving together, all at the same time. They - may rotate - on they own center, not the plate center, of - course. They also may have a linear move. You can see an - example of linear moving head in any cdreader, looking at the - move of the laser head. Most disks are as shown by this - wikipedia image - . - When you think of all the tracks defined by each head - at the same time, you have a cylinder. So on a rotating - drive, all the tracks of the same cylinder are read or - written at the same time. The actual data is spread on all - the plates. The way the data is actually written is up to the - drive manufacturer, not the user. -
-
- Disks - Small disks are used directly as a hole bunch of - sectors. Basic programs can access data directly on sectors. - Many do (like dd or any partitionning programm). - But we live in a world of extremely high capacity mass - storage. Terabytes is normal nowaday (2009), when a complete - Linux system can live on a floppy (1440 bytes). So there is a - need of making several parts from a mass storage device, - though the partitions. -
-
- Partitions - Partitioning is a means to divide a single drive into - many logical drives. A partition is a contiguous set of - sectors. To lessen the heads travel, partitions can be - "aligned" on the cylinder size, that is use an integer number - of cylinder. This is not always done, but should as it have - many other advantages for recovery. -
-
- Partition Table - As you can have many partitions, you need to have a - partition table. This partition table is stored in the very - beginning of the drive. It's very unlikely that you will have - to change this table directly writing bytes with an - hexadecimal editor, so we wont say more on the position of - the table. - There are many Operating Systems all around that all - share similar hardware and as many partition systems. We will - look only at what one can find in a PC, even if it's not easy - to define that nowaday. Say, for us, a PC is any computer - able to run Linux (I know, it's not always true). - Each of these partition kinds are noted in the table by - a special flag called "type" ("t" in fdisk). Most known are - type 83 for Linux partitions and 82 for Linux swap (hex - numbers). - Notice that most Operating Systems can share partition - tables. At least, if a disk is hardware compatible with - several systems, these systems should be able to see what the - others have done, not to erase a drive by accident. I can't - say for sure that its true in the real life. -
-
- File Systems - Partitions can be accessed directly as sectors, as any - part of the disk, but are usually filled with a - file system. File system - and partitions are related only because a file system is in a - partition, but that's all. You can have a disk without - partition but with a file system or have partitions without - file system (the swap partition beeing the most well known). - For details on file systems, - see - Wikipedia. - In summary, file systems allow storing data in files - with human readable names and to sort the files in a friendly - way, for example as directories, subdirectories, text, - images... -
-
- Files and Nodes - Nearly all what you can find on a mass storage - partition, beside sectors, from an user point of view, is a - file. But computers are curious geeks and you can treat files - like disks if you want. Using the "loop" system, default in - most Linux kernels, one can partition the inside of the file, - create file systems on it and mount it. This is specially - handy for experiments. - Some of these files are - devicesor - nodes. Partitions are not files and are - accessed via special nodes we will see later. These nodes are - not created by touch but by - mknode. Use with caution. Nodes need a - type ( - cfor "character" or "b" for - block) and major and minor numbers. For - what we need, major numbers are disk numbers and minor - numbers are partition numbers. The list is visible in - /proc/partitions - - - - - - - Creates a /dev/sda9 node of no nuse, given this don't - create partition, only the node. In a usual Linux - distribution, nodes are dynamically created at boot time, so - nobody should have to do so. However, sometime the automatic - system fails. -
-
-
- Drive Naming in Linux - There is a special nomenclature that linux uses to refer - to mass storage that must be understood. -
- Naming Convention - Linux used to deal with two kind of drives, depending - of the electronic interface (controller), IDE and SCSI. - Oldtimers remember the day where cdwriters where acccessed - through "SCSI emulation". In fact IDE and SCSI use mostly the - same low level commands and for 2007 up, with the new "SATA" - interface, the naming was unified and, in new ditributions, - all the drives have the same naming. For this part, CD or DVD - readers/writers are seen like Hard Drives. -
- Old IDE Names - By convention, IDE drives where given device names - /dev/hdato - /dev/hdd. - Hard - Drive - A( - /dev/hda) is the first drive and - Hard - Drive - C( - /dev/hdc) is the third. - A typical PC has two IDE controllers, each of which - can have two drives connected to it. For example, - /dev/hdais the first drive (master) on the - first IDE controller and - /dev/hddis the second (slave) drive on the - second controller (the fourth IDE drive in the - computer). - So, typically, a computer with IDE controller can - accomodate 4 drives: /dev/hda (primary master), /dev/hdb - (primary slave), /dev/hdc (secondary master), /dev/hdd - (secondary slave). Some (rare) Mother Boards have more than - two controllers, some addition cards can also have - controllers, these are numbered following the alphabet, but - one have to figure out what real names are given for his - particular hardware. - You can have drives where ever you want, it's not - mandatory to fill the gaps. You may have interest to read - about what drive/cdrom connect to what place, but it's out - of this document scope. -
-
- New Hard Drives Names - Now all the rotating hard drives uses the same names - as the old SCSI controllers, that is "s" in place of "h", - so /dev/sda, and so on. The number of drives depends on the - number of controllers on the Mother Board or the extended - boards. Usually 4 are available. What will be the number of - a drive is up to the controller card and the way it's read - by the kernel, so difficult to say at first. -
-
- Flash Drives Names - Flash drives are usually not connected through IDE or - SATA interfaces and so don't uses the same names. Several - interfaces are used with each different names. The kernel - documentations gives the names. -
-
- Low level Devices and Extra naming - You will find in some apps references to lowlevel - SCSI devices and various naming conventions, for example - (wodim is the command line cd burner): - - - - And you may have to use some sort of - SCSI:1,1,0option to access the CDROM. - try to avoid using this as much as possible, as it's very - error prone and should be let to programmers only. I only - mention it because you can't always avoid it. - If you do "cat /dev/ | more", you can see: - - sr0 -(...) -crw-r----- 1 root disk 21, 0 mars 9 07:56 sg0 -crw-rw----+ 1 root disk 21, 1 mars 9 07:56 sg1]]> - - These scd, sr, sg devices are lowlevel interface - (notice the "c" for "character"). Try not using them. - dmesgand - more /var/log/boot.msgshould give you - the usable sdxx device, like (short summary): - - sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500GB/465GiB) -<5>sd 0:0:0:0: [sda] Write Protect is off -<7>sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00]]> - - This mean the drive is - /dev/sda. - However these files (given by - dmesgand - more /var/log/boot.msg) used to be - easy to read but are no more. Now the kernel starts in - parallel several drivers, so the messages are mixed, you - can have - - sda:<6>USB Universal Host Contr'ller Interface driver v3.0]]> - - This don't mean that your sda drive is an usb one, - but the usb module was started at the same time as the - drive one and send it's messages simultaneously. You still - have a - /dev/sdadrive. -
-
- New Media Names - Here the dmesg content for inserting an USB - key: - - - - You see there all what we where speaking about right - now! SCSI emulation, scsi, sd and sg names, but also the - sdb that is most important for us. - Here are the messages for a high speed SDHC - card: - - - - When the two cards are probably the same flash memory - chip, the USB key uses the USB interface and SCSI - emulation, the SDHC card uses the PCMCIA slot of the - laptop, with a special device naming (/dev/mmcblk0). The - use, as far as partitionning is involved is the - same. -
-
- Disk ID - In a world where disks are many and removable, it's - impossible to track what device is used by what disk. So - there are now many way of using a disk name. This makes it - extremely difficult to work with basic tools. These are - "Disk labels" and "Disk UUID", also "Partition Labels". See - fstab man page for details. -
-
-
-
- Partition Naming in Linux -
- Numbers - Partition naming is thanksfully simpler than drive one. - Partitions are simply given a number from 0 up (decimal). - Sometime a "p" is appended on front of the number: - - - - As you see, partition devices are listed in - /proc/partition. This file... is not a real file but is - created on the fly. Don't worry, for what we need it's a - file. - Notice the "p1" partition name for the SDHC - card. - Max number of partitions is 15 for SCSI and all the - drives using the new SATA driver, 63 for IDE drives (0 is the - full drive, 0 to 15 is four bits 0 to 64, 6 bits) -
-
- Meaning of the Numbers - Not all the numbers have the same meaning. This mess - come from the PC history. One can divide floppies with - partitions, but then 4 ones seems sufficient. But then come - Hard drives :-). So the partitons numbers 1, 2, 3 and 4 are - primarypartitions. One drive can only - have 4 primaries. - To go further, we have to use one of these primary as a - big one and sub-partition this one, so to have - logicalpartitions. The big - extendedpartition can be any of the - 4. - So, remember, the primary partitions are inside the - drive and the logical partitions are inside one of the - primary, called the - extendedpartition. - Once the logical partitions are created, it's no more - recommended to write directly to the extended one. Writing to - an extended partition would erase the logical ones like - writing directly to a hard drive erase the partitons. Beware, - - it's possible!! - If, after creating 4 primary partitions, all the disk - space is not used, the remaining space is lost (unusable), so - most of the time, create the desired primaries, then at last - the extended one with all the remaining room. - It's not necessary to create 4 primaries. You could use - only one extended (Linux only), but there are some advantages - of using primaries. - Primaries being 4, the first logical partition is - always 5. So any partition with number of five and up is a - logical one. -
-
-
- Device Major and Minor Numbers - The only important thing with a device file are its major - and minor device numbers, which are shown instead of the file - size: - - - - Shows permissions ( - brw-rw----), owner (root), group (disk), major - device number (8), minor device number (0), date (mars 9 - - french, no year), hour (07:56) and device name (guess - :-). - When accessing a device file, the major number selects - which device driver is being called to perform the input/output - operation. This call is being done with the minor number as a - parameter and it is entirely up to the driver how the minor - number is being interpreted. The driver documentation usually - describes how the driver uses minor numbers. -
-
- Partition Types -
- Linux Partition Types - A partition is labeled to host a certain kind of file - system (not to be confused with a volume label. Such a file - system could be the linux standard ext3 file system or linux - swap space, or even foreign file systems like (Microsoft) - NTFS or (Sun) UFS. There is a numerical code associated with - each partition type. For example, the code for ext2 is - 0x83and linux swap is - 0x82(0x mean hexadecimal). -
-
- Foreign Partition Types - The partition type codes have been arbitrarily chosen - (you can't figure out what they should be) and they are - particular to a given operating system. Therefore, it is - theoretically possible that if you use two operating systems - with the same hard drive, the same code might be used to - designate two different partition types. OS/2 marks its - partitions with a 0x07 type and so does Windows NT's NTFS. - MS-DOS allocates several type codes for its various flavors - of FAT file systems: 0x01, 0x04 and 0x06 are known. DR-DOS - used 0x81 to indicate protected FAT partitions, creating a - type clash with Linux/Minix at that time, but neither - Linux/Minix nor DR-DOS are widely used any more. -
-
- Swap Partitions - Every process running on your computer is allocated a - number of blocks of RAM. These blocks are called pages. The - set of in-memory pages which will be referenced by the - processor in the very near future is called a "working set." - Linux tries to predict these memory accesses (assuming that - recently used pages will be used again in the near future) - and keeps these pages in RAM if possible. - If you have too many processes running on a machine, - the kernel will try to free up RAM by writing pages to disk. - This is what swap space is for. It effectively increases the - amount of memory you have available. However, disk I/O is - about a hundred times slower than reading from and writing to - RAM. Consider this emergency memory and not extra - memory. - If memory becomes so scarce that the kernel pages out - from the working set of one process in order to page in for - another, the machine is said to be thrashing. Some readers - might have inadvertenly experienced this: the hard drive is - grinding away like crazy, but the computer is slow to the - point of being unusable. Swap space is something you need to - have, but it is no substitute for sufficient RAM. -
-
- Complete List - From the fdisk help: - - - -
-
-
- How Many Partitions - The exact number of partitions allowed on a drive is - fixed by the kernel. So you can find the exact number is the - kernel documentation, the last version is maintained here - If - you have the kernel source installed, you can find your version - on your computer at - /usr/src/linux/Documentation/devices.txt. - Look at "limit on partition". Find yours. Common SATA - number is 31, SCSI is 15, some are less. -
-
diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture10.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture10.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture10.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture10.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture11.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture11.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture11.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture11.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture12.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture12.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture12.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture12.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture13.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture13.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture13.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture13.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture14.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture14.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture14.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture14.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture15.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture15.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture15.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture15.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture16.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture16.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture16.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture16.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture17.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture17.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture17.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture17.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture18.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture18.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture18.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture18.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture19.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture19.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture19.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture19.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture20.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture20.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture20.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture20.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture21.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture21.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture21.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture21.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture22.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture22.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture22.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture22.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture23.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture23.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture23.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture23.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture24.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture24.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture24.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture24.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture25.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture25.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture25.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture25.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture26.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture26.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture26.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture26.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture27.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture27.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture27.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture27.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture28.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture28.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture28.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture28.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture29.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture29.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture29.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture29.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture30.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture30.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture30.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture30.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture31.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture31.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture31.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture31.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture32.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture32.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture32.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture32.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture7.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture7.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture7.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture7.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture8.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture8.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture8.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture8.jpg diff --git a/LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture9.jpg b/LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture9.jpg similarity index 100% rename from LDP/howto/docbook/Partition-Mass-Storage-Dummies-Linux-HOWTO/images/capture9.jpg rename to LDP/howto/docbook/Partitions-Mass-Storage-Definitions-Naming-HOWTO/images/capture9.jpg diff --git a/LDP/howto/docbook/TimePrecision-HOWTO/TimePrecision-HOWTO.xml b/LDP/howto/docbook/TimePrecision-HOWTO/TimePrecision-HOWTO.xml index 469a87a4..88679e31 100644 --- a/LDP/howto/docbook/TimePrecision-HOWTO/TimePrecision-HOWTO.xml +++ b/LDP/howto/docbook/TimePrecision-HOWTO/TimePrecision-HOWTO.xml @@ -3,8 +3,7 @@ ]> -
+
Managing Accurate Date and Time 2002,2003,2004,2005Avi Alkalay @@ -13,11 +12,11 @@ Avi Alkalay - avi unix sh - Linux, Open Standards consultant :: Senior IT and Software Architect IBM Linux Impact Team :: ibm.com/linux + Linux, Open Standards consultant :: Senior IT and Software Architect + avi unix sh BradKnowles @@ -33,28 +32,28 @@ TakeoNakano - nakano at apm.seikei.ac.jp Japanese translation + nakano at apm.seikei.ac.jp SHAKI - sha-ki at narod.ru Russian translation + sha-ki at narod.ru Mihaly Gyulai - gyulai at fbi pont hu Hungarian translation (magyar forditas), the chorny section and the very first section + gyulai at fbi pont hu Philippe Wautelet - p.wautelet at fractalzone be French translation + p.wautelet at fractalzone be Kemal Ökmen - kemal at comu edu tr Turkish translation (türkçe çeviri) + kemal at comu edu tr @@ -89,8 +88,10 @@ 1.0.7 9 Jul 2004 avi - Disclaimer near to license, to let people know they can translate without asking permission. - Small fixes in some phrases. + + Disclaimer near to license, to let people know they can translate without asking permission. + Small fixes in some phrases. + 1.0.6 @@ -364,7 +365,8 @@ ARC=false Here is an example of good architecture:
Local Relay Servers for NTP - + +
If you have several machines to synchronize, do not make them all access the remote NTP servers you chose. Only 2 of your server farm's machines must access remote NTP servers, and the other machines will sync with these 2. We will call them the Relay Servers. Your Relay Servers can be any machine already available in your network. NTP consumes low memory and CPU. You don't need a dedicated machine for it. diff --git a/LDP/howto/docbook/Traffic-Control-HOWTO/classful-qdiscs.xml b/LDP/howto/docbook/Traffic-Control-HOWTO/classful-qdiscs.xml index b302b076..1cd1b307 100644 --- a/LDP/howto/docbook/Traffic-Control-HOWTO/classful-qdiscs.xml +++ b/LDP/howto/docbook/Traffic-Control-HOWTO/classful-qdiscs.xml @@ -990,7 +990,7 @@ $ tc qdisc ... dev dev ( parent classid | root) [ handle major: ] prio [bands ba - parent root | major:minor + parent root | major:minor this mandatory parameter determines the place of the CBQ @@ -1196,7 +1196,7 @@ $ tc qdisc ... dev dev ( parent classid | root) [ handle major: ] prio [bands ba - bounded | borrow + bounded | borrow @@ -1208,7 +1208,7 @@ $ tc qdisc ... dev dev ( parent classid | root) [ handle major: ] prio [bands ba - isolated | sharing + isolated | sharing identifies a sharing policy. Either the class will engage diff --git a/LDP/howto/docbook/libdc1394-HOWTO/libdc1394-HOWTO.xml b/LDP/howto/docbook/libdc1394-HOWTO/libdc1394-HOWTO.xml index 9c0484cc..6200d27c 100755 --- a/LDP/howto/docbook/libdc1394-HOWTO/libdc1394-HOWTO.xml +++ b/LDP/howto/docbook/libdc1394-HOWTO/libdc1394-HOWTO.xml @@ -27,7 +27,7 @@ 1.2 2007-04-14 RA - Addition of DMA related section contributed by Ian Peikon idp2@duke.eduand Tim Hanson tim@hardcarve.com + Addition of DMA related section contributed by Ian Peikon idp2@duke.eduand Tim Hanson tim@hardcarve.com 1.0 @@ -882,7 +882,7 @@ where the values of the parameters for channel, speed, bytes_per_packet, speed, The value of the width and height depends on the size of frame the user wants, for example, if one wants 960x720 then pass 960 as width and 720 as height. - + Example: How to grab image from the IEEE1394 camera using DMA This section has been contributed by Ian Peikon idp2@duke.eduand Tim Hanson tim@hardcarve.com We will now present an example of how to grab a frame by the camera using DMA calls. The example is simple to understand as the logic remains the same as the previous example. We will later compare the function calls used in the previous example (without dma) and this example (with dma) for better understanding. @@ -1064,23 +1064,25 @@ Just like the previous example () the program includes After this the following steps are followed which are very similar to the previous example () - Open ohci and assign handle to it using the function dc1394_create_handle(0) -Get the camera nodes using the function dc1394_get_camera_nodes -Find out various parameters need to be passed during the camera setup. This is done by querying the camera using the following functions - -dc1394_get_iso_channel_and_speed(): To get the channel and speed information -dc1394_get_video_format(): To get the camera format -dc1394_get_video_framerate(): To get the framerate information -dc1394_get_video_mode(): To get the camera mode - -Also we are required to set the dma buffers to 8 and number of drop frames to 1. +Open ohci and assign handle to it using the function dc1394_create_handle(0) +Get the camera nodes using the function dc1394_get_camera_nodes +Find out various parameters need to be passed during the camera setup. This is done by querying the camera using the following functions + + dc1394_get_iso_channel_and_speed(): To get the channel and speed information + dc1394_get_video_format(): To get the camera format + dc1394_get_video_framerate(): To get the framerate information + dc1394_get_video_mode(): To get the camera mode + + + +Also we are required to set the dma buffers to 8 and number of drop frames to 1. Once the values of the parameter have been obtained (framerate,format,mode,channel,speed etc), they are passed in dc1394_dma_setup_capture which then sets up the camera and enables it for capturing video. For DMA you must pass the number of dma buffers and drop frames parameter. -After the camera is set, dc1394_start_iso_transmission() is called. This function starts data transactions from the camera to the bus. -Now capture one frame using dc1394_dma_single_capture(). This function will capture a frame into the dma buffer -After the frame has been grabbed release the dma buffer using dc1394_dma_done_with_buffer(). This is required so that the memory can be reused. It is imperative that dc1394_dma_done_with_buffer() always follows a dma_capture function call -So in order to capture more than one frame the code will be +After the camera is set, dc1394_start_iso_transmission() is called. This function starts data transactions from the camera to the bus. +Now capture one frame using dc1394_dma_single_capture(). This function will capture a frame into the dma buffer +After the frame has been grabbed release the dma buffer using dc1394_dma_done_with_buffer(). This is required so that the memory can be reused. It is imperative that dc1394_dma_done_with_buffer() always follows a dma_capture function call +So in order to capture more than one frame the code will be for( i=0;i<100 ;i++)/* to capture 100 images*/ { @@ -1088,12 +1090,12 @@ for( i=0;i<100 ;i++)/* to capture 100 images*/ dc1394_dma_done_with_buffer(&camera); } - + -Stop listening to the iso channel by calling dc1394_dma_unlisten() -Terminate the data transmission by calling dc1394_stop_iso_transmission() -Save the image in a file and add a PGM header for viewing using gimp. -Finally call dc1394_release_camera to release the camera +Stop listening to the iso channel by calling dc1394_dma_unlisten() +Terminate the data transmission by calling dc1394_stop_iso_transmission() +Save the image in a file and add a PGM header for viewing using gimp. +Finally call dc1394_release_camera to release the camera @@ -1606,15 +1608,14 @@ be set accordingly. failed error message being displayed. - Solution: (contributed by Ian and Tim)There are various reasons for this error message. Type dmesg in the command prompt to gain a better understanding of the problem. Here is a list of problem we ran into + Solution: (contributed by Ian and Tim)There are various reasons for this error message. Type dmesg in the command prompt to gain a better understanding of the problem. Here is a list of problem we ran into - Channel 0 is not being used- This means you are listening on the iso channel and then calling a capture function again. Make sure not to call dma_unlisten until you are ready to stop iso transmission. + Channel 0 is not being used- This means you are listening on the iso channel and then calling a capture function again. Make sure not to call dma_unlisten until you are ready to stop iso transmission. - Channel 0 is already being used- This means you have set two camera nodes to the same Channel. Fix your dma_setup_capture(). This could also mean that you have tried to call the setup function more than once without releasing the camera between the calls. This error is more likely to occur when you are working with more than one camera. - Buffer 0 is already being used- This means that you have not freed the DMA buffer before trying to write to it again. Make sure to alternate dma_done_with_buffer calls with dma_capture_calls + Channel 0 is already being used- This means you have set two camera nodes to the same Channel. Fix your dma_setup_capture(). This could also mean that you have tried to call the setup function more than once without releasing the camera between the calls. This error is more likely to occur when you are working with more than one camera. + Buffer 0 is already being used- This means that you have not freed the DMA buffer before trying to write to it again. Make sure to alternate dma_done_with_buffer calls with dma_capture_calls - - +