{"id":357,"date":"2020-08-18T19:23:47","date_gmt":"2020-08-18T20:23:47","guid":{"rendered":"http:\/\/www.linux-tutorial.info\/?page_id=77"},"modified":"2020-08-22T19:26:17","modified_gmt":"2020-08-22T20:26:17","slug":"this-is-the-page-title-toplevel-190","status":"publish","type":"page","link":"http:\/\/www.linux-tutorial.info\/?page_id=357","title":{"rendered":"Partitioning"},"content":{"rendered":"\n<title>Partitioning<\/title>\n<p>\nIf you have an existing <glossary>operating system<\/glossary> that takes up the whole disk, you will have\nto backup and reinstall the existing system to make room for Linux. You need\nto be careful because you may make <glossary>partition<\/glossary> too small\nfor all the files that were there before!\n<\/p>\n<p>\nA couple of tools are available on the Internet that will reformat a <glossary>DOS<\/glossary>\n<glossary>partition<\/glossary>\nwith an existing system (assuming there is enough free space). I have never used such a tool,\nalthough I have read messages on the Internet from people who have done it successfully.\n<\/p>\n<concept id=\"\" description=\"The fdisk command is used to partition a hard disk.\" \/>\n<question id=\"\" type=\"tf\" text=\"The fdisk command is used to partition a hard disk.\" \/>\n<question id=\"\" type=\"mc\" text=\"Which command is used to partition a hard disk?\" \/>\n<p>\nDuring the installation, you will have a chance to either install on an existing <glossary>partition<\/glossary>\nor repartition the drive. As with other PC-based OSs, use the <command>fdisk<\/command> tool to partition the drive.\nNost modern distributions have full-screen, menu-driven versions, but they all perform the same functions,\nsuch as creating, deleting, and making partitions active.\n<\/p>\n<concept id=\"\" description=\"Linux fdisk can do much more than DOS or Windows.\" \/>\n<p>\nHowever, the Linux <command>fdisk<\/command> can do much more than that. For example, it can change the <glossary>partition<\/glossary>\ntype, which is helpful when you need to have a system with several different OSs. <glossary>DOS<\/glossary> and older <glossary>Windows<\/glossary>\ncan only create a single primary and a single extended partition. I have used Linux to create all of\nthe necessary partitions and then DOS\/Windows to recognize them correctly.\n<\/p>\n<p>\nAnother useful thing is that the Linux <command>fdisk<\/command> will do what you tell it. Some time aog, I have wanted to delete an entire extended  <glossary>partition<\/glossary> on a Windows system, but couldn&#8217;t because logical partitions were there. Linux will do that for you.\n<\/p>\n<p>\nAs with other operating systems, Linux <command>fdisk<\/command> will see that other partitions are there, even\nthough it may not  know what type they really are. Linux is very good at recognizing the type,\nalthough there are a few cases in which I have seen it off the mark (but not by much). The reason is\nthat all fdisk versions just read the <glossary>partition<\/glossary> table, which is in a common\nformat.\n<\/p>\n<concept id=\"\" description=\"You can have more than 3 logical partitions.\" \/>\n<p>\n<strong>Warning:<\/strong> I have seen a number of Linux certification prep books that claim you can only have four primary partitions or three primary <glossary>partition<\/glossary> and one extended partition which is further broken down into four logical partitions for a total of seven (7) partitions. He is the partition layout of one hard disk on one of current systems:\n<\/p>\n<screenoutput>\n\/dev\/hda1   *         1       222   1783183+   7  HPFS\/NTFS\n\/dev\/hda2           223       229     56227+  83  Linux\n\/dev\/hda3           230       882   5245222+  83  Linux\n\/dev\/hda4           883      9963  72943132+   f  Win95 Ext&#8217;d (LBA)\n\/dev\/hda5           883      1078   1574338+  82  Linux swap\n\/dev\/hda6          1079      2384  10490413+  83  Linux\n\/dev\/hda7          2385      3037   5245191    c  Win95 FAT32 (LBA)\n\/dev\/hda8          3038      3168   1052226   83  Linux\n\/dev\/hda9          3169      6811  29262366   83  Linux\n\/dev\/hda10         6812      7072   2096451   83  Linux\n\/dev\/hda11         7073      7725   5245191   83  Linux\n<\/screenoutput>\n<p>\nThe first three partitions (<device>hda1<\/device>, <device>hda2<\/device>, and <device>hda3<\/device>) are all primary partitions. The extended partition (<device>hda4<\/device>) is devided into <strong>eight<\/strong> (8) or twice the\nnumber these books claim. This is very outdated information, but it still <em>may<\/em> appear on the Linux certification like this.\n<\/p>\n<question id=\"\" type=\"MC\" text=\"How much swap space does the Linux 2.6 kernel support on x86 machines?\" \/>\n<p>\nNote also that depending on how old the book is, it might tell you that there is a limit of 128 MB of swap. This is no longer true with Linux 2.2.x and later kernels. The current limits (Aug 2006) are approximately 2 GB on x86,MC680x0 and PowerPC, 512 MB on MIPS, 128 GB on Alpha, and <strong>3 Terabytes<\/strong> on UltraSparc.\n<\/p>\n<question id=\"\" type=\"MC\" text=\"You can tell if you have a logical partition because it partition number is at least what?\" \/>\n<concept id=\"\" description=\"Logical partitions numbers start a 5.\" \/>\n<p>\nAs you can see in the example above, the logical partitions start number at 5. This is true whether or not you are using up all of the primary partitions and is the same for <glossary>IDE<\/glossary>\nas well as <glossary>SCSI<\/glossary> drives.\n<\/p>\n<p>\nDuring the installation of Linux, you will typically have a choice of doing an automatic or manual installation, and in some cases a combination of the two. If you chose a manual installation you will probably be allowed to defined the partition layout of your hard disks. On SUSE linux you have an &#8220;expert&#8221; mode which looks something like this:\n<\/p>\n<img loading=\"lazy\" decoding=\"async\" src=\"yast_partition1.png\" width=\"804\" height=\"630\" border=\"0\" usemap=\"#yast_partition1\">\n<map name=\"yast_partition1\">\n<!-- #$-:Image Map file created by GIMP Imagemap Plugin -->\n<!-- #$-:GIMP Imagemap Plugin by Maurits Rijk -->\n<!-- #$-:Please do not edit lines starting with \"#$\" -->\n<!-- #$VERSION:1.4 -->\n<!-- #$AUTHOR:James Mohr -->\n<area shape=\"rect\" coords=\"4,108,215,621\" href=\"popup#additional information#Here you find more information to help you partition your disk.\" \/>\n<area shape=\"rect\" coords=\"248,148,311,480\" href=\"popup#device nodes#The device node of the respective partition.\" \/>\n<area shape=\"rect\" coords=\"312,147,394,480\" href=\"popup#partition size#The size of the partition. Typically in either megabytes or gigabytes.\" \/>\n<area shape=\"rect\" coords=\"395,149,430,480\" href=\"popup#format the partition#This specifies whether a filesystem should be created or not(i.e. format)\" \/>\n<area shape=\"rect\" coords=\"431,147,570,480\" href=\"popup#partition type#The \\'translated\\' name of the partition type (i.e not the partition code)\" \/>\n<area shape=\"rect\" coords=\"571,149,644,480\" href=\"popup#mount point#The directory onop which this file system is to be mount.\" \/>\n<area shape=\"rect\" coords=\"645,149,700,480\" href=\"popup#start block#The starting block of the partition relative to the start of the hard disk.\" \/>\n<area shape=\"rect\" coords=\"701,148,781,480\" href=\"popup#end block#The ending block of the partition relative to the start of the hard disk.\" \/>\n<area shape=\"rect\" coords=\"235,107,800,505\" href=\"popup#existing partions#By default all partition on all available hard disks are displayed.\" \/>\n<area shape=\"rect\" coords=\"235,506,796,626\" href=\"popup#function buttons#Buttons for various functions.\" \/>\n<\/map>\n<p>\n<p>\n<icaption>SUSE Linux YAST &#8211; Hard disk partitioning<\/icaption>\n<\/p>\n<p>\nNote that this what is displayed here is what you get when you start YAST <em>after<\/em> the system is installed, so what you see during the installation will probably look different. You can see that the start cylinder of the first partition is 0.\nHowever in the text output above, the starting cylinder is 1. In fact, if you compare the two they are essentially identical except that the values differ by 1. So, you need\nto be careful if you are using values taking from <command>fdisk<\/command> (as above) and want to input them into YAST.\n<\/p>\n<p>When you select the <keyinput>Create<\/keyinput> button, you reach the following screen:\n<\/p>\n<img loading=\"lazy\" decoding=\"async\" src=\"yast_partition2.png\" width=\"634\" height=\"447\" border=\"0\" usemap=\"#yast_partition2\" \/>\n<map name=\"yast_partition2\">\n<!-- #$-:Image Map file created by GIMP Imagemap Plugin -->\n<!-- #$-:GIMP Imagemap Plugin by Maurits Rijk -->\n<!-- #$-:Please do not edit lines starting with \"#$\" -->\n<!-- #$VERSION:1.4 -->\n<!-- #$AUTHOR:James Mohr -->\n<area shape=\"rect\" coords=\"8,29,188,439\" href=\"popup#additional information#Here you find more information to help you partition your disk.\" \/>\n<area shape=\"rect\" coords=\"191,84,401,380\" href=\"popup#formatting options#here you define whether to format the partition or not, what filesystem type to use, filesystem options and so forth.\" \/>\n<area shape=\"rect\" coords=\"419,138,617,185\" href=\"popup#starting cylinder#\" \/>\n<area shape=\"rect\" coords=\"424,196,621,245\" href=\"popup#ending cylinder#Here you can also specify the size of the partition in megabytes or gibabyte.\" \/>\n<area shape=\"rect\" coords=\"419,266,625,303\" href=\"popup#fstab options#Here are the options that are written to the \/etc\/fstab file.\" \/>\n<area shape=\"rect\" coords=\"412,320,624,394\" href=\"popup#mount point#This is the directory onto which the filesystem is mounted.\" \/>\n<\/map>\n<p>\n<icaption>SUSE Linux YAST &#8211; Partition and file system configuration<\/icaption>\n<\/p>\n<p>\nHere you are defining various parameters for this partition and the associated filesystem. In some cases, it is logical not to format the partition (i.e. create a filesystem). For example, if you are recovering from a crash where the partition table was destroyed, you can usually recover the filesystem fully if you simply input the appropriate values for the starting cylinder, ending cylinder and mount point.\n<\/p>\n<question id=\"\" type=\"TF\" text=\"If you specify a specific size and not start-end cylinders when creating a partition, it might get rounded to end on a cylinder boundary.\" \/>\n<concept id=\"\" description=\"If you specify a specific size and not start-end cylinders when creating a partition, it might get rounded to end on a cylinder boundary.\" \/>\n<p>\nBe careful when you specify the size of the partition but always specify the ending cylinder. This is because the size is not an exact value. You might think that the correct value is (for example) 4.3 GB, but because of the technical aspects of one of your hard disks it is closer to 4.26 GB. Inputting 4.3 GB might round down to only 4.28 GB on another disk, which is larger than you want. However, if you specify the ending cylinder, you always have the correct value.\n<\/p>\n<p>\nFor the most part this is not an issue, as you typically do not really care if the drive is 4.26 or 4.28. However, if you setting up a <glossary>RAID<\/glossary> system, having the drives the same size is obviously important.\n<\/p>\n<concept id=\"\" description=\"The options that are provided when creating a filesystem will differ depending on the filesystem type you choose.\" \/>\n<p>\nThe options that are provided when creating the filesystem will differ depending on the filesystem type you choose. For example, if you choose a type <glossary>swap<\/glossary> there are no options. If you choose and EXT3 filesystem, you can choose (for example); the block size, such as\n1024, 2048, or 4096 bytes per block. If you select auto then the block size is determined by the file system size. Other filesystem have different options which appear in the left-hand frame when you choose the respective file system type.\n<\/p>\n<p>\nPartitioning by hand using <command>fdisk<\/command> uses the same basic\nconcepts. However, instead of showing all of the partitions on all of you hard disks,\nyou need to specify the <glossary>device node<\/glossary> for the hard disk you which\nto partition (assuming you have more than one). For example, to partition the first IDE hard disk, the command might look\nlike this:\n<\/p>\n<commandexample command=\"fdisk\">\nfdisk \/dev\/hda\n<\/commandexample>\n<concept id=\"\" description=\"When starting fdisk you specify the whole disk and not just a single partition.\" \/>\n<question id=\"\" type=\"tf\" text=\"When starting fdisk you specify the whole disk and not just a single partition.\" \/>\n<p>\nBe careful that this is the <glossary>device node<\/glossary> of the <strong>entire<\/strong> hard disk and\nnot an individual partition like <device>\/dev\/hda1<\/device>. If you should\nspecify an individual partition, you will end up with a message like this:\n<\/p>\n<screenoutput>\nDevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel\nBuilding a new DOS disklabel. Changes will remain in memory only,\nuntil you decide to write them. After that, of course, the previous\ncontent won&#8217;t be recoverable.\nWarning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)\n<\/screenoutput>\n<p>\nWith a never version of <command>fdisk<\/command> (fdisk v2.12q, run in August 2006), I got different output:\n<\/p>\n<screenoutput>\nCommand (m for help): p\nDisk \/dev\/hda1: 1825 MB, 1825979904 bytes\n16 heads, 63 sectors\/track, 3538 cylinders\nUnits = cylinders of 1008 * 512 = 516096 bytes\nThis doesn&#8217;t look like a partition table\nProbably you selected the wrong device.\n     Device Boot      Start         End      Blocks   Id  System\n\/dev\/hda1p1   ?        7571     1693696   849806598+  72  Unknown\nPartition 1 does not end on cylinder boundary.\n\/dev\/hda1p2   ?     1383568     2105988   364099898   72  Unknown\nPartition 2 does not end on cylinder boundary.\n\/dev\/hda1p3   ?      166444      166444           0   45  Unknown\nPartition 3 does not end on cylinder boundary.\n\/dev\/hda1p4         2804720     2804772       25947    0  Empty\nPartition 4 does not end on cylinder boundary.\nPartition table entries are not in disk order\n<\/screenoutput>\n<p>\nWith an even later verion of <command>fdisk<\/command> (disk v2.12q, run in August 20090), I got output similar to the first:\n<\/p>\n<screenoutput>\nDevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel\nBuilding a new DOS disklabel with disk identifier 0xab611276.\nChanges will remain in memory only, until you decide to write them.\nAfter that, of course, the previous content won&#8217;t be recoverable.\n<\/screenoutput>\n<p>\nIf you made changes and then decided to write the partition table, it will not do what you expect and you probably have lost all the data on the partition. Note that when you run <glossary>YAST<\/glossary> it warns you about only making changes if you know what you are doing. I can only add: Heed the warning!\n<\/p>\n<p>\nNotice the warning about the number of cylinders. This is usually only an issue when booting the system and loading the kernel. Typically, I have by <directory>\/boot<\/directory> directory on a separate file system that is one of the first two partitions. I make sure that the this partition ends below cylinder 1024 to ensure that there are no problems when booting. As with the GUI version (shown above), you can specify the ending cylinder so you don&#8217;t have to do any calculations yourself in figuring out how big the partition is.\n<\/p>\n<p>\nIf you press <keyinput>m<\/keyinput> at this point, you get the following &#8220;menu&#8221;:\n<\/p>\n<screenoutput>\nCommand action\n   a   toggle a bootable flag\n   b   edit bsd disklabel\n   c   toggle the dos compatibility flag\n   d   delete a partition\n   l   list known partition types\n   m   print this menu\n   n   add a new partition\n   o   create a new empty DOS partition table\n   p   print the partition table\n   q   quit without saving changes\n   s   create a new empty Sun disklabel\n   t   change a partition&#8217;s system id\n   u   change display\/entry units\n   v   verify the partition table\n   w   write table to disk and exit\n   x   extra functionality (experts only)\n<\/screenoutput>\n<p>\nTo look at the existing partition partitions you input <keyinput>p<\/keyinput>, which\ngives you something like this:\n<\/p>\n<screenoutput>\nDisk \/dev\/hda: 81.9 GB, 81964302336 bytes\n255 heads, 63 sectors\/track, 9964 cylinders\nUnits = cylinders of 16065 * 512 = 8225280 bytes\n   Device Boot    Start       End    Blocks   Id  System\n\/dev\/hda1   *         1       222   1783183+   7  HPFS\/NTFS\n\/dev\/hda2           223       229     56227+  83  Linux\n\/dev\/hda3           230       882   5245222+  83  Linux\n\/dev\/hda4           883      9963  72943132+   f  Win95 Ext&#8217;d (LBA)\n\/dev\/hda5           883      1078   1574338+  82  Linux swap\n\/dev\/hda6          1079      2384  10490413+  83  Linux\n\/dev\/hda7          2385      3037   5245191    c  Win95 FAT32 (LBA)\n\/dev\/hda8          3038      3168   1052226   83  Linux\n\/dev\/hda9          3169      6811  29262366   83  Linux\n\/dev\/hda10         6812      7072   2096451   83  Linux\n\/dev\/hda11         7073      7725   5245191   83  Linux\n<\/screenoutput>\n<p>\n<em>(Note that this is the same table as above)<\/em>\n<\/p>\n<p>\nIf you take a close look, you will see that the extended partition (<device>\/dev\/hda4<\/device>) goes up to cylinder 9963. However, the last partition only goes up to cylinder 7725, thus there is a fair bit of free, unpartitioned space on this drive. If I want to create a new partition, I input <keyinput>n<\/keyinput>, which then prompts me for a start cylinder:\n<\/p>\n<screenoutput>\nFirst cylinder (7726-9963, default 7726):\n<\/screenoutput>\n<p>\nSince there is already three primary partition and one extended partition, you can only create  a new logical partition. If some of these partitions were missing, you would be prompted to select the kind of partion with a prompt like this:\n<\/p>\n<screenoutput>\nCommand action\n   e   extended\n   p   primary partition (1-4)\n<\/screenoutput>\n<concept id=\"\" description=\"Note that the start (first) cylinder is always 1 more than the last cylinder of the previous partition.\" \/>\n<concept id=\"\" description=\"Because fdisk usually ends partitions on cylinder boundaries, when you create a partition of a particular size it is typically small than you expected.\" \/>\n<p>\nNote that the start (first) cylinder is always 1 more than the last cylinder of the previous partition. If you then input 7726 (or simply press return) you are prompted to input either the size of the partition or the end\/last cylinder. The default is the last available cylinder. Note that the calculation of the partition size is not exact if\nyour specify the size. The <command>fdisk<\/command> command will fit the size to\n<glossary>cylinder boundary<\/glossary> and thus it is typically a smaller less than you expect.\n<\/p>\n<p>\nBy default, <command>fdisk<\/command> will create a standard linux partition (as you can see in the last two columns). If you want to create a diffent kind of partion, you would input the <keyinput>t<\/keyinput> option to specify the type. Next you would input the number of the partition (so we might input <keyinput>12<\/keyinput> if we were adding a new partition) and then the hex code of the desired type. If you are not sure, you can input <keyinput>L<\/keyinput> and you will be shown a table of possible partition types:\n<\/p>\n<screenoutput>\n 0  Empty           1e  Hidden W95 FAT1 80  Old Minix       be  Solaris boot\n 1  FAT12           24  NEC DOS         81  Minix \/ old Lin bf  Solaris\n 2  XENIX root      39  Plan 9          82  Linux swap \/ So c1  DRDOS\/sec (FAT-\n 3  XENIX usr       3c  PartitionMagic  83  Linux           c4  DRDOS\/sec (FAT-\n 4  FAT16 &lt;32M      40  Venix 80286     84  OS\/2 hidden C:  c6  DRDOS\/sec (FAT-\n 5  Extended        41  PPC PReP Boot   85  Linux extended  c7  Syrinx\n 6  FAT16           42  SFS             86  NTFS volume set da  Non-FS data\n 7  HPFS\/NTFS       4d  QNX4.x          87  NTFS volume set db  CP\/M \/ CTOS \/ .\n 8  AIX             4e  QNX4.x 2nd part 88  Linux plaintext de  Dell Utility\n 9  AIX bootable    4f  QNX4.x 3rd part 8e  Linux LVM       df  BootIt\n a  OS\/2 Boot Manag 50  OnTrack DM      93  Amoeba          e1  DOS access\n b  W95 FAT32       51  OnTrack DM6 Aux 94  Amoeba BBT      e3  DOS R\/O\n c  W95 FAT32 (LBA) 52  CP\/M            9f  BSD\/OS          e4  SpeedStor\n e  W95 FAT16 (LBA) 53  OnTrack DM6 Aux a0  IBM Thinkpad hi eb  BeOS fs\n f  W95 Ext&#8217;d (LBA) 54  OnTrackDM6      a5  FreeBSD         ee  EFI GPT\n10  OPUS            55  EZ-Drive        a6  OpenBSD         ef  EFI (FAT-12\/16\/\n11  Hidden FAT12    56  Golden Bow      a7  NeXTSTEP        f0  Linux\/PA-RISC b\n12  Compaq diagnost 5c  Priam Edisk     a8  Darwin UFS      f1  SpeedStor\n14  Hidden FAT16 &lt;3 61  SpeedStor       a9  NetBSD          f4  SpeedStor\n16  Hidden FAT16    63  GNU HURD or Sys ab  Darwin boot     f2  DOS secondary\n17  Hidden HPFS\/NTF 64  Novell Netware  b7  BSDI fs         fd  Linux raid auto\n18  AST SmartSleep  65  Novell Netware  b8  BSDI swap       fe  LANstep\n1b  Hidden W95 FAT3 70  DiskSecure Mult bb  Boot Wizard hid ff  BBT\n<\/screenoutput>\n<p>\nNote that the table you have might look different as different partition types are added.\n<\/p>\n<p>\nMost of the partition types listed are once that you probably never have heard of, let alone need. Looking at the <command>fdisk<\/command> output above, I only use a small fraction of these and have only ever needed a couple of others. Still, there are valid reasons to use any of the them.\n<\/p>\n<p>\nAt this point the partition table has <strong>not<\/strong> yet been changed. The changes are only in memory. It not until you input <keyinput>w<\/keyinput> to write the partition table and quit.\n<\/p>\n<question id=\"\" type=\"TF\" text=\"If you use fdisk to create the partition, you must manually create the file system.\" \/>\n<concept id=\"\" description=\"If you use fdisk to create the partition, you must manually create the file system.\" \/>\n<concept id=\"\" description=\"Creating a filesystem is comparable to formating a partition under DOS\/Windows,\" \/>\n<p>\nUnlike when you use the YAST or another GUI, you are still not done. Unless you created a swap or other type of &#8220;administrative&#8221; partition, you cannot use the partition as it because it needs\nas file system. Creating a filesystem is comparable to formating a partition under DOS, the details of which can be found <site id=\"332\">here<\/site>.\n<\/p>\n<p>\nThe type of applications you are going to run on your server should guide you when deciding how you want to partition your system. As discussed previously, partitions  are often created for\n<directory>\/boot<\/directory>, <directory>\/usr<\/directory>, <directory>\/var<\/directory>, <directory>\/opt<\/directory>, and <directory>\/home<\/directory>. It is also common that data or files related\nto your application are stored on a seperate partition. For example, on a database server, the database files are often stored on an seperate partition. It is also common to store these files on\na seperate hard disk, which typically improves performance because the work is spread acrosss multiple disks.\n<\/p>\n<p>\nAnother consider here is to consider putting the data on the fastest drive you have. If your applications do a lot of logging, you might also want to consider putting <directory>\/var<\/directory>\non a faster disk. Keep in mind that if both data and log files are on the same disk, you might be shooting yourself in the foot because the disk is so busy that it eliminates any benefits from the\nextra speed.\n<\/p>\n<p>\n<ul>\n<li>Database server<\/li>\n<li>Application server<\/li>\n<li>Web server<\/li>\n<li>Mail Server<\/li>\n<\/ul>\n<\/p>\n<p>\nChoosing the right hard disk is just as important as choosing the right partitioning.\n<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Partitioning If you have an existing operating system that takes up the whole disk, you will have to backup and reinstall the existing system to make room for Linux. You need to be careful because you may make partition too &hellip; <a href=\"http:\/\/www.linux-tutorial.info\/?page_id=357\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-357","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=357"}],"version-history":[{"count":1,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/357\/revisions"}],"predecessor-version":[{"id":650,"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=\/wp\/v2\/pages\/357\/revisions\/650"}],"wp:attachment":[{"href":"http:\/\/www.linux-tutorial.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}