On Wed, Apr 26, 2017 at 6:04 AM, Duncan <1i5t5.dun...@cox.net> wrote: > > Mark Knecht posted on Tue, 25 Apr 2017 10:43:29 -0700 as excerpted: > > > 3) Respectfully, I'm not sure your answer encompasses the problems and > > frustrations of having to maintain OTHER people's computers. I don't > > hear you speak of that very often. The problem with KDE is on my wife's > > computer. When it's building KDE it's unavailable to her. In the past 2 > > weeks I've had two massive builds that each took about 24 hours. That > > amounts to about 15% downtime on her machine, > > What I'm trying to say, tho, is that if you set it up right, you'll only > be building once, for your machine, or at least /on/ your machine if it's > a package you don't yourself use, and will then be using already built > binpkgs on her machine. > > So effectively it's like using a binary distro on everything except your > build machine, only the binary distro will be customized with your chosen > gentoo profile, USE flags, etc. > > IOW, bigger picture, the gentoo as metadistro idea, with you effectively > creating the customized binary distro out of it with the build on your > machine, that you then install on your wife's machine, and however many > more you have around that you maintain or help maintain. > > Now depending on how similar the machines and layouts are, you may still > end up building a /few/ packages individually for each or at least some > of the machines, but if you choose your battles (packages) well, it'll be > perhaps 10% of them, and "big" packages like gcc, firefox or chromium, > etc, will only be built once. Tho if you have say kde on some and xfce > on others, you might be building one or the other of them for perhaps one > machine only, and certainly, kde at least is big, but still, if you're > building for say 10 machines and a few packages are only used on one or > two, with another few that you have to rebuild custom for each one, you > might be building in total say 120% or 150% or even 200% of what you'd > build for a single machine, but that's still way better than the 1000% > (100% * 10) that you'd be building if you did each one individually. > > And while not /exacty/ the same as you'd get with all individual builds > (the 1000%), it'd still be way closer to fully customized individual > builds then the generic target mass distribution build you'd get using a > normal binary distro. > > Meanwhile, the per-machine update and admin time, for other than that > first build machine, would be very nearly the same as you'd spend with a > mass binary distro anyway, and actually possibly less than the time you'd > spend if you were splitting distros and having to keep up with the > different ways different distros did things. > > At that point the update and admin time on your wife's machine would > probably be /less/ staying with gentoo, because you'd be doing binpkg > installs with already-built packages done on your main machine, and being > gentoo, you'd know it better and be more effective at admin, so you'd > actually spend less time on the admin side than you would if it were the > only machine you had running ubuntu (or fedora or whatever), and thus > dealing with any changes to config for the first and only time on her > machine. >
Yeah, I think the idea is at least worth investigating. However this is one of those ideas that I always thought sounded good on paper but would likely be a problem in real life. However maybe these machines are close enough to make it a good option. Other than the aes flag the two CPUs appear to support the same features. I have no idea how that maps into system performance or application space. I'll have to research that a bit. Not using it might make my machine a little slower on web pages or something like that but I doubt I'll see it. I could investigate turning that off and seeing what my machine wants to rebuild. On the other hand, it might make a bigger difference inside the Windows VMs. mark@c2RAID6 ~ $ cpuinfo2cpuflags-x86 CPU_FLAGS_X86="aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" mark@c2RAID6 ~ $ ssh laptop Password: mark@slinky ~ $ cpuinfo2cpuflags-x86 CPU_FLAGS_X86="mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" mark@slinky ~ $ I'll need to see about bringing the two machines into parity in terms of portage config files. Other than LibreOffice I'm pretty sure our world files are close and Office is binary anyway. She actually uses very few apps. The big sticking point here is the time it takes to build KDE which I'm going to do anyway on my machine so if the binary packages work that would be great. As I'm travelling next week there's no rush on this. I'll do some reading and think about possibly giving it a try. Cheers, Mark
