Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [papers] >> rjb94b.mosaic
[Index] [Contents] [Source] [Notation] [Copyright] [Comment] [Search ]
Fri Jan 20 11:53:30 PST 2006

Disclaimer. CSUSB and the CS Dept have no responsibility for the content of this page.

Copyright. Richard J. Botting ( Fri Jan 20 11:53:30 PST 2006 ). Permission is granted to quote and use this document as long as the source is acknowledged.


    Warning: Obsolete Information

    I'm keeping this for historical purposes only. The advice and code worked in the 1994.

    Mosaic = ftp + www

      We now have a special machine that provides anonymous access to are files using the Internet File Transfer Protocol(FTP) or the World-Wide-Web (WWW) protocols. These are two popular ways of making work publically available. They are both wide open doors onto the Internet - anyone can enter and read the data. There security has not been formally proven... just tested. I need to be sure that people get access to our public data only. So for the time being only the new system will run anonymous FTP and WWW. The machine is a Sun SparkClassic. The machine has a 2 gigabyte hard drive dedicated for public information. The system has been set up as a repository rather than duplicating all the facilities on the other machines. In general use it to "publish" finished works, rather than actually developing the work on the machines.

      People access the files using "anonymous FTP" - with any password. The files can be in any format and any content - papers, source code, binaries, PostScript, TeX, EMACs LISP, ... When you tell other people about FTP server use the full domain name:

    1. and the directory name
    2. /your-user-name. Please use thefollwoing "universal resource locator"(URL) syntax:


    4. The anonymous user will see a file system like this:




      We also run a world-wide-web service on the same machine. This means that the popular Mosaic program can access files on the same machine. The ftp host is therefore also known as

    5. Tell people to use the following URL in their WWW browser


      Any WWW browser - Mosaic, Lynx etc. - can use browse through the same files as FTP. So the HTML(Hyper-Text Markup Language) pages are kept in the same directories as the FTP files. Files to be accessed by Mosiac and Lynx need to be in HTML but there are help, templates, and tools available "real-soon- now" to generate HTML. These files should all have suffix "html".


        Set Up

        Login as yourself onto the SGI workstation in front of you. You will need a normal shell window to run commands in - open one if necessary.


        This shows you how someone can get a copy of your files - using a special file of mine as a demo. We will use this file in later demonstrations. Input the underlined text below into the shell window:
      1. sgi30$ ftp ftp
      2. Login [username:...] anonymous
      3. Password: (invisible)
      4. ftp> ls
      5. ...
      6. ftp> cd dick
      7. ftp> dir
      8. ...
      9. ftp> get home.html
      10. ...
      11. ftp> quit


        Lynx runs on non-graphic terminals - it gets info faster than Mosiac and is ideal for a user with a modem. Run this command
      12. lynx home.html (On Suns, use xvt -e lynx home.html this gives you a new window that simulates a DEC vt100 terminal...)

        Use the space bar, 'b' , and Tab to explore the document that you see. The highlighted text are hyper-text links that can take you to different parts of the document or to a document on any WWW server. Tap the Enter key to follow a link. The '<-' arrow key reurns you to the original document.

      13. Explore!


        Mosaic is a full multimedia browser - graphics, audio, movies, text. However you do need to specify the names of the programs on your machine that view/replay the special formats. Run this command in your original command window
      14. mosaic home.html& It will pop up a GUI version of your home page. Use the mouse etc to explore
      15. Explore! Making yourself at Home You now have your own "Home Page". It is called "home.html" that you should modify to help you do your work. It is a normal UNIX text file and can editted ny any UNIX text editor. The language HTML is not difficult to figure out wither... and 'home.html' has pointers in it to documentation, primers, and resources to help you.


        The new host is set up as a means for faculty to share their work - finished and in progress - with people on the Internet.

        The department will have a special "home page" in the HTML format used by 'lynx' and 'Mosaic'. This needs to define the department for strangers and lead them to areas that interest them. I'd like to have a set of vita files for faculty and to link these to the dept home page. Since Mosiac is good (but slow!) with pictures, we can include scanned in pictures of the faculty as well.

        The public part of ftp|www is only a part of of the server. Faculty will see something else on logging in to '':

      1. blaze$ rlogin ftp -l dick
      2. Password: ...
      3. $ ls




        Faculty have been given a home directory to log in to, and a subdirectory called ftp into which they put publically available items. You have a separate password on this system. It can be the same as the one on other systems - and it is your responsibility to change it and remember it. You can create and delete and edit files in your directory quite freely in the usual way. You can - as usual - create and delete directories to organise their works. You should prepare files to guide the user to relevant papers: a README file, A VITA file, and a home.html file would be good.

        To create a public copy of a MyNewPaper.tex use these steps:

      4. blaze$ rlogin ftp
      5. Password: ...
      6. $ ftp blaze
      7. [...Blaze asks you to login. Use your own name and password....]
      8. ftp> get MyNewPaper.tex /ftp/MyNewPaper.tex
      9. ftp> quit
      10. $ ^D
      11. blaze$ We actually have this:




        It is easy to update an existing file, without 'rlogin':

      12. blaze$ ftp ftp
      13. [...ftp asks you to login. Use your own name and password....]
      14. > put MyNewPaper.tex ftp/MyNewPaper.tex
      15. > quit Note. Just 'put'ting a file to create the"first edition" like the above is risky. It can give write permission to anybody in the world. An anonymous user can erase it or replace it by anything they want without your knowledge.

        Each faculty is solely responsible for there own directories on the ftp/www host. You should include a disclaimer in your files... These directories can contain both partly baked ideas(work in progress) as well as pre- publication copies of papers, articles and reviews. We can expect the quality to vary... The department will publically disclaim all responsibillity for the faculty's individual work in there directories - for example the top-level README file explains the layout of the system and disclaiming responsibility for the content of faculty directories.

        It is, of course, possible to share course materials with students via the ftp/www host... as long as it is OK for everybody in the world to read and copy them as well.

      Special Directories

        We will have several special directories for special projects. Contact the system administrative team (paul and dick) if you have an idea.... the following are already open for business or about to be opened.

      1. The Department Directory The department will be responsible for the contents of the 'dept' directory - which idelly needs to hold up to date schedules, phone books, curriculum, etc. .

      2. The FreeBSD Directory The FreeBSD directory holds the files for the PC UNIX that our students can download and run on their own machines.

      3. The Gaelic Directory Dr. Murphy has volunteered us to be the West Coast site for the internet Gaelic archives. Slanjae Var! (Spelling phonetic)


        Students with Public Information

        I would like it to be possible for students to have files that are on the World-Wide-Web. I want to test the software on the ftp/www server and to look at the risks or opening student accounts to public access before doing this.

        Department Technical Reports etc

        I would like there to be a way for peer reviewed work to be recognized. I therefore propose the following procedure:

        The system administrators create a special directory(dept) for selected materials that have EITHER

      1. been accepted for publication or presentation in another proffessional journal or conference or book OR have been reviewed and selected as being of good enough to be published by the department itself, by (1) the chair of the department
      2. or (2) A group of three tenured faculty other than the chair. In particular, the group and/or chair shouldn't adjudicate on their own work...

        They are electronic technical reports and other papers and articles that can be been printed by anyone. The technique is for a link to made from the faculty's publication into the department's directory. The name of the dept link will the be the faculty's initials , the year and month of its acceptance, (perhaps) a letter, and a mnemonic:

      3. xyz9411.NP!=P!

        The systems administrator can review and summarize all the accesses that are recorded by the system (for example all FTPs are logged automatically) every 3 to 4 weeks, and will report to the department meeting which files a attracting most attention.