**** BEGIN LOGGING AT Fri Sep 08 03:00:00 2017 Sep 08 09:50:40 Enrico_Menotti: DocScrutinizer05: I find the ncdu program useful for determining why a file system volume is full and deleting unnecessary files to free space. If you have a GUI (X Window System), programs such as WinDirStat that use a (squarified) tree map to visually represent how space is used in a file system are useful too. Yes, WinDirStat is a Windows program but similar programs are available for *nix (GNU+Linux). **** BEGIN LOGGING AT Fri Sep 08 10:56:16 2017 Sep 08 12:08:54 I gotta say jdiskreport is neat if you got java installed, I prefer it over windirstat Sep 08 12:09:00 especially since it's multi-platform Sep 08 13:22:51 hi Sep 08 19:20:42 I'm going to ask a few questions about kernel building, in particular building a single kernel module (a new module to be added to the system). It's a bit off-topic at the beginning, but since my aim is to see whether I may add a couple of modules to the Maemo kernel, maybe it's not that wrong to ask here. Sep 08 19:22:59 First a general question about building the kernel: when I did that for Devuan, I learnt that the first thing to do is to call make against a "pre-cooked" config file, like make rx51-defconfig. Then one may simply invoke make to build kernel (+ modules), or call make against menuconfig, for tweaking the configuration, before actually building the kernel. Sep 08 19:26:44 Now I was trying to prepare a configuration from scratch. For that, I invoked make menuconfig as first command, and saved the configuration to a file named ".config". Then I tried make, which didn't work, or make .menuconfig, which didn't work either. By googling a bit, I have found that I have to call make oldconfig and make prepare before making the kernel. That led further, but I had other errors about some Sep 08 19:26:44 scripts, so I searched further and found I have also to call make scripts. I have seen around also a make modules_prepare, which however I didn't use. Sep 08 19:28:29 Al this allows a build (really I didn't build the whole kernel, I tried with a single subdirectory, containing sources of a driver.) But I have to admit that I don't understand the various steps I had to take. If anybody could explain or point to an explanation, I'd be happy. Sep 08 19:39:09 Now my real point is how to build a single kernel module (without having previously built the kernel). Seems this may be done by cd'ing to the module directory and invoking make -C $(KERNEL_SRC) V=0 M=$$PWD, where KERNEL_SRC has been defined as /lib/modules/$(shell uname -r)/build. I'm on Devuan on an x86 machine, so KERNEL_SRC really is /lib/modules/3.16.0-4-686-pae/build. Sep 08 19:40:00 If I got it correctly, I could as well cd to KERNEL_SRC and invoke make V=0 M=. Is this correct? Sep 08 19:42:12 Also, I don't know what V=0 is. But will investigate about that. In any case, my main question is: what is there in the KERNEL_SRC directory? I didn't install any kernel sources, but I find there some directories which remind me of (some of) the directories which are found in the kernel source tree. Sep 08 19:44:28 Last thing: this would produce a module for the running system. What if I want to build a module for a different kernel (specifically, Maemo kernel)? Is it enough to substitute for KERNEL_SRC the path to the kernel source directory? Do I need to invoke some make before building the module? Sep 08 19:45:28 Thanks in advance for any answer. Sep 08 23:55:51 hola que tal? Sep 08 23:56:06 alguien para una duda? **** ENDING LOGGING AT Sat Sep 09 03:00:00 2017