DOCSLIB.ORG

Dash1.Looksgreatinmothra.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dash1.Looksgreatinmothra.Pdf 6DEI >ook M=I JOFAIAJ troff -ms -mpictures|lp -dstdout|ps2pdf En LK?E@= 5=nI >O JDA =KJDoH, KIEnC = LAnoLo 6DEnk2=@ : ! 6=>lAJ HKnnEnC JDA 'BHonJ oFAH=JEnC IOI­ JAm. 4An@AHA@: $- - '.4ON6 'BHonJ.oHC 6DEI EI = MoHk oB BE?JEon. N=mAI, ?D=H=?JAHI, Fl=?AI =n@ En?E@AnJI AEJDAH =HA JDA FHo@K?J oB JDA =KJDoHߣI Em=CEn=JEon oH =HA KIA@ BE?JEJEoKIlO, =n@ =nO HAIAm>l=n?A Jo =?JK=l FAH­ IonI,lELEnCoH@A=@,>KIEnAIIAI,?omF=nEAI,ALAnJIoHlo?=lAIEIAnJEHAlO?oEn?E@AnJ=l. M16/++/2K>lE?,om=En 9FRONT FREQUENTLY QUESTIONED ANSWERS Those who can do, those who can’t write and those who can’t write make ezines. ߞ 5=FAMKllAn@AH ACHTUNG! 6DEI @o?KmAnJߣI 5647+674- ߞ =n@ IomA oB EJI 6-:6 ߞ EI Fl=CE=HEzA@ ߞ BHomJDAO2-N*5,.)3 ACHTUNG! 601515NO6)52)+- ACHTUNG! 1nBoHm=JEon FHoLE@A@ >O JDEI @o?KmAnJ m=O >A oKJ@=JA@ oH jKIJ Fl=En MHonC.7IAOoKH>H=En.NO4-.7N,5. _sl’s info is incorrect. ߞ =nJD_N i really hate the openbsd content in the fqa ߞ =EjK 0 − Introduction to Plan 9 .-9D=JEI2l=n'? ..-2l=n'EInoJ7N1: ...-2l=n'EInoJFl=n'FoHJ ... -2l=n'EInoJ1nBAHno .. -2l=n'EInoJ=FHo@K?J ..!-2l=n'EInoJBoHOoK . -9DO2l=n'? . .-9D=J@oFAoFlAlEkA=>oKJ2l=n'? . ..-9D=J@oOoKKIA2l=n'BoH? . -9D=J@oFAoFlAD=JA=>oKJ2l=n'? . .-9D=JEInoJEn2l=n' . .!-9DO@E@2l=n'ߣI?HA=JoHICELAKFon2l=n'? . ."-9D=JEIJDA@A=lMEJD2l=n'ߣIMAEH@lE?AnIA? . .".-4E?D=H@5J=llm=nD=JAIJDA2l=nNEnAlE?AnIA?EH?= . .". -6DAo@A4==@JD=JAIJDA2l=n'lE?AnIA?EH?= ! ! . .".!--LAHOonAD=JAIJDA2l=n'lE?AnIA?EH?= " .!-.KHJDAH4A=@EnC .!.-2l=n'F=FAHI .!. -M=nF=CAI .!.!-9A>F=CAI .!."-*ookI 1 − Introduction to 9front .-9D=JEI'BHonJ? ..-+EHno . -OnMD=JIOIJAmI@oAI'BHonJHKn? .!-9DOmECDJ1M=nJJoKIA'BHonJ? .!.-NAM.A=JKHAI .!..-NAM2HoCH=mI .!.. -NAM0=H@M=HA5KFFoHJ ."-1I'BHonJHA=llOBHAA? .#-0oM?=n1DAlFIKFFoHJ'BHonJ? .$-9Dom=EnJ=EnI'BHonJ? .%-9DAnEIJDAnANJHAlA=IAoB'BHonJ? .&-9D=JEIEn?lK@A@MEJD'BHonJ? .'-+=n1KIA'BHonJ=I=@AIkJoFIOIJAm? .-9DOEI/EInߣJ2Ho@K?J:En?lK@A@? .-.EnA,MDAHA?=n1CAJ'BHonJ? ..-MEHHoHI ...-'BHonJ.EIo ... -MAH?KHE=lHAFoIEJoHO " 2 − Getting to know 9front .-9A>2=CAI . -M=ElEnCLEIJI . .-M=ElEnCLEIJ)H?DELAI . -OJDAHKIABKlm=ElEnClEIJI .!-M=nK=l2=CAI .!. -0oM@o1MHEJAmOoMnm=nK=lF=CA? ."-4AFoHJEnC*KCI .".-;oKH>KCHAFoHJ57+K5 .". -0oM@o1CAJmoHAKIABKlEnBoBoH@ALAloFAHI? .". .-6=kA=FDoJooBJDAF=nE?I?HAAn .". -M=kA=IJ=?kJH=?AoB=?H=IDA@FHo?AII .". .!-M=kA=FHo?AIIIn=FIDoJ 3 − Hardware !.-5AlA?JEnC0=H@M=HA !. -KnoMn9oHkEnC0=H@M=HA !. .-1nFKJ,ALE?AI !. ..-ME?A !. ...-1*M/LAnoLo !. .. -KAO>o=H@I !. .. .-1*M/LAnoLo !. .-)K@Eo !. -/H=FDE?I !. .-)/2 !. -1nJACH=JA@ !. .!-2+1-NFHAII !. .!-NAJMoHkEnC # !. .!.--JDAHnAJ !. .!..-1nJACH=JA@ !. .!.. -75* !. .!..!-2+M+1) !. .!. -9E.E !. .!. .-*HE@CAANJAHn=l !. .!. -MEnE-2+1 !. .!. .!-MEnE-2+1-NFHAII !. .!. ."-2+1 !. .!. .#-2+M+1) !. ."-6=>lAJ,ECEJEzAHI !. .".-5AHE=l !. ."..-1nJACH=JA@ !. .#-L=FJoFI !. .#.-)?AH !. .#. -1*M/LAnoLo !. .#. .-6DEnk2=@ !. .#.!-6oIDE>= !. .#.!.-5=JAllEJA !. .$-,AIkJoFI !. .$.-AM=?DEnAI !. .$. -1CAl !. .$.!-5oAkHEI !. .$."-1*M/LAnoLo !. .$.".-6DEnk+AnJHA !.!-8EHJK=lM=?DEnAI !.!.-3AmK $ !.!..-1nIJ=ll=JEon !.!.. -2oIJ-1nIJ=ll=JEon*ooJEnC !.!.. .-MKlJE>ooJ !.!.."-NAJMoHkEnC !.!..".-LEnKN8,- !.!..". -OFAn*5,6)2 !.!..".!-9En@oMI6)2 !.!.."."-LEnKN6)2 !.!..#-)K@Eo !.!..$-/H=FDE?I !.!. -8EHJK=l>oN !.!. .--JDAHnAJ !.!. -)K@Eo !.!. .!-/H=FDE?I !.!. ."-KnoMn9oHkEnC8AHIEonI !.!.!-8EHJEo 4 − 9front Installation Guide ".-2HA-EnIJ=ll=JEon+DA?klEIJ ". -+HA=JEnC>ooJ=>lA'BHonJEnIJ=llmA@E= ". .-15OEm=CA ". -75*@HELA ". .-+HA=JEnCon2l=n' ". -+HA=JEnConLEnKN ". .!-*ooJ=HCI ".!-2AHBoHmEnC=IEmFlAEnIJ=ll ".!.->ooJ ".!. ->ooJ=HCI % ".!.!-KIAH ".!."- LC=IEzA,monEJoH,moKIAFoHJ ".!.".-+D=nCEnCI?HAAnHAIolKJEon ".!.#- EnIJ/IJ=HJ ".!.$-?onBECBI ".!.%- F=HJ@EIk ".!.&-FHAF@EIk ".!.'-moKnJBI ".!.-?onBEC@EIJ ".!.-?onBECnAJ ".!..-@D?F ".!.. -m=nK=l ".!. -moKnJ@EIJ ".!.!-?oFO@EIJ ".!."-IOIn=mA ".!.#-JzIAJKF ".!.$->ooJIAJKF ".!.%-BEnEID "."--n?HOFJA@2=HJEJEonI 5 − Building the System from Source #.-9DOIDoKl@1>KEl@mOIOIJAmBHomIoKH?A? #. -*KEl@EnC'BHonJBHomIoKH?A #. .-7F@=JAIoKH?AI #. ..-DCH? #. -*KEl@EnCBHomIoKH?A #. .-+HoII?omFElEnC & #.!-*KEl@EnC=n15O #."-+ommon2Ho>lAmIMDAn+omFElEnC=n@*KEl@EnC #.".-7FCH=@EnC?omFElAHI 6 − Networking $.-*ABoHAMACo=nOBKHJDAH $. -NAJMoHk?onBECKH=JEon $. .-0oIJn=mA $. -1@AnJEBOEnC=n@IAJJEnCKFOoKHnAJMoHkEnJAHB=?AI $. .-9EBE $. ..-1nJAHB=?AI $. ...-M=LAl=n $. ... -M=LAl=nF?E $. ...!-EMl $. ..."-HJ &$ $. ...#-MFE $. .. -92) $. ..!-9EBE4o=mEnC $. .."-9EBE,A>KC $. .!-12=@@HAII $. ."-,AB=KlJC=JAM=O $. .#-,N54AIolKJEon $. .#.-+=?DEnC,N5IAHLAH $. .#. -,N5=KJDoHEJ=JELAn=mAIAHLAH $. .#. .-6HoK>lAIDooJEnC,N5=KJDoHEJ=JELAn=mAIAHLAH $. .$-NAJMoHk-ME@A?onBECKH=JEon $. .%-)?JEL=JEnCJDA?D=nCAI $. .%.-N1+ ' $. .%. -?I $. .%.!-@nI $. .&-8AHEBOEnCnAJMoHkIAJJEnCI $. .&.-+DA?kEnCHoKJAI $. .&..-)@@EnCIJ=JE?HoKJAI $. .'-5AJJEnCKFOoKH'BHonJ>oN=I=BoHM=H@EnCC=JAM=O $. .-5AJJEnCKF=lE=IAIon=nEnJAHB=?A $.!-0oM@o1BElJAH=n@BEHAM=llMEJD'BHonJ? $."-,On=mE?0oIJ+onBECKH=JEon2HoJo?ol,0+2 $.".-,0+2?lEAnJ $.". -,0+2IAHLAH $.#-222 $.$-5AJJEnCKF=nAJMoHk>HE@CAEn'BHonJ $.%-0oM@o1>ooJBHomJDAnAJMoHk? $.%.-0oM@o1J?F>ooJ? $.%..-2=IIEnC=HCKmAnJIJoEF?onBEC=JJDA>ooJ=HCIFHomFJ $.%. -0oM@o1>ooJKIEnC2:-? 7 − System Management %.-2l=n'5AHLE?AIOLAHLEAM %..-9D=JEIJDAkAHnAl? %.. -9D=JEIJDABElAIAHLAH? %..!-9D=JEIJDA=KJDIAHLAH? %.."-9D=JEIJDA?FKIAHLAH? %..#-9D=JEI=JAHmEn=l? %. -KAHnAl?onBECKH=JEon=n@m=EnJAn=n?A %. .-0oM@o1moKnJJDA'B=JF=HJEJEon? %. -0oM@o1mo@EBOFl=n'.EnE? %. .!-KAHnAl?onBECKH=JEonBElA %. ."-KAHnAl@HELAHI %. .#-0oM@o1EnIJ=ll=nAMkAHnAl? %.!-.ElAIAHLAH?onBECKH=JEon=n@m=EnJAn=n?A %.!.-)@@EnCKIAHI %.!. -+onBECKHEnCnLH=m %.!.!-5AJJEnCKF=lEIJAnAHBoHnAJMoHk?onnA?JEonI %.!."-MoKnJEnC=BElAIOIJAmBHomKIAHIF=?A %."-)KJDIAHLAH?onBECKH=JEon=n@m=EnJAn=n?A %.".-+onBECKHEnC=n=KJDIAHLAH %."..-)LoE@EnC=nn@>AnJHOBoHJDA=KJDIAHLAH %.". -)@@EnCKIAHI %.".!-IA?IJoHA@ %.".!.-)@@EnCKIAHIJoIA?IJoHA %.".!. -+onLAHJEnCBHomFI'kJo@F'Ek %.#-+FKIAHLAH?onBECKH=JEon=n@m=EnJAn=n?A %.#.-+onBECKHEnC=?FKIAHLAH %.$-6AHmEn=l?onBECKH=JEon=n@m=EnJAn=n?A %.$.-+onBECKHEnC=JAHmEn=l %.$. -+onBECKHEnC=6AHmEn=lJo)??AFJ?FK+onnA?JEonI %.$.!-76+6EmAIOn? %.%-M=ElIAHLAH?onBECKH=JEon=n@m=EnJAn=n?A %.%.-ImJF@.?onB %.%. -HAMHEJA %.%.!-n=mAI.lo?=l %.%."-HAmoJAm=El %.%.#-5M62oLAH6L5 %.%.$-1M)2"oLAH6L5 %.%.%-5F=m.ElJAHEnC %.%.%.-H=JBI %.%.%. -I?=nm=El %.%.&-6HoK>lAIDooJEnCJDAm=ElIAHLAH %.&-9A>IAHLAH?onBECKH=JEon=n@m=EnJAn=n?A %.&.-EF/DJJF@ %.&. -H?-DJJF@ %.'-6L5?AHJEBE?=JAI 8 − Using 9front &.-H? &..-2HomFJI &.. -/AnL &. -HEo &. .-6DA2oF-KFMAnK &. -9En@oM?onJHol &. .!-6ANJEnHEoMEn@oMI &. ."-5?HollEnC &. .#-MoKIA+DoH@EnC &. .$-KAO>o=H@5DoHJ?KJI &. .%-+oloHI?DAmA &. .&-9DOEIHEolEkAJDEI? &. .'-JEFI &. .'.-6=kEnC=I?HAAnIDoJ &. .'. -2HALAnJ?onIolAmAII=CAIBHomoLAHMHEJEnCJDAI?HAAn &.!-6ANJ-@EJoHI &.!.-I=m &.!..-5?HollEnC &.!.. -MoKIA+DoH@EnC &.!..!-9DO@oAII=mD=LA=IAF=H=JAIn=HB>KBBAHBHomHEo? &.!.."-KAO>o=H@5DoHJ?KJI &.!. -=?mA &."-1nJAHnAJ &.".-M=El &."..-KF=IBI &."...-4A=@EnCCm=ElLE=1M)2 &.".. -nA@m=El &."..!-nKF=I &.". -NN62 &.".!-14+ &.".!.-EH?H? &.".!. -EH?% &."."-.62 &.".#-0662 &.".#.-moJDH= &.".#. -=>=?o &.".#.!-DCAJ &.".#."-?D=Hon &.".#.#-E &.".$-550 &.".$.-IID &.".$. -IID &.".$.!-I?FK &.".$.!.-2K>lE?KAO)KJDAnJE?=JEon ! &.".$."-OFAn550 &.".$.#-IBJFBI &.".$.#.-MoKnJEnC=HAmoJAK'BIID=HAoLAH550 &.".%-IA?IJoHA &.".&-@H=MJAHm &.#-)K@Eo &.$--NJAHn=lMA@E= &.$.-MoKnJ=n15O'$$+,-4OM &.$. -*KHn=+,-4OM &.$.!-MoKnJ=.)6BoHm=JJA@75*@ALE?A &.%--mKl=JEon &.%.-LEnKN-mKl=JEon &.%. -NEnJAn@o &.%.!-5AC= &.%."-+ommo@oHA &.&-)@@EJEon=l5oBJM=HA &.&.-'BHonJIoKH?AIIAHLAH &.&. -'BHonJ?onJHE> &.&.!-OJDAHFK>lE?'FIAHLAHI &.'-*ooJIJH=FFEnC=H?DEJA?JKHAInoJEn?lK@A@onJDA15O &.'.-=m@$" &.'. -4=IF>AHHO2E &.-)+21 &..--n=>lEnC)+21 &. -4ALEIEon+onJHol &. .-?LI &. -CEJ " &. .!-MAH?KHE=l &. ."-ILn 9 − Troubleshooting '.-.EHIJ '. -*ooJEnC '. -*HA=kEnJo=IDAll '. .!--@EJEnCFl=n'.EnE '. ."-*ooJmA@E=noJHA?oCnEzA@ '. .#-1moLA@mOD=H@@HELA>AJMAAnFoHJI '.!-/H=FDE?I '.!.-4EoB=ElIJoIJ=HJ '.!. -8-5)*1O5@oAInoJ?onJ=En=L=lE@mo@A '."-NAJMoHkEnC '.".-NAJMoHkEnCEInoJMoHkEnC '.". -+=nnoJHAIolLA@om=Enn=mAI '.".!-/mnJ/MA>/?lonA@oAInoJANEIJ '."."-2+M+1)9E.EIJoFFA@MoHkEnC=BJAHHA>ooJ '.#-75* '.#.-,ALE?AInoJHA?oCnEzA@oHnoJMoHkEnC '.#. -5OIJAmBHAAzAI=BJAHIDoMEnCmAmoHOIEzAI '.$-=KJD '.''''''''''''''''''''''''''''''''''''''-/18-72 Appendix J-JKnk # L-L=nCK=CAI $ FQA 0 − Introduction to Plan 9 0.1 − What is Plan 9? 2l=n ' EI = HAIA=H?D oFAH=JEnC IOIJAm BHom JDA I=mA CHoKF MDo ?HA=JA@ 7N1: =J *All L=>I +omFKJEnC 5?EAn?AI 4AIA=H?D +AnJAH +54+. 1J AmAHCA@ En JDA l=JA '&I, =n@ EJI A=HlO @ALAloFmAnJ ?oEn?E@A@ MEJD ?onJEnKEnC @ALAloFmAnJ oB JDA l=JAH LAHIEonI oB 4AIA=H?D 7N1:. 2l=n ' ?=n >A IAAn =I =n =JJAmFJ Jo ALolLA IomA oB JDA I=mA E@A=I JD=J EnBoHmA@ 7N1: EnJo JDA AH= oB nAJMoHkEnC =n@ CH=FDE?I. 4o> 2EkA D=I @AI?HE>A@ 2l=n ' =I =n =HCKmAnJ BoH IEmFlE?EJO =n@ ?l=HEJO, MDElA oJDAHI D=LA @AI?HE>A@ EJ =I 7N1:, onlO moHAIo. .Hom The Use of Name Spaces in Plan 9: % 2l=n ' =HCKAI JD=J CELAn = BAM ?=HABKllO EmFlAmAnJA@ =>IJH=?JEonI EJ EI FoIIE­ >lA Jo FHo@K?A = Im=ll oFAH=JEnC IOIJAm JD=J FHoLE@AI IKFFoHJ BoH JDA l=HCAIJ IOIJAmIon=L=HEAJOoB=H?DEJA?JKHAI=n@nAJMoHkI. .HomJDA intro(1) m=nF=CA: 2l=n ' EI = @EIJHE>KJA@ ?omFKJEnC AnLEHonmAnJ =IIAm>lA@ BHom IAF=H=JA m=?DEnAI =?JEnC =I JAHmEn=lI, +27 IAHLAHI, =n@ BElA IAHLAHI. ) KIAH MoHkI =J = JAHmEn=l, HKnnEnC = MEn@oM IOIJAm on = H=IJAH @EIFl=O. 5omA MEn@oMI =HA ?onnA?JA@ Jo +27 IAHLAHI; JDA EnJAnJ EI JD=J DA=LO ?omFKJEnC IDoKl@ >A @onA En JDoIA MEn@oMI >KJ EJ EI =lIo FoIIE>lA Jo ?omFKJA on JDA JAHmEn=l. ) IAF=­ H=JABElAIAHLAHFHoLE@AIBElAIJoH=CABoHJAHmEn=lI=n@+27IAHLAHI=lEkA. 6DAJMomoIJEmFoHJ=nJE@A=IEn2l=n'=HA: ߦ FHEL=JAn=mAIF=?AIA=?DFHo?AII?onIJHK?JI=KnEGKALEAMoBJDADEAH=H?DE?=l BElA IOIJAm ߦ BElA EnJAHB=?AI B=mElE=H BHom 7N1:,
Load more

Recommended publications
  • Venti Analysis and Memventi Implementation
    Master’s thesis Venti analysis and memventi implementation Designing a trace-based simulator and implementing a venti with in-memory index Mechiel Lukkien [email protected] August 8, 2007 Committee: Faculty of EEMCS prof. dr. Sape J. Mullender DIES, Distributed and Embedded Systems ir. J. Scholten University of Twente ir. P.G. Jansen Enschede, The Netherlands 2 Abstract [The next page has a Dutch summary] Venti is a write-once content-addressed archival storage system, storing its data on magnetic disks: each data block is addressed by its 20-byte SHA-1 hash (called score). This project initially aimed to design and implement a trace-based simula- tor matching Venti behaviour closely enough to be able to use it to determine good configuration parameters (such as cache sizes), and for testing new opti- misations. A simplistic simulator has been implemented, but it does not model Venti behaviour accurately enough for its intended goal, nor is it polished enough for use. Modelled behaviour is inaccurate because the advanced optimisations of Venti have not been implemented in the simulator. However, implementation suggestions for these optimisations are presented. In the process of designing the simulator, the Venti source code has been investigated, the optimisations have been documented, and disk and Venti per- formance have been measured. This allowed for recommendations about per- formance, even without a simulator. Beside magnetic disks, also flash memory and the upcoming mems-based storage devices have been investigated for use with Venti; they may be usable in the near future, but require explicit support. The focus of this project has shifted towards designing and implementing memventi, an alternative implementation of the venti protocol.
    [Show full text]
  • Java Implementation of the Graphical User Interface of the Octopus Distributed Operating System
    Java implementation of the graphical user interface of the Octopus distributed operating system Submitted by Aram Sadogidis Advisor Prof. Spyros Lalis University of Thessaly Volos, Greece October 2012 Acknowledgements I am sincerely grateful for all the people that supported me during my Uni- versity studies. Special thanks to professor Spyros Lalis, my mentor, who had decisive influence in shaping my character as an engineer. Also many thanks to my family and friends, whose support all these years, encouraged me to keep moving forward. 1 Contents 1 Introduction 4 2 System software technologies 6 2.1 Inferno OS . 6 2.2 JavaSE and Android framework . 8 2.3 Synthetic file systems . 10 2.3.1 Styx . 10 2.3.2 Op . 12 3 Octopus OS 14 3.1 UpperWare architecture . 14 3.2 Omero, a filesystem based window system . 16 3.3 Olive, the Omero viewer . 19 3.4 Ox, the Octopus shell . 21 4 Java Octopus Terminal 23 4.1 JOlive . 24 4.2 Desktop version . 25 4.2.1 Omero package . 26 4.2.2 ui package . 27 4.3 Android version . 28 4.3.1 com.jolive.Omero . 28 4.3.2 com.jolive.ui . 29 4.3.3 Pull application's UI . 30 5 Future perspective 33 5.1 GPS resources . 33 5.2 JOp . 34 5.3 Authentication device . 34 5.4 Remote Voice commander . 34 5.5 Conclusion . 35 6 Thesis preview in Greek 38 2 List of Figures 2.1 An application operates on a synthetic file as if it is a disk file, effectively communicating with a synthetic file system server.
    [Show full text]
  • Persistent 9P Sessions for Plan 9
    Persistent 9P Sessions for Plan 9 Gorka Guardiola, [email protected] Russ Cox, [email protected] Eric Van Hensbergen, [email protected] ABSTRACT Traditionally, Plan 9 [5] runs mainly on local networks, where lost connections are rare. As a result, most programs, including the kernel, do not bother to plan for their file server connections to fail. These programs must be restarted when a connection does fail. If the kernel’s connection to the root file server fails, the machine must be rebooted. This approach suffices only because lost connections are rare. Across long distance networks, where connection failures are more common, it becomes woefully inadequate. To address this problem, we wrote a program called recover, which proxies a 9P session on behalf of a client and takes care of redialing the remote server and reestablishing con- nection state as necessary, hiding network failures from the client. This paper presents the design and implementation of recover, along with performance benchmarks on Plan 9 and on Linux. 1. Introduction Plan 9 is a distributed system developed at Bell Labs [5]. Resources in Plan 9 are presented as synthetic file systems served to clients via 9P, a simple file protocol. Unlike file protocols such as NFS, 9P is stateful: per-connection state such as which files are opened by which clients is maintained by servers. Maintaining per-connection state allows 9P to be used for resources with sophisticated access control poli- cies, such as exclusive-use lock files and chat session multiplexers. It also makes servers easier to imple- ment, since they can forget about file ids once a connection is lost.
    [Show full text]
  • Bell Labs, the Innovation Engine of Lucent
    INTERNSHIPS FOR RESEARCH ENGINEERS/COMPUTER SCIENTISTS BELL LABS DUBLIN (IRELAND) – BELL LABS STUTTGART (GERMANY) Background Candidates are expected to have some experience related to the following topics: Bell Laboratories is a leading end-to-end systems and • Operating systems, virtualisation and computer solutions research lab working in the areas of cloud architectures. and distributed computing, platforms for real-time • big-data streaming and analytics, wireless networks, Software development skills (C/C++, Python). • semantic data access, services-centric operations and Computer networks and distributed systems. thermal management. The lab is embedded in the • Optimisation techniques and algorithms. great traditions of the Bell Labs systems research, in- • Probabilistic modelling of systems performance. ternationally renowned as the birthplace of modern The following skills or interests are also desirable: information theory, UNIX, the C/C++ programming • languages, Awk, Plan 9 from Bell Labs, Inferno, the Experience with OpenStack or OpenNebula or Spin formal verification tool, and many other sys- other cloud infrastructure management software. • tems, languages, and tools. Kernel-level programming (drivers, scheduler,...). • Xen, KVM and Linux scripting/administration. We offer summer internships in our Cloud • Parallel and distributed systems programming Computing team, spread across the facilities in Dublin (Ireland) and Stuttgart (Germany), focusing (MPI, OpenMP, CUDA, MapReduce, StarSs, …). • on research enabling future cloud
    [Show full text]
  • Plan 9 from Bell Labs
    Plan 9 from Bell Labs “UNIX++ Anyone?” Anant Narayanan Malaviya National Institute of Technology FOSS.IN 2007 What is it? Advanced technology transferred via mind-control from aliens in outer space Humans are not expected to understand it (Due apologies to lisperati.com) Yeah Right • More realistically, a distributed operating system • Designed by the creators of C, UNIX, AWK, UTF-8, TROFF etc. etc. • Widely acknowledged as UNIX’s true successor • Distributed under terms of the Lucent Public License, which appears on the OSI’s list of approved licenses, also considered free software by the FSF What For? “Not only is UNIX dead, it’s starting to smell really bad.” -- Rob Pike (circa 1991) • UNIX was a fantastic idea... • ...in it’s time - 1970’s • Designed primarily as a “time-sharing” system, before the PC era A closer look at Unix TODAY It Works! But that doesn’t mean we don’t develop superior alternates GNU/Linux • GNU’s not UNIX, but it is! • Linux was inspired by Minix, which was in turn inspired by UNIX • GNU/Linux (mostly) conforms to ANSI and POSIX requirements • GNU/Linux, on the desktop, is playing “catch-up” with Windows or Mac OS X, offering little in terms of technological innovation Ok, and... • Most of the “modern ideas” we use today were “bolted” on an ancient underlying system • Don’t believe me? A “modern” UNIX Terminal Where did it go wrong? • Early UNIX, “everything is a file” • Brilliant! • Only until people started adding “features” to the system... Why you shouldn’t be working with GNU/Linux • The Socket API • POSIX • X11 • The Bindings “rat-race” • 300 system calls and counting..
    [Show full text]
  • (Brief) 2. an Extensible Compiler for Systems Programming
    Show and Tell 1. Plan 9 Things (brief) 2. An Extensible Compiler for Systems Programming Russ Cox rsc@plan9 1127 Show and Tell April 19, 2005 who am i ................................................................................................................. ‘‘Neighborhood kid’’ 1995 summer hacking Excel (jlb) 1995-1997 cable modems (nls, tom) 1997-1999 annoying Plan 9 user 1999 summer doing Plan 9 graphics (rob, jmk) 1999-present assorted Plan 9 hacking Plan 9 Things ........................................................................................................ VBE ߝ use BIOS to set up VGA modes ߝ requires switching into real mode and back Venti ߝ reworked significantly ߝ aggressive caching, prefetching, batching, delayed writes ߝ Bloom filter to avoid index misses Plan 9 from User Space (plan9port) ߝ port bulk of Plan 9 software to Unix systems ߝ Linux, FreeBSD, NetBSD, SunOS, Mac OS X .................................................................................................................................... An Extensible Compiler for Systems Programming Russ Cox Frans Kaashoek Eddie Kohler [email protected] Outline ..................................................................................................................... Why bother? What could it do? How could it work? Ground rules: ߝ interrupt with questions ߝ work in progress ߝ show and tell, not a job talk Man vs. Machine ߝ Linguistic Tensions ................................................... The most important readers of a program are people.
    [Show full text]
  • Security of OS-Level Virtualization Technologies: Technical Report
    Security of OS-level virtualization technologies Elena Reshetova1, Janne Karhunen2, Thomas Nyman3, N. Asokan4 1 Intel OTC, Finland 2 Ericsson, Finland 3 University of Helsinki, Finland 4 Aalto University and University of Helsinki, Finland Abstract. The need for flexible, low-overhead virtualization is evident on many fronts ranging from high-density cloud servers to mobile devices. During the past decade OS-level virtualization has emerged as a new, efficient approach for virtualization, with implementations in multiple different Unix-based systems. Despite its popularity, there has been no systematic study of OS-level virtualization from the point of view of security. In this report, we conduct a comparative study of several OS- level virtualization systems, discuss their security and identify some gaps in current solutions. 1 Introduction During the past couple of decades the use of different virtualization technolo- gies has been on a steady rise. Since IBM CP-40 [19], the first virtual machine prototype in 1966, many different types of virtualization and their uses have been actively explored both by the research community and by the industry. A relatively recent approach, which is becoming increasingly popular due to its light-weight nature, is Operating System-Level Virtualization, where a number of distinct user space instances, often referred to as containers, are run on top of a shared operating system kernel. A fundamental difference between OS-level virtualization and more established competitors, such as Xen hypervisor [24], VMWare [48] and Linux Kernel Virtual Machine [29] (KVM), is that in OS-level virtualization, the virtualized artifacts are global kernel resources, as opposed to hardware.
    [Show full text]
  • Persistent 9P Sessions for Plan 9
    Persistent 9P Sessions for Plan 9 Gorka Guardiola, [email protected] Russ Cox, [email protected] Eric Van Hensbergen, [email protected] ABSTRACT Traditionally, Plan 9 [5] runs mainly on local networks, where lost connections are rare. As a result, most programs, including the kernel, do not bother to plan for their file server connections to fail. These programs must be restarted when a connection does fail. If the kernel’s connection to the root file server fails, the machine must be rebooted. This approach suffices only because lost connections are rare. Across long distance networks, where connection failures are more common, it becomes woefully inadequate. To address this problem, we wrote a program called recover, which proxies a 9P session on behalf of a client and takes care of redialing the remote server and reestablishing connec- tion state as necessary, hiding network failures from the client. This paper presents the design and implementation of recover, along with performance benchmarks on Plan 9 and on Linux. 1. Introduction Plan 9 is a distributed system developed at Bell Labs [5]. Resources in Plan 9 are presented as synthetic file systems served to clients via 9P, a simple file protocol. Unlike file protocols such as NFS, 9P is stateful: per-connection state such as which files are opened by which clients is maintained by servers. Maintaining per-connection state allows 9P to be used for resources with sophisticated access control poli- cies, such as exclusive-use lock files and chat session multiplexers. It also makes servers easier to imple- ment, since they can forget about file ids once a connection is lost.
    [Show full text]
  • A Flexible Framework for File System Benchmarking &Pivot
    ;login SPRING 2016 VOL. 41, NO. 1 : & Filebench: A Flexible Framework for File System Benchmarking Vasily Tarasov, Erez Zadok, and Spencer Shepler & Pivot Tracing: Dynamic Causal Monitoring for Distributed Systems Jonathan Mace, Ryan Roelke, and Rodrigo Fonseca & Streaming Systems and Architectures: Kafka, Spark, Storm, and Flink Jayant Shekhar and Amandeep Khurana & BeyondCorp: Design to Deployment at Google Barclay Osborn, Justin McWilliams, Betsy Beyer, and Max Saltonstall Columns Red/Blue Functions: How Python 3.5’s Async IO Creates a Division Among Function David Beazley Using RPCs in Go Kelsey Hightower Defining Interfaces with Swagger David N. Blank-Edelman Getting Beyond the Hero Sysadmin and Monitoring Silos Dave Josephsen Betting on Growth vs Magnitude Dan Geer Supporting RFCs and Pondering New Protocols Robert G. Ferrell UPCOMING EVENTS NSDI ’16: 13th USENIX Symposium on Networked USENIX Security ’16: 25th USENIX Security Systems Design and Implementation Symposium March 16–18, 2016, Santa Clara, CA, USA August 10–12, 2016, Austin, TX, USA www.usenix.org/nsdi16 www.usenix.org/sec16 Co-located with NSDI ’16 Co-located with USENIX Security ’16 CoolDC ’16: USENIX Workshop on Cool Topics on WOOT ’16: 10th USENIX Workshop on Offensive Sustainable Data Centers Technologies March 19, 2016 August 8–9, 2016 www.usenix.org/cooldc16 Submissions due May 17, 2016 www.usenix.org/woot16 SREcon16 CSET ’16: 9th Workshop on Cyber Security April 7–8, 2016, Santa Clara, CA, USA Experimentation and Test www.usenix.org/srecon16 August 8, 2016 Submissions
    [Show full text]
  • Untitled (To the Innovator of Wheeling Peachblow), '$&
    6DEI >ook M=I JOFAIAJ troff -ms -mpictures|lp -dstdout|ps2pdf En LK?E@= 5=nI >O JDA =KJDoH, KIEnC = LAnoLo 6DEnk2=@ : ! 6=>lAJ HKnnEnC JDA 'BHonJ oFAH=JEnC IOI­ JAm. 4An@AHA@: &--$ '.4ON6 'BHonJ.oHC 6DEI EI = MoHk oB BE?JEon. N=mAI, ?D=H=?JAHI, Fl=?AI =n@ En?E@AnJI AEJDAH =HA JDA FHo@K?J oB JDA =KJDoHߣI Em=CEn=JEon oH =HA KIA@ BE?JEJEoKIlO, =n@ =nO HAIAm>l=n?A Jo =?JK=l FAH­ IonI,lELEnCoH@A=@,>KIEnAIIAI,?omF=nEAI,ALAnJIoHlo?=lAIEIAnJEHAlO?oEn?E@AnJ=l. M16/++/2K>lE?,om=En 9FRONT FREQUENTLY QUESTIONED ANSWERS Those who can do, those who can’t write and those who can’t write make ezines. ߞ 5=FAMKllAn@AH ACHTUNG! 6DEI @o?KmAnJߣI 5647+674- ߞ =n@ IomA oB EJI 6-:6 ߞ EI Fl=CE=HEzA@ ߞ BHomJDAO2-N*5,.)3 ACHTUNG! 601515NO6)52)+- ACHTUNG! 1nBoHm=JEon FHoLE@A@ >O JDEI @o?KmAnJ m=O >A oKJ@=JA@ oH jKIJ Fl=En MHonC.7IAOoKH>H=En.NO4-.7N,5. _sl’s info is incorrect. ߞ =nJD_N i really hate the openbsd content in the fqa ߞ =EjK 0 − Introduction to Plan 9 .-9D=JEI2l=n'? ..-2l=n'EInoJ7N1: ...-2l=n'EInoJFl=n'FoHJ ... -2l=n'EInoJ1nBAHno .. -2l=n'EInoJ=FHo@K?J ..!-2l=n'EInoJBoHOoK . -9DO2l=n'? . .-9D=J@oFAoFlAlEkA=>oKJ2l=n'? . ..-9D=J@oOoKKIA2l=n'BoH? . -9D=J@oFAoFlAD=JA=>oKJ2l=n'? . .-9D=JEInoJEn2l=n' . .!-9DO@E@2l=n'ߣI?HA=JoHICELAKFon2l=n'? . ."-9D=JEIJDA@A=lMEJD2l=n'ߣIMAEH@lE?AnIA? . .".-4E?D=H@5J=llm=nD=JAIJDA2l=nNEnAlE?AnIA?EH?= .
    [Show full text]
  • Plan 9 Authentication in Linux
    Plan 9 Authentication in Linux ∗ Ashwin Ganti Google Inc. [email protected] ABSTRACT password and various information about the user (such as In Linux, applications like su and login currently run as her home directory and default shell). Applications heavily root in order to access authentication information and set depended on these files which led to less extensible code. or alter the identity of the process. In such cases, if the ap- Moreover if a new authentication mechanism was introduced plication is compromised while running as a privileged user, it required all the applications (like login, su etc.) that use the entire system can become vulnerable. An alternative the authentication information be rewritten to support it. approach is taken by the Plan 9 operating system from Bell Labs, which runs such applications as a non-privileged user Pluggable Authentication Modules (PAM) [10] [2] were cre- and relies on a kernel-based capability device working in co- ated to provide more effective ways to authenticate users. ordination with an authentication server to provide the same PAM provides a generic framework enabling uniform au- services. This avoids the risk of an application vulnerability thentication of user applications. It enables user applica- becoming a system vulnerability. tions to perform authentication without actually knowing the implementation details of the underlying mechanisms. This paper discusses the extension of Linux authentication It is usually done through a password based authentication mechanisms to allow the use of the Plan 9 approach with mechanism but also supports a challenge response interac- existing Linux applications in order to reduce the security tion.
    [Show full text]
  • Glen Or Glenda Empowering Users and Applications with Private Namespaces
    Glen or Glenda Empowering Users and Applications with Private Namespaces Eric Van Hensbergen IBM Research [email protected] Abstract in a network, and reference resources within a file system. Within each of these cate- gories names are evaluated in a specific con- Private name spaces were first introduced into text. Program variables have scope, database LINUX during the 2.5 kernel series. Their use indexes are evaluated within tables, networks has been limited due to name space manipu- machine names are valid within a particular lation being considered a privileged operation. domain, and file names provide a mapping to Giving users and applications the ability to cre- underlying resources within a particular name ate private name spaces as well as the ability to space. This paper is primarily concerned with mount and bind resources is the key to unlock- the evaluation and manipulation of names and ing the full potential of this technology. There name space contexts for file systems under the are serious performance, security and stability LINUX operating system. issues involved with user-controlled dynamic private name spaces in LINUX. This paper pro- File systems evolved from flat mappings of poses mechanisms and policies for maintain- names to multi-level mappings where each cat- ing system integrity while unlocking the power alog (or directory) provided a context for name of dynamic name spaces for normal users. It resolution. This design was carried further discusses relevant potential applications of this by MULTICS[1] with deep hierarchies of di- technology including its use with FILESYSTEM rectories including the concept of links be- IN USERSPACE[24], V9FS[8] (the LINUX port tween directories within the hierarchy[5].
    [Show full text]