Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Yesterday
  2. cardinal

    Use of unstable ebuilds

    Set up a local overlay. Copy from master branch net-kit to local overlay: net-mail/dovecot/dovecot-2.3.4.ebuild net-mail/dovecot/files Reference: https://github.com/funtoo/net-kit/tree/master/net-mail/dovecot
  3. zogg

    Funtoo release model

    From my understanding anyone that is so concerned about stability should not use current masks and use stable ones instead. Telling that waiting for release for 6 months in case you need to fix something on your system (don't tell me that if it says stable it will be 100% perfect and bug free, especially if it's done by 1.5 person). As an example I have some 32 bit software I can't use with 1.3 release as no proper workaround is ready now, so it forces me to have chroot with new system I need to maintain as well for this 32bit software or being stuck on 1.2 which is broken (Oleg words btw) and just left to die as is. Meaning I have no security updates and using old system or I can update to half working which I never be sure when will be finished (if at all). So I'm not sure about what stability and "I don't want to fight with my computer systems, I want to use them" he was referencing. So what we have now is that latest Ubuntu LTS (binary based one) already has newer packages (including system/core ones). I'm not even sure if all critical CVEs are fixed by anyone on Funtoo (telling me I can do it - means exactly "fighting with your computer" btw). So it seems that stability means — don't touch as it is working? :D I really do not understand why not utilize Gentoo ebuilds that are built by much bigger community and reinvent new concept that requires much more man power and maintenance while much less people are now involved in any of this on Funtoo side. I mean, sure kits are great idea, but why not just prepare automation that patches/breaks gentoo portage into kits first and grow maintainers and contributors power first, instead of making plans for perfect release in long distance future ( if Funtoo will survive at all till then.) P.S. Community ebuilds - much worse than rolling release, as no QA there and look at yaourt as an example on Arch - it is such a mess of duplicated and messed packages with broken dependencies. So I'm not sure how stable and ebuilds done by community members who need tutorials to do it comes along
  4. Is there any way to use not stable ebuild in funtoo? Ebuilds from master branches of a funtoo kits. For example I need >=dovecot-2.3.4 but a net-kit have only <dovecot-2.3.4. Is it possible to add all of master branch ebuilds to the portage for example with a masked flag in a system-way. And users if they need can unmask them and use for own risk. Or possible you can add a big button to site: "Ask developers to add a package". 🙂
  5. The problem has been reported: sys-kernel/debian-sources-lts-4.9.161_p1 tarball needs mirrored or bumped The user/password for forums.funtoo.org and bugs.funtoo.org should be the same.
  6. More_Piffle

    debian-sources-lts-4.9.161_p1 Failing emerge -auDN @world

    Not sure if some expect me to ask a question here, I am not. only trying to be as helpful as I can, worked fine the other night didn't this morning. I am an absolute linux N00b so if you catch me doing something dumb please tell me 🙂 Edit: possible question can I mask this and contiinue with my install ?
  7. Yeah I figured that I would have to manually edit grub.cfg. For some reason adding an entry to boot.conf didn't work. But I copied the entry for win7 from the grub.cfg that would boot Windows only, and added it to the one that would boot Funtoo only. Now I have dual boot working. Thank you all for your help.
  8. Please refer to man boot.conf add an entry to /etc/boot.conf such as "Windows 7" { type win7 params root=/dev/sda3 params += chainloader=+1 }
  9. The way I did was to generate the boot update first, copy the section of Funtoo menuentry and after that you do the grub-mkconfig and paste the Funtoo entry in the end of the cfg file generated by the grub-mkconfig. Seems that boot update does not execute os-prober like grub-mkconfig.
  10. Last week
  11. More_Piffle

    Funtoo release model

    Nuf said for me 🙂 I am here to break, and then learn how to fix things - dont mind me!
  12. debian-sources-lts-4.9.161_p1 Failing emerge -auDN @world getting a 404 not found - !!! Couldn't download 'linux_4.9.161-1.debian.tar.xz'. Aborting. * Fetch failed for 'sys-kernel/debian-sources-lts-4.9.161_p1', shell-init: error retrieving current directory: getcwd: cannot access parent di$ ^[[32;01m * ^[[39;49;00mlinux_4.9.161.orig.tar.xz SHA512 size 😉 ... $ >>> Downloading 'http://http.debian.net/debian/pool/main/l/linux/linux_4.9.161-$ --2019-04-23 02:50:24-- http://http.debian.net/debian/pool/main/l/linux/linux_$ Resolving http.debian.net... 128.31.0.62, 5.153.231.4, 149.20.4.15, ... Connecting to http.debian.net|128.31.0.62|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://cdn-fastly.deb.debian.org/debian/pool/main/l/linux/linux_4.9.1$ --2019-04-23 02:50:24-- http://cdn-fastly.deb.debian.org/debian/pool/main/l/li$ Resolving cdn-fastly.deb.debian.org... 151.101.24.204, 2a04:4e42:6::204 Connecting to cdn-fastly.deb.debian.org|151.101.24.204|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-04-23 02:50:24 ERROR 404: Not Found. !!! Couldn't download 'linux_4.9.161-1.debian.tar.xz'. Aborting. ^[[31;01m * ^[[39;49;00mFetch failed for 'sys-kernel/debian-sources-lts-4.9.161$ ^[[31;01m * ^[[39;49;00m '/var/tmp/portage/sys-kernel/debian-sources-lts-4.9.16$ Sorry for not knowing how to report this, can delete post 🙂 Cannot login to bugs.funtoo.org no account - I need to contact Jira admin??
  13. Background info: new install of Win7 and Funtoo on a laptop (HP Elitebook 8470p, core i7-3720, 16GB RAM, 500GB SSD). Partitioned as follows. The partition scheme is classic BIOS/MBR, not UEFI. /dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sda2 206848 747522047 747315200 356.4G 7 HPFS/NTFS/exFAT /dev/sda3 747522048 957237247 209715200 100G 83 Linux /dev/sda4 957237248 1000215215 42977968 20.5G 82 Linux swap / Solaris Win7 installed first, Funtoo second in the unpartitioned space that was divided into sda3 and sda4. No separate boot and home partitions. Used sysrescd 4.9.0 for the install. No problems until setting grub for dual boot. I do have os-prober installed. The same issue occurs with both grub-legacy and grub2. Installed grub on /dev/sda. I want to dual boot Funtoo and Win7 with Funtoo being the default, and a timeout of 10s. 1. Using either 'ego boot update' or just boot-update, a /boot/grub/grub.cfg is installed that allows me to boot Funtoo only, no entry for Windows. os-prober when run separately does find the Windows installation but apparently that doesn't get funneled into boot-update. Adding an entry for Windows in /etc/grub.d/40_custom with chainloading also gets ignored. With that I can boot Funtoo, but not WIndows 2. Using grub or grub2's 'grub-mkconfig -o /boot/grub/grub.cfg' results in a config that has entries for Funtoo and Win7 but only Windows can be booted from it. Attempting to boot Funtoo results in a kernel panic because sda3 cannot be mounted as root partition. I'm pasting below the two grub.cfg files; notice that the root partitions are defined differently in the files. I don't want to edit grub.cfg manually if I can help it. Any ideas appreciated. 1. grub.cfg generated by boot-update (boots Funtoo correctly but no entry for Windows) set timeout=10 if [ -s $prefix/grubenv ]; then load_env fi function savedefault { if [ -z "{boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos3) search --no-floppy --fs-uuid --set 38c0a8f9-0e12-462c-92f6-650e5748eba3 if loadfont /boot/grub/fonts/unicode.pf2; then set gfxmode=text insmod all_video terminal_output gfxterm fi set menu_color_normal=cyan/blue set menu_color_highlight=blue/cyan menuentry "Funtoo Linux genkernel - kernel-debian-sources-lts-x86_64-4.9.161_p1" { insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos3) search --no-floppy --fs-uuid --set 38c0a8f9-0e12-462c-92f6-650e5748eba3 linux /boot/kernel-debian-sources-lts-x86_64-4.9.161_p1 real_root=/dev/sda3 rootfstype=ext4 rand_id=L0AGZ8KL initrd /boot/early_ucode.cpio /boot/initramfs-debian-sources-lts-x86_64-4.9.161_p1 set gfxpayload=keep } menuentry "Funtoo Linux genkernel - kernel-debian-sources-lts-x86_64-4.9.130-2" { insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos3) search --no-floppy --fs-uuid --set 38c0a8f9-0e12-462c-92f6-650e5748eba3 linux /boot/kernel-debian-sources-lts-x86_64-4.9.130-2 real_root=/dev/sda3 rootfstype=ext4 rand_id=AFRCNQ3V initrd /boot/early_ucode.cpio /boot/initramfs-debian-sources-lts-x86_64-4.9.130-2 set gfxpayload=keep } if [ ! "${next_entry}" = "" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true elif [ ! "${saved_entry}" = "" ]; then set default="${saved_entry}" else set default=0 fi 2. grub.cfg generated by grub-mkconfig (boots windows but kernel panic on booting Funtoo because it can't mount /dev/sda3) # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_US insmod gettext fi terminal_output gfxterm if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-38c0a8f9-0e12-462c-92f6-650e5748eba3' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi echo 'Loading Linux x86_64-4.9.161_p1 ...' linux /boot/kernel-debian-sources-lts-x86_64-4.9.161_p1 root=/dev/sda3 ro echo 'Loading initial ramdisk ...' initrd /boot/early_ucode.cpio } submenu 'Advanced options for Gentoo GNU/Linux' $menuentry_id_option 'gnulinux-advanced-38c0a8f9-0e12-462c-92f6-650e5748eba3' { menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.9.161_p1' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.9.161_p1-advanced-38c0a8f9-0e12-462c-92f6-650e5748eba3' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi echo 'Loading Linux x86_64-4.9.161_p1 ...' linux /boot/kernel-debian-sources-lts-x86_64-4.9.161_p1 root=/dev/sda3 ro echo 'Loading initial ramdisk ...' initrd /boot/early_ucode.cpio } menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.9.161_p1 (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.9.161_p1-recovery-38c0a8f9-0e12-462c-92f6-650e5748eba3' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi echo 'Loading Linux x86_64-4.9.161_p1 ...' linux /boot/kernel-debian-sources-lts-x86_64-4.9.161_p1 root=/dev/sda3 ro single echo 'Loading initial ramdisk ...' initrd /boot/early_ucode.cpio } menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.9.130-2' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.9.130-2-advanced-38c0a8f9-0e12-462c-92f6-650e5748eba3' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi echo 'Loading Linux x86_64-4.9.130-2 ...' linux /boot/kernel-debian-sources-lts-x86_64-4.9.130-2 root=/dev/sda3 ro echo 'Loading initial ramdisk ...' initrd /boot/early_ucode.cpio } menuentry 'Gentoo GNU/Linux, with Linux x86_64-4.9.130-2 (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-x86_64-4.9.130-2-recovery-38c0a8f9-0e12-462c-92f6-650e5748eba3' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 38c0a8f9-0e12-462c-92f6-650e5748eba3 else search --no-floppy --fs-uuid --set=root 38c0a8f9-0e12-462c-92f6-650e5748eba3 fi echo 'Loading Linux x86_64-4.9.130-2 ...' linux /boot/kernel-debian-sources-lts-x86_64-4.9.130-2 root=/dev/sda3 ro single echo 'Loading initial ramdisk ...' initrd /boot/early_ucode.cpio } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows 7 (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-704278994278662E' { insmod part_msdos insmod ntfs set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 704278994278662E else search --no-floppy --fs-uuid --set=root 704278994278662E fi parttool ${root} hidden- chainloader +1 } ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. #menuentry "Win7" { # root (hd0,msdos1) # chainloader +1 # boot # } ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ###
  14. sputnik

    alternative to fchroot

    Not a criticism or to belittle Drobbins hard work, but I have been doing this for years with a simple bash script. If you haven't seen his video on fchroot on the forum here and don't know what it does search for fchroot. I simply keep 2 bash scripts in ROOT directory of any device I want to use it with, navigate to that directory (mounted via NFS) from the BIG BOY computer and run 1st one script to enter the QEMU chroot, the other to cleanup when exiting. Here's an example from my odroid C1+, armv7a: #MOUNTDIRS - script name mount -t proc none proc mount --rbind /sys sys mount --rbind /dev dev mount --bind /dev/pts dev/pts mount tmpfs -t tmpfs -o rw,nosuid,nodev,noexec dev/shm mount --bind /tmp tmp cp /etc/resolv.conf etc echo "" echo "don't use pump" echo 'env -i HOME=/root TERM=$TERM DISTCC_HOSTS="star,cpp,lzo joshua,cpp.lzo mrpink,cpp,lzo micah,cpp,lzo localhost" MAKEOPTS="-j8" chroot . /bin/bash -l' # UMOUNTDIRS - script name umount proc umount -l sys umount -l dev/pts umount -l tmp umount dev/shm umount -l dev umount tmp That's it! The 1st script echoes some reminders to me and the exact line to chroot in, I just copy & paste it (the script can't run that line directly). This is a particularly good example because I also set some environment variables on the way in, shows that. Of course you must set up your makefile as drobbins states, in my case: QEMU_SOFTMMU_TARGETS="i386 arm" QEMU_USER_TARGETS="i386 arm" And install qemu. Finally, you must run /etc/init.d/binfmt either in rc-update (bootup) or add starting/stopping it to the scripts. I find it mainly handy for things that overwhelm the whopping 1G ram on the odroid, it'll work but it's s...l...o...w. If at all possible it's much faster to use the cross-compile SYSROOT method, search on the web for "gentoo cross-compile", you'll find it. Unfortunately it doesn't work with many packages, particularly the intensive ones you'd like to use it on. One notable exception is LLVM. The odroid can't build it anymore as of a couple of years ago, but I found a trick to build it natively on the powerful machine and output a 32 bit arm package in minutes. Last time I used the qemu chroot method it was > 10 hours on a core2. Here are my notes: ****WARNING!!! DO NOT DO THIS, THERE IS A PROBLEM, READ BELOW**** # LLVM trick notes: # 1. you must have same version already installed on the compile machine # 2. in $SYSROOT/etc/portage/profile/use.mask, put a file that has this in it: abi_x86_64 llvm_targets_X86 # 3. you must have libffi installed: armv7a-hardfloat-linux-gnueabi-emerge libffi type: ABI_X86="" LLVM_TARGETS="BPF ARM" armv7a-hardfloat-linux-gnueabi-emerge -BO llvm:<version> probably just this now: LLVM_TARGETS="BPF ARM" armv7a-hardfloat-linux-gnueabi-emerge -BO llvm:<version> #5. Check out the package.env stuff for llvm, see llvm.conf ENJOY! # ${SYSROOT}/etc/portage/package.env sys-devel/llvm notmpfs.conf nodistccccache.conf llvm.conf # ${SYSROOT}/etc/portage/env/llvm.conf ABI_X86="" CMAKE_EXTRA_CACHE_FILE=/usr/armv7a-hardfloat-linux-gnueabi/etc/portage/env/cmake_cache_files/llvm.cmake # ${SYSROOT}/etc/portage/env/cmake_cache_files/llvm.cmake SET (CMAKE_INSTALL_LIBDIR "lib" CACHE STRING "" FORCE) SET (LIB_SUFFIX="" CACHE STRING "" FORCE) SET (LLVM_TARGETS_TO_BUILD "ARM;BPF" CACHE STRING "" FORCE) SET (LLVM_LIBDIR_SUFFIX "" CACHE STRING "" FORCE) SET (FFI_LIBRARY_DIR "/usr/armv7a-hardfloat-linux-gnueabi/usr/lib" CACHE STRING "" FORCE) SET (FFI_INCLUDE_DIR "/usr/armv7a-hardfloat-linux-gnueabi/usr/lib/libffi-3.2.1/include" CACHE STRING "" FORCE) THE PROBLEM: This indeed makes the package in arm-32 bit format, but later I found it is linked to lib64, non-existent on the arm. In my case, the odroid does just fine with it for my uses and I'm sure that can be remedied with CMAKE_OPTIONS, but since I have no problem I haven't worked on it. I skipped Funtoo 1.3 on the odroid, when 1.4 is released I'll update to that and get to the bottom of a solution on it. It makes a package which you can then install natively on the arm with emerge -K. Hmm, it's been so long, maybe I did fix that lib problem, maybe that's why it JUST WORKS®. I dunno...try it at your risk... I used to build my arm kernels with the SYSROOT method, but nowadays I find that pump distcc on the native device is just as fast and easier. Here's the basic script for doing such a thing, minus the dracut and mkimage operations: export SYSROOT=/usr/armv7a-hardfloat-linux-gnueabi armv7a-hardfloat-linux-gnueabi-emerge odroidc1-sources #custom amlogic kernel # cd usr/src/linux # ${SYSROOT}/usr/bin/xkmake menuconfig # cd ${SYSROOT} KERNEL_VERSION=-$(readlink ${SYSROOT}/usr/src/linux|cut -d'-' --complement -s -f1) cd ${SYSROOT}/usr/src/linux ${SYSROOT}/usr/bin/xkmake -j3 ${SYSROOT}/usr/bin/xkmake -j3 modules ${SYSROOT}/usr/bin/xkmake -j3 INSTALL_MOD_PATH="/mnt/nfs/odroid" modules install ${SYSROOT}/usr/bin/xkmake -j3 uImage cp ${SYSROOT}/usr/src/linux/arch/arm/boot/uImage /mnt/nfs/odroid/mnt/sdcard/storage/uImage.funtoo cp ${SYSROOT}/usr/src/linux/arch/arm/boot/dts/meson8b_odroidc.dtb /mnt/nfs/odroid/mnt/sdcard/storage/meson8b_odroidc.funtoo.dtb Just a rough guide there to show what can be done. The gentoo cross-compile info tells you to use xkmake rather than make when using the cross-compile ${SYSROOT} method. Here's my ${SYSROOT}/usr/bin xkmake file for the odroid: #!/bin/bash make ARCH="armv7a" CROSS_COMPILE="armv7a-hardfloat-linux-gnueabi-" INSTALL_MOD_PATH="${SYSROOT}" $* My 2 cents worth...
  15. Otakku

    Sddm does not recognize password

    I solve that issue reinstall "pam".
  16. tux

    Sddm does not recognize password

    Do you still have the issue ? I add it on a new Funtoo 1.3 install few days ago. I'm not sure exactly how I resolved it, I think by creating a /etc/X11/xorg.conf.d/10-keyboard.conf file... Section "InputClass" Identifier "keyboard-all" Driver "evdev" Option "XkbLayout" "fr,us" Option "XkbModel" "pc105" Option "XkbOptions" "grp:alt_shift_toggle" MatchIsKeyboard "on" EndSection
  17. Earlier
  18. hackbyte

    Outdated Desktop Environments

    I actually found that gentoo upstream ebuilds actually provide LxQt 0.14.1 including pcmanfm-qt and qterminal and stuff. Now, i actually need to find out how to/manage to get them together with my fresh built funtoo 1.3-kit. (Well, at least, having a funtoo within funtoo is sorta fun.. chroot ftw. ;)) P.s.: The linked git repo from shadow53 seems to be down sadly. 😞
  19. safulkin

    Outdated Desktop Environments

    This overlay for funtoo 1.2 updated up to Mate 1.20.4 Good choice for arm boards, all my asus tinkerboards with Mate DE 1.20 since august 2018. Next version Mate 1.22 (release month ago) in different new overlay for funtoo 1.3 and funtoo 1.2 https://github.com/safulkin/mate-122 Work in progress. few issues. Declared new features not tested (wayland, elogind)
  20. Fresh install of Funtoo I began getting Fetch Failed, 502 Bad Gateway and 404 Not Found errors emerging tcp-wrappers the first in the series of actually emerging KDE. After a fair amount of frustration \ research, I emerged mirrorselect and then ran mirrorselect -i -c usa Now everything is emerging with no errors. i hope this helps others. Enjoy, Scott A. Guthrie drazahoib
  21. I also getting the same error message in my funtoo container # docker run --rm -it alpine sh docker: Error response from daemon: unable to find "systemd" in controller set: unknown. @drobbins, if you could fix it it would be great. Also it would good to know the cause and the fix for this issue.
  22. hackbyte

    Outdated Desktop Environments

    I'm happy to see that there is at least some base to start from. I actually have a problem with pcmanfm-qt 0.13.0 not remembering that i always want to see all (including hidden) files and just got slapped over there that 0.13.0 is outdated (for today there is 0.14.1 already). So i cannot promise anything at all but will right now go and find out how to get lxtq-base/* and x11-base/pcmanfm-qt up to the newer versions. Thanx for your work! And don't feel bad, we all have some sort of real life. 😉 Hacky P.s.: Sorry for full-quote, i don't know how to cut it down properly right now.. 😉
  23. mlinuxgada

    Funtoo release model

    @lazlo.vii You know, it will be much better if you at least try to be polite, right? @drobbins Back to the topic - if you want to get more and more involved into funtoo dev - isnt it better to have current/dev branch? If you want devs, isnt it a must to have at least dev branch,where they can work with ?! I mean, some of the major distros release based models have that : - Debian has unstable/sid -> testing ... -> stable release major/minor releases - FreeBSD has current -> release -> .. stable I still don't get it with removing current branch. Do releases, implement whatever process you think its best for you. But keep the current. Or, explain how it can be done.
  24. Also, the 3 kernel config warnings you see on emerge don't appear to be problematic. I think they can be safely ignored.
  25. Just for everyone else, I resolved this for @skygunner -- If you ever have an issue running docker in your container, just let me know and I'll take care of it.
  26. drobbins

    Funtoo release model

    Hey I just want to jump in and say it's OK, I understand if there are some people that are disappointed about us not having pure rolling releases anymore. It's fine to express your opinions here. I think that's totally understandable, frankly. Now yes, these changes were totally needed and like I said earlier, there is a strategy that is being very successful so far even though it's in its early stages. The strategy is that I support our users (with things like YouTube videos, code.funtoo.org, fchroot) to be contributors to Funtoo. So yes, right now I think it's fair to say we are playing a bit of catch-up with Oleg moving on to other things -- BUT, considering we just started this effort, I also think it's fair to say that in time we will likely catch up and even go beyond what we were capable of before. And that means that we can push ahead more with many more updates and possibly even a more up-to-date release (betas?) or a true rolling release again. In the mean time, I ask @lazlo.vii and others to be supportive of those expressing disappointment since I want people to have a place to vent their disappointment -- I don't see it being overboard or in poor taste at all -- and in my experience, the worst thing for a community is if any disappointment is bottled up and never expressed (and then we need to guess why people are unhappy) so I would much rather have people share how they feel. As long as they understand the reason for the decision, it's fine to share feedback and vent a bit.
  27. lazlo.vii

    Funtoo release model

    It seems as though you two do not understand that isn't something the our BDFL just decided to do. There are important reasons for this change. Don't take it personally that change has come you favorite distro. Complaining about the changes is bad for our signal to noise ratio and confuses the issue. Everything changes. If you can work hard enough maybe you can change it back. Again, there are important reason for this change. The biggest reason is that the one person that was maintaining the vast majority of Funtoo ebuilds is no longer doing it. If either of you can take his place go for it. Otherwise if we going to get updated packages between upstream snapshots it's going to take a few people doing a lot or a lot of people doing a little. If you two have any better ideas about how to keep Funtoo running smoothly then please share your plans with us.
  28. mlinuxgada

    Funtoo release model

    About doing smth, well, some do, me included. Small, but here and there. The question is more about the direction things are going. We all know release model is much easier than rolling distro. One of the reasons I jumped on Gentoo/long time ago/ then on Funtoo is the rolling model. Some of the others are that its source based, slots, alot of customisation/flags ... etc. My point is - today you decide to switch from rolling to release, eg no current, just freezed releases. Tomorrow nothing stops you from source based to package/bin oriented ? Maybe Debian clone /one of dozens/ ? Dont get me wrong. I use funtoo not geeky weekends, where I can spend whole day install/reinstall/fiddle with this or that. My workstation is build on Funtoo. My work depends on Funtoo. If some1 decides to flip a coin and make a decision, when I am not sure about the general direction ... I can install a Debian/Manjaro in minutes, but I dont want to. I want Funtoo as it was for years - just to have current.
  1. Load more activity
×