Şimdi Ara

Ceviri

Daha Fazla
Bu Konudaki Kullanıcılar: Daha Az
2 Misafir - 2 Masaüstü
5 sn
2
Cevap
0
Favori
226
Tıklama
Daha Fazla
İstatistik
  • Konu İstatistikleri Yükleniyor
0 oy
Öne Çıkar
Sayfa: 1
Giriş
Mesaj
  • Arkadaslar ingilizce ceviri ödevim var son 1 sayfa kaldı, ceviride bana yardımcı olur musunuz






    SEC. 1.6 SYSTEM CALLS 57
    an open on the file xyz will open /usr/ast/test/xyz. The concept of a working directory
    eliminates the need for typing (long) absolute path names all the time.
    In UNIX every file has a mode used for protection. The mode includes the
    read-write-execute bits for the owner, group, and others. The chmod system call
    makes it possible to change the mode of a file. For example, to make a file readonly
    by everyone except the owner, one could execute
    chmod("fi!e", 0644);
    The kill system call is the way users and user processes send signals. If a
    process is prepared to catch a particular signal, then when it arrives, a signal handler
    is run. If the process is not prepared to handle a signal, then its arrival kills the
    process (hence the name of the call).
    POSIX defines several procedures for dealing with time. For example, time
    just returns the current time in seconds, with 0 corresponding to Jan. 1, 1970 at
    midnight (just as the day was starting, not ending). On computers using 32-bit
    words, the maximum value time can return is 2 3 2 - 1 seconds (assuming an unsigned
    integer is used). This value corresponds to a little over 136 years. Thus in
    the year 2106, 32-bit UNIX systems will go berserk, not unlike the famous Y2K
    problem that would have wreaked havoc with the world's computers in 2000,
    were it not for the massive effort the IT industry put into fixing the problem. If
    you currently have a 32-bit UNIX system, you are advised to trade it in for a 64-bit
    one sometime before the year 2106.
    1.6.5 The Windows Win32 API
    So far we have focused primarily on UNIX. Now it is time to look briefly at
    Windows. Windows and UNIX differ in a fundamental way in their respective
    programming models. A UNIX program consists of code that does something or
    other, making system calls to have certain services performed. In contrast, a Windows
    program is normally event driven. The main program waits for some event
    to happen, then calls a procedure to handle it. Typical events are keys being
    struck, the mouse being moved, a mouse button being pushed, or a CD-ROM
    inserted. Handlers are then called to process the event, update the screen and
    update the internal program state. All in all, this leads to a somewhat different
    style of programming than with UNIX, but since the focus of this book is on operating
    system function and structure, these different programming models will not
    concern us much more.
    Of course, Windows also has system calls. With UNIX, there is almost a oneto-
    one relationship between the system calls (e.g., read) and the library procedures
    (e.g., read) used to invoke the system calls. In other words, for each system
    call, there is roughly one library procedure that is called to invoke it, as indicated
    in Fig. 1-17. Furthermore, POSIX has only about 100 procedure calls.







  • 57. sayfa Miscellaneous System ile baslayıp 100 procedure calls ile bitiyor


    http://s5.dosya.tc/server/5hduWu/i_letimsistemleri_en.pdf.html
  • Yapay Zeka’dan İlgili Konular
    LİNGUSTA INGILIZCE
    9 yıl önce açıldı
    Daha Fazla Göster
    
Sayfa: 1
- x
Bildirim
mesajınız kopyalandı (ctrl+v) yapıştırmak istediğiniz yere yapıştırabilirsiniz.