bopsvino.blogg.se

Nfs run level
Nfs run level












nfs run level
  1. #NFS RUN LEVEL 64 BIT#
  2. #NFS RUN LEVEL FULL#
  3. #NFS RUN LEVEL WINDOWS#

You should notice that after a clean install, the total size of these directories is not that big, It contains character and block special devices that allow programms to communicate with the computers devices via the kernel. It is divided into many subdirectories with alternate usability. It is a spool area for programms that want to write somewhere. It contains configuration files for most programms and the rc.d directories that is the default for startup scripts. It contains file commands and shells for running startup scripts. It contains the libc libraries that are absolutely necessary if your init is dynamically linked. Some useful programms like the portmap programm and many other programms that are needed before you mount the /usr directory. Also, the /sbin directory contains the startup scripts in the case of SuSE, Which is responsible for starting other programms and start up scripts during

nfs run level

To be able to boot a Linux system, you have to provide it with the following:

nfs run level

SuSE 7.0 distribution: My favorite one, IMHO the most balancedīetween ease of use and understanding of a Linux system structure.GNOME + Afterstep is another option, but not as mature as a solution as KDE.

#NFS RUN LEVEL WINDOWS#

  • The KDE 2.1.1 desktop environment: VERY stable, easy to use, Internet enabled, makes the transition from Windows.
  • If it is important for your users to attach devices to their PC's then it is the only solution.Īlso provides NFS v3, and more efficient memory management.
  • The new 2.4 kernel: It provides a robust and fast solution, using less memory than the old 2.2 series.
  • I choose the following, for the reasons illustrated: Provide a complete working solution without new expenses and without modifying anything but the necessary on the server.īeing the responsible for the project, I had to choose between a variety of solutions about it. The task I had to accomplish was the following:
  • "Dumb" target workstations: 60-70 PC's with variable configurations, ranging from PII 266 to PIII 450 with 64-128 MB RAM.
  • #NFS RUN LEVEL 64 BIT#

    UNIX server: SUN Enterprise 3500 with 2 64 bit Mhz processors and 512 MB of memory.The network at the computer lab consists of the following. Try to persuade the same guy to approve of transforming the server to a diskless node server.Try to persuade the department' s headmaster to approve of the purchase of a bunch of new Unix workstations.The restrictive environment of telnet does not allow us to enjoy the use of a power server.There are 2 alternatives to that:

    #NFS RUN LEVEL FULL#

    On the other hand, students, especially those attending a computer science department,įeel like taking full advantage of it, just for fun or for "educational purposes" (breaking in, hacking it.). This UNIX server is most of times idle or meerly accessed by telnet and running stupid tasks. It is a common case a University computer lab to have a lot PC's running Windows 98 or/and NT and a powerful UNIX server to satisfy the need of an alternative operating environment. This HOWTO expects that you have a general knowledge of what you are up to, so first read the Diskless Nodes HOW-TO.

  • All steps are described in detail, letting the reader to adapt them to his own system.
  • It uses more up to date tools, ex NFS v3.0, kernel 2.4.0, dhcp instead of bootparamd.
  • The distribution specific points should be applicable to all major distributions (RedHat,SuSE,Debian).
  • It provides a working solution fom the distribution used.
  • It borrows the structure of the current Root over NFS, but differs from it in the following points:

    nfs run level

    This document does not resemble a common HOWTO, meaning referencing to general principles,īut it is rather an on-hand approach to a by nature complex matter. Root over NFS - Another Approach: Introduction Next














    Nfs run level