• Can't install big programs with yaourt


    I installed my Antergos on a 20GB root partition, which I later increased with GParted. Some folders on / were not increased in size. So /dev, /proc, /sys, /tmp and /run just have 4GB of free space left. The other folders have 180GB of free space left. I want to install Matlab and Altera, which are huge applications. How can I change this??

  • Could you please run:

    sudo fdisk -l && cat /etc/fstab

    And Paste the outcome here?

    I make things work…
    My humble wiki: https://anotherlinux.com/

  • Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 707E3662-4870-4E11-9651-BD880E08514B
    Device          Start        End    Sectors   Size Type
    /dev/sda1        2048    2050047    2048000  1000M Windows recovery environment
    /dev/sda2     2050048    2582527     532480   260M EFI System
    /dev/sda3     2582528    4630527    2048000  1000M Lenovo boot partition
    /dev/sda4     4630528    4892671     262144   128M Microsoft reserved
    /dev/sda5     4892672 1260810239 1255917568 598.9G Microsoft basic data
    /dev/sda6  1875210240 1927639039   52428800    25G Microsoft basic data
    /dev/sda7  1927639040 1953523711   25884672  12.4G Windows recovery environment
    /dev/sda8  1260810240 1340053503   79243264  37.8G Linux filesystem
    /dev/sda9  1340053504 1859586047  519532544 247.8G Linux filesystem
    /dev/sda10 1859586048 1875210239   15624192   7.5G Linux swap
    Partition table entries are not in disk order.
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    UUID=B6B8-6F3F /boot/efi vfat defaults,relatime 0 0
    UUID=8625371f-7109-4e5d-b5aa-db2fd6b5001e / ext4 defaults,relatime,data=ordered 0 1

    sda9 is my root partition sda8 is the old Mint installation

  • I read that it is defined by the RAM size, so that is the problem.


  • I will have a look as soon as I get home, but this information might give a clue đź‘Ť

    I make things work…
    My humble wiki: https://anotherlinux.com/

  • This is from the ubuntu wiki, but should still give you an idea what dir do what. Your / drive is more than big enough, you should have no problems.

    Main directories
    The standard Ubuntu directory structure mostly follows the Filesystem Hierarchy Standard, which can be referred to for more detailed information.

    Here, only the most important directories in the system will be presented.

    /bin is a place for most commonly used terminal commands, like ls, mount, rm, etc.

    /boot contains files needed to start up the system, including the Linux kernel, a RAM disk image and bootloader configuration files.

    /dev contains all device files, which are not regular files but instead refer to various hardware devices on the system, including hard drives.

    /etc contains system-global configuration files, which affect the system’s behavior for all users.

    /home home sweet home, this is the place for users’ home directories.

    /lib contains very important dynamic libraries and kernel modules

    /media is intended as a mount point for external devices, such as hard drives or removable media (floppies, CDs, DVDs).

    /mnt is also a place for mount points, but dedicated specifically to “temporarily mounted” devices, such as network filesystems.

    /opt can be used to store additional software for your system, which is not handled by the package manager.

    /proc is a virtual filesystem that provides a mechanism for kernel to send information to processes.

    /root is the superuser’s home directory, not in /home/ to allow for booting the system even if /home/ is not available.

    /run is a tmpfs (temporary file system) available early in the boot process where ephemeral run-time data is stored. Files under this directory are removed or truncated at the beginning of the boot process.
    (It deprecates various legacy locations such as /var/run, /var/lock, /lib/init/rw in otherwise non-ephemeral directory trees as well as /dev/.* and /dev/shm which are not device files.)

    /sbin contains important administrative commands that should generally only be employed by the superuser.

    /srv can contain data directories of services such as HTTP (/srv/www/) or FTP.

    /sys is a virtual filesystem that can be accessed to set or obtain information about the kernel’s view of the system.

    /tmp is a place for temporary files used by applications.

    /usr contains the majority of user utilities and applications, and partly replicates the root directory structure, containing for instance, among others, /usr/bin/ and /usr/lib.

    /var is dedicated to variable data, such as logs, databases, websites, and temporary spool (e-mail etc.) files that persist from one boot to the next. A notable directory it contains is /var/log where system log files are kept.

    I make things work…
    My humble wiki: https://anotherlinux.com/

  • The problem was that the application was too big to build it in tmp, since it uses the RAM. I tried to increase my swap, but even that didn’t work, because my system would freeze. Then I figured out that you can just change the build directory in /etc/yaourtrc :laughing: Building on the HDD now, but at least it works…

  • Good going, I learned something new as well ;).

    I make things work…
    My humble wiki: https://anotherlinux.com/

size3 programs6 increasing1 Posts 8Views 136
Log in to reply