2020 S4C CS232 Free and Open Source Software Lab


Online activities



14/07/20
Sessional
23/7/
Attendance percentage (Added missing entries)


Shortage list (Added missing entries)
RN, Att, Perc

30  35  73
12  35  73
64  34  71
32  34  71
15  34  71
55  33  69
21  33  69
8  32  67
49  32  67
28  32  67
63  31  65
56  30  63
3  30  63
59  29  61
40  27  57
60  26  55
54  26  55
4  25  53
10  25  53
19  22  46
22  21  44
57  20  42
23  20  42
1  20  42
20  19  40
42  16  34


24/7
Attendance: Some calculation errors in code.
Will be updated soon.
Total attendance = BC  hours +AC hours (10 of 11 by me & 8 of faculty 2).
(BC - Before Covid)

BC:
For Batch 1: Four labs + One 2 hr + Two 1 hr = 12 + 2 + 2 =16
For Batch 2: Five labs + One 2 hr + Two 1 hr = 15 + 2 + 2 =19
Late: Two late = 1 hr absent

AC:
Server upload - evaluated by me. Max 10.
Github upload - evaluated by Faculty 2: 8 hrs

So,
Total for batch 1 = 16 + 10 + 8 = 34
Batch 2 = 37

Updated attendance

New shortage list
RN, Att, Perc

36  26  71
64  24  65
30  22  65
32  21  62
12  21  62
49  22  60
21  20  59
15  20  59
63  21  57
8  19  56
28  19  56
55  20  55
3  17  50
56  17  46
40  17  46
60  15  41
59  15  41
54  15  41
4  12  36
10  12  36
57  10  28
19  9  27
22  8  24
23  7  21
1  7  21
20  6  18
42  6  17

25/7
I shall enter the lab attendance as above in KTU after taking my own decision on very low attendance score.  If it is accepted then no issue. We will see.

Sessional;
The following students seem to have less than pass marks.
They are requested to email me, if they have any specific arguments which should be considered while awarding the marks. Make fresh requests ignoring previous requests.

Subject line should have the following text -
S4C/CS232/CS18CXX  - Sessional Marks
(replace XX appropriately)

(Last date and time 27/7/20 2PM)

Other students also if they have any genuine grievances -- please email afresh.



------------------------
RN    V1    V2    V3    V4    Tot    /100
8      20    21    28.5    31     100      39
64      26    31       0    41    98.5      38
3      24    39    14.5    21      98      38
30      24    37    16.5    21      98      38
59      12    17    33.5    31    93.5      36
49      21    26      16    31      94      36
10       0    0      40    51      91      35
63      22    25       0    31      78      30
60       8    17       0    51      76      29
56      22    30       7    10      69      27
40      14    24       6    0    43.5      17
54      14    22       0    0      36      14
20     6.5    17       0    10    33.5      13
23      18    12       0    0    29.5      11
19      11    18       0    0      29      11
1      13    16       0    0      29      11
22     6.5    9       0    10    25.5      10
57       0    0       0    21      21       8
4       9    11       0    0      20       8
42       0    0       0    10      10       4


I will directly address matters that could be decided between us.
I cannot condone myself, if you have not submitted your works.
Normally, difficulties reported in time will have more weight.
Excuses for not doing your work must be routed through staff advisor and HoD.

27/7
Those with less than 40% attendance will be marked as incomplete.


Final sessional is here

28/7
See the marks and attendance as entered in KTU portal.
Discrepancy with published data if any, please report.


Attendance breakup:
Those with at least 40% have been cleared.

File contents: Column-wise
roll number, regular, server, github, total, percentage



 Date
Details
16/3/
2020
In the wake of closure of the college till 31/3/2020 on account of Coronavirus pandemic, and instruction from higher authorities to conduct academic activities through online media, we are also exploring the possibility of using Internet for completing S4C CS232. Hence all experiments that could be completed at home could be done by the students in their personal systems and uploaded to the server and GitHub as per existing instructions. Evaluation 1 will be conducted possibly every day. So please make use of this facility.
If user ask is online write command may be used to discuss doubts. Will be online intermittently during daytime. But, will be online most of the time between 7PM to 10PM.
17/3 ** A PC will cost not more than the smartphones most of us possess.

** Those of you who could do it at home, should do the experiments. For the rest we will consider other options.

** For uploading only very little data traffic is needed. So Internet speed is not an issue.

** Students are asked to do those experiments which could be conducted at home, the rest we will do after re-opening.

** Most of you possess a smartphone? As, mentioned sometime before, install a Linux terminal in it and try your experiments there, if you    don't have a PC.

**
There could be enough excuses not to do something. It is not difficult to figure out whether reasons are genuine or not.

**
If students do their experiments well, they are the beneficiaries. It is not about marks alone. It is not for the faculty or the institution.

** Opinion: Being CS students, a Linux PC or laptop is as essential as a smartphone now.


-------

** When you login via ssh look for mails sent by me. "mail" command could be used. It could be used to communicate with me and your colleagues. It works even while the other user is logged out.
18/3 When using "mail" command, let us be a little informal!, because the context and identity are already defined.
19/3 Ensure that uploaded files are readable by all. 
These off campus submissions are evaluated and posted as Evaluation 3. See table below

To mail me type: mail ask <-l
input Cc if you want, it could be your id say cs18c00
type subject 
<-l
type the mail content
finally press ^D
21/3 I will evaluate all your works uploaded. Need not mail about it. You may mail if not evaluated after 3 or 4 days. Also, look for my mails in case it doesn't appear in evaluation sheet.

** Also look for comments in
evaluation sheet.
22/3 Please read the instructions posted earlier again. Re-read "Messages" 10 again.

** I expect independent programs. Why many are doing same examples even for writing simple perl programs?

** Experiments which were scheduled to have completed before college closure, will not be evaluated now. You may submit them. But, decision regarding their evaluation will be taken later.

** When ftp and http servers are installed try connecting from other devices also. Upload traces of such connections if possible.

** Date of submission and directory name should match
23/3 ** Server installation and testing: When servers are installed, try connecting them from another device and show the results.
   - web server, ftp server etc
   - LAMP stack: Try connecting the web server from another device via php code. Also try some elementary database access from another device.

** Please do not edit the contents of a dated folder already posted. Instead create another folder with new date and post there. This is because, normally I will evaluate one folder only once - for practical reasons.

** Also ensure that a dated folder is updated only when every contents are ready with your local system.

** Look for reasons/replies at public mail, server mail,  or ev3 comments.

** Kernel compilation: It will be worth trying to compile a custom kernel say by only retaining very essential modules.

**++: Can somebody plan and write the script to visualize with charts and graphs the spread of Covid-19 day by day district-wise for Kerala and state-wise across India?
24/3 It is painful to re-state every instruction written already. Read them again. Read about image size restriction.
25/3 Looked at the code submitted by 47 Aravind R  about the covid data visualization. I didn't notice that he had submitted it yesterday. Any one else done similar work independently please mail me about the submission. We will think of making it public, so that it benefits others.
If data is not available online, static feeding also can be considered. Now, I shall assess Aravind's code.

On testing, I am facing some url request errors. To get them resolved, to complete.
26/3 ** Some pending evaluations piled up, as spent little time here on last three days. Now, may I put up a question here - given a package management exercise, what is the probability of 3 persons at different locations installing and removing the same package under Ubuntu Linux?

** Just now saw the corona graph of 62. Can't you along with 47 publish the details online here or elsewhere via http? Try log graph, district-wise bars.
28/3 * Upload only files <= 500 KB
* After a directory contents are evaluated any modification done there won't be seen by me.
29/3 All submissions upto 28/3/20 have been cleared.
30/3 ** All submissions upto 29/3/20 have been cleared.
** Syllabus experiments from  2 onward will be evaluated. (Except 12, 15, 17, and 18)
31/3 ** "drwxr-xr-x 2 cs18cxx cs18   4096 Mar 30 21:52 3103"
How is this possible?

** It is human to attribute the fault elsewhere, (of course, I am also human!).
Anyway, if you have received less marks, check the read permissions of your uploaded files.
Also, read general comments, comments about your postings, and comments about others but applicable to you as well.
Also, once a submission is made, modified files should not be uploaded there, I will download one directory contents only once.
Also, I will be best impressed on seeing genuine original stuff, in work, in style, and in format.
Still not able to find the fault?  --  email me -- but only then. But, emails will normally be replied after other pending evaluations are over, but I am getting continuous submissions, happy about it though!

Please don't send emails displaying your frustrations, it won't serve any purpose. Definitely, I am not going to get influenced, especially if you think you are anonymous!

** Create the directory and post the contents of the day only after completing and readying all the files. Only one date-wise directory is permitted per day.


** All submissions up to 30/3/20 have been cleared.
1/4
** All submissions up to 31/3/20 have been cleared.

** Once again asking if any one or a group from you could write a web based code to show the growth of covid globally, country-wise,  state-wise, and district-wise. It graph may be based on actual data, and log graph. Also, various charts should also be displayed. the data could be collected from various sources and stored in text files or so. Or, data could could be extracted online - but only if possible, and feasible.  If after testing, and approval, for hosting in our server, if any package is to be installed, you may inform me.
2/4 All submissions up to 01/04/20 have been cleared.
3/4 All submissions up to 02/04/20 have been cleared.
4/4
From 5/4 onward all report.txt should contain the public ip of the machine you are using.
5/4
All submissions up to 03/04/20 have been cleared.
6/4
All submissions up to 04/04/20 have been cleared.
7/4
In the report please mention the task number.
All submissions up to 05/04/20 have been cleared.
8/4
* Evaluations queued up: 5 9 , 3 38 31 52 37 62 65
* Up to 06/04 - Cleared
* "Professional Ethics" is as important as the profession. We need to practice it from student-hood. We need to have self respect, we need to respect others.
We must acknowledge the source if for any particular task,  we have gathered critical help from that source.
* Cleared - up to 7/4
* New Q: 31 43 58 11
9/4
* Cleared - up to 8/4
* New Q: 26 37 65 07 11
10/4
* Cleared - up to 9/4
* Q - Empty!
11/4
Q: 53 38 41 50 26 58
12/4
Q - Empty
13/4
Q: 6, 37 16 26
14/4
Q:59
16/4
Q: 43
17/4
Q: 53 11 59
18/4
Q: 37 18
20/4
Q: 30 07 27
21/4
Q: 30 07 27, 18 11
22/4
Planning to be on Jitsi Meet tomorrow after 7PM for discussion with students. Details later. 
23/4
I am there. ceccs
passwd cscec
over
Q: 15 39 02
24/4
Q:  62 15 65 02
25/4
Q: 36 31
26/4
59 37 26
27/4
37
29/4
07
30/4
48 02 07 49
1/5
48
17/5
Q: 48 06 30 51 11 08 46 34
21/5
Q: 40
11/07
Last and final Q: 14 34 05 26 51 13 46 41 16 62 61 39 63 40 18 36
Files extracted. Evaluation soon.

Evaluation over.

14/07
Consolidation of online submissions. Best 10 will be considered.

All files considered for sessional : ev1.txt  ev2.txt  ev3.w.txt  ev4.m.txt






Syllabus
.html                      .pdf
Students' List
S4C


Contact  Hours

Monday
1-3
Thursday
2-4

Material/Tasks
git tutorial

(t1)  Linux commands

(t2) Scripting Task
Download KTU S1 results of your batch.
Convert to .txt file: may be pdftotext -layout useful
Separate results of S4C only. grep command may be useful. Don't edit the files directly.
Compute sgpa for students who passed all subjects, for the rest count number failed subjects as n and display it as -n.
Show result with name and register number.
Similarly do for S2.
Compute cgpa.
Sort the result.

grade and grade points
O,A+,A,B+,B,C,P,F,FE,I
10,9,8.5,8,7,6,5,0,0,0
  
(t3) Networking tasks
Set up n/w with ifconfig, route, /etc/resolv.conf

(t4) ssh, rsync, scp etc.

(t5) ftp usage:
Server: Public 14.139.189.217, LAN 192.168.0.30

Refer and read ftp commands before usage (man ftp)

username and password will be provided

if any trouble with ftp, try sftp.


(t6) Linux installation:
First using DVD, which will be provided.
To photo the process camera or phone may be used, but only for this purpose. Upload photosize is limited to 500KB/photo.

(t7) Setting up http and ftp servers

(t8) Further tasks
1. Package management
2. perl
3. LAMP stack
4. Kernel compilation


(t9) Create own web page at our server.
Upload contents in your home directory and if required in sub directories, linked to index.html at  your home directory in 192.168.0.30. Sample is there at cs17d00.
http://192.168.0.30/cs18c/cs18c00

The pages could be accessed as http://192.168.0.30/cs18c/cs18cxx




Schedule
By
Syllabus Experiments
Custom experiments to cover the syllabus
Feb 28
1-9, 11,18
t1-t5, t9
March 6 12
t7
March 13 10,13

March 20
14,15
t8
March 27
16

April 6

t6
April 17
17


Messages 1. Whenever writing code, write code indented and documented.
2. git upload the code and results. Upload to ftp server also.
3. Result is preferred as copy paste of text content from the screen.

4. "script" command is recommended for recording your actions on the terminal
usage example:
script work.txt 
do your work
finally type "exit"
Upload   work.txt after removing unnecessary and duplicated contents


5. Upload a short report of the work carried out in the lab, along with supporting docs as report.txt. Copy paste the input and output from the terminal as you executed the code.

6. You are required to upload every day's work in github and ftp server

7. Server username and password:  cs18cxx.
Password may be changed by the student. Recommended.

8.
The work file, report file, and other task script files should be stored in a directory named  ddmm where dd refers the day  and mm the month. Directory ddmm should be created at the server.  No further sub-directories are allowed inside ddmm.

9.  Note these:
Directory name: ddmm
Work script file name: work.txt
Report file name: report.txt

10. Every file shall bear your roll number as cec-cs-18-cxx and date of lab work as dd-mm-yyyy

11. Format of report.txt

12.
Come prepared to the lab with questions and written commands/script/task  in a note book.
Note book should bear the date and experiment number written on the top-left margin of the code as " 20/01/20  #1,  20/01/20 #2, ... " etc.

13. Adhere to the instructions strictly.

14. Commence the lab in time and finish all the work including file uploading by the scheduled closing time of the lab.

 18/2/20: Additional instructions:
15. Please don't create any subdirectory. Store all files files in the stated folder.
16. Ensure that the directory names are strictly as suggested.
17. In the web page all links should be to the LAN server files - that is mandatory. Additionally may create links to github contents.
18. For networking experiments ethernet switch is avalable.
19. For installation experiment DVDs are available.
Experiments

Students' Progress
Experiment Progress

Evaluation 1

Evaluation 2

Evaluation 3
Final Evaluation

Attendance




Internal marks
 



                                        Course Progress

Month
Date
Hours
Progress
Class
Count
1-32
Class
Count
33-65
Absentees
No.
of
Abs
Late
Remarks
January
13
1-2
Intro, Linux commands
1
1
1 5 7 8 10 14 15 20 21 23 26 28 32 39 40 41 42 43 44 48 55 60 63
23



15
6
Linux commands, scripting
2
2
1 2 3 4 5 7 8 9 10 12 13 14 19 20 21 22 23 25 26 27 28 34 36 37 38 40 42 43 53 55 56 58 59 60 61 65
36

At 4 PM at final bell, wished to convey more instructions to willing students so that it could be shared among the class. Given a choice none stayed back. Happy to know that S4C students can do the works of this subject on their own.

20
1-3
Lab

3
34 36 40 42 46 51 54 57 59 60
10



24
2-4

3

1 8 10 11 19 20 22 23
8



27



4
39 42 57
3
43 38 64 53 37 58 61 34 47 52 59 62
63 41 60 65 44 49 40 51 46 55 56 36


29
6
Class
4
5
12 15 29 36 54 59
6

Conveyed that the preparations and performance in the lab are not satisfactory. Discussed more topics. talked about ssh, rsync, ifconfig etc.

31
2-4

5

4 10 22 23



February
3
1-3


6
42 49 57 58 60
5
36 59 56 55


7
2-4

6

3 10 20 22
4



10
1-3


7
34 42 57 59
4
46 51 36 55 56
Have some self respect. When you copy others work and report you learn nothing. Moreover when you copy without knowing what is it, the errors are easily identified and it is annoying.




17
1-3

7

1 10 19 20 21
5
4 22 23 26 14

24
1-3


8
55 56 59
3
60 41 36