{"id":501,"date":"2012-07-17T12:39:46","date_gmt":"2012-07-17T12:39:46","guid":{"rendered":"http:\/\/naich.net\/wordpress\/?p=501"},"modified":"2012-08-17T15:09:03","modified_gmt":"2012-08-17T15:09:03","slug":"appendixes","status":"publish","type":"post","link":"https:\/\/naich.net\/wordpress\/index.php\/appendixes\/","title":{"rendered":"Appendixes"},"content":{"rendered":"<p>These are appendixes from the <a href=\"http:\/\/naich.net\/wordpress\/?p=435\">set of posts<\/a> about setting up and using a Raspberry Pi.<\/p>\n<h3><a href=\"http:\/\/naich.net\/wordpress\/?p=457\">Appendix A: Selecting an IP Address<\/a><\/h3>\n<p>As part of the boot process, your Pi used <a title=\"It's fun to stay at the DHCP\" href=\"http:\/\/en.wikipedia.org\/wiki\/Dynamic_Host_Configuration_Protocol\" target=\"_blank\">DHCP<\/a> to get an IP address from the router. The problem with this is that it is an automated process which is invisible to you unless you log onto your router&#8217;s admin page to discover it.\u00c2\u00a0 If only the Pi and your router know what its IP address is, you don&#8217;t know where to log on to your Pi.\u00c2\u00a0 The easiest thing to do is change the IP settings on the Pi&#8217;s card to a static address, assigned by you.\u00c2\u00a0 That way you know what it is and you know it won&#8217;t change.\u00c2\u00a0 You don&#8217;t need to let the router know which address you have chosen, as the magic IPixies in the Pi sprinkle the router with their Ipixie Dust to let it know automatically.\u00c2\u00a0 Well, they do for all I know; I&#8217;ve no idea how the router finds out, but it does.<\/p>\n<p>You need to pick an address for your Pi &#8211; something like 192.168.1.16, but you want to pick one that is not in the range of addresses your router assigns for DHCP requests.\u00c2\u00a0 If the address you choose is within the router&#8217;s DHCP address range there is a possibility that you will end up with two devices using the same address.<\/p>\n<p>I&#8217;m going to leave it to you to find out what range of addresses your router assigns for DHCP and which ones are suitable for static IP addresses.\u00c2\u00a0 The settings will be available somewhere in your router&#8217;s admin pages.\u00c2\u00a0 If fiddling around with your router is out of the question, as a quick bodge you could try <a href=\"http:\/\/windows.microsoft.com\/en-us\/windows-vista\/Find-your-computers-IP-address\" target=\"_blank\">finding the IP address of your PC<\/a> in order to guess a safe non-DHCP range address for your Pi.\u00c2\u00a0 Copy the first 3 sets of numbers of your PC&#8217;s address and change the last number to a low one if it&#8217;s not low or a high one (maximum 254) if it is low. \u00c2\u00a0e.g.<\/p>\n<ul>\n<li>Your PC&#8217;s IP is 192.168.1.3 so you pick 192.168.1.250 for your Pi<\/li>\n<li>Your PC&#8217;s IP is 192.168.1.101 so you pick 192.168.1.3 for your Pi<\/li>\n<\/ul>\n<p>You also need to know the <a href=\"http:\/\/wiki.answers.com\/Q\/How_do_you_find_the_gateway_address_and_subnet_mask\" target=\"_blank\">gateway<\/a> (the router&#8217;s IP address on the LAN) and subnet mask (which will probably be 255.255.255.0 &#8211; it usually is for home networks).<\/p>\n<p><a href=\"http:\/\/naich.net\/wordpress\/?p=457\">Go back<\/a><\/p>\n<h3>Appendix B: The Linux Filesystem<\/h3>\n<p>Here&#8217;s a quick and dirty note about the way the Linux filesystem is arranged.\u00c2\u00a0 For a better description try <a href=\"http:\/\/freeos.com\/articles\/3102\/\">this<\/a> or <a href=\"http:\/\/www.tuxradar.com\/content\/take-linux-filesystem-tour\">this<\/a>.<\/p>\n<p>You might be used to Windows, with its lame C: drives, D: drives, random assignation of drive letters for plug-in devices, and its pathetic attempts to hide this lameness with My Documents, libraries and other rubbish. \u00c2\u00a0Linux has one hierarchical tree of files, with everything hanging off the root &#8220;\/&#8221; directory.\u00c2\u00a0 There are no drive letters or special places; everything &#8211; programs, user data, log files, temporary files and even devices, is placed on the same directory tree.\u00c2\u00a0 There is a convention as to <a href=\"http:\/\/www.tuxfiles.org\/linuxhelp\/linuxdir.html\/\">where different types of file are stored<\/a>, but let&#8217;s have a little wander around and see for ourselves.<\/p>\n<p>Take a look at the command prompt &#8211; &#8220;naich@raspberrypi ~ $&#8221;\u00c2\u00a0 It contains 4 pieces of information; your name and the name of the computer you are on (with an &#8220;@&#8221; between them), the working directory (~) and the effective user ID ($).\u00c2\u00a0 The &#8220;$&#8221; changes to a &#8220;#&#8221; if you are currently root &#8211; that&#8217;s all that does, but it is important to know if your powers are currently elevated to those of the godly root.\u00c2\u00a0 The working directory is where you currently are in the directory tree, i.e. it is the directory that a command will take action in if you don&#8217;t actually specify which directory you want the command to do its stuff in.\u00c2\u00a0 Get it?\u00c2\u00a0 No?\u00c2\u00a0 An example will demonstrate better than that convoluted jumble of words; type <strong><tt>ls<\/tt><\/strong>:<\/p>\n<blockquote>\n<pre>naich@raspberrypi: ~ $ ls\r\nnaich@raspberrypi: ~ $<\/pre>\n<\/blockquote>\n<p>See anything?\u00c2\u00a0 Nope.\u00c2\u00a0 <strong><tt>ls<\/tt><\/strong> means list all the files in a directory.\u00c2\u00a0 As you did not specify a directory it lists the files in the working directory, which is &#8220;~&#8221;, and is currently empty.\u00c2\u00a0 If you tell it to list files in a different directory it will use that one instead of the working one; type <strong><tt>ls \/<\/tt><\/strong>:<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls \/\r\nbin\u00c2\u00a0\u00c2\u00a0 dev\u00c2\u00a0 home\u00c2\u00a0 lost+found\u00c2\u00a0 mnt\u00c2\u00a0 proc\u00c2\u00a0 run\u00c2\u00a0\u00c2\u00a0 selinux\u00c2\u00a0 sys\u00c2\u00a0 usr\r\nboot\u00c2\u00a0 etc\u00c2\u00a0 lib\u00c2\u00a0\u00c2\u00a0 media\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 opt\u00c2\u00a0 root\u00c2\u00a0 sbin\u00c2\u00a0 srv\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 tmp\u00c2\u00a0 var\r\nnaich@raspberrypi ~ $<\/pre>\n<\/blockquote>\n<p>These are all the files and directories in the root directory &#8220;\/&#8221;.\u00c2\u00a0 Try <strong><tt>ls \/bin<\/tt><\/strong> &#8211; see what is happening there?\u00c2\u00a0 You are listing all the files in the &#8220;\/bin&#8221; directory.\u00c2\u00a0 This rule also goes for file names.\u00c2\u00a0 If you want to access a file but only write a file name, the command or program will look for that file in the working directory.\u00c2\u00a0 If you include the directory that the file is in, it will look there instead. This goes for any type of file &#8211; data, programs or devices.\u00c2\u00a0 Think of your terminal window as psychically sitting on a branch of the directory tree, with everything you type in acting on that branch unless you explicitly specify otherwise.\u00c2\u00a0 The location of that branch is the working directory.<\/p>\n<blockquote><p><strong>Handy hint<\/strong> &#8211; Stuff shooting off the top your screen before you can read it?\u00c2\u00a0 Add &#8220;<strong><tt> | more<\/tt><\/strong>&#8221; to the end of your command, (e.g. <strong><tt>ls \/bin | more<\/tt><\/strong>) to show one page of output at a time.\u00c2\u00a0 Scroll to the next page with the space bar or press &#8220;Q&#8221; to quit.\u00c2\u00a0 This works with all commands.\u00c2\u00a0 Don&#8217;t try to understand how it works for the moment, just consider it magic.<\/p><\/blockquote>\n<p>You can move your terminal around the directory tree with the <strong><tt>cd<\/tt><\/strong> (change directory) command.\u00c2\u00a0 Type <strong><tt>cd \/<\/tt><\/strong> to move your working directory to the root directory and type <strong><tt>ls<\/tt><\/strong> again.\u00c2\u00a0 Now your working directory is &#8220;\/&#8221;, it lists the files there when you don&#8217;t explicitly say otherwise.\u00c2\u00a0 Try moving to &#8220;\/bin&#8221; and looking at the files there.\u00c2\u00a0 Try moving to other places and have a good old poke around.\u00c2\u00a0 Even with a basic install there are tens of thousands of files on your Pi, so there&#8217;s plenty to look at.\u00c2\u00a0 When you are done, move back to your home directory by simply typing <strong><tt>cd ~<\/tt><\/strong>.<\/p>\n<p>As well as looking at the the prompt, another way to find out the working directory is to type <strong><tt>pwd<\/tt><\/strong>:<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ pwd\r\n\/home\/naich\r\nnaich@raspberrypi ~ $<\/pre>\n<\/blockquote>\n<p>Eh?\u00c2\u00a0 I thought we were in &#8220;~&#8221;?\u00c2\u00a0 Well, we are.\u00c2\u00a0 &#8220;~&#8221; means &#8220;my home directory&#8221;, which is &#8220;\/home\/your_username&#8221;.\u00c2\u00a0 Your home directory is where you put all your stuff and is probably the only directory you can write to.\u00c2\u00a0 If you are going to start drawing Windows analogies, it is a bit like &#8220;My Documents&#8221;.\u00c2\u00a0 The &#8220;~&#8221; provides a reference to where all your stuff is, so using &#8220;~\/README.txt&#8221; refers to README.txt which resides in your home directory, rather than any other README.txt which might be in whatever working directory you happen to be in.<\/p>\n<p>It&#8217;s all relative though.\u00c2\u00a0 When you specify a directory to move to, look in, or to find a file in, the location you give is relative to where you currently are &#8211; i.e. your working directory.\u00c2\u00a0 If you start the directory location off with a &#8220;\/&#8221; or &#8220;~\/&#8221; it doesn&#8217;t matter where you are, as the location you are specifying starts at the root or home directory.\u00c2\u00a0 These are fixed absolute points on the tree, but miss off the &#8220;\/&#8221; or &#8220;~\/&#8221; from the start of the directory or file and it becomes relative to your working directory.\u00c2\u00a0 Type <strong><tt>cd \/usr<\/tt><\/strong> to move your working directory to the &#8220;\/usr&#8221; directory.\u00c2\u00a0 Do a <strong><tt>ls<\/tt><\/strong> to see the contents.\u00c2\u00a0 See that directory called &#8220;bin&#8221;?\u00c2\u00a0 It&#8217;s not the one you looked at earlier; that was a directory for general system bin(ary) programs, this one is for user-orientated bin(ary) programs.\u00c2\u00a0 Type <strong><tt>ls bin<\/tt><\/strong>.\u00c2\u00a0 The files listed are not the ones you saw earlier in &#8220;\/bin&#8221; but are the ones in &#8220;\/usr\/bin&#8221;.\u00c2\u00a0 Because the &#8220;\/&#8221; is missing from the front of &#8220;bin&#8221;, the &#8220;bin&#8221; it is showing you is the one relative to your working directory, which is currently &#8220;\/usr&#8221;.\u00c2\u00a0 You can still see the contents of &#8220;\/bin&#8221; (with the slash) by typing <strong><tt>ls \/bin<\/tt><\/strong> (with the slash).<\/p>\n<p>If you understand the concept that everything is relative to the working directory unless you say so, you are ready to know about dots &#8211; &#8220;..&#8221;, &#8220;.&#8221; and dots at the start of files.<\/p>\n<p>A double dot is shorthand for &#8220;the parent directory&#8221;, i.e. the next directory down on the way to the root.\u00c2\u00a0 If your working directory is &#8220;\/home\/naich&#8221; then typing <strong><tt>cd ..<\/tt><\/strong> will change your working directory to &#8220;\/home&#8221;.\u00c2\u00a0 Typing <strong><tt>ls ..<\/tt><\/strong> will list the contents of &#8220;\/home&#8221; and so on.\u00c2\u00a0 You can string double dots together as if they were real directories. <strong><tt>cd ..\/..<\/tt><\/strong> will move you <em>two<\/em> directories towards root &#8211; from &#8220;\/home\/naich&#8221; to &#8220;\/&#8221;.\u00c2\u00a0 You can do daft things like <strong><tt>cd \/home\/naich\/..\/..\/home\/naich<\/tt><\/strong> to end up in &#8220;\/home\/naich&#8221;, the first &#8220;\/home\/naich&#8221; having been rendered pointless by the two sets of double dots moving you back down to &#8220;\/&#8221; again.<\/p>\n<p>A single dot means &#8220;this directory&#8221;, i.e. the current working directory.\u00c2\u00a0 That might not sounds useful, seeing as how, by it&#8217;s very nature, you are already working in the working directory but it does have its uses.\u00c2\u00a0 I&#8217;m not going to go in to them here, but you should know about it in case you see it later on.<\/p>\n<p>Finally, there are hidden files.\u00c2\u00a0 These are hidden for convenience not security and are simply files that you don&#8217;t care about in the normal scheme of things.\u00c2\u00a0 Files like configuration files or log files.\u00c2\u00a0 You can hide a file or directory by starting its name with a dot, e.g. &#8220;.config_file&#8221;.\u00c2\u00a0 You have some in your home directory but didn&#8217;t see them earlier.\u00c2\u00a0 Go home (<strong><tt>cd ~<\/tt><\/strong>) and have a closer look &#8211; type <strong><tt>ls -a<\/tt><\/strong>.<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls -a\r\n.\u00c2\u00a0 ..\u00c2\u00a0 .bash_history\u00c2\u00a0 .bash_logout\u00c2\u00a0 .bashrc\u00c2\u00a0 .profile\r\nnaich@raspberrypi ~ $<\/pre>\n<\/blockquote>\n<p>The &#8220;-a&#8221; bit is an &#8220;option&#8221; that tells the &#8220;ls&#8221; command to show hidden files.\u00c2\u00a0 Those hidden files are configuration files that are automatically generated when you create a user and control parameters about the way your terminal works.\u00c2\u00a0 Most of the time you don&#8217;t need to see them, so they are hidden.\u00c2\u00a0 You can also see the &#8220;.&#8221; and &#8220;..&#8221;, which show up as directories in their own right.<\/p>\n<p><a title=\"Another pi pun\" href=\"http:\/\/naich.net\/wordpress\/?p=526\">Go back<\/a><\/p>\n<h3>Appendix C: Commands<\/h3>\n<p>The basic format for doing things from the command line has 3 sections separated by spaces:<\/p>\n<blockquote>\n<pre>command [-options] [the_thing_you_are_doing_it_to]<\/pre>\n<\/blockquote>\n<p>An &#8220;option&#8221; is a way to modify what the command does.\u00c2\u00a0 For example, the default thing for the <strong><tt>ls<\/tt><\/strong> command to do is show the files as a horizontal list, so to list all the files in the root &#8220;\/&#8221; directory:<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls \/\r\nbin\u00c2\u00a0\u00c2\u00a0 dev\u00c2\u00a0 home\u00c2\u00a0 lost+found\u00c2\u00a0 mnt\u00c2\u00a0 proc\u00c2\u00a0 run\u00c2\u00a0\u00c2\u00a0 selinux\u00c2\u00a0 sys\u00c2\u00a0 usr\r\nboot\u00c2\u00a0 etc\u00c2\u00a0 lib\u00c2\u00a0\u00c2\u00a0 media\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 opt\u00c2\u00a0 root\u00c2\u00a0 sbin\u00c2\u00a0 srv\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 tmp\u00c2\u00a0 var\r\nnaich@raspberrypi \/ $<\/pre>\n<\/blockquote>\n<p>but if you add the option &#8220;-l&#8221; (minus lower case L) to the &#8220;ls&#8221; command it does this:<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls -l \/\r\ntotal 84\r\ndrwxr-xr-x\u00c2\u00a0 2 root root\u00c2\u00a0 4096 Aug\u00c2\u00a0 6 12:35 bin\r\ndrwxr-xr-x\u00c2\u00a0 2 root root 16384 Jan\u00c2\u00a0 1\u00c2\u00a0 1970 boot\r\n... skip a few ...\r\ndrwxr-xr-x 10 root root\u00c2\u00a0 4096 Jul 15 19:57 usr\r\ndrwxr-xr-x 11 root root\u00c2\u00a0 4096 Jul 15 20:42 var\r\nnaich@raspberrypi \/ $<\/pre>\n<\/blockquote>\n<p>The &#8220;-l&#8221; means print it in &#8220;long&#8221; format, i.e. with more information about what sort of file or directory it is (the &#8220;d&#8221; in &#8220;drwxr-xr-x&#8221; means directory, don&#8217;t worry about the rest for now), who owns it (&#8220;root&#8221;), the group they are in (root), the size of the file, date it was last modified and its name.\u00c2\u00a0 You can have more than one option.\u00c2\u00a0 Try <strong><tt>ls -lh \/<\/tt><\/strong>.\u00c2\u00a0 The &#8220;h&#8221; means put the file sizes in human readable units.<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls -lh \/\r\ntotal 84K\r\ndrwxr-xr-x\u00c2\u00a0 2 root root 4.0K Aug\u00c2\u00a0 6 12:35 bin\r\ndrwxr-xr-x\u00c2\u00a0 2 root root\u00c2\u00a0 16K Jan\u00c2\u00a0 1\u00c2\u00a0 1970 boot\r\n... and so on<\/pre>\n<\/blockquote>\n<p>You could make it show you hidden files (&#8220;-a&#8221;), in date order (&#8220;-t&#8221;), but reversed so the latest is at the bottom (&#8220;-r&#8221;) by using <strong><tt>ls -lhatr \/<\/tt><\/strong><\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls -lahtr \/\r\ntotal 92K\r\ndrwxr-xr-x\u00c2\u00a0 2 root root\u00c2\u00a0 16K Jan\u00c2\u00a0 1\u00c2\u00a0 1970 boot\r\ndr-xr-xr-x 68 root root\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 0 Jan\u00c2\u00a0 1\u00c2\u00a0 1970 proc\r\ndrwxr-xr-x 12 root root\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 0 Jan\u00c2\u00a0 1\u00c2\u00a0 1970 sys\r\ndrwxr-xr-x\u00c2\u00a0 2 root root 4.0K Jun\u00c2\u00a0 2 10:25 mnt\r\n... etc. ...<\/pre>\n<\/blockquote>\n<p>Note that the &#8220;Jan 1 1970&#8221; comes from boot time, when the Pi doesn&#8217;t know what time it is (no real time clock), so it defaults to the earliest time a Unix timestamp can have.<\/p>\n<p>It would be pretty unreasonable to expect everyone to remember what all the options are, so most commands have help built in, accessible by using either &#8220;-h&#8221; or &#8220;&#8211;help&#8221; (that&#8217;s two dashes there, compared to the one for single letter options). \u00c2\u00a0With ls, &#8220;-h&#8221; is used for specifying human-readable units, so &#8211;help (with the two dashes) is the option to use for help.<\/p>\n<blockquote>\n<pre>naich@raspberrypi ~ $ ls --help\r\nUsage: ls [OPTION]... [FILE]...\r\nList information about the FILEs (the current directory by default).\r\nSort entries alphabetically if none of -cftuvSUX nor --sort is specified.\r\n\r\nMandatory arguments to long options are mandatory for short options too.\r\n\u00c2\u00a0 -a, --all\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 do not ignore entries starting with .\r\n... blah blah etc. ...<\/pre>\n<\/blockquote>\n<p>Options with two dashes and a word are called &#8220;long options&#8221;, one dash, one letter ones are &#8220;short&#8221; options.\u00c2\u00a0 Obviously you can&#8217;t lump long options together behind the same dashes, so you have to use them seperately, i.e. <strong><tt>ls --all --human-readable \/<\/tt><\/strong>.\u00c2\u00a0 You can also mix them if you want, i.e. <strong><tt>ls -la --human-readable \/<\/tt><\/strong>.<\/p>\n<p>A huge amount of help is also available from the manual pages residing on your Pi, which contain more verbose instructions.\u00c2\u00a0 You use these by typing &#8220;man command&#8221;, e.g. <strong><tt>man ls<\/tt><\/strong> or <strong><tt>man adduser<\/tt><\/strong> or even <strong><tt>man man<\/tt><\/strong>.\u00c2\u00a0 While they are very detailed and available for pretty much every command you&#8217;ll use, a) you need to already know what command you want, and b) they aren&#8217;t always written in the clearest manner for a beginner.\u00c2\u00a0 Don&#8217;t be afraid to google for information too &#8211; for example, putting &#8220;how do i add a user in linux&#8221; into google&#8217;s search box gives you exactly what you need to know.\u00c2\u00a0 You aren&#8217;t born with knowledge of how Linux works so you need to find it somewhere.\u00c2\u00a0 Start off with the manual pages but if you only understand a few of the words on them, have a google for it.<\/p>\n<p><a href=\"http:\/\/naich.net\/wordpress\/?p=526\">Go back<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>These are appendixes from the set of posts about setting up and using a Raspberry Pi. Appendix A: Selecting an IP Address As part of the boot process, your Pi used DHCP to get an IP address from the router. The problem with this is that it is an automated process which is invisible to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"aside","meta":{"footnotes":""},"categories":[74,102],"tags":[],"class_list":["post-501","post","type-post","status-publish","format-aside","hentry","category-geek","category-raspberry-pi","post_format-post-format-aside"],"_links":{"self":[{"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/comments?post=501"}],"version-history":[{"count":34,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/501\/revisions"}],"predecessor-version":[{"id":669,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/501\/revisions\/669"}],"wp:attachment":[{"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/media?parent=501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/categories?post=501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/naich.net\/wordpress\/index.php\/wp-json\/wp\/v2\/tags?post=501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}