Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


its1louder last won the day on May 11 2015

its1louder had the most liked content!

About its1louder

  • Rank

Recent Profile Visitors

697 profile views
  1. Thank you Cardinal, You have confirmed what I guessed based on that notice on the generic page. You are saying that the only difference between the different subarches is the cpuflags, I wasn't sure if that was true or if there was something else beyond that. Like I thought atom was a more radically different CPU type from the pentium/core types. I guess I'm not sure what is meant to convey by the atom brand. In the end, I went ahead with generic gnome, because what I'm really trying to do is make my own personal binary metadistribution (including my overlay for some obscure stuff I n
  2. I've got an embedded machine with a 4 core atom CPU (C2758 @ 2.40GHz) that I've run reliably with silvermont subarch. I've not been able to upgrade from 1.3 to 1.4 without significant dependency issues. I want to convert an old laptop ( Core i5-3317U CPU @ 1.70GHz) to a development machine so I don't have significant downtime on the atom PC. The idea is I'll keep this old hardware around just for being a compile machine for bleeding edge packages that I'll then distribute out as a stage 4 tarball to upgrade and then continue upkeep with qpkg. I originally meant to just go with generic sub
  3. thanks for the tips. The last 5.x sysresc image is not too stale yet, but It is good to find a replacement now. I also found pentoo because I needed to steal a couple ebuilds from their overlay. Although it is a catalyst/gentoo based system I saw a symlink in the profiles list that was designed to point to either a *.gentoo or *.funtoo file, didn't investigate further.
  4. From Version 6, released Feb 2 2019, SysrescCD is based on Arch Linux. This doesn't necessarily mean we can't still use it as a liveCD or rescue cd in most cases, except I found a corner case where it doesn't work. I happen to run several systems with encrypted LVM as described here. I had the root volume on one system that needed an fsck journal repair. I tried to decrpyt it with the lastest sysresccd and found that the cryptsetup/lvm in the sysresccd 6.0.2 could not see my unencrypted volumes. I rebooted with the last gentoo based sysresccd, 5.3.2 from Nov 2018 and it worked no problem.
  5. OK I am still getting the hang of kits and funtoo style profiles. But wherever basic targets are set for the system I'd rather not override these in make.conf (why I reset the RUBY_TARGETS variable on the commandline). so looking at # ego query v ruby dev-lang/ruby| slot| repo --------------+-----+------------------- 2.2.9| 2.2| ruby-kit/1.1-prime --------------+-----+------------------- 2.3.5| 2.3| ruby-kit/1.1-prime * 2.3.6| | ruby-kit/1.1-prime --------------+-----+------------------- 2.4.2| 2.4| ruby-kit/1.1-prime
  6. yeah When I went to --depclean after @world it purged ruby 2.2, and I felt totally ok with only having two rubies. I suspect that what is going on is ruby 2.2 is in the process of being unsupported and it is taking time for that news to percolate through all the varies ruby library maintainers. In the short term the command line variable setting gets it done while leaving space for the ruby-kit or whatever is setting my RUBY_TARGETS to change in the near future.
  7. I had a similar problem this morning when I went to update @world. It seemed to complain that many many ruby libraries wanted racc and rdoc with ruby 2.2 targets, but couldn't have them. I couldn't get it to run without explicitly turning off ruby 2.2 support. I kind of felt like I could live with only two recent versions of ruby on my machine instead of 3, esp since I don't personally use ruby at all but clearly some dependency along the way does. So maybe some ebuilds upstream are phasing out ruby 2.2 support? prospero ~ # emerge -va racc rdoc These are the packages that would
  8. Works, thanks. As noted by palica, eix-sync works as well so that's nice. Is it a bug with epro that put the gentoo tag on the mix-ins? This is a new install on blank disk from stage 3. I did some of the mixin and installation stuff a little earlier than usual - normally would have booted into the system before installing x etc.
  9. here it is. I haven't edited it directly, but it was of course changed when I issued commands like epro mix-in +xfce so far I am still operating in the livecd chroot, haven't bootstrapped into the system yet. parent
  10. I'm doing my first funtoo install since all the big changes last summer. I'm trying to get up to speed chasing down all the right news and forum posts, but I am not clear on which tools that I've always used I should no longer use in favor of ego or epro. here is what I think I know: deprecated emerge --sync (use ego sync) eix-sync (use ego sync && eix-update) eselect profile (use epro) I'm not sure what to do if I want to use eix or equery. These are two tools I use alot when analyzing conflicts. Right now both seem to work, but
  11. I ran into this clusterblock also. I also run a stable system but mixin some unstables w/keyword file when necessary, and I have a few of my own ebuilds in a personal overlay for more arcane scientific software. I don't agree that this is doing it wrong but to each his own. Anyway, I got around the block with reference to this gentoo thread, only slightly tweaked (incr xorg server from r4 to r5). # from https://forums.gentoo.org/viewtopic-p-7833004.html =x11-base/xorg-server-1.16.4-r5 ~amd64 =app-eselect/eselect-opengl-1.3.1-r4 ~amd64 =x11-proto/glproto-1.4.17-r1 ~amd64 =media-libs/me
  12. Just did a eix-update and saw sys-boot/refind whiz by. So its in portage now. That's nice I guess, I've been downloading source manually and compiling it within root's home during the system bootstrapping.
  13. Actually I broke a rule, which is I changed two things at once and so I am not sure which fixed it. It might be the grub kernel command or it might be the udev rule I stuck in for usb devices to shut off autosuspend. Not sure which did it, and I am not sure why I only have this problem on my desktop and not my laptop. Off the top of my head, the laptop is running laptop_mode as an init process so maybe the autosuspending is better managed. Anyway its fixed so I am not going to investigate it further. But my original point to the post stands, which is that I am still not sure on the co
  14. Actually neither of these worked for me in the end I had to add usbcore.autosuspend=-1 to my grub launch line. Still it would be nice to know how to do it in /etc/conf.d/modules, and if this is even incorporated into the genkernel initramfs, perhaps not.
  15. The Documentation for /etc/conf.d/modules is a bit vague. On this page it says OK so at least one of the instances of the word "module" is not meant to be replaced with the name of the module. For example: I need to change usbcore kernel module to prevent my desktop's mouse from going to sleep every 2 seconds. I think what I need to do based on the linked page above is: BTW based on the comments on /etc/conf.d/modules itself I would have thought that it should be this: I am building initramfs files both ways just to be sure.
  • Create New...