Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

666threesixes666

Members
  • Posts

    132
  • Joined

  • Last visited

  • Days Won

    16

666threesixes666 last won the day on July 3 2015

666threesixes666 had the most liked content!

1 Follower

Personal

  • Interests
    https://www.youtube.com/watch?v=e-IWRmpefzE

Recent Profile Visitors

2,861 profile views

666threesixes666's Achievements

  1. i also love funtoo... everything is very well thought out.
  2. i agree about gnu being pushy about what distros are gnu approved. they should work on excellent software instead of gripe... if you don't like a package, make a sweet alternative that's better than the original =)
  3. not sure... here are some articles about it though =) https://lwn.net/Articles/580194/ http://www.phoronix.com/scan.php?page=news_item&px=KDBUS-Perf-Linus-Comments
  4. sorry ive been gone so long. my dad had medical problems, so i was gone for that... sister flew in from maui, so more away time. ill be back shortly. -tripsix
  5. kdbus is for systemd... its a kernel space dbus implementation instead of pure userspace. =)
  6. do you use gdm, kdm, lightdm, slim, or xdm?? when i have slim or lightdm load my session up .bash_profile is never sourced.... try putting those entries at the bottom of .bashrc if you're running those.
  7. a good ole startx will unlock the gnome keyring. not so much with lightdm or slim. the pam module for gnome keyring is installed but its never called from the pam configs for lightdm or slim. it seems like this is a shortcoming from pam not recognizing that the DM is pretty much a login. where do i start? i guess i don't? its working now? or not... maybe this is a google chrome specific issue. chrome repeatedly is asking for keyring passwords.
  8. this tv setup is screwy. somethings not happening correctly. dmesg chunk [233070.695477] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 131 [233070.695483] Raw EDID: [233070.695487] 00 ff ff ff ff ff ff 00 05 b2 04 10 01 01 01 01 [233070.695490] 09 1f ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695493] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695495] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695497] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695499] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695502] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.695504] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [233070.696538] nouveau E[ DRM] DDC responded, but no EDID for DVI-I-1 this is orbiting around xrandr trying to get the tv settings and getting incorrect or incomplete information. i tried having xfce4 configure new monitors as they come along plug & unplug but that's also failing. xrandr --verbose -q --display :0 between when the tv is working and not only differ in working having *current.... there are a few very messy ways to fix this that are heavy handed. for now, when the tv goes off ill ctrl + alt + f1 turn tv on, then ctrl + alt + f8 or f7 to go back to X.... (yeah this really works) ill try out lightdm to see if my .xinitrc is terrible.
  9. m. subdomain is an outdated technique to deal with mobile websites. use bootstrap unsemantic foundation or another mobile css framework.
  10. my custom kernels are about 1/5th the size of debian, but they also miss little details like console speaker modules. ill look over the kernel docs, and roll a vanilla kernel tonight. you need your file system, sata controller compiled in to boot with out initrd images. ok 1st the kernel is the drivers. its basically all the drivers a system could want, and some programs like iptables (firewalling) drbd (raid 0 over lan) etc.... when you update the kernel it generates a new bzImage file with the kernel version, if its the same version it will append .old to the kernel. the system boots, does post, then bios/efi then bootloader loads linux, linux loads its self and friends, starts openrc. or something CLOSE to that.... it might be boot loader hands off to openrc then spawns kernel. the file system and hard drive ide or sata controller which contains the linux are important drivers to find. everything else you copy your old kernel config to the new kernel you're going to compile then add in whichever driver is required to run whatever you're trying to run.
  11. i think you generate entropy on the host then import it to the vm. other tips ive seen are to generate the crypto data then import the data to the vm/server in the wild. i've tinkered with fortuna and csprng https://code.google.com/p/csrng/ i haven't posted this info to the wiki because im not done and haven't tested it under useful conditions. which vm software are you using?
  12. funtoo is more stable than gentoo, it ships with kernels prebuilt for your arch out of the box so the install is partition, unwrap stage3, bootloader setup go.... funtoo's lead dev is the original author of portage.
  13. bottom left, expand the wiki.... http://www.funtoo.org/Welcome your login info is the same as forums and bugs thanks for updating the documentation, i dont have a machine in the wild to test stuff of this sort against and i wrote a bunch of the web stuff.
  14. yeah, i dont think you'll see any support on the bug tracker though... we don't have a huge dev team to address issues of these sorts. i started contributing systemd documentation before ANYONE was aware of it. i started the whole 2 year long thread on the subject of boot speed. people of linbit got me started on systemd, and broke at least 3 of my systems in the process. i just recently learned how to start deving from local overlay documentation in the funtoo dev guide. i think the major point is that as default were sticking to our openrc guns which are very straight forward bash scripts. systemd support within funtoo specific ebuilds is probably problematic. i think i was running monit as pid 1 for a while. openrc is getting features of process monitoring and mail notification of failure if it doesn't have it already... i was using openrc to init zero to xorg as quickly as possible and monit to start up other services on the side and restart if they were crashed.
  15. yeah, its not the ebuild passenger.... its a use flag that pulls in tengine specific passenger. "Your compiler failed with the exit status 4. This probably means that it ran out of memory." i was having problems with this message until i updated world..... so add that line to make.conf if you haven't already, update world, then try emerge -av tengine again =)
×
×
  • Create New...