Problem of installation Ruby through RVM on Raspberry Pi



  • I'm trying to fix ruby through rvm. I got a rvm.

    pi@raspberrypi:~ $ rvm -v
    rvm 1.26.11 (latest) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]
    

    I'm making ruby now, making a mistake.

    pi@raspberrypi:~ $ rvm install ruby
    Searching for binary rubies, this might take some time.
    No binary rubies available for: debian/8/armhf/ruby-2.2.1.
    Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
    Not enough space (297MB) to install ruby (440MB).
    

    Disk space is enough. What's my problem?

    UPDATE:

    Team mount:

    pi@raspberrypi:~ $ mount
    /dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)
    devtmpfs on /dev type devtmpfs (rw,relatime,size=469748k,nr_inodes=117437,mode=755)
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
    tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
    tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-    cgroups-agent,name=systemd)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    configfs on /sys/kernel/config type configfs (rw,relatime)
    /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
    

    Team df-h:

    pi@raspberrypi:~ $ df -h
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/root       1.3G  882M  310M  75% /
    devtmpfs        459M     0  459M   0% /dev
    tmpfs           463M     0  463M   0% /dev/shm
    tmpfs           463M  6.2M  457M   2% /run
    tmpfs           5.0M  4.0K  5.0M   1% /run/lock
    tmpfs           463M     0  463M   0% /sys/fs/cgroup
    /dev/mmcblk0p1   60M   20M   41M  34% /boot
    

    Team lsblk:

    pi@raspberrypi:~ $ lsblk
    NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    mmcblk0     179:0    0   15G  0 disk
    ├─mmcblk0p1 179:1    0   60M  0 part /boot
    └─mmcblk0p2 179:2    0  1.3G  0 part /
    


  • To be honest, you really don't have enough room:

    The question has nothing to do with the Rails or Ruby, and it has very little connection to the linux. It relates to the features of an operating system installation on Raspberry Pi.

    The main way in the community is to shed with help. dd (and analogs) a SD card image, blind. But you have to understand that licking the image is going to write as much byte as it looks. Therefore, the sum of the card, if not done, will be cut to the size of the image. In doing so, the table of sections and the contents of the sections themselves are written on the card, including the Free Place♪ Yes, a free disk is included in the sample! That's why the image is usually squeezed before the publication so that this "free place" doesn't have to be downloaded.

    Exhaust lsblk It can be seen that there are 15 gigabytes on the card and only 1.3 gigabytes (ruth) and 60 megabytes (loader). And the exhaust. df -h You see, there's only 310 megabytes left on the rudder.

    Take any section editors. gparted) and Extend the main section (which 1.3 Gb) to the edge of the card




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2