Currently all the syllabus files are empty. We need to update the Syllabus files with the correct syllabus specified by VTU

Currently, like in resources section of Introduction to GCC in Sem1_Sem2 lab, we mention link in embedded text which doesnt get converted while converting to pdf and hence the link never gets known to user. Ideal case would be having the links in the footer, but initially atleast we should change the embedded text and give full link in the text.

In the PDF generated for the CPP Lab the text on the right is not justified. It does not look good to the eye. This is a basic requirement in all manuals and reports

08_Zombie_process

include<stdio.h>

include<stdlib.h>

include<unistd.h>

int main()
{
int pid;
if((pid=fork())<0)
printf("fork error\n");
else if(pid==0)
{
if((pid=fork())<0)
printf("fork error\n");
else if(pid<0) //should be replaced with "else if(pid>0)" <<<<<<<<<<<<<<<<<<<<<<<<<<<<
_exit(0);
sleep(2);
printf("second child,parent pid:%d\n",getppid());
_exit(0);
}
_exit(0);
}

We do not have 8 sem labs...so i suggest we remove them from all repos

The solutions that were made available for the network simulation part in the 7th sem Network Programming lab is missing. I remember @niteshjain had contributed those ns2 simulation scripts. See if they can be restored back

In the pdf at https://docs.google.com/file/d/0B_LXwlSwYmBVUUw4YVJtUVdaMHM/edit
the 3rd program has 3 screenshots....of which only the 3rd one is required..the other two are not relevant to the given program in any way

Currently the contributors list already has around 60 names. We may have to add new contributors who have contributed by sending PRs. So it is better to move the list to the lab manual site. In the manual, we may just add the core team name which is managing the manuals currently or just the owner of the particular subject with his/her contact details so that students who have doubt/issues/corrections can contact him/her.

Isn't it a good idea to have the License file first, before forking as you will now have to ask permission and include all contributors in you license ?

no positional parameters, can't continue, need to know number of commands we want to execute.

So recently one incident happened in #164 , totally my bad! Since Github now has awesome features relating to review, I'd like someone who has admin rights to this repo to impose a few restrictions. (I like to merge stuff quick, that's how we work here, reverting is easy, even in production, we just revert if something breaks). I want the following restriction:

• there's should be at least 2 approved review from maintainers (any fsmk members) to merge

and that's all :)

During my study, I was frustrated with not so understandable ML lab programs, so I created these just a day before final LAB exam to prepare myself and to help my friends.

May I raise a PR to push these into this repo?
https://github.com/ravish0007/ml

The problem is to create a fifo using mkfifo and use a reader and writer process to open the fifo and make them communicate. The code attached in the repo does not achieve this. It just open/creates a regular file and reads content from it (this is my opinion from what i quickly saw).

The following two pieces of code solve the problem in syllabus
https://github.com/niteshjain/CS-VTU-Lab-Manual/blob/master/VTU/Sem6/USP_CD_Lab/04_ipc_fifo_writer.cpp
https://github.com/niteshjain/CS-VTU-Lab-Manual/blob/master/VTU/Sem6/USP_CD_Lab/04_ipc_fifo_reader.cpp

The screen shots also need to be updated along with th instructions

Flowcharts are also required by the students.
It would be helpful if somebody could make them along with the algorithm

There is a .old folder in V/3/DS the purpose of which is not clear.

Can someone take a little time and share their thoughts on the points which I'm think here:

1. We use github site generator to generate documentation which can serve as a site.
2. We can use existing theme and github will generate html from markdown
3. for reference, please have a look at facebook's react native. Not 100% sure though.

We can use Github's automatic page generator.

We really should try the following so the entire repository is maintainable.
We add programs into separate individual files. We can add tests if applicable, or we try to compile and see if that worked. Additionally, we can use make to test a few more things, probably passing set of arguments should yield certain result.

I'd say for example, we've a quadratic equation program, we write in a C file, and not on LaTex or md file, we write in a good way easy to read and maintain, probably chunk them into functions, and if possible, unit test them, else at least do a compile.

thoughts? @fsmk/vtu-lab-manual-maintainers

If everyone agrees, I'll add a sample program (probably refactor a program) with all the tests, and structures over the weekend and send a PR then we can slowly migrate and make it really easy to maintain, easy for students to follow, and a consistent code style.

I'm not sure what's going on with syllabus, or does it make sense to only do this with newer syllabus at first, and slowly refactor the older ones later?

We need to start maintaining all the list of students who have contributed to the repository. Also need to understand how we will manage the names and put it in the Lab Manual once it becomes a big list.

The title should reflect that the manual is a free software manual
Another thing to add is a statement at the bottom that even the manual is designed entirely using Free Software
Since the lab manual is for both 1st and 2nd Sem it should be I/II Semester C Programming lab and also the subject code in Brackets 10CPL16/26

The Markdown files do not make use of GitHub's syntax highlighting format as specified here.

It would be a simple matter of surrounding all code blocks with three back-ticks and specifying the language.

The procedure in the markdown file is not clear. I have prepared a video on how to develop/run this program.
https://www.youtube.com/watch?v=zhbXhQ5cjPU

This can act as an aid to the lab program

Some of the images on the consolidated md file are not loading and the link for mysql package on ubuntu is wrong. It is pointing to multiarch-support

Under VTU all departments in the 1st year have only one computer lab i.e the CCP lab. So i suggest that 1st and 2nd sem be removed from all repos and we have a another repo called VTU-CCP or something like that

I detected at least one duplicate set of programs (refer #14 and #10). I think @prometheansacrifice and @pcputta and everyone else who will contribute should coordinate.

One way is to open an issue here on which program/set/lab/sem you are going to take up so that others will know before picking the next one. Close the issue once you are done. You may mention 'closes #issue_number_here' in the commit message to automatically close the related issue.

@viggyprabhu @shijiltv @sant0sh Share if you think there's a better way to coordinate.

Instead of putting the code in README it is better to keep the code in separate .c or .cpp file and all the documentation in README. So we can clone the repository and just compile and run the code without any hassle.