overkill

Eventhough the two are similar, you'd need to do a fresh install. You could then copy and/or transfer config files or personal files.

No! # emerge google-chrome -av These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] www-client/google-chrome-43.0.2357.130_p1 USE="plugins" LINGUAS="am ar bg bn ca cs da de el en_GB es es_LA et fa fi fil fr gu he hi hr hu id it ja kn ko lt lv ml mr ms nb nl pl pt_BR pt_PT ro ru sk sl sr sv sw ta te th tr uk vi zh_CN zh_TW" 47,185 kB Total: 1 package (1 new), Size of downloads: 47,185 kB Would you like to merge these packages? [Yes/No]

equery is your friend. # equery l -po *chrom* * Searching for *chrom* ... [-P-] [ ] games-action/chromium-bsu-0.9.15.1:0 [-P-] [ ] kde-misc/chromi-0.2:4 [-P-] [ ] kde-misc/chromi-0.2_p20141209:4 [-P-] [ ] media-libs/chromaprint-0.6:0 [-P-] [ ] media-libs/chromaprint-0.7:0 [-P-] [ ] media-libs/chromaprint-1.1:0 [-P-] [ ] media-libs/chromaprint-1.2:0 [-P-] [ ] net-misc/chrome-remote-desktop-40.0.2214.44:0 [-P-] [ ] net-misc/chrome-remote-desktop-41.0.2272.41:0 [-P-] [ ] net-misc/chrome-remote-desktop-41.0.2272.41-r1:0 [-P-] [ ] sec-policy/selinux-chromium-2.20140311-r5:0 [-P-] [ ] sec-policy/selinux-chromium-2.20140311-r6:0 [-P-] [ ] sec-policy/selinux-chromium-2.20140311-r7:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r1:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r2:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r3:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r4:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r5:0 [-P-] [ ] sec-policy/selinux-chromium-2.20141203-r6:0 [-P-] [ -] sec-policy/selinux-chromium-9999:0 [-P-] [ ] www-client/chromium-43.0.2357.65:0 [-P-] [ ] www-client/chromium-43.0.2357.73:0 [-P-] [ ] www-client/chromium-43.0.2357.130:0 [-P-] [ ] www-client/chromium-44.0.2403.18:0 [IP-] [ ] www-client/chromium-44.0.2403.30:0 [-P-] [M ] www-client/chromium-45.0.2427.7:0 [-P-] [M ] www-client/chromium-45.0.2431.0:0 [-P-] [ ] www-client/google-chrome-43.0.2357.130_p1:0 [-P-] [ ] www-client/google-chrome-beta-44.0.2403.52_p1:0 [-P-] [ ] www-client/google-chrome-unstable-45.0.2438.3_p1:0 [-P-] [ ] www-plugins/chrome-binary-plugins-43.0.2357.130_p1:stable [IP-] [ ] www-plugins/chrome-binary-plugins-44.0.2403.52_beta1:beta [-P-] [M ] www-plugins/chrome-binary-plugins-45.0.2438.3_alpha1:unstable [-P-] [M-] www-plugins/chrome-binary-plugins-9999:unstable [-P-] [ ] x11-drivers/xf86-video-openchrome-0.3.3:0

What is the output of # ifconfig -a ?

intel64-haswell

Just sync'd and updated to -r2. Now running kernel 4.0.4! Thanks for finding and reporting to Gentoo!

I'll check my work PC tomorrow. I have a different problem that I haven't filed a bug for yet - I cannot use X (also xf86-video-intel) with any kernel >=4.x.x. I get a segfault everytime. Works fine with 3.x.x. Started having the problem around the same time as the tool chain update, which included linux-headers-4.0 & the 4 series kernel. Looks like you already complained at bugs.gentoo.org. Did you file a new bug there? Did you file one at bugs.funtoo.org?

Are you sure you are using the module? If it's built-in, the module syntax would silently fail, but the kernel command line syntax in grub would work. What is the output of: # lsmod | grep usb FYI, the module/kernel parameters reference is in /usr/src/linux/Documentation/kernel-parameters.txt I checked my system - confirmed I've got usbcore built into my kernel. It also has autosuspend=2 and I have no issues with mice on either of my funtoo systems. # cat /sys/module/usbcore/parameters/autosuspend 2 If I need to change it, I could just issue: # echo -n -1 > /sys/modules/usbcore/parameters/autosuspend

I haven't seen a logo I liked yet. I'm no artist, but how about something simple and classy. Maybe just a penguin in the shape of the letter "f". The top of the f could be the head and neck, and the horizontal cross could be the wings.

It's a sandybridge. Why not http://www.funtoo.org/Intel64-sandybridge ?

Do you have a MAC allow list enabled on the router? Check the log on the router and see what it says. Are you using authentication?

So, indeed it is a sandybridge. See the "-march=sandybridge" in the output? There ya go.

You could try # echo "" | gcc -march=native -v -E - 2>&1 | grep cc1 to see what "native" detects.

I've always called it "Network Mangler" :)

The output shows that you have NOT successfully masked either of the two. Is your package.mask file located in /etc/portage/ ? Double-check your contents of that file. Do you have any typos?

Let's see the output of: equery l -po mono and equery l -po gtk-sharp

Thanks for the corrections, but both items are the default in Funtoo. I also believe that Gentoo does not offer Gnome-3.14 WITHOUT systemd. Funtoo does.

Biggest differences are: Benevolent Dictator as oppossed to a committee - Decisions are made in a more timely manner. Funtoo uses git instead of rsync for syncing tree No Systemd

I believe Daniel is still perfecting the eselect profile feature.

I think you found a bug. If I change my arch from x64_86 to pure64, then I only show 10 subarchs available, just like you noted. # eselect profile replace 1 2 # eselect profile list Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit [2] funtoo/1.0/linux-gnu/arch/pure64 * Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-bulldozer-pure64 [4] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-jaguar-pure64 [5] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k10-pure64 [6] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-k8-pure64 [7] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-piledriver-pure64 [8] funtoo/1.0/linux-gnu/arch/pure64/subarch/amd64-steamroller-pure64 [9] funtoo/1.0/linux-gnu/arch/pure64/subarch/atom_64-pure64 [10] funtoo/1.0/linux-gnu/arch/pure64/subarch/core2_64-pure64 [11] funtoo/1.0/linux-gnu/arch/pure64/subarch/corei7-pure64 [12] funtoo/1.0/linux-gnu/arch/pure64/subarch/generic_64-pure64 Currently available build profiles: [13] funtoo/1.0/linux-gnu/build/stable [14] funtoo/1.0/linux-gnu/build/current * [15] funtoo/1.0/linux-gnu/build/experimental Currently available flavor profiles: [16] funtoo/1.0/linux-gnu/flavor/minimal [17] funtoo/1.0/linux-gnu/flavor/core [18] funtoo/1.0/linux-gnu/flavor/desktop * [19] funtoo/1.0/linux-gnu/flavor/workstation [20] funtoo/1.0/linux-gnu/flavor/hardened Currently available mix-ins profiles: [21] funtoo/1.0/linux-gnu/mix-ins/audio [22] funtoo/1.0/linux-gnu/mix-ins/cinnamon [23] funtoo/1.0/linux-gnu/mix-ins/console-extras [24] funtoo/1.0/linux-gnu/mix-ins/dvd [25] funtoo/1.0/linux-gnu/mix-ins/gnome * [26] funtoo/1.0/linux-gnu/mix-ins/kde [27] funtoo/1.0/linux-gnu/mix-ins/mate [28] funtoo/1.0/linux-gnu/mix-ins/media [29] funtoo/1.0/linux-gnu/mix-ins/media-pro [30] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer [31] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro [32] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base [33] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer [34] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro [35] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common [36] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [37] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common [38] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [39] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common [40] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [41] funtoo/1.0/linux-gnu/mix-ins/lxde [42] funtoo/1.0/linux-gnu/mix-ins/lxqt [43] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [44] funtoo/1.0/linux-gnu/mix-ins/no-systemd [45] funtoo/1.0/linux-gnu/mix-ins/print (auto) [46] funtoo/1.0/linux-gnu/mix-ins/python3-only [47] funtoo/1.0/linux-gnu/mix-ins/X [48] funtoo/1.0/linux-gnu/mix-ins/xfce [49] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [50] funtoo/1.0/linux-gnu/mix-ins/hardened If I change it back, then all the subarchs reappear: # eselect profile replace 2 1 # eselect profile list Currently available arch profiles: [1] funtoo/1.0/linux-gnu/arch/x86-64bit * [2] funtoo/1.0/linux-gnu/arch/pure64 Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-bulldozer [4] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-jaguar [5] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k10 [6] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8 [7] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8+sse3 [8] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver [9] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-steamroller [10] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/atom_64 [11] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/btver1_64 [12] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core2_64 [13] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core-avx-i [14] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 [15] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64 [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell [17] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-ivybridge [18] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-sandybridge [19] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 [20] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/nocona [21] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/opteron_64 [22] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/xen-pentium4+sse3_64 Currently available build profiles: [23] funtoo/1.0/linux-gnu/build/stable [24] funtoo/1.0/linux-gnu/build/current * [25] funtoo/1.0/linux-gnu/build/experimental Currently available flavor profiles: [26] funtoo/1.0/linux-gnu/flavor/minimal [27] funtoo/1.0/linux-gnu/flavor/core [28] funtoo/1.0/linux-gnu/flavor/desktop * [29] funtoo/1.0/linux-gnu/flavor/workstation [30] funtoo/1.0/linux-gnu/flavor/hardened Currently available mix-ins profiles: [31] funtoo/1.0/linux-gnu/mix-ins/audio [32] funtoo/1.0/linux-gnu/mix-ins/cinnamon [33] funtoo/1.0/linux-gnu/mix-ins/console-extras [34] funtoo/1.0/linux-gnu/mix-ins/dvd [35] funtoo/1.0/linux-gnu/mix-ins/gnome * [36] funtoo/1.0/linux-gnu/mix-ins/kde [37] funtoo/1.0/linux-gnu/mix-ins/mate [38] funtoo/1.0/linux-gnu/mix-ins/media [39] funtoo/1.0/linux-gnu/mix-ins/media-pro [40] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-consumer [41] funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro [42] funtoo/1.0/linux-gnu/mix-ins/mediadevice-base [43] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-consumer [44] funtoo/1.0/linux-gnu/mix-ins/mediadevice-video-pro [45] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-common [46] funtoo/1.0/linux-gnu/mix-ins/mediaformat-audio-extra [47] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-common [48] funtoo/1.0/linux-gnu/mix-ins/mediaformat-gfx-extra [49] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-common [50] funtoo/1.0/linux-gnu/mix-ins/mediaformat-video-extra [51] funtoo/1.0/linux-gnu/mix-ins/lxde [52] funtoo/1.0/linux-gnu/mix-ins/lxqt [53] funtoo/1.0/linux-gnu/mix-ins/no-emul-linux-x86 [54] funtoo/1.0/linux-gnu/mix-ins/no-systemd [55] funtoo/1.0/linux-gnu/mix-ins/print (auto) [56] funtoo/1.0/linux-gnu/mix-ins/python3-only [57] funtoo/1.0/linux-gnu/mix-ins/X [58] funtoo/1.0/linux-gnu/mix-ins/xfce [59] funtoo/1.0/linux-gnu/mix-ins/vmware-guest [60] funtoo/1.0/linux-gnu/mix-ins/hardened

Have you updated your system lately? I show 20 subarchs: Currently available subarch profiles: [3] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-bulldozer [4] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-jaguar [5] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k10 [6] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8 [7] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-k8+sse3 [8] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver [9] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-steamroller [10] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/atom_64 [11] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/btver1_64 [12] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core2_64 [13] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/core-avx-i [14] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7 [15] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/generic_64 [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-haswell [17] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-ivybridge [18] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-sandybridge [19] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 [20] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/nocona [21] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/opteron_64 [22] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/xen-pentium4+sse3_64 So, 19 is the one I would choose on my system.

No. 12 is march=generic. If you want native, choose native-64. If you are really curious, you can view the settings of each subarch by reading the file contents for a particular subarch. They reside in /usr/portage/profile/funtoo/1.0/linux-gnu/arch/<preferred arch>/subarch/<preferred subarch>/make.defaults

`emerge -1` (-1 = --oneshot) will not add the package to the world file. You need to remove the --oneshot option for any package to be added to the world file when manually installing a package. --oneshot SHOULD be used when manually reinstalling @system files, that way they are not added to the @world set as well as belonging to the @system set. One can manually add a previously installed package to the world set by using the --noreplace flag, ie `emerge --noreplace =debian-sources-3.14.37`.

Local service is the very last thing to start. You'd just need to create a file with .start as the extension in /etc/local.d/ like eset.start, then put a start up command in it like `/etc/init.d.eset start` or whatever your script is.

Local is the last service started - after all other services. If you don't want to start it manually, that's the way to start it. I guess one could use a cron job, but I think it would have to have logic to check it's status and ignore or start based on the status. Why don't you want to use the init script?