Hot answers tagged kernel
Yes this is possible, but it is not possible by cutting two USB cables with USB-A connectors (what is normally going into the USB on your motherboard) and cross connecting the data cables. If you connect the USB power lines on such a self made cable, you are likely to end up frying your on-board USB handling chip. Don't try this at home! On most computer ...
It might help to up /proc/sys/vm/page-cluster (default: 3). From the kernel documentation (sysctl/vm.txt): page-cluster page-cluster controls the number of pages up to which consecutive pages are read in from swap in a single attempt. This is the swap counterpart to page cache readahead. The mentioned consecutivity is not in terms of ...
Mounting or remounting a filesystem is done using the mount(2) syscall. When remounting, this takes the target location (the mountpoint), the flags to be used in the mount operation, and any extra data used for the specific filesystem involved. When remounting read-only, the flags used are MS_RDONLY and MS_REMOUNT; you're also supposed to provide any other ...
You may try adding the programs you most care about to a cgroup and tuning swappiness so that the next time the application runs the programs you add are less likely to be candidates for swapping. Some of their pages will likely still be swapped out but it may get around your performance problems. A large part of it is probably just the "stop and start" ...
It seems to me that you can't magically "make the system responsive again". You either incur the penalty or reading pages back from swap space into memory now or you incur it later, but one way or the other you incur it. Indeed, if you do something like swapoff -a && swapon -a then you may feel more pain rather than less, because you force some pages ...
you could use a USB bridge device which is available in a cable form-factor like this ... http://www.usbgear.com/link/ (auto-play video warning)
I expect library symbols will be different, even if you've got what appear to be the same versions in-place. As a half-measure, look for statically-built binaries; then you only have to worry about getting a myriad file locations all correct so the app stops complaining. In many, many cases, if not all, it's simpler to rebuild the app for the environment ...
Most of them used to be implemented at some point in Linux kernel history time, but some like at least vserver are still implemented in specific kernels. The majority of these calls is now essentially obsolete but their slot remains and contains a stub which role is not to break old code and allow a re-implementation in a specialized or new kernel should it ...
For compiling kernel module you should create Makefile and to include kernel module makefile /usr/src/share/mk/bsd.kmod.mk for example: # Note: It is important to make sure you include the <bsd.kmod.mk> makefile after declaring the KMOD and SRCS variables. # Declare Name of kernel module KMOD = module # Enumerate Source files for kernel module ...
Linux Mint comes in two flavors. Ubuntu based Debian based (LMDE) The Ubuntu based version (the default one) is guaranteed to work with Ubuntu packages and the LMDE is guaranteed to be compatible with packages from the Debian repository. Even though most debs of Debian works in Ubuntu it still some non-compatible packages due to File system hierarchy ...
In the modern kernel, devices are described via the device tree. The device tree will contain a description of various hardware elements and names of their respective drivers. When a device matches a device tree entry, the device driver associated with it is alerted. The device driver then probes the device to test capabilities. mac80211 is a framework ...
There's a fantastic pair of articles on LWN that describe how syscalls work on Linux: "Anatomy of a system call", part 1 and part 2.
All firmware which isn't distributable under the GPL-2 isn't provided within the kernel, but is available separately in the linux-firmware project. You'll find OLAND_pfp.bin there; you can clone the repository and run make install as root, which will install all the firmware in appropriate sub-directories of /lib/firmware.
To be sure that your machine generates a "core" file when a core is generated then you should confirm "systcl" settings of your machine. IMO, following should be the settings (minimal) in /etc/sysctl.conf kernel.core_pattern = /var/crash/core.%t.%p kernel.panic=10 kernel.unknown_nmi_panic=1 Do not forget to execute "sysclt -p" after making changes in ...
It's in kernel space. This article from Linux Device Drivers is a bit dated but still should generally apply: https://lwn.net/images/pdf/LDD3/ch18.pdf However, there is some effort recently towards replacing the kernel driver with a userspace console called "KMSCON" -- see that project's site for more: http://cgit.freedesktop.org/~dvdhrm/kmscon/tree/README
The Linux-based system I tried doesn't have a section 9 in its man page, but, looking online, one can find the NetBSD intro(9) man page: This section contains information related to the internal operation of the system kernel. It describes function interfaces and variables of use to the systems and device driver programmer. This appears to be about APIs ...
Virtualbox allows to configure two types of SCSI controllers, one being LSILOGIC the other Buslogic compatible. Those should be supported by the bt(4) and mpt(4) drivers. You can remove all other SCSI controllers If you use IDE/SATA controllers you can remove all SCSI drivers.
I tried as G-man suggested in the comments.The main Makefile will include the 'Makefile.inc1' and pass some parameters to it e.g: TARGET_ARCH=i386, that's where buildkernel is defined.
On FreeBSD there is a difference between reboot and shutdown -r now. From the reboot man page: Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs.
Only top voted, non community-wiki answers of a minimum length are eligible