<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Stuart on Medium]]></title>
        <description><![CDATA[Stories by Stuart on Medium]]></description>
        <link>https://medium.com/@Mr_Kaides?source=rss-65474a282d0b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fllyZJm2-2fQ_kBz.png</url>
            <title>Stories by Stuart on Medium</title>
            <link>https://medium.com/@Mr_Kaides?source=rss-65474a282d0b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:23:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Mr_Kaides/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[C static libraries]]></title>
            <link>https://medium.com/@Mr_Kaides/c-static-libraries-eb46a0c1b7d2?source=rss-65474a282d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb46a0c1b7d2</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cisfun]]></category>
            <dc:creator><![CDATA[Stuart]]></dc:creator>
            <pubDate>Mon, 07 Nov 2016 02:46:25 GMT</pubDate>
            <atom:updated>2016-11-07T02:46:25.422Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*o4GeueAUO9evOx9p_ij_rw.jpeg" /></figure><h3>What is it?</h3><p>A static library is a list of functions/programs that you can call upon in other programs. The file is made from the object files of the various programs you wish to include. Since the object files are conveniently stored in one place (the library), your computer does not have to search the entire disk to find your function during the linking phase.</p><h3>How to make one.</h3><p>Since a library is also an archive file, you can use the archiving tool (ar-command) to make one. First, however, you will need the object file of your programs. To do this you can use “gcc -c filename.c” to tell gcc to compile your .c file, but it will stop when it reaches the object file. This will create a file name “filename.o”. You can do multiple files at once by adding the file names onto the command. Example: gcc -c file.c file2.c file3.c. Which will give you 3 object files.</p><p>From here you will want to use the “ar” command with the “r” and “c” options. “r” will tell it to replace the library if their is an older version, and “c” will create a new one if one does not already exist. After the “r” and “c” flags, add the library name followed by all of the object files you wish to include. The format will look like this: “ar rc libraryname.a objectfile1.o objectfile2.o”. You can check the contents of your library with the “ar -t libraryname.a” command.</p><p>If all is well, you will want to index it by using “ranlib libraryname.a”. The index is used by the compiler to speed up symbol-lookup and to make sure the order does not matter for the symbols. Now you are all ready to use your new library. Just make sure to link it when compiling your next program by tagging a “-L library.a” at the end of your gcc command. Example: “gcc prog-name.c -L lib-name.a” .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb46a0c1b7d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when you type gcc main.c]]></title>
            <link>https://medium.com/@Mr_Kaides/what-happens-when-you-type-gcc-main-c-2b9b72510626?source=rss-65474a282d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9b72510626</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[holberton-school]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Stuart]]></dc:creator>
            <pubDate>Thu, 13 Oct 2016 06:12:33 GMT</pubDate>
            <atom:updated>2016-10-13T06:12:33.305Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/236/1*CoaVTi0BtFbzLbSWckc4Ww.jpeg" /></figure><p>GCC is GNU’s C Compiler and the program you would use to turn your C source code into a working executable.</p><p>When you type <em>“</em><strong><em>gcc main.c</em></strong><em>”</em>, your shell will first search check and see if gcc is an alias, if not it will check see if it is a built in and than if it is a program. Once your shell finds the location of gcc it will look for “main.c” in the current directory and run it through the following steps:</p><p>Step 1: Pre-processor<br>GCC takes your .c source code and runs it though the pre-processor.<br>The pre-processor will remove any comments made within the source file. It will than add any header file code listed into the file. An example of this would be #include &lt;stdio.h&gt; or &lt;string.h&gt; etc. The last step of the pre-processor is to replace any macros with code. After all this is done it will out an intermediary file “filename.i”</p><p>Step 2: Compiler<br>That .i file is than taken and run through the compiler to translate it into assembly code. Your hardware is still not able to read this fully yet. Files will end in “.s”.</p><p>step 3: Assembler<br>The assembler takes output of the compiler (assembly code) and turns it into object code. Object code is your binary zeros and ones, which your hardware can understand.files end in “.o”</p><p>step 4: Linker<br>Finally linker will take any other object files needed for the program and add them. Linker will also take your finished object code and link it to any necessary libraries. The output will be your final executable file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*A9R7clK3lw3R_lp1uZYbdA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9b72510626" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the difference between a hard link and a symbolic link?]]></title>
            <link>https://medium.com/@Mr_Kaides/what-is-the-difference-between-a-hard-link-and-a-symbolic-link-d8277523f855?source=rss-65474a282d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8277523f855</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[holberton-school]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Stuart]]></dc:creator>
            <pubDate>Tue, 11 Oct 2016 01:19:54 GMT</pubDate>
            <atom:updated>2016-10-11T01:19:54.354Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*u7HhTpzlyUlcK_fNPwKVqQ.jpeg" /><figcaption>my-soft-link is the symbolic link in this instance.</figcaption></figure><p>A hard-link points to the files inode location. If you change the file or update the file, the hard-link will still point to the old inode location. A symbolic link points to the files name/location. If you change the file’s name or location, it will break the link. If you update the file, however, the symbolic link will still take you to the updated file. Hard-links can only exist within an environment, while symbolic links can span file-systems.</p><p>To make a hard link: ln [target] [location] <br>Example: ln testFile testFile-hardlink</p><p>To make a symbolic link: ln -s [target] [location]<br>Example: ln -s testFile2 testFile2-symlink</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8277523f855" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when you type `ls *.c]]></title>
            <link>https://medium.com/@Mr_Kaides/what-happens-when-you-type-ls-c-31f7324016b9?source=rss-65474a282d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/31f7324016b9</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[holberton-school]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Stuart]]></dc:creator>
            <pubDate>Mon, 10 Oct 2016 21:43:46 GMT</pubDate>
            <atom:updated>2016-10-10T21:43:46.028Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*uDZNJTk132OMMnzX9w4Owg.png" /><figcaption>Example of <strong>ls *.c</strong> command being used with several directories and files ending in<strong> .c</strong></figcaption></figure><p>The command <em>“</em><strong><em>ls *.c</em></strong><em>”</em> in a nutshell will list any file ending in <em>“</em><strong><em>.c</em></strong><em>”</em> that is in the current directory AND it will list the contents of any directory ending in “<strong><em>.c</em></strong><em>”</em>. Since the command is not recursive, meaning it will continue to follow every folder or directory down the chain until it ends, it will not list the contents of any further sub-directories.</p><p>Let’s now break the command step by step and piece by piece. The <em>ls </em>command will list the contents of the current directory. The symbol <strong><em>*</em></strong> is a wildcard looking for anything, and since <em>“</em><strong><em>.c</em></strong><em>”</em> is after anything <strong><em>*</em></strong> we are looking for any file ending with <em>“</em><strong><em>.c</em></strong><em>”</em>. So on the first pass, the command lists any files ending in .c in the currently directory, and after that it will list <strong>all </strong>the<strong> </strong>contents of any directory ending in <em>“</em><strong><em>.c</em></strong><em>”</em>, including files that do not end in <em>“</em><strong><em>.c</em></strong><em>”</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31f7324016b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I want to attend Holberton School,]]></title>
            <link>https://medium.com/@Mr_Kaides/why-i-want-to-attend-holberton-school-5194da341b8c?source=rss-65474a282d0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5194da341b8c</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[holberton-school]]></category>
            <dc:creator><![CDATA[Stuart]]></dc:creator>
            <pubDate>Wed, 09 Dec 2015 06:54:33 GMT</pubDate>
            <atom:updated>2015-12-09T06:54:33.011Z</atom:updated>
            <content:encoded><![CDATA[<p>Why I want to attend Holberton School,</p><p>From an early age I have fond memories of computers. My first experience was using the command prompt on MS Dos to boot into my favorite games such as Doom, Blake stone, Quest for Glory, and Zone 66. My dad had to set up short cuts as I would pester him continuously if I could not navigate to the newest game — I was 4 or 5 at the time. It would not be until years later when I migrated into the Linux community that I would start using and writing scripts to automate long and arduous tasks.</p><p>Going into college right out of high school was a difficult time for me. During my freshman year of high school I suffered an acute subdural hematoma. While I was able to get through high school on what I already knew, my head injury deeply affected my short term memory which took most of high school to relearn. Entering into college was another story. I was not able to figure out what I wanted to do, dropping in and out of college for a number of years. Eventually I ended up working and teaching myself Linux and programming, as this stimulated my mind in overcoming my injuries. This included basic Linux system administration, networking, server setup, and other related skills that I needed to know at the time; “Necessity is the mother of all invention,” after all.</p><p>I currently use Linux Academy, iRC channels, various books, and of course the man pages to further my knowledge. The most important thing I have learned is how to read the fine manual, one of Linux’s core teachings, as this teaches you how to learn on your own. I enjoy programming because it challenges my current way of thinking and builds new neural pathways. This is much like learning a new language or relearning the same language as I had to do in school.</p><p>Over time I have come to realize that while it is a great skill to learn on your own, it would be highly beneficial to seek assistance from someone who understands different styles of learning instead of your classic “one size fits most” institution. This is when I discovered the Holberton School. Reading about the amazing women who were thrust into the monumental task of programming a computer without prior knowledge or direction, gives me inspiration to become an even greater success. I hope to one day give back to the open source community with the knowledge that Holberton school can provide.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5194da341b8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>