SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My OS professor asked for details of architecture, process synchronization, escalonating, deadlocks, threads and how process function but he seem to be convinced that distros have their own implementation of those while I'm pretty sure it is all done by the kernel (which I believe is not changed from distro to distro)...
Anyone can clarify this to me and maybe give me info on where can I get those details as it pertains to the kernel (if in fact that is all handled by the kernel ) ?
Generally speaking, Slackware ships vanilla kernels and unmodified usespace programs and utilities, e.g.those included in util-linux and coreutils packages in the /a series.
Basically the tasks you mentioned are mostly done by the kernel, I think.
Either that, or download a kernel, unpack it, then look in the linux-[version]/Documentation directory. There's plenty of documentation there. Sometimes, the files have easy titles like "preempt-locking.txt". For things like the RCU files, either you have to know where you're going (linux-[version]/Documentation/RCU), or you grep around and hope that a match comes up.
not quite so easy. Sure, all the fundamental services are situated in the kernel, and the kernel has to solve the concurrency problem for itself. But every multithreaded user space application has to solve inter-thread or inter-process communication and synchronization, usually through the use of some thread library. I just don't see where the distro comes into this picture, other than packaging it all up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
