Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

lego12239

Members
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by lego12239

  1. Look, to boot to your clean(base) funtoo system you don't need to do chroot or emerge/ego. Just: - make partition - make fs - mount this partition - unpack stage3 (cd /mnt; unxz -c ~/stage3-intel64-nehalem-1.4-release-std-2020-09-07.tar.xz | tar -x --numeric-owner --xattrs --xattrs-include='*' --acls ) - clear root passwd (delete "x" in /mnt/etc/passwd) - install boot loader: - without EFI: grub-install --target=i386-pc --boot-directory=/mnt/boot/ /dev/sdc - with EFI: mkdir /mnt/boot/efi; mount /dev/sdc2 /mnt/boot/efi; grub-install --target=x86_64-efi --boot-directory=/mnt/boot/ --efi-directory=/mnt/boot/efi --removable - write a simple /mnt/boot/grub/grub.cfg, like: set timeout=2 menuentry 'Funtoo' { insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos3)' echo 'Loading kernel...' linux /boot/kernel-debian-sources-x86_64-4.8.15-1 root=/dev/sda3 ro echo 'Loading initial ramdisk...' initrd /boot/initramfs-debian-sources-x86_64-4.8.15-1 } - umount /mnt/boot/efi; umount /mnt; - reboot to fresh OS - login as root - set new passwod for root with passwd program - ego sync; epro mix-ins no-systemd; emerge -auND @world - etc The goal of these steps are to minimize actions in the installation environment and do most of them in the fresh Funtoo instance(this is simpler).
  2. Try to specify a path to boot dir with --boot-directory option. Like this: grub-install --target=i386-pc --no-floppy --boot-directory=/mnt/funtoo/boot/ /dev/sda
  3. Hm. It's strange. I installed musescore about a year ago too with emerge command. There was an ebuild for it. What happened with it now?
  4. I think yes. But this was a year ago. I need several days to find a server where i installed nginx with these changes.
  5. ? Daniel, i have only 2 kids and no free time at all. I want to send a few patches for funtoo network scripts infrastructure duringabout several month, but I stupidly do not have enough time for this :-D. How do you manage all this :-D?
  6. IIUC, if you get a power failure, then all new data will be lost, isn't it(or you mount /home from ssd/hdd?)? If your workflow consist of running several programs, then after first run every program should start fast in any case, due to fs blocks cache. Thus, how this speeds are differ(program second start from ssd/hdd and from tmpfs)?
  7. Even after reading this, I still wonder why gentoo chose such a weird way of solving this problem :-D.
  8. Hi. Your installed OS from stage3-2021-04-21 and want to update OS, right?
  9. Hi. It seems that this is not ego problem. May be some firewall or proxy? What curl -v -X HEAD https://github.com/funtoo/meta-repo is show?
  10. Yeah. But i have no permission to do this :-).
  11. Hi. Sorry for a late reply - just saw your post. Try to change LLVM_MAX_SLOT to 11 in the ebuild. Or simply use kit from https://github.com/lego12239/firefox-kit
  12. Hi, all. How to tell "ego sync" to update my kit? When i set auto-sync to yes nothing is happened.
  13. Wow. Didn't know about this :-D. I always use /boot/... in grub.cfg .
  14. What does it mean? What error message or what behaviour do you see? Do you really have kernel and initramfs in the fs root(instead of /boot)?
  15. Unpack funtoo stage3, remove kernel with all kernel modules and pack it again. And you will get as small stage3 as gentoo has :-D.
  16. May be we can remove firefox*.sh files, but there is wayland support, IIUC. I don't use wayland, thus i just stayed they intact.
  17. Hi, all. firefox kit with ESR version: https://github.com/lego12239/firefox-kit
  18. Another one issue may be. In src_install() we have But we specify EPREFIX in src_configure() for "configure --prefix". IIUC, in this case we should use $D with emake.
  19. Found answer here - https://www.funtoo.org/Portage_Variables : The same for EROOT.
  20. I use custom scripts: https://bugs.funtoo.org/browse/FL-6305
  21. Add the next line into a config(.schism/config) in the [Audio] section: driver=alsa:default or use the command line option: -a alsa:default
×
×
  • Create New...