Tag Info

Hot answers tagged

9

LTR stands for Long Term Release. This is also known as a LTSR, short for Long Term Support Release. These releases are supported for a longer time, and are meant to be used in Production Environments, where stability is preferred over new features. In terms of the kernel you are reading about, the LTR cycle is about 3 years. This means if you are a user ...


4

As it so happens, there is another significant interface with the kernel: the /proc and /sys virtual filesystems. While they do not hold regular files, their contents are direct gateways to the kernel: to act on them is to act directly on kernel-allocated memory. For instance, if you want to drop all memory caches, you may use... echo 3 > ...


4

I will try to answer questions as briefly as possible. The questions you are asking are usually addressed in introductory operating systems courses at universities but I will assume you have not taken such a course. Memory isolation for userspace processes is very desirable - not only to protect the kernel from malicious userspace programs, but also to ...


4

These are Long Term Releases: There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees. Source: https://www.kernel.org/releases.html


3

The premise is unprovable. Science requires a falsifiable hypothesis; there is no way to test any of the likely counterhypotheses, such as that Windows would crash less if Apple wrote all of the drivers instead, or that Windows would be more stable if Microsoft somehow cut off support for a vast chunk of the existing supported hardware space. You'd basically ...


2

Regarding Village's Bounty, all I can find is an archived mailing list post from August, 2011 stating that the preferred default before kernel commit r225076 was 32 GB, and up to 32 Slices for a Total of 1 TB of Ram (32^2 = 1024) After r225076 the limit per slice was removed, but the thread goes on to say that the practical limit should still be considered ...


2

The OpenBSD FAQ is your friend in this case. They have extensive documentation on how to build your own kernel. In particular you want section 5.3.4 but before you do that make sure and read all of section 5.3 to get a feel for the bigger picture. I'd also recommend taking a look at Absolute OpenBSD by Michael Lucas. He's got a pretty good walk through on ...


2

Since kernel 2.4 there is no difference between these cache types, there is only the page cache left.


2

Get your current config.gz and deploy it in a source tree as described in this answer. Start make menuconfig and go into the "Device Drivers" submenu. Make sure "Serial ATA and Parallel ATA drivers (libata)" is disabled. Scroll down to the "USB support" sub-submenu and make sure "USB Mass Storage" is disabled. You could completely disable USB too if you ...


1

It depends. What do you mean by 'verify'? If you just want to monitor what syscalls some process is triggering then it's possible.. usually.... But if you feel like digging deeper then you're in trouble... I have not heard of any tools that could do that. You can use strace to see what syscalls some particular process is firing. Of course you'll have to ...


1

If a process is doing a lot of memory IO, then that will translate into using a lot of cpu time, so the scheduler will account for it, indirectly.


1

If someone has physical access to your computer, they can boot from a USB key, or take out the hard drive and plug it into another computer. To prevent someone from changing boot parameters, put the computer in a locked case or locked room. If the computer is in a locked case but its keyboard is accessible to untrusted people, then you need a software means ...


1

As it turns out, it seems the underlying issue was not having the right proprietary drivers installed for my nVidia graphics card. I was under the presumption that I had to use nVidia's driver installer, but installing the right packages from RPMFusion and disabling Nouveau worked perfectly. Since installing the necessary drivers, my system is running ...


1

In both cases those are not primarily warnings that break the build. For the kernel compilation: error: 'struct run_vap' has no member named 'beacon_mbuf' the compiler tells you, that the code is trying to access something that isn't there. This may have many reasons, but generally it suggests that the code is broken. Maybe you are trying to compile a ...


1

Turns out to be a false warning. To quote from the (now closed) kernel bug report: Alfred Krohmer: If I unterstand your patch correctly it just removes the warning, but it won't actually fix the driver crash this bug report was submitted for. So why mark it as resolved? Emmanuel Grumbach: There is no real bug. The commit message explains this. ...


1

For Ubuntu, usbcore is compiled in the kernel, so create entries on /etc/modprobe.d will NOT work: we need to change the kernel boot parameters. Edit the /etc/default/grub file and change the GRUB_CMDLINE_LINUX_DEFAULT line to add the usbcore.autosuspend=-1 option: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1" Note that quit splash ...



Only top voted, non community-wiki answers of a minimum length are eligible