Is there any way by which a process can acess any field of its process control block structure?
Thanx in advance....
Printable View
Is there any way by which a process can acess any field of its process control block structure?
Thanx in advance....
How are you managing to learn anything, while you're making such huge jumps all over the tech landscape?
One minute it's network gaming, and the next it's kernel hacking.
http://cboard.cprogramming.com/c-pro...er-gaming.html
http://cboard.cprogramming.com/linux...emenation.html
Because he keeps getting these big ideas and discovers he's in over his head and moves on to something else.Quote:
Originally Posted by Salem
What Dibyayan really needs to do is pick some simpler projects, commensurate with his skill level and work towards the bigger goals. Balance the cheque book, do a houshold inventory, write a windows program, write a media player... along a progression of increasing complexity...
We see this all the time... people get through the basics, they learn the keywords, write the parking lot program and maybe the money changer, then decide they're ready for big time coding... Most often the result is that they frustrate themselves to the point of giving up on what could be a very rewarding career or hobby because they are constantly taking on projects they can't handle. I worked console projects for nearly 6 months before trying Windows GUI and worked that for nearly a year before letting any of it get beyond my own hard disk...
It needs to be said that what students learn --even at university level-- is usually just enough to qualify them to start learning... it's not a complete education and anyone who thinks it is, usually ends up repeatedly banging up against their limitations.
Even with the diploma in their hands, they still need to follow the learning process...
yeah....
u r right..
then please help me.tell me a project which might be in my grasp.i am currently doing graduation in computer science.
I really want to learn these things...(i.e network programming,system programming etc..)
please GUIDE me.
Start off with writing a simple file transfer program or a chat server. Then take up an end to end protocol of your choice and implement it from scratch. Post that you can move over to more advanced projects that involve kernel hacking etc. You need to start small.
sorry.i needed to mention the things that i hav done so far..
Implementing graph theory algorithms,numerical analysis.
Basic File handling programmes,
Implementing sorting and searching algorithms,
Implementing linked-list and tree operations
a simple editer programme using Ncurses(could have done with xlib).
A Human v/s Human chess game Interface..(leaving the network programming part)
Using Basic Linux System calls(read,open,write,fork,wait,getpid,exec,kill)
Implemented printf() function using the write system call
Linux Signal Handling,
Shared Memory creation and few process synchronisation problems with solution(producer consumer problem,bounded buffer problem)
Message passing within two or more Cooperating process.
A programme which searches the entire directory tree for a specific file or folder in Linux.(must be a super user )
Using basic functionality provided by shadow.h api in linux.
Image processing--recovery of degraded text document grayscale image and converting it to a binary image.
so i think network programming is way above my head..so
please GUIDE me.I would be very greatfull to all of you guys.
thanx.
From what I understand, you want to get started with network programming, right? How about implementing a command line chat client and a server for starters? You need to mention what you are aiming for. Simply taking up random projects on disjoint topics won't help much.
i think its not a good time for network programming.Quote:
Originally Posted by PING
because i am not confident about my knowledge on networking.there are many basic technical terms (like internet protocol family,tcp/ip etc) which i dont understand yet..
but i think i know just enough about system programming(like things involving linux system call)
to get started..
so i think it would be best for me to learn the system programming first..
what do you guys think.?????
please let me know.
Get a copy of Linux System Programming - O'Reilly Media from a local bookstore. It should get you started on the basics. Once you are comfortable with the introductory material covered in the book, you can take up relevant projects.
No... learn APPLICATION programming first... Write a few small utilities... simple stuff that everyone will use... a mass file renamer, a system cleanup tool, duplicate file finder... then move on to something more advanced, perhaps some system usage monitors or performance monitors. From there get started in GUI mode (Windows or *nix, either way) and write some nice applications... a media player, maybe a few system utilities... file finders, that sort of thing.Quote:
Originally Posted by Dibyayan Chakra
Trying to go from "Finishing your course exercises" straight into messing with kenel code or internet protocals is just going to frustrate the living daylights out of you...
As a friend of mine points out... "You can't dig a hole from the bottom up..."
> i needed to mention the things that i hav done so far..
But if you've already done these things, then why do you need our help for doing anything else?
Someone who has real experience of all those things would have mastered books, google, tutorials, trying things out for themselves.
I think you need to spend some time actually practising what you have learnt.
Because it seems to me that all you're after is a long list of tick boxes without actually learning much at all. That would put you in the 97% bracket of the people in my sig-link. And on that note, some English practice would be helpful as well.
> so i think it would be best for me to learn the system programming first..
I think you need to pick a level and go with it. Personally, I would suggest an application level (there are many applications to write, but there are very few kernels). There's nothing wrong with being "aware" of what is going on in the kernel if you're an apps programmer, but it doesn't need to be a speciality.
thanks for your opinions....
thanks tater.
thanks salem.