New answers tagged

0

Isn't /boot mounted readonly, by chance? If so, mount -o rw,remount /boot && yum update kernel && mount -o ro,remount /boot (note: I'm rarely seen at centos hosts being an ALT Linux developer so YMMV)


0

An error is occured when you are trying to copy the existing Kernel: To copy your existing Linux kernel config file run: cp /boot/config-`uname -r` .config Or cp /boot/config-$(uname -r) .config Install the kernel-package: apt-get install kernel-package To configure the kernel, run: make menuconfig make sur that Kernel module loader is ...


1

Adding more detail to the answers above. As we're using VM's more and more, a linux host may be a vm on one of these cloud environments. In both examples 1 & 2 we've got a good idea of the applications running and so how much RAM they consume. In 3, not so much Example 1 A high performance private cloud (think the sort most banks would pay millions ...


1

That depends on the underlying storage technology. Some storage allows a certain block size to be stored atomically, typically a power of 2 which is at least 256 and usually in the 1kB—4kB range. If that's the case, then the filesystem layer can replace blocks in place, provided that the replacement of the block yields a valid system state. This is fine ...


1

The linux kernel source in Ubuntu is open source, so there is no problem with using (parts of) it, just like you can use any other linux kernel source. Using the Ubuntu name for your OS is not allowed unless you have permission from Canonical (who own the Ubuntu trademark), which in general is true for any other trademarks and their owners too. Of course ...


3

A disk should grant that a sector is written atomically. The sector size was 512 bytes and today is typically 4096 bytes for larger disks. In order to get no problem from partially written "blocks", it is important to write everything in a special order. Note that the only reason why there could be a partially written part in the filesystem is a power ...


-2

Generally, all moderm OSes 'll have a system call for writing data to a file (in Linux we have write system call). And because all system call should be atomic. So writing the entire block size (using only 1 system call) will be atomic.


1

I'm looking at this one: Slurm is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First it allocates exclusive and/or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and ...


0

I had same problem. After much googling, this solution worked for me. It first determines the installed kernel version and then uses that exact version to install the kernel header package. sudo yum install "kernel-devel-uname-r == $(uname -r)"


0

It is the lack of support for the GPU in kernel (and likely also in X.Org video driver) which you need to somehow solve. Proper support for Sky Lake based GPUs in i915 kernel driver should be available from kernel 4.4 on. Then again, myself I still couldn't get a Intel GPU with device code 1912 working in Debian Jessie under 4.4.5 due to something with ...


2

The kernel on OpenBSD via in6_ifattach_linklocal, as found by a fgrep -rl fe80 /usr/src 2>/dev/null search.


-1

Kernel space is strictly reserved for running a privileged operating system kernel, kernel extensions, and most device drivers. In contrast, user space is the memory area where application software and some drivers execute. Reference link: http://rhelblog.redhat.com/2015/07/29/architecting-containers-part-1-user-space-vs-kernel-space/


1

You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax module_to_blacklist.blacklist=yes OR modprobe.blacklist=module_to_blacklist You need to modify the grub,cfg to make the changes permanent. Mind you, this solution will not work for few modules


2

This is potentially related to El Capitan and its System Integrity Protection (csrutil status) which can affect the dtrace behaviour. The potential fix includes rebooting Mac into recovery mode (⌘-R at boot time), then in Terminal run: csrutil enable --without dtrace to keep SIP enabled, but disable DTrace restrictions (note: this is undocumented ...


1

For redirection, I would assume this (redirection) is implemented by the shell replacing stdin (by input for < input) and stdout (by output for > output) using dup2() - open files for input and output in = open() out = open() dup2(in, 0) // replace input file with stdin dup2(out, 1) // replace output file with stdout close(in) ...


1

"redirection" is a concept of the shell, and the details around it depend on which shell you are talking about. Though, one might say that the basis for redirection rests with the notion that programs have pre-opened input and output file descriptors when they start, which traces back to how the execve function works. Namely that the child process inherits ...


1

On any POSIX system, the interface between applications and the kernel is a few function calls: open, read, write, close, etc. An application such as cat calls those functions; it doesn't care how the functions are implemented under the hood. On Unix systems, those functions are actually system calls: the application calls the kernel. Inside the kernel, a ...


2

The Unix/Linux system offers the POSIX system calls open(2)/close(2)/read(2)/write(2) and stat(2) and some higher-level functions like opendir(3)/closedir(3)/readdir(3), which are enough to write the tools stated (it is easier using the C wrappers). Part of the hard job of the kernel is precisely to make them work on the various filesystems offered, and make ...


1

For most tools, the underlying layer is the C Standard Library ("libc"). libc provides a number of low-level file handling routines, such as open, read, and write. These routines in turn interface to the filesystem layer in the kernel, which sits on top of the kernel's block device layer, the device drivers, and finally the hardware. One implementation of ...


6

Overwriting swap with random values is equivalent to overwriting process images in memory with random values. If a text segment with random values is executed, the most likely result is process termination due to an illegal instruction (signal SIGILL). If a data segment with random values is read, the result is most likely process termination due to a ...


4

If you just mean running "swapoff -a" when you say "clean up", then no. If you corrupt/overwrite the swap device/file, an application that gets swapped back in (with corrupted data) is very likely to crash, yes. The kernel does not get swapped out, so the "system" would not crash.


0

Your laptop has a BIOS whitelist and the Intel 5100 is not on it I would recommend calling Lenovo and ordering an Intel wifi card with 5 Ghz from them that will work with the X220 as the option to update the BIOS with a version that eliminates the whitelist might render the laptop useless. I found the maintenance manual for the X220 and the Centrino ...


0

You should see if relevant messages is available in logs or dmesg Look for lines like missing firmware file xxxx/xxxx (Since I do not have a Linux box at hand, it's just an example found online) Then you'll know which file to download.


0

You can get the specific source RPM from Koji, Fedora's build system. In this case, it's at https://kojipkgs.fedoraproject.org/packages/kernel/3.17.7/200.fc20/. (There are multiple ways to find this, but in this case, I simply did a Google search for "kernel-3.17.7-200.fc20.x86_64 koji".) Install the source rpm (as non-root) — install and run ...


1

You can manipulate some of the pci bus registers of the device fairly easily with setpci. Note: this is dangerous and may crash your system! For example, find the pci bus and slot for your graphics board: $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) $ ...


1

Some notes, mainly on BIOS/GRUB systems. BIOS system with GRUB: BIOS start of from address 0xfffffff0 (x86). Do various tests e.g. POST. If all well then check the devices, in the order configured and saved in CMOS. First boot device that has a valid MBR, (signature at offset 510 is 0x55aa), is loaded into memory at address 0x7c00. Then BIOS leaves ...


0

Try to downgrade the kernel from 4.2.0 to e.g 3.19.



Top 50 recent answers are included