mauricev

How odd, I set fsid=0 as an option to the export line and now it works in the older gentoo kernel.

When I use debian-sources, I can mount the exported nfs share (nfs v3) on this system, but when I try to use a gentoo-sources I customized, I get this instead: mount.nfs: access denied by server while mounting zfs:/z/nfs In debugging, I get mount.nfs: mount(2): Permission denied So something has to be missing from my gentoo-sources, but I don't know what it can be. Everything seems to be in order according to exportfs and rpcinfo. More info, the log reveals [rpc.mountd] authenticated mount request from 127.0.0.1:836 for /z/nfs (/z/nfs) Aug 02 23:41:23 [rpc.mountd] Cannot export /z/nfs, possibly unsupported filesystem or fsid= required

The reason is explained here https://bugs.funtoo.org/browse/FL-5318?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel The profile overrules the make.conf

I have my use with -pam and I don't have pam installed. I have no idea why I would need so I don't have it. But suddenly portage insisting I get it. [ebuild N ] sys-libs/pam-1.3.0-r2::core-kit USE="cracklib filecaps nls pie -audit -berkdb -debug -nis (-selinux) {-test} -vim-syntax" ABI_X86="(64) -32 (-x32)" 1,754 KiB [ebuild N ] sys-auth/pambase-20150213-r3::core-kit USE="cracklib nullok sha512 -consolekit -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc -securetty (-selinux) -systemd" 4 KiB

I didn't get those warnings because when I built the digest I gave it the full path and when I attempted to emerge autossh, I just told it emerge -v autossh. I never referenced "cat" itself.

Ah, the word cat was not meant to be taken literally, but it refers to the category of the package, which, in this case, is net-misc. That fixed it. And, no, there were no warnings from emerge. Thanks!

/var/git/overlay └── local-overlay ├── COPYRIGHT.txt ├── LICENSE.txt ├── README.rst ├── cat │ └── autossh │ ├── Manifest │ ├── autossh-1.4f.ebuild │ └── metadata.xml ├── metadata │ └── layout.conf └── profiles └── repo_name

sudo: tree: command not found

That was a mistake, not the mistake. It still doesn't work.

Yes, I did that. But one thing that wasn't not stated in the docs is that path where the packages must reside. I would have never guessed it.

I want to use the latest version of autossh, which isn't yet in the portage tree. I followed the instructions at https://www.funtoo.org/Local_Overlay, but what are the next steps? Do I recreate the kits directory hierarchy in /var/git/overlay/local-overlay. ( I tried that and it had no effect.) My updated autossh ebuild is not being seen.

4.15.17-1 https://pastebin.com/zK629ztL

On a system I built with KDE-plasma, I notice that login to the KDE console (using SDDM) may take up to more than a minute to login. I also noticed once that parts of the GUI (the "start" menu) became nonresponsive for about 30 seconds. I am noticing this in the log [console-kit-daemon] CRITICAL: polkit_authority_check_authorization: assertion 'POLKIT_IS_AUTHORITY (authority)' failed_ This seems like a hint.

I put RUBY_TARGETS="ruby23 ruby24" in make.conf and now everything is emerging. If I comment the line, I get this emerge: there are no ebuilds built with USE flags to satisfy "virtual/rubygems[ruby_targets_ruby22]". !!! One of the following packages is required to complete your request: - virtual/rubygems-13::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-12::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-11::ruby-kit (Missing IUSE: ruby_targets_ruby22) (dependency required by "dev-ruby/minitest-5.10.3::ruby-kit[-test,ruby_targets_ruby22]" [ebuild]) (dependency required by "dev-lang/ruby-2.4.3::ruby-kit" [installed]) (dependency required by "dev-ruby/test-unit-3.2.6::ruby-kit[ruby_targets_ruby24]" [ebuild]) (dependency required by "dev-lang/ruby-2.3.6::ruby-kit" [installed]) (dependency required by "dev-ruby/net-telnet-0.1.1-r1::ruby-kit[ruby_targets_ruby23]" [ebuild])

https://pastebin.com/D8knQCXg