Scribd Logo
Upload

Welcome to Scribd!

  • 13 views

    Log - Additional Task For Every Week: V - Knmrdk69Qm&List Pl3Efbfbce1249Abc0&Index 2

    Uploaded by

    Akhda Khairul Zadid
    Students are required to keep a weekly log of their operating systems study activities, with each entry specifying the week, date, start time, activity category (learning and review, practice session, or discussion session), and details of the activity. The log should have entries in a specified template format and be submitted to a GitHub folder on a weekly basis, either in one cumulative file or separate weekly files. Examples of completed log entries are provided to illustrate the required template format.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Log - Additional Task For Every Week: V - Knmrdk69Qm&List Pl3Efbfbce1249Abc0&Index 2

    Uploaded by

    Akhda Khairul Zadid
    13 views2 pages
    Students are required to keep a weekly log of their operating systems study activities, with each entry specifying the week, date, start time, activity category (learning and review, practice session, or discussion session), and details of the activity. The log should have entries in a specified template format and be submitted to a GitHub folder on a weekly basis, either in one cumulative file or separate weekly files. Examples of completed log entries are provided to illustrate the required template format.

    Original Description:

    Original Title

    01_LOG-additionaltaskforeveryweek.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Students are required to keep a weekly log of their operating systems study activities, with each entry specifying the week, date, start time, activity category (learning and review, practice session, or discussion session), and details of the activity. The log should have entries in a specified template format and be submitted to a GitHub folder on a weekly basis, either in one cumulative file or separate weekly files. Examples of completed log entries are provided to illustrate the required template format.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    13 views2 pages

    Log - Additional Task For Every Week: V - Knmrdk69Qm&List Pl3Efbfbce1249Abc0&Index 2

    Uploaded by

    Akhda Khairul Zadid
    Students are required to keep a weekly log of their operating systems study activities, with each entry specifying the week, date, start time, activity category (learning and review, practice session, or discussion session), and details of the activity. The log should have entries in a specified template format and be submitted to a GitHub folder on a weekly basis, either in one cumulative file or separate weekly files. Examples of completed log entries are provided to illustrate the required template format.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 2

    Version Fri 10th February 2017 at 15:28

    LOG - additional task for every week


    You are required to record your study session each week in a form of log.
    Each row are worth 30 minutes of activity.
    If you have 1 hour session at 14:00 to 15:00, make two row for that session.
    Each row are sorted by time and dates (the newest will be at the bottom).
    Any activity are categorized into 3 different categories, that is:
    a. Learning and Review (code: LR, this is including reading books, watching OS
    related video, listening to lectures, etc),
    b. Practice Session (code: PS, this is including doing lab session, problem
    solving, etc),
    c. Discussion Session (code: DS, this is including discussion with anyone and
    anytime that deepen your knowledge about the OS related matter).
    Specify the detail of each activity in any way you want, with clear information.

    Template for log:

    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]
    [Week:w##]-[Date:YYMMDD]-[StartTime:HH]-[CategoryCode:LR/PS/DS]-[Detail]

    Example for log:

    w00-170206-10-LR-About: Introduction to Operating System, From: Book-


    Guide to operating system
    w00-170206-22-LR-About: Linux Introduction, From: Youtube-
    https://www.youtube.com/watch?
    v=_KnmRdK69qM&list=PL3EFBFBCE1249ABC0&index=2
    w00-170207-13-LR-About: Introduction to Operating System, From: Lecturer
    w00-170207-13-LR-About: Introduction to Operating System, From: Lecturer
    w00-170207-14-LR-About: Introduction to Operating System, From: Lecturer
    Version Fri 10th February 2017 at 15:28
    w00-170207-19-PS-About: GITHUB Learning
    w00-170209-13-LR-Watching demo from lecturer
    w00-170209-13-LR-Watching demo from lecturer
    w00-170209-14-PS-Binary to decimal exercise in class
    w00-170209-19-DS-Discuss scripting
    w00-170209-21-LR-About: Basic Scripting, From:
    https://www.youtube.com/watch?v=34WTt0gNy0g

    Submit the log at the end of every week to yourGithubAccount > os171 > log, you can
    edit and add the log in one file named log.txt for everyweek or make separated file each
    week with name log##.txt (## according to associated week).

    Dont forget to delete file named dummy at folder yourGithubAccount > os171 > log
    before submitting the log.

    You might also like