• File manager that ignores kcore
    10 replies, posted
I have Nautilus and whenever I try and download files it says I have not enough space. It views my kcore file as 131GB. This is on arch linux. Does anyone know a file manager that doesn't fuck up?
Try Worker or Gentoo file manager.
They work better, but they don't view my network files. I am trying to copy a bunch of shit on a computer connected to my linux computer.
Maybe pcmanfm will work then?
Your /proc/kcore, as well as everything else in /proc, is a virtual file that doesn't actually take up any disk space, and it's not the basis for Nautilus saying you don't have enough disk space. Nautilus tells you, in the statusbar at the bottom of each of its windows, how much free space is available in the folder you're viewing. How much space do you actually have free in the folder where you're trying to download the files?
When I tell Nautilus to look at the size of kcore it says it is 131GB. Anyways, yeah it says I do not have much space in that folder. I have an assload of free space just lying around, so how might I increase the folder's space?
Nautilus is right, your kcore file really is 131GB, but its contents aren't stored on disk. It's a live view of your computer's physical RAM, followed by a large virtual address space that's used by the kernel's memory manager. The amount of free space in a folder is actually the amount of free space in the filesystem that contains the folder. Filesystems generally correspond to disk partitions, though not always. (/proc is an example of one that doesn't.) It sounds like you have one partition with lots of free space, and another partition that's getting full.
Haha, wow. I mounted root on the partition I meant for /boot and vice versa. Am I totally fucked and have to reinstall everything or is there some magical workaround I can do? [editline]06:46PM[/editline] Can I just backup everything onto my external, redo the partition mounting so that they are mounted in the right spots, then just copy all the old files over the new ones?
You might be able to make /usr, /bin, and /var use a different partition, that will save a bit of space.
If you mean that you installed your OS on the small partition that you'd meant for the kernel and boot files, and installed the kernel and boot files on the large partition that you'd meant for the OS, that's possible to fix, but you may find it easier to just reinstall. The process would be something like: [list] [*]Boot a liveCD and mount both partitions. [*]Move the kernel and bootloader files from the large partition into the /boot directory of the small partition. [*]Now that the large partition is empty, move everything from the small partition into it. [*]Now that the small partition is empty, move the files from the large partiton's /boot directory into it. [*]Update fstab and reinstall GRUB. [/list] If your /boot partition is big enough to hold a whole OS install, it's probably much larger than it needs to be. 100MB is plenty for two or three kernels.
I keep /boot at 60 MB because 60 MB is where it's at.
Sorry, you need to Log In to post a reply to this thread.