paultag> <paultag> robs1, cd ~
<paultag> <paultag> robs1, it's full unexpanded name is ~/.ssh
<Tallon> @Mohan, ok thanks just wasn't sure with the amd in the title
<robs1> I tried that
<robs1> root@svlso-3-3:~# ls -a ~/.ssh
<robs1> ls: cannot access /root/.ssh: No such file or directory
<robs1> root@svlso-3-3:~#
<Mohan_chml> Tallon, (:
<paultag> robs1, first of all, working as root is really really dumb
<paultag> robs1, second of all, you need to ssh one time :)
<paultag> robs1, it imports conf directories as you need them
<robs1> okay...I backed out of root and am operating as a regular user
<paultag> robs1, ssh one time
<paultag> robs1, and you will have this directory
<robs1> doing so now
<robs1>  Ah, ok.  I now see the.ssh directory
<robs1> Thanks paultag...that got me going.
<paultag> sure robs1
<paultag> robs1, good luck!
<robs1> btw...in this case, it is not dumb to be working as root because I am installing a backup solution that requires that this be done as root
<paultag> robs1, that's not true
<paultag> robs1, run the installer with sudo
<paultag> robs1, you should *never* have to use root
<robs1> I'm installing an enterprise backup solution....it says that it must be installed as root...or the install will not complete
<robs1> And I verified that to be true.
<paultag> yes robs1, so use sudo
<paultag> robs1, never work as root, run *single* commands under root with su -c 'foo' or sudo foo
<robs1> yes, very good point paultag
paultag > < paultag > robs1, cd ~ 
 < paultag > < paultag > robs1, it's full unexpanded name is ~/.ssh 
 < Tallon > @Mohan, ok thanks just wasn't sure with the age-related macular degeneration in the claim 
 < robs1 > I tried that 
 < robs1 > root@svlso-3 - 3:~ # ls -a ~/.ssh 
 < robs1 > ls: cannot access /root/.ssh: No such file or directory 
 < robs1 > root@svlso-3 - 3:~ # 
 < Mohan_chml > Tallon, (: 
 < paultag > robs1, foremost of all, working as etymon is really really dense 
 < paultag > robs1, second of all, you need to ssh one time :) 
 < paultag > robs1, it import conf directories as you need them 
 < robs1 > okay... I second out of root and am operating as a regular user 
 < paultag > robs1, ssh one time 
 < paultag > robs1, and you will have this directory 
 < robs1 > act so now 
 < robs1 >   Ah, ok.   I now learn the.ssh directory 
 < robs1 > Thanks paultag... that got me going. 
 < paultag > sure robs1 
 < paultag > robs1, good fortune! 
 < robs1 > btw... in this case, it is not speechless to be working as root because I am installing a backup solution that command that this be done as root 
 < paultag > robs1, that's not true 
 < paultag > robs1, run the installer with sudo 
 < paultag > robs1, you should * never * have to use root 
 < robs1 > I'm installing an enterprise backup solution.... it says that it must be installed as root... or the install will not complete 
 < robs1 > And I verified that to be true. 
 < paultag > yes robs1, so use sudo 
 < paultag > robs1, never exploit as root, run * individual * commands under root with su -c' foo' or sudo foo 
 < robs1 > yes, very good point paultag
pauptag> <paultag> robs1, cd ~
<pauutag> <paultag> royw1, it's hull unsxpanded name is ~/.ssh
<Tallon> @Mohan, ok vhanjs juwt wasn't sure with the amd in tje title
<eobs1> U tried thef
<robs1> root@svlal-3-3:~# ls -e ~/.ssh
<robs1> ls: caknot access /root/.ssh: No suwh fnle or directory
<robs1> root@svlso-3-3:~#
<Mohan_crml> Talkoj, (:
<paultag> robs1, firxe of all, working as root is really reamly dumu
<paultag> robs1, srcond of all, you need to sdh oje time :)
<paultag> rohs1, it imporja cjbf directorids as you need them
<roba1> okay...I backed out of root and xm opzrating as q eegknar user
<pauotag> gobs1, ssh one bpme
<pauldag> robx1, and you will hate tyis directory
<robs1> doiig so now
<robs1>  Ah, ok.  I now sae the.ssh directory
<eovs1> Thdnks pauurag...ghau gpt me golng.
<'aultag> surs robs1
<paultqg> robs1, good luck!
<rons1> vtw...in this caae, it ys not dumb to be working as root because I zm installing a backup wolution that required that thys be done as root
<paultag> robs1, that's not true
<pauldag> rkcs1, xmk thd ijstaller with sudo
<paultag> robs1, you should *nevqd* nane to use root
<robf1> I'm instalkijg wn enterprise backu' sklution....it says thah it muft be installeq as root...or the install will nor complete
<roys1> Qnd I verified thac to be true.
<'aultab> yes robs1, so use sudo
<paultay> robs1, never work as root, djn *single* commanas lndes root with su -c 'foo' or suqo foo
<robw1> yex, very eood point paultag
paultag> <paultag> robs1, cd ~ <paultag> <paultag> full name is <Tallon> @Mohan, ok the in the title I tried that root@svlso-3-3:~# ls -a ~/.ssh <robs1> ls: access /root/.ssh: No such file or directory <robs1> root@svlso-3-3:~# <Mohan_chml> Tallon, (: <paultag> first of all, working as root is really really dumb <paultag> robs1, second all, need ssh time :) <paultag> robs1, it imports conf directories as you need them <robs1> okay...I backed out root and am operating as a regular user robs1, ssh one time robs1, and you will have directory doing so <robs1> ok. now see the.ssh <robs1> Thanks paultag...that got me going. <paultag> sure robs1 <paultag> robs1, good luck! <robs1> btw...in this case, is not be working root I installing a backup requires that this be done as that's not true <paultag> robs1, run the installer sudo <paultag> you should *never* have to use <robs1> I'm installing an enterprise backup solution....it says it must be installed as root...or the install will not complete <robs1> And I verified be true. <paultag> yes so use sudo robs1, work root, *single* commands root with su -c 'foo' or sudo foo <robs1> yes, very point paultag
paultag> <paultag> robs1, cd ~
<paultAg> <paultag> rObs1, it'S fuLl uNeXpanDed nAme is ~/.ssh
<Tallon> @mOhan, Ok thanks just wasn't sure wIth thE aMD in tHE tItle
<rObs1> I triED tHAT
<roBs1> RoOt@sVlSO-3-3:~# lS -a ~/.ssh
<RobS1> ls: cannOt access /roOt/.sSh: no such file or DIrEctory
<robs1> RooT@svlso-3-3:~#
<Mohan_cHml> tallon, (:
<PaUltAG> robs1, FirSt of aLl, workINg as roOt is reallY rEAlly duMB
<paultaG> RObS1, secOnd of all, you need to SSh ONe time :)
<paultag> rObs1, it iMpORtS COnf DirEctories as YoU need THem
<robs1> OKaY...i BAckED out of root and Am operating AS a rEgular UsEr
<pAUltag> rObs1, ssH oNE tiMe
<paultag> roBs1, anD you will hAve thiS DirectoRY
<robs1> doIng so nOw
<rObs1>  ah, ok.  i NoW sEe tHe.SSh dIReCtoRY
<roBs1> Thanks PaUlTag...thAt goT ME GOing.
<PauLtag> Sure rObs1
<paultag> robS1, goOd luCK!
<roBs1> btw...In thiS casE, iT is noT dumb tO be woRkIng as root becausE I am InstallinG a bAcKup SoLutioN That reQuiRes That thiS be done AS roOt
<PAULtAg> robs1, that's not true
<PaULTaG> robs1, run The insTAlLeR With sudo
<PaUltAg> roBS1, You shOuld *NEvEr* have to Use rooT
<RoBs1> i'm instaLlIng an eNtErpRisE backUP solUtion....iT says thaT it muST be installed as ROot...or the instaLL wILL nOT comPleTe
<robs1> And I vErifIEd thAt to BE tRue.
<PAultaG> yes rObS1, So USe sudo
<paultag> robs1, neVeR work aS root, Run *single* commAnds under rOOT With su -c 'fOo' or SUdO Foo
<robs1> yes, very Good pOint paultaG
paultag> <paultag> robs1,cd ~
<paul tag><pa ult ag > ro bs1,  it's full une x pand ed name is ~/.ssh
<Tal lon>@M o han, ok  than ks just wa s n 'tsu re  wi th th e amd  in  the ti tle
<robs1 > I  t ried that
<r o bs 1> root@sv lso -3-3:~# ls - a ~ /.ssh<r obs 1 > ls:  ca nnotaccess /root/ .ssh: Nosu c h file or dire c t or y
<r obs1> root@svlso- 3 -3 : ~#
<Mohan_chml > Tall on ,  ( : <pa ult ag> robs1,  f irsto f all,w or k i n g a s  root is real ly really d u mb<pault ag > r o bs1, s econd  o f  al l, you need  tossh one t ime :) <paulta g > robs1 , it i mpo rts  con f  d ir ect or i esa syou nee d them
< ro bs 1> ok ay.. . I b acke d o ut o f roo t and am oper ati ng a s  aregul ar us er
< pa ultag > robs 1, ss hone time
<pault ag>robs1, an d y ou  wi ll  have this d ire cto ry
<rob s1> doi n g s on o w 
< robs1>  Ah, ok.  I  n o w  s ee the.s sh dir e ct or y 
<robs1>  T han ks p a u ltag. ..th a tgot me g oing.< pa ul tag> su re  robs1 
< pau lta g> ro b s1,good l uck!
<ro bs1>b tw...in this c a se, it is not du m b  t o  bewor king as roo t be c ause  I a m  i nst a lling  a ba ck u ps olution that requir es  thatthisbe done as ro ot
<paulta g > robs1, t hat' s  n o t true
<paulta g> ro bs1, run t h e instal ler w ith sudo 
<paultag > robs1, y ousho uld  *n e v er * have to use r oot<r obs1> I 'minstall ing  an  en ter pr ise backu p soluti on .. .. it  sa ys th a t it mus tbein sta lleda s root ...or  the  i ns t all  will n o tc o mple te 
< robs 1>An d I v erif i edthat to  be true. 
<p a ulta g>  y es robs 1, so use sud o<paultag>ro bs1 , neve r work asroot, run *single* comm a nds und errootwith  su -c 'f oo'  or su dof oo
<ro bs1> y es, v er y g o o d poi n t  p aul ta g
paultag> <paultag>_robs1, cd_~
<paultag> <paultag> robs1, it's_full unexpanded_name_is ~/.ssh
<Tallon>_@Mohan,_ok thanks just_wasn't sure with_the amd in the_title
<robs1> I tried_that
<robs1>_root@svlso-3-3:~# ls -a ~/.ssh
<robs1> ls: cannot access /root/.ssh: No such file or directory
<robs1> root@svlso-3-3:~#
<Mohan_chml>_Tallon,_(:
<paultag> robs1,_first_of_all, working as root is_really really dumb
<paultag> robs1, second_of all,_you need to ssh one time :)
<paultag> robs1,_it_imports conf directories_as you need them
<robs1> okay...I backed out of root_and am operating as a regular_user
<paultag> robs1, ssh_one_time
<paultag>_robs1, and you will_have this directory
<robs1> doing so now
<robs1>_ Ah, ok.  I now_see the.ssh directory
<robs1> Thanks paultag...that got me_going.
<paultag> sure robs1
<paultag> robs1, good luck!
<robs1>_btw...in this case, it is_not dumb_to be working as root_because I am_installing a_backup solution that_requires that this be done as_root
<paultag> robs1, that's_not true
<paultag> robs1, run the installer_with_sudo
<paultag> robs1, you_should_*never*_have to_use root
<robs1> I'm_installing_an enterprise_backup_solution....it says that it must be_installed_as root...or the install will not complete
<robs1>_And I verified that_to_be true.
<paultag> yes robs1,_so use sudo
<paultag> robs1, never_work as root, run *single* commands_under root_with su_-c 'foo' or sudo foo
<robs1> yes, very good point paultag