Tag Info

Hot answers tagged

3

When you run git branch --set-upstream v3.9.1 origin/master you're telling git that you want your local v3.9.1 branch to track master on the remote. To get the remote v3.9.1 you can simply do git checkout v3.9.1 If you're using the repository you created previously, you'll need to delete your own v3.9.1 branch first: git checkout master git branch -d ...


3

In general linux has very good support for network devices. If the device will work with your version of linux it will allow setup of nfs root with the appropriate initrd. so the problem with root over nfs is that you have to make an initrd that will accommodate it. NFS root without initrd may still work, but will not work with usb ethernet adapters as they ...


2

I don't know what you mean by "console input" but I guess you want to add and remove keys from shell scripts or the command line or such. The interface to the kernel keyring is a set of system calls such as add_key(2). You cannot access system calls directly from the command line. keyctl is the command line interface to the kernel keyring so you will need ...


2

The file containing the kernel is only read by the bootloader (e.g. Grub). As part of the boot process, the bootloader loads the kernel file (and might transform it a bit, e.g. decompress it) and transfers control to the code that was stored in that file. After this, the kernel is in memory, and the kernel file is not used. Therefore, removing all kernel ...


1

You can Install a .deb completely 'by hand' but in this case I would recommend against that approach: the kernel packages rely on a certain amount of infrastructure to build the appropriate initrd for your system, and I think it would be very difficult to get it working manually... If you really want kernel 4.0 and can't wait for the appropriate ...


1

If the kernel is not a complete rewrite (with function names changed etc, reordering of parameters passed into functions), you can analyse the binaries of the original kernel and the patched kernel, and see which functions changed. Then you overwrite the start of a changed routine to jump to a changed version of the routine that you have loaded into memory. ...


1

Your kernel pre-dates the release of Cedarview processors, so it's not surprising that you're having problems. Patching the kernel is likely to be rather complex though, given that you're new at it; you'd probably also need to patch X.org and/or MESA to get things working properly. Since you plan to upgrade at some point, I'd suggest doing that first: it ...


1

by default the mount command displays a list of media devices currently mounted on the system.There are four pieces of information the mount command provides: The device location of the media The mount point in the virtual directory where the media is mounted The file-system type The access status of the mounted media as in your example output of mound ...


1

/proc/net/tcp is not a real file, that can be edited. Each time you read from it, kernel allocates temporary buffer called a seq file, and writes statistics there from current in-kernel data. You may only hjack that by changing code in tcp4_seq_show() in net/ipv4/tcp_ipv4.c and subsequent functions. Note that /proc/net/tcp is actually is a symlink to a ...


1

Kernel modules, whether in-tree or out-of-tree, are installed in directories specific to given kernel versions (/lib/modules/$(uname -r)), so you shouldn't need to clean up modules to upgrade to a new kernel: the new kernel simply won't consider the old modules. Nevertheless, as far as I'm aware in-tree modules go in /lib/modules/$(uname -r)/kernel, so ...


1

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.


1

What happens when my init program exits with return value 0? This code, from the find_child_reaper function in kernel/exit.c, is run: panic("Attempted to kill init! exitcode=0x%08x\n", father->signal->group_exit_code ?: father->exit_code); And consequently this message appears on your console: Kernel panic - not syncing: Attempted to kill init! ...


1

There is no such thing as "Official Support of Linux Kernel". Linux Kernel accepts patches from many vendors, including Red Hat, Intel and even Microsoft (lol!). Eventually, drivers/scsi directory became full of that drivers. You may try to cross-reference supported PCI IDs with names from database. Get supported ids with modinfo: find /lib/modules/$(uname ...


1

You can also try this: Use sar to report on context-switches and irq use over time. Sar is a great but unhearalded system monitoring tool. Run it for a day and then use various reports to look for oddness. Steps: Install the sysstat package. Set up the cron job (check /etc/cron.d/ to see if such a file exists) like this: * * * * * root ...



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