jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-18 15:00:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove Debian packaging

Browse Source 
The packaging used for uploads to Debian is maintained on Debian
infrastructure, presently at
http://anonscm.debian.org/cgit/pkg-k5-afs/openafs.git .

The packaging repository for any given Debian openafs source
package will be listed in the Vcs-* fields in the package's
control file.

The version of the Debian packaging in the openafs repository
will almost always be out-of-date and is not used by Debian,
and the actual packaging used by Debian is easily available, so
there is no purpose in maintaining Debian packaging in the OpenAFS
source code repository.

Change-Id: I23011315ece011e32cdddd992c4f8a176e348c67
Reviewed-on: http://gerrit.openafs.org/11621
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
This commit is contained in:
Benjamin Kaduk 2014-12-04 17:00:04 -05:00 committed by Jeffrey Altman
parent a4dc1d8fc0
commit e34e0d149f
98 changed files with 0 additions and 11650 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
configure.ac
View File

@ -231,7 +231,6 @@ AC_OUTPUT([
src/lwp/Makefile
src/lwp/test/Makefile
src/opr/Makefile
src/packaging/Debian/changelog
src/packaging/MacOS/OpenAFS-debug.Description.plist
src/packaging/MacOS/OpenAFS-debug.Info.plist
src/packaging/MacOS/OpenAFS.Description.plist

5
src/packaging/Debian/.gitignore vendored
View File

@ -1,5 +0,0 @@
# After changing this file, please run
# git ls-files -i --exclude-standard
# to check that you haven't inadvertently ignored any tracked files.
/changelog

660
src/packaging/Debian/CellServDB
View File

@ -1,660 +0,0 @@
>grand.central.org #GCO Public CellServDB 17 Nov 2014
18.9.48.14 #grand.mit.edu
128.2.13.219 #grand-old-opry.central.org
>wu-wien.ac.at #University of Economics, Vienna, Austria
137.208.3.33 #goya.wu-wien.ac.at
137.208.7.57 #caravaggio.wu-wien.ac.at
137.208.8.14 #vermeer.wu-wien.ac.at
>hephy.at #hephy-vienna
193.170.243.10 #mowgli.oeaw.ac.at
193.170.243.12 #baloo.oeaw.ac.at
193.170.243.14 #akela.oeaw.ac.at
>cgv.tugraz.at #CGV cell
129.27.218.30 #phobos.cgv.tugraz.at
129.27.218.31 #deimos.cgv.tugraz.at
129.27.218.32 #trinculo.cgv.tugraz.at
>itp.tugraz.at #Institute of Theoretical and Computational Physics, TU Graz, Aus
129.27.161.7 #faepafs1.tu-graz.ac.at
129.27.161.15 #faepafs2.tu-graz.ac.at
129.27.161.114 #faepafs3.tu-graz.ac.at
>sums.math.mcgill.ca #Society of Undergraduate Mathematics Students of McGill Universi
132.216.24.122 #germain.sums.math.mcgill.ca
132.216.24.125 #turing.sums.math.mcgill.ca
>ualberta.ca #University of Alberta
129.128.1.131 #file13.ucs.ualberta.ca
129.128.98.17 #mystery.ucs.ualberta.ca
129.128.125.40 #drake.ucs.ualberta.ca
>cern.ch #European Laboratory for Particle Physics, Geneva
137.138.128.148 #afsdb1.cern.ch
137.138.246.50 #afsdb3.cern.ch
137.138.246.51 #afsdb2.cern.ch
>ams.cern.ch #AMS Experiment
137.138.188.185 #ams.cern.ch
137.138.199.58 #pcamsf4.cern.ch
>epfl.ch #Swiss Federal Institute of Technology at Lausanne
128.178.109.111 #kd1.epfl.ch
128.178.109.112 #kd2.epfl.ch
128.178.109.113 #kd3.epfl.ch
>ethz.ch #Swiss Federal Inst. of Tech. - Zurich, Switzerland
82.130.118.32 #afs-db-1.ethz.ch
>psi.ch #Paul Scherrer Institut - Villigen, Switzerland
129.129.190.140 #afs00.psi.ch
129.129.190.141 #afs01.psi.ch
129.129.190.142 #afs02.psi.ch
>extundo.com #Simon Josefsson's cell
195.42.214.241 #slipsten.extundo.com
>freedaemon.com #Free Daemon Consulting, Oklahoma City, OK, USA
66.210.104.254 #afs0.freedaemon.com
>membrain.com #membrain.com
66.93.118.125 #stormy
130.85.24.11 #weasel
130.85.24.13 #straykitten
>nilcons.com #nilcons.com
5.9.14.177 #files.nilcons.com
>sodre.cx #Sodre.cx
128.8.140.165 #greed.sodre.cx
>ruk.cuni.cz #Charles University Computer Centre, Prague, CR
195.113.0.36 #asterix.ruk.cuni.cz
195.113.0.37 #obelix.ruk.cuni.cz
195.113.0.40 #sal.ruk.cuni.cz
>ics.muni.cz #Masaryk university
147.251.3.11 #grond.ics.muni.cz
147.251.3.15 #nimloth.ics.muni.cz
147.251.3.19 #sirion.ics.muni.cz
>zcu.cz #University of West Bohemia, Czech Republic
147.228.10.18 #sauron.zcu.cz
147.228.52.10 #oknos.zcu.cz
147.228.52.17 #nic.zcu.cz
>desy.de #Deutsches Elektronen-Synchrotron
131.169.2.19 #afsdb2.desy.de
131.169.2.20 #afsdb3.desy.de
131.169.244.60 #solar00.desy.de
>naf.desy.de #National Analysis Facility at DESY
141.34.220.32 #tcsh1-vm1.naf.desy.de
141.34.230.33 #tcsh2-vm1.naf.desy.de
141.34.230.34 #tcsh3-vm1.naf.desy.de
>gppc.de #GPP Chemnitz mbH
213.187.92.33 #gpp1.gppc.de
213.187.92.34 #paulchen.gppc.de
213.187.92.35 #lotus.gppc.de
>cms.hu-berlin.de #Humboldt University Berlin
141.20.1.65 #commodus.cms.hu-berlin.de
141.20.1.66 #faustinus.cms.hu-berlin.de
141.20.1.67 #marcellus.cms.hu-berlin.de
>ifh.de #DESY Zeuthen
141.34.22.10 #romulus.ifh.de
141.34.22.11 #remus.ifh.de
141.34.22.29 #hekate.ifh.de
>integra-ev.de #INTEGRA e.V.
134.155.48.8 #afsdb2.integra-ev.de
134.155.48.63 #afsdb1.integra-ev.de
>lrz-muenchen.de #Leibniz Computing Centre, Germany
129.187.10.36 #afs1.lrz-muenchen.de
129.187.10.56 #afs3.lrz-muenchen.de
129.187.10.57 #afs2.lrz-muenchen.de
>ipp-garching.mpg.de #Institut fuer Plasmaphysik
130.183.9.5 #afs-db1.rzg.mpg.de
130.183.14.14 #afs-db3.bc.rzg.mpg.de
130.183.100.10 #afs-db2.aug.ipp-garching.mpg.de
>mpe.mpg.de #MPE cell
130.183.130.7 #irafs1.mpe-garching.mpg.de
130.183.134.20 #irafs2.mpe-garching.mpg.de
>nicsys.de #NICsys GbR
213.187.80.3 #attila.nicsys.de
>i1.informatik.rwth-aachen.de #Informatik I, RWTH Aachen
137.226.244.79 #remus.informatik.rwth-aachen.de
>combi.tfh-wildau.de #Philips Research Lab
194.95.50.106 #joda13.combi.tfh-wildau.de
>tu-berlin.de #TU Berlin
130.149.204.10 #afsc-pr-1.tubit.tu-berlin.de
130.149.204.11 #afsc-pr-2.tubit.tu-berlin.de
130.149.204.70 #afsc-ba-1.tubit.tu-berlin.de
>tu-bs.de #Technical University of Braunschweig, Germany
134.169.1.1 #rzafs1.rz.tu-bs.de
134.169.1.5 #rzafs2.rz.tu-bs.de
134.169.1.6 #rzafs3.rz.tu-bs.de
>tu-chemnitz.de #Technische Universitaet Chemnitz, Germany
134.109.2.1 #zuse.hrz.tu-chemnitz.de
134.109.2.2 #andrew.hrz.tu-chemnitz.de
134.109.2.15 #phoenix.hrz.tu-chemnitz.de
>e18.ph.tum.de #Experimental Physics, TU Munich, Germany
129.187.154.165 #dionysos.e18.physik.tu-muenchen.de
129.187.154.223 #hamlet.e18.physik.tu-muenchen.de
>physik.uni-bonn.de #Institute of Physics, University of Bonn, Germany
131.220.166.33 #afsdb1.physik.uni-bonn.de
131.220.166.34 #afsdb2.physik.uni-bonn.de
131.220.166.35 #afsdb3.physik.uni-bonn.de
>atlass01.physik.uni-bonn.de #Bonn ATLAS
131.220.165.43 #atlass01.physik.uni-bonn.de
>uni-freiburg.de #Albert-Ludwigs-Universitat Freiburg
132.230.6.237 #sv8.ruf.uni-freiburg.de
132.230.6.239 #sv10.ruf.uni-freiburg.de
>physik.uni-freiburg.de #Institute of Physics, University Freiburg, Germany
132.230.6.234 #afs1.ruf.uni-freiburg.de
132.230.6.235 #afs2.ruf.uni-freiburg.de
132.230.77.12 #sherlock.physik.uni-freiburg.de
>math.uni-hamburg.de #Department of Mathematics Uni Hamburg
134.100.223.3 #afs-core.math.uni-hamburg.de
134.100.223.6 #afs-core2.math.uni-hamburg.de
134.100.223.9 #afs-core3.math.uni-hamburg.de
>physnet.uni-hamburg.de #PHYSnet-Rechenzentrum university of hamburg
134.100.106.44 #afs-core.physnet.uni-hamburg.de
134.100.106.45 #afs-core2.physnet.uni-hamburg.de
134.100.106.47 #afs-core3.physnet.uni-hamburg.de
>mathi.uni-heidelberg.de #Uni Heidelberg (Mathematisches Institut)
129.206.26.241 #hactar.mathi.uni-heidelberg.de
>urz.uni-heidelberg.de #Uni Heidelberg (Rechenzentrum)
129.206.119.10 #afsdb.urz.uni-heidelberg.de
129.206.119.16 #afsdb1.urz.uni-heidelberg.de
129.206.119.17 #afsdb2.urz.uni-heidelberg.de
>ziti.uni-heidelberg.de #Institute of Computer Science at the University of Heidelberg
147.142.42.246 #mp-sun.ziti.uni-heidelberg.de
147.142.42.252 #mp-pizza.ziti.uni-heidelberg.de
>uni-hohenheim.de #University of Hohenheim
144.41.2.2 #rs13.serv.uni-hohenheim.de
144.41.2.3 #rs14.serv.uni-hohenheim.de
144.41.2.4 #rs15.serv.uni-hohenheim.de
>rz.uni-jena.de #Rechenzentrum University of Jena, Germany
141.35.2.180 #afs00.rz.uni-jena.de
141.35.2.181 #afs01.rz.uni-jena.de
141.35.2.182 #afs02.rz.uni-jena.de
>meteo.uni-koeln.de #Univ. of Cologne - Inst. for Geophysics & Meteorology
134.95.144.22 #afs1.meteo.uni-koeln.de
134.95.144.24 #afs2.meteo.uni-koeln.de
>rrz.uni-koeln.de #University of Cologne - Reg Comp Center
134.95.19.3 #afsdb1.rrz.uni-koeln.de
134.95.19.4 #afsdb2.rrz.uni-koeln.de
134.95.19.10 #lyra.rrz.uni-koeln.de
134.95.67.97 #afs.thp.uni-koeln.de
134.95.112.8 #ladon.rrz.uni-koeln.de
>urz.uni-magdeburg.de #Otto-von-Guericke-Universitaet, Magdeburg
141.44.7.6 #lem.urz.uni-magdeburg.de
141.44.8.14 #bowles.urz.uni-magdeburg.de
141.44.13.5 #strugazki.urz.uni-magdeburg.de
>physik.uni-mainz.de #institute of physics, university Mainz, Germany
134.93.130.93 #hardy.physik.uni-mainz.de
>uni-mannheim.de #Uni Mannheim (Rechenzentrum)
134.155.97.204 #afsdb1.uni-mannheim.de
134.155.97.205 #afsdb2.uni-mannheim.de
134.155.97.206 #afsdb3.uni-mannheim.de
>uni-paderborn.de #University of Paderborn, Germany
131.234.137.10 #afsdb1.uni-paderborn.de
131.234.137.11 #afsdb2.uni-paderborn.de
131.234.137.12 #afsdb3.uni-paderborn.de
>physik.uni-wuppertal.de #Physics department of Bergische Universität Wuppertal
132.195.104.3 #afs1.physik.uni-wuppertal.de
132.195.104.230 #afs2.physik.uni-wuppertal.de
>s-et.aau.dk #Aalborg Univ., The Student Society, Denmark
130.225.196.22 #afs.s-et.aau.dk
>ies.auc.dk #Aalborg Univ., Inst. of Electronic Systems, Denmark
130.225.51.73 #afsdb1.kom.auc.dk
130.225.51.74 #afsdb2.kom.auc.dk
130.225.51.85 #afsdb3.kom.auc.dk
>asu.edu #Arizona State University
129.219.10.69 #authen2.asu.edu
129.219.10.70 #authen1.asu.edu
129.219.10.72 #authen3.asu.edu
>hep.caltech.edu #Caltech High Energy Physics
131.215.116.20 #afs.hep.caltech.edu
>ugcs.caltech.edu #Caltech UGCS lab
131.215.176.65 #afs-c.ugcs.caltech.edu
131.215.176.67 #afs-a.ugcs.caltech.edu
131.215.176.68 #afs-b.ugcs.caltech.edu
>andrew.cmu.edu #Carnegie Mellon University - Computing Services Cell
128.2.10.2 #afsdb-01.andrew.cmu.edu
128.2.10.7 #afsdb-02.andrew.cmu.edu
128.2.10.11 #afsdb-03.andrew.cmu.edu
>mw.andrew.cmu.edu #Carnegie Mellon University - Middleware Test Cell
128.2.234.24 #null.andrew.cmu.edu
128.2.234.170 #mw-mgr.andrew.cmu.edu
>club.cc.cmu.edu #Carnegie Mellon University Computer Club
128.2.204.149 #barium.club.cc.cmu.edu
128.237.157.11 #sodium.club.cc.cmu.edu
128.237.157.13 #potassium.club.cc.cmu.edu
>chem.cmu.edu #Carnegie Mellon University - Chemistry Dept.
128.2.40.134 #afs.chem.cmu.edu
128.2.40.140 #afs2.chem.cmu.edu
>cs.cmu.edu #Carnegie Mellon University - School of Comp. Sci.
128.2.172.58 #date.srv.cs.cmu.edu
128.2.172.60 #fig.srv.cs.cmu.edu
128.2.200.97 #watermelon.srv.cs.cmu.edu
>ece.cmu.edu #Carnegie Mellon University - Elec. Comp. Eng. Dept.
128.2.129.7 #porok.ece.cmu.edu
128.2.129.8 #vicio.ece.cmu.edu
128.2.129.9 #e-xing.ece.cmu.edu
>scotch.ece.cmu.edu #CMU ECE CALCM research group
128.2.134.82 #lagavulin.ece.cmu.edu
>qatar.cmu.edu #Carnegie Mellon University - Qatar
86.36.46.6 #afs1.qatar.cmu.edu
86.36.46.7 #afs2.qatar.cmu.edu
>sbp.ri.cmu.edu #Carnegie Mellon University - Sensor Based Planning Lab
128.2.179.12 #nihao.sbp.ri.cmu.edu
128.2.179.113 #youtheman.sbp.ri.cmu.edu
>cnf.cornell.edu #CNF
128.253.198.9 #hole.cnf.cornell.edu
128.253.198.27 #smoke.cnf.cornell.edu
128.253.198.231 #mist.cnf.cornell.edu
>math.cornell.edu #Cornell Math Dept
128.84.234.12 #pooh.math.cornell.edu
128.84.234.16 #bernoulli.math.cornell.edu
128.84.234.162 #dyno.math.cornell.edu
>msc.cornell.edu #Cornell University Materials Science Center
128.84.231.242 #miranda.ccmr.cornell.edu
128.84.241.35 #co.ccmr.cornell.edu
128.84.249.78 #dax.ccmr.cornell.edu
>dbic.dartmouth.edu #Dartmouth Brain Imaging Center
129.170.30.143 #dbicafs1.dartmouth.edu
129.170.30.144 #dbicafs2.dartmouth.edu
129.170.30.145 #dbicafs3.dartmouth.edu
>northstar.dartmouth.edu #Dartmouth College Research Computing
129.170.16.22 #halley.dartmouth.edu
129.170.16.26 #andromeda.dartmouth.edu
129.170.16.43 #cygnusx1.dartmouth.edu
>cs.hm.edu #Department Computer Science Munich University Of Applied Science
129.187.208.31 #afs1.cs.hm.edu
>eecs.harvard.edu #Harvard - EECS
140.247.60.64 #lefkada.eecs.harvard.edu
140.247.60.83 #corfu.eecs.harvard.edu
>iastate.edu #Iowa State University
129.186.1.243 #afsdb-1.iastate.edu
129.186.6.243 #afsdb-2.iastate.edu
129.186.142.243 #afsdb-3.iastate.edu
>athena.mit.edu #MIT/Athena cell
18.3.48.11 #aether.mit.edu
18.9.48.11 #castor.mit.edu
18.9.48.12 #pollux.mit.edu
>csail.mit.edu #MIT Computer Science & Artificial Intelligence Lab
128.30.2.13 #titanic.csail.mit.edu
128.30.2.31 #vasa.csail.mit.edu
128.30.2.75 #maine.csail.mit.edu
>lns.mit.edu #MIT/LNS Cell
198.125.160.134 #afs2.lns.mit.edu.
198.125.160.217 #afsdbserv1.lns.mit.edu.
198.125.160.218 #afsdbserv2.lns.mit.edu.
>net.mit.edu #MIT/Network Group cell
18.7.62.60 #willy.mit.edu
18.9.48.15 #moby.mit.edu
18.9.48.16 #springer.mit.edu
>numenor.mit.edu #Project Numenor
18.243.2.49 #numenor.mit.edu
>sipb.mit.edu #MIT/SIPB cell
18.181.0.19 #reynelda.mit.edu
18.181.0.22 #rosebud.mit.edu
18.181.0.23 #ronald-ann.mit.edu
>msu.edu #Michigan State University Main Cell
35.9.7.10 #afsdb0.cl.msu.edu
>nd.edu #University of Notre Dame
129.74.223.17 #john.helios.nd.edu
129.74.223.33 #lizardo.helios.nd.edu
129.74.223.65 #buckaroo.helios.nd.edu
>crc.nd.edu #University of Notre Dame - Center for Research Computing
129.74.85.34 #afsdb1.crc.nd.edu
129.74.85.35 #afsdb2.crc.nd.edu
129.74.85.36 #afsdb3.crc.nd.edu
>pitt.edu #University of Pittsburgh
136.142.8.15 #afs09.srv.cis.pitt.edu
136.142.8.20 #afs10.srv.cis.pitt.edu
136.142.8.21 #afs11.srv.cis.pitt.edu
>cs.pitt.edu #University of Pittsburgh - Computer Science
136.142.22.5 #afs01.cs.pitt.edu
136.142.22.6 #afs02.cs.pitt.edu
136.142.22.7 #afs03.cs.pitt.edu
>psc.edu #PSC (Pittsburgh Supercomputing Center)
128.182.59.182 #shaggy.psc.edu
128.182.66.184 #velma.psc.edu
128.182.66.185 #daphne.psc.edu
>scoobydoo.psc.edu #PSC Test Cell
128.182.59.181 #scooby.psc.edu
>cede.psu.edu #Penn State - Center for Engr. Design & Entrepeneurship
146.186.218.10 #greenly.cede.psu.edu
146.186.218.60 #b50.cede.psu.edu
146.186.218.246 #stalin.cede.psu.edu
>rose-hulman.edu #Rose-Hulman Institute of Technology
137.112.7.11 #afs1.rose-hulman.edu
137.112.7.12 #afs2.rose-hulman.edu
137.112.7.13 #afs3.rose-hulman.edu
>cs.rose-hulman.edu #Rose-Hulman CS Department
137.112.40.10 #galaxy.cs.rose-hulman.edu
>rpi.edu #Rensselaer Polytechnic Institute
128.113.22.11 #saul.server.rpi.edu
128.113.22.12 #joab.server.rpi.edu
128.113.22.13 #korah.server.rpi.edu
128.113.22.14 #achan.server.rpi.edu
>hep.sc.edu #University of South Carolina, Dept. of Physics
129.252.78.77 #cpeven.physics.sc.edu
>cs.stanford.edu #Stanford University Computer Science Department
171.64.64.10 #cs-afs-1.Stanford.EDU
171.64.64.66 #cs-afs-2.stanford.edu
171.64.64.69 #cs-afs-3.stanford.edu
>ir.stanford.edu #Stanford University
171.64.7.222 #afsdb1.stanford.edu
171.64.7.234 #afsdb2.stanford.edu
171.64.7.246 #afsdb3.stanford.edu
>slac.stanford.edu #Stanford Linear Accelerator Center
134.79.18.25 #afsdb1.slac.stanford.edu
134.79.18.26 #afsdb2.slac.stanford.edu
134.79.18.27 #afsdb3.slac.stanford.edu
>physics.ucsb.edu #UC Santa Barbara, Physics Dept
128.111.18.161 #ledzeppelin.physics.ucsb.edu
>cats.ucsc.edu #University of California, Santa Cruz
128.114.123.8 #afs-prod-front-1.ucsc.edu
128.114.123.9 #afs-prod-front-2.ucsc.edu
128.114.123.10 #afs-prod-front-3.ucsc.edu
>ncsa.uiuc.edu #National Center for Supercomputing Applications at Illinois
141.142.192.66 #nile-vm.ncsa.uiuc.edu
141.142.192.143 #congo-vm.ncsa.uiuc.edu
141.142.192.144 #kaskaskia-vm.ncsa.uiuc.edu
>umbc.edu #University of Maryland, Baltimore County
130.85.24.23 #db2.afs.umbc.edu
130.85.24.87 #db3.afs.umbc.edu
130.85.24.101 #db1.afs.umbc.edu
>glue.umd.edu #University of Maryland - Project Glue
128.8.70.11 #olmec.umd.edu
128.8.236.4 #egypt.umd.edu
128.8.236.230 #babylon.umd.edu
>wam.umd.edu #University of Maryland Network WAM Project
128.8.70.9 #csc-srv.wam.umd.edu
128.8.236.5 #avw-srv.wam.umd.edu
128.8.236.231 #ptx-srv.wam.umd.edu
>umich.edu #University of Michigan - Campus
141.211.1.32 #fear.ifs.umich.edu
141.211.1.33 #surprise.ifs.umich.edu
141.211.1.34 #ruthless.ifs.umich.edu
>atlas.umich.edu #ATLAS group cell in physics at University of Michigan
141.211.43.102 #linat02.grid.umich.edu
141.211.43.103 #linat03.grid.umich.edu
141.211.43.104 #linat04.grid.umich.edu
>citi.umich.edu #University of Michigan - Center for Information Technology Integ
141.212.112.5 #babylon.citi.umich.edu
>isis.unc.edu #Univ. of NC at Chapel Hill - ITS
152.2.1.5 #db0.isis.unc.edu
152.2.1.6 #db1.isis.unc.edu
152.2.1.7 #db2.isis.unc.edu
>eng.utah.edu #University of Utah - Engineering
155.98.111.9 #lenny.eng.utah.edu
155.98.111.10 #carl.eng.utah.edu
>cs.uwm.edu #University of Wisconsin--Milwaukee
129.89.38.124 #solomons.cs.uwm.edu
>cs.wisc.edu #Univ. of Wisconsin-Madison, Computer Sciences Dept.
128.105.132.14 #timon.cs.wisc.edu
128.105.132.15 #pumbaa.cs.wisc.edu
128.105.132.16 #zazu.cs.wisc.edu
>engr.wisc.edu #University of Wisconsin-Madison, College of Engineering
144.92.13.14 #larry.cae.wisc.edu
144.92.13.15 #curly.cae.wisc.edu
144.92.13.16 #moe.cae.wisc.edu
>hep.wisc.edu #University of Wisconsin -- High Energy Physics
128.104.28.219 #anise.hep.wisc.edu
144.92.180.7 #rosemary.hep.wisc.edu
144.92.180.30 #fennel.hep.wisc.edu
>physics.wisc.edu #Univ. of Wisconsin-Madison, Physics Department
128.104.160.13 #kendra.physics.wisc.edu
128.104.160.14 #fray.physics.wisc.edu
128.104.160.15 #buffy.physics.wisc.edu
>ciemat.es #Ciemat, Madrid, Spain
130.206.11.42 #afsdb1.ciemat.es
130.206.11.217 #afsdb2.ciemat.es
130.206.11.247 #afsdb3.ciemat.es
>ifca.unican.es #Instituto de Fisica de Cantabria (IFCA), Santander, Spain
193.144.209.20 #gridwall.ifca.unican.es
>ific.uv.es #Instituto de Fisica Corpuscular, Valencia, Spain
147.156.163.11 #alpha.ific.uv.es
>alteholz.eu #alteholz.eu
78.47.192.125 #krb1eu.afs.alteholz.net
>in2p3.fr #IN2P3
134.158.104.11 #ccafsdb01.in2p3.fr
134.158.104.12 #ccafsdb02.in2p3.fr
134.158.104.13 #ccafsdb03.in2p3.fr
>mcc.ac.gb #University of Manchester
130.88.203.41 #nevis.mc.man.ac.uk
130.88.203.144 #eryri.mc.man.ac.uk
130.88.203.145 #scafell.mc.man.ac.uk
>anl.gov #Argonne National Laboratory
146.137.96.33 #arteus.it.anl.gov
146.137.162.88 #agamemnon.it.anl.gov
146.137.194.80 #antenor.it.anl.gov
>rhic.bnl.gov #Relativistic Heavy Ion Collider
130.199.6.51 #rafs03.rcf.bnl.gov
130.199.6.52 #rafs02.rcf.bnl.gov
130.199.6.69 #rafs01.rcf.bnl.gov
>usatlas.bnl.gov #US Atlas Tier 1 Facility at BNL
130.199.48.32 #aafs01.usatlas.bnl.gov
130.199.48.33 #aafs02.usatlas.bnl.gov
130.199.48.34 #aafs03.usatlas.bnl.gov
>fnal.gov #Fermi National Acclerator Laboratory
131.225.68.1 #fsus01.fnal.gov
131.225.68.4 #fsus03.fnal.gov
131.225.68.14 #fsus04.fnal.gov
>jpl.nasa.gov #Jet Propulsion Laboratory
137.78.160.21 #afsdb08.jpl.nasa.gov
137.78.160.22 #afsdb09.jpl.nasa.gov
137.78.160.23 #afsdb10.jpl.nasa.gov
>doe.atomki.hu #Institute of Nuclear Research (MTA ATOMKI), Debrecen, Hungary
193.6.179.31 #afs.doe.atomki.hu
>bme.hu #Budapest University of Technology and Economics
152.66.241.6 #afs.iit.bme.hu
>kfki.hu #Wigner Research Centre for Physics - Budapest, Hungary
148.6.2.109 #afs0.kfki.hu
>dev.ru.is #Reykjavik University
130.208.209.37 #afsdb1.dev.ru.is
130.208.209.39 #afsdb2.dev.ru.is
130.208.209.40 #afsdb3.dev.ru.is
>caspur.it #CASPUR Inter-University Computing Consortium, Rome
193.204.5.45 #pomodoro.caspur.it
193.204.5.46 #banana.caspur.it
193.204.5.50 #maslo.caspur.it
>enea.it #ENEA New Tech. Energy & Environment Agency, Italy
192.107.54.5 #aixfs.frascati.enea.it
192.107.54.11 #rs2ced.frascati.enea.it
192.107.54.12 #43p.frascati.enea.it
>fusione.it #Assoz. FUSIONE/Euratom, ENEA, Frascati-Italy
192.107.90.2 #fusafs1.frascati.enea.it
192.107.90.3 #fusafs2.frascati.enea.it
192.107.90.4 #fusafs3.frascati.enea.it
>icemb.it #ICEMB, Universita' La Sapienza - Rome - Italy
193.204.6.130 #icembfs.caspur.it
>ictp.it #The Abdus Salam International Centre for Theoretical Physics (IC
140.105.34.7 #afsdb1.ictp.it
140.105.34.8 #afsdb2.ictp.it
>infn.it #Istituto Nazionale di Fisica Nucleare (INFN), Italia
131.154.1.7 #afscnaf.infn.it
141.108.26.75 #afsrm1.roma1.infn.it
192.84.134.75 #afsna.na.infn.it
>ba.infn.it #INFN, Sezione di Bari
193.206.185.235 #baafsserver.ba.infn.it
193.206.185.236 #debsrv.ba.infn.it
>kloe.infn.it #INFN, KLOE experiment at Laboratori di Frascati
192.135.25.111 #kloeafs1.lnf.infn.it
192.135.25.112 #kloeafs2.lnf.infn.it
>le.infn.it #INFN, Sezione di Lecce
192.84.152.40 #afs01.le.infn.it
192.84.152.148 #afs02.le.infn.it
>lnf.infn.it #INFN, Laboratori Nazionali di Frascati
193.206.84.121 #afs1.lnf.infn.it
193.206.84.122 #afs2.lnf.infn.it
193.206.84.123 #afs3.lnf.infn.it
>lngs.infn.it #INFN, Laboratori Nazionali del Gran Sasso
192.84.135.21 #afs1.lngs.infn.it
192.84.135.133 #afs2.lngs.infn.it
>pi.infn.it #INFN, Sezione di Pisa
192.84.133.50 #aix1.pi.infn.it
212.189.152.6 #afs1.pi.infn.it
212.189.152.7 #afs2.pi.infn.it
>roma3.infn.it #Istituto Nazionale di Fisica Nucleare (INFN), Italia
193.205.159.17 #afsrm3.roma3.infn.it
>psm.it #Progetto San Marco, Universita' di Roma-1
151.100.1.65 #atlante.psm.uniroma1.it
>tgrid.it #CASPUR-CILEA-CINECA Grid Cell
193.204.5.33 #cccgrid.caspur.it
>math.unifi.it #math.unifi.it
150.217.34.182 #xeno.math.unifi.it
>ing.uniroma1.it #Universita' La Sapienza, Fac. Ingeneria
151.100.85.253 #alfa.ing.uniroma1.it
>dia.uniroma3.it #University Roma Tre - DIA
193.204.161.67 #srv.dia.uniroma3.it
193.204.161.79 #aux.dia.uniroma3.it
193.204.161.118 #afs.dia.uniroma3.it
>vn.uniroma3.it #University Roma Tre, area Vasca Navale
193.205.219.59 #alfa2.dia.uniroma3.it
193.205.219.60 #beta2.dia.uniroma3.it
193.205.219.61 #gamma2.dia.uniroma3.it
>italia #Italian public AFS cell
193.204.5.9 #afs.caspur.it
>cmf.nrl.navy.mil #Naval Research Laboratory - Center for Computational Science
134.207.12.68 #picard.cmf.nrl.navy.mil
134.207.12.69 #riker.cmf.nrl.navy.mil
134.207.12.70 #kirk.cmf.nrl.navy.mil
>lcp.nrl.navy.mil #Naval Research Lab - Lab for Computational Physics
132.250.114.2 #afs1.lcp.nrl.navy.mil
132.250.114.4 #afs2.lcp.nrl.navy.mil
132.250.114.6 #afs3.lcp.nrl.navy.mil
>nucleares.unam.mx #Instituto de Ciencias Nucleares, UNAM, Mexico
132.248.29.50 #nahualli.nucleares.unam.mx
>crossproduct.net #crossproduct.net
207.114.88.173 #geodesic.crossproduct.net
>epitech.net #EPITECH, France
163.5.255.41 #afs-db-1.epitech.net
163.5.255.42 #afs-db-2.epitech.net
>es.net #Energy Sciences Net
198.128.3.21 #fs1.es.net
198.128.3.22 #fs2.es.net
198.128.3.23 #fs3.es.net
>gorlaeus.net #Gorlaeus Laboratories, Leiden University
132.229.170.27 #fwncisafs1.gorlaeus.net
>laroia.net #Laroia Networks
66.66.102.254 #supercore.laroia.net
>sinenomine.net #Sine Nomine Associates
72.73.25.18 #afsdb2.sinenomine.net
72.73.30.74 #afsdb3.sinenomine.net
199.167.73.142 #afsdb1.sinenomine.net
>slackers.net #The Slackers' Network
199.4.150.159 #alexandria.slackers.net
>tproa.net #The People's Republic of Ames
204.11.35.83 #service-3.tproa.net
204.11.35.84 #service-4.tproa.net
204.11.35.85 #service-5.tproa.net
>interdose.net #Interdose Ltd. & Co. KG, Germany
80.190.171.42 #bfd9000.tow5.interdose.net
80.190.171.43 #bfd9001.tow5.interdose.net
>nikhef.nl #The Dutch National Institute for High Energy Physics
192.16.185.26 #afs1.nikhef.nl
192.16.185.27 #afs2.nikhef.nl
>acm-csuf.org #California State Univerisity Fullerton ACM
137.151.29.193 #afs1.acm-csuf.org
>adrake.org #adrake.org
128.2.98.241 #afs.adrake.org
>bazquux.org #Baz Quux Organization
66.207.142.196 #baxquux.org
>coed.org #Adam Pennington's Cell
66.93.61.184 #vice1.coed.org
128.237.157.35 #vice3.coed.org
>dementia.org #Dementia Unlimited (old)
128.2.13.209 #dedlock.dementix.org
128.2.234.204 #vorkana.dementix.org
128.2.235.26 #meredith.dementix.org
>dementix.org #Dementia Unlimited
128.2.13.209 #dedlock.dementix.org
128.2.234.204 #vorkana.dementix.org
128.2.235.26 #meredith.dementix.org
>idahofuturetruck.org #University of Idaho hybrid vehicle development
12.18.238.210 #dsle210.fsr.net
>afs.ietfng.org #ietfng.org
67.62.51.95 #a.afs.ietfng.org
>jeaton.org #jeaton.org (Jeffrey Eaton, jeaton@jeaton.org)
128.2.234.89 #jeaton-org-01.jeaton.org
128.2.234.92 #jeaton-org-02.jeaton.org
>mrph.org #Mrph
66.207.133.1 #sanber.mrph.org
128.2.99.209 #hernandarias.mrph.org
>mstacm.org #Missouri Science & Technology - ACM
131.151.249.193 #acm.mst.edu
>nomh.org #nomh.org
204.29.154.12 #iota.nomh.org
204.29.154.32 #adversity.xi.nomh.org
>oc7.org #The OC7 Project
128.2.122.140 #knife.oc7.org
207.22.77.170 #spoon.oc7.org
>pfriedma.org #pfriedma.org
72.95.215.18 #vice.pfriedma.org
>riscpkg.org #The RISC OS Packaging Project
83.104.175.10 #delenn.riscpkg.org
>kth.se #Royal Institute of Technology, Stockholm, Sweden
130.237.32.145 #sonen.e.kth.se
130.237.48.7 #anden.e.kth.se
130.237.48.244 #fadern.e.kth.se
>ict.kth.se #Royal Institute of Technology, Information and Communication tec
130.237.216.11 #afsdb1.ict.kth.se
130.237.216.12 #afsdb2.ict.kth.se
130.237.216.13 #afsdb3.ict.kth.se
>isk.kth.se #Royal Institute of Technology, ISK
130.237.216.17 #afsdb1.isk.kth.se
130.237.216.82 #afsdb2.isk.kth.se
130.237.216.83 #afsdb3.isk.kth.se
>it.kth.se #Royal Institute of Technology, Teleinformatics, Kista
130.237.216.14 #afsdb1.it.kth.se
130.237.216.15 #afsdb2.it.kth.se
130.237.216.16 #afsdb3.it.kth.se
>md.kth.se #Royal Institute of Technology, MMK
130.237.57.21 #euler.md.kth.se
130.237.57.68 #trinity.md.kth.se
130.237.57.72 #morpheus.md.kth.se
>mech.kth.se #Royal Institute of Technology, MECH
130.237.233.142 #matterhorn.mech.kth.se
130.237.233.143 #castor.mech.kth.se
130.237.233.144 #pollux.mech.kth.se
>nada.kth.se #Royal Institute of Technology, NADA
130.237.222.20 #kosmos.nada.kth.se
130.237.223.12 #sputnik.nada.kth.se
130.237.224.78 #mir.nada.kth.se
130.237.227.23 #gagarin.nada.kth.se
130.237.228.28 #laika.nada.kth.se
>pdc.kth.se #Royal Institute of Technology, PDC
130.237.232.29 #crab.pdc.kth.se
130.237.232.112 #anna.pdc.kth.se
130.237.232.114 #hokkigai.pdc.kth.se
>stacken.kth.se #Stacken Computer Club
130.237.234.3 #milko.stacken.kth.se
130.237.234.43 #hot.stacken.kth.se
130.237.234.101 #fishburger.stacken.kth.se
>syd.kth.se #Royal Institute of Technology, KTH-Syd
130.237.83.23 #afs.haninge.kth.se
>physto.se #Physics department Stockholm University
130.237.205.36 #sysafs1.physto.se
130.237.205.72 #sysafs2.physto.se
>sanchin.se #Sanchin Consulting AB, Sweden
192.195.148.10 #sesan.sanchin.se
>su.se #Stockholm University
130.237.162.81 #afsdb1.su.se
130.237.162.82 #afsdb2.su.se
130.237.162.230 #afsdb3.su.se
>f9.ijs.si #F9, Jozef Stefan Institue
194.249.156.1 #brenta.ijs.si
>p-ng.si #University of Nova Gorica
193.2.120.2 #solkan.p-ng.si
193.2.120.9 #sabotin.p-ng.si
>ihep.su #Institute for High-Energy Physics
194.190.165.201 #fs0001.ihep.su
194.190.165.202 #fs0002.ihep.su
>hep-ex.physics.metu.edu.tr #METU Department of Physics, Experimental HEP group, Ankara/Turke
144.122.31.131 #neutrino.physics.metu.edu.tr
>phy.bris.ac.uk #Bristol University - physics
137.222.74.18 #zen.phy.bris.ac.uk
>inf.ed.ac.uk #School of Informatics, University of Edinburgh
129.215.64.16 #afsdb0.inf.ed.ac.uk
129.215.64.17 #afsdb1.inf.ed.ac.uk
129.215.64.18 #afsdb2.inf.ed.ac.uk
>phas.gla.ac.uk #Univeristy of Glasgow Physics And Astronomy
194.36.1.19 #afsdb1.phas.gla.ac.uk
194.36.1.27 #afsdb3.phas.gla.ac.uk
194.36.1.33 #afsdb2.phas.gla.ac.uk
>ic.ac.uk #Imperial College London
155.198.63.148 #icafs2.cc.ic.ac.uk
155.198.63.149 #icafs1.cc.ic.ac.uk
>hep.man.ac.uk #Manchester HEP
194.36.2.3 #afs1.hep.man.ac.uk
194.36.2.4 #afs2.hep.man.ac.uk
194.36.2.5 #afs3.hep.man.ac.uk
>tlabs.ac.za #iThemba LABS Cell
196.24.232.1 #afs01.tlabs.ac.za
196.24.232.2 #afs02.tlabs.ac.za
196.24.232.3 #afs03.tlabs.ac.za

26
src/packaging/Debian/ConfigUtils.pm
View File

@ -1,26 +0,0 @@
# This is -*- perl -*-
package Debian::OpenAFS::ConfigUtils;
use strict;
use vars qw( @ISA @EXPORT @unwinds);
@ISA = qw(Exporter);
require Exporter;
@EXPORT = qw(@unwinds run unwind);
sub run ($) {
print join(' ', @_);
print "\n";
system (@_) == 0
or die "Failed: $?\n";
}
# This subroutine takes a command to run in case of failure. After
# each succesful step, this routine should be run with a command to
# undo the successful step.
sub unwind($) {
push @unwinds, $_[0];
}
1;

170
src/packaging/Debian/README.Debian
View File

@ -1,170 +0,0 @@
OpenAFS for Debian
Introduction
For an OpenAFS client system, install openafs-client and a kernel
module. See README.modules for information on how to build the kernel
module for your system. Then, read /etc/openafs/afs.conf to understand
the client configuration options. The openafs-client package will
attempt to guess at a good cache configuration based on the size of your
cache, but you may want to tune it further. There are also other
options configured in that file you may want to consider.
FAM does not work correctly with AFS except for directories that are
world-readable since it does not run in the user's security context and
therefore doesn't have the user's AFS tokens. If you are using FAM,
you'll encounter errors from file managers such as Nautilus that use it
if you browse restricted AFS directories. Instead of FAM, install
gamin, which runs in the user's security context and works correctly
with AFS.
For information on how to set up an OpenAFS server, read README.servers.
You will want the openafs-fileserver package for a file server and,
additionally, the openafs-dbserver package for a database server.
Documentation
For the complete OpenAFS manual, install openafs-doc. This is the same
documentation as found at <http://www.openafs.org/>, and is
unfortunately outdated in several respects, but it's the best that we
have at present.
If want to set up a new cell, read README.servers and then look at the
example session in configuration-transcript.txt.gz in this directory.
The procedure outlined in these two files is much simpler and more
secure than the one in the OpenAFS documentation, but the OpenAFS
documentation provides useful background.
Build Options
The OpenAFS file server has been built with --enable-demand-attach-fs,
which enables a new method of handling volume attachment. Volumes will
be attached only when needed, and the file server will persist state to
disk when shutting down for faster restarts. This file server mode is
experimental and should not yet be used for production data. Please
report any bugs you encounter.
The OpenAFS servers have been built with --enable-supergroups, which
permits nesting of PTS groups. Be aware that the PT database created by
these packages is not compatible with servers not built with
--enable-supergroups if nested PTS groups are used. In other words, if
you need the openafs-dbserver package to interoperate with ptservers
that aren't built with this option, don't use this capability.
The OpenAFS client and kernel module have been built with
--enable-disconnected, which enables experimental support for
disconnected operations. This support is still experimental and known
to have problems, but should not interfere with normal use of AFS. If
you want to experiment with it, see fs help discon.
Changes Relative to Stock OpenAFS
Long-time AFS users may be confused by the directory layout. The files
that normally go in /usr/vice/etc go in /etc/openafs. The cache should
be mounted on /var/cache/openafs. The server files have been moved
around even more; see README.servers for the details.
The OpenAFS kernel module is named openafs, not libafs, to better match
normal Linux kernel module naming standards. The Debian source package
only builds one kernel module that matches the kernel source tree it is
built against and does not attempt to build separate SMP and non-SMP
modules against the same tree. Doing so does not work on all platforms.
To distinguish between an SMP and a non-SMP kernel module package, use
--append_to_version; see README.modules for more information.
The AFS up utility is installed as afs-up, since the standard name is
rather generic.
The libopenafs-dev package only includes static libraries and there are
no shared library packages. The shared libraries built by AFS are not
compatible with Debian policy. They do not have a stable ABI or an
appropriate SONAME.
kaserver is not included. New AFS cells should use Kerberos v5 rather
than the old K4-based kaserver KDC.
Debugging and Bug Reporting
The current OpenAFS installation process installs fileserver and
volserver unstripped, since backtraces and other debugging information
for those binaries are necessary to track down file server problems.
For the Debian packages, the fileserver and volserver binaries in the
openafs-fileserver package are stripped, but the debugging information
is available in the openafs-dbg package, which can be installed
separately. If it is installed, gdb will find that debugging
information automatically.
Eventually the openafs-dbg package will contain debugging information
for all OpenAFS binaries.
When reporting a bug in the OpenAFS client, please include your exact
kernel version and architecture (reportbug will do this for you). Also,
if the client caused a kernel oops or BUG, be sure to include the
complete kernel output, including the lines before the oops. That's
where the OpenAFS error message, if any, will be.
When reporting a bug in the OpenAFS file server, please include
backtrace information from a core dump, if any. If the file server is
deadlocked, you can capture a core dump using the gcore script that
comes with the gdb package. The file server is threaded, so use the
command "thread apply all backtrace" in gdb to get a complete backtrace.
It's also often useful to have the output of rxdebug <server> 7000 at
the time of the problem and the FileLog from the file server. You can
increase the logging level of the file server with kill -TSTP (and reset
it to 0 with kill -HUP).
You can report any bug in OpenAFS against the Debian package with
reportbug and the OpenAFS package maintainers will forward the bug
upstream as necessary. If you do want to report a bug directly
upstream, see http://www.openafs.org/ for bug reporting instructions.
PAM Authentication
Any new OpenAFS cell is strongly encouraged to use Kerberos v5 for
authentication. If you want PAM to automatically obtain AFS credentials
and you are using Kerberos v5, you will want to install the libpam-krb5
and libpam-afs-session packages and then put something like the
following in /etc/pam.d/common-auth:
auth [success=ok default=1] pam_krb5.so ignore_root
auth [default=done] pam_afs_session.so
auth required pam_unix.so nullok_secure try_first_pass
and something like the following in /etc/pam.d/common-session:
session optional pam_krb5.so ignore_root
session optional pam_afs_session.so
session required pam_unix.so
You'll probably also want the following in /etc/pam.d/common-account:
account required pam_krb5.so ignore_root
account required pam_unix.so
There are, of course, many variations depending on what different
mechanism you want to use and how you want to handle fallbacks.
If you are still using Kerberos v4 and the OpenAFS kaserver (or a KDC
that understands the same protocol) for authentication, you can instead
use the libpam-openafs-kaserver package and a configuration like:
auth sufficient pam_afs.so ignore_root
auth required pam_unix.so nullok_secure try_first_pass
in /etc/pam.d/common-auth and:
session optional pam_afs.so
session required pam_unix.so
in /etc/pam.d/common-session. Use pam_afs.krb.so instead of pam_afs.so
if you also want the PAM module to acquire a ticket cache for you. If
using this configuration with sshd, you may need to disable privilege
separation to get everything working properly. I've had mixed results
with that. Obviously, converting to Kerberos v5 authentication is
strongly preferred.
If you are using the kaserver as your KDC, you may also want to install
the openafs-kpasswd package to get the administrative utilities for
managing those Kerberos accounts.
-- Russ Allbery <rra@debian.org>, Tue, 6 Apr 2010 15:04:42 -0700

112
src/packaging/Debian/README.modules
View File

@ -1,112 +0,0 @@
Building Kernel Modules
Introduction
The easiest way to get AFS modules is to install prebuilt modules. For
example, if you are running kernel 2.6.26-2-686, you might try:
apt-get install openafs-modules-2.6.26-2-686
Pre-built modules are not provided with Debian (building and maintaining
them in Debian proper poses too many problems), but many organizations
that use OpenAFS build their own and provide them locally.
If this doesn't work, you will need to build your own modules. There
are three methods for doing this.
When following any of these methods, be aware that the Debian package
creates a module named openafs, not libafs as is used by upstream. It
also prefers not to add the .mp extension for modules built for SMP
kernels; the indication of whether the module is for an SMP kernel
should go into the package name via something like --append_to_version,
not into the file name of the module.
DKMS
DKMS is relatively new and untested compared to the other mechanisms for
building kernel modules, but if it works for you, it's the easiest.
DKMS stands for Dynamic Kernel Module Support. It provides
infrastructure that will automatically rebuild kernel modules when the
source package or the kernel has been upgraded.
To build OpenAFS kernel modules via DKMS, just install the
openafs-modules-dkms package. This depends on DKMS and will install it
as well. The OpenAFS kernel modules should then be built automatically
and will be installed under updates/dkms in the module tree for your
kernel.
module-assistant
This method is the best method for manually building kernel modules for
kernels that come with Debian, since module-assistant knows how to get
the right header files to build modules for your currently running
kernel. Generally, all you should have to do is:
apt-get install module-assistant
module-assistant auto-install openafs
This combines all of the following steps, taking the defaults. If you
want to do it more step-by-step, first prepare the kernel headers and
install openafs-modules-source with:
apt-get install module-assistant
module-assistant prepare openafs-modules
If you want to build modules for a different kernel than your currently
running one, pass the -l flag to module-assistant. See the man page.
module-assistant may be able to find the right packages itself or it may
tell you to install particular packages. Once you've finished with
that, build the module with:
module-assistant auto-build openafs-modules
You may prefer to pass module-assistant the -t flag to get more
conventional output. If everything works correctly, the openafs-modules
deb should be created in /usr/src. You can use dpkg -i to install it.
module-assistant will take care of naming the openafs-modules package
correctly so that it matches the name of the kernel-image package and
installs its modules into the correct directory.
make-kpkg
This method may work better than module-assistant if you're also
building your own kernel rather than using the pre-packaged Debian one.
Install a kernel source package and untar it in /usr/src. Then, install
openafs-modules-source.
apt-get install openafs-modules-source
Next, unpack openafs-modules-source:
cd /usr/src
tar xzf openafs.tar.gz
Now, change into your kernel source tree. You should then create a
.config file; the easiest way to do this is to run make menuconfig or to
copy in a kernel configuration from the same version of the kernel.
Debian kernel packages store a copy of their kernel configuration in
/boot/config.version_number.
The kernel configuration needs to be identical to the configuration that
produced the kernel that you're using. Ideally, you would build the
kernel image you're going to use with make-kpkg kernel_image and install
that along with the module image, although as long as the configuration
is identical, you may be able to get away with using a pre-built kernel.
(A better approach, if you're using pre-built kernels, may be to use
module-assistant as described above.)
Finally, build the modules:
make-kpkg modules_image
You may need to use the --append_to_version switch to add version
suffixes like -686 or -smp to match your kernel and install the OpenAFS
module into a directory like /lib/modules/version-686. Be aware that
the Debian OpenAFS packages build either a regular module or an SMP
module, not both, so the generated package will only work with a kernel
with the same SMP configuration.
An openafs-modules deb should be created in /usr/src. Use dpkg -i to
install this package.

403
src/packaging/Debian/README.servers
View File

@ -1,403 +0,0 @@
Setting up a Debian OpenAFS Server
Introduction
This document describes how to set up an OpenAFS server using the Debian
packages. If you are not already familiar with the basic concepts of
OpenAFS, you should review the documentation at:
http://docs.openafs.org/
particularly the AFS Administrator's Guide. This documentation is
somewhat out of date (it doesn't talk about how to use a Kerberos v5 KDC
instead of the AFS kaserver, for example), but it's a good introduction
to the basic concepts and servers you will need to run.
The Debian OpenAFS packages follow the FHS and therefore use different
paths than the standard AFS documentation or the paths that experienced
AFS administrators may be used to. In the first column below are the
traditional paths, and in the second column, the Debian paths:
/usr/afs/etc /etc/openafs/server
/usr/afs/local /var/lib/openafs/local
/usr/afs/db /var/lib/openafs/db
/usr/afs/logs /var/log/openafs
/usr/afs/bin /usr/lib/openafs
/usr/vice/etc /etc/openafs
The AFS kaserver (a Kerberos v4 KDC) is not packaged for Debian. Any
new OpenAFS installation should use Kerberos v5 for authentication in
conjunction with either the tools packaged in the openafs-krb5 package
or the Heimdal KDC. When setting up a new cell, you should therefore
not set up a kaserver as described in the AFS Administrator's Guide, and
you will need to follow a slightly different method of setting the cell
key.
Creating a New Cell
For documentation on adding a server to an existing cell, see below.
These instructions assume that you are using MIT Kerberos and the
openafs-krb5 package. If you are using Heimdal instead, some of the
steps will be slightly different (Heimdal can write the AFS KeyFile
directly, for example, so you don't have to use asetkey). The
afs-newcell and afs-rootvol scripts are the same, however.
/usr/share/doc/openafs-dbserver/configuration-transcript.txt.gz has a
transcript of the results of these directions, which you may want to
follow along with as you do this.
1. If you do not already have a Kerberos KDC (Key Distribution Center,
the daemon that handles Kerberos authentication) configured, do so.
You can run the KDC on the same system as your OpenAFS db server,
although if you plan on using Kerberos for other things, you may
eventually want to use separate systems. If you do not have a
Kerberos realm set up already, you can do so in Debian with:
apt-get install krb5-admin-server
krb5_newrealm
This will install a KDC and kadmind server (the server that handles
password changes and account creations) on the local system. Please
be aware that the security of everything that uses Kerberos for
authentication, including AFS, depends on the security of the KDC.
The name of your Kerberos realm should, for various reasons, be in
all uppercase and be a domain name that you control, although
neither is technically required.
2. It is traditional (and recommended) in AFS (and for Kerberos) to
give administrators two separate Kerberos principals, one regular
principal to use for regular purposes and a separate admin principal
to use for privileged actions. This is similar to the distinction
between a regular user and the root user in Unix, except that
everyone can have their own separate root identity. Kerberos
recommends username/admin as the admin principal for username, and
this will work for AFS as well.
If you have not already created such an admin principal for yourself
in your Kerberos realm, do so now (using kadmin.local on your KDC,
unless you have a local method that you prefer). Also create a
regular (non-admin) principal for yourself if you have not already;
this is the identity that you'll use for regular operations, like
storing files or reading mail. To do this with kadmin.local, run
that program and then run the commands:
addprinc username/admin
addprinc username
at the kadmin prompt. You'll be prompted for passwords for both
accounts.
If the KDC is not on the same system that the OpenAFS db server will
be on, you will also need to give your admin principal the rights to
download the afs keytab in /etc/krb5kdc/kadm5.acl by adding a lines
like:
username/admin@REALM *
where REALM is your Kerberos realm and username/admin is the admin
principal that you created. That line gives you full admin access
to the Kerberos v5 realm. You can be more restrictive if you want;
see the kadmind man page for the syntax.
3. Install the OpenAFS db server package on an appropriate system with:
apt-get install openafs-dbserver openafs-krb5
The openafs-krb5 package will be used to create the AFS KeyFile.
As part of this installation, you will need to configure
openafs-client with the cell you are creating as the local cell name
and the server on which you're working as the db server. This name
is technically arbitrary but should, for various reasons, be a valid
domain name that you control; unlike Kerberos realms, it should be
in all lowercase. Enter the name of the local system when prompted
for the names of your OpenAFS db servers. Don't start the client;
that will happen below. For right now, say that you don't want it
to start at boot. You can change that later with dpkg-reconfigure
openafs-client.
If you have already installed openafs-client and configured it for
some other cell, you do need to configure it to point to your new
cell for these instructions to work. Stop the AFS client on the
system with /etc/init.d/openafs-client stop and then run:
dpkg-reconfigure openafs-client
pointing it to the new cell you're about to create instead.
Remember, your cell name should be in lowercase. If you have had to
do this several times, double-check /etc/openafs/CellServDB when
you're done and make sure that there is only one entry for your new
cell at the top of that file and that it lists the correct IP
address for your new db server.
In order to complete the AFS installation, you will also need a
working AFS client installed on that system, which means that you
need to install an OpenAFS kernel module. Please see:
/usr/share/doc/openafs-client/README.modules
for information on how to do that.
4. Create an AFS principal in Kerberos. This is the AFS service
principal, used by clients to authenticate to AFS and for AFS
servers to authenticate to each other. It *must* be a DES key; AFS
does not support any other encryption type. Run kadmin.local on
your KDC and then, at the kadmin.local prompt, run:
addprinc -randkey -e des-cbc-crc:v4 afs
If your Kerberos realm name does not match your AFS cell name (if,
for instance, you have one Kerberos realm with multiple AFS cells),
use "afs/cell.name" as the name of the principal above instead of
just "afs", where cell.name is the name of your new AFS cell.
5. On the db server, download this key into a keytab. If this is the
same system as the KDC, you can use kadmin.local again. If not, you
should use kadmin (make sure that krb5-user is installed), and you
may need to pass -p username/admin to kadmin to tell it what
principal to authenticate as. Whichever way you get into kadmin,
run:
ktadd -k /tmp/afs.keytab -e des-cbc-crc:v4 afs
(or afs/cell.name if you used that instead). In the message that
results, note the kvno number reported, since you'll need it later
(it will normally be 3).
Don't forget the -e des-cbc-crc:v4 to force the afs key to be DES.
You can verify this with:
getprinc afs
and checking to be sure that the only key listed is a DES key. If
there are multiple keys listed, delprinc the afs principal, delete
the /tmp/afs.keytab file, and then start over with addprinc, making
sure not to forget the -e option.
6. Create the AFS KeyFile with:
asetkey add <kvno> /tmp/afs.keytab afs
(or afs/cell.name if you used that instead). <kvno> should be
replaced by the kvno number reported by kadmin. This tells AFS the
Kerberos key that it should use, making it match the key in the
Kerberos KDC.
7. If the name of your Kerberos realm does not match the name of your
AFS cell, tell AFS what Kerberos realm to use with:
echo REALM > /etc/openafs/server/krb.conf
where REALM is the name of your Kerberos realm. If your AFS cell
and Kerberos realm have the same name, this is unnecessary.
8. Create some space to use for AFS volumes. You can set up a separate
AFS file server on a different system from the Kerberos KDC and AFS
db server, and for a larger cell you will want to do so, but when
getting started you can make the db server a file server as well.
For a production cell, you will want to create a separate partition
devoted to AFS and mount it as /vicepa (and may want to make
multiple partitions mounted as /vicepb, /vicepc, etc.), but for
testing purposes, you can use the commands below to create a
zero-filled file, create a file system in it, and then mount it:
dd if=/dev/zero of=/var/lib/openafs/vicepa bs=1024k count=32
mke2fs /var/lib/openafs/vicepa
mkdir /vicepa
mount -oloop /var/lib/openafs/vicepa /vicepa
mke2fs will ask you if you're sure you want to create a file system
on a non-block device; say yes.
9. Run afs-newcell. This will prompt you to be sure that the above
steps have been complete and will ask you for the Kerberos principal
to use for AFS administrative access. You should use the
username/admin principal discussed above. afs-newcell sets up the
initial protection database (which stores users and groups),
configures the AFS database and file server daemons, and creates the
root volume for AFS clients.
At the completion of this step, you should see bosserver and several
other AFS server processes running, and you should be able to see
the status of those processes with:
bos status localhost -local
bosserver is a master server that starts and monitors all the
individual AFS servers, and bos is the program used to send it
commands.
Now, you should be able to run:
kinit username/admin@REALM
aklog cell.name -k REALM
where username/admin is the admin principal discussed above, REALM
is the name of your Kerberos realm, and cell.name is the name of
your AFS cell. This will obtain Kerberos tickets and AFS tokens in
your Kerberos realm and new AFS cell. You should be able to see
your AFS tokens by running:
tokens
Finally, you should be able to see the status of the AFS server
processes with:
bos status <hostname>
where <hostname> is the hostname of the local system, once you've
done the above. This tests authenticated bos access as your admin
principal (rather than using the local KeyFile to authenticate).
10. Run afs-rootvol. This creates the basic AFS volume structure for
your new cell, including the top-level volume, the mount point for
your cell in the AFS root volume, and the mount points for all known
public cells. It will prompt you to be sure that the above steps
are complete and then will ask you what file server and partition to
create the volume on. If you were following the above instructions,
use the local hostname and "a" as the partition (without the
quotes), which will use /vicepa.
After this command completes, you should be able to /bin/ls /afs and
see your local cell (and, if you aren't using dynroot, mount points
for several other cells). Note that if you're not using fakestat,
run /bin/ls rather than just ls to be sure that ls isn't aliased to
ls -F, ls --color, or some other option that would stat each file in
/afs, since this would require contacting lots of foreign cells and
could take a very long time.
You should now be able to cd to /afs/cell.name where cell.name is
the AFS cell name that you used. Currently, there isn't anything in
your cell except two volumes, user and service, created by
afs-rootvol. To make modifications, cd to /afs/.cell.name (note the
leading period) and make changes there. To make those changes show
up at /afs/cell.name, run vos release root.cell. For more details
on what you can do now, see the AFS Administrator's Reference.
11. While this is optional, you probably want to add AFSDB records to
DNS for your new AFS cell. These special DNS records let AFS
clients find the db servers for your cell without requiring local
configuration. To do this, create a DNS record like:
<cell>. 3600 IN AFSDB 1 <server>.
where <cell> is the name of your AFS cell and <server> is the name
of your db server. Note the trailing periods to prevent the DNS
server from appending the origin. You can, of course, choose what
you prefer for the lifetime. The 1 is not a priority; it's a
special indicator saying that this record is for an AFS database
server.
If you have multiple db servers (see below for adding new ones), you
should create multiple records of this type, one per db server.
Congratulations! You now have an AFS cell. If any of the above steps
failed, please check the steps carefully and make sure that you've done
them all in order. If that doesn't reveal the cause of the problem,
please feel free to submit a bug report with reportbug. Include as many
details as possible on exactly what you typed and exactly what you saw
as a result, particularly any error messages.
Adding Additional Servers
If you decide one server is not enough, or if you're adding a server to
an existing cell, here is roughly what you should do:
1. Copy securely (using scp, encrypted Kerberos rcp, or some other
secure method) all of /etc/openafs/server to the new server.
2. Install the openafs-fileserver package on the new server.
3. If the machine is to be a file server, create an fs instance using
bos create:
bos create <host> fs fs -cmd /usr/lib/openafs/dafileserver \
-cmd /usr/lib/openafs/davolserver \
-cmd /usr/lib/openafs/salvageserver \
-cmd /usr/lib/openafs/salvager -localauth
For a file server, this is all you have to do. The above uses the
default fileserver options, however, which are not particularly
well-tuned for modern systems. afs-newcell uses the following
parameters from Harald Barth:
-p 23 -busyat 600 -rxpck 400 -s 1200 -l 1200 -cb 65535
-b 240 -vc 1200
If you want to add any additional fileserver options, enclose
/usr/lib/openafs/dafileserver and the following options in double
quotes when giving the bos create command.
This creates a demand-attach fileserver, which is recommended for
new installations. You can also create a regular fileserver if you
prefer. See the bos_create(8) man page for more information.
4. For database servers, also install openafs-dbserver and then use bos
addhost to add the new server to /etc/openafs/server/CellServDB:
bos addhost <server> <new-server>
for each db server <server> in your cell (including the new one).
Then, restart the ptserver and vlserver instances on each of your
existing servers with:
bos restart <server> ptserver
bos restart <server> vlserver
It's best to wait a few seconds after doing this for each server
before doing the next server so that voting finishes and you never
lose a quorum.
Only after ptserver and vlserver have been restarted on each of your
existing servers, create ptserver and vlserver instances on the new
server:
bos create <host> ptserver simple /usr/lib/openafs/ptserver \
-localauth
bos create <host> vlserver simple /usr/lib/openafs/vlserver \
-localauth
The existing servers should then propagate the database to the new
server. If you are using buserver, you will need to do the same
thing for it as with ptserver and vlserver.
Note that you do not need to run a file server on a db server if you
don't want to (and larger sites probably will not want to), but you
always need to have the openafs-fileserver package installed on db
servers. It contains the bosserver binary and some of the shared
infrastructure.
5. If you added a new db server, configure your clients to use it. If
you are using AFSDB records in DNS, you can just add a new record
(see point 10 in the instructions for creating a new cell).
Otherwise, clients will need to have the new server IP address added
to their /etc/openafs/CellServDB file (or /usr/vice/etc/CellServDB
for non-Debian clients using the standard AFS paths), and the client
will have to be restarted before it will know about the new db
server.
The standard rule of thumb is that all of your database servers and file
servers should ideally be running the same version of OpenAFS. However,
in practice OpenAFS is fairly good at backward compatibility and you can
generally mix and match different versions. Be careful, though, to
ensure that all of your database servers are built the same when it
comes to options like --enable-supergroups (enabled in the Debian
packages).
Upgrades
Currently, during an upgrade of the openafs-fileserver package, all
services will be stopped and restarted. If openafs-dbserver is upgraded
without upgrading openafs-fileserver, those server binaries will not be
stopped and restarted; that restart will have to be done by hand.
It is possible that future versions of this package will install for
example /usr/lib/openafs/fileserver.package instead of
/usr/lib/openafs/fileserver and then create links to the actual binaries
in postinst. Upgrades would then not replace the old binaries, but
instead a script will be provided to roll the links forward to the new
versions. The intent is that people could install the new package on
all their servers and then quickly move the links before restarting the
bosserver. This has not yet been implemented.

136
src/packaging/Debian/README.source
View File

@ -1,136 +0,0 @@
General Maintenance
This package is maintained in Git via the Alioth pkg-k5-afs project.
Alioth is used only for repository access control and not for any of
its other features.
Since we often pull up many upstream fixes from the upstream stable
branch due to slow upstream release frequencies, we use Git to handle
merging and patch pullups and do not attempt to export the Git
repository state as a patch set. Accordingly, this package uses
source format 1.0, since 3.0 (quilt) doesn't offer many additional
features.
Ideally, any changes that are not strictly Debian packaging changes
should be submitted upstream first. Upstream uses Gerrit for patch
review, which makes it very easy for anyone who wishes to submit
patches for review using Git. See:
http://wiki.openafs.org/GitDevelopers/
for information on how to submit patches upstream. There are some
Debian-specific patches to the upstream source in the 1.4 versions of
the Debian packages, but in the 1.5 experimental branch there are no
Debian changes outside of the debian/* directory. We want to keep it
that way if at all possible.
Importing a New Upstream Release
We want to be able to use Git to cherry-pick fixes from upstream, but
we want to base the Debian packages on the upstream tarball releases.
We also need to strip some non-DFSG files from the upstream tarball
releases and imported code, and want to drop the WINNT directory to
save some space. This means we follow a slightly complicated method
for importing a new upstream release.
Follow the following procedure to import a new upstream release:
1. Update the package version in debian/changelog to match the new
upstream version. If the new upstream version is a release
candidate, don't forget to add "~" before "rc" so that the versions
will sort property.
2. Double-check the TAG setting in debian/rules to be sure it's going
to retrieve the correct Git tag.
3. Run debian/rules get-orig-source. This will generate a tarball
from the upstream Git tag using git archive, remove the WINNT
directory, and create a file named openafs_<version>.orig.tar.gz in
the current directory.
4. Ensure that you have the OpenAFS upstream Git repository available
as a remote in the Git repository where you're doing the packaging
work and it's up to date:
git remote add openafs git://git.openafs.org/openafs.git
git fetch openafs
This will be required to locate the tag for the new upstream
release.
5. Determine the release tag corresponding to this tarball. At the
time of this writing, upstream uses tags in the form:
openafs-stable-<version>
openafs-devel-<version>
for stable and development releases respectively. <version> is the
version number with periods replaced by underscores. This
convention may change, so double-check with git tag.
6. Import the upstream source from the tarball with:
debian/import-upstream <tarball> <upstream-tag> <local-tag>
where <tarball> is the tarball created by get-orig-source above,
<upstream-tag> is the corresponding tag from the upstream Git
repository, and <local-tag> is of the form upstream/<version> where
<version> is the non-Debian portion of the package version number.
(In other words, including any tildes, but not the dash and the
Debian revision.)
7. Commit the tarball to the repository with pristine-tar, using the
new local tag as the reference:
pristine-tar commit <tarball> <local-tag>
8. Merge the new upstream source into the master branch:
git checkout master
git merge <local-tag>
where <local-tag> is the tag you used above. You can also just
merge with the upstream branch; either is equivalent.
9. Flesh out the changelog entry for the new version with a summary of
what changed in that release, and continue as normal with Debian
packaging.
Pulling Upstream Changes
Upstream releases, particularly stable releases, are relatively
infrequent, so it's often desirable to pull upstream changes from the
stable branch into the Debian package. This should always be done
using git cherry-pick -x so that we can use git cherry to see which
changes on the stable branch have not been picked up.
The procedure is therefore:
1. Identify the hash of the commit that you want to pull up using git
log or other information.
2. git cherry-pick -x <hash>. If the cherry-pick fails and you have
to manually do a merge, follow the instructions to use -c to keep
the original commit message as a starting point, but *also*
manually add a line like:
(cherry picked from commit <hash>)
to the changelog entry where <hash> is the full hash of the
upstream commit. Note that the upstream commits on the stable
branch will generally already have a line like this from upstream's
cherry-pick. This will be a second line.
3. Add a changelog entry and commit it separately. Use the following
convention for changelog entries for cherry-picks:
* Apply upstream deltas:
- [<hash>] <title>
- ...
where <hash> is the first eight characters of the upstream commit
hash and <title> is the first line of the upstream commit message,
edited as necessary to keep the length of the changelog lines
down.
-- Russ Allbery <rra@debian.org>, Tue, 13 Jul 2010 19:30:15 -0700

8
src/packaging/Debian/TODO
View File

@ -1,8 +0,0 @@
* Get bos restrict working.
* The configuration transcript and the README.servers file would be best
read together, but preferrably with some nicer formatting (such as HTML
with a style sheet to set off the transcript in a different background
color).
* Use pts addu -local instead of pt_util for initial cell setup.

289
src/packaging/Debian/afs-newcell
View File

@ -1,289 +0,0 @@
#!/usr/bin/perl -w
# Copyright (C) 2000 by Sam Hartman
# This file may be copied either under the terms of the GNU GPL or the IBM
# Public License either version 2 or later of the GPL or version 1.0 or later
# of the IPL.
use Term::ReadLine;
use strict;
use Debian::OpenAFS::ConfigUtils;
use Getopt::Long;
use Socket qw(inet_ntoa);
use vars qw($admin $server $requirements_met $shutdown_needed);
my $rl = new Term::ReadLine('afs-newcell');
# The default file server options are poor. Until they've been updated, use
# the following from Harald Barth; it should be an improvement for most
# people.
my $fs_options = '-p 23 -busyat 600 -rxpck 400 -s 1200 -l 1200 -cb 65535'
. ' -b 240 -vc 1200';
=head1 NAME
afs-newcell - Set up initial database server for AFS cell
=head1 SYNOPSIS
B<afs-newcell> [B<--requirements-met>] [B<--admin> admin_user]
=head1 DESCRIPTION
This script sets up the initial AFS database and configures the first
database/file server.
The B<--requirements-met> option specifies that the initial requirements have
been met and that the script can proceed without displaying the initial
banner or asking for confirmation.
The B<--admin> option specifies the name of the administrative user. This
user will be given system:administrators and susers permission in the cell.
=head1 AUTHOR
Sam Hartman <hartmans@debian.org>
=cut
# Flush all output immediately.
$| = 1;
GetOptions ("requirements-met" => \$requirements_met, "admin=s" => \$admin);
unless ($requirements_met) {
print <<eoreqs;
Prerequisites
In order to set up a new AFS cell, you must meet the following:
1) You need a working Kerberos realm with Kerberos4 support. You
should install Heimdal with KTH Kerberos compatibility or MIT
Kerberos 5.
2) You need to create the single-DES AFS key and load it into
/etc/openafs/server/KeyFile. If your cell's name is the same as
your Kerberos realm then create a principal called afs. Otherwise,
create a principal called afs/cellname in your realm. The cell
name should be all lower case, unlike Kerberos realms which are all
upper case. You can use asetkey from the openafs-krb5 package, or
if you used AFS3 salt to create the key, the bos addkey command.
3) This machine should have a filesystem mounted on /vicepa. If you
do not have a free partition, then create a large file by using dd
to extract bytes from /dev/zero. Create a filesystem on this file
and mount it using -oloop.
4) You will need an administrative principal created in a Kerberos
realm. This principal will be added to susers and
system:administrators and thus will be able to run administrative
commands. Generally the user is a root or admin instance of some
administrative user. For example if jruser is an administrator then
it would be reasonable to create jruser/admin (or jruser/root) and
specify that as the user to be added in this script.
5) The AFS client must not be running on this workstation. It will be
at the end of this script.
eoreqs
#'# cperl-mode
$_ = $rl->readline("Do you meet these requirements? [y/n] ");
unless (/^y/i ) {
print "Run this script again when you meet the requirements\n";
exit(1);
}
if ($> != 0) {
die "This script should almost always be run as root. Use the\n"
. "--requirements-met option to run as non-root.\n";
}
}
# Make sure the AFS client is not already running.
open(MOUNT, "mount |") or die "Failed to run mount: $!\n";
while(<MOUNT>) {
if (m:^AFS:) {
print "The AFS client is currently running on this workstation.\n";
print "Please restart this script after running"
. " /etc/init.d/openafs-client stop\n";
exit(1);
}
}
close MOUNT;
# Make sure there is a keyfile.
unless ( -f "/etc/openafs/server/KeyFile") {
print "You do not have an AFS keyfile. Please create this using\n";
print "asetkey from openafs-krb5 or the bos addkey command\n";
exit(1);
}
# Stop the file server.
print "If the fileserver is not running, this may hang for 30 seconds.\n";
run("/etc/init.d/openafs-fileserver stop");
# Get the local hostname. Use the fully-qualified hostname to be safer.
$server = `hostname -f`;
chomp $server;
my $ip = gethostbyname $server;
if (inet_ntoa($ip) eq '127.0.0.1') {
print "\n";
print "Your hostname $server resolves to 127.0.0.1, which AFS cannot\n";
print "cope with. Make sure your hostname resolves to a non-loopback\n";
print "IP address. (Check /etc/hosts and make sure that your hostname\n";
print "isn't listed on the 127.0.0.1 line. If it is, removing it from\n";
print "that line will probably solve this problem.)\n";
exit(1);
}
# Determine the admin principal.
$admin = $rl->readline("What administrative principal should be used? ")
unless $admin;
print "\n";
die "Please specify an administrative user\n" unless $admin;
my $afs_admin = $admin;
$afs_admin =~ s:/:.:g;
if ($afs_admin =~ /@/) {
die "The administrative user must be in the same realm as the cell and\n"
. "no realm may be specified.\n";
}
# Determine the local cell. This should be configured via debconf, from the
# openafs-client configuration, when openafs-fileserver is installed.
open(CELL, "/etc/openafs/server/ThisCell")
or die "Cannot open /etc/openafs/server/ThisCell: $!\n";
my $cell = <CELL>;
chomp $cell;
# Make sure the new cell is configured in the client CellServDB.
open(CELLSERVDB, "/etc/openafs/CellServDB")
or die "Cannot open /etc/openafs/CellServDB: $!\n";
my $found = 0;
while (<CELLSERVDB>) {
next unless /^>\Q$cell\E\s/;
while (<CELLSERVDB>) {
last if /^>/;
my ($dbserver) = split ' ';
if ($dbserver eq inet_ntoa($ip)) {
$found = 1;
last;
}
}
last;
}
unless ($found) {
print "\n";
print "The new cell $cell is not configured in /etc/openafs/CellServDB\n";
print "Add configuration like:\n\n";
print ">$cell\n";
print inet_ntoa($ip), "\t\t\t#$server\n\n";
print "to that file before continuing.\n";
exit(1);
}
# Write out a new CellServDB for the local cell containing only this server.
if (-f "/etc/openafs/server/CellServDB") {
print "/etc/openafs/server/CellServDB already exists, renaming to .old\n";
rename("/etc/openafs/server/CellServDB",
"/etc/openafs/server/CellServDB.old")
or die "Cannot rename /etc/openafs/server/CellServDB: $!\n";
}
open(CELLSERVDB, "> /etc/openafs/server/CellServDB")
or die "Cannot create /etc/openafs/server/CellServDB: $!\n";
print CELLSERVDB ">$cell\n";
print CELLSERVDB inet_ntoa($ip), "\t\t\t#$server\n";
close CELLSERVDB or die "Cannot write to /etc/openafs/server/CellServDB: $!\n";
# Now, we should be able to start bos and add the admin user.
run("/etc/init.d/openafs-fileserver start");
$shutdown_needed = 1;
run("bos adduser $server $afs_admin -localauth");
unwind("bos removeuser $server $afs_admin -localauth");
# Create the initial protection database using pt_util. This is safer than
# the standard mechanism of starting the cell in noauth mode until the first
# user has been created.
if (-f "/var/lib/openafs/db/prdb.DB0") {
warn "ERROR: Protection database already exists; cell already partially\n";
warn "ERROR: created. If you do not want the current database, remove\n";
warn "ERROR: all files in /var/lib/openafs/db and then run this program\n";
warn "ERROR: again.\n";
exit(1);
}
print "\nCreating initial protection database. This will print some errors\n";
print "about an id already existing and a bad ubik magic. These errors can\n";
print "be safely ignored.\n\n";
open(PRDB, "| pt_util -p /var/lib/openafs/db/prdb.DB0 -w")
or die "Unable to start pt_util: $!\n";
print PRDB "$afs_admin 128/20 1 -204 -204\n";
print PRDB "system:administrators 130/20 -204 -204 -204\n";
print PRDB " $afs_admin 1\n";
close PRDB;
unwind("rm /var/lib/openafs/db/prdb*");
print "\n";
# We should now be able to start ptserver and vlserver.
run("bos create $server ptserver simple /usr/lib/openafs/ptserver -localauth");
unwind("bos delete $server ptserver -localauth");
run("bos create $server vlserver simple /usr/lib/openafs/vlserver -localauth");
unwind("bos delete $server vlserver -localauth");
# Create a file server as well.
run("bos create $server dafs dafs"
. " -cmd '/usr/lib/openafs/dafileserver $fs_options'"
. " -cmd /usr/lib/openafs/davolserver"
. " -cmd /usr/lib/openafs/salvageserver"
. " -cmd /usr/lib/openafs/dasalvager");
unwind("bos delete $server fs -localauth");
# Make sure that there is no scheduled general restart time; it's not needed.
run("bos setrestart $server -time never -general -localauth");
# Pause for a while for ubik to catch up.
print "Waiting for database elections: ";
sleep(30);
print "done.\n";
# Past this point we want to control when bos shutdown happens.
$shutdown_needed = 0;
unwind("bos shutdown $server -localauth -wait");
run("vos create $server a root.afs -localauth");
unwind("vos remove $server a root.afs -localauth");
# We should now be able to bring up the client (it may need root.afs to exist
# if not using dynroot). We override whatever default cell was configured for
# the client, just in case it was pointing to some other cell.
open(THIS, "> /etc/openafs/ThisCell")
or die "ERROR: Cannot create /etc/openafs/ThisCell: $!\n";
print THIS "$cell\n";
close THIS or die "ERROR: Cannot write to /etc/openafs/ThisCell: $!\n";
run("/etc/init.d/openafs-client force-start");
# Verify that AFS has managed to start.
my $afs_running = 0;
open(MOUNT, "mount |") or die "ERROR: Failed to run mount: $!\n";
while(<MOUNT>) {
if (m:^AFS:) {
$afs_running = 1;
}
}
unless ($afs_running) {
print "ERROR: The AFS client failed to start.\n";
print "ERROR: Please fix whatever problem kept it from running.\n";
exit(1);
}
print "\n";
print "Now, get tokens as $admin in the $cell cell.\n";
print "Then, run afs-rootvol.\n";
# Success, so clear the unwind commands.
@unwinds = ();
# If we fail before all the instances are created, we need to back out of
# everything we did as much as possible.
END {
if ($shutdown_needed || @unwinds) {
print "\nCell setup failed, ABORTING\n";
}
system("bos shutdown $server -localauth -wait") if $shutdown_needed;
run(pop @unwinds) while @unwinds;
}

194
src/packaging/Debian/afs-rootvol
View File

@ -1,194 +0,0 @@
#!/usr/bin/perl -w
# Copyright (C) 2000 by Sam Hartman
# This file may be copied either under the terms of the GNU GPL or the IBM
# Public License either version 2 or later of the GPL or version 1.0 or later
# of the IPL.
use strict;
use Debian::OpenAFS::ConfigUtils;
use Term::ReadLine;
use Getopt::Long;
use vars qw($rl $server $part $requirements_met);
=head1 NAME
afs-rootvol - Generate and populate root volumes for new AFS cells.
=head1 SYNOPSIS
B<afs-rootvol> [B<--requirements-met>] [B<--server> I<server-name>]
[B<--partition> I<partition-letter>]
=head1 DESCRIPTION
This script sets up an AFS cell's root volumes. It assumes that you already
have a fileserver and database servers. The fileserver should have an empty
root.afs. This script creates root.cell, user, and service and populates
root.afs.
=head1 AUTHOR
Sam Hartman <hartmans@debian.org>
=cut
#'# cperl-mode
# This subroutine creates a volume, mounts it and then sets the access
# to allow read by anyuser. The volume is scheduled for deletion in
# case of error.
sub mkvol($$) {
my ($vol, $mnt) = @_;
run("vos create $server $part $vol -localauth");
unwind("vos remove $server $part $vol -localauth");
run("fs mkm $mnt $vol ");
run("fs sa $mnt system:anyuser rl");
}
# Main script. Flush all output immediately.
$| = 1;
$rl = new Term::ReadLine('AFS');
GetOptions ("requirements-met" => \$requirements_met,
"server=s" => \$server,
"partition=s" => \$part);
unless ($requirements_met) {
print <<eotext;
Prerequisites
In order to set up the root.afs volume, you must meet the following
pre-conditions:
1) The cell must be configured, running a database server with a
volume location and protection server. The afs-newcell script will
set up these services.
2) You must be logged into the cell with tokens in for a user in
system:administrators and with a principal that is in the UserList
file of the servers in the cell.
3) You need a fileserver in the cell with partitions mounted and a
root.afs volume created. Presumably, it has no volumes on it,
although the script will work so long as nothing besides root.afs
exists. The afs-newcell script will set up the file server.
4) The AFS client must be running pointed at the new cell.
eotext
$_ = $rl->readline("Do you meet these conditions? (y/n) ");
unless (/^y/i ) {
print "Please restart the script when you meet these conditions.\n";
exit(1);
}
if ($> != 0) {
die "This script should almost always be run as root. Use the\n"
. "--requirements-met option to run as non-root.\n";
}
}
# Get configuration information we need.
open(CELL, "/etc/openafs/server/ThisCell")
or die "Unable to find out what cell this machine serves: $!\n";
my $cell = <CELL>;
close CELL;
chomp $cell;
unless ($server) {
print <<eotext;
You will need to select a server (hostname) and AFS partition on which to
create the root volumes.
eotext
$server = $rl->readline("What AFS Server should volumes be placed on? ");
die "Please select a server.\n" unless $server;
}
unless ($part) {
$part = $rl->readline("What partition? [a] ");
$part = "a" unless $part;
}
print "\n";
# Make sure the user has tokens. Forgetting to do this is a common error.
my $status = system("tokens | grep Expires > /dev/null");
if ($status != 0) {
die "You appear to not have AFS tokens. Obtain tokens (with aklog,\n"
. "for example) and then run this script again.\n";
}
# Figure out where root.afs is. There are two possibilities: either we aren't
# running with dynroot, and root.afs is therefore accessible as /afs, or we
# are running with dynroot, in which case we have to create root.cell first
# and then mount root.afs under it.
#
# Always create root.cell first; we may need it if running with dynroot, and
# it doesn't hurt to do it now regardless.
my $rootmnt = "/afs";
run("vos create $server $part root.cell -localauth");
unwind("vos remove $server $part root.cell -localauth");
my $dynroot = (-d "$rootmnt/$cell/.");
if ($dynroot) {
run("fs mkm /afs/$cell/.root.afs root.afs -rw");
unwind("fs rmm /afs/$cell/.root.afs");
$rootmnt = "/afs/$cell/.root.afs";
}
run("fs sa $rootmnt system:anyuser rl");
# Scan CellServDB and create the cell mount points for every cell found there.
# Force these commands to succeed, since it's possible to end up with
# duplicate entries in CellServDB (and the second fs mkm will fail).
open(CELLSERVDB, "/etc/openafs/CellServDB")
or die "Unable to open /etc/openafs/CellServDB: $!\n";
while (<CELLSERVDB>) {
chomp;
if (/^>\s*([a-z0-9_\-.]+)/) {
run("fs mkm $rootmnt/$1 root.cell -cell $1 -fast || true");
unwind("fs rmm $rootmnt/$1 || true");
}
}
# Now, create the read/write mount points for root.cell and root.afs and set
# root.cell system:anyuser read.
run("fs sa /afs/$cell system:anyuser rl");
run("fs mkm $rootmnt/.$cell root.cell -cell $cell -rw");
unwind("fs rmm $rootmnt/.$cell");
run("fs mkm $rootmnt/.root.afs root.afs -rw");
unwind("fs rmm $rootmnt/.root.afs");
# Create the user and service mount point volumes to fit the semi-standard AFS
# cell layout.
mkvol("user", "/afs/$cell/user");
mkvol("service", "/afs/$cell/service");
# Strip the domain off of the cell name and create the short symlinks.
$cell =~ /^([^.]+)/;
my $cellpart = $1;
if ($cellpart && $cellpart ne $cell) {
run("ln -s $cell $rootmnt/$cellpart");
unwind("rm $rootmnt/$cellpart");
run("ln -s .$cell $rootmnt/.$cellpart");
unwind("rm $rootmnt/.$cellpart");
}
if ($dynroot) {
run("fs rmm /afs/$cell/.root.afs");
unwind("fs mkm /afs/$cell/.root.afs root.afs -rw");
}
# Now, replicate the infrastructure volumes.
run("vos addsite $server $part root.afs -localauth");
run("vos addsite $server $part root.cell -localauth");
run("vos release root.afs -localauth");
run("vos release root.cell -localauth");
unwind("vos remove $server $part root.cell.readonly -localauth");
unwind("vos remove $server $part root.afs.readonly -localauth");
# Success, so clear the unwind commands.
@unwinds = ();
# If we fail before all the instances are created, we need to back out of
# everything we did as much as possible.
END {
if (@unwinds) {
print "\nRoot volume setup failed, ABORTING\n";
}
run(pop @unwinds) while @unwinds;
}

116
src/packaging/Debian/afs.conf
View File

@ -1,116 +0,0 @@
# -*- sh -*-
# Copyright 2000, International Business Machines Corporation and others.
# All Rights Reserved.
#
# This software has been released under the terms of the IBM Public
# License. For details, see the LICENSE file in the top-level source
# directory or online at http://www.openafs.org/dl/license10.html
# Configuration information for AFS client.
# The following options are maintained by debconf. To change them, run
# dpkg-reconfigure openafs-client.
#
# AFS_CLIENT Whether to start the AFS client at boot
# AFS_AFSDB Whether to use AFSDB DNS records to find VLDB servers
# AFS_CRYPT Whether to enable fcrypt encryption
# AFS_DYNROOT Whether to use a dynamic /afs directory
# AFS_FAKESTAT Whether to fake stat data for mount points
test -f /etc/openafs/afs.conf.client && . /etc/openafs/afs.conf.client
# Set to "-verbose" for a lot of debugging information from afsd. Only useful
# for debugging as it prints a LOT of information.
VERBOSE=
# AFS client configuration options.
#
# Here is a (mostly) complete list of flags that afsd accepts and that are
# useful here:
#
# -blocks The number of blocks available in the workstation cache.
# -files The target number of files in the workstation cache (Default:
# 1000).
# -rootvol The name of the root volume to use.
# -stat The number of stat cache entries.
# -hosts List of servers to check for volume location info FOR THE
# HOME CELL.
# -memcache Use an in-memory cache rather than disk.
# -cachedir The base directory for the workstation cache.
# -mountdir The directory on which the AFS is to be mounted.
# -confdir The configuration directory.
# -nosettime Don't keep checking the time to avoid drift (default).
# -settime Keep checking the time to avoid drift.
# -verbose Be chatty.
# -debug Print out additional debugging info.
# -daemons The number of background daemons to start (Default: 2).
# -rmtsys Also fires up an afs remote sys call (e.g. pioctl, setpag)
# support daemon
# -chunksize 2^n is the chunksize to be used (Default: use a kernel
# module default).
# -dcache The number of data cache entries.
# -prealloc Number of preallocated "small" memory blocks
# -waitclose Make close calls always synchronous (slows them down, though)
# -files_per_subdir Number of files per cache subdir (Default: 2048).
#
# Using the memory cache is not recommended. It's less stable than the disk
# cache and doesn't improve performance as much as it might sound.
#
# The default behavior is to let afsd automatically choose an apporpriate set
# of flags. This should produce reasonable behavior for most working sets
# provided that one is using a modern AFS client (1.4.2 or later).
#
# You can override that default behavior by setting OPTIONS to a specific set
# of flags.
OPTIONS=AUTOMATIC
# The default value for the client sysname (as returned by fs sysname) is
# determined during the kernel module build and is taken from the architecture
# and the major Linux kernel version. Accesses to directories named "@sys" in
# AFS will be internally redirected to a directory by this name by the AFS
# client, allowing a single path to resolve to different directories depending
# on the client architecture.
#
# If you would like to override the client sysname, uncomment this line and
# set the variable to a space-separated list of sysnames. The AFS client will
# attempt to resolve @sys to each directory name in the order given.
#AFS_SYSNAME=""
# If you want to prefer particular servers for replicated volumes, you can
# configure that by defining an afs_server_prefs function here and then
# uncommenting the setting of AFS_POST_INIT below. For more information, see
# fs help setserverprefs and fs getserverprefs (for the current values).
#afs_server_prefs() {
# fs setserverprefs <host> <rank>
#}
# If you want to always run some command after starting OpenAFS, you can put
# it here. Note that you cannot run multiple commands, even combined with &&
# or ; or similar shell meta-characters. If you want to run multiple
# commands, define a shell function instead and put the name of the shell
# function here.
AFS_POST_INIT=
# Uncomment this line if you defined an afs_server_prefs function. (If you
# have other commands that you also want to run, you'll have to put them in
# that function, as you can only run one function.)
#AFS_POST_INIT=afs_server_prefs
# If you want to always run some command before shutting down OpenAFS, you can
# put it here. The same caveat applies about multiple commands.
AFS_PRE_SHUTDOWN=
# If you are having problems with AFS shutting down cleanly or the system not
# rebooting because the partition the AFS cache was on could not be unmounted,
# try installing lsof and uncommenting this. This will cause all processes
# with open AFS files to be killed before unmounting AFS if the runlevel being
# switched to is 0 or 6.
#
# Warning: This means /etc/init.d/openafs-client stop will kill all processes
# with files open in AFS rather than returning an error saying the file system
# is busy. This is probably what you want when the whole system is shutting
# down, but often *not* what you want when just stopping and restarting the
# client. The code doesn't run unless the runlevel is 0 or 6, but still, be
# sure that this is what you want before enabling it.
#AFS_PRE_SHUTDOWN=kill_all_afs

2244
src/packaging/Debian/changelog.in
View File

File diff suppressed because it is too large Load Diff

12
src/packaging/Debian/clean
View File

@ -1,12 +0,0 @@
.version
aclocal.m4
configure
configure-libafs
doc/man-pages/man1/*.1
doc/man-pages/man5/*.5
doc/man-pages/man8/*.8
doc/xml/*/Makefile
doc/xml/*/version.xml
src/config/Makefile.version-CML
src/kauth/ka-forwarder
src/packaging/RedHat/openafs.spec

1
src/packaging/Debian/compat
View File

@ -1 +0,0 @@
8

561
src/packaging/Debian/configuration-transcript.txt
View File

@ -1,561 +0,0 @@
This is a transcript of a user following the instructions in
README.servers. It is best read side-by-side with that documentation
while you are setting up your cell.
This transcript includes creation of a loopback mount on /vicepa using
file full of zeros. This is useful to know how to do because it allows
you to test an AFS server without repartitioning. However, for production
cells, you should repartition and create a /vicepa partition.
Thanks to Faheem Mitha for the transcript.
##########################################################################
riverside:/home/faheem# apt-get install krb5-admin-server
...
The following extra packages will be installed:
krb5-config krb5-kdc krb5-user
The following NEW packages will be installed:
krb5-admin-server krb5-config krb5-kdc krb5-user
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 348kB of archives.
After unpacking 889kB of additional disk space will be used.
Do you want to continue? [Y/n]
...
Configuring krb5-config
-----------------------
When users attempt to use Kerberos and specify a principal or user
name without specifying what administrative Kerberos realm that
principal belongs to, the system appends the default realm.
Normally default realm is the upper case version of the local DNS
domain.
What is the default Kerberos version 5 realm? DULCI.BIOSTAT.DUKE.EDU
Configuring krb5-kdc
--------------------
By default, Kerberos4 requests are allowed from principals that do not
require preauthentication. This allows Kerberos4 services to exist
while requiring most users to use Kerberos5 clients to get their
initial tickets. These tickets can then be converted to Kerberos4
tickets. Alternatively, the mode can be set to full, allowing
Kerberos4 to get initial tickets even when preauthentication would
normally be required, or to disable, which will disable all Kerberos4
support.
1. disable 2. full 3. nopreauth 4. none
Kerberos4 compatibility mode to use: 3
Configuring krb5-admin-server
-----------------------------
Setting up a Kerberos Realm
This package contains the administrative tools necessary to run on the
Kerberos master server. However, installing this package does not
automatically set up a Kerberos realm. Doing so requires entering
passwords and as such is not well-suited for package installation. To
create the realm, run the krb5_newrealm command. You may also wish to
read /usr/share/doc/krb5-kdc/README.KDC and the administration guide
found in the krb5-doc package.
Don't forget to set up DNS information so your clients can find your
KDC and admin servers. Doing so is documented in the administration
guide.
Selecting previously deselected package krb5-config.
(Reading database ... 81199 files and directories currently installed.)
Unpacking krb5-config (from .../krb5-config_1.6_all.deb) ...
Selecting previously deselected package krb5-user.
Unpacking krb5-user (from .../krb5-user_1.3.6-2sarge2_i386.deb) ...
Selecting previously deselected package krb5-kdc.
Unpacking krb5-kdc (from .../krb5-kdc_1.3.6-2sarge2_i386.deb) ...
Selecting previously deselected package krb5-admin-server.
Unpacking krb5-admin-server (from .../krb5-admin-server_1.3.6-2sarge2_i386.deb) ...
Setting up krb5-config (1.6) ...
Configuring krb5-config
-----------------------
Enter the hostnames of Kerberos servers in the DULCI.BIOSTAT.DUKE.EDU Kerberos realm separated by spaces.
What are the Kerberos servers for your realm? riverside.dulci.biostat.duke.edu
Enter the hostname of the administrative (password changing) server
for the DULCI.BIOSTAT.DUKE.EDU Kerberos realm.
What is the administrative server for your Kerberos realm? riverside.dulci.biostat.duke.edu
Setting up krb5-user (1.3.6-2sarge2) ...
Setting up krb5-kdc (1.3.6-2sarge2) ...
Setting up krb5-admin-server (1.3.6-2sarge2) ...
Starting Kerberos Administration Servers: kadmind: No such file or directory while initializing, aborting
kadmind.
riverside:/home/faheem# krb5_newrealm
This script should be run on the master KDC/admin server to initialize
a Kerberos realm. It will ask you to type in a master key password.
This password will be used to generate a key that is stored in
/etc/krb5kdc/stash. You should try to remember this password, but it
is much more important that it be a strong password than that it be
remembered. However, if you lose the password and /etc/krb5kdc/stash,
you cannot decrypt your Kerberos database.
Loading random data
Initializing database '/var/lib/krb5kdc/principal' for realm 'DULCI.BIOSTAT.DUKE.EDU',
master key name 'K/M@DULCI.BIOSTAT.DUKE.EDU'
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.
Enter KDC database master key:
Re-enter KDC database master key to verify:
Starting Kerberos KDC: krb5kdc krb524d.
Starting Kerberos Administration Servers: kadmind.
Now that your realm is set up you may wish to create an administrative
principal using the addprinc subcommand of the kadmin.local program.
Then, this principal can be added to /etc/krb5kdc/kadm5.acl so that
you can use the kadmin program on other computers. Kerberos admin
principals usually belong to a single user and end in /admin. For
example, if jruser is a Kerberos administrator, then in addition to
the normal jruser principal, a jruser/admin principal should be
created.
Don't forget to set up DNS information so your clients can find your
KDC and admin servers. Doing so is documented in the administration
guide.
riverside:/home/faheem# kadmin.local
Authenticating as principal root/admin@DULCI.BIOSTAT.DUKE.EDU with password.
kadmin.local: addprinc faheem/admin
WARNING: no policy specified for faheem/admin@DULCI.BIOSTAT.DUKE.EDU; defaulting to no policy
Enter password for principal "faheem/admin@DULCI.BIOSTAT.DUKE.EDU":
Re-enter password for principal "faheem/admin@DULCI.BIOSTAT.DUKE.EDU":
Principal "faheem/admin@DULCI.BIOSTAT.DUKE.EDU" created.
kadmin.local: addprinc faheem
WARNING: no policy specified for faheem@DULCI.BIOSTAT.DUKE.EDU; defaulting to no policy
Enter password for principal "faheem@DULCI.BIOSTAT.DUKE.EDU":
Re-enter password for principal "faheem@DULCI.BIOSTAT.DUKE.EDU":
Principal "faheem@DULCI.BIOSTAT.DUKE.EDU" created.
kadmin.local: exit
riverside:/home/faheem# apt-get install openafs-dbserver openafs-krb5
...
The following extra packages will be installed:
openafs-client openafs-fileserver
The following NEW packages will be installed:
openafs-client openafs-dbserver openafs-fileserver openafs-krb5
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 2927kB of archives.
After unpacking 6898kB of additional disk space will be used.
Do you want to continue? [Y/n]
...
Configuring openafs-client
--------------------------
AFS filespace is organized into cells or administrative domains. Each
workstation belongs to one cell. Usually the cell is the DNS domain
name of the site.
What AFS cell does this workstation belong to? dulci.biostat.duke.edu
AFS uses an area of the disk to cache remote files for faster access.
This cache will be mounted on /var/cache/openafs. It is important
that the cache not overfill the partition it is located on. Often,
people find it useful to dedicate a partition to their AFS cache.
How large is your AFS cache (kB)? 50000
/afs generally contains an entry for each cell that a client can talk
to. Traditionally, these entries were generated by servers in the
client's home cell. However, OpenAFS clients can generate the
contents of /afs dynamically based on the contents of
/etc/openafs/CellServDB and DNS.
If you generate /afs dynamically, you may need to create
/etc/openafs/CellAlias to include aliases for common cells. DO NOT
SELECT THIS OPTION IF THIS MACHINE IS THE FIRST DATABASE SERVER IN A
NEW CELL .
Dynamically generate the contents of /afs? no
Selecting previously deselected package openafs-client.
(Reading database ... 81267 files and directories currently installed.)
Unpacking openafs-client (from .../openafs-client_1.3.81-3sarge1_i386.deb) ...
Selecting previously deselected package openafs-fileserver.
Unpacking openafs-fileserver (from .../openafs-fileserver_1.3.81-3sarge1_i386.deb) ...
Selecting previously deselected package openafs-dbserver.
Unpacking openafs-dbserver (from .../openafs-dbserver_1.3.81-3sarge1_i386.deb) ...
Selecting previously deselected package openafs-krb5.
Unpacking openafs-krb5 (from .../openafs-krb5_1.3-10.1_i386.deb) ...
Setting up openafs-client (1.3.81-3sarge1) ...
Configuring openafs-client
--------------------------
AFS uses the file /etc/openafs/CellServDB to hold the list of servers
that should be contacted to find parts of a cell. The cell you claim
this workstation belongs to is not in that file. Enter the host names
of the database servers separated by spaces. IMPORTANT: If you are
creating a new cell and this machine is to be a database server in
that cell, only enter this machine's name; add the other servers later
after they are functioning. Also, do not enable the AFS client to
start at boot on this server until the cell is configured. When you
are ready you can edit /etc/openafs/afs.conf.client to enable the
client.
What hosts are DB servers for your home cell? riverside.dulci.biostat.duke.edu
Should the Openafs filesystem be started and mounted at boot?
Normally, most users who install the openafs-client package expect to
run it at boot. However, if you are planning on setting up a new cell
or are on a laptop, you may not want it started at boot time. If you
choose not to start AFS at boot , run /etc/init.d/openafs-client
force-start to start the client when you wish to run it.
Run Openafs client now and at boot? no
Setting up openafs-fileserver (1.3.81-3sarge1) ...
Starting AFS Server: bosserver.
Setting up openafs-dbserver (1.3.81-3sarge1) ...
Setting up openafs-krb5 (1.3-10.1) ...
riverside:/home/faheem# kadmin.local
Authenticating as principal root/admin@DULCI.BIOSTAT.DUKE.EDU with password.
kadmin.local: addprinc -randkey -e des-cbc-crc:v4 afs
WARNING: no policy specified for afs@DULCI.BIOSTAT.DUKE.EDU; defaulting to no policy
Principal "afs@DULCI.BIOSTAT.DUKE.EDU" created.
kadmin.local: ktadd -k /tmp/afs.keytab -e des-cbc-crc:v4 afs
Entry for principal afs with kvno 3, encryption type DES cbc mode with CRC-32 added to keytab WRFILE:/tmp/afs.keytab.
kadmin.local: getprinc afs
Principal: afs@DULCI.BIOSTAT.DUKE.EDU
Expiration date: [never]
Last password change: Wed Aug 24 03:09:42 EDT 2005
Password expiration date: [none]
Maximum ticket life: 0 days 10:00:00
Maximum renewable life: 7 days 00:00:00
Last modified: Wed Aug 24 03:09:42 EDT 2005 (root/admin@DULCI.BIOSTAT.DUKE.EDU)
Last successful authentication: [never]
Last failed authentication: [never]
Failed password attempts: 0
Number of keys: 1
Key: vno 3, DES cbc mode with CRC-32, no salt
Attributes:
Policy: [none]
kadmin.local: exit
riverside:/home/faheem# asetkey add <kvno> /tmp/afs.keytab afs
riverside:/home/faheem# dd if=/dev/zero of=/var/lib/openafs/vicepa bs=1024k count=32
32+0 records in
32+0 records out
33554432 bytes transferred in 0.093776 seconds (357814258 bytes/sec)
riverside:/home/faheem# mke2fs /var/lib/openafs/vicepa
mke2fs 1.37 (21-Mar-2005)
/var/lib/openafs/vicepa is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
8192 inodes, 32768 blocks
1638 blocks (5.00%) reserved for the super user
First data block=1
4 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
riverside:/home/faheem# mkdir /vicepa
riverside:/home/faheem# mount -oloop /var/lib/openafs/vicepa /vicepa
riverside:/home/faheem# afs-newcell
Prerequisites
In order to set up a new AFS cell, you must meet the following:
1) You need a working Kerberos realm with Kerberos4 support. You
should install Heimdal with Kth-kerberos compatibility or MIT
Kerberos5.
2) You need to create the single-DES AFS key and load it into
/etc/openafs/server/KeyFile. If your cell's name is the same as
your Kerberos realm then create a principal called afs. Otherwise,
create a principal called afs/cellname in your realm. The cell
name should be all lower case, unlike Kerberos realms which are all
upper case. You can use asetkey from the openafs-krb5 package, or
if you used AFS3 salt to create the key, the bos addkey command.
3) This machine should have a filesystem mounted on /vicepa. If you
do not have a free partition, then create a large file by using dd
to extract bytes from /dev/zero. Create a filesystem on this file
and mount it using -oloop.
4) You will need an administrative principal created in a Kerberos
realm. This principal will be added to susers and
system:administrators and thus will be able to run administrative
commands. Generally the user is a root or admin instance of some
administrative user. For example if jruser is an administrator then
it would be reasonable to create jruser/root (or jruser/admin) and
specify that as the user to be added in this script.
5) The AFS client must not be running on this workstation. It will be
at the end of this script.
Do you meet these requirements? [y/n] y
If the fileserver is not running, this may hang for 30 seconds.
/etc/init.d/openafs-fileserver stop
Stopping AFS Server: bos: could not find entry (can't find cell '<default>' in cell database)
bosserver.
What administrative principal should be used? faheem/admin
/etc/openafs/server/CellServDB already exists, renaming to .old
/etc/init.d/openafs-fileserver start
Starting AFS Server: bosserver.
bos adduser riverside.dulci.biostat.duke.edu faheem.admin -localauth
pt_util: /var/lib/openafs/db/prdb.DB0: Bad UBIK_MAGIC. Is 0 should be 354545
Ubik Version is: 2.0
Error while creating system:administrators: Entry for id already exists
pt_util: Ubik Version number changed during execution.
Old Version = 2.0, new version = 33554432.0
bos create riverside.dulci.biostat.duke.edu ptserver simple /usr/lib/openafs/ptserver -localauth
bos create riverside.dulci.biostat.duke.edu vlserver simple /usr/lib/openafs/vlserver -localauth
bos create riverside.dulci.biostat.duke.edu fs fs -cmd /usr/lib/openafs/fileserver -cmd /usr/lib/openafs/volserver -cmd /usr/lib/openafs/salvager -localauth
Waiting for database elections: done.
vos create riverside.dulci.biostat.duke.edu a root.afs -localauth
Volume 536870912 created on partition /vicepa of riverside.dulci.biostat.duke.edu
/etc/init.d/openafs-client force-start
Starting AFS services: afsd: All AFS daemons started.
afsd.
Now, get tokens as faheem/admin in the dulci.biostat.duke.edu cell.
Then, run afs-rootvol.
riverside:/home/faheem# bos status localhost -local
Instance ptserver, currently running normally.
Instance vlserver, currently running normally.
Instance fs, currently running normally.
Auxiliary status is: file server running.
riverside:/home/faheem# kinit faheem/admin@DULCI.BIOSTAT.DUKE.EDU
Password for faheem/admin@DULCI.BIOSTAT.DUKE.EDU:
riverside:/home/faheem# aklog dulci.biostat.duke.edu -k DULCI.BIOSTAT.DUKE.EDU
riverside:/home/faheem# tokens
Tokens held by the Cache Manager:
User's (AFS ID 1) tokens for afs@dulci.biostat.duke.edu [Expires Aug 24 13:22]
--End of list--
riverside:/home/faheem# boss status riverside
Instance ptserver, currently running normally.
Instance vlserver, currently running normally.
Instance fs, currently running normally.
Auxiliary status is: file server running.
riverside:/home/faheem# afs-rootvol
Prerequisites
In order to set up the root.afs volume, you must meet the following
pre-conditions:
1) The cell must be configured, running a database server with a
volume location and protection server. The afs-newcell script will
set up these services.
2) You must be logged into the cell with tokens in for a user in
system:administrators and with a principal that is in the UserList
file of the servers in the cell.
3) You need a fileserver in the cell with partitions mounted and a
root.afs volume created. Presumably, it has no volumes on it,
although the script will work so long as nothing besides root.afs
exists. The afs-newcell script will set up the file server.
4) The AFS client must be running pointed at the new cell.
Do you meet these conditions? (y/n) y
You will need to select a server (hostname) and AFS partition on which to
create the root volumes.
What AFS Server should volumes be placed on? riverside.dulci.biostat.duke.edu
What partition? [a]
vos create riverside.dulci.biostat.duke.edu a root.cell -localauth
Volume 536870915 created on partition /vicepa of riverside.dulci.biostat.duke.edu
fs sa /afs system:anyuser rl
fs mkm /afs/dulci.biostat.duke.edu root.cell -cell dulci.biostat.duke.edu -fast || true
fs mkm /afs/grand.central.org root.cell -cell grand.central.org -fast || true
fs mkm /afs/wu-wien.ac.at root.cell -cell wu-wien.ac.at -fast || true
fs mkm /afs/hephy.at root.cell -cell hephy.at -fast || true
fs mkm /afs/itp.tugraz.at root.cell -cell itp.tugraz.at -fast || true
fs mkm /afs/cern.ch root.cell -cell cern.ch -fast || true
fs mkm /afs/ams.cern.ch root.cell -cell ams.cern.ch -fast || true
fs mkm /afs/ethz.ch root.cell -cell ethz.ch -fast || true
fs mkm /afs/psi.ch root.cell -cell psi.ch -fast || true
fs mkm /afs/extundo.com root.cell -cell extundo.com -fast || true
fs mkm /afs/mekinok.com root.cell -cell mekinok.com -fast || true
fs mkm /afs/membrain.com root.cell -cell membrain.com -fast || true
fs mkm /afs/midnightlinux.com root.cell -cell midnightlinux.com -fast || true
fs mkm /afs/setfilepointer.com root.cell -cell setfilepointer.com -fast || true
fs mkm /afs/sodre.cx root.cell -cell sodre.cx -fast || true
fs mkm /afs/desy.de root.cell -cell desy.de -fast || true
fs mkm /afs/gppc.de root.cell -cell gppc.de -fast || true
fs mkm /afs/ifh.de root.cell -cell ifh.de -fast || true
fs mkm /afs/lrz-muenchen.de root.cell -cell lrz-muenchen.de -fast || true
fs mkm /afs/ipp-garching.mpg.de root.cell -cell ipp-garching.mpg.de -fast || true
fs mkm /afs/mpe.mpg.de root.cell -cell mpe.mpg.de -fast || true
fs mkm /afs/i1.informatik.rwth-aachen.de root.cell -cell i1.informatik.rwth-aachen.de -fast || true
fs mkm /afs/tu-bs.de root.cell -cell tu-bs.de -fast || true
fs mkm /afs/tu-chemnitz.de root.cell -cell tu-chemnitz.de -fast || true
fs mkm /afs/e18.ph.tum.de root.cell -cell e18.ph.tum.de -fast || true
fs mkm /afs/uni-bonn.de root.cell -cell uni-bonn.de -fast || true
fs mkm /afs/atlass01.physik.uni-bonn.de root.cell -cell atlass01.physik.uni-bonn.de -fast || true
fs mkm /afs/uni-freiburg.de root.cell -cell uni-freiburg.de -fast || true
fs mkm /afs/physik.uni-freiburg.de root.cell -cell physik.uni-freiburg.de -fast || true
fs mkm /afs/urz.uni-heidelberg.de root.cell -cell urz.uni-heidelberg.de -fast || true
fs mkm /afs/uni-hohenheim.de root.cell -cell uni-hohenheim.de -fast || true
fs mkm /afs/rz.uni-jena.de root.cell -cell rz.uni-jena.de -fast || true
fs mkm /afs/meteo.uni-koeln.de root.cell -cell meteo.uni-koeln.de -fast || true
fs mkm /afs/rrz.uni-koeln.de root.cell -cell rrz.uni-koeln.de -fast || true
fs mkm /afs/physik.uni-mainz.de root.cell -cell physik.uni-mainz.de -fast || true
fs mkm /afs/uni-mannheim.de root.cell -cell uni-mannheim.de -fast || true
fs mkm /afs/physik.uni-wuppertal.de root.cell -cell physik.uni-wuppertal.de -fast || true
fs mkm /afs/s-et.aau.dk root.cell -cell s-et.aau.dk -fast || true
fs mkm /afs/ies.auc.dk root.cell -cell ies.auc.dk -fast || true
fs mkm /afs/asu.edu root.cell -cell asu.edu -fast || true
fs mkm /afs/hep.caltech.edu root.cell -cell hep.caltech.edu -fast || true
fs mkm /afs/clarkson.edu root.cell -cell clarkson.edu -fast || true
fs mkm /afs/andrew.cmu.edu root.cell -cell andrew.cmu.edu -fast || true
fs mkm /afs/club.cc.cmu.edu root.cell -cell club.cc.cmu.edu -fast || true
fs mkm /afs/chem.cmu.edu root.cell -cell chem.cmu.edu -fast || true
fs mkm /afs/cs.cmu.edu root.cell -cell cs.cmu.edu -fast || true
fs mkm /afs/ece.cmu.edu root.cell -cell ece.cmu.edu -fast || true
fs mkm /afs/scotch.ece.cmu.edu root.cell -cell scotch.ece.cmu.edu -fast || true
fs mkm /afs/qatar.cmu.edu root.cell -cell qatar.cmu.edu -fast || true
fs mkm /afs/sbp.ri.cmu.edu root.cell -cell sbp.ri.cmu.edu -fast || true
fs mkm /afs/msc.cornell.edu root.cell -cell msc.cornell.edu -fast || true
fs mkm /afs/dbic.dartmouth.edu root.cell -cell dbic.dartmouth.edu -fast || true
fs mkm /afs/northstar.dartmouth.edu root.cell -cell northstar.dartmouth.edu -fast || true
fs mkm /afs/eecs.harvard.edu root.cell -cell eecs.harvard.edu -fast || true
fs mkm /afs/iastate.edu root.cell -cell iastate.edu -fast || true
fs mkm /afs/athena.mit.edu root.cell -cell athena.mit.edu -fast || true
fs mkm /afs/dev.mit.edu root.cell -cell dev.mit.edu -fast || true
fs mkm /afs/net.mit.edu root.cell -cell net.mit.edu -fast || true
fs mkm /afs/sipb.mit.edu root.cell -cell sipb.mit.edu -fast || true
fs mkm /afs/msu.edu root.cell -cell msu.edu -fast || true
fs mkm /afs/nd.edu root.cell -cell nd.edu -fast || true
fs mkm /afs/pitt.edu root.cell -cell pitt.edu -fast || true
fs mkm /afs/cs.pitt.edu root.cell -cell cs.pitt.edu -fast || true
fs mkm /afs/psc.edu root.cell -cell psc.edu -fast || true
fs mkm /afs/scoobydoo.psc.edu root.cell -cell scoobydoo.psc.edu -fast || true
fs mkm /afs/cede.psu.edu root.cell -cell cede.psu.edu -fast || true
fs mkm /afs/rose-hulman.edu root.cell -cell rose-hulman.edu -fast || true
fs mkm /afs/cs.rose-hulman.edu root.cell -cell cs.rose-hulman.edu -fast || true
fs mkm /afs/rpi.edu root.cell -cell rpi.edu -fast || true
fs mkm /afs/hep.sc.edu root.cell -cell hep.sc.edu -fast || true
fs mkm /afs/cs.stanford.edu root.cell -cell cs.stanford.edu -fast || true
fs mkm /afs/ir.stanford.edu root.cell -cell ir.stanford.edu -fast || true
fs mkm /afs/slac.stanford.edu root.cell -cell slac.stanford.edu -fast || true
fs mkm /afs/cats.ucsc.edu root.cell -cell cats.ucsc.edu -fast || true
fs mkm /afs/acm.uiuc.edu root.cell -cell acm.uiuc.edu -fast || true
fs mkm /afs/ncsa.uiuc.edu root.cell -cell ncsa.uiuc.edu -fast || true
fs mkm /afs/umbc.edu root.cell -cell umbc.edu -fast || true
fs mkm /afs/glue.umd.edu root.cell -cell glue.umd.edu -fast || true
fs mkm /afs/wam.umd.edu root.cell -cell wam.umd.edu -fast || true
fs mkm /afs/umich.edu root.cell -cell umich.edu -fast || true
fs mkm /afs/atlas.umich.edu root.cell -cell atlas.umich.edu -fast || true
fs mkm /afs/citi.umich.edu root.cell -cell citi.umich.edu -fast || true
fs mkm /afs/lsa.umich.edu root.cell -cell lsa.umich.edu -fast || true
fs mkm /afs/math.lsa.umich.edu root.cell -cell math.lsa.umich.edu -fast || true
fs mkm /afs/umr.edu root.cell -cell umr.edu -fast || true
fs mkm /afs/physics.unc.edu root.cell -cell physics.unc.edu -fast || true
fs mkm /afs/uncc.edu root.cell -cell uncc.edu -fast || true
fs mkm /afs/eng.utah.edu root.cell -cell eng.utah.edu -fast || true
fs mkm /afs/cs.uwm.edu root.cell -cell cs.uwm.edu -fast || true
fs mkm /afs/cs.wisc.edu root.cell -cell cs.wisc.edu -fast || true
fs mkm /afs/engr.wisc.edu root.cell -cell engr.wisc.edu -fast || true
fs mkm /afs/hep.wisc.edu root.cell -cell hep.wisc.edu -fast || true
fs mkm /afs/physics.wisc.edu root.cell -cell physics.wisc.edu -fast || true
fs mkm /afs/ifca.unican.es root.cell -cell ifca.unican.es -fast || true
fs mkm /afs/ific.uv.es root.cell -cell ific.uv.es -fast || true
fs mkm /afs/biocenter.helsinki.fi root.cell -cell biocenter.helsinki.fi -fast || true
fs mkm /afs/dapnia.saclay.cea.fr root.cell -cell dapnia.saclay.cea.fr -fast || true
fs mkm /afs/in2p3.fr root.cell -cell in2p3.fr -fast || true
fs mkm /afs/anl.gov root.cell -cell anl.gov -fast || true
fs mkm /afs/rhic.bnl.gov root.cell -cell rhic.bnl.gov -fast || true
fs mkm /afs/usatlas.bnl.gov root.cell -cell usatlas.bnl.gov -fast || true
fs mkm /afs/fnal.gov root.cell -cell fnal.gov -fast || true
fs mkm /afs/ic-afs.arc.nasa.gov root.cell -cell ic-afs.arc.nasa.gov -fast || true
fs mkm /afs/jpl.nasa.gov root.cell -cell jpl.nasa.gov -fast || true
fs mkm /afs/nersc.gov root.cell -cell nersc.gov -fast || true
fs mkm /afs/bme.hu root.cell -cell bme.hu -fast || true
fs mkm /afs/caspur.it root.cell -cell caspur.it -fast || true
fs mkm /afs/fusione.it root.cell -cell fusione.it -fast || true
fs mkm /afs/icemb.it root.cell -cell icemb.it -fast || true
fs mkm /afs/infn.it root.cell -cell infn.it -fast || true
fs mkm /afs/kloe.infn.it root.cell -cell kloe.infn.it -fast || true
fs mkm /afs/le.infn.it root.cell -cell le.infn.it -fast || true
fs mkm /afs/lnf.infn.it root.cell -cell lnf.infn.it -fast || true
fs mkm /afs/lngs.infn.it root.cell -cell lngs.infn.it -fast || true
fs mkm /afs/pi.infn.it root.cell -cell pi.infn.it -fast || true
fs mkm /afs/psm.it root.cell -cell psm.it -fast || true
fs mkm /afs/tgrid.it root.cell -cell tgrid.it -fast || true
fs mkm /afs/ictp.trieste.it root.cell -cell ictp.trieste.it -fast || true
fs mkm /afs/ing.uniroma1.it root.cell -cell ing.uniroma1.it -fast || true
fs mkm /afs/vn.uniroma3.it root.cell -cell vn.uniroma3.it -fast || true
fs mkm /afs/italia root.cell -cell italia -fast || true
fs mkm /afs/cmf.nrl.navy.mil root.cell -cell cmf.nrl.navy.mil -fast || true
fs mkm /afs/lcp.nrl.navy.mil root.cell -cell lcp.nrl.navy.mil -fast || true
fs mkm /afs/es.net root.cell -cell es.net -fast || true
fs mkm /afs/laroia.net root.cell -cell laroia.net -fast || true
fs mkm /afs/sinenomine.net root.cell -cell sinenomine.net -fast || true
fs mkm /afs/slackers.net root.cell -cell slackers.net -fast || true
fs mkm /afs/nikhef.nl root.cell -cell nikhef.nl -fast || true
fs mkm /afs/1ts.org root.cell -cell 1ts.org -fast || true
fs mkm /afs/bazquux.org root.cell -cell bazquux.org -fast || true
fs mkm /afs/coed.org root.cell -cell coed.org -fast || true
fs mkm /afs/dementia.org root.cell -cell dementia.org -fast || true
fs mkm /afs/firelion.org root.cell -cell firelion.org -fast || true
fs mkm /afs/hackish.org root.cell -cell hackish.org -fast || true
fs mkm /afs/idahofuturetruck.org root.cell -cell idahofuturetruck.org -fast || true
fs mkm /afs/nimlabs.org root.cell -cell nimlabs.org -fast || true
fs mkm /afs/nomh.org root.cell -cell nomh.org -fast || true
fs mkm /afs/oc7.org root.cell -cell oc7.org -fast || true
fs mkm /afs/openafs.org root.cell -cell openafs.org -fast || true
fs mkm /afs/e.kth.se root.cell -cell e.kth.se -fast || true
fs mkm /afs/hallf.kth.se root.cell -cell hallf.kth.se -fast || true
fs mkm /afs/isk.kth.se root.cell -cell isk.kth.se -fast || true
fs mkm /afs/it.kth.se root.cell -cell it.kth.se -fast || true
fs mkm /afs/md.kth.se root.cell -cell md.kth.se -fast || true
fs mkm /afs/mech.kth.se root.cell -cell mech.kth.se -fast || true
fs mkm /afs/nada.kth.se root.cell -cell nada.kth.se -fast || true
fs mkm /afs/pdc.kth.se root.cell -cell pdc.kth.se -fast || true
fs mkm /afs/stacken.kth.se root.cell -cell stacken.kth.se -fast || true
fs mkm /afs/syd.kth.se root.cell -cell syd.kth.se -fast || true
fs mkm /afs/physto.se root.cell -cell physto.se -fast || true
fs mkm /afs/sanchin.se root.cell -cell sanchin.se -fast || true
fs mkm /afs/su.se root.cell -cell su.se -fast || true
fs mkm /afs/f9.ijs.si root.cell -cell f9.ijs.si -fast || true
fs mkm /afs/p-ng.si root.cell -cell p-ng.si -fast || true
fs mkm /afs/phy.bris.ac.uk root.cell -cell phy.bris.ac.uk -fast || true
fs mkm /afs/hep.man.ac.uk root.cell -cell hep.man.ac.uk -fast || true
fs mkm /afs/rl.ac.uk root.cell -cell rl.ac.uk -fast || true
fs sa /afs/dulci.biostat.duke.edu system:anyuser rl
fs mkm /afs/.dulci.biostat.duke.edu root.cell -cell dulci.biostat.duke.edu -rw
fs mkm /afs/.root.afs root.afs -rw
vos create riverside.dulci.biostat.duke.edu a user -localauth
Volume 536870918 created on partition /vicepa of riverside.dulci.biostat.duke.edu
fs mkm /afs/dulci.biostat.duke.edu/user user
fs sa /afs/dulci.biostat.duke.edu/user system:anyuser rl
vos create riverside.dulci.biostat.duke.edu a service -localauth
Volume 536870921 created on partition /vicepa of riverside.dulci.biostat.duke.edu
fs mkm /afs/dulci.biostat.duke.edu/service service
fs sa /afs/dulci.biostat.duke.edu/service system:anyuser rl
ln -s dulci.biostat.duke.edu /afs/dulci
ln -s .dulci.biostat.duke.edu /afs/.dulci
vos addsite riverside.dulci.biostat.duke.edu a root.afs -localauth
Added replication site riverside.dulci.biostat.duke.edu /vicepa for volume root.afs
vos addsite riverside.dulci.biostat.duke.edu a root.cell -localauth
Added replication site riverside.dulci.biostat.duke.edu /vicepa for volume root.cell
vos release root.afs -localauth
Released volume root.afs successfully
vos release root.cell -localauth
Released volume root.cell successfully
riverside:/home/faheem# cd /afs/dulci.biostat.duke.edu/
riverside:/afs/dulci.biostat.duke.edu# ls
service user

229
src/packaging/Debian/control
View File

@ -1,229 +0,0 @@
Source: openafs
Section: net
Priority: optional
Maintainer: Russ Allbery <rra@debian.org>
Uploaders: Sam Hartman <hartmans@debian.org>
Build-Depends: debhelper (>= 8), autoconf, automake, bison, comerr-dev,
cpio, dblatex, dkms (>= 2.1.1.1), docbook-xsl, doxygen, flex,
libfuse-dev, libkrb5-dev, libncurses5-dev, libpam0g-dev, libxml2-utils,
perl, pkg-config, xsltproc
Standards-Version: 3.9.1
Homepage: http://www.openafs.org/
Vcs-Git: git://git.debian.org/git/pkg-k5-afs/openafs.git
Vcs-Browser: http://git.debian.org/?p=pkg-k5-afs/openafs.git
Package: openafs-client
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: lsof, openafs-modules-dkms (>= ${source:Version})
| openafs-modules-source (>= ${source:Version})
| openafs-modules3
Suggests: openafs-doc, openafs-krb5
Conflicts: arla
Breaks: openafs-modules1, openafs-modules2
Description: AFS distributed filesystem client support
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides basic client support to mount and manipulate
AFS. If your site uses Kerberos v5 authentication for AFS, you will also
want to install openafs-krb5.
Package: openafs-fuse
Priority: extra
Architecture: alpha amd64 arm armel i386 ia64 lpia powerpc ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends},
openafs-client (= ${binary:Version})
Description: AFS distributed file system experimental FUSE client
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides an experimental FUSE implementation of the AFS
client as afsd.fuse. This currently only provides read-only access to
AFS, doesn't work with all of the normal AFS client programs, and must be
started manually, but may be of interest in situations where read-only
access is sufficient and the kernel module cannot be built.
Package: openafs-kpasswd
Priority: extra
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends},
openafs-client (= ${binary:Version})
Conflicts: krb5-user, heimdal-clients, kerberos4kth-clients
Description: AFS distributed filesystem old password changing
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides kpasswd and kas, utilities needed by the OpenAFS
kaserver to create users and change passwords. Only install this package
if you are already using kaserver; generally you should not install this
package for new cells or for cells using Kerberos v5.
Package: openafs-fileserver
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, openafs-client, lsb-base
Recommends: ntp | time-daemon
Suggests: openafs-doc
Description: AFS distributed filesystem file server
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the AFS fileserver binaries. It should be
installed on any machine that will export files into AFS.
Package: openafs-dbserver
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${perl:Depends}, ${misc:Depends},
openafs-fileserver, openafs-client (= ${binary:Version})
Suggests: openafs-doc
Description: AFS distributed filesystem database server
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides AFS database server binaries. It should be
installed on the servers that will act as volume location and
protection servers.
Package: openafs-doc
Section: doc
Architecture: all
Depends: ${misc:Depends}
Description: AFS distributed filesystem documentation
AFS is a distributed filesystem allowing cross-platform sharing of files
among multiple computers. Facilities are provided for access control,
authentication, backup and administrative management.
.
This package contains the OpenAFS user's and reference manuals, some
protocol documentation, and other OpenAFS documentation.
Package: openafs-krb5
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: openafs-client (<< 1.4.7.dfsg1-1)
Description: AFS distributed filesystem Kerberos 5 integration
AFS is a distributed filesystem allowing cross-platform sharing of files
among multiple computers. Facilities are provided for access control,
authentication, backup and administrative management.
.
This package provides aklog, a utility for authenticating to AFS using
Kerberos 5. It also provides asetkey, a utility to set AFS server keys
from a Kerberos keytab, and ka-forwarder, a utility to forward kaserver
requests to a KDC using fakeka.
Package: libkopenafs1
Section: libs
Architecture: alpha amd64 arm armel i386 ia64 lpia powerpc ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: AFS distributed file system runtime library (PAGs)
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the shared library implementing an interface to
manipulating AFS process authentication groups (PAGs). It provides the
a subset of the interface provided by the Heimdal libkafs library.
Package: libafsauthent1
Section: libs
Architecture: alpha amd64 arm armel i386 ia64 lpia powerpc ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: AFS distributed file system runtime library (authentication)
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the shared library implementing AFS client
authentication and token management.
Package: libafsrpc1
Section: libs
Architecture: alpha amd64 arm armel i386 ia64 lpia powerpc ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: AFS distributed file system runtime library (RPC layer)
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the shared library implementing the Rx protocol and
other AFS RPC functionality.
Package: libopenafs-dev
Section: libdevel
Priority: extra
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends},
libafsauthent1 (= ${binary:Version}), libafsrpc1 (= ${binary:Version}),
libkopenafs1 (= ${binary:Version}),
Suggests: openafs-doc
Conflicts: arla-dev, liblwp-dev
Description: AFS distributed filesystem development libraries
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides static development libraries and headers
needed to compile AFS applications.
Package: openafs-modules-source
Section: kernel
Priority: extra
Architecture: all
Depends: ${misc:Depends}, debhelper (>= 8),
module-assistant | kernel-package, perl
Recommends: openafs-client (>= ${source:Version})
Description: AFS distributed filesystem kernel module source
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the source to the AFS kernel module in a form
suitable for use by module-assistant or kernel-package.
Package: openafs-modules-dkms
Section: kernel
Priority: extra
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends}, dkms, libc6-dev
Recommends: openafs-client (>= ${source:Version})
Description: AFS distributed filesystem kernel module DKMS source
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package contains the source for the AFS kernel module, packaged with
approriate configuration for DKMS to build new modules dynamically.
Package: libpam-openafs-kaserver
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Section: admin
Priority: extra
Depends: ${shlibs:Depends}, ${misc:Depends},
openafs-client (= ${binary:Version})
Description: AFS distributed filesystem kaserver PAM module
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides a PAM module for existing sites using the AFS
kaserver for authentication. New sites should use a Kerberos v5
implementation, a Kerberos v5 PAM module such as libpam-krb5, and
libpam-afs-session.
Package: openafs-dbg
Section: debug
Priority: extra
Architecture: alpha amd64 arm armel i386 ia64 powerpc powerpcspe ppc64 s390 s390x sparc
Depends: ${misc:Depends}, openafs-fileserver (= ${binary:Version})
| openafs-dbserver (= ${binary:Version})
Description: AFS distributed filesystem debugging information
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package contains the debugging information for the OpenAFS
server binaries (the openafs-fileserver and openafs-dbserver packages).

433
src/packaging/Debian/copyright
View File

@ -1,433 +0,0 @@
This package was debianized by Sam Hartman <hartmans@debian.org> on
Fri, 3 Nov 2000 23:41:41 -0500.
It was downloaded via Git from:
git://git.openafs.org/openafs.git
Upstream Maintainers:
openafs-gatekeepers@openafs.org
The upstream source is generated from a Git tag for the corresponding
upstream release, but with the WINNT directory removed to reduces the size
of the upstream tarball by about 8MB.
The source package contains the OpenAFS documentation as distributed by
the OpenAFS project, some of which does not include the original source.
These documents were originally created using TeX internally by Transarc,
the original authors of AFS. By the time that AFS was released as free
software by IBM after acquiring Transarc, the original source could no
longer be found. It has apparently been lost over the years.
Although these HTML and PDF files would not normally be considered source,
they're all that's available until they can be rewritten and updated in
some better format. They have been released under the IBM Public License
Version 1.0 (included below), the same license as the rest of OpenAFS.
Normally, this documentation could not be included in Debian without being
accompanied by the original TeX source and build tools under DFSG#2, but
under the circumstances, these files essentially are the source, as
they're all that anyone has.
These documents are being replaced by revised versions in DocBook and
Doxygen, with suitable source, and once that process is complete, the old
sourceless HTML and PDF documents will be removed. The documentation
installed in the openafs-doc package already includes only material built
from the new maintainable source.
Copyright:
Copyright 2000, International Business Machines Corporation and others.
All Rights Reserved.
IBM Public License Version 1.0
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF
THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of International Business Machines Corporation ("IBM"),
the Original Program, and
b) in the case of each Contributor,
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and
are distributed by that particular Contributor. A Contribution
'originates' from a Contributor if it was added to the Program by
such Contributor itself or anyone acting on such Contributor's
behalf. Contributions do not include additions to the Program
which: (i) are separate modules of software distributed in
conjunction with the Program under their own license agreement,
and (ii) are not derivative works of the Program.
"Contributor" means IBM and any other entity that distributes the
Program.
"Licensed Patents " mean patent claims licensable by a Contributor
which are necessarily infringed by the use or sale of its Contribution
alone or when combined with the Program.
"Original Program" means the original version of the software
accompanying this Agreement as released by IBM, including source code,
object code and documentation, if any.
"Program" means the Original Program and Contributions.
"Recipient" means anyone who receives the Program under this
Agreement, including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free
copyright license to reproduce, prepare derivative works of,
publicly display, publicly perform, distribute and sublicense the
Contribution of such Contributor, if any, and such derivative
works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free patent
license under Licensed Patents to make, use, sell, offer to sell,
import and otherwise transfer the Contribution of such
Contributor, if any, in source code and object code form. This
patent license shall apply to the combination of the Contribution
and the Program if, at the time the Contribution is added by the
Contributor, such addition of the Contribution causes such
combination to be covered by the Licensed Patents. The patent
license shall not apply to any other combinations which include
the Contribution. No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the
licenses to its Contributions set forth herein, no assurances are
provided by any Contributor that the Program does not infringe the
patent or other intellectual property rights of any other entity.
Each Contributor disclaims any liability to Recipient for claims
brought by any other entity based on infringement of intellectual
property rights or otherwise. As a condition to exercising the
rights and licenses granted hereunder, each Recipient hereby
assumes sole responsibility to secure any other intellectual
property rights needed, if any. For example, if a third party
patent license is required to allow Recipient to distribute the
Program, it is Recipient's responsibility to acquire that license
before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient
copyright rights in its Contribution, if any, to grant the
copyright license set forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form
under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties
and conditions, express and implied, including warranties or
conditions of title and non-infringement, and implied warranties
or conditions of merchantability and fitness for a particular
purpose;
ii) effectively excludes on behalf of all Contributors all liability
for damages, including direct, indirect, special, incidental and
consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are
offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such
Contributor, and informs licensees how to obtain it in a
reasonable manner on or through a medium customarily used for
software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the
Program.
Each Contributor must include the following in a conspicuous location
in the Program:
Copyright © {date here}, International Business Machines Corporation
and others. All Rights Reserved.
In addition, each Contributor must identify itself as the originator
of its Contribution, if any, in a manner that reasonably allows
subsequent Recipients to identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain
responsibilities with respect to end users, business partners and the
like. While this license is intended to facilitate the commercial use
of the Program, the Contributor who includes the Program in a
commercial product offering should do so in a manner which does not
create potential liability for other Contributors. Therefore, if a
Contributor includes the Program in a commercial product offering,
such Contributor ("Commercial Contributor") hereby agrees to defend
and indemnify every other Contributor ("Indemnified Contributor")
against any losses, damages and costs (collectively "Losses") arising
from claims, lawsuits and other legal actions brought by a third party
against the Indemnified Contributor to the extent caused by the acts
or omissions of such Commercial Contributor in connection with its
distribution of the Program in a commercial product offering. The
obligations in this section do not apply to any claims or Losses
relating to any actual or alleged intellectual property infringement.
In order to qualify, an Indemnified Contributor must: a) promptly
notify the Commercial Contributor in writing of such claim, and b)
allow the Commercial Contributor to control, and cooperate with the
Commercial Contributor in, the defense and any related settlement
negotiations. The Indemnified Contributor may participate in any such
claim at its own expense.
For example, a Contributor might include the Program in a commercial
product offering, Product X. That Contributor is then a Commercial
Contributor. If that Commercial Contributor then makes performance
claims, or offers warranties related to Product X, those performance
claims and warranties are such Commercial Contributor's responsibility
alone. Under this section, the Commercial Contributor would have to
defend claims against the other Contributors related to those
performance claims and warranties, and if a court requires any other
Contributor to pay any damages as a result, the Commercial Contributor
must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
responsible for determining the appropriateness of using and
distributing the Program and assumes all risks associated with its
exercise of rights under this Agreement, including but not limited to
the risks and costs of program errors, compliance with applicable
laws, damage to or loss of data, programs or equipment, and
unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR
ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING
WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED
HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under
applicable law, it shall not affect the validity or enforceability of
the remainder of the terms of this Agreement, and without further
action by the parties hereto, such provision shall be reformed to the
minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor with
respect to a patent applicable to software (including a cross-claim or
counterclaim in a lawsuit), then any patent licenses granted by that
Contributor to such Recipient under this Agreement shall terminate as
of the date such litigation is filed. In addition, If Recipient
institutes patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Program
itself (excluding combinations of the Program with other software or
hardware) infringes such Recipient's patent(s), then such Recipient's
rights granted under Section 2(b) shall terminate as of the date such
litigation is filed.
All Recipient's rights under this Agreement shall terminate if it
fails to comply with any of the material terms or conditions of this
Agreement and does not cure such failure in a reasonable period of
time after becoming aware of such noncompliance. If all Recipient's
rights under this Agreement terminate, Recipient agrees to cease use
and distribution of the Program as soon as reasonably practicable.
However, Recipient's obligations under this Agreement and any licenses
granted by Recipient relating to the Program shall continue and
survive.
IBM may publish new versions (including revisions) of this Agreement
from time to time. Each new version of the Agreement will be given a
distinguishing version number. The Program (including Contributions)
may always be distributed subject to the version of the Agreement
under which it was received. In addition, after a new version of the
Agreement is published, Contributor may elect to distribute the
Program (including its Contributions) under the new version. No one
other than IBM has the right to modify this Agreement. Except as
expressly stated in Sections 2(a) and 2(b) above, Recipient receives
no rights or licenses to the intellectual property of any Contributor
under this Agreement, whether expressly, by implication, estoppel or
otherwise. All rights in the Program not expressly granted under this
Agreement are reserved.
This Agreement is governed by the laws of the State of New York and
the intellectual property laws of the United States of America. No
party to this Agreement will bring a legal action under this Agreement
more than one year after the cause of action arose. Each party waives
its rights to a jury trial in any resulting litigation.
Kerberos 5 ticket support in rxkad is subject to the following copyright:
/*
* Copyright (c) 1995, 1996, 1997, 2002 Kungliga Tekniska Högskolan
* (Royal Institute of Technology, Stockholm, Sweden).
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* 3. Neither the name of the Institute nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
Some code in rxkad/ticket5.c is subject to the following copyright:
/*
* Copyright 1992, 2002 by the Massachusetts Institute of Technology.
* All Rights Reserved.
*
* Export of this software from the United States of America may
* require a specific license from the United States Government.
* It is the responsibility of any person or organization contemplating
* export to obtain such a license before exporting.
*
* WITHIN THAT CONSTRAINT, permission to use, copy, modify, and
* distribute this software and its documentation for any purpose and
* without fee is hereby granted, provided that the above copyright
* notice appear in all copies and that both that copyright notice and
* this permission notice appear in supporting documentation, and that
* the name of M.I.T. not be used in advertising or publicity pertaining
* to distribution of the software without specific, written prior
* permission. Furthermore if you modify this software you must label
* your software as modified software and not distribute it in such a
* fashion that it might be confused with the original M.I.T. software.
* M.I.T. makes no representations about the suitability of
* this software for any purpose. It is provided "as is" without express
* or implied warranty.
*/
Some portions of Rx are subject to the following license:
/*
* Sun RPC is a product of Sun Microsystems, Inc. and is provided for
* unrestricted use provided that this legend is included on all tape
* media and as a part of the software program in whole or part. Users
* may copy or modify Sun RPC without charge, but are not authorized
* to license or distribute it to anyone else except as part of a product or
* program developed by the user or with the express written consent of
* Sun Microsystems, Inc.
*
* SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THE
* WARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
* PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.
*
* Sun RPC is provided with no support and without any obligation on the
* part of Sun Microsystems, Inc. to assist in its use, correction,
* modification or enhancement.
*
* SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE
* INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC
* OR ANY PART THEREOF.
*
* In no event will Sun Microsystems, Inc. be liable for any lost revenue
* or profits or other special, indirect and consequential damages, even if
* Sun has been advised of the possibility of such damages.
*
* Sun Microsystems, Inc.
* 2550 Garcia Avenue
* Mountain View, California 94043
*/
ka-forwarder was taken from the AFS/Kerberos 5 Migration Kit, to which it
was donated by Jeffrey T. Hutzelman. It is covered under the following
license:
/*
* Copyright (c) 1993 Carnegie Mellon University
* All Rights Reserved.
*
* Permission to use, copy, modify and distribute this software and its
* documentation is hereby granted, provided that both the copyright
* notice and this permission notice appear in all copies of the
* software, derivative works or modified versions, and any portions
* thereof, and that both notices appear in supporting documentation.
*
* CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
* CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
* ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
*
* Carnegie Mellon requests users of this software to return to
*
* Software Distribution Coordinator or Software_Distribution@CS.CMU.EDU
* School of Computer Science
* Carnegie Mellon University
* Pittsburgh PA 15213-3890
*
* any improvements or extensions that they make and grant Carnegie Mellon
* the rights to redistribute these changes.
*/
src/afs/LINUX/osi_flush.s included code under IBM Public License with
permission of the author, Paul MacKerras.
Personal contributions made by Jason Edgecombe
<jason@rampaginggeek.com> that refer to the "BSD license" are subject
to the following license:
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above
copyright notice, this list of conditions and the following
disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the name of OpenAFS nor the names of its
contributors may be used to endorse or promote products
derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

47
src/packaging/Debian/import-upstream
View File

@ -1,47 +0,0 @@
#!/bin/sh
#
# This script is used rather than git-import-orig to import a new upstream
# tarball. It does essentially the same work as git-import-orig -- take the
# contents of the tarball and commit it to the upstream branch and then tag it
# with a new upstream/* tag -- but it records that commit as a merge commit
# between the upstream branch and another tag.
#
# The purpose of this procedure is to have the imported tarball look to Git
# like a merge between upstream's tagged Git tree corresponding to that
# tarball and our upstream branch. This lets things like git cherry-pick work
# properly against upstream's release branch.
#
# This script assumes that the upstream tarball has already had non-DFSG
# material removed.
#
# Written by Sam Hartman <hartmans@debian.org> for krb5
# Adopted for openafs by Russ Allbery <rra@debian.org>
set -e
if [ $# -ne 3 ] ; then
echo "Usage: import-upstream <tarball> <upstream-tag> <local-tag>" >&2
exit 2
fi
tarball="$1"
upstream="$2"
tag="$3"
# Unpack the tarball.
dir=$(basename $(tar tzf "$tarball" | head -1))
tar xzf "$tarball"
# Add the tarball to the current index and then use that to create a tree
# object corresponding to the contents of that directory. Then, use
# commit-tree to commit that to the repository.
git add -f "$dir"
tree=$(git write-tree --prefix="$dir"/)
commit=$(echo "Imported upstream tag $upstream via tarball" | \
git commit-tree "$tree" -p upstream-1.5 -p $(git rev-list -n1 "$upstream"))
# Now that we have a commit, repoint upstream at that commit, tag it, and then
# remove the unpacked upstream tarball from our index.
git branch -f upstream-1.5 "$commit"
git tag "$tag" "$commit"
git rm -q -r -f "$dir"
rm -rf "$dir"

1
src/packaging/Debian/libafsauthent1.install
View File

@ -1 +0,0 @@
debian/tmp/usr/lib/libafsauthent.so.*

80
src/packaging/Debian/libafsauthent1.symbols
View File

@ -1,80 +0,0 @@
libafsauthent.so.1 libafsauthent1 #MINVER#
afsconf_AddKey@Base 1.5.75
afsconf_AddUser@Base 1.5.75
afsconf_CellApply@Base 1.5.75
afsconf_CheckAuth@Base 1.5.75
afsconf_ClientAuth@Base 1.5.75
afsconf_ClientAuthSecure@Base 1.5.75
afsconf_Close@Base 1.5.75
afsconf_CheckRestrictedQuery@Base 1.5.75
afsconf_DeleteKey@Base 1.5.75
afsconf_DeleteUser@Base 1.5.75
afsconf_GetCellInfo@Base 1.5.75
afsconf_GetKey@Base 1.5.75
afsconf_GetKeys@Base 1.5.75
afsconf_GetLatestKey@Base 1.5.75
afsconf_GetLocalCell@Base 1.5.75
afsconf_GetNoAuthFlag@Base 1.5.75
afsconf_GetNthUser@Base 1.5.75
afsconf_IntGetKeys@Base 1.5.75
afsconf_Open@Base 1.5.75
afsconf_ServerAuth@Base 1.5.75
afsconf_SetCellInfo@Base 1.5.75
afsconf_SetNoAuthFlag@Base 1.5.75
afsconf_SuperUser@Base 1.5.75
ka_AuthServerConn@Base 1.5.75
ka_Authenticate@Base 1.5.75
ka_CellConfig@Base 1.5.75
ka_CellToRealm@Base 1.5.75
ka_ChangePassword@Base 1.5.75
ka_ExpandCell@Base 1.5.75
ka_ExplicitCell@Base 1.5.75
ka_GetAdminToken@Base 1.5.75
ka_GetAuthToken@Base 1.5.75
ka_GetSecurity@Base 1.5.75
ka_GetServerToken@Base 1.5.75
ka_GetServers@Base 1.5.75
ka_GetToken@Base 1.5.75
ka_Init@Base 1.5.75
ka_LocalCell@Base 1.5.75
ka_ParseLoginName@Base 1.5.75
ka_ReadPassword@Base 1.5.75
ka_SingleServerConn@Base 1.5.75
ka_StringToKey@Base 1.5.75
ka_KeyCheckSum@Base 1.5.75
ka_UserAuthenticateGeneral@Base 1.5.75
ka_VerifyUserToken@Base 1.5.75
ktc_ForgetAllTokens@Base 1.5.75
ktc_ForgetToken@Base 1.5.75
ktc_GetToken@Base 1.5.75
ktc_ListTokens@Base 1.5.75
ktc_OldPioctl@Base 1.5.75
ktc_SetToken@Base 1.5.75
ktc_curpag@Base 1.5.75
ubik_Call@Base 1.5.75
ubik_Call_New@Base 1.5.75
ubik_CallIter@Base 1.5.75
ubik_ClientDestroy@Base 1.5.75
ubik_ClientInit@Base 1.5.75
ubik_ParseClientList@Base 1.5.75
pioctl@Base 1.5.75
getDirPath@Base 1.5.75
ka_AuthSpecificServersConn@Base 1.5.75
pthread_recursive_mutex_lock@Base 1.5.75
pthread_recursive_mutex_unlock@Base 1.5.75
grmutex@Base 1.5.75
initAFSDirPath@Base 1.5.75
renamefile@Base 1.5.75
pr_GetCPS@Base 1.5.75
pr_Initialize@Base 1.5.75
pr_GetHostCPS@Base 1.5.75
afs_krb_get_lrealm@Base 1.5.75
pr_NameToId@Base 1.5.75
pr_IdToName@Base 1.5.75
pr_ListMembers@Base 1.5.75
pr_End@Base 1.5.75
pr_SNameToId@Base 1.5.75
afs_get_pag_from_groups@Base 1.5.75
setpag@Base 1.5.75
afs_snprintf@Base 1.5.75
LogThreadNum@Base 1.5.75

1
src/packaging/Debian/libafsrpc1.install
View File

@ -1 +0,0 @@
debian/tmp/usr/lib/libafsrpc.so.*

122
src/packaging/Debian/libafsrpc1.symbols
View File

@ -1,122 +0,0 @@
libafsrpc.so.1 libafsrpc1 #MINVER#
des_check_key_parity@Base 1.5.75
des_fixup_key_parity@Base 1.5.75
des_init_random_number_generator@Base 1.5.75
des_is_weak_key@Base 1.5.75
des_key_sched@Base 1.5.75
des_random_key@Base 1.5.75
des_string_to_key@Base 1.5.75
des_cbc_cksum@Base 1.5.75
des_ecb_encrypt@Base 1.5.75
des_pcbc_encrypt@Base 1.5.75
ktohl@Base 1.5.75
life_to_time@Base 1.5.75
rx_DestroyConnection@Base 1.5.75
rx_EndCall@Base 1.5.75
rx_Finalize@Base 1.5.75
rx_GetCachedConnection@Base 1.5.75
rx_GetCall@Base 1.5.75
rx_GetIFInfo@Base 1.5.75
rx_GetSpecific@Base 1.5.75
rx_Init@Base 1.5.75
rx_KeyCreate@Base 1.5.75
rx_NewCall@Base 1.5.75
rx_NewConnection@Base 1.5.75
rx_NewService@Base 1.5.75
rx_PrintPeerStats@Base 1.5.75
rx_PrintStats@Base 1.5.75
rx_PrintTheseStats@Base 1.5.75
rx_ReadProc@Base 1.5.75
rx_ReleaseCachedConnection@Base 1.5.75
rx_ServerProc@Base 1.5.75
rx_SetSpecific@Base 1.5.75
rx_StartServer@Base 1.5.75
rx_WriteProc@Base 1.5.75
rxevent_Init@Base 1.5.75
rxevent_Post@Base 1.5.75
rxkad_GetServerInfo@Base 1.5.75
rxkad_NewClientSecurityObject@Base 1.5.75
rxkad_NewServerSecurityObject@Base 1.5.75
rxnull_NewClientSecurityObject@Base 1.5.75
rxnull_NewServerSecurityObject@Base 1.5.75
rxs_Release@Base 1.5.75
time_to_life@Base 1.5.75
tkt_CheckTimes@Base 1.5.75
tkt_DecodeTicket@Base 1.5.75
tkt_MakeTicket@Base 1.5.75
xdrrx_create@Base 1.5.75
hton_syserr_conv@Base 1.5.75
rxkad_global_stats@Base 1.5.75
rxkad_global_stats_lock@Base 1.5.75
rxkad_stats_key@Base 1.5.75
afs_com_err@Base 1.5.75
afs_error_message@Base 1.5.75
rx_socket@Base 1.5.75
rxevent_debugFile@Base 1.5.75
rx_debugFile@Base 1.5.75
rx_connDeadTime@Base 1.5.75
rx_maxReceiveSize@Base 1.5.75
rx_UdpBufSize@Base 1.5.75
rx_extraQuota@Base 1.5.75
rx_extraPackets@Base 1.5.75
rx_tranquil@Base 1.5.75
rx_getAllAddr@Base 1.5.75
rx_nWaiting@Base 1.5.75
rx_stats@Base 1.5.75
rx_SetNoJumbo@Base 1.5.75
rx_SetConnDeadTime@Base 1.5.75
rx_FlushWrite@Base 1.5.75
rx_thread_id_key@Base 1.5.75
multi_Finalize@Base 1.5.75
multi_Select@Base 1.5.75
multi_Init@Base 1.5.75
multi_Finalize_Ignore@Base 1.5.75
afs_add_to_error_table@Base 1.5.75
xdr_afsUUID@Base 1.5.75
xdr_afs_int32@Base 1.5.75
xdr_afs_uint32@Base 1.5.75
xdr_afs_int64@Base 1.5.75
xdr_afs_uint64@Base 1.5.75
rx_IncrementTimeAndCount@Base 1.5.75
rx_enable_stats@Base 1.5.75
rx_GetServerDebug@Base 1.5.75
rx_GetServerStats@Base 1.5.75
rx_GetServerVersion@Base 1.5.75
rx_GetServerConnections@Base 1.5.75
rx_stats_mutex@Base 1.5.75
rx_GetServerPeers@Base 1.5.75
rx_RetrieveProcessRPCStats@Base 1.5.75
rx_RetrievePeerRPCStats@Base 1.5.75
rx_FreeRPCStats@Base 1.5.75
rx_queryProcessRPCStats@Base 1.5.75
rx_queryPeerRPCStats@Base 1.5.75
rx_enableProcessRPCStats@Base 1.5.75
rx_enablePeerRPCStats@Base 1.5.75
rx_disableProcessRPCStats@Base 1.5.75
rx_disablePeerRPCStats@Base 1.5.75
RXSTATS_ExecuteRequest@Base 1.5.75
RXSTATS_RetrieveProcessRPCStats@Base 1.5.75
RXSTATS_RetrievePeerRPCStats@Base 1.5.75
RXSTATS_QueryProcessRPCStats@Base 1.5.75
RXSTATS_QueryPeerRPCStats@Base 1.5.75
RXSTATS_EnableProcessRPCStats@Base 1.5.75
RXSTATS_EnablePeerRPCStats@Base 1.5.75
RXSTATS_DisableProcessRPCStats@Base 1.5.75
RXSTATS_DisablePeerRPCStats@Base 1.5.75
RXSTATS_QueryRPCStatsVersion@Base 1.5.75
RXSTATS_ClearProcessRPCStats@Base 1.5.75
RXSTATS_ClearPeerRPCStats@Base 1.5.75
TM_GetTimeOfDay@Base 1.5.75
FT_GetTimeOfDay@Base 1.5.75
strcompose@Base 1.5.75
stolower@Base 1.5.75
ucstring@Base 1.5.75
lcstring@Base 1.5.75
AssertionFailed@Base 1.5.75
rx_GetLocalPeers@Base 1.5.75
rx_GetMaxReceiveWindow@Base 1.5.75
rx_GetMaxSendWindow@Base 1.5.75
rx_SetMaxReceiveWindow@Base 1.5.75
rx_SetMaxSendWindow@Base 1.5.75
rx_GetMinPeerTimeout@Base 1.5.75
rx_SetMinPeerTimeout@Base 1.5.75

1
src/packaging/Debian/libkopenafs1.install
View File

@ -1 +0,0 @@
debian/tmp/usr/lib/libkopenafs.so.*

7
src/packaging/Debian/libkopenafs1.symbols
View File

@ -1,7 +0,0 @@
libkopenafs.so.1 libkopenafs1 #MINVER#
KOPENAFS_1.0@KOPENAFS_1.0 1.5.69
k_hasafs@KOPENAFS_1.0 1.5.69
k_haspag@KOPENAFS_1.0 1.5.75
k_pioctl@KOPENAFS_1.0 1.5.69
k_setpag@KOPENAFS_1.0 1.5.69
k_unlog@KOPENAFS_1.0 1.5.69

1
src/packaging/Debian/libopenafs-dev.dirs
View File

@ -1 +0,0 @@
usr/lib

9
src/packaging/Debian/libopenafs-dev.install
View File

@ -1,9 +0,0 @@
debian/tmp/usr/bin/rxgen usr/bin
debian/tmp/usr/include usr
debian/tmp/usr/lib/*.a usr/lib
debian/tmp/usr/lib/*.so usr/lib
debian/tmp/usr/lib/afs usr/lib
debian/tmp/usr/share/man/man1/rxgen.1 usr/share/man/man1

2
src/packaging/Debian/libpam-openafs-kaserver.dirs
View File

@ -1,2 +0,0 @@
lib/security
usr/share/doc

1
src/packaging/Debian/module/compat
View File

@ -1 +0,0 @@
8

8
src/packaging/Debian/module/control
View File

@ -1,8 +0,0 @@
Source: openafs-modules
Section: kernel
Priority: optional
Maintainer: Russ Allbery <rra@debian.org>
Uploaders: Sam Hartman <hartmans@debian.org>
Build-Depends: debhelper (>= 8)
Standards-Version: 3.9.1
Homepage: http://www.openafs.org/

20
src/packaging/Debian/module/control.in
View File

@ -1,20 +0,0 @@
Source: openafs-modules
Section: kernel
Priority: optional
Maintainer: Russ Allbery <rra@debian.org>
Uploaders: Sam Hartman <hartmans@debian.org>
Build-Depends: debhelper (>= 8)
Standards-Version: 3.9.1
Package: openafs-modules-=KVERS
Breaks: openafs-client (<< 1.5.61)
Provides: openafs-modules3
Architecture: any
Recommends: linux-image-=KVERS
Description: AFS distributed filesystem kernel module
AFS is a distributed filesystem allowing cross-platform sharing of
files among multiple computers. Facilities are provided for access
control, authentication, backup and administrative management.
.
This package provides the compiled AFS kernel module for kernel
version =KVERS.

19
src/packaging/Debian/module/genchanges
View File

@ -1,19 +0,0 @@
#!/bin/sh
# genchanges.sh - generate a changes file for a deb file generated via
# the make-kpkg utility
# KSRC, KVERS, KMAINT, and KEMAIL are expected to be passed through the
# environment.
set -e
umask 022
MODVERS=`cat debian/VERSION | sed s/:/\+/`
ARCH=`dpkg --print-architecture`
mprefix=`grep Package: debian/control.in | cut -d' ' -f 2 | cut -d= -f 1`
chfile="$KSRC/../$mprefix${KVERS}${INT_SUBARCH}_${MODVERS}_${ARCH}.changes"
dpkg-genchanges -b ${KMAINT:+-m"$KMAINT <$KEMAIL>"} -u"$KSRC/.." \
-cdebian/control > "$chfile"
#debsign "$chfile"

24
src/packaging/Debian/module/kernel-version
View File

@ -1,24 +0,0 @@
#!/usr/bin/perl
#
# Extract the kernel version from the kernel version header file. Takes the
# kernel source path as its only argument. If the version header couldn't be
# found, print nothing and exit quietly.
my $ksrc = shift;
unless ($ksrc && open (VERSION, "$ksrc/include/linux/version.h")) {
exit 0;
}
my $found;
my $line = <VERSION>;
if ($line =~ /"(.+)"/) {
print "$1\n";
$found = 1;
}
exit 0 if $found;
unless (open (VERSION, "$ksrc/include/config/kernel.release")) {
exit 0;
}
if ($line = <VERSION>) {
print "$line";
}
exit 0;

93
src/packaging/Debian/module/prep-modules
View File

@ -1,93 +0,0 @@
#! /bin/sh
#
# Prepares to build kernel modules. This script figures out and munges
# version strings. The goal is:
#
# * Set the package name to openafs-modules-$(KVERS) where $(KVERS) is the
# major kernel revision plus the debian subrevision and whatever
# architecture string is appropriate if building against the stock Debian
# kernels. $(KVERS) should be identical to the version component contained
# in the Debian kernel package names (in other words, the ABI version, not
# the package version)..
#
# * Make the package recommend linux-image-$(KVERS) as appropriate for the
# kernel version that we're building against. Use recommend rather than
# depends since the user may have built their own kernel outside of the
# Debian package infrastructure.
#
# * Save the version number of the binary package in debian/VERSION for later
# use by dh_gencontrol. This will be the version number of the source
# package followed by a + and the version number of the kernel package that
# we're building against. If the kernel package version contains an epoch,
# try to hack our way into doing the right thing by using that epoch number
# as our own. This isn't quite the right thing, but seems reasonably good.
#
# This script generates debian/control from debian/control.module using sed.
# Unfortunately, substvars cannot be used since the name of the package is
# modified and substvars happens too late. It also outputs debian/VERSION,
# containing the version of the binary package.
set -e
if [ "$#" -ne 1 ]; then
echo "Usage: $0 <kernel-source-location>" >&2
exit 1
fi
# We can get the kernel version from one of three places. If KVERS and KDREV
# are both already set in the environment (which will be the case when invoked
# by make-kpkg or module-assistant), use them. Otherwise, if we have a kernel
# source directory that contains debian/changelog (generated by make-kpkg),
# parse that file to find the version information. Finally, if neither works,
# extract the kernel version from the kernel headers, append INT_SUBARCH to
# that version if it's available, and assume a kernel package revision of -0
# if none is provided.
#
# Set the variables $afs_kvers, which will hold the revision of the kernel,
# and $afs_kdrev, which will hold the version of the kernel package that we're
# building against.
changelog="$1/debian/changelog"
if [ -n "$KVERS" ] && [ -n "$KDREV" ]; then
afs_kvers="${KVERS}${INT_SUBARCH}"
afs_kdrev="${KDREV}"
elif [ ! -f "$changelog" ] ; then
if [ -n "$KVERS" ] ; then
afs_kvers="$KVERS"
else
afs_kvers=`perl debian/kernel-version "$1"`
fi
if [ -z "$KDREV" ] ; then
afs_kdrev="${afs_kvers}-0"
else
afs_kvers="${afs_kvers}${INT_SUBARCH}"
afs_kdrev="${KDREV}"
fi
else
if [ -n "$KVERS" ] ; then
afs_kvers="$KVERS"
else
afs_kvers=`head -1 "$changelog" \
| sed -e 's/.*source-\([^ ]*\) (\([^)]*\)).*/\1/'`
fi
afs_kdrev=`head -1 "$changelog" \
| sed -e 's/.*source-\([^ ]*\) (\([^)]*\)).*/\2/'`
fi
# Generate the control file from the template.
sed -e "s/=KVERS/${afs_kvers}/g" debian/control.in > debian/control
# Now, calcuate the binary package version. Extract the epoch from the kernel
# package revision and add it to the beginning of the binary package version
# if present. Then, concatenate the source version, '+', and the kernel
# package revision without the epoch.
afs_version=`head -1 debian/changelog | sed -e 's/.*(\([^)]*\)).*/\1/'`
afs_epoch=`echo ${afs_kdrev} | sed -n -e 's/^\([0-9]*\):.*/\1/p'`
afs_version="${afs_version}+`echo ${afs_kdrev} | sed -e 's/^[0-9]*://'`"
if [ -n "$afs_epoch" ] ; then
afs_version="${afs_epoch}:${afs_version}"
fi
echo "$afs_version" > debian/VERSION

89
src/packaging/Debian/module/rules
View File

@ -1,89 +0,0 @@
#!/usr/bin/make -f
# Determine whether we're building with optimization. This doesn't really
# work at the moment due to upstream problems.
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
DEBIAN_OPT_FLAGS = --disable-optimize --disable-optimize-lwp
DEBIAN_KERN_FLAGS = --disable-optimize-kernel
else
DEBIAN_OPT_FLAGS =
DEBIAN_KERN_FLAGS =
endif
# Find kernel build information.
ifndef KSRC
KSRC := /lib/modules/$(shell uname -r)/build
endif
ifndef KPKG_DEST_DIR
KPKG_DEST_DIR = ..
endif
KVERS := $(shell perl debian/kernel-version $(KSRC))
export KSRC
export KVERS
export KPKG_DEST_DIR
SYS_NAME := $(shell KSRC="$(KSRC)" KVERS="$(KVERS)" ARCH="$(ARCH)" \
sh debian/sysname)
package = openafs
modulepkg := openafs-modules-$(KVERS)${INT_SUBARCH}
moduledir := debian/$(modulepkg)/lib/modules/$(KVERS)/fs
# This setup must be done before running any other target if it hasn't
# already been done.
setup:
@if test x"$(SYS_NAME)" = x"UNKNOWN" ; then exit 1 ; fi
@if test x"$(KVERS)" = x ; then \
echo 'No version in $(KSRC)/include/linux/version.h' >&2 ; \
exit 1 ; \
fi
sh debian/prep-modules $(KSRC)
touch $@
%: setup
dh $@
override_dh_auto_configure:
sh configure --prefix=$(CURDIR)/debian/tmp \
--with-afs-sysname=$(SYS_NAME) \
--disable-linux-syscall-probing \
--with-linux-kernel-headers=$(KSRC) \
--with-linux-kernel-packaging \
--enable-debug --enable-debug-lwp --enable-debug-kernel \
$(DEBIAN_OPT_FLAGS) $(DEBIAN_KERN_FLAGS)
override_dh_auto_install:
cd src/libafs && make install DESTDIR=$(CURDIR)/debian/tmp
install -d -g root -o root -m 755 $(moduledir)
install -g root -o root -m 644 \
debian/tmp/lib/modules/*/extra/openafs/*o $(moduledir)/
override_dh_clean:
rm -rf src/libafs/MODLOAD-* *-stamp
dh_clean Makefile config.log config.status setup src/libafs/Makefile \
src/libafs/Makefile.common src/libafs/asm src/libafs/asm-generic \
src/libafs/h src/libafs/linux src/libafs/net src/libafs/netinet \
src/libafs/rpc src/libafs/sys
override_dh_gencontrol:
dh_gencontrol -- -v`cat debian/VERSION`
override_dh_builddeb:
dh_builddeb --destdir="$(KPKG_DEST_DIR)"
kdist_configure: override_dh_auto_configure
kdist_image:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-arch
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
kdist:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-arch
KSRC="$(KSRC)" KMAINT="$(KMAINT)" KEMAIL="$(KEMAIL)" \
sh -v debian/genchanges
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
kdist_clean:
$(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
.PHONY: kdist kdist_clean kdist_configure kdist_image

137
src/packaging/Debian/module/sysname
View File

@ -1,137 +0,0 @@
#!/bin/sh
if [ x"$KVERS" = x ] ; then
echo "ERROR: no kernel version" >&2
echo " ($KSRC/include/linux/version.h not found?)" >&2
echo UNKNOWN
exit 1
fi
case ${ARCH:-`uname -m`} in
alpha)
case $KVERS in
2.2*)
echo alpha_linux_22
;;
2.4*)
echo alpha_linux_24
;;
2.6*)
echo alpha_linux_26
;;
esac
;;
arm|armel|armv5tel)
case $KVERS in
2.4*)
echo arm_linux24
;;
2.6*)
echo arm_linux26
;;
esac
;;
i[3456]86)
case $KVERS in
2.2*)
echo i386_linux22
;;
2.4*)
echo i386_linux24
;;
2.6*)
echo i386_linux26
;;
esac
;;
ia64)
case $KVERS in
2.4*)
echo ia64_linux24
;;
2.6*)
echo ia64_linux26
;;
esac
;;
ppc)
case $KVERS in
2.2*)
echo ppc_linux22
;;
2.4*)
echo ppc_linux24
;;
2.6)
echo ppc_linux26
;;
esac
;;
ppc64)
case $KVERS in
2.4*)
echo ppc64_linux24
;;
2.6*)
echo ppc64_linux26
;;
esac
;;
s390)
case $KVERS in
2.4*)
echo s390_linux24
;;
2.6*)
echo s390_linux26
;;
esac
;;
s390x)
case $KVERS in
2.4*)
echo s390x_linux24
;;
2.6*)
echo s390x_linux26
;;
esac
;;
sparc)
case $KVERS in
2.2*)
echo sparc_linux22
;;
2.4*)
echo sparc_linux24
;;
esac
;;
sparc64)
case $KVERS in
2.2*)
echo sparc64_linux22
;;
2.4*)
echo sparc64_linux24
;;
2.6*)
echo sparc64_linux26
;;
esac
;;
x86_64)
case $KVERS in
2.4*)
echo amd64_linux24
;;
2.6*)
echo amd64_linux26
;;
esac
;;
*)
echo "ERROR: unsupported architecture" >&2
echo UNKNOWN
exit 1
esac

51
src/packaging/Debian/openafs-client.NEWS
View File

@ -1,51 +0,0 @@
openafs (1.5.73.3-1) experimental; urgency=low
This version of the OpenAFS client is built with experimental
disconnected support. This support should not change the normal
operation of the client unless it is used. If you wish to use it,
please be aware that it is an experimental feature, may not work
correctly, and may lose data. Disconnected mode is configured through
the fs discon command, which is not yet documented.
The communication protocol between afsd (in openafs-client) and the
OpenAFS kernel module has changed in 1.5. You must upgrade your kernel
module to a 1.5.x kernel module when using this or newer versions of
openafs-client, or OpenAFS will not start correctly.
-- Russ Allbery <rra@debian.org> Tue, 06 Apr 2010 14:51:38 -0700
openafs (1.4.10+dfsg1-1) unstable; urgency=high
This release of OpenAFS contains security fixes in the kernel module.
Be sure to also upgrade openafs-modules-source, build a new kernel
module for your system following the instructions in
/usr/share/doc/openafs-client/README.modules.gz, and then either stop
and restart openafs-client or reboot the system to reload the kernel
module.
-- Russ Allbery <rra@debian.org> Mon, 06 Apr 2009 15:51:14 -0700
openafs (1.4.2-6) unstable; urgency=medium
As of this release of the OpenAFS kernel module, all cells, including
the local cell, have setuid support turned off by default due to the
possibility of an attacker forging AFS fileserver responses to create a
fake setuid binary. Prior releases enabled setuid support for the local
cell. Those binaries will now run with normal permissions by default.
This security fix will only take effect once you've installed a kernel
module from openafs-modules-source 1.4.2-6 or later. Doing so is highly
recommended. In the meantime, you can disable setuid support by
running:
fs setcell -cell <localcell> -nosuid
as root (where <localcell> is your local cell, the one listed in
/etc/openafs/ThisCell).
If you are certain there is no security risk of an attacker forging AFS
fileserver responses, you can enable setuid status selectively using the
fs setcell command.
-- Russ Allbery <rra@debian.org> Sun, 11 Mar 2007 22:28:07 -0700

58
src/packaging/Debian/openafs-client.config
View File

@ -1,58 +0,0 @@
#!/bin/sh
set -e
. /usr/share/debconf/confmodule
db_version 2.0
# Configure the client cell. Default to the current ThisCell file and,
# failing that, the lowercased local domain name, if available. Ignore errors
# on read, since it may fail if there's no newline in the file.
if [ -r /etc/openafs/ThisCell ] ; then
read cell < /etc/openafs/ThisCell
db_set openafs-client/thiscell "$cell"
fi
db_get openafs-client/thiscell || true
if [ "x$RET" = "x" ] ; then
domain=`dnsdomainname 2>/dev/null || true`
if [ -n "$domain" ] ; then
db_set openafs-client/thiscell `echo "$domain" | tr 'A-Z' 'a-z'`
fi
fi
db_input high openafs-client/thiscell || true
# Configure the cache size. Default to the current value in the cacheinfo
# configuration file.
if [ -r /etc/openafs/cacheinfo ] ; then
IFS=: read mountpoint cachedir cachesize < /etc/openafs/cacheinfo
db_set openafs-client/cachesize "$cachesize"
fi
db_input high openafs-client/cachesize || true
db_go
# Configure the AFS client parameters set in /etc/openafs/afs.conf, taking
# defaults from the current file.
test -f /etc/openafs/afs.conf && . /etc/openafs/afs.conf
if [ "x$AFS_CLIENT" != "x" ] ; then
db_set openafs-client/run-client "$AFS_CLIENT"
fi
db_input low openafs-client/run-client || true
if [ "x$AFS_AFSDB" != "x" ] ; then
db_set openafs-client/afsdb "$AFS_AFSDB"
fi
if [ "x$AFS_CRYPT" != "x" ] ; then
db_set openafs-client/crypt "$AFS_CRYPT"
fi
if [ "x$AFS_DYNROOT" != "x" ] ; then
db_set openafs-client/dynroot "$AFS_DYNROOT"
fi
if [ "x$AFS_FAKESTAT" != "x" ] ; then
db_set openafs-client/fakestat "$AFS_FAKESTAT"
fi
db_beginblock
db_input low openafs-client/afsdb || true
db_input low openafs-client/crypt || true
db_input medium openafs-client/dynroot || true
db_input low openafs-client/fakestat || true
db_endblock
db_go

4
src/packaging/Debian/openafs-client.dirs
View File

@ -1,4 +0,0 @@
var/cache/openafs
etc/openafs
etc/init.d
usr/share/openafs

4
src/packaging/Debian/openafs-client.docs
View File

@ -1,4 +0,0 @@
README
debian/README.servers
debian/configuration-transcript.txt
debian/README.modules

240
src/packaging/Debian/openafs-client.init
View File

@ -1,240 +0,0 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides: openafs-client
# Required-Start: $remote_fs $network $time
# Required-Stop: $remote_fs $network
# Should-Start: $syslog
# X-Stop-After: autofs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: OpenAFS client
# Description: Starts or stops the OpenAFS client, loading the
# OpenAFS kernel module as necessary.
### END INIT INFO
#
# Modified by Sam Hartman <hartmans@mit.edu> for Debian
# Copyright 2000, International Business Machines Corporation and others.
# All Rights Reserved.
#
# This software has been released under the terms of the IBM Public
# License. For details, see the LICENSE file in the top-level source
# directory or online at http://www.openafs.org/dl/license10.html
# This init script bears little resemblence to the regular upstream init
# script at this point and is therefore maintained as a Debian-specific file.
# The upstream init script assumes Red Hat paths and uses insmod to load the
# module directly rather than using modprobe.
PATH=/bin:/usr/bin:/sbin:/usr/sbin
CACHEINFO=${CACHEINFO:-/etc/openafs/cacheinfo}
MODULEROOT=${MODULEROOT:-/lib/modules/`uname -r`}
MODULEDIR=${MODULEDIR:-$MODULEROOT/fs}
DKMSDIR=${DKMSDIR:-$MODULEROOT/updates/dkms}
exec 3>/dev/null
exec </dev/null
# Gather up options and post startup script name, if present
if [ -f /etc/openafs/afs.conf ]; then
. /etc/openafs/afs.conf
fi
# Return 1 if the argument is "true".
is_on() {
if [ x"$1" = x"true" ] ; then
return 0
else
return 1
fi
}
# Load the AFS client module if it's not already loaded. Set $MODULEDIR and
# $LIBAFS to override the default location and module name. Also check before
# loading whether the module is listed in the module dependencies so that we
# can exit with a 0 status in that case.
load_client() {
if [ -z "$LIBAFS" ] ; then
LIBAFS=openafs.ko
fi
if [ ! -f "$MODULEDIR/$LIBAFS" -a ! -f "$DKMSDIR/$LIBAFS" ] ; then
echo ""
cat <<EOF >&2
AFS module $MODULEDIR/$LIBAFS does not exist.
Not starting AFS. Please consider building kernel modules using
instructions in /usr/share/doc/openafs-client/README.modules
EOF
# We must exit successfully here or openafs-client will fail on
# installation unless a module is installed.
exit 0
fi
sawdep=0
if grep -q openafs "$MODULEROOT/modules.dep" ; then
sawdep=1
fi
LOADED=`/sbin/lsmod | fgrep openafs`
if [ -z "$LOADED" ] ; then
modprobe openafs
status=$?
if [ $status = 0 ] ; then
echo -n " openafs"
fi
# We must exit successfully here if the openafs module just isn't
# listed in the dependency information for modprobe, which can happen
# if openafs-client and the module package are installed at the same
# time and the module hasn't been set up yet.
if [ $sawdep = 0 ] ; then
return 0
else
return $status
fi
fi
return 0
}
# Determine which afsd options to use. /etc/openafs/afs.conf contains the
# settings that are checked here.
choose_afsd_options() {
if [ -z "$OPTIONS" ] || [ "$OPTIONS" = "AUTOMATIC" ] ; then
AFSD_OPTIONS="$VERBOSE"
else
AFSD_OPTIONS="$OPTIONS $VERBOSE"
fi
# These variables are from /etc/openafs/afs.conf.client and are managed
# automatically by debconf.
if is_on $AFS_AFSDB ; then
AFSD_OPTIONS="$AFSD_OPTIONS -afsdb"
fi
if is_on $AFS_DYNROOT ; then
AFSD_OPTIONS="$AFSD_OPTIONS -dynroot"
fi
if is_on $AFS_FAKESTAT ; then
AFSD_OPTIONS="$AFSD_OPTIONS -fakestat"
fi
}
# Start afsd. Be careful not to start it if another one is already running,
# as that has a bad tendency to hang the system. Earlier versions of the
# openafs-client package put afsd in /usr/sbin.
start_client() {
if pidof /sbin/afsd >/dev/null || pidof /usr/sbin/afsd >/dev/null ; then
echo "."
else
choose_afsd_options
echo " afsd."
start-stop-daemon --start --quiet --exec /sbin/afsd -- $AFSD_OPTIONS
fi
# From /etc/openafs/afs.conf.client, whether to enable fcrypt encryption.
if is_on $AFS_CRYPT ; then
fs setcrypt on
fi
# From /etc/openafs/afs.conf, set a sysname list if one was configured.
if [ -n "$AFS_SYSNAME" ] ; then
fs sysname $AFS_SYSNAME
fi
}
# Kill all processes that are accessing AFS. Not enabled by default, and
# normally called via kill_all_afs.
kill_afs() {
signal=$1
mount=`grep ^'AFS ' /etc/mtab | awk '{ print $2 }'`
if [ -n "$mount" ] ; then
pids=`/usr/bin/lsof -Fp $mount | sed 's/p//'`
if [ -n "$pids" ] ; then
kill -$signal $pids > /dev/null 2>&1
sleep 1
fi
fi
}
# Repeatedly call kill_afs for a series of signals to give AFS-using processes
# a hope of shutting down cleanly if the system is shutting down. Not enabled
# by default. Enable this in /etc/openafs/afs.conf.
#
# Warns and does nothing if lsof is not installed.
kill_all_afs() {
runlevel=`runlevel | sed 's/^. //'`
if [ "$runlevel" -eq 0 ] || [ "$runlevel" -eq 6 ] ; then
if [ -x /usr/bin/lsof ] ; then
echo -n "Killing processes with AFS files open: "
kill_afs HUP
kill_afs TERM
kill_afs ABRT
kill_afs KILL
echo "done."
else
echo '/usr/bin/lsof not found, not killing processes' >&2
fi
fi
}
case "$1" in
start)
if is_on $AFS_CLIENT && test -x /sbin/afsd ; then
echo -n "Starting AFS services:"
if load_client ; then
start_client
$AFS_POST_INIT
else
echo ""
echo "Failed to load AFS kernel module, not starting AFS" >&2
exit 1
fi
fi
;;
force-start)
if test -x /sbin/afsd ; then
echo -n "Starting AFS services:"
if load_client ; then
start_client
$AFS_POST_INIT
else
echo ""
echo "Failed to load AFS kernel module, not starting AFS" >&2
exit 1
fi
fi
;;
stop|force-stop)
$AFS_PRE_SHUTDOWN
echo -n "Stopping AFS services:"
if grep -q '^AFS ' /etc/mtab ; then
umount `grep ^'AFS ' /etc/mtab | awk '{ print $2 }'`
echo -n " afsd"
fi
if pidof /usr/sbin/afsd >/dev/null || pidof /sbin/afsd >/dev/null ; then
afsd -shutdown
fi
# If running with the -rmtsys option, afsd doesn't kill the rmtsys helper
# on afsd -shutdown. Run start-stop-daemon to make sure that everything
# is dead.
start-stop-daemon --stop --quiet --name afsd
LIBAFS=`/sbin/lsmod | awk 'BEGIN { FS = " " } /openafs/ { print $1 }'`
if [ -n "$LIBAFS" ] ; then
/sbin/rmmod $LIBAFS
echo -n " openafs"
fi
echo "."
;;
restart|force-reload)
"$0" stop
"$0" start
;;
*)
echo Usage: \
'openafs-client {start|force-start|stop|restart|force-reload}' >&2
exit 1
esac

258
src/packaging/Debian/openafs-client.install
View File

@ -1,258 +0,0 @@
debian/afs.conf etc/openafs
debian/tmp/usr/bin/afsmonitor usr/bin
debian/tmp/usr/bin/bos usr/bin
debian/tmp/usr/bin/cmdebug usr/bin
debian/tmp/usr/bin/fs usr/bin
debian/tmp/usr/bin/klog usr/bin
debian/tmp/usr/bin/knfs usr/bin
debian/tmp/usr/bin/livesys usr/bin
debian/tmp/usr/bin/pagsh usr/bin
debian/tmp/usr/bin/pts usr/bin
debian/tmp/usr/bin/restorevol usr/bin
debian/tmp/usr/bin/scout usr/bin
debian/tmp/usr/bin/sys usr/bin
debian/tmp/usr/bin/tokens usr/bin
debian/tmp/usr/bin/translate_et usr/bin
debian/tmp/usr/bin/udebug usr/bin
debian/tmp/usr/bin/unlog usr/bin
debian/tmp/usr/bin/up usr/bin
debian/tmp/usr/bin/xstat_cm_test usr/bin
debian/tmp/usr/bin/xstat_fs_test usr/bin
debian/tmp/usr/sbin/rxdebug usr/bin
debian/tmp/usr/sbin/vos usr/bin
debian/tmp/usr/sbin/backup usr/sbin
debian/tmp/usr/sbin/butc usr/sbin
debian/tmp/usr/sbin/fms usr/sbin
debian/tmp/usr/sbin/fstrace usr/sbin
debian/tmp/usr/sbin/rmtsysd usr/sbin
debian/tmp/usr/sbin/afsd sbin
debian/CellServDB usr/share/openafs
debian/tmp/usr/share/openafs/C/afszcm.cat usr/share/openafs/C
debian/tmp/usr/share/man/man1/afs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/afs-up.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/afsmonitor.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/cmdebug.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_apropos.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_checkservers.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_checkvolumes.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_cleanacl.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_copyacl.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_diskfree.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_examine.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_exportafs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_flush.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_flushmount.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_flushvolume.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getcalleraccess.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getcacheparms.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getcellstatus.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getfid.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getclientaddrs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getcrypt.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_getserverprefs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_help.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_listacl.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_listaliases.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_listcells.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_listquota.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_lsmount.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_messages.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_mkmount.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_monitor.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_newalias.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_newcell.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_quota.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_rmmount.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_rxstatpeer.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_rxstatproc.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setacl.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setcachesize.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setcbaddr.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setcell.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setclientaddrs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setcrypt.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setquota.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setserverprefs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_setvol.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_storebehind.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_sysname.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_uuid.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_whereis.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_whichcell.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/fs_wscell.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/klog.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/knfs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/livesys.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pagsh.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_adduser.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_apropos.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_chown.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_creategroup.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_createuser.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_delete.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_examine.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_help.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_interactive.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_listentries.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_listmax.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_listowned.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_membership.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_quit.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_removeuser.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_rename.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_setfields.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_setmax.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_sleep.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/pts_source.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/restorevol.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/rxdebug.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/scout.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/sys.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/tokens.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/translate_et.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/udebug.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/unlog.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_addsite.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_apropos.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_backup.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_backupsys.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_changeaddr.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_changeloc.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_clone.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_convertROtoRW.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_copy.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_create.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_delentry.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_dump.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_endtrans.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_examine.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_help.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_listaddrs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_listpart.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_listvldb.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_listvol.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_lock.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_offline.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_online.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_move.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_partinfo.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_release.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_remove.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_remsite.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_rename.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_restore.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_setfields.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_shadow.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_size.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_setaddrs.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_status.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_syncserv.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_syncvldb.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_unlock.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_unlockvldb.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/vos_zap.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/xstat_cm_test.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/xstat_fs_test.1 usr/share/man/man1
debian/tmp/usr/share/man/man5/CellAlias.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/CellServDB.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/NetInfo.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/NetRestrict.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/ThisCell.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/afs.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/afs_cache.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/afsmonitor.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/afszcm.cat.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/butc.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/butc_logs.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/cacheinfo.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/tapeconfig.5 usr/share/man/man5
debian/tmp/usr/share/man/man8/afsd.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_adddump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_addhost.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_addvolentry.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_addvolset.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_apropos.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_dbverify.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_deldump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_deletedump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_delhost.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_delvolentry.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_delvolset.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_diskrestore.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_dump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_dumpinfo.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_help.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_interactive.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_jobs.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_kill.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_labeltape.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_listdumps.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_listhosts.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_listvolsets.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_quit.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_readlabel.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_restoredb.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_savedb.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_scantape.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_setexp.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_status.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_volinfo.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_volrestore.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/backup_volsetrestore.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_addhost.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_addkey.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_adduser.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_apropos.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_create.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_delete.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_exec.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_getdate.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_getlog.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_getrestart.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_getrestricted.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_help.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_install.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_listhosts.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_listkeys.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_listusers.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_prune.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_removehost.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_removekey.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_removeuser.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_restart.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_salvage.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_setauth.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_setcellname.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_setrestart.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_setrestricted.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_shutdown.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_start.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_startup.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_status.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_stop.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bos_uninstall.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/butc.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fms.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_apropos.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_clear.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_dump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_help.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_lslog.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_lsset.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_setlog.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fstrace_setset.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/rmtsysd.8 usr/share/man/man8

10
src/packaging/Debian/openafs-client.lintian-overrides
View File

@ -1,10 +0,0 @@
# The AFS client cache should not be world-readable, since it may contain
# files only readable by some of the local users based on their tokens.
openafs-client: non-standard-dir-perm var/cache/openafs/ 0700 != 0755
# These are virtual packages, and breaks is more correct than Conflicts
# since upgrading to something that provides openafs-modules3 will fix
# the problem but the packages can be co-installed from a file system
# perspective.
openafs-client: breaks-without-version openafs-modules1
openafs-client: breaks-without-version openafs-modules2

98
src/packaging/Debian/openafs-client.postinst
View File

@ -1,98 +0,0 @@
#! /bin/sh
set -e
if [ "$1" = configure ] || [ "$1" = reconfigure ] ; then
update-alternatives --install /usr/bin/pagsh pagsh \
/usr/bin/pagsh.openafs 100 \
--slave /usr/share/man/man1/pagsh.1.gz pagsh.1.gz \
/usr/share/man/man1/pagsh.openafs.1.gz
update-alternatives --install /usr/bin/klog klog \
/usr/bin/klog.afs 10 \
--slave /usr/share/man/man1/klog.1.gz klog.1.gz \
/usr/share/man/man1/klog.afs.1.gz
test -d /afs || mkdir /afs
. /usr/share/debconf/confmodule
db_version 2.0
db_get openafs-client/thiscell
THISCELL="$RET"
if [ -n "$THISCELL" ] ; then
echo "$THISCELL" > /etc/openafs/ThisCell
fi
if [ ! -f /etc/openafs/CellServDB ] ; then
cp /usr/share/openafs/CellServDB /etc/openafs
fi
# If ThisCell is not in CellServDB, we have to prompt the user for the
# VLDB servers. Unfortunately, we can't do this in config because we
# need the CellServDB file, which is part of the package.
#
# If the user is using afsdb for cell location, don't worry about
# prompting them for cells for their local system.
db_get openafs-client/afsdb
afsdb="$RET"
if grep -q -F "$THISCELL" /etc/openafs/CellServDB \
&& [ "x$THISCELL" != "x" ] ; then
:
elif [ x"$afsdb" != xtrue ] ; then
db_input critical openafs-client/cell-info || true
db_input high openafs-client/run-client || true
db_go
db_get openafs-client/cell-info
if [ "x$RET" != "x" ] ; then
echo ">$THISCELL" > /etc/openafs/CellServDB.new
perl -MSocket -e 'foreach (@ARGV) {' \
-e '@a=gethostbyname($_) and ' \
-e 'printf("%s\t\t# %s\n",inet_ntoa($a[4]),$a[0]) }' $RET \
>>/etc/openafs/CellServDB.new
if [ `wc -l </etc/openafs/CellServDB.new` -eq 1 ] ; then
echo None of the hostnames resolved to an address 2>&1
db_reset openafs-client/cell-info || true
rm /etc/openafs/CellServDB.new
else
cat /etc/openafs/CellServDB.new /etc/openafs/CellServDB \
> /etc/openafs/CellServDB.tmp
mv /etc/openafs/CellServDB.tmp /etc/openafs/CellServDB
rm /etc/openafs/CellServDB.new
fi
fi
fi
# Our config script will have already taken care of extracting the cache
# size from the cacheinfo file and using it as the default for the debconf
# prompt, but the mount point and cache directory have no debconf prompts.
# For those, we need to get the default from the file.
mountpoint=/afs
cachedir=/var/cache/openafs
if [ -r /etc/openafs/cacheinfo ] ; then
IFS=: read mountpoint cachedir cachesize < /etc/openafs/cacheinfo
fi
db_get openafs-client/cachesize
echo "${mountpoint}:${cachedir}:${RET}" > /etc/openafs/cacheinfo
echo <<'EOF' > /etc/openafs/afs.conf.client
# This file is managed by debconf. You may change the parameters set below,
# but any additional lines or comments will be lost when the package is
# upgraded or reconfigured. Local modifications other than setting the
# following parameters should be made in /etc/openafs/afs.conf instead.
EOF
db_get openafs-client/run-client
echo AFS_CLIENT="$RET" > /etc/openafs/afs.conf.client
echo AFS_AFSDB="$afsdb" >> /etc/openafs/afs.conf.client
db_get openafs-client/crypt
echo AFS_CRYPT="$RET" >> /etc/openafs/afs.conf.client
db_get openafs-client/dynroot
echo AFS_DYNROOT="$RET" >> /etc/openafs/afs.conf.client
db_get openafs-client/fakestat
echo AFS_FAKESTAT="$RET" >> /etc/openafs/afs.conf.client
fi
#DEBHELPER#
exit 0

21
src/packaging/Debian/openafs-client.postrm
View File

@ -1,21 +0,0 @@
#! /bin/sh
set -e
case "$1" in
purge)
rmdir /afs 2>/dev/null || true
for file in cacheinfo CellServDB ThisCell afs.conf.client ; do
rm -f "/etc/openafs/$file"
done
;;
remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;
*)
echo "postrm called with unknown argument $1" >&2
exit 0
esac
#DEBHELPER#

12
src/packaging/Debian/openafs-client.prerm
View File

@ -1,12 +0,0 @@
#!/bin/sh
set -e
if [ "$1" = remove ] || [ "$1" = deconfigure ] ; then
update-alternatives --remove pagsh /usr/bin/pagsh.openafs
update-alternatives --remove klog /usr/bin/klog.afs
fi
#DEBHELPER#
exit 0

85
src/packaging/Debian/openafs-client.templates
View File

@ -1,85 +0,0 @@
Template: openafs-client/cell-info
Type: string
_Description: DB server host names for your home cell:
AFS uses the file /etc/openafs/CellServDB to hold the list of servers that
should be contacted to find parts of a cell. The cell you claim this
workstation belongs to is not in that file. Enter the host names of the
database servers separated by spaces. IMPORTANT: If you are creating a new
cell and this machine is to be a database server in that cell, only enter
this machine's name; add the other servers later after they are
functioning. Also, do not enable the AFS client to start at boot on this
server until the cell is configured. When you are ready you can edit
/etc/openafs/afs.conf.client to enable the client.
Template: openafs-client/thiscell
Type: string
_Description: AFS cell this workstation belongs to:
AFS filespace is organized into cells or administrative domains.
Each workstation belongs to one cell. Usually the cell is the DNS
domain name of the site.
Template: openafs-client/cachesize
Type: string
Default: 50000
_Description: Size of AFS cache in kB:
AFS uses an area of the disk to cache remote files for faster
access. This cache will be mounted on /var/cache/openafs. It is
important that the cache not overfill the partition it is located
on. Often, people find it useful to dedicate a partition to their
AFS cache.
Template: openafs-client/run-client
Type: boolean
Default: true
_Description: Run Openafs client now and at boot?
Normally, most users who install the openafs-client package expect AFS to
be mounted automatically at boot. However, if you are planning on
setting up a new cell or are on a laptop, you may not want it started at
boot time. If you choose not to start AFS at boot, run
/etc/init.d/openafs-client force-start to start the client when you wish
to run it.
Template: openafs-client/afsdb
Type: boolean
Default: true
_Description: Look up AFS cells in DNS?
In order to contact an AFS cell, you need the IP addresses of the cell's
database servers. Normally, this information is read from
/etc/openafs/CellServDB. However, if Openafs cannot find a cell in that
file, it can use DNS to look for AFSDB records that contain the
information.
Template: openafs-client/crypt
Type: boolean
Default: true
_Description: Encrypt authenticated traffic with AFS fileserver?
AFS provides a weak form of encryption that can optionally be used between
a client and the fileservers. While this encryption is weaker than DES
and thus is not sufficient for highly confidential data, it does provide
some confidentiality and is likely to make the job of a casual attacker
significantly more difficult.
Template: openafs-client/dynroot
Type: boolean
Default: true
_Description: Dynamically generate the contents of /afs?
/afs generally contains an entry for each cell that a client can talk to.
Traditionally, these entries were generated by servers in the client's
home cell. However, OpenAFS clients can generate the contents of /afs
dynamically based on the contents of /etc/openafs/CellServDB and DNS.
.
If you generate /afs dynamically, you may need to create
/etc/openafs/CellAlias to include aliases for common cells. (The syntax
of this file is one line per alias, with the cell name, a space, and then
the alias for that cell.)
Template: openafs-client/fakestat
Type: boolean
Default: true
_Description: Use fakestat to avoid hangs when listing /afs?
Because AFS is a global file space, operations on the /afs directory can
generate significant network traffic. If some AFS cells are unavailable
then looking at /afs using ls or a graphical file browser may hang your
machine for minutes. AFS has an option to simulate answers to these
operations locally to avoid these hangs. You want this option under most
circumstances.

20
src/packaging/Debian/openafs-dbserver.NEWS
View File

@ -1,20 +0,0 @@
openafs-dbserver (1.4.7.dfsg1-1) unstable; urgency=low
If you are upgrading from one of the 1.4.7 pre-releases, be aware that
there was a serious bug in those versions that could cause Ubik database
entries to be lost if all database servers were restarted at the same
time. You should restart each database server in turn, one at a time,
to pick up the new 1.4.7 binaries before the next nightly restart.
Only 1.4.7 pre-releases were affected by this problem. If you are
upgrading from an older version, you should not have to take special
precautions.
You may also want to turn off any general restart for your servers with:
bos setrestart -server <server> -time never -general
This was an old defense against memory leaks and is no longer needed.
-- Russ Allbery <rra@debian.org> Fri, 09 May 2008 10:24:48 -0700

4
src/packaging/Debian/openafs-dbserver.dirs
View File

@ -1,4 +0,0 @@
usr/share/doc
var/lib/openafs/db
usr/share/man/man8
usr/sbin

27
src/packaging/Debian/openafs-dbserver.install
View File

@ -1,27 +0,0 @@
debian/tmp/usr/sbin/prdb_check usr/sbin
debian/tmp/usr/sbin/pt_util usr/sbin
debian/tmp/usr/sbin/read_tape usr/sbin
debian/tmp/usr/sbin/vldb_check usr/sbin
debian/afs-rootvol usr/sbin
debian/afs-newcell usr/sbin
debian/tmp/usr/lib/openafs/buserver usr/lib/openafs
debian/tmp/usr/lib/openafs/ptserver usr/lib/openafs
debian/tmp/usr/lib/openafs/vlserver usr/lib/openafs
debian/ConfigUtils.pm usr/share/perl5/Debian/OpenAFS
debian/tmp/usr/share/man/man5/BackupLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/VLLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/bdb.DB0.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/prdb.DB0.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/vldb.DB0.5 usr/share/man/man5
debian/tmp/usr/share/man/man8/buserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/prdb_check.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/pt_util.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/ptserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/read_tape.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/vldb_check.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/vlserver.8 usr/share/man/man8

3
src/packaging/Debian/openafs-dbserver.lintian-overrides
View File

@ -1,3 +0,0 @@
# The database directory should be kept locked down to prevent reading
# database information that may not be accessible without authentication.
openafs-dbserver: non-standard-dir-perm var/lib/openafs/db/ 0700 != 0755

28
src/packaging/Debian/openafs-dbserver.postrm
View File

@ -1,28 +0,0 @@
#! /bin/sh
# postrm script for openafs-dbserver
#
# Purges the database and log files created by the package. We assume that
# it's safe to do this for database files since they're normally transferred
# via Ubik to other hosts.
set -e
case "$1" in
purge)
for file in prdb.DB0 prdb.DBSYS1 vldb.DB0 vldb.DBSYS1 ; do
rm -f "/var/lib/openafs/db/$file"
done
for file in PtLog PtLog.old VLLog VLLog.old ; do
rm -f "/var/log/openafs/$file"
done
;;
remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;
*)
echo "postrm called with unknown argument $1" >&2
exit 0
esac
#DEBHELPER#

21
src/packaging/Debian/openafs-doc.README.Debian
View File

@ -1,21 +0,0 @@
OpenAFS Documentation for Debian
--------------------------------
Included in this package are the original Transarc AFS manuals with small
modifications. This is the best available comprehensive documentation for
OpenAFS, but please be aware that this documentation has not been updated
to reflect the changes made to OpenAFS since the original public release.
Work on this is ongoing upstream, and newer documentation will be packaged
as soon as it is available.
All of the manuals are included because, even including significant
portions that are not relevant to Debian, because they all do contain some
valuable information. Debian users should ignore the installation
information and much of the Quick Start Guide in favor of the
documentation that comes with the Debian OpenAFS packages.
The AFS protocol information included here is dated and may not be
accurate in all details, but is the best protocol information currently
available.
-- Russ Allbery <rra@debian.org>, Mon, 14 Jun 2010 18:18:35 -0700

14
src/packaging/Debian/openafs-doc.doc-base.openafs-admin
View File

@ -1,14 +0,0 @@
Document: openafs-admin
Title: AFS Administrator's Guide
Author: IBM
Abstract: Describes concepts and procedures for an AFS cell administrator.
This is a somewhat outdated guide to configuring and administering an AFS
cell and an introduction to AFS for those considering running it.
Section: File Management
Format: HTML
Index: /usr/share/doc/openafs-doc/html/AdminGuide/index.html
Files: /usr/share/doc/openafs-doc/html/AdminGuide/*
Format: PDF
Files: /usr/share/doc/openafs-doc/auagd000.pdf.gz

14
src/packaging/Debian/openafs-doc.doc-base.openafs-quick
View File

@ -1,14 +0,0 @@
Document: openafs-quick
Title: AFS Quick Start Guide for UNIX
Author: IBM
Abstract: Initial setup and configuration documentation for AFS on Unix
platforms. Debian users can ignore most of the installation information,
but the configuration information is still useful.
Section: File Management
Format: HTML
Index: /usr/share/doc/openafs-doc/html/QuickStartUnix/index.html
Files: /usr/share/doc/openafs-doc/html/QuickStartUnix/*
Format: PDF
Files: /usr/share/doc/openafs-doc/auqbg000.pdf.gz

13
src/packaging/Debian/openafs-doc.doc-base.openafs-user
View File

@ -1,13 +0,0 @@
Document: openafs-user
Title: AFS User's Guide
Author: IBM
Abstract: Introduction and documentation of AFS for the end-user. This is
the best document for people who will be using but not administering AFS.
Section: File Management
Format: HTML
Index: /usr/share/doc/openafs-doc/html/UserGuide/index.html
Files: /usr/share/doc/openafs-doc/html/UserGuide/*
Format: PDF
Files: /usr/share/doc/openafs-doc/auusg000.pdf.gz

3
src/packaging/Debian/openafs-doc.docs
View File

@ -1,3 +0,0 @@
doc/arch/dafs-overview.txt
doc/arch/fssync.txt
doc/txt/ka2heim.txt

1
src/packaging/Debian/openafs-doc.examples
View File

@ -1 +0,0 @@
doc/examples/CellAlias

81
src/packaging/Debian/openafs-fileserver.NEWS
View File

@ -1,81 +0,0 @@
openafs (1.5.77-1) experimental; urgency=low
This version of the OpenAFS file server includes a version built with
demand-attach, but as binaries with a different name.
Demand-attach completely changes how the file server shuts down and
starts up. Instead of detaching all volumes on shutdown and reattaching
them on startup, the file server saves state to disk and restores state
when starting, enabling it to start far faster. Volumes are only
attached when used and are detached again if they go unused for an
extended period. Volumes can also be salvaged on demand.
Demand-attach is recommended for new deployments and for evaluation in
current production deployments, but requires a change to your bos
configuration to use. If you want to switch your file server to
demand-attach, run:
bos status localhost -instance fs -long
and take note of the flags that you're using with the fileserver and
volserver. Then, run:
bos stop localhost fs -localauth
bos delete localhost fs -localauth
bos create localhost dafs dafs \
"/usr/lib/openafs/dafileserver <fileserver-flags>" \
"/usr/lib/openafs/davolserver <volserver-flags>" \
/usr/lib/openafs/salvageserver /usr/lib/openafs/dasalvager
to create the correct new BosConfig entry for demand-attach AFS.
If you were running an earlier version of the experimental
openafs-filserver package, the way that demand-attach was handled has
changed and you have to change your bos configuration to use the new
demand-attach binary names. Run:
bos stop localhost dafs -localauth
bos delete localhost dafs -localauth
and then run the bos create command above. This only applies to users
of the previous experimental packages, not to upgrades from unstable.
-- Russ Allbery <rra@debian.org> Tue, 21 Sep 2010 14:08:04 -0700
openafs (1.5.73.3-1) experimental; urgency=low
As of this release, the default permissions for /etc/openafs/server are
now 0755, matching upstream. The only file in that directory that needs
to be kept secure is KeyFile, which is created with 0600 permissions.
The directory permissions won't be changed on upgrade, so bosserver will
complain now that it is no longer patched to permit restrictive
permissions. Once you're certain the per-file permissions of all files
in that directory are safe, chmod 755 /etc/openafs/server to make
bosserver happy.
-- Russ Allbery <rra@debian.org> Tue, 06 Apr 2010 14:51:52 -0700
openafs (1.4.4.dfsg1-4) unstable; urgency=low
The files previously located in /etc/openafs/server-local have been
moved to /var/lib/openafs/local. The OpenAFS fileserver and bosserver
write files to this directory on startup which are not configuration
files and therefore, per the File Hierarchy Standard, should not be in
/etc. Any sysid, sysid.old, NetInfo, and NetRestrict files in
/etc/openafs/server-local have been copied to /var/lib/openafs/local.
upserver and upclient have moved to /usr/lib/openafs (from /usr/sbin) to
match the other programs intended to be run by the bosserver and to
match upstream's layout. If you're running upserver or upclient from
bosserver, BosConfig has been updated with the new path, but the
services have not been restarted.
At your convenience, you should restart your servers with:
bos restart -all -bosserver
so that the running servers will look at the new locations. After doing
so, you may remove /etc/openafs/server-local if you wish.
-- Russ Allbery <rra@debian.org> Tue, 19 Jun 2007 03:51:58 -0700

27
src/packaging/Debian/openafs-fileserver.config
View File

@ -1,27 +0,0 @@
#!/bin/sh
set -e
. /usr/share/debconf/confmodule
db_version 2.0
# Warn anyone who's trying to run the file server on alpha.
arch=`dpkg --print-architecture`
if [ "$arch" = "alpha" ] ; then
db_input high openafs-fileserver/alpha-broken || true
fi
# Configure the local cell. Ignore errors on read since it may fail if
# there's no newline in the file. Default to the server ThisCell file and, if
# that fails, the configured client cell.
if [ -r /etc/openafs/server/ThisCell ] ; then
read cell < /etc/openafs/server/ThisCell || true
db_set openafs-fileserver/thiscell "$cell"
fi
db_get openafs-fileserver/thiscell || true
if [ "x$RET" = "x" ] ; then
db_get openafs-client/thiscell || true
db_set openafs-fileserver/thiscell "$RET"
fi
db_input low openafs-fileserver/thiscell || true
db_go

4
src/packaging/Debian/openafs-fileserver.dirs
View File

@ -1,4 +0,0 @@
usr/share/doc
var/log/openafs
etc/openafs/server
var/lib/openafs/local

139
src/packaging/Debian/openafs-fileserver.init
View File

@ -1,139 +0,0 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides: openafs-fileserver
# Required-Start: $remote_fs $network $time $named
# Required-Stop: $remote_fs $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: OpenAFS file and database server manager
# Description: Starts, stops, or restarts the OpenAFS bosserver,
# which is the process that starts and manages the
# OpenAFS file server or database servers depending on
# its configuration.
### END INIT INFO
# Author: Sam Hartman <hartmans@mit.edu>
# Author: Russ Allbery <rra@debian.org>
#
# Based on the /etc/init.d/skeleton template as found in initscripts version
# 2.86.ds1-15.
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC="OpenAFS BOS server"
NAME=bosserver
DAEMON=/usr/sbin/bosserver
DAEMON_ARGS=""
SCRIPTNAME=/etc/init.d/openafs-fileserver
# Exit if the package is not installed and we were not given the status option.
if [ ! -x "$DAEMON" ] && [ "status" != "$1" ] ; then
exit 0
fi
# Read configuration if it is present.
[ -r /etc/default/openafs-fileserver ] && . /etc/default/openafs-fileserver
# Get the setting of VERBOSE and other rcS variables.
[ -f /etc/default/rcS ] && . /etc/default/rcS
# Define LSB log functions (requires lsb-base >= 3.0-6).
. /lib/lsb/init-functions
# Make sure we don't leave file descriptors open.
exec 3>/dev/null
exec </dev/null
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
do_start()
{
start-stop-daemon --start --quiet --startas $DAEMON --name $NAME --test \
> /dev/null || return 1
start-stop-daemon --start --quiet --startas $DAEMON --name $NAME \
-- $DAEMON_ARGS || return 2
}
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
do_stop()
{
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
}
case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_action_msg "Stopping OpenAFS services"
bos shutdown localhost -wait -localauth
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
restart|force-reload)
[ "$VERBOSE" != no ] && log_daemon_msg "Restarting $DESC" "$NAME"
start-stop-daemon --start --quiet --startas $DAEMON --name $NAME --test \
> /dev/null
case "$?" in
0)
do_start
case "$?" in
0) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
*) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
1)
bos restart localhost -all -bosserver -localauth
case "$?" in
0) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
*) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
*)
log_end_msg 1
;;
esac
;;
status)
start-stop-daemon --start --quiet --startas $DAEMON --name $NAME --test \
> /dev/null
case "$?" in
0)
echo "$NAME is not running"
exit 3
;;
1)
echo "$NAME is running"
exit 0
;;
*)
log_warning_msg "Cannot determine if $NAME is running"
exit 4
;;
esac
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 3
;;
esac
exit 0

71
src/packaging/Debian/openafs-fileserver.install
View File

@ -1,71 +0,0 @@
debian/tmp/usr/sbin/bos_util usr/sbin
debian/tmp/usr/sbin/bosserver usr/sbin
debian/tmp/usr/sbin/dafssync-debug usr/sbin
debian/tmp/usr/sbin/fssync-debug usr/sbin
debian/tmp/usr/sbin/salvsync-debug usr/sbin
debian/tmp/usr/sbin/state_analyzer usr/sbin
debian/tmp/usr/sbin/voldump usr/sbin
debian/tmp/usr/sbin/volinfo usr/sbin
debian/tmp/usr/lib/openafs/dafileserver usr/lib/openafs
debian/tmp/usr/lib/openafs/dasalvager usr/lib/openafs
debian/tmp/usr/lib/openafs/davolserver usr/lib/openafs
debian/tmp/usr/lib/openafs/fileserver usr/lib/openafs
debian/tmp/usr/lib/openafs/salvager usr/lib/openafs
debian/tmp/usr/lib/openafs/salvageserver usr/lib/openafs
debian/tmp/usr/lib/openafs/upclient usr/lib/openafs
debian/tmp/usr/lib/openafs/upserver usr/lib/openafs
debian/tmp/usr/lib/openafs/volserver usr/lib/openafs
debian/tmp/usr/share/man/man5/BosConfig.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/BosLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/FORCESALVAGE.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/FileLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/KeyFile.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/NoAuth.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/SALVAGE.fs.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/SalvageLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/UserList.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/VolserLog.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/afs_volume_header.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/krb.conf.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/krb.excl.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/salvage.lock.5 usr/share/man/man5
debian/tmp/usr/share/man/man5/sysid.5 usr/share/man/man5
debian/tmp/usr/share/man/man8/bos_util.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bosserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/dafileserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/dafssync-debug.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/dasalvager.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/davolserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fileserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_attach.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_callback.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_detach.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_error.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_header.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_leaveoff.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_list.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_mode.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_move.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_offline.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_online.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_query.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_stats.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vgcadd.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vgcdel.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vgcquery.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vgcscan.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vgcscanall.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_vnode.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_volop.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/salvager.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/salvageserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/state_analyzer.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/upclient.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/upserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/voldump.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/volinfo.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/volserver.8 usr/share/man/man8

5
src/packaging/Debian/openafs-fileserver.lintian-overrides
View File

@ -1,5 +0,0 @@
# /var/lib/openafs/local contains the fssync.sock file used to coordinate
# volume actions between the fileserver and the volserver so upstream
# wants it to be locked down. Probably doesn't matter on Linux, but if we
# diverge, we either have to patch bosserver or it complains.
openafs-fileserver: non-standard-dir-perm var/lib/openafs/local/ 0700 != 0755

64
src/packaging/Debian/openafs-fileserver.postinst
View File

@ -1,64 +0,0 @@
#!/bin/sh
set -e
case "$1" in
configure)
. /usr/share/debconf/confmodule
db_version 2.0
db_get openafs-fileserver/thiscell
echo $RET >/etc/openafs/server/ThisCell
if [ ! -f /etc/openafs/server/CellServDB ] ; then
sed -n "/^>$RET/,/^>/p" /etc/openafs/CellServDB | sed '$d' \
>/etc/openafs/server/CellServDB
if [ ! -s /etc/openafs/server/CellServDB ] ; then
echo ">$RET" >/etc/openafs/server/CellServDB
fi
fi
db_stop
# Move the contents of the old /etc/openafs/server-local directory into
# /var/lib/openafs/local. Most of the files in this directory are
# automatically generated, so it didn't belong in /etc.
#
# Change the paths to upserver and upclient in BosConfig from older
# versions that had the binaries in /usr/sbin.
if [ x"$2" != x ] && dpkg --compare-versions "$2" lt 1.4.4.dfsg1-4 ; then
for f in sysid sysid.old NetInfo NetRestrict ; do
if [ -e "/etc/openafs/server-local/$f" ] ; then
cp "/etc/openafs/server-local/$f" "/var/lib/openafs/local/$f"
fi
done
if [ -e /etc/openafs/BosConfig ] ; then
sed -i -e 's,/usr/sbin/upserver,/usr/lib/openafs/upserver,' \
-e 's,/usr/sbin/upclient,/usr/lib/openafs/upclient,' \
/etc/openafs/BosConfig
fi
fi
# Previous versions of the package set the permissions on
# /var/lib/openafs/local to 755, but upstream prefers 700 to protect the
# fssync.sock socket. Probably doesn't matter on Linux, but if we
# diverge, either bosserver complains or we have to patch it. dpkg won't
# change the permissions of existing directories.
if [ x"$2" != x ] && dpkg --compare-versions "$2" lt 1.4.11+dfsg-3 ; then
chmod 700 /var/lib/openafs/local
fi
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
exit 0
;;
esac
# dh_installdeb will replace this with shell code automatically generated by
# other debhelper scripts.
#DEBHELPER#
exit 0

46
src/packaging/Debian/openafs-fileserver.postrm
View File

@ -1,46 +0,0 @@
#! /bin/sh
# postrm script for openafs-fileserver
#
# Purges various extra configuration files and data files created by the
# package. Whether to purge KeyFile is a bit iffy since the user created it
# with asetkey or with bos addkey, but it always exists for any running server
# and we shouldn't be losing any critical data.
#
# We intentionally don't remove NetInfo and NetRestrict in
# /var/lib/openafs/local since those are created separately by the user and
# may contain information not stored elsewhere.
set -e
case "$1" in
purge)
for file in CellServDB CellServDB.old KeyFile ThisCell UserList ; do
rm -f "/etc/openafs/server/$file"
done
for file in SALVAGE.fs fssync.sock salvage.lock sysid sysid.old ; do
rm -f "/var/lib/openafs/local/$file"
done
rm -f /etc/openafs/BosConfig
for file in BosLog FileLog SalvageLog VolserLog ; do
rm -f "/var/log/openafs/$file"
rm -f "/var/log/openafs/$file.old"
done
# Clean up after files left behind from older versions of the package.
if [ -d /etc/openafs/server-local ] ; then
for file in SALVAGE.fs fssync.sock salvage.lock sysid sysid.old ; do
rm -f "/etc/openafs/server-local/$file"
done
rmdir --ignore-fail-on-non-empty /etc/openafs/server-local
fi
;;
remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;
*)
echo "postrm called with unknown argument \`$1'" >&2
exit 0
esac
#DEBHELPER#

14
src/packaging/Debian/openafs-fileserver.templates
View File

@ -1,14 +0,0 @@
Template: openafs-fileserver/thiscell
Type: string
_Description: Cell this server serves files for:
AFS fileservers belong to a cell. They have the key for that cell's
Kerberos service and serve volumes into that cell. Normally, this cell is
the same cell as the workstation's client belongs to.
Template: openafs-fileserver/alpha-broken
Type: note
_Description: OpenAFS file server probably does not work!
You are running the OpenAFS file server package on an alpha. This
probably doesn't work; the DES code is flaky on the alpha, along with the
threaded file server. Likely, the fileserver will simply fail to start,
but if it does load, data corruption may result. You have been warned.

1
src/packaging/Debian/openafs-fuse.dirs
View File

@ -1 +0,0 @@
usr/share/doc

1
src/packaging/Debian/openafs-fuse.install
View File

@ -1 +0,0 @@
debian/tmp/usr/sbin/afsd.fuse usr/sbin

1
src/packaging/Debian/openafs-fuse.links
View File

@ -1 +0,0 @@
/usr/share/man/man8/afsd.8.gz usr/share/man/man8/afsd.fuse.8.gz

1
src/packaging/Debian/openafs-kpasswd.dirs
View File

@ -1 +0,0 @@
usr/share/doc

23
src/packaging/Debian/openafs-kpasswd.install
View File

@ -1,23 +0,0 @@
debian/tmp/usr/bin/kpasswd usr/bin
debian/tmp/usr/sbin/kas usr/bin
debian/tmp/usr/share/man/man1/kpasswd.1 usr/share/man/man1
debian/tmp/usr/share/man/man8/kas.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_apropos.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_create.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_delete.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_examine.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_forgetticket.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_help.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_interactive.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_list.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_listtickets.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_noauthentication.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_quit.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_setfields.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_setpassword.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_statistics.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_stringtokey.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/kas_unlock.8 usr/share/man/man8

14
src/packaging/Debian/openafs-krb5.NEWS
View File

@ -1,14 +0,0 @@
openafs-krb5 (1.4.7.dfsg1-1) unstable; urgency=low
This package now includes a Kerberos v5 version of klog, klog.krb5,
which authenticates via Kerberos v5 to obtain tokens. When this package
is installed, that version of klog becomes the default. This is correct
for any site that uses Kerberos v5 for AFS authentication
klog is managed by alternatives. If your site still uses the AFS
kaserver or otherwise requires use of the old AFS protocol to obtain
tokens with klog, run update-alternatives --config /usr/bin/klog and
select klog.afs as the default instead of klog.krb5.
-- Russ Allbery <rra@debian.org> Thu, 01 May 2008 16:44:12 -0700

11
src/packaging/Debian/openafs-krb5.install
View File

@ -1,11 +0,0 @@
debian/tmp/usr/bin/aklog usr/bin
debian/tmp/usr/bin/klog.krb5 usr/bin
debian/tmp/usr/bin/asetkey usr/sbin
debian/tmp/usr/sbin/ka-forwarder usr/sbin
debian/tmp/usr/share/man/man1/aklog.1 usr/share/man/man1
debian/tmp/usr/share/man/man1/klog.krb5.1 usr/share/man/man1
debian/tmp/usr/share/man/man8/asetkey.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/ka-forwarder.8 usr/share/man/man8

14
src/packaging/Debian/openafs-krb5.postinst
View File

@ -1,14 +0,0 @@
#!/bin/sh
set -e
if [ "$1" = configure ] || [ "$1" = reconfigure ] ; then
update-alternatives --install /usr/bin/klog klog \
/usr/bin/klog.krb5 20 \
--slave /usr/share/man/man1/klog.1.gz klog.1.gz \
/usr/share/man/man1/klog.krb5.1.gz
fi
#DEBHELPER#
exit 0

11
src/packaging/Debian/openafs-krb5.prerm
View File

@ -1,11 +0,0 @@
#!/bin/sh
set -e
if [ "$1" = remove ] || [ "$1" = deconfigure ] ; then
update-alternatives --remove klog /usr/bin/klog.krb5
fi
#DEBHELPER#
exit 0

16
src/packaging/Debian/openafs-modules-dkms.dkms
View File

@ -1,16 +0,0 @@
# DKMS configuration for the OpenAFS kernel module. -*- sh -*-
# The version is replaced at build time by dh_dkms invoked in debian/rules.
PACKAGE_NAME="openafs"
PACKAGE_VERSION="#MODULE_VERSION#"
BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
DEST_MODULE_LOCATION[0]="/updates/dkms/"
AUTOINSTALL=yes
MAKE[0]="(./configure --disable-linux-syscall-probing \
--with-linux-kernel-packaging \
--with-linux-kernel-headers=${kernel_source_dir} \
&& make \
&& mv src/libafs/MODLOAD-*/openafs.ko .)"
CLEAN="rm -f openafs.ko && make clean"

1
src/packaging/Debian/openafs-modules-dkms.docs
View File

@ -1 +0,0 @@
README

2
src/packaging/Debian/openafs-modules-source.docs
View File

@ -1,2 +0,0 @@
README
debian/README.modules

2
src/packaging/Debian/po/POTFILES.in
View File

@ -1,2 +0,0 @@
[type: gettext/rfc822deb] openafs-client.templates
[type: gettext/rfc822deb] openafs-fileserver.templates

254
src/packaging/Debian/po/cs.po
View File

@ -1,254 +0,0 @@
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.1-3\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:23-0800\n"
"Last-Translator: Martin Sin <martin.sin@seznam.cz>\n"
"Language-Team: Czech <debian-l10n-czech@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Jména počítačů s DB serverem vaší domovské buňky:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS používá k uchovávání seznamu serverů, které mají být kontaktovány při "
"hledání částí buňky, soubor /etc/openafs/CellServDB. Buňka, do které tato "
"stanice patří, není ve zmíněném souboru uvedena. Zadejte mezerami oddělená "
"jména databázových serverů. DŮLEŽITÉ: pokud vytváříte novou buňku a tento "
"počítač bude databázovým serverem této buňky, pak stačí pouze zadat jméno "
"počítače; ostatní servery přidejte později až po jejich zprovoznění. Dokud "
"nebude buňka nastavena, tak na tomto serveru nepovolujte spuštění AFS "
"klienta při startu serveru. Až budete připraveni, můžete klienta povolit "
"úpravou souboru /etc/openafs/afs.conf.client."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Buňka AFS, ke které náleží tento počítač:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Souborový prostor systému AFS je uspořádán do buněk nebo administrativních "
"domén. Každá stanice patří jedné buňce. Obvykle je buňkou doménové jméno "
"skupiny."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Velikost cache AFS v kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS používá určitý prostor na disku pro cachování vzdálených souborů, aby k "
"nim měl rychlejší přístup. Tato cache bude připojena do /var/cache/openafs. "
"Je důležité, aby cache nepřeplnila oblast na které je umístěna. Často je "
"užitečné umístit cache AFS do své vlastní diskové oblasti."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Spustit klienta Openafs nyní a při zavádění počítače?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Běžně většina uživatelů balíčku openafs-client očekává, že bude AFS "
"připojeno automaticky při startu počítače. Samozřejmě, pokud plánujete "
"nastavení nové buňky, nebo používáte laptop, pak byste zřejmě AFS při startu "
"spouštět nechtěli. Zvolíte-li možnost nespouštět AFS při startu počítače, "
"můžete klienta spustit ručně příkazem /etc/init.d/openafs-client force-start."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Hledat buňky AFS v DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Pro kontaktování buňky AFS potřebujete znát IP adresu databázového serveru "
"buňky. Obvykle lze tuto informaci přečíst ze souboru /etc/openafs/"
"CellServDB. Nicméně pokud Openafs nemůže najít buňku v tomto souboru, může "
"použít DNS pro vyhledání AFSDB záznamů, které obsahují požadované informace."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "Šifrovat autentikovaný provoz se souborovým serverem AFS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS poskytuje slabou formu šifrování, která může být nepovinně použita mezi "
"klientem a souborovým serverem. Přestože je toto šifrování slabší než DES a "
"tedy není dostatečné pro velmi důvěrná data, poskytuje určitou formu utajení "
"a určitě tak ztíží práci náhodnému útočníkovi."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Vygenerovat obsah /afs dynamicky?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs obvykle obsahuje záznam pro každou buňku, se kterou může klient "
"hovořit. Tradičně jsou tyto záznamy vytvářeny servery v mateřské buňce "
"klienta. Klienti OpenAFS však mohou generovat obsah adresáře /afs dynamicky "
"na základě souboru /etc/openafs/CellServDB a systému DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Pokud vytváříte /afs dynamicky, možná budete muset vytvořit /etc/openafs/"
"CellAlias pro začlenění aliasů běžných buněk. (Syntaxe tohoto souboru je "
"jeden řádek na alias, který se skládá ze jména buňky, mezery a pak následuje "
"alias pro tuto buňku.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "Použít fakestat pro obejití zatuhnutí při výpisu /afs?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Protože je AFS globální souborový prostor, mohou operace na adresáři /afs "
"výzrazně zvýšit provoz na síti. Pokud jsou některé buňky AFS nedosažitelné, "
"pak může prohlížení /afs pomocí příkazu ls nebo grafického prohlížeče "
"způsobit zatuhnutí počítače na dobu několika minut. AFS má volbu, která "
"simuluje odpovědi pro tyto operace a tak se snaží vyhnout popsaným výpadkům. "
"Tuto volbu budete chtít použít ve většině případů."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Buňka, které bude tento server poskytovat soubory:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Souborové servery AFS náleží buňce. Servery mají klíč ke službě Kerberos "
"dané buňky a v rámci buňky nabízejí souborové svazky. Tato buňka je obvykle "
"shodná s buňkou, ke které patří klient na pracovní stanici."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Souborový server OpenAFS pravděpodobně nepracuje!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Souborový server OpenAFS běží na Aplha systému, což pravděpodobně nebude "
"fungovat; DES kód se ve spojení s vlákny na souborovém serveru chová "
"podivně. Souborový server nejpravděpodobněji vůbec nespustí nespustí, ale "
"pokud naběhne, může dojít ke ztrátě dat. Byli jste varováni."
#~ msgid "How large is your AFS cache (kB)?"
#~ msgstr "Jak velká je vaše cache AFS (v kB)?"

282
src/packaging/Debian/po/de.po
View File

@ -1,282 +0,0 @@
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.2-3\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2006-11-24 22:34+0200\n"
"Last-Translator: Henrik Kroeger <henrik_kroeger@arcor.de>\n"
"Language-Team: Debian German <debian-l10n-german@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Rechnername des Datenbank-Servers für Ihre Home-Zelle:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS benutzt die Datei /etc/openafs/CellServDB für eine Liste von Servern, "
"die angesprochen werden sollen, um Teile einer Zelle zu finden. Die Zelle, "
"von der Sie sagen, diese Workstation gehöre zu ihr, ist nicht in dieser "
"Datei. Geben Sie die Hostnamen der Datenbank-Server ein, getrennt durch "
"Leerzeichen. WICHTIG: Falls Sie eine neue Zelle erstellen und dieser "
"Computer der Datenbank-Server der Zelle sein soll, geben Sie nur den "
"Hostnamen dieses Computers ein; fügen Sie andere Server erst später hinzu, "
"sobald diese funktionieren. Außerdem sollten Sie den AFS-Client auf diesem "
"Server nicht beim Rechnerstart starten lassen, bevor diese Zelle "
"konfiguriert ist. Wenn Sie soweit sind, können Sie /etc/openafs/afs.conf."
"client editieren, um den AFS-Client zu aktivieren."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "AFS-Zelle, zu der diese Workstation gehört:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Der AFS-Dateiraum ist in Zellen bzw. administrativen Domains organisiert. "
"Jede Workstation gehört zu einer Zelle. Normalerweise ist eine Zelle gleich "
"dem DNS Domain-Namen."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Größe des AFS-Cache in kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS benutzt einen Bereich der Festplatte, um Netzwerk-Dateien zum "
"schnelleren Zugriff zwischenzuspeichern. Dieser Cache wird unter /var/cache/"
"openafs eingehängt werden. Es ist wichtig, dass der Cache nicht die "
"Partition überfüllt, auf dem er sich befindet. Viele Leute finden es "
"nützlich, eine extra Partition für ihren AFS-Cache zu haben. "
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Soll der Openafs-Client jetzt und beim Booten gestartet werden?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Normalerweise erwarten Benutzer, die das Paket openafs-client installieren, "
"dass AFS automatisch beim Boot eingehängt wird. Falls Sie aber eine neue "
"Zelle erstellen wollen, oder einen Laptop benutzen, möchten Sie es "
"vielleicht nicht beim Boot gestartet haben. Wenn Sie sich dafür "
"entscheiden, AFS nicht beim Rechnerstart zu starten, können Sie /etc/init.d/"
"openafs-client force-start ausführen, um den AFS-Client zu starten. "
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Sollen AFS-Zellen im DNS nachgeschlagen werden?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Um eine AFS-Zelle zu kontaktieren, brauchen Sie die IP-Adressen der "
"Datenbank-Server der Zellen. Normalerweise werden diese Informationen aus "
"der Datei /etc/openafs/CellServDB gelesen. Falls Openafs aber keine Zelle in "
"dieser Datei finden kann, kann auch DNS benutzt werden, um nach AFSDB-EintrÃ"
"¤gen zu suchen, die diese Information enthalten."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
"Soll authentifizierter Verkehr mit AFS-Dateiservern verschlüsselt werden?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS bietet eine schwache Form der Verschlüsselung, die optional zwischen "
"Client und Dateiserver benutzt werden kann. Obwohl diese Verschlüsselung "
"schwächer als DES und daher nicht ausreichend für sehr vertrauliche Daten "
"ist, macht es einem möglichen Angreifer die Arbeit dennoch deutlich "
"schwerer."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Soll der Inhalt von /afs dynamisch generiert werden?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs enthält einen Eintrag für jede Zelle, mit der der Client interagieren "
"kann. Normalerweise werden diese Einträge von Servern in der Home-Zelle des "
"Clients generiert. Trotzdem kann aber der OpenAFS-Client den Inhalt von /afs "
"dynamisch anhand der Informationen von /etc/openafs/CellServDB und DNS "
"erstellen."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Wenn Sie /afs dynamisch erstellen lassen, werden Sie vielleicht /etc/openafs/"
"CellAlias erstellen müssen, sodass die Datei Aliase für gebräuchliche "
"Zellen enthält. Die Syntax ist: Eine Zeile pro Aliase, mit Zellenname - "
"Leerzeichen - Alias."
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"Soll fakestat benutzt werden, um eine Verzögerung beim Auflisten von /afs "
"zu vermeiden?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Da AFS ein globaler Dateiraum ist, können Operationen im /afs-Verzeichnis "
"zu großen Netzverkehr führen. Wenn einige AFS-Zellen nicht erreichbar sind, "
"kann das Anschauen von /afs (mit ls oder einem Dateibrowser) zu "
"minutenlangem Aufhängen führen. AFS kann aber Antworten zu solchen "
"Operationen simulieren, um ein Aufhängen zu vermeiden. Die meisten Leute "
"wollen das."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Zelle, für die dieser Server Dateien ausliefert:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"AFS-Dateiserver gehören zu einer Zelle. Die Server haben den Schlüssel "
"für den Kerberos-Service der Zelle und stellen Volumes für die Zelle "
"bereit. Normalerweise ist die Zelle identisch mit der des Clients."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Der OpenAFS-Dateiserver wird wahrscheinlich nicht funktionieren!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Sie benutzen den OpenAFS-Dateiserver auf einer Alpha-Maschine. Das "
"funktioniert wahrscheinlich nicht; der DES-Code unter Alpha zusammen mit dem "
"Dateiserver im Thread-Modus ist fehlerhaft. Wahrscheinlich wird der "
"Dateiserver einfach nicht starten, aber wenn er gestartet wird, könnte "
"Datenverlust die Folge sein. Sie wurden gewarnt."
#~ msgid "Upgrading will move files to new locations; continue?"
#~ msgstr "Upgraden wird Dateien an neue Orte verschieben; Fortfahren?"
#~ msgid ""
#~ "Between Openafs 1.1 and Openafs 1.2, several files moved. In particular, "
#~ "files in /etc/openafs/server-local have been distributed to other "
#~ "locations. The BosConfig file is now located in /etc/openafs and the "
#~ "other files are located in /var/lib/openafs. If you continue with this "
#~ "upgrade, these files will be moved. You should use the bos restart "
#~ "command to reload your servers. Any configuration changes made before "
#~ "you do so will be lost."
#~ msgstr ""
#~ "Zwischen Openafs 1.1 und Openafs 1.2, wurden einige Dateien verschoben. "
#~ "Besonders Dateien in /etc/openafs/server-local sind betroffen. Die "
#~ "BosConfig-Datei ist nun unter /etc/openafs zu finden und alle anderen "
#~ "Dateien sind unter /var/lib/openafs. Wenn Sie mit dem Upgrade fortfahren, "
#~ "werden diese Dateien verschoben. Sie sollten den bos restart Befehl "
#~ "verwenden, um Ihre Server neuzustarten. Jede Konfigurationsänderung, die "
#~ "Sie davor machen, wird verloren gehen."

279
src/packaging/Debian/po/es.po
View File

@ -1,279 +0,0 @@
# openafs po-debconf translation to Spanish
# Copyright (C) 2007, 2009 Software in the Public Interest
# This file is distributed under the same license as the openafs package.
#
# Changes:
# - Initial translation
# Javier Ruano Ruano <adrakoa@es.gnu.org>, 2007
#
# - Updates
# Francisco Javier Cuadrado <fcocuadrado@gmail.com>, 2009
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.7.dfsg1-6\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:23-0800\n"
"Last-Translator: Francisco Javier Cuadrado <fcocuadrado@gmail.com>\n"
"Language-Team: Debian l10n Spanish <debian-l10n-spanish@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr ""
"Escriba para la celda de «home» los nombres de los servidores de la base de "
"datos:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS utiliza el archivo «/etc/openafs/CellServDB» para mantener una lista de "
"los servidores a los que se consultará para encontrar la distintas partes de "
"una celda. La celda que solicita esta estación de trabajo no está incluida "
"en ese archivo. Introduzca los nombres de los servidores de la base de datos "
"separados por espacios. IMPORTANTE: Si está creando una nueva celda y esta "
"máquina es uno de los servidores de la base de datos en esa celda, "
"introduzca sólo el nombre de esta máquina; añada los demás servidores más "
"tarde cuando estén en funcionamiento. Además, no habilite en el arranque el "
"cliente AFS de ese servidor hasta que configure la celda. Cuando esté "
"preparado, edite el archivo «/etc/openafs/afs.conf.client»."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "La celda AFS de esta máquina pertenece a:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"El espacio de los archivos AFS se organizará en celdas o dominios "
"administrativos. Cada máquina pertenece a una celda. Generalmente la celda "
"es el servidor de nombres de dominio del sitio."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Tamaño de la cache de AFS en kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"Para mejorar la velocidad de acceso, AFS utiliza un espacio del disco para "
"la cache de archivos remotos. Esta cache se montará en «/var/cache/openafs». "
"Es importante que la cache no ocupe más que la partición en la que se ubica. "
"Frecuentemente, la gente encuentra útil dedicar una partición a la cache de "
"AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "¿Desea ejecutar ahora el cliente Openafs y en el arranque?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Normalmente, la mayoría de los usuarios que instalan el paquete «openafs-"
"client» esperan que se monte automáticamente en el arranque. Sin embargo, si "
"tiene pensado configurar una nueva celda o utiliza un portátil, puede que "
"quiera iniciarlo en el arranque. Si elige no iniciar AFS en el arranque, "
"ejecute «/etc/init.d/openafs-client force-start» para iniciar el cliente "
"cuando lo desee."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "¿Desea buscar las celdas AFS en el DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Para conectar a una celda de AFS, necesita la dirección IP de la celda de "
"los servidores de la base de datos. Normalmente, esta información se "
"encuentra en el archivo «/etc/openafs/CellServDB». Sin embargo, si Openafs no "
"encuentra una celda en ese archivo, puede usar el DNS para buscar las copias "
"de los registros de AFSDB que contengan la información."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
"¿Desea cifrar el tráfico de autenticación con el servidor de archivos AFS? "
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS proporciona un mecanismo de cifrado endeble que se puede utilizar "
"opcionalmente entre el cliente y los servidores de archivos. Aunque este "
"cifrado es más débil que DES y por ello no es suficiente para la mayor "
"confidencialidad de los datos, éste ofrece confidencialidad y hace que para "
"un atacante esporádico el trabajo sea sensiblemente más difícil."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "¿Desea crear dinámicamente los contenidos de «/afs»?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"Normalmente «/afs» incluye una entrada por cada celda que un cliente "
"solicita. Tradicionalmente, estas entradas las generan los servidores en la "
"celda del «home» del cliente. Sin embargo, los clientes de OpenAFS pueden "
"generar los contenidos de «/afs» dinámicamente basándose en la información "
"del archivo «/etc/openafs/CellServDB» y del DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Si genera dinámicamente «/afs», necesitará crear el archivo «/etc/openafs/"
"CellAlias» para incluir los seudónimos («alias») de las celdas comunes. (La "
"estructura del archivo es un seudónimo por línea, con el nombre de la celda, "
"un espacio, y después el seudónimo para esa celda)."
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "¿Desea utilizar «fakestat» para evitar que se bloquee al listar «/afs»?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Debido a que AFS es un espacio global de archivos, las operaciones en el "
"directorio «/afs» pueden generar un tráfico de red significativo. Si algunas "
"de las celdas de AFS no están disponibles, al mirar «/afs» usando «ls» o un "
"navegador de archivos gráfico podría bloquear varios minutos la máquina. AFS "
"tiene una opción que simula localmente las respuesta a esas operaciones "
"evitando así estas paradas. Debería seleccionar esta opción en la mayoría de "
"los casos."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Celda para los archivos de este servidor:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Los servidores de archivos de AFS forman parte de una celda. Poseen una "
"clave para la celda del servicio Kerberos y proporciona la capacidad de las "
"celdas. Normalmente, esta celda es la misma que la celda a la que la máquina "
"cliente pertenece."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "¡Seguramente el servidor de archivos OpenAFS no funciona!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Está ejecutando el paquete OpenAFS como servidor de archivos sobre la "
"arquitectura alpha. Es probable que no funcione, el código DES se ha hecho "
"añicos sobre alpha, junto a los hilos del servidor de archivos. De este "
"modo, el servidor de archivos simplemente fallará al iniciarlo, pero si "
"carga, puede producir datos corruptos. Ha sido advertido."

266
src/packaging/Debian/po/fr.po
View File

@ -1,266 +0,0 @@
# translation of fr.po to French
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
# Christian Perrier <bubulle@debian.org>, 2006.
msgid ""
msgstr ""
"Project-Id-Version: fr\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:23-0800\n"
"Last-Translator: Christian Perrier <bubulle@debian.org>\n"
"Language-Team: French <debian-l10n-french@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.2\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr ""
"Hôtes serveurs de bases de données pour votre cellule locale (« home cell ») :"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS utilise le fichier /etc/openafs/CellServDB pour conserver la liste des "
"serveurs à contacter pour trouver les constituants d'une cellule. La cellule "
"dont ce poste de travail est censé faire partie n'est pas indiquée dans ce "
"fichier. Veuillez indiquer les noms des serveurs de bases de données, "
"séparés par des espaces. IMPORTANT : si vous créez une nouvelle cellule et "
"que cette machine doit être un serveur de bases de données dans cette "
"cellule, veuillez seulement indiquer le nom de cette machine. N'ajoutez les "
"autres serveurs que plus tard, lorsqu'ils seront opérationnels. Enfin, "
"n'activez pas le client AFS au démarrage tant que cette cellule n'est pas "
"configurée. Quand vous serez prêt, vous pourrez modifier /etc/openafs/afs."
"conf.client pour mettre en service le client."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Cellule AFS dont ce poste de travail fait partie :"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"L'espace des fichiers AFS est organisé en cellules ou domaines "
"administratifs. Chaque poste de travail appartient à une cellule. "
"Habituellement, la cellule est le nom de domaine du site."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Taille du cache d'AFS (ko) :"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS utilise une partie du disque pour mettre en cache des fichiers distants "
"et accélérer les accès. Ce cache sera monté sur /var/cache/openafs. Il est "
"important que le cache ne remplisse pas la partition sur laquelle il est "
"situé. De nombreux utilisateurs choisissent de dédier une partition au cache "
"d'AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Lancer le client AFS maintenant, puis à chaque démarrage ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"La majorité des utilisateurs qui installent le paquet openafs-client "
"s'attendent à ce qu'il soit lancé au démarrage. Cependant, si vous prévoyez "
"de mettre en service une nouvelle cellule ou si vous utilisez un ordinateur "
"portable, vous ne souhaitez peut-être pas le lancer au démarrage. Si vous "
"préférez ne pas le lancer au démarrage, utilisez la commande « /etc/init.d/"
"openafs-client force-start » pour le lancer quand vous en aurez besoin."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Faut-il chercher les cellules AFS dans le DNS ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Afin de contacter une cellule AFS, vous avez besoin des adresses IP de ses "
"serveurs de bases de données. Cette information est normalement extraite de /"
"etc/openafs/CellServDB. Cependant, si OpenAFS ne peut pas trouver de cellule "
"dans ce fichier, il peut utiliser le DNS pour rechercher des enregistrements "
"AFSDB qui fourniront cette information."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
"Faut-il chiffrer le trafic authentifié avec le serveur de fichiers AFS ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS offre un mode de chiffrement faible qu'il est possible d'utiliser entre "
"un client et les serveurs de fichiers. Bien que ce chiffrement soit plus "
"faible que DES, et donc insuffisant pour des données hautement "
"confidentielles, il fournit une certaine forme de confidentialité et peut "
"rendre une attaque non préparée nettement plus difficile."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Faut-il gérer le contenu de /afs dynamiquement ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"Le répertoire /afs contient généralement une entrée par cellule accessible à "
"un client donné. Traditionnellement, ces entrées ont été créées par les "
"serveurs dans la cellule locale de chaque client. Cependant, OpenAFS peut "
"gérer dynamiquement le contenu de /afs en se servant de /etc/openafs/"
"CellServDB et du DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Si vous créez /afs de manière dynamique, vous aurez peut-être à créer /etc/"
"openafs/CellAlias pour inclure les alias des cellules communes. Ce fichier "
"comporte une ligne par alias, avec le nom de la cellule, une espace et "
"l'alias utilisé pour la cellule."
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"Utiliser fakestat pour éviter les erreurs à l'affichage du contenu de /afs ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Comme AFS est un espace global de fichiers, les opérations sur /afs peuvent "
"générer un trafic réseau non négligeable. Si certaines cellules sont "
"indisponibles, l'affichage de /afs avec ls ou avec un gestionnaire de "
"fichiers graphique peut stopper votre machine pour quelques minutes. AFS "
"comporte une option permettant de simuler les réponses à ces requêtes pour "
"éviter ces plantages. Cette option est utile dans la plupart des cas."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Cellule pour laquelle ce serveur est un serveur de fichiers :"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Les serveurs de fichiers AFS appartiennent à une cellule. Ils possèdent la "
"clé pour le service Kerberos de cette cellule et y mettent à disposition des "
"volumes. Normalement, cette cellule est la même que celle à laquelle "
"appartient le client."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Le serveur de fichiers OpenAFS ne fonctionne probablement pas"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Vous utilisez le paquet du serveur de fichier OpenAFS sur une plateforme "
"alpha. Cela ne fonctionne probablement pas ; le code DES est défectueux sur "
"ces plateformes de même que le serveur de fichiers à processus légers. Il "
"est probable que le serveur refusera tout simplement de démarrer. Cependant, "
"s'il démarre quand même, des corruptions de données peuvent avoir lieu."

247
src/packaging/Debian/po/gl.po
View File

@ -1,247 +0,0 @@
# Galician translation of openafs's debconf templates
# This file is distributed under the same license as the openafs package.
# Jacobo Tarrio <jtarrio@debian.org>, 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:23-0800\n"
"Last-Translator: Jacobo Tarrio <jtarrio@debian.org>\n"
"Language-Team: Galician <proxecto@trasno.net>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Nomes dos servidores de bases de datos para a cela inicial:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS emprega o ficheiro /etc/openafs/CellServDB para manter a lista de "
"servidores cos que se hai que comunicar para atopar partes dunha cela. A "
"cela á que di que esta estación de traballo pertence non figura nese "
"ficheiro. Introduza os nomes dos servidores de bases de datos, separados por "
"espazos. IMPORTANTE: Se está a crear unha nova cela e esta máquina ha ser un "
"servidor de bases de datos desa cela, introduza só o nome desta máquina; "
"engada os nomes dos outros servidores despois, cando xa estean a funcionar. "
"Ademáis, non permita que o cliente AFS arrinque no inicio do ordenador ata "
"que a cela estea configurada. Cando estea preparado pode editar o ficheiro /"
"etc/openafs/afs.conf.client para activar o cliente."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Cela AFS á que pertence esta estación de traballo:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"O espazo de ficheiros AFS está organizado en celas ou dominios "
"administrativos. Cada estación de traballo pertence a unha cela. Normalmente "
"a cela está no nome de dominio DNS do sitio."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Tamaño da caché AFS en kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS emprega unha área do disco para facer unha caché dos ficheiros remotos "
"para un acceso máis rápido. Esta caché hase montar en /var/cache/openafs. É "
"importante que a caché non se faga máis grande que a partición na que está "
"situada. A miúdo é útil adicar unha partición á caché AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "¿Executar o cliente Openafs agora e no inicio?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Normalmente, a maioría dos usuarios que instalan o paquete openafs-client "
"esperan que AFS se monte automaticamente ao arrincar o sistema. "
"Nembargantes, se pretende configurar unha nova cela ou emprega un ordenador "
"portátil, pode que non queira inicialo co sistema. Se prefire non iniciar "
"AFS co sistema, execute /etc/init.d/openafs-client force-start para iniciar "
"o cliente cando o queira executar."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "¿Buscar as celas AFS en DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Para se comunicar cunha cela AFS, precisa dos enderezos IP dos servidores de "
"base de datos da cela. Normalmente, esta información lese de /etc/openafs/"
"CellServDB. Nembargantes, se Openafs non pode atopar unha cela nese "
"ficheiro, pode empregar DNS para buscar rexistros AFSDB que conteñan a "
"información."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "¿Cifrar o tráfico autenticado co servidor de ficheiros AFS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS fornece unha forma feble de cifrado que se pode empregar, opcionalmente, "
"entre un cliente e os servidores de ficheiros. Aínda que este cifrado é máis "
"feble que DES, e polo tanto non é dabondo para datos altamente "
"confidenciais, si que fornece algunha confidencialidade e seguramente faga o "
"traballo dun potencial atacante significativamente máis complicado."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "¿Xerar o contido de /afs dinamicamente?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs adoita conter unha entrada por cada cela coa que un cliente se pode "
"comunicar. Tradicionalmente, esas entradas xerábanas os servidores da cela "
"inicial do cliente. Nembargantes, os clientes OpenAFS poden xerar o contido "
"de /afs dinamicamente baseándose no contido de /etc/openafs/CellServDB e DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Se xera /afs dinamicamente, pode ter que crear /etc/openafs/CellAlias para "
"incluír os alias dalgunhas celas habituais. (A sintaxe deste ficheiro é unha "
"liña por alias, co nome da cela, un espazo, e despois o alias desa cela)."
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "¿Empregar fakestat para evitar esperas ao ver o listado de /afs?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Como AFS é un espazo de ficheiros global, as operacións no directorio /afs "
"poden xerar unha cantidade significativa de tráfico na rede. Se algunhas "
"celas AFS non están dispoñibles, ver o contido de /afs empregando ls ou un "
"navegador gráfico de ficheiros pode facer que a máquina se deteña durante "
"varios minutos. AFS ten unha opción para simular respostas a esas operacións "
"de xeito local para evitar esas esperas. Na maioría dos casos emprégase esta "
"opción."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Cela para a que este servidor serve ficheiros:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Os servidores de ficheiros AFS pertencen a celas. Teñen a clave do servizo "
"Kerberos desa cela e serven volumes na cela. Normalmente, esta cela é a "
"mesma cela á que pertence o cliente da estación de traballo."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "O servidor de ficheiros OpenAFS probablemente non funcione"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Está a executar o paquete servidor de ficheiros OpenAFS nun Alpha. "
"Probablemente isto non funcione; o código DES ten fallos no Alpha, igual que "
"o servidor de ficheiros con fíos. O máis probable é que o servidor de "
"ficheiros non se inicie, pero se se inicia, pódese causar corrupción de "
"datos."

266
src/packaging/Debian/po/ja.po
View File

@ -1,266 +0,0 @@
# Copyright (C) 2008-2009 Russ Allbery <rra@debian.org>
# This file is distributed under the same license as openafs package.
# Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2009.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.5.50.dfsg1\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-03-28 11:26+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
"Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "ホームセルの DB サーバホスト名:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS はセルの各パートを検索するのに使用する確認先サーバのリストを保持するの"
"に /etc/openafs/CellServDB ファイルを使います。あなたがこのワークステーション"
"が属していると指定しているセルは、このファイル上にありません。データベース"
"サーバのホスト名を空白で区切って入力してください。「重要」：新しいセルを作っ"
"て、このマシンがそのセルでのデータベースサーバになった場合、このマシンの名前"
"のみを入力してください。他のサーバが動作するようになった後で、そのサーバを追"
"加してください。そして、セルが設定されるまで、このサーバでは AFS クライアント"
"を起動時に開始しないようにしてください。設定が完了して準備が整ったら /etc/"
"openafs/afs.conf.client を編集してクライアントを有効にしてください。"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "このワークステーションが所属する AFS セル:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"AFS ファイル空間はセルや管理ドメインから成ります。各ワークステーションは一つ"
"のセルに属します。通常セルはサイトの DNS ドメイン名です。"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "AFS キャッシュサイズ (kB):"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS はより速いアクセスを行うために、ディスクの一部をリモートファイルのキャッ"
"シュとして使います。このキャッシュは /var/cache/openafs にマウントされます。"
"重要なのはキャッシュが置かれたパーティションを過度に圧迫しない事です。多くの"
"場合、AFS キャッシュを専用のパーティションに割り当てるのが適していることで"
"しょう。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Openafs クライアントを今すぐ、そして起動時に実行しますか?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"通常、openafs-client パッケージをインストールしたユーザの大半は起動時に自動的"
"に AFS をマウントすることを期待しています。しかし、新しいセルを設定しようとし"
"ている、あるいはノート PC で作業している場合は起動時に開始したくないかもしれ"
"ません。起動時に AFS を開始しないのを選んだ場合は、実行したくなったときに /"
"etc/init.d/openafs-client force-start を実行してクライアントを開始してくださ"
"い。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "AFS セルの検索を DNS で行いますか?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"AFS セルに接続するためには、セルのデータベースサーバ群の IP アドレスが必要で"
"す。通常、この情報は /etc/openafs/CellServDB で参照できます。しかし、Openafs "
"がそのファイル中でセルを見つけられなかった場合、DNS を使ってその情報を含む "
"AFSDB レコードを検索することができます。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "AFS ファイルサーバへの認証トラフィックを暗号化しますか?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS はクライアントとファイルサーバ間で使うこともできる弱い暗号化形式を提供し"
"ています。この暗号化は DES よりも弱く、そのため非常に重要なデータを取り扱うに"
"は不十分ですが、ある程度の隠匿性は提供しており、技術力の低い攻撃者の作業をか"
"なり難しくするでしょう。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "/afs の内容を動的に生成しますか?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs は通常クライアントが通信できる各セルのエントリを含んでいます。慣例上、こ"
"れらのエントリはクライアントのホームセル内にサーバによって生成されています。"
"しかし、OpenAFS クライアントは /afs の内容を /etc/openafs/CellServDB の内容"
"と DNS を元にして動的に生成することができます。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"/afs を動的に生成する場合、共通のセルのエイリアスを含むために /etc/openafs/"
"CellAlias を作成する必要があります (このファイルのシンタックスはエイリアスご"
"とに 1 行で、セルの名前・空白・そしてセルのエイリアス、となります)。"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"/afs をリストアップする際にハングアップを避けるため、fakestat を使いますか?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"AFS は巨大なファイル空間であるため、/afs ディレクトリでの操作は膨大なネット"
"ワークトラフィックを生成することがあります。もし、いくつかの AFS セルが利用で"
"きなくなり、その際に /afs で ls やグラフィカルなファイルブラウザを実行して参"
"照すると、数分間はマシンがハングアップするでしょう。AFS はこのようなハング"
"アップを避けるため、これらの操作に対してローカルで答えをシミュレートするオプ"
"ションがあります。多くの場合、このオプションを有効にしておいた方が良いでしょ"
"う。"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "このサーバがファイルを提供するセル:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"AFS のファイルサーバ群は一つのセルに属しています。このファイルサーバ群は、セ"
"ルの Kerberos サービスについての鍵を持っており、ボリュームをこれらのセルに提"
"供します。通常、このセルはワークステーションのクライアントが属しているのと同"
"じセルです。"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "OpenAFS ファイルサーバは恐らく動作しません!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"OpenAFS ファイルサーバを alpha アーキテクチャ上で動作させています。これは恐ら"
"く動作しません。DES コードは alpha 上で、加えてスレッドで動作するファイルサー"
"バでは怪しげなものです。最もありえるのはファイルサーバは起動せず、もし動作し"
"たとしてもデータの損傷が起こるであろうということです。警告しました。"
#~ msgid "Upgrading will move files to new locations; continue?"
#~ msgstr ""
#~ "アップグレードによってファイルは新しい場所に移動されます。続行しますか?"
#~ msgid ""
#~ "Between Openafs 1.1 and Openafs 1.2, several files moved. In particular, "
#~ "files in /etc/openafs/server-local have been distributed to other "
#~ "locations. The BosConfig file is now located in /etc/openafs and the "
#~ "other files are located in /var/lib/openafs. If you continue with this "
#~ "upgrade, these files will be moved. You should use the bos restart "
#~ "command to reload your servers. Any configuration changes made before "
#~ "you do so will be lost."
#~ msgstr ""
#~ "Openafs 1.1 と Openafs 1.2 では、複数のファイルが移動しています。特に、/"
#~ "etc/openafs/server-local にあるファイルは他の位置へと移動されています。"
#~ "BosConfig ファイルは新たに /etc/openafs に移動し、他のファイルは /var/lib/"
#~ "openafs に位置することになります。このアップグレードを続行したい場合は、こ"
#~ "れらのファイルは移動されます。以前に行った設定の変更は、アップグレードに"
#~ "よって失われます。再起動コマンドをサーバを再ロードするのに bos を使う必要"
#~ "があります。この作業のため、設定に対して以前に加えられた変更は失われます。"

258
src/packaging/Debian/po/nl.po
View File

@ -1,258 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:24-0800\n"
"Last-Translator: Bart Cornelis <cobaco@skolelinux.no>\n"
"Language-Team: debian-l10n-dutch <debian-l10n-dutch@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: nl\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Computernamen van de DB-servers voor uw thuiscel:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS houdt in het bestand '/etc/openafs/CellServDB een lijst bij van servers "
"die gecontacteerd moeten worden bij het zoeken naar delen van een cel. De "
"cel waartoe dit werkstation volgens wat u aangaf behoort, is niet terug te "
"vinden in dit bestand. Gelieve dus de computernamen van de databaseservers "
"op te geven, gescheiden met spaties. OPGELET: als bezig bent een nieuwe cel "
"op te zetten en deze machine als databaseserver voor deze cel zal fungeren "
"dient u hier enkel de naam van deze machine in te geven; u kunt verdere "
"servers dan later toevoegen eens alles functioneert. Zorg er ook voor dat u "
"het opstarten van de AFS-client tijdens het opstarten van de machine niet "
"activeert voordat de cel geconfigureerd is, zodra u daarmee klaar bent kunt "
"u /etc/openafs/afs.conf.client aanpassen om het automatisch opstarten van de "
"client tijdens de machinestart te activeren."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Tot welke AFS-cel behoort dit werkstation?"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Een AFS-bestandsruimte is georganiseerd in cellen of administratieve "
"domeinen. Elk werkstation behoort tot 1 cel. Gewoonlijk is deze cel de DNS-"
"domeinnaam van de site."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Grootte van de AFS-cache in kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS gebruikt ruimte op de schijf als cache, zodat toegang tot bestanden op "
"andere systemen sneller werkt. Deze cache wordt aangekoppeld in /var/cache/"
"openafs. Het is belangrijk dat de cache niet groter wordt dan de partitie "
"waarop deze zich bevindt. Vaak is het handig om een partititie te hebben met "
"enkel de AFS-cache."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Wilt u de Openafs-client nu en tijdens het opstarten draaien?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Gebruikers die het 'openafs-client'-pakket installeren verwachten meestal "
"dat AFS automatisch aangekoppeld wordt tijdens het opstarten. Als u echter "
"van plan bent een nieuwe cel op te zetten, of als deze machine een laptop "
"is, wilt u wellicht niet dat AFS tijdens het opstarten aangekoppeld wordt. U "
"kunt AFS op elk moment starten met het commando '/etc/init.d/openafs-client "
"force-start."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "AFS-cellen opzoeken in DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Om een AFS-cel te contacteren dient u het IP-adres van de databaseserver "
"voor die cel te hebben. Normaal is deze informatie beschikbaar in /etc/"
"openafs/CellServDB. Openafs biedt de mogelijkheid om de AFSDB-records op te "
"zoeken via DNS wanneer dit bestand niet aanwezig is."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
"Wilt u dat geauthenticeerd verkeer met de AFS-bestandsserver versleuteld "
"word?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS biedt een zwakke encryptievorm aan die optioneel kan gebruikt worden bij "
"de communicatie tussen de client en bestandsservers. Hoewel deze encryptie "
"zwakker is dan DES, en dus niet voldoende is voor hoogvertrouwelijke data, "
"biedt het enige betrouwbaarheid daar het de taak van een niet-gerichte "
"aanval significant moeilijker maakt. "
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Wilt u de inhoud van /afs dynamisch genereren?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs bevat een ingang voor elke cel waarmee een client kan communiceren. "
"Traditioneel worden deze ingangen aangemaakt door de servers van de thuiscel "
"van de client. OpenAFS-clients zijn echter in staat om de inhoud van /afs "
"dynamisch te genereren, uitgaande van de data in /etc/openafs/CellServDB en "
"DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Als u ervoor kiest om /afs dynamisch te genereren kan het noodzakelijk zijn "
"om /etc/openafs/CellAlias aan te maken met daarin de aliases voor "
"veelgebruikte cellen. (de syntax van dit bestand is 1 regel per alias, "
"waarbij elke regel bestaat uit een celnaam gevolgd door een spatie en de "
"alias voor die cel)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"Wilt u fakestat gebruiken om vasthangen tijdens het weergeven van de inhoud "
"van /afs tegen te gaan?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Omdat AFS een globale bestandsruimte is kunnen operaties op de '/afs'-map "
"flink wat netwerkverkeer veroorzaken. Wanneer sommige AFS-cellen "
"onbeschikbaar zijn kan het weergeven van /afs in een grafische browser uw "
"machine enkele minuten vasthangen. AFS heeft een optie die antwoorden voor "
"deze operaties lokaal simuleert en zo dit vasthangen vermijdt. Onder de "
"meeste omstandigheden kunt u dit best activeren."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Voor welke cellen biedt deze server bestanden aan?"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"AFS-bestandsservers maken deel uit van een cel. Ze beschikken over de "
"sleutel voor de Kerberos-dienst van die cel, en ondersteunen volumes binnen "
"die cel. Normaal is dit dezelfde cel als waartoe de client op het "
"werkstation behoort."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "De OpenAFS bestandsserver werkt waarschijnlijk niet!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"U draait het OpenAFS bestandsserver pakket op een alpha. Dit werkt "
"waarschijnlijk niet; de DES-code, en de 'threaded' bestandsserver zijn "
"onbetrouwbaar op alpha. In alle waarschijnlijkheid zal de bestandsserver "
"weigeren op te starten, maar als deze toch start is data corruptie "
"waarschijnlijk. U bent gewaarschuwd. "

252
src/packaging/Debian/po/pt.po
View File

@ -1,252 +0,0 @@
# Portuguese translation for openafs debconf messages
# Copyright (C) 2007 Miguel Figueiredo
# This file is distributed under the same license as the openafs package.
# Miguel Figueiredo <elmig@debianpt.org>, 2007.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.2-5\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:24-0800\n"
"Last-Translator: Miguel Figueiredo <elmig@debianpt.org>\n"
"Language-Team: Portuguese <traduz@debianpt.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Nomes de máquinas dos servidores de bases de dados para a sua célula:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"O AFS utiliza o ficheiro /etc/openafs/CellServDB para guardar a lista de "
"servidores que devem ser contactados para encontrar partes de uma célula. A "
"célula que você diz a que esta estação de trabalho pertence não está nesse "
"ficheiro. Introduza os nomes das máquinas dos servidores de bases de dados "
"separados por espaços. IMPORTANTE: Se está a criar uma nova célula e esta "
"máquina é uma máquina que irá servir a base de dados nessa célula, apenas "
"introduza o nome desta máquina; acrescente depois os outros servidores "
"depois de estes estarem a funcionar. Além disso, não habilite o client AFS "
"para iniciar no arranque neste servidor até que a célula esteja "
"configurada. Quando você estiver pronto pode editar /etc/openafs/afs.conf."
"client para habilitar o cliente."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Célula AFS a que esta estação de trabalho pertence:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"O espaço de ficheiros do AFS é organizado em células ou domínios "
"administrativos. Cada estação de trabalho pertence a uma célula. "
"Normalmente a célula é o nome de domínio DNS do site."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Tamanho da cache AFS em kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"O AFS utiliza uma área do disco para fazer cache de ficheiros remotos para "
"um acesso mais rápido. Esta cache irá ser montada em /var/cache/openafs. É "
"importante que a cache não encha a partição em que está localizada. Muitas "
"vezes, algumas pessoas acham útil dedicar uma partição para a sua cache AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Correr o cliente Openafs agora e no arranque?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Normalmente, a maioria dos utilizadores que instalam o pacote openafs-client "
"esperam que o AFS seja montado automaticamente no arranque. No entanto, se "
"você está a planear instalar uma nova célula ou está num portátil pode não "
"querer que seja iniciado no arranque. Se escolher não iniciar o AFS no "
"arranque, corra /etc/init.d/openafs-client force-start para iniciar o "
"cliente quando quiser que este corra."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Procurar por células AFS no DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"De modo a contactar uma célula AFS, você precisa dos endereços IP dos "
"servidores de bases de dados das células. Normalmente, esta informação é "
"lida a partir de /etc/openafs/CellServDB. No entanto, se o Openafs não "
"conseguir encontrar a célula nesse ficheiro, pode utilizar o DNS para "
"procurar por registos AFSDB que contenham esta informação."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "Encriptar tráfico autenticado com o servidor de ficheiros AFS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"O AFS disponibiliza uma forma fraca de encriptação que pode ser utilizada "
"opcionalmente entre um cliente e os servidores de ficheiros. Enquanto que "
"esta encriptação é mais fraca que a DES e por isso não suficiente para dados "
"altamente confidenciais, esta disponibiliza alguma confidencialidade e é "
"provável que torne o trabalho de um casual atacante significativamente mais "
"difícil."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Gerar dinamicamente o conteúdo de /afs?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"O /afs geralmente contém uma entrada para cada célula para a qual cada "
"cliente pode falar. Tradicionalmente, estas entradas foram geradas por "
"servidores na célula do cliente. No entanto, os clientes OpenAFS podem "
"gerar o conteúdo dinamicamente de /afs baseado no conteúdo de /etc/openafs/"
"CellServDB e do DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Se gerar dinamicamente /afs, você pode precisar de criar /etc/openafs/"
"CellAlias para incluir 'aliases' para células usuais. (A sintaxe para este "
"ficheiro é uma linha por alias, com o nome da célula, um espaço, e depois o "
"alias para essa célula.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "Utilizar o fakestat para evitar bloqueios ao listar /afs?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Devido ao AFS ser um espaço de ficheiros global, as operações no directório /"
"afs podem gerar tráfego de rede significativo. Se algumas células AFS não "
"estiverem disponíveis então olhar para /afs utilizando o ls ou um explorador "
"de ficheiros gráfico pode bloquear a sua máquina por minutos. O AFS tem uma "
"opção para simular localmente respostas a essas operações para evitar esses "
"bloqueios. Você irá querer esta opção na maioria das circunstâncias."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Célula para a qual este servidor serve ficheiros:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Os servidores de ficheiros AFS pertencem a uma célula. Estes têm a chave "
"para o serviço Kerberos dessa célula e volumes a servir nessa célula. "
"Normalmente, esta célula é a mesma célula a que pertence o cliente da "
"estação de trabalho."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "O servidor de ficheiros AFS provavelmente não funciona!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Você está a correr o pacote do servidor de ficheiros OpenAFS num alpha. "
"Isto provavelmente não funciona; o código DES tem problemas em alpha, além "
"do servidor de ficheiros com 'threads'. Provavelmente, o servidor de "
"ficheiros irá simplesmente falhar o arranque, mas se carregar, pode resultar "
"em corrupção de dados. Você foi avisado."

268
src/packaging/Debian/po/pt_BR.po
View File

@ -1,268 +0,0 @@
#
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:24-0800\n"
"Last-Translator: André Luís Lopes <andrelop@debian.org>\n"
"Language-Team: Debian-BR Project <debian-l10n-portuguese@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Nomes de host do servidor DB para sua célula home :"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"O AFS usa o arquivo /etc/openafs/CellServDB para armazenar a lista de "
"servidores que deverão ser contactados para se encontrar partes de uma "
"célula. A célula que você diz que essa estação de trabalho pertence não está "
"nesse arquivo. Informe os nomes de hosts dos servidore de base de dados "
"separados por espaços. IMPORTANTE : Caso você esteja criando uma nova célula "
"e esta máquina será um servidor de base de dados na célula, somente informe "
"o nome desta máquina. Adicione os outros servidores posteriormente depois "
"que os mesmos estejam funcionando. Adicionalmente, não habilite o cliente "
"AFS para inicialização em tempo de inicialização neste servidor até que a "
"célula esteja configurada. Quando você estiver terminado você poderá editar "
"o arquivo /etc/openafs/afs.conf.client para habilitar este cliente."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Célula AFS a qual esta estação de trabalho pertence :"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"O espaço de arquivo AFS é organizado em células ou domínios administrativos. "
"Cada estação de trabalho pertence a uma célula. Normalmente a célula é o "
"nome de domínio DNS do site."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Tamanho do cache AFS em kB :"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"O AFS usa uma àrea do disco para fazer cache de arquivos remotos para acesso "
"mais rápido. Esse cache será montando em /var/cache/openafs. É importante "
"que o cache não ocupe toda a partrição na qual está localizado. Geralmente, "
"os usuários AFS acham útil dedicar uma partição para seus caches AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Executar o cliente OpenAFS agora e em tempo de inicialização ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Normalmente, a maioria dos usuários que instalam o pacote openafs-client "
"esperam que o AFS seja montado automaticamente na inicialização. Porém, caso "
"você esteja planejando configurar uma nova célula ou esteja em um laptop, "
"você pode não desejar que o AFS seja iniciado automaticamente no momento da "
"inicialização da máquina. Caso você opte por não iniciar o AFS na "
"inicialização da máquina, execute /etc/init.d/openafs-client force-start "
"para iniciar o cliente quando desejar executá-lo."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Procurar células AFS no DNS ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Para poder contactar uma célula AFS, você precisa dos endereços IP dos "
"servidores de base de dados da célula. Normalmente, esta informação é lida "
"de /etc/openafs/CellServDB. Porém, caso o OpenAFS não possa encontrar uma "
"célula nesse arquivo, o DNS poderá ser usado para pesquisar registros AFSDB "
"que contenham a informação."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "Encriptar o tráfego autenticado com o servidor de arquivos AFS ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"O AFS fornece uma forma fraca de encriptação que pode ser opcionalmente "
"usada entre o cliente e os servidor de arquivos. Enquanto esta encriptação é "
"mais fraca do que DES e portanto não é suficiente para dados altamente "
"confidenciais, essa encriptação fornece alguma confidencialidade e "
"provavelmente torna o trabalho de um atacante casual mais difícil."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Gerar dinamicamente o conteúdo de /afs ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"O /afs geralmente contém uma entrada para cada célula com a qual o cliente "
"pode conversar. Tradicionalmente, essas entradas eram geradas por servidores "
"no célula home do cliente. Porém, clientes OpenAFS podem gerar o conteúdo "
"de /afs dinamicamente baseando-se no conteúdo de /etc/openafs/CellServDB e "
"do DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Caso você gere o /afs dinamicamente, você pode precisar criar o /etc/openafs/"
"CellAlias para incluir apelidos (aliases) para células comuns. (A sintaxe "
"desse arquivo é uma linha por apelido, com o nome da célula, um espaço e "
"depois o apelido para a célula.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "Usar fakestat para evitar travadas na listagem do /afs ?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Devido ao AFS ser um espaço de arquivos global, operações no diretório /afs "
"podem gerar um tráfego de rede significativo. Caso algumas células AFS não "
"estejam disponíveis, pesquisar o /afs usando o comando \"ls\" ou um "
"gerenciador de arquivos gráfico pode travar sua máquina por alguns minutos. "
"O AFS possui uma opção para simular respostas para essas operações "
"localmente para evitar essas travadas. Você irá desejar usar esta opção na "
"maioria dos casos."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Célula para a qual este servidor serve arquivos :"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Servidor de arquivos AFS pertencem a uma célula. Eles possuem uma chave para "
"cada serviço Kerberos da célula e servem volumes dentro da célula. "
"Normalmente, essa célula é a mesma célula da qual a estação de trabalho faz "
"parte."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Servidor de Arquivos OpenAFS provavelmente não funciona !"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Você está executando o pacote do servidor de arquivos OpenAFS em uma máquina "
"Alpha. Isso provavelmente não funcionará. O código DES é em conjunto com o "
"servidor de arquivos com suporte a threads é problemático em máquinas Alpha. "
"Provavelmente, o servidor de arquivos irá simplesmente falhar ao iniciar. "
"Caso consiga ser iniciado, poderá causar corrupção de dados. Você foi "
"avisado."
#~ msgid "How large is your AFS cache (kB)?"
#~ msgstr "Qual o tamanho de seu cache AFS (KB) ?"
#~ msgid "50000"
#~ msgstr "50000"

253
src/packaging/Debian/po/ru.po
View File

@ -1,253 +0,0 @@
# translation of ru.po to Russian
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Yuri Kozlov <yuray@komyakino.ru>, 2009.
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.10+dfsg1-2\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-06-16 20:50+0400\n"
"Last-Translator: Yuri Kozlov <yuray@komyakino.ru>\n"
"Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Имена машин-серверов БД ячейки:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS использует файл /etc/openafs/CellServDB для хранения списка серверов, "
"с которыми нужно соединяться при поиске частей ячейки. Ячейка, которой "
"принадлежит данная рабочая станция, указывается не в этом файле. Введите "
"имена хостов серверов базы данных через пробел. ВАЖНО: если вы создаёте "
"новую ячейку и эта машина является базой данных этой ячейки, то введите "
"здесь только имя данной машины; добавляйте другие серверы по мере ввода "
"их в работу. "
"Также, выключите запуск клиента AFS при загрузке машины пока не будет "
"настроена ячейка. Когда будете готовы, можете включить клиент, "
"отредактировав файл /etc/openafs/afs.conf.client."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Ячейка AFS, которой принадлежит данная рабочая станция:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Всё файловое пространство AFS сгруппировано в ячейки или административные "
"домены. Каждая рабочая станция принадлежит определённой ячейке. Обычно, "
"ячейка характеризуется доменным именем DNS данной машины."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Размер кэша AFS в килобайтах:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS использует часть диска для кэширования удалённых файлов для ускорения "
"доступа. Этот кэш будет смонтирован в каталог /var/cache/openafs. "
"Очень важно, чтобы кэш не переполнил раздел на котором расположен. "
"Часто пользователи создают отдельный раздел для кэша AFS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Запустить клиента Openafs сейчас и при включении компьютера?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Обычно, большинство пользователей, устанавливающих пакет "
"openafs-client, ожидают, что AFS будет монтироваться автоматически "
"при включении компьютера. Однако, если вы планируете настройку "
"новой ячейки или работаете на ноутбуке, то можете не захотеть этого. "
"Если вы укажите не запускать AFS при включении, то по желанию "
"его можно запустить командой /etc/init.d/openafs-client force-start."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Искать ячейки AFS в DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Чтобы подключиться к ячейке AFS вам нужны IP-адреса серверов базы данных "
"ячейки. Обычно, эта информация берётся из файла /etc/openafs/CellServDB. "
"Однако, если Openafs не может найти ячейку в этом файле, то она может "
"поискать записи AFSDB в DNS, в которых тоже содержится данная информация."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "Шифровать обмен с файловым сервером AFS во время аутентификации?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS предоставляет нестойкое подобие шифрования, которое можно включить "
"для обмена данными между клиентом и файловыми серверами. Хотя это шифрование "
"слабее чем DES и недостаточно для очень конфиденциальных данных, оно всё же "
"обеспечивает некоторую защиту, которая значительно осложнит работу "
"неискушённому атакующему."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Генерировать содержимое /afs динамически?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"В /afs, в основном, содержатся элементы для каждой ячейки, с которыми работает клиент. "
"Обычно, эти элементы генерируются серверами клиентской домашней ячейки. Однако, "
"клиенты OpenAFS могут генерировать содержимое /afs динамически на основе содержимого "
"/etc/openafs/CellServDB и DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Если вы разрешите генерировать /afs динамически, то вам может потребоваться "
"создать /etc/openafs/CellAlias с псевдонимами часто используемых ячеек. (В файле "
"указываются псевдонимы по одному на строку в формате: имя ячейки, пробел, "
"псевдоним ячейки.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"Использовать fakestat, чтобы избежать зависаний при просмотре списка "
"содержимого /afs?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Так как AFS представляет собой глобальное файловое пространство, операции "
"с каталогом /afs могут создавать значительный сетевой трафик. "
"Если некоторые ячейки AFS недоступны, то просмотр /afs с помощью "
"команды ls или графического файлового обозревателя может приостановить "
"работу машины на несколько минут. В AFS есть возможность симулировать "
"ответы для таких операций, чтобы предотвратить зависания. В большинстве "
"случаев лучше воспользоваться данной возможностью."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Ячейка, для которой работает сервер:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Файловые серверы AFS принадлежат ячейке. У них есть ключ для службы Kerberos "
"их ячейки, и они обслуживают тома этой ячейки. Обычно, эта ячейка совпадает "
"с ячейкой, которой принадлежит клиент рабочей станции."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Вероятно, файловый сервер OpenAFS не работает!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Вы работаете с пакетом файлового сервера OpenAFS на архитектуре alpha. "
"Скорее всего, он не работает; код DES часто отказывает на alpha, тоже "
"случается и с потоковым файловым сервером. Вероятно, файловый сервер "
"просто не запустится, но если это даже произойдёт, то в результате "
"это может повредить данные. Это было предупреждение."

246
src/packaging/Debian/po/sv.po
View File

@ -1,246 +0,0 @@
# Swedish OpenAFS debconf
# Copyright (C) 2008 Martin Bagge and the OpenAFS task force.
# This file is distributed under the same license as the OpenAFS package.
# Martin Bagge <brother@bsnet.se>, 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:24-0800\n"
"Last-Translator: Martin Bagge <brother@bsnet.se>\n"
"Language-Team: Swedish <debian-l10n-swedish@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: Swedish\n"
"X-Poedit-Country: Sweden\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Värdnamn för DB-server för din hemmacell:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS använder filer /etc/openafs/CellServDB för att hålla reda på listan av "
"servrar som ska kontaktas för att hitta delar till en cell. Cellen du påstår "
"att den här arbetsstationen tillhör finns inte i den filen. Ange värdnamnet "
"på databasservrar, skilj med mellanslag. VIKTIGT: Om du håller på att skapa "
"en ny cell och denna maskinen ska agera databas för den cellen anger du bara "
"namnet på denna maskinen här. Lägg till de övriga servrarna när de är redo. "
"Du ska heller inte ange att AFS-klienten ska starta vid systemets uppstart "
"förrens cellen är helt konfigurerad. Redigera /etc/openafs/afs.conf.client "
"för att aktivera klienten."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "AFS-cell som denna arbetsstation tillhör:"
# altså. det här med "the domain namne of the site" är helt menlöst att översätta.... /brother 31/7-08
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Filsystemet i AFS är organiserat i celler eller administrativa domäner. "
"Varje arbetsstation tillhör en cell, cellnamnet är vanligen samma som "
"domännamnet."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Storlek på AFS-cache i kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS använder en del av disken för att mellanlagrar fjärrfiler för snabbare "
"tillgång. Denna mellanlagring kommer att monteras som /var/cache/openafs. "
"Det är viktigt att mellanlagringen inte tar större plats än partitionen som "
"den huserar på. Det är vanligt att ha en dedikerad partition för AFS "
"mellanlagring."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Starta Openafsklienten nu och vid varje upstart?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Vanligen monteras AFS automatiskt vid uppstart men om du håller på att sätta "
"upp en ny cell eller arbetar med en bärbar dator kan det vara en idé att "
"inte starta klienten automatiskt. Om du inte väljer att starta AFS vid "
"uppstart ska du köra /etc/init.d/openafs-client force-start för att starta "
"klienten när du vill ha tillgång till den."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Slå upp AFS-celler i DNS?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"För att kontakta en AFS-cell så behöver du IP-adresser till cellens "
"databasservrar. Vanligen kan dessa läsas från /etc/openafs/CellServDB men om "
"cellen inte finns där kan DNS användas för att slå upp AFSDB-poster med "
"korrekt information."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "Kryptera autentiseringstrafiken till AFS-filservern?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS tillhandahåller en svag typ av kryptering som kan användas mellan "
"klienten och filservrarna. Även om denna kryptering är svagare än DES och "
"därmed inte särskilt lämplig för känslig information så kan den förhindra "
"enklare attacker och försvåra vissa steg för en utomstående."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Skapa innehåll i /afs dynamiskt?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs innehåller generellt sett en post för varje cell som klienten kan prata "
"med. Dessa poster skapades tidigare av servrar i klientens hemmacell. Numera "
"kan OpenAFS-klienter skapa innehållet i /afs dynamiskt med stöd av "
"innehållet i /etc/openafs/CellServDB eller DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Om /afs skapas dynamiskt så kan du behöva skapa /etc/openafs/CellAlias för "
"de vanligare cellerna. (Direktivet skrivs med ett alias per rad. Cellnamnet, "
"ett mellanslag och alias för den cellen)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "Ska fakestat användas för att undvika problem när /afs listas?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Då AFS är ett globalt filutrymme kan operationer på /afs skapa ganska mycket "
"nätverkstrafik. Om några AFS-celler är onåbara så kan ls och grafiska "
"filhanterare låsa maskinen i flera minuter om en eller flera celler är "
"onåbara. AFS kan ställas in att simulera svar från de onåbara cellerna för "
"att undvika låsningar. Det är mycket sällsynt att inte aktivera detta "
"alternativ."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Namn på cellen som denna server tillhandahåller filer för:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"AFS-filservrar tillhör en cell. De har en nyckel till cellens Kerberostjänst "
"och tillhandahåller volymer i den cellen. Vanligen är denna cell samma cell "
"som arbetsstationens klient tillhör."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Filservern OpenAFS fungerar troligen inte!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Du kör OpenAFS filservern på en Alpha. Det kommer förmodligen inte att "
"fungera då DES-koden i kombination med den trådade filservern är instabil. "
"Förmodligen kommer filservern helt enkelt att vägra starta, om den laddar så "
"kan data skadas. Nu har du fått varningen, det är ditt beslut."

194
src/packaging/Debian/po/templates.pot
View File

@ -1,194 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr ""
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr ""
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr ""
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr ""
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr ""
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""

253
src/packaging/Debian/po/vi.po
View File

@ -1,253 +0,0 @@
# Vietnamese translation for ApenAFS.
# Copyright © 2006 Free Software Foundation, Inc.
# Clytie Siddall <clytie@riverland.net.au>, 2005-2006.
#
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.1-3\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:25-0800\n"
"Last-Translator: Clytie Siddall <clytie@riverland.net.au>\n"
"Language-Team: Vietnamese <gnomevi-list@lists.sourceforge.net>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0\n"
"X-Generator: LocFactoryEditor 1.6a7\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "Các tên máy chạy trình phục vụ cơ sở dữ liệu cho ô chính của bạn:"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS dùng tập tin « /etc/openafs/CellServDB » để chứa danh sách các máy phục "
"vụ nên được liên hệ để tìm phần ô. Bạn đã tuyên bố máy trạm này thuộc một ô "
"không phải trong tập tin ấy. Hãy nhập tên máy của những máy phục vụ cơ sở dữ "
"liệu, định giới bằng dấu cách. QUAN TRỌNG: nếu bạn đang tạo một ô mới, và "
"máy này sẽ là một máy phục vụ cơ sở dữ liệu trong ô ấy, thì bạn hãy nhập chỉ "
"tên máy này thôi. Hãy thêm những máy phục vụ khác lần sau, sau khi chúng "
"hoạt động. Hơn nữa, có thể hiệu lực trình khách AFS khởi chạy khi khởi động "
"máy, chỉ sau khi cấu hình ô ấy. Khi bạn sẵn sàng thì có thể hiệu chỉnh tập "
"tin « /etc/openafs/afs.conf.client » để hiệu lực trình khách ấy."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Ô AFS chứa máy trăm này:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"Khoảng cách tập tin loại AFS được tổ chức ra nhiều ô hay miền quản lý. Mỗi "
"máy trạm thuộc một ô riêng lẻ. Thường ô ấy là tên miền DNS của nơi Mạng ấy."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Kích cỡ của bộ nhớ tạm AFS theo kB:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS dùng một vùng trên đĩa để lưu tạm tập tin từ xa, mà cho phép truy cập "
"nhanh hơn. Bộ nhớ tạm này sẽ được gắn vào « /var/cache/openafs ». Quan trọng "
"là bộ nhớ tạm ấy không vượt quá phân vùng ở. Thường có ích khi dùng một phân "
"vùng chỉ cho bộ nhớ tạm AFS thôi."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Chạy trình khách Openafs ngay bây giờ và cũng khi khởi động máy không?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"Bình thường, phần lớn người dùng cài đặt gói ứng dụng khách « openafs-client "
"» ngờ AFS được gắn kết tự động khi khởi động. Tuy nhiên, nếu bạn định thiết "
"lập một ô mới, hoặc sử dụng máy tính xách tay, bạn có thể không muốn nó được "
"khởi chạy vào lúc khởi động. Nếu bạn chọn không khởi chạy AFS vào lúc khởi "
"động, hãy chạy lệnh ép buộc khởi chạy « /etc/init.d/openafs-client force-"
"start » để khởi chạy ứng dụng khách khi bạn muốn khởi chạy nó."
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "Tra cứu ô AFS trong DNS không?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"Để liên hệ một ô AFS, bạn cần có địa chỉ IP của mọi máy phục vụ cơ sở dữ "
"liệu của nó. Bình thường, thông tin này được đọc từ tập tin « /etc/openafs/"
"CellServDB ». Tuy nhiên, nếu trình Openafs không tìm thấy một ô nào đó trong "
"tập tin ấy thì nó có thể dùng DNS (hệ thống tên miền) để tìm mục ghi AFSDB "
"chứa thông tin ấy."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr ""
"Mật mã hóa các dữ liệu xác thực truyền với trình phục vụ tập tin AFS không?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS cung cấp một cách mật mã yếu mà tùy chọn có thể được dùng giữa một trình "
"khách nào đó và những trình phục vụ tập tin khác. Dù cách mặt mã này yếu hơn "
"DES, vì vậy không đủ cho dữ liệu quan trọng, nó có cung cấp một mức độ riêng "
"tư, thì sẽ làm cho người tấn công gặp khó khăn một phần."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "Tạo ra nội dung « /afs » một cách động không?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"Thư mục « /afs » thường chứa một mục ghi cho mỗi ô mà trình khách có thể liên "
"hệ. Trước này, trình phục vụ trong ô chính của trình khác đã tạo ra mục ghi "
"này. Tuy nhiên, trình khách loại OpenAFS có thể tạo ra nội dung « /afs » một "
"cách động, đựa vào nội dung « /etc/openafs/CellServDB » và vào DNS."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"Nếu bạn chọn tạo ra « /afs » một cách động, có lẽ bạn sẽ cần phải tạo « etc/"
"openafs/CellAlias » (bí danh ô) để gồm bí danh cho các ô chung. (Cú pháp của "
"tập tin này là một dòng cho mỗi bí danh, mà chứa tên ô, rồi một dấu cách, "
"rồi bí danh cho ô đó.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr ""
"Dùng « fakestat » (thống kê giả) để tránh hệ thống treo cứng khi liệt kê « /"
"afs » không?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"Vì AFS là một khoảng cách toàn cục, thao tác trên thư mục « /afs » có thể tạo "
"ra nhiều tải cho mạng. Nếu một số ô AFS không sẵn sàng thì việc xem « /afs » "
"dùng lệnh « ls » (liệt kê) hoặc dùng một trình đồ họa duyệt tập tin thì có "
"thể treo cứng máy bạn trong vòng nhiều phút. AFS tùy chọn có thể mô phỏng "
"trả lời cho thao tác loại này một cách địa phương, để tránh treo cứng hệ "
"thống như thế. Đệ nghi bạn sử dụng tùy chọn này: nó cần thiết trong phần lớn "
"trường hợp."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "Ô cho đó trình phục vụ tập tin:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"Mọi trình phục vụ tập tin AFS thuộc một ô nào đó. Trình ấy có khóa của dịch "
"vụ Kerberos của ô này, và phục vụ khối đĩa vào ô này. Bình thường, ô này là "
"cùng một ô với ô sở hữu trình khách của máy trạm này."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "Rất có thể là trình phục vụ tập tin OpenAFS không hoạt động."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"Bạn có chạy gói tin trình phục vụ tập tin OpenAFS trên một anfa. Rất có thể "
"là nó không hoạt động vì mã DES bị lỗi trên anfa, cũng với trình phục vụ tập "
"tin theo mạch. Rất có thể là trình phục vụ tập tin sẽ không khởi chạy, nhưng "
"mà nếu nó có phải khởi chạy thì dữ liệu có thể bị hỏng. Bạn đã nhận một cảnh "
"báo rồi."
#~ msgid "How large is your AFS cache (kB)?"
#~ msgstr "Bạn có bộ nhớ tạm AFS lớn bao nhiêu (theo kB)?"

229
src/packaging/Debian/po/zh_CN.po
View File

@ -1,229 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.4.2-4\n"
"Report-Msgid-Bugs-To: openafs@packages.debian.org\n"
"POT-Creation-Date: 2009-02-13 09:22-0800\n"
"PO-Revision-Date: 2009-02-13 09:25-0800\n"
"Last-Translator: Chun Tian (binghe) <binghe.lisp@gmail.com>\n"
"Language-Team: Internationalization <debian-i18n@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr "您起始单元的数据库服务器主机名："
#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell. The cell you claim this "
"workstation belongs to is not in that file. Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured. When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS 使用 /etc/openafs/CellServDB 文件来存放那些在寻找一个单元 (cell) 各部分服"
"务器用来联系的服务器列表. 当前工作站您声称其所在的单元并不在这个文件里. 请以"
"空格分隔输入该单元数据库服务器的主机名. 重要提示: 如果您正在创建一个新单元并"
"且该机将做为此单元的数据库服务器, 那么只输入这台机器的主机名即可; 其他服务器"
"当他们可用时再加入进来. 并且, 直到该单元配置完成之前不要令 AFS 客户端在这台服"
"务器引导时启动. 当您一切就绪以后可以编辑 /etc/openafs/afs.conf 来打开客户端."
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "这台工作站所属的 AFS 单元:"
#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell. Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"AFS 文件空间按单元和管理域来组织. 每一台工作站属于一个单元. 单元名是通常是该"
"站点的 DNS 域名."
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "以 kB 计的 AFS 缓存大小:"
#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access. This "
"cache will be mounted on /var/cache/openafs. It is important that the cache "
"not overfill the partition it is located on. Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS 使用磁盘的一块区域来缓存远程文件来加速访问. 缓存将被挂载到 /var/cache/"
"openafs. 很重要的一点是不能让该缓存把它所在的分区填满. 通常, 人们发现用独立的"
"分区做 AFS 缓存很有用."
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "现在就启动 OpenAFS 客户端并且开机启动吗?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid ""
"Normally, most users who install the openafs-client package expect AFS to be "
"mounted automatically at boot. However, if you are planning on setting up a "
"new cell or are on a laptop, you may not want it started at boot time. If "
"you choose not to start AFS at boot, run /etc/init.d/openafs-client force-"
"start to start the client when you wish to run it."
msgstr ""
"通常, 多数安装了 openafs-client 包的用户期望 AFS 在开机后自动挂载. 尽管如此, "
"如果您正在计划设置一个新单元或者在笔记本电脑上, 您可能不希望它开机自动启动. "
"如果您选择了开机不启动 AFS, 可以在您需要它启动的时候运行 /etc/init.d/openafs-"
"client force-start"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid "Look up AFS cells in DNS?"
msgstr "要通过 DNS 查询 AFS 单元吗?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:5001
msgid ""
"In order to contact an AFS cell, you need the IP addresses of the cell's "
"database servers. Normally, this information is read from /etc/openafs/"
"CellServDB. However, if Openafs cannot find a cell in that file, it can use "
"DNS to look for AFSDB records that contain the information."
msgstr ""
"为了联系一个 AFS 单元, 您需要该单元的数据库服务器 IP 地址. 正常情况下, 这一信"
"息从 /etc/openafs/CellServDB 读取. 尽管如此, 如果 OpenAFS 无法在这个文件里找"
"到一个单元, 它可以用 DNS 查询包含这一信息的 AFSDB 记录."
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid "Encrypt authenticated traffic with AFS fileserver?"
msgstr "要加密和 AFS 文件服务器之间的认证通信吗?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:6001
msgid ""
"AFS provides a weak form of encryption that can optionally be used between a "
"client and the fileservers. While this encryption is weaker than DES and "
"thus is not sufficient for highly confidential data, it does provide some "
"confidentiality and is likely to make the job of a casual attacker "
"significantly more difficult."
msgstr ""
"AFS 提供一种可选的弱加密形式用在客户端和文件服务器之间. 虽然这种加密比 DES 还"
"弱一些, 从而不能适用于那些高度机密数据, 但它确实提供了一定的保密性, 可以令那"
"些偶然的攻击明显地变得困难."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid "Dynamically generate the contents of /afs?"
msgstr "动态生成 /afs 的内容吗?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"/afs generally contains an entry for each cell that a client can talk to. "
"Traditionally, these entries were generated by servers in the client's home "
"cell. However, OpenAFS clients can generate the contents of /afs "
"dynamically based on the contents of /etc/openafs/CellServDB and DNS."
msgstr ""
"/afs 里通常含有客户端能访问到的每一个单元的入口. 这些入口传统上是由客户端所在"
"单元的服务器生成. 尽管如此, OpenAFS 客户端也可以根据 /etc/openafs/"
"CellServDB 和 DNS 的内容来动态生成 /afs 的内容."
#. Type: boolean
#. Description
#: ../openafs-client.templates:7001
msgid ""
"If you generate /afs dynamically, you may need to create /etc/openafs/"
"CellAlias to include aliases for common cells. (The syntax of this file is "
"one line per alias, with the cell name, a space, and then the alias for that "
"cell.)"
msgstr ""
"如果您动态生成 /afs, 您可能需要创建 /etc/openafs/CellAlias 来包含通用单元的别"
"名. (这个文件的语法是每个别名一行, 由单元名, 一个空格, 和该单元的别名组成.)"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid "Use fakestat to avoid hangs when listing /afs?"
msgstr "使用 fskestat 来避免对 /afs 列目录时挂起吗?"
#. Type: boolean
#. Description
#: ../openafs-client.templates:8001
msgid ""
"Because AFS is a global file space, operations on the /afs directory can "
"generate significant network traffic. If some AFS cells are unavailable "
"then looking at /afs using ls or a graphical file browser may hang your "
"machine for minutes. AFS has an option to simulate answers to these "
"operations locally to avoid these hangs. You want this option under most "
"circumstances."
msgstr ""
"因为 AFS 是一个公共文件空间, 所以对 /afs 目录的操作能产生明显的网络流量. 如"
"果某些 AFS 单元无法访问, 那么当使用 ls 或者图形界面文件浏览器列 /afs 目录时可"
"能会令您的主机挂起几分钟. AFS 有一个选项可以将这些操作模拟成本机操作从而避免"
"这类挂起. 大多数情况下您都需要这一选项."
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid "Cell this server serves files for:"
msgstr "这台文件服务器所在的单元:"
#. Type: string
#. Description
#: ../openafs-fileserver.templates:1001
msgid ""
"AFS fileservers belong to a cell. They have the key for that cell's "
"Kerberos service and serve volumes into that cell. Normally, this cell is "
"the same cell as the workstation's client belongs to."
msgstr ""
"AFS 文件服务器属于一个单元. 它们有该单元的 Kerberos 服务密钥并且为该单元提供"
"卷服务. 正常情况下, 这个单元跟工作站上的客户端属于的那个单元是同一个."
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid "OpenAFS file server probably does not work!"
msgstr "OpenAFS 文件服务器可能不会工作!"
#. Type: note
#. Description
#: ../openafs-fileserver.templates:2001
msgid ""
"You are running the OpenAFS file server package on an alpha. This probably "
"doesn't work; the DES code is flaky on the alpha, along with the threaded "
"file server. Likely, the fileserver will simply fail to start, but if it "
"does load, data corruption may result. You have been warned."
msgstr ""
"您正在一台 alpha 机上运行 OpenAFS 文件服务器包. 这可能不会工作; alpha 下的随"
"线程文件服务器带的 DES 代码很奇怪. 文件服务器很可能简单地直接启动失败, 但如果"
"它确实起来了, 数据错乱也有可能发生. 您将被警告这点."

244
src/packaging/Debian/rules
View File

@ -1,244 +0,0 @@
#!/usr/bin/make -f
# Tell Autoconf the correct system types.
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
SYSTEM = --build $(DEB_HOST_GNU_TYPE)
else
SYSTEM = --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)
endif
# Determine whether we're building with optimization. This doesn't really
# work at the moment due to upstream problems.
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
DEBIAN_OPT_FLAGS = --disable-optimize --disable-optimize-lwp
DEBIAN_KERN_FLAGS = --disable-optimize-kernel
else
DEBIAN_OPT_FLAGS =
DEBIAN_KERN_FLAGS =
endif
SYS_NAME := $(shell sh debian/sysname)
package = openafs
srcpkg = openafs-modules-source
dkmspkg = openafs-modules-dkms
DOCS = $(CURDIR)/debian/openafs-doc/usr/share/doc/openafs-doc
# The path to the XSLT used to generate HTML from the DocBook source files.
# This path is specific to different Linux distributions, so we have to pass
# it into configure.
HTML_XSL = /usr/share/xml/docbook/stylesheet/nwalsh/html/chunk.xsl
# The /usr/share/doc directory for these packages should be a symlink to
# /usr/share/doc/openafs-client. Any package on this list must depend on
# openafs-client. This variable is used as options to dh_installdocs with
# the --link-doc option.
DOC_PACKAGES = -plibpam-openafs-kaserver -popenafs-dbserver -popenafs-fuse \
-popenafs-kpasswd
# These are files that we know we don't want to install. List them so that we
# can use dh_install --fail-missing and catch anything new that shows up.
IGNORE = -XAuthLog -Xcompile_et -Xcopyauth -Xdlog -Xdpass -Xfms.log \
-Xfs_chgrp.1 -Xfs_chown.1 -Xfs_cscpolicy.1 -Xfs_flushall.1 \
-Xfs_memdump.1 -Xfs_minidump.1 -Xfs_trace.1 -Xkadb_check -Xkaserver \
-Xkdb -Xkdump -Xkpwvalid -Xpagsh.krb -Xsymlink -Xtokens.krb -Xuss \
-Xvldb_convert -Xvsys -Xxfs_size_check
# Installed via other means since we have to rename them.
IGNORE += -Xafsd.fuse.8 -Xpam_afs
# These variables are used by get-orig-source, to construct dkms.conf, and
# to set the build version. You will need to change TAG to package stable
# releases instead of experimental releases.
DEBIAN := $(shell dpkg-parsechangelog | grep ^Version: | cut -d' ' -f2)
DEBVERS := $(shell echo '$(DEBIAN)' | cut -d- -f1)
VERSION := $(shell echo '$(DEBVERS)' | sed -e 's/[+-].*//' -e 's/~//g')
TAG := $(shell echo 'openafs-devel-$(VERSION)' | sed 's/\./_/g')
REPO := git://git.openafs.org/openafs.git
# Upstream does tarball releases for major releases, but not for point
# relesaes, and the tarball releases are split into src and doc and contain
# the WINNT directory. Dropping WINNT, which is not used on Debian, saves a
# substantial amount of space in the source package, and there's no reason
# to include the files generated by regen.sh when we're going to run it
# again ourselves anyway.
#
# This rule therefore generates an upstream tarball from the upstream Git
# tag, rather than the tarball release, without the generated files that are
# not in Git and without the WINNT directory. It assumes that git-core is
# installed and there's network connectivity to the upstream repository.
get-orig-source:
git archive --remote='$(REPO)' --prefix='openafs_$(DEBVERS).orig/' \
--format=tar '$(TAG)' | tar xf -
rm -r openafs_$(DEBVERS).orig/src/WINNT
tar cf openafs_$(DEBVERS).orig.tar openafs_$(DEBVERS).orig
rm -r openafs_$(DEBVERS).orig
gzip -9 openafs_$(DEBVERS).orig.tar
# Use dh for most actions, with overrides below.
%:
dh $@
# Handle the renaming of the up man page to afs-up here since the man pages
# are generated from POD source by regen.sh.
override_dh_auto_configure:
@if test x"$(SYS_NAME)" = x"UNKNOWN" ; then exit 1 ; fi
echo '$(DEBIAN)'-debian > .version
mv doc/man-pages/pod1/up.pod doc/man-pages/pod1/afs-up.pod
rm -f doc/man-pages/man1/up.1
sh regen.sh
afslogsdir=/var/log/openafs afslocaldir=/var/lib/openafs/local \
sh configure \
--with-afs-sysname=$(SYS_NAME) --disable-kernel-module \
--prefix=/usr --mandir=\$${prefix}/share/man \
--sysconfdir=/etc --libexecdir=/usr/lib --with-krb5 \
--localstatedir=/var/lib --enable-supergroups \
--enable-fuse-client --enable-debug --enable-debug-lwp \
--with-xslt-processor=xsltproc --with-html-xsl=$(HTML_XSL) \
--enable-reduced-depends $(DEBIAN_OPT_FLAGS) $(SYSTEM)
# Also build a libafs_tree and build the XML documentation.
override_dh_auto_build:
dh_auto_build
$(MAKE) libafs_tree
set -e; for d in AdminGuide QuickStartUnix UserGuide ; do \
$(MAKE) -C doc/xml/$$d all ; \
done
# The manipulation of debian/changelog here is unnecessary with a regular
# Debian build. It is provided solely so that upstream can share the Debian
# packaging files, working around problems caused by upstream's distclean
# removing packaging/Debian/changelog because it's Autoconf-generated.
override_dh_auto_clean:
[ ! -f doc/man-pages/pod1/afs-up.pod ] \
|| mv doc/man-pages/pod1/afs-up.pod doc/man-pages/pod1/up.pod
set -e; for d in AdminGuide QuickStartUnix UserGuide ; do \
[ ! -f doc/xml/$$d/Makefile ] || $(MAKE) -C doc/xml/$$d clean ; \
done
[ ! -f debian/changelog.in ] \
|| cp debian/changelog debian/changelog.save
dh_auto_clean
[ -f debian/changelog ] || mv debian/changelog.save debian/changelog
# We have to use a non-standard install target and then do some fiddling
# with the results.
override_dh_auto_install:
mkdir -p $(CURDIR)/debian/tmp
$(MAKE) install_nolibafs DESTDIR=$(CURDIR)/debian/tmp
rm -f debian/tmp/usr/bin/klog.krb
rm -f debian/tmp/usr/share/man/man1/klog.krb.1
# Override dh_install to handle installation of all the extra documentation
# that upstream doesn't install by default, install the source required for
# the kernel source package and the DKMS package, move some files about and
# do some manually installation of additional things like PAM modules, and
# to ensure that the extra scripts we install are executable.
override_dh_install:
chmod +x debian/afs-rootvol debian/afs-newcell
dh_install --fail-missing $(IGNORE)
mkdir -p $(DOCS)/html
cp doc/xml/*.gif doc/xml/*.html $(DOCS)/html/
set -e; for d in AdminGuide QuickStartUnix UserGuide ; do \
mkdir $(DOCS)/html/$$d ; \
cp doc/xml/$$d/*.html $(DOCS)/html/$$d/ ; \
cp doc/xml/$$d/*.pdf $(DOCS)/ ; \
done
cp doc/xml/AdminGuide/*.png $(DOCS)/html/AdminGuide/
mkdir $(DOCS)/html/arch-overview
cp doc/arch/arch-overview.h $(DOCS)/html/arch-overview
cd $(DOCS)/html/arch-overview && doxygen *.h && rm *.h && mv html/* . \
&& rm -r latex html
set -e; for h in doc/protocol/*.h ; do \
mkdir $(DOCS)/html/`basename $$h .h` ; \
cp $$h $(DOCS)/html/`basename $$h .h` ; \
cd $(DOCS)/html/`basename $$h .h` && doxygen *.h && rm *.h \
&& mv html/* . && rm -r latex html && cd $(CURDIR) ; \
done
install -d debian/$(srcpkg)/usr/src/modules/$(package)
cd libafs_tree && find . -print | \
cpio -admp $(CURDIR)/debian/$(srcpkg)/usr/src/modules/$(package)
cp .version debian/$(srcpkg)/usr/src/modules/$(package)/
mkdir -p debian/$(srcpkg)/usr/src/modules/$(package)/debian
cp debian/copyright debian/module/* \
debian/$(srcpkg)/usr/src/modules/$(package)/debian/
sed 's/^openafs /openafs-modules /' debian/changelog \
> debian/$(srcpkg)/usr/src/modules/$(package)/debian/changelog
chmod 755 debian/$(srcpkg)/usr/src/modules/$(package)/debian/rules
chown -R root.src debian/$(srcpkg)
find debian/$(srcpkg) -type d | xargs chmod 755
find debian/$(srcpkg) -type f -perm -100 | xargs chmod 755
find debian/$(srcpkg) -type f -not -perm -100 | xargs chmod 644
chmod 775 debian/$(srcpkg)/usr/src/modules
cd debian/$(srcpkg)/usr/src && tar cf $(package).tar modules
bzip2 debian/$(srcpkg)/usr/src/$(package).tar
chmod 644 debian/$(srcpkg)/usr/src/$(package).tar.bz2
install -d debian/$(dkmspkg)/usr/src
mv debian/$(srcpkg)/usr/src/modules/$(package) \
debian/$(dkmspkg)/usr/src/openafs-$(VERSION)
rm -rf debian/$(dkmspkg)/usr/src/openafs-$(VERSION)/debian
rmdir debian/$(srcpkg)/usr/src/modules
dh_dkms -V $(VERSION)
mv debian/openafs-client/usr/bin/pagsh \
debian/openafs-client/usr/bin/pagsh.openafs
mv debian/openafs-client/usr/share/man/man1/pagsh.1 \
debian/openafs-client/usr/share/man/man1/pagsh.openafs.1
mv debian/openafs-client/usr/bin/klog \
debian/openafs-client/usr/bin/klog.afs
mv debian/openafs-client/usr/share/man/man1/klog.1 \
debian/openafs-client/usr/share/man/man1/klog.afs.1
mv debian/openafs-client/usr/bin/up \
debian/openafs-client/usr/bin/afs-up
install -m 644 -c debian/tmp/usr/lib/pam_afs.so.1 \
debian/libpam-openafs-kaserver/lib/security/pam_afs.so
install -m 644 -c debian/tmp/usr/lib/pam_afs.krb.so.1 \
debian/libpam-openafs-kaserver/lib/security/pam_afs.krb.so
install -d debian/openafs-dbserver/usr/share/man/man8
( cd debian && pod2man --section 8 --center "Debian GNU/Linux" \
afs-rootvol ) \
>debian/openafs-dbserver/usr/share/man/man8/afs-rootvol.8
( cd debian && pod2man --section 8 --center "Debian GNU/Linux" \
afs-newcell ) \
>debian/openafs-dbserver/usr/share/man/man8/afs-newcell.8
install -d debian/$(srcpkg)/usr/share/doc/$(srcpkg)
install -m 644 debian/openafs-client.NEWS \
debian/$(srcpkg)/usr/share/doc/$(srcpkg)/NEWS.Debian
# We have multiple init scripts with some non-standard defaults.
override_dh_installinit:
dh_installinit -popenafs-client -r -- defaults 25 20
dh_installinit -popenafs-fileserver -r
# Create the documentation symlinks.
override_dh_installdocs:
dh_installdocs $(DOC_PACKAGES) --link-doc=openafs-client
dh_installdocs --remaining-packages
# Install the upstream NEWS file as the upstream changelog.
override_dh_installchangelogs:
dh_installchangelogs NEWS
# Override some of our permissions.
override_dh_fixperms:
dh_fixperms
chmod 700 debian/openafs-client/var/cache/openafs
chmod 700 debian/openafs-dbserver/var/lib/openafs/db
chmod 700 debian/openafs-fileserver/var/lib/openafs/local
# Only include debugging information for the servers installed into
# /usr/lib/openafs rather than for all binaries. The servers are where
# debugging backtraces really matter, and a 10MB debugging package is
# overkill.
override_dh_strip:
dh_strip --dbg-package=openafs-dbg
rm -rf debian/openafs-dbg/usr/lib/debug/lib
rm -rf debian/openafs-dbg/usr/lib/debug/sbin
rm -rf debian/openafs-dbg/usr/lib/debug/usr/bin
rm -rf debian/openafs-dbg/usr/lib/debug/usr/sbin

1
src/packaging/Debian/source/format
View File

@ -1 +0,0 @@
1.0

43
src/packaging/Debian/sysname
View File

@ -1,43 +0,0 @@
#!/bin/sh
# Maps Debian architectures to AFS sysnames for building the clients and
# libraries. This doesn't worry about the kernel version; kern-sysname
# does that when building the kernel module.
#
# Not all architectures are listed, only those that OpenAFS supports.
case `dpkg --print-architecture` in
alpha)
echo alpha_linux_26
;;
arm|armel|armv5tel)
echo arm_linux26
;;
amd64)
echo amd64_linux26
;;
i[3456]86)
echo i386_linux26
;;
ia64)
echo ia64_linux26
;;
powerpc|powerpcspe)
echo ppc_linux26
;;
ppc64)
echo ppc64_linux26
;;
s390)
echo s390_linux26
;;
s390x)
echo s390x_linux26
;;
sparc|sparc64)
echo sparc_linux24
;;
*)
echo "ERROR: unsupported architecture" >&2
echo UNKNOWN
exit 1
esac

15
src/packaging/Debian/watch
View File

@ -1,15 +0,0 @@
# Note that the following watch file does not find development releases,
# only general releases and release candidates. If we package development
# releases, a rule should be added to find them as well.
version=3
# Without the /pages in the URL, one gets the frameset page.
opts=dversionmangle=s/[\.+]dfsg\d+$// \
http://www.openafs.org/pages/release/latest.html \
.*/openafs-([^-]+)-src\.tar\.gz
# Release candidates are stashed in another secret place and we change the
# version number for proper sorting of versions in Debian.
opts="uversionmangle=s/-rc/~rc/;s/pre/~pre/,dversionmangle=s/[\.+]dfsg\d+$//" \
http://dl.openafs.org/dl/openafs/candidate/ ([^/]+-?(?:rc|pre)\d+)/