Conceptual difference between Linux and (Free)BSD Kernel
(I’ve already noticed that this question was asked before but I think it has not been answered in a way I’d like to understand the topic.)
linux-kernel
Are FIFO, pipe & Unix domain socket the same thing in Linux kernel?
I heard that FIFOs are named pipes. And they have exactly the same semantics. On the other hand, I think Unix domain socket is quite similar to pipe (although I’ve never made use of it). So I wonder if they all refer to the same implementation in Linux kernel. Any idea?
Which Debian kernel should I install?
I’ve started installing Debian testing on amd64 and I’ve come to a screen asking me to install a kernel. It gives me a choice between linux-image-3.16-2-amd64, linux-image-amd64, and none.
Why is there a Linux kernel policy to never break user space?
I started thinking about this issue in the context of etiquette on the Linux Kernel Mailing list. As the world’s best known and arguably most successful and important free software project, the Linux kernel gets plenty of press. And the project founder and leader, Linus Torvalds, clearly needs no introduction here.
What do the kernel parameters acpi_osi=linux and acpi_backlight=vendor do?
I had troubles with the screen brightness control in my laptop and I fixed it by adding the acpi_osi=linux and acpi_backlight=vendorparameters to the filegrub.cfg.
I’d like to know what these parameters mean and why they work.
How is the IFB device positioned in the packet flow of the Linux kernel
I would like to know the exact position of the following device in the packet flow for ingress traffic shaping:
cp vs. cat to copy a file
cp a b and cat a > b, what’s the difference?
Does the Linux kernel need a file system to run?
My opinion is yes, it does, because all useful exposure to the outside world (non-privileged processor mode) would first require a process running in the outside world. That would require a file system, even a temporary, in-RAM, file system.
Your kernel headers for kernel 3.10.0-229.el7.x86_64 cannot be found
When I type the command service vboxdrv setup in my CentOS 7 terminal, I get the following error:
What would be the best way to work around this glibc problem?
I administer a Gentoo Hardened box that uses file capabilities to eliminate most of the need for setuid-root binaries (e.g. /bin/ping has CAP_NET_RAW, etc).