Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


cafaia last won the day on October 28 2017

cafaia had the most liked content!

About cafaia

  • Rank
    Advanced Member

Recent Profile Visitors

989 profile views
  1. Hi, Walterw! I removed the 'ro' option but the error is still there. I'm sending my initramfs, I hope you can help me. Best regards. Here is the link to the initramfs file: https://mega.nz/#!ZYNVGKBQ!hryGEXRWUmIkiTcyNOyP4VwuAxerNMNTY61LgQopl4w
  2. Hi, Walterw! I did not modify my initramfs, I created it with the genkernel command. And I have this in my grub.cfg file: linux /vmlinuz-4.15.17-1 root=/dev/mapper/swsyho-system ro domdadm dolvm rootfstype=ext4 scandelay resume=/dev/mapper/swsyho-swap initrd /initramfs-genkernel-x86_64-4.15.17-1 Best regards!
  3. Hi, Walterw! Thank you for your attention and tip! I made three changes, with scandelay, no scandelay and with this spelling 'scandelay=3', but the 'sh: bad number' continues... Best regards!
  4. Hi, Palica! Thank you for your attention and for the tip! I have this message about three lines before starting openrc, in the boot process before openrc starts. My fstab: /dev/md1 /boot ext2 defaults,noatime 1 2 /dev/mapper/swsyho-swap none swap sw 0 0 /dev/mapper/swsyho-system / ext4 noatime 0 1 /dev/mapper/swsyho-home /home
  5. Hello, everyone! In all installations made of Funtoo, I have this message: Using mount -t ext4 -o ro sh: bad number This message always appears before starting the openrc program. I believe it is harmless, but someone would know how to fix it? I thank you in advance for your help!
  6. Hi, Mauricev! I'm glad to hear that you found the mistake. Best regards!
  7. Hi, Mauricev! After you create the local repository, did you do that: # ebuild /var/git/overlay/local-overlay/cat/pkg/autossh-version.ebuild digest I hope this is what is missing. Best regards!
  8. Hi, Donjames! I believe that is what you are looking for: I hope I've helped! Best regards!
  9. Hi, Biocyberman! Did you add this repository with layman? If so, you can use eix, look: https://www.funtoo.org/Package:Eix If not, you can use the file '/etc/portage/repos.conf/myoverlay.conf', look: https://www.funtoo.org/Local_Overlay , you should look at the variable 'auto-sync'. Hope this helps! Best regards!
  10. Hi, Safulkin! There is already an open bug about it ( https://bugs.funtoo.org/browse/FL-5127 ), if you want you can start seeing this bug. Best regards!
  11. Hi, Belenar! Ops, the thing is complicated then, because you do not have the current version of ego and the gitmodules file has been removed, look: https://github.com/funtoo/meta-repo/commit/85a413af847d9b0fd9e73b7f7a601a4101dd7e05#diff-8903239df476d7401cf9e76af0252622 Then you should do this to have a functional repository: # install -d /var/git # cd /var/git # git clone https://github.com/funtoo/meta-repo.git # cd meta-repo # wget https://raw.githubusercontent.com/funtoo/meta-repo/aadee00606e39b63cb0f21b48a7780dc5bc33b08/.gitmodules # git submodule init # cd kits # git clone ht
  12. Hi, Belenar! I believe the page https://github.com/funtoo/meta-repo information is outdated, I advise you to use the instructions here: Downloading the Portage tree Now it's time to install a copy of the Portage repository, which contains package scripts (ebuilds) that tell portage how to build and install thousands of different software packages. To create the Portage repository, simply run ego sync from within the chroot. This will automatically clone the portage tree from GitHub and all kit submodules: (chroot) # ego sync from https://www.funtoo.org/Install#Downloading_the_Port
  13. Hi, Delyas! Unfortunately I can not help with these two problems in specific, but the language problem I registered two bugs ( https://bugs.funtoo.org/browse/FL-5084 https://bugs.funtoo.org/browse/FL-5037 ), if you can help me by talking about your problem, I thank you. With best regards!
  14. Hi, dear Silvio! Well, now who does not know, it's me. Unfortunately I give up... I suggest you do a new installation of Funtoo, in the face of all this seems to be the most correct thing to do. Big hug, Eduardo
  15. Hi, Silvio! Yes, the "emerge grub" command should be with chroot and if you get error while running the "boot-update" command you should do this "emerge boot-update" and follow these steps: https://www.funtoo.org/Package:Boot-Update Big hug, Eduardo
  • Create New...