Hot answers tagged

9

I'm not working for a distribution, but I can think of at least two reasons: Some distributions apply their custom patches to the Kernel which are not merged into mainline yet. This means for every update of the Kernel they need to ensure that their patches don't break anything and still function properly. Even the latest stable Kernel release can contain ...


5

The Linux kernel's system call interfaces are very stable. But the kernel has other interfaces that aren't always compatible. /proc is mostly stable, but there have been a few changes in the past (e.g. some interfaces moving to /sys some time after /sys was created). A number of device-related interfaces have been removed in the past. /sys contains some ...


4

You can use rsync linux utility. You need to specify source and destination,it works locally as well as remotely. Please check man rsync for more details. For solaris, you'll need to install it.


3

ps output can be filtered in may ways. To see your processes, you could filter by the user/uid. relevant man page below -- U userlist Select by effective user ID (EUID) or name. This selects the processes whose effective user name or ID is in userlist. The effective user ID describes the user whose file access ...


3

If you do not want an absolute limit but just pressure the kernel to flush out the buffers faster, you should look at vm.vfs_cache_pressure This variable controls the tendency of the kernel to reclaim the memory which is used for caching of VFS caches, versus pagecache and swap. Increasing this value increases the rate at which VFS caches are ...


3

Many answers found on the Internet (including those in TNW's comment) rely on /sys/bus/usb/devices/2-2/power/level or /sys/bus/usb/devices/2-2/power/control which are both deprecated since 2.6.something kernel. For newer kernels, the suggested procedure is to unbind and rebind its driver, which usually results in a power cycle: # Find out which driver to ...


2

In the good old times of ISA sound cards, it was not possible to create device nodes in /dev/ dynamically, so all devices had to be preallocated. This resulted in a limit of 8 sound cards, and the drivers were written with this limit in mind. Later, when devfs and USB were introduced, this limit was removed. However, the easiest way to do this was to make ...


2

The actual question consists of these two items: Can I use 256 colors in the console without fbterm/framebuffer ? Where does the 8 color limit in the console come from ? To the first: apparently not. All of the suggested approaches use fbterm. To the second: it comes from the terminal description (aka "terminfo entry"). For Linux console, with TERM set ...


2

I was invoking this make command from another makefile, which means I should export the variables in such case. The following post explains this topic in detail http://stackoverflow.com/questions/2826029/passing-additional-variables-from-command-line-to-make


2

If all Ubuntu 12.04 x86 have the same addresses, it is most probably because they all ship the same Linux build. If you use a modern version of GCC with optimizations enabled to compile your own kernel, it will randomize your addresses for each build. And in fact, this is not even necessary for recent kernels. Since this commit (January 2014), the address ...


1

I filter the output with awk, using the fact the pid 2 is the parent of all kernel threads: ps -fHuroot | awk '$3!=2' This prints only lines where the third field (PPID) is not 2.


1

This could be ganged-mode RAM operation (see here: http://www.tomshardware.com/forum/278881-30-what-ganged-unganged-mode). Check in your BIOS that the memory slots are properly detected and not ganged. dmidecode or dmidecode -t shows you how Fedora sees the RAM.


1

I don't know about A % but, You can set a time limit so it drops it after x amount of minutes. First in a terminal sync && echo 3 | sudo tee /proc/sys/vm/drop_caches To clear current caches. Make it a cron-job Press Alt-F2, type gksudo gedit /etc/crontab, Then Add this line near the bottom. */15 * * * * root sync && echo 3 ...


1

The message appears in case that certain process (in this case sftp-server) doesn't get CPU for 120s (default limit). This could be caused by high load on the system. Generally this could be caused waiting on any resource, most likely candidates are CPU, disk and network. When debugging such problems you can test writing speed on disk: $ dd if=/dev/zero ...


1

If your embedded device uses U-boot, the kernel image might be written on a particular partition on a NAND flash. See this! If this is the case i think you can locate the binary by looking at your U-boot source code if you have access to it. You can also check the environment variable for clues. This will vary greatly depending on your system so I can't ...



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