Guest User

Untitled

a guest
Aug 16th, 2011
220
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.88 KB | None | 0 0
  1. #
  2. # Introduction to nic.funet.fi archive
  3. #
  4. # Status: Update in progress
  5. # Author: staff of ftp.funet.fi
  6. # Created: Sat Aug 22 20:31:58 1992
  7. # Last modified: 2011-03-08
  8. #
  9.  
  10.  
  11. Welcome to FTP.FUNET.FI aka NIC.FUNET.FI
  12.  
  13.  
  14. This is a Dell R710 server with 72GB of RAM and dual Quad-Core Nehalem
  15. EP processors (Intel Xeon E5540) giving 16 CPU threads. Storage is
  16. provided via fibre channel connections to the CSC Storage Area
  17. Network. Currently it uses 20TB on a EMC CX700 RAID subsystem for
  18. ZFS storage and it can be extended on the fly if required.
  19.  
  20. Operating system is Solaris 10 Unix from Sun Microsystems. We have a
  21. 10Gbit/s dedicated connection to Funet which connects at 10Gbit/s level
  22. to academic backbone networks like GEANT and Internet 2 through a nordic
  23. dark fibre network and of course inside Finland.
  24.  
  25. This system is owned by the finnish ministry of education
  26. and operated on their behalf by CSC primarily for the Finnish Academic
  27. and Research Network FUNET users. It is located in the town of Espoo
  28. in Finland.
  29.  
  30. Paper mail address:
  31. NIC.FUNET.FI coordinator
  32. Harri Salminen
  33. CSC
  34. POBOX 405 (street address is Keilaranta 14)
  35. FIN-02101 Espoo
  36. FINLAND
  37.  
  38. This server group has many names. Its "staff" will always be
  39. at `nic.funet.fi', but othervice consider using philosophy: `name by
  40. function', thus FTP from ftp.funet.fi.
  41.  
  42. ftp.funet.fi traditional anonymous ftp service (also with http and IPv6 support)
  43. www.nic.funet.fi http access to our collections (shows index.html's if any)
  44. nic.funet.fi email and other administrative tasks (in practice ftp
  45. is also supported)
  46.  
  47. We have also several other names and may move some services to other
  48. computers as we see necessary.
  49.  
  50. CONTENTS:
  51.  
  52. - Intro
  53. - What is considered proper conduct of anonymous FTP usage
  54. - Privacy issues
  55. - Contacts about material in here
  56. ( GIFs and others )
  57. - Uploading
  58. - CD-ROMs
  59. - FTPD sources
  60. - Reporting a bug/problems
  61. - Physical disk structure is hidden behind logical one
  62. - Restrictions
  63. - Minimum of maximum retrieval rate
  64. - IP-reversal and valid "passwd" requirements
  65. - What is `Freely distributable' ?
  66. - Other services available from here
  67. - Many names of the server
  68.  
  69. INTRO:
  70.  
  71. This system has plenty of freely distributable material on its FTPable
  72. areas. We have also other services, see at the end of this document for
  73. pointers.
  74.  
  75. If you have any questions regarding MATERIALS in this archive, read
  76. first `Contacts about material in here' below. If you can't locate correct
  77. person/mail alias with it, try `[email protected]', but do not do that
  78. as your only attempt!
  79.  
  80. WHAT IS CONSIDERED A PROPER CONDUCT OF ANONYMOUS FTP USAGE:
  81.  
  82. Like many systems world wide, ours offers anonymous logins for
  83. FTP users. Such a service means:
  84. - You do not need to apply an account at this server, just use
  85. well known userid: anonymous (or ftp) and for a password please
  86. do enter your email address (in format: your_userid@your_site)
  87. according to the convention used since the 1970s in public FTP servers.
  88.  
  89. - While this service is called "anonymous" due to that well-known
  90. userid, it is considered good manners to identify yourself
  91. properly. (No, this is not truly anonymous.)
  92. (See PRIVACY ISSUES)
  93.  
  94. For those who have this privilege of using ftp, here are some do's
  95. and don'ts:
  96.  
  97. - When you are working over long distance links, do limit yourself
  98. to off hours. When working between the USA and Finland, try it
  99. after 4 PM OUR time ( 10 AM Eastern USA time.) And remember that
  100. we wake up 10 hours before California.
  101. We are at time zone `UTC +2h' and in summer 'UTC +3h'
  102.  
  103. - Major portion material in this archive originates from various
  104. locations all over USA. Sometimes those locations are well
  105. known. Often not. We try to indicate origins if we know them.
  106. DO try to use server nearest (network wise) to yourself, USA
  107. folks: please restrain yourself to USA.
  108.  
  109. - When you log in anonymous, system immediately identifies you, and
  110. if you are not limited by number of users, you are
  111. prompted with:
  112.  
  113. 331 Any password will work
  114.  
  115. We'd still appreciate you to give your email address as password.
  116. We might someday spot problems on files and send warnings to those who
  117. have requested that(/those) file(s) (see PRIVACY ISSUES).
  118.  
  119. If your FTP program uses getpass(3) routine blindly (mostly old
  120. BSD networking source derived FTP programs), you can't enter
  121. more than 8 characters for password from the keyboard. Ever.
  122. Try to install FTP program from /pub/local/src/net2+mea-ftp.tar.Z.
  123. You can then feed in a lot longer `passwords'.
  124. (It has replacement for getpass() which inputs 130 chars.)
  125.  
  126. Alternatively, read the man-page of ftp-program (assuming you
  127. are using UNIX ftp client), and see what is said about ".netrc".
  128.  
  129. Some machines have problems with @-characters at such addresses,
  130. UNIX: stty erase ^? kill ^u
  131. IBM VM/SP CMS: CP TERM CHARDEL OFF, CP TERM LINEND OFF
  132.  
  133. - When you upload something, make sure it is freely distributable.
  134. For example some GIF images we have gotten are very obviously
  135. scanned from magazines, which have publication copyrights on them.
  136. This makes it illegal to copy those pictures `without the prior
  137. written consent of the publisher.' (And yes, WE WANT TO SEE THAT
  138. WRITTEN CONSENT FOR UPLOADING SUCH!)
  139.  
  140. - See below more about what is `Freely Distributable'.
  141. After all, it is not always the same as Public Domain!
  142.  
  143. - Don't do many parallel downloads, it will slow down the
  144. service for others and eventually even you. There's a maximum limit
  145. on simultaneous connections for FTP which is shown when you log in.
  146. For HTTP we have had to limit the maximum connections from one
  147. IP to 10.
  148.  
  149.  
  150. - REMEMBER: USING ANONYMOUS FTP IS A PRIVILEGE. DON'T ABUSE IT!
  151.  
  152.  
  153. PRIVACY ISSUES
  154.  
  155. All file accesses, logins etc. are logged, and the logs are kept
  156. for indefinite period of time pending disk space availability (months online,
  157. years offline.) to satisfy statistical and legislative requirements.
  158.  
  159. If you want to be unidentifiable, that is entirely up to you, and
  160. possible within rules of our server by using password of type:
  161.  
  162. inconnu@<your host identity>
  163.  
  164. If you want to be totally unknown, you must not use FTP, as it can
  165. never be used without revealing the IP address of your FTP client.
  166. Even if you had a firewall or proxy somewhere in between, they often
  167. keep track who's using them. In any case we don't collect email
  168. addresses for spammers and we might use them only in exceptional cases
  169. ourselves. For statistics we use the domain part of your hostname,
  170. not the hostname itself which in practice means organization and
  171. country level statistics which we need to maintain the service and
  172. it's funding. Please try to keep your reverse DNS working, especially
  173. if you are under .fi domain since we will try to give preference to
  174. finnish users in case we will someday again have to impose domain
  175. based speed restrictions on the service like in the early days of the
  176. Internet.
  177.  
  178.  
  179. CONTACTS ABOUT MATERIAL IN HERE:
  180.  
  181. Example: An alias "xyz-adm" is to be addressed as
  182. "[email protected]", please don't use HTML email or something else
  183. that might be interpreted as SPAM by our filters. Plain old english or
  184. finnish text is the best! Please note, that many of the old /pub
  185. areas are not actively maintained and most of the content is actually
  186. automatically updated from a master site which you should be able to
  187. deduce from the /pub/mirrors/some.site/ directory path.
  188.  
  189. Alias Area Description
  190. =============================================================================
  191. astro-adm pub/astro/ (amateur) Astronomy related material
  192. csc-adm pub/csc/ Centre for Scientific Computing, FI
  193. cpan-adm pub/CPAN/ Comprehensive Perl Archive Network (master)
  194. culture-adm pub/culture/ Cultural information
  195. doc-adm pub/doc/ Documents
  196. gnu-adm pub/gnu/ GNU material
  197. graphics-adm pub/graphics/ Graphics software
  198. ham-adm pub/ham/ Radio-Amateur related information
  199. pics-adm pub/pics/ JPEG encoded images
  200. languages-adm pub/languages/ Programming languages
  201. linux-adm pub/Linux/ Linux
  202. neural-adm pub/sci/neural/ Neural Networks
  203. papers-adm pub/sci/papers/ Scientific papers
  204. sci-adm pub/sci/ Scientific information in general
  205. tex-adm pub/TeX/ TeX
  206. unix-adm pub/unix/ UN*X software etc.
  207. mirror-adm pub/mirrors Mirror maintenance
  208.  
  209. Specials
  210. ========
  211.  
  212. mirror-adm Generic mirror maintenance if you don't know exactly
  213. who or which area managers are responsible for the mirror.
  214. Please check first the master site in case they have the same issue too,
  215. we just try to mirror them sometimes with some exclusions to save space.
  216.  
  217. problems FTP server software problem reporting address.
  218. You can use it also if you can't otherwise get
  219. in contact with the appropriate area managers
  220.  
  221. managers Everything archive related, which isn't proper
  222. for area maintainers or doesn't have an area manager
  223. and thus goes to the general the system managers and coordinators.
  224.  
  225.  
  226.  
  227. If you can logon (anonymously) and read this file, you probably
  228. do not have problems with your/our ftp software, therefore you should
  229. contact above mentioned area administrators.
  230.  
  231. If you don't find suitable alias to approach, try:
  232. managers at ftp.funet.fi
  233.  
  234.  
  235. UPLOADING:
  236.  
  237. See file /README.UPLOADER for detailed procedure and explanations.
  238. For short: there are directories that are world writable, BUT THIS SYSTEM
  239. DOES NOT LET UPLOADED FILES TO BE VISIBLE/RETRIEVABLE BEFORE AREA-MAINTAINERS
  240. CHECK AND APPROVE THEM.
  241.  
  242. What we expect uploader to do when uploading anything is stated in
  243. /README.UPLOADER. Read it!
  244.  
  245.  
  246. CD-ROMs
  247.  
  248. Every now and then we are asked for a CD-ROM of this archive; so far
  249. there are none available with the exception of the Euroscene 1 collection
  250. based on part of the Amiga area. We don't expect many exceptions...
  251.  
  252. Reasons for this are multiple, not the least of them being our
  253. unwillingess to do the effort of publishing such a set. Arranging the
  254. publishing on this kind of directly government funded system is not so
  255. easy in legal wise when it comes to direct money making as of selling
  256. those CD-ROMs... Also it doesn't too well fit to our main business
  257. idea of providing all the WAN network services the Academic and
  258. Research community needs. The whole archive on CD-ROM would take
  259. thousands of CD-ROMs and require lots of manpower to figure out what
  260. should or shouldn't be on each cd-rom and how to finance it. We are a
  261. network service provider, not a cd-rom store.
  262.  
  263. Some software collections are available commercially, with technical
  264. support, on CD-ROM from other sources (e.g. most Linux distributions). That
  265. may even be a major revenue source for maintaining those collections
  266. so they might not even allow cd-rom versions by others. Some other
  267. collections however are specifically available as CD-ROM images (.iso)
  268. that you can burn yourself and even distribute according to their
  269. copyright statements. So please read the fine print before
  270. redistributing collections available from us.
  271.  
  272. FTPD SOURCES:
  273.  
  274.  
  275. For a simple to maintain ftp server, you might want to
  276. look at www.pureftpd.org, we have used it successfully in several
  277. different places. Another Very Secure choice might be vsftpd
  278. available from http://vsftpd.beasts.org that is being used by many large
  279. sites.
  280.  
  281.  
  282.  
  283. REPORTING A BUG:
  284.  
  285. If you observe odd behaviour of this server, which is not of what you
  286. believe to be correct, please contact [email protected] and in the
  287. report have attached a session log which shows the wrong functionality.
  288. However, check at first what we state about "Restrictions" below!
  289.  
  290. Such log should start from your FTP session startup, and it should contain:
  291.  
  292. - Descriptions about your (computing-) environment relevant
  293. with attempted FTP access;
  294. - Maker and model of the computer where you ran your
  295. FTP session,
  296. - TCP/IP software model and maker (quite many system do
  297. not come with builtin TCP/IP -- VMS-machines are one
  298. such example.)
  299. - UNEDITED (verbose, unabridged) session transcript showing
  300. EVERYTHING you sent to this system, and what were the responses.
  301.  
  302. Note: Reports about corrupted files belong to archive area keepers; they
  303. handle those files; "problems" handles the server subsystem.
  304.  
  305.  
  306. Bugs/problems relating to ARCHIVED MATERIAL:
  307. Select by list under: `Contacts about material in here'
  308.  
  309. Uploads:
  310. Select by list under: `Contacts about material in here'.
  311. If no suitable one can be found, check also /README.UPLOADER.
  312. In outmost despair (ONLY then! [email protected])
  313.  
  314.  
  315. Bugs/problems relating to other parts of system software:
  316. Problems group: <[email protected]>
  317. ("system software" does not mean anything under /pub/")
  318.  
  319. If you can get /README without trouble, don't contact <problems>,
  320. but one of earlier mentioned area administration aliases.
  321.  
  322.  
  323. WHAT IS `FREELY DISTRIBUTABLE' ?
  324.  
  325. Freely distributable does not mean the same thing as PD
  326. (public domain). A big portion of the software available here is not
  327. in the public domain, although it is freely distributable. Many are
  328. copyrighted by some person or organization, but can be distributed
  329. freely; there may be limitations on the manner of distribution and/or
  330. the usage of the programs. There may also be certain rules concerning
  331. the distribution of modified versions (derivate work) of the programs,
  332. like saying that if you redistribute a modified version you must
  333. include in the distribution the date and author of the modification.
  334. Also on many programs you must include a note crediting the original
  335. author of the program if you use his code in your own programs.
  336.  
  337. An example of this is the Free Software Foundation's GNU
  338. software. GNU software may be distributed freely, provided that the
  339. sources are included, an offer to distribute the sources is included
  340. or that a pointer to where the sources can be gotten from is included.
  341. On FTP.FUNET.FI, all the GNU source code published is available from
  342. the directory pub/gnu. Some GNU binaries are available from other
  343. directories as well; although we have tried to include a pointer to
  344. the sources and the copyright information in these other directories,
  345. too, it might be that we have neglected some. This note is here to
  346. point you to the sources in pub/gnu. For further information, the
  347. GNU copyright is in the file pub/gnu/COPYING.
  348.  
  349.  
  350. We have multiple filesystems that are all mounted via mountpoints under
  351. the /.m/ directory. We may move mirrors and other directories from
  352. one filesystem to another without notice, so please refer to our directories
  353. with the official /pub/ or /index/ path instead of the physical /.m they
  354. map to and might be shown to you by various user agents. Especially all
  355. /.m/mirror*/ filesystems are all symlinked via the /pub/mirrors/ directory
  356. and the subdirectories try to match those on the original site.
  357.  
  358.  
  359.  
  360. A very concise history of NIC
  361. =============================
  362.  
  363. 1988 Finland gets it's first internet link of 56Kbit/s via the NORDUnet co-operation and major part of the traffic was from FTP
  364. 1989 Funet saw a need for a FTP-server that would allow better access to the internet content (web was still a dream)
  365. from Finland. Decision to set up NIC.FUNET.FI was made and Request for Proposals sent out
  366. 1990 First NIC.FUNET.FI, a SUN 4/330, with dual 40Mhz SPARC processors, 128MB RAM and 6GB of usable
  367. disk space which made it then among the largest FTP servers in the Internet.
  368. Our international internet connectivity for whole Funet was 64Kbit/s so mea develops an ftpd with speed limits
  369. More hardware details are available in historical/First-NIC-Hardware.txt
  370. 1991 Linus Torvalds offered a small OS for public distribution which our volunteer
  371. Ari Lemmke decided to call Linux and the name stuck... International connection was upgraded to 128Kbit/s
  372. 1992 We had about 20GB of external disks and a motherboard upgrade making it in practice a SUN 630-41 MP
  373. International connectivity was upgraded to 1Mbit/s
  374. 1994 Second NIC with 275Mhz Alpha processor, 320MB of memory and 100GB+ disk space (DEC AXP3000-900)
  375. International connection for Funet upgraded to 2 x 2Mbit/s
  376. 1999 Third NIC with four processors and 4GB of memory (a SUN 450) was taken in use.
  377. Under 1TB made from well over hunred old and new disks in two RAID racks (DEC and Eurologic)
  378. International connections used 155Mbit/s links with redundancy
  379. 2003 A user survey to determine whether users still need NIC is made with an encouraging response
  380. 2006 The fourth version of NIC from Fujitsu-Siemens Computers with 16GB of memory and four processors
  381. is taken into production initially with 3TB+ EMC CX300 SAN storage array. A SUN V240 is in a support role.
  382. 2.5Gbit/s and 10Gbit/s international links
  383. 2007 5-6 TB SAN storage added. Dark fibers with support for many lightpaths deployed in the Funet backbone.
  384. 2010 Fifth version of NIC, a Dell R710, with dual Quad-Core Nehalem EP (2,53Ghz Intel Xeon 5540) processors,
  385. 72GB of RAM and storage from the CSC storage area network (initially 10TB+ from a EMC CX700)
  386. taken into use under Solaris 10 and the ZFS filesystem. Network connection is now
  387. 10Gbit/s to the Funet backbone and multiples of 10Gbit/s to the rest of the Internet.
  388.  
  389.  
  390. More historical pieces of information can be found in various files around NIC and especially a more
  391. generic Internet-history in a concise web format at http://www.nic.funet.fi/index/FUNET/history/internet/
  392.  
  393. There's also a more verbose article of NIC now and then at the CSCnews 3/06 available at
  394. http://www.csc.fi/english/csc/publications/cscnews/back_issues/cscnews3_06
Advertisement
Add Comment
Please, Sign In to add comment