\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Cloud-based Architecture of Raspberry Pi: Personal Cloud Storage},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2019 2019-01-15 (revised: 4 Year 2019 15 January 2019)}
\def\TheID{\makeatother }
\def\TheDate{2019 2019-01-15}
\title{Cloud-based Architecture of Raspberry Pi: Personal Cloud Storage}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Faisal  Khalil-Ur-Rehman}

             \affil[1]{  Limkokwing Universty of Creative Technology Malayisa}

\renewcommand\Authands{ and }

\date{\small \em Received: 11 December 2018 Accepted: 1 January 2019 Published: 15 January 2019}

\maketitle


\begin{abstract}
        


The research explained the reason why we need personal cloud storage. This research will show steps on how to build a personal cloud storage by using credit card size Raspberry Pi (minicomputer), which will help the user to enable cloud storage mode to their external hard drive. However, other cloud storage services like Dropbox, Google Drive, and iCloud gives limited amount of storage. This research will help the users to use (1TB) or above size external hard drive to be use and have access anywhere from any device over internet. Also the second part of this research focus on replace the laptops to raspberry pi that lecturers use in the classroom to play PowerPoint slides, and videos at university. Universities use laptops to plug and play their educational slides and videos. All these laptops price and maintenance cost lot to the university, if we look deeply just for play slides we do not have to buy a laptop which cost $300 and also the lecturer have to carry the laptops all the times from the faculty to classes, moreover most of the times the laptops are not available. Overcome above statement, all the laptops can be replaced to ?Raspberry Pi? which cost $35 and it does not need any maintenance.

\end{abstract}


\keywords{raspberry Pi, cloud storage, cost benefit-analysis, low cost-computing, university classrooms.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{I. Introduction}]{I. Introduction}\par
he aim of this research is to develop a cloud computing project, where the users can use their external hard drive's connected to Raspberry Pi through internet they can have access to anywhere from any device. According to  {\ref (Jon Brodkin, 2008)} Even though Security, Privacy and Trust issues exists since the evolution of Internet, the reason why they are widely spoken these days is because of the Cloud Computing scenario. Any client/small organization/enterprise that processes data in the cloud is subjected to an inherent level of risk because outsourced services bypass the "physical, logical and personnel controls" of the user.\par
To develop a cloud computing project where users can have large amount of storage with the help of Raspberry Pi. Most of the user have external hard drive 1 TB (Terabyte) or more but the users cannot carry the external hard drives all the time, whereby this project will benefit the users connect to personal cloud storage over internet. The new technology which will be affordable to everyone and also it will enable the user to use their external hard drives over internet possible.\par
Author ?: Postgraduate Centre, Limkokwing University of Creative Technology, Malaysia. e-mail: faisal.albalushi22@gmail.com Laptops that the lecturers are using for slides provided by Limkokwing University are limited in quantity and most of them are not working (requires maintenance). Replace all the laptops with the Raspberry Pi, which only cost \$35 and does not require maintenance (low maintenance). The laptop cost is above \$300 and need maintenance but the Raspberry Pi cost is \$35 and does not need any maintenance. Raspberry Pi will reduce the cost and effort for lecturers, also it is easy to carry.\par
Most of the cloud computing services are providing limited storage to the users, at the same time the risk of your data to store at third party is a big issue. Example is the recent incident of exposed nude pictures of the celebrities from iCloud. Which is a clear example that our data is not safe, to overcome these problems this research will come up with the perfect solution with unlimited cloud data storage by the help of "Raspberry Pi".\par
Rather than store all our media and files on a cloud server in an unknown location, we can keep a cloud at our home and make it personal.\par
The objectives for this research are ? The primary object of this research is to develop a cloud storage, whereby all the users can connect their external hard drives to raspberry pi and have access everywhere over internet. ? To develop a raspberry pi which can connect to projector and run the slides, videos and also web browsing as well. ? To save the cost for the university by replacing the laptops to raspberry pi, whereby the university can save money and maintenance time as well. Also it will be easy for the lecturers to carry the raspberry pi to classes rather than laptops. The university can save roughly up to RM 200, 000. ? To compare the current cloud computing to the Pi cloud computing. In term of storage because all the cloud computing services provide only limited number of storage to the users or the users have to buy extra storage if they require more space. ? To help the lecturers retrieve files (chapter's slides) from Pi cloud in the classroom. By using raspberry pi in the classrooms will represent the student's creativity and the education level at Limkokwing University.\par
T 
\section[{II. Literature Review}]{II. Literature Review}\par
According to William (2014), in order to do effective way of computation, Cloud Computing offers IaaS, PaaS and SaaS levels of service models. The lowest service model is called Infrastructure as a Service (IaaS), which follows by Platform as a Service (PaaS) and last, but not least Software as a Service (SaaS). Each service model helps to add more functionality and abstraction to the technical details. The National Institutes of Standards and Technology (NIST) definition runs to several hundred words but essentially says that:\par
"Cloud Computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned" and released with minimal management effort or service provider interaction." \hyperref[b3]{Armbrust (2009)} defined clouds as computers are being able to network anywhere in the world by perper-use way to pay for used clouds, the actual meaning of this idea is that the resources that are being used will be paid only. Below will be introduces types of clouds. The first one is the Public Clouds. \hyperref[b3]{Armbrust (2009)} mentioned that public cloud is the traditional cloud computing that will have the opportunity to access to the computing resources from anywhere of the world. The pay-per-use manner will be used in clouds, as defined the only resources that are being used will be paid by transaction fees. On a superficial level, my findings may seem self-evident: a technology company tells its users what it expects of them and users for the most part agree, so long as the technology holds up. However, if we dig deeper, we can extract some important implications from this research. Following the work of other scholars who look at trust in information and communications technologies, I believe that trust is a more useful concept for studying the implications of new technologies than simply looking at privacy. 
\section[{a) Cloud Computing Deployment Models}]{a) Cloud Computing Deployment Models}\par
There are four deployment models for cloud computing, depending on the owners requirement, the security issues starts from here. Public cloud computing is based on large-scale offering to general public, the infrastructure is located at premises of provider. The provider owns and manages the cloud infrastructure. 
\section[{ii. The Private Cloud}]{ii. The Private Cloud}\par
In this case the infrastructure is provisioned for exclusive use by a single organization. It can be owned, managed, and operated by the organization themselves, a supplier as a third party, or some combination of them. Additionally it can exist on or off premises of the organization (Mell/Grance, 2011). Therefore special forms, can be also considered as a private Clouds. These are listed by some researchers as e.g. virtual private Clouds (e.g. Ried et al. 2011), where the cloud is hosted on dedicated, virtual machines in the data center of the Cloud provider, as well as managed private clouds, where the cloud is hosted by a third party in the data center of the customer.\par
However, what makes this analysis different than other literature on trust -and what this project is ultimately about on a theoretical level is the nexus of technology, objectivity and trust. A word about each and how they relate is necessary. My analysis and understanding of technology rests on many of the assumptions of actor-network theory, and particularly Bruno Latour's (1991) quip: "Technology is society made durable." I have extensively used the metaphor of the black box to exemplify this principle and stay faithful to the central tenets of Raspberry Pi Cloud Storage. The black box represents a network of associated humans and non-humans that has stabilized such that its heterogeneity is reduced and it appears as a homogenous whole. Its associations (i.e., its social relations) are hidden and become a durable technological entity. Users of this black boxed technology must not understand, follow or even be aware of the internal workings and associations but only need to understand how to use the black box as a whole; they only need to follow the user scripts and interact with the technology's user interface. 
\section[{III. Methodology}]{III. Methodology}\par
Maxwell (2012) has stated that 'the strengths of qualitative research derive primarily from its inductive approach'. The reason why the inductive approach was used in this research due to the newness of the idea to create your own cloud with Raspberry Pi. A deductive 'approach to this subject would risk restricting the potential avenues of investigation. The inductive approach necessitated attempting to understand the meaning and the context of people's responses to the adoption of Cloud Computing. It attempted to uncover unforeseen trends and detect linkages between Cloud Computing and Raspberry Pi. 
\section[{a) Data Collection}]{a) Data Collection}\par
The focus is on using qualitative data collection techniques. Qualitative data is data that is focusing on delivering information that can be described with terms and theories. It is not like quantitative research that focuses on the numbers behind a survey or something similar. It focuses on delivering numbers and information in terms of quantity. Qualitative research can be interviews or observations where the research is done on the behaviour or theories  {\ref (Saunders et.al.2010)}.\par
Our research will consist of both primary and secondary data. Primary data is data collected by the researcher using different methods. The primary data that is collected are often more reliable due to that you know where the data comes from and been following the progression all the way. Primary data sources could be (Kelly 2010): ? Observation when observing a system or a research object to see the details that is important to a research. Requires a lot of resources and time.\par
Secondary data are data that is collected from external sources that already exist. The only thing that has to be done is to look for the data you need. Secondary data has the upside compared to primary that it is cheaper to collect but the reliability, validity and accuracy is not as great. You do not know where the data actually comes from and cannot fully trust is against primary data where you have more control.\par
Secondary data is easier to obtain and cheaper to get also. Some examples of secondary data (Kelly 2010): 
\section[{? Magazines, Newspapers and Reviews ? Research articles}]{? Magazines, Newspapers and Reviews ? Research articles}\par
There is a third data source called tertiary data that is the search tools for obtaining secondary and primary data such as encyclopaedias and indexes. Often it is used in literature search when not knowing where to start searching for a specific topic  {\ref (Saunders et.al. 2012)}. Our primary data collection will consist observation in different forms and the secondary data collection will be recent articles in the area of cloud computing and raspberry Pi, internet sources and literature that is within our field of research.  
\section[{IV. Results}]{IV. Results}\par
Cloud computing is defined by the United States National Institute of Standards and Technology (NIST) as: "A model for enabling convenient, ondemand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction." (National Institute of Standards and Technology 2011).\par
In a similar vein, Mather, Kumaraswamy and Latif (2009) add that there are five common attributes of all cloud computing services: shared resources, massive scalability, elasticity, pay as you go and the self-provisioning of resources. While these definitions are technical and bureaucratic, they do provide some starting points to discuss what cloud computing is and how it can be analyzed sociologically. In simpler terms, cloud computing broadly refers to computing services, software and platforms that are not owned individually by users and installed locally on their personal computer, but rather accessed via an Internet connection.\par
From these characteristics of cloud computing, two ideas are of sociological significance. First, the idea of "convenient, on-demand" (National Institute of Standards and Technology 2011) services fits into the idea of what some authors have called a 'convenience culture.' For example, Tierney (1993) argues that one of the defining features of modernity is the consumption of 'conveniences.' He defines convenience as an "ability to mitigate the effects of bodily limits"; for something to be convenient it must make easy and simple an action that was previously difficult, impossible or troublesome.  
\section[{Primary Secondary Tertiary}]{Primary Secondary Tertiary} 
\section[{Reports}]{Reports} 
\section[{Setup admin account}]{Setup admin account}\par
While setting up the admin account you should provide the path to your data folder. You can ideally set this to your NAS drive or external drive, which you may have mounted. Owncloud will complain and not proceed with admin account if the data directory path is not readable \& writable by the user www-data. Also it should not be readable by "others". 
\section[{b) Setup Mount / Auto Mount USB Hard Drive on Raspberry Pi}]{b) Setup Mount / Auto Mount USB Hard Drive on Raspberry Pi}\par
Follow the simple steps in the order mentioned below to have your USB drive mounted on your Raspberry Pi every time you boot it.\par
These steps are required especially if you are setting up a Samba share, or a 24x7 torrent downloader, or alike where your Raspberry Pi must have your external storage already mounted and ready for access by the services / daemons.\par
Step 0. Plug in your USB HDD / Drive to Raspberry Pi If you are using a NTFS formatted drive, install the following sudo apt-get install ntfs-3g\par
Step 1. Log on pi using ssh terminal and execute: ls -l /dev/disk/by-uuid/ You will see something like the following: lrwxrwxrwx 1 root root 10 Jan 1 1970 0AC4D607C4D5F543 -> ../../sda1\par
Note down the value of the UUID --> 0AC4D607C4D5F543\par
Step 2. Create a location for mount point: sudomkdir /media/NASDRIVE Give proper permission: sudochmod 770 /media/NASDRIVE Step 3.\par
Get the uid, gid for pi user and group with id command (usually 1000)\par
Step 4.\par
Mount the USB Drive and then check if it is accessible at /media/NASDRIVE sudo mount -t ntfs-3g -o uid=1000, gid=1000, umask=007/dev/sda1 /media/NASDRIVE Step 5. Now, we will configure RasPi to do this after every reboot: Take a backup of current fstab and then edit sudocp /etc/fstab /etc/fstab.backup sudonano /etc/fstab Add the mount information in the fstab file (replace UUID with your own): UUID=0AC4D607C4D5F543 /media/NASDRIVE ntfs-3g uid=1000, gid=1000, umask=007 0 0\par
Step 6. 
\section[{Reboot sudo reboot}]{Reboot sudo reboot}\par
Step 8. (Optional, required if using as data storage for Owncloud)\par
If you are configuring ownCloud's data directory on your NAS drive, it should be having a 770 permission for www-data user. You can simply add user www-data to pi group, since it's already having 770 as permission as set above in fstab. sudousermod -a -G pi www-data.\par
In studies of black boxed technologies, objectivity is always implicit but rarely explicitly discussed. Part of this is likely due to the self-evidence of the objectivity of black boxed technologies. Technological entities are objective in multiple senses of the word: one, they are objects; and two, they behave consistently. Users of a black boxed technology who behave in accordance with the user scripts should expect the technology to behave the same way every time. Its internal workings and associations are reduced such that users provide an input and expect consistent outputs from the black box. The objectivity of technologies is, in this sense, very self-explanatory. Nevertheless, using the metaphor of the black box highlights a key point about the nexus between objectivity and technology: objectivity is an effect of a network or association's durability and stabilization. It is precisely when a network becomes black boxed that it becomes seen as objective. It is when those contingent associations and subjective actors are reduced (in other words, when the social has been reduced) that a technology that behaves consistently and objectively appears. 
\section[{V. Conclusion}]{V. Conclusion}\par
What are some repercussions of this analysis of Raspberry Pi ownCloud storage, users, cloud computing, and data privacy? OpenSSH is an application that allows you to securely access Linux systems remotely over the network. You can use OpenSSH simply for secure file sharing. But it also allows you to log on to a system and control it over the network, even using the GUI, just as if you were sat in front of it. The default installation of Linux on your Raspberry Pi should have "SSH daemon" running. This means that your Raspberry Pi is listening on port 22 for a remote computer asking to make a connection to it. In your case, this will probably mean your normal desktop or laptop computer.\par
In Chapter Two, I found that there is a dearth of existing literature on Raspberry Pi personal cloud storage and data privacy that examines the role of user agency and that trust is one conceptual tool to avoid this problem. In Chapter Three, I outlined how using principles from Raspberry Pi and bring it in a shape to personal cloud storage, theory one could study trust and reimagine the role of user agency in discussing cloud computing. In particular, I outlined the methodological principles of Akrich's (1992; Akrich and Latour 1992) user scripts and description and the principle of co-production to look at how users and technologies are mutually working on each other. In applying these principles to my case study in Chapters Four and Five, I found that Raspberry Pi personal cloud storage, prescribed trust and privacy protection on its users, while maintaining security as its domain. Users, for the most part, accepted this script; however, some varying levels of trust were observed in users. What was noteworthy about the analysis in Chapter Five, however, was how in instances of breakdown, these user scripts and trust fall to pieces. This has led me to the conclusion that only when trust is shattered does privacy and the trade-off of personal privacy for use become contested and negotiable.\par
My example of cloud computing, and more specifically Raspberry Pi cloud storage, can highlight this principle. As discussed in the introduction, cloud computing is a great example of a heterogeneous assemblage. It is not a simple technological artefact but is rather an idea that encompasses a wide range of computing programs, hardware and human actors in order to be realized. Through my analysis of users of Raspberry Pi cloud storage, I have found that many of these users simply accept the user scripts of this program; they interact with Raspberry Pi cloud storage as a black boxed technology. They do not need to question or understand how Raspberry Pi cloud storage. Or how cloud computing more generally functions, they just need to know how to interact with Raspberry Pi cloud storage's user interface. To them, Raspberry Pi cloud storage is a program to store and synchronize files to be accessed at a later date, not a heterogeneous network of associated human and non-human actants.\par
When exploring technology and objectivity in this way, it is possible to conceptualize the understanding of trust I have put forth in this analysis. Trust simply becomes a necessary by-product of the stabilization and reduction of heterogeneous associations, and the perceived objectivity of a technological entity. Technologies, here understood as stabilized networks, objectivity and trust all necessitate one another. Black boxed technologies are trusted to behave as expected, to behave objectively. If there is distrust in the technology, it is not perceived as completely objective; there is room for error. If the heterogeneity of a network is not completely reduced, there is more room for distrust as users must now trust each of the heterogeneous associations and not simply the homogenous black boxed technology. Thus, technology, objectivity and trust go hand in hand; they all appear simultaneously as a heterogeneous network is reduced, stabilized and made durable. My findings, in Chapter Four and particularly Chapter Five thus suggest that Raspberry Pi cloud storage as a case study of cloud computing is not a completely stabilized technology, though it is well on its way. It is stable enough that users for the most part trust the technology and behave in accordance with its user scripts. However, there is still a concerted effort on the part of Raspberry Pi cloud storage to communicate its objectivity and trustworthiness and to further reduce its heterogeneity and the marginality of some users.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 3 :}\end{figure}
   		 		\backmatter   			 
\subsection[{Acknowledgement}]{Acknowledgement}\par
The author would like to thank Mohammed Mahmud for his technical support of the cloud. This work is supported by FICT, Limkokwing University. 			  			  				\begin{bibitemlist}{1}
\bibitem[Tabona (2013)]{b2}\label{b2} 	 		\textit{-freenetwork-monitoring-and-analysis-tools-for-sysadmins/. Last accessed 2nd},  		 			Andrew Tabona 		.  		 \url{http://www.gfi.com/blog/the-top-20}  		2013. November 2014.  	 	 (The Top 20 Free Network Monitoring and Analysis Tools for Sys Admins) 
\bibitem[
			Bessie
		 (2012)]{b4}\label{b4} 	 		\textit{-Ouya-vs-Raspberry-Pi},  		 			Bessie 		.  		 \url{http://ouyaforum.com/showthread.php?755}  		December 2012. October 2014.  	 	 (Ouya vs Raspberry Pi) 
\bibitem[Armbrust et al. ()]{b3}\label{b3} 	 		\textit{Above the Clouds: A Berkeley View of Cloud Computing},  		 			M Armbrust 		,  		 			A Fox 		,  		 			R Griffith 		,  		 			A Joseph 		,  		 			R Katz 		,  		 			A Konwinski 		,  		 			G Lee 		,  		 			D Patterson 		,  		 			A Rabkin 		,  		 			I Stoica 		,  		 			M Zaharia 		.  		2009.  		 			University of California at Berkeley 		 	 	 (Technical Report) 
\bibitem[Aderemi et al. (2011)]{b1}\label{b1} 	 		 			A Aderemi 		,  		 			* Atayero 		,  		 			* * Oluwaseyi Feyisetan 		.  		\textit{Journal of Emerging Trends in Computing and Information Sciences. Security Issues in Cloud Computing: The Potentials of Homomorphic Encryption},  				October 2011. 2 p. .  	 
\bibitem[
			Abraham
		 ()]{b0}\label{b0} 	 		‘Autonomic Clouds on the Grid’.  		 			Abraham 		.  	 	 		\textit{Journal of Grid Computing}  		2009. p. .  	 
\bibitem[Cisco ()]{b7}\label{b7} 	 		 			Cisco 		.  		 \url{http://www.packettracernetwork.com/.Lastaccessed}  		\textit{Cisco Packet Tracer},  				2013. 2018th November 2014.  	 
\bibitem[Foster et al. ()]{b11}\label{b11} 	 		\textit{Cloud Computing and Grid Computing 360-Degree Compared},  		 			I Foster 		,  		 			Y Zhao 		,  		 			I Raicu 		,  		 			S Lu 		.  		2008. p. .  		 			University of Chicago 		 	 
\bibitem[Christodorescu et al. ()]{b6}\label{b6} 	 		‘Cloud security is not (just) virtualization security’.  		 			M Christodorescu 		,  		 			R Sailer 		,  		 			D L Schales 		,  		 			D Sgandurra 		,  		 			D Zamboni 		.  	 	 		\textit{Proceedings of the ACM Cloud Computing Security Workshop (CCSW)},  				 (the ACM Cloud Computing Security Workshop (CCSW))  		2009. p. .  	 
\bibitem[Current status and the future direction of IPv6 in Japan (2018)]{b13}\label{b13} 	 		\textit{Current status and the future direction of IPv6 in Japan},  		 15. jaipa.or.jp. 2011.  		 \url{http://www.jaipa.or.jp/ipv6day/data/111121\textunderscore iaetf.pdf}  		April 2018. p. 9.  	 
\bibitem[Marianthi ()]{b17}\label{b17} 	 		‘Data protection jurisdiction and cloud computing when cloud users and providers subject to eu data protection law are? the cloud of unknowing, Part 3’.  		 			Marianthi 		.  		 \url{http://meetings.apnic.net/\textunderscore \textunderscore data/assets/pdf\textunderscore file/0003/44976/ipv6\textunderscore deployment.pdf}  	 	 		\textit{International Review of Law, Computers \& Technology}  		2013. 2012 20. April 2018. 26 p. 9.  	 	 (Meetings.apnic.net. 2012.) 	 (IPV6 deployement of KDDI) 
\bibitem[Hilton (2013)]{b14}\label{b14} 	 		\textit{Designing and Building the Best Small Office Network From the Ground Up},  		 			James Hilton 		.  		 \url{http://www.networkcomputing.com/netdesign/soho1.html.Lastaccessed}  		June, 2013. 2018th November 2014.  	 
\bibitem[Oven ()]{b10}\label{b10} 	 		\textit{Ethernet Tutorial -Part I: Networking Basics},  		 			David Oven 		.  		 \url{http://www.lantronix.com/resources/net-tutor-etntba.html.Lastaccessed}  		2013. 2018th November 2014.  	 
\bibitem[Lantronix ()]{b16}\label{b16} 	 		\textit{Networking Tutorials},  		 			Lantronix 		.  		 \url{http://www.lantronix.com/resources/networking.html.Lastaccessed}  		2014. 2018th November 2014.  	 
\bibitem[Boniface et al. ()]{b5}\label{b5} 	 		\textit{Platform-as-a-Service Architecture for Real-time Quality of Service Management in Clouds},  		 			M Boniface 		,  		 			B Nasser 		,  		 			J Papay 		,  		 			S Phillips 		,  		 			A Servin 		,  		 			X Yang 		.  		2009.  	 
\bibitem[Ico (2013)]{b12}\label{b12} 	 		\textit{Privacy impact assessment handbook},  		 			Ico 		.  		2013. Jul.  	 	 (v2.0, Information Commissioner's Office, UK. [Online]. Available: http) 
\bibitem[Cn Vr (2014)]{b9}\label{b9} 	 		‘The Raspberry Pi B’.  		 			Cn Vr 		.  		 \url{http://www.ebay.com/itm/CN-Ver-}  	 	 		\textit{Raspberry-Pi-2-0-Model-B-512MB-ARM11-Linux-System-Development-Board-Kit-/261189408347. Last accessed 11},  				17 September 2014. October 2014.  	 
\bibitem[Top Threat to Cloud Computing V1.0 (2010)]{b8}\label{b8} 	 		\textit{Top Threat to Cloud Computing V1.0},  		 \url{https://cloudsecurityalliance.org/topthreats/csathreats.v1.0.pdf}  		March 2010.  		 			Cloud Security Alliance 		 	 
\bibitem[Jackson ()]{b15}\label{b15} 	 		\textit{What is a Computer Network},  		 			Jhony Jackson 		.  		 \url{http://www.e-tutes.com/.Lastaccessed}  		2012. 2018th November 2014.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
