Re: [gentoo-user] enlightenment experience
Mick wrote: My knowledge of coding is non-existent, but as a plain user I have been using enlightenment since the e17 days and can confirm it does not have many native applications. Last time I looked I found around a dozen apps in various stages of development, plus its file manager & desktop gadgets. ... > I've used e with a small selection of KDE applications, but obviously not the > full Plasma DE. For most of the time it worked fine. No crashes, no lost > data, no drama. It just did what I needed from a desktop, efficiently, > without eating up resources, without buggy indexers, getting out of the way > and letting me get on with work. I had to improvise to get some Qt Thanks that's the kind of info I was looking for. In the end I decided to go for Xfce, mainly because the gentoo wiki pages are a lot more detailed than the E ones so it gives me the idea of a better supported environment. raffaele
Re: [gentoo-user] Re: Dolphin only allowing a single instance after update
Mick wrote:
> On Sunday, 18 August 2019 22:57:14 BST Dale wrote:
>> Nikos Chantziaras wrote:
>>> On 17/08/2019 05:56, Dale wrote:
I upgraded my system last night. I logged out and back in earlier and
have noticed something new. It seems to only allow one instance of
Dolphin to run at a time.
>>> When you press Meta+E ("meta" being the key with the Windows logo on
>>> most keyboard), you can start a new Dolphin instance. Dolphin doesn't
>>> have to be already open for this to work. It's a global Plasma shortcut.
>> That works. It gives me a new instance of it at least. I've looked
>> everywhere in the configure section and I've even found and looked at
>> the Dolphin handbook online and can't find a way to disable this.
>> Usually I click on the folder on my desktop to go where I want. I have
>> either the directory itself or links to those I go to frequently. Have
>> you seen a way to make it work the old way? Doing the keyboard shortcut
>> is a workaround for the moment tho. Thanks much for that. I'd still
>> prefer to have it the old way tho.
>>
>> Thanks so much again. At least I have a workaround for the time being.
>>
>> Dale
>>
>> :-) :-)
> I must be pressing the keyboard buttons the wrong way, it does not work here
> on plasma-5.15.5 & dolphin-19.04.3 :-/
>
Yours are older so that may not be added yet.
root@fireball / # equery list -p plasma
* Searching for plasma ...
[IP-] [ ] kde-frameworks/plasma-5.60.0:5/5.60
[-P-] [ ] kde-frameworks/plasma-5.61.0:5/5.61
root@fireball / # equery list -p kde-apps/dolphin
* Searching for dolphin in kde-apps ...
[-P-] [ ] kde-apps/dolphin-19.04.3:5
[IP-] [ ] kde-apps/dolphin-19.08.0:5
root@fireball / #
When you get to the latest Dolphin, maybe then it will work.
Dale
:-) :-)
Re: [gentoo-user] Re: Dolphin only allowing a single instance after update
On Sunday, 18 August 2019 22:57:14 BST Dale wrote:
> Nikos Chantziaras wrote:
> > On 17/08/2019 05:56, Dale wrote:
> >> I upgraded my system last night. I logged out and back in earlier and
> >> have noticed something new. It seems to only allow one instance of
> >> Dolphin to run at a time.
> >
> > When you press Meta+E ("meta" being the key with the Windows logo on
> > most keyboard), you can start a new Dolphin instance. Dolphin doesn't
> > have to be already open for this to work. It's a global Plasma shortcut.
>
> That works. It gives me a new instance of it at least. I've looked
> everywhere in the configure section and I've even found and looked at
> the Dolphin handbook online and can't find a way to disable this.
> Usually I click on the folder on my desktop to go where I want. I have
> either the directory itself or links to those I go to frequently. Have
> you seen a way to make it work the old way? Doing the keyboard shortcut
> is a workaround for the moment tho. Thanks much for that. I'd still
> prefer to have it the old way tho.
>
> Thanks so much again. At least I have a workaround for the time being.
>
> Dale
>
> :-) :-)
I must be pressing the keyboard buttons the wrong way, it does not work here
on plasma-5.15.5 & dolphin-19.04.3 :-/
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Dolphin only allowing a single instance after update
Nikos Chantziaras wrote:
> On 17/08/2019 05:56, Dale wrote:
>> I upgraded my system last night. I logged out and back in earlier and
>> have noticed something new. It seems to only allow one instance of
>> Dolphin to run at a time.
>
> When you press Meta+E ("meta" being the key with the Windows logo on
> most keyboard), you can start a new Dolphin instance. Dolphin doesn't
> have to be already open for this to work. It's a global Plasma shortcut.
>
>
>
That works. It gives me a new instance of it at least. I've looked
everywhere in the configure section and I've even found and looked at
the Dolphin handbook online and can't find a way to disable this.
Usually I click on the folder on my desktop to go where I want. I have
either the directory itself or links to those I go to frequently. Have
you seen a way to make it work the old way? Doing the keyboard shortcut
is a workaround for the moment tho. Thanks much for that. I'd still
prefer to have it the old way tho.
Thanks so much again. At least I have a workaround for the time being.
Dale
:-) :-)
[gentoo-user] Re: Dolphin only allowing a single instance after update
On 17/08/2019 05:56, Dale wrote:
I upgraded my system last night. I logged out and back in earlier and
have noticed something new. It seems to only allow one instance of
Dolphin to run at a time.
When you press Meta+E ("meta" being the key with the Windows logo on
most keyboard), you can start a new Dolphin instance. Dolphin doesn't
have to be already open for this to work. It's a global Plasma shortcut.
Re: [gentoo-user] empty cdrom drive is busy or mounted [resolved]
On 08/16/2019 06:21:30 PM, Jack wrote: On 2019.08.16 12:00, Helmut Jarausch wrote: On 08/16/2019 05:25:34 PM, Jack wrote: try "lsof /cdrom"? It says the mount point, not the device, might be busy. This didn't show anything. I still don't know the cause of my problems. But fortunately, they have been resolved by recompiling the kernel (5.2.0), systemd and all packages depending on systemd - using the new gcc-9.2.0 Furthermore I had to add the use flags cgroup-hybrid -sysv-utils for systemd. This hasn't been necessary before - very strange. For me, systemd is a monster which I haven't understood. I try to not use it since I am using openrc. Perhaps I have to remove it from my system and use eudev instead of udev as part of systemd. Thanks for trying to help me - it was a really strange situation. If you are using openrc (as I am) I would say you really don't want systemd installed at all. I can't imagine any good coming from that. You do need eudev, I also have elogind installed, but I'm not sure if it's absolutely required, or if I had some other reason for installing (possibly to get rid of consolekit?) Thank you Jack and Laurence! I've put the (possibly dangerous) task to get rid of systemd on my to-do list. Meanwhile, the issue is resolved here - most probably because I uninstalled sys-fs/udiskie. (Less likely because I upgraded the kernel from 5.2.8 to 5.2.9) Many thanks again, Helmut
Re: [gentoo-user] NFS setup
On Sunday, 18 August 2019 10:35:36 BST Adam Carter wrote: > On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey > > wrote: > > On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: > > > Is the output of 'mount | grep nfs' the same on the two client > > > machines? > > > > $ mount | grep nfs > > nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) > > nfs4 requires less ports than nfs3, just 2049 and something for mountd > (IIRC). Try using nfs4 and setting up the firewall for 2049 and 32767 from > your OPTS_RPC_MOUNTD="-p 32767" setting. From tcpdump, where .2 is the > client and .250 is the server; > 192.168.1.2.949 > 192.168.1.250.2049: Flags [S] > but the other session is > 192.168.1.250.730 > 192.168.1.2.40895: Flags [S] > ie a low port on the nfs server makes a connection back to the client, so > its quite unconventional > > FYI, here's what one of mine looks like > $ mount | grep nfs > 192.168.1.250:/export/public on /mnt/public type nfs4 > (ro,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,t > imeo=600,retrans=2,sec=sys,clientaddr=192.168.1.251,local_lock=none,addr=192 > .168.1.250,_netdev) > > $ grep nfs /etc/fstab > 192.168.1.250:/export/public/mnt/publicnfs4 > ro,_netdev,vers=4.0,soft,noatime 0 0 Thanks Adam. One thing I forgot to say is that emerge --sync and eix-update work fine with file transfers; it's only when a file is opened remotely that a new port is used. But! All this is moot now, because today as I'm running my usual update, everything is working just fine! I haven't changed anything, honest. Thanks again for your help; if it goes wrong again I'll follow your suggestion. -- Regards, Peter.
Re: [gentoo-user] NFS setup
On Sun, Aug 18, 2019 at 7:11 PM Peter Humphrey wrote: > On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: > > > Is the output of 'mount | grep nfs' the same on the two client machines? > > $ mount | grep nfs > nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) > > nfs4 requires less ports than nfs3, just 2049 and something for mountd (IIRC). Try using nfs4 and setting up the firewall for 2049 and 32767 from your OPTS_RPC_MOUNTD="-p 32767" setting. From tcpdump, where .2 is the client and .250 is the server; 192.168.1.2.949 > 192.168.1.250.2049: Flags [S] but the other session is 192.168.1.250.730 > 192.168.1.2.40895: Flags [S] ie a low port on the nfs server makes a connection back to the client, so its quite unconventional FYI, here's what one of mine looks like $ mount | grep nfs 192.168.1.250:/export/public on /mnt/public type nfs4 (ro,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.251,local_lock=none,addr=192.168.1.250,_netdev) $ grep nfs /etc/fstab 192.168.1.250:/export/public/mnt/publicnfs4 ro,_netdev,vers=4.0,soft,noatime 0 0
Re: [gentoo-user] NFS setup
On Sunday, 18 August 2019 09:30:36 BST Adam Carter wrote: > Is the output of 'mount | grep nfs' the same on the two client machines? $ mount | grep nfs nfsd on /proc/fs/nfsd type nfsd (rw,nosuid,nodev,noexec,relatime) It's the same on both clients. In the chroots, I see: atom / # mount | grep nfs 192.168.1.2:/usr/portage on /usr/portage type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.2,mountvers=3,mountport=32767,mountproto=udp,local_lock=none,addr=192.168.1.2) (That's the one that works right) clrn / # mount | grep nfs 192.168.1.4:/usr/portage on /usr/portage type nfs (rw,relatime,vers=3,rsize=1024,wsize=1024,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.4,mountvers=3,mountport=32767,mountproto=udp,local_lock=none,addr=192.168.1.4) The only differences I can see are the IP addresses (of course) and the rsize and wsize; the good one has 128K, the other 1K. I'd better look into that, though it doesn't look like the problem. The good client is a 32-bit single- core Atom, the other is a 64-bit quad-core Celeron. /etc/conf.d/nfs is the same on both clients: OPTS_RPC_NFSD="1" OPTS_RPC_MOUNTD="-p 32767" OPTS_RPC_STATD="-p 32765 -o 32766" OPTS_RPC_IDMAPD="" OPTS_RPC_GSSD="" OPTS_RPC_SVCGSSD="" OPTS_RPC_RQUOTAD="" EXPORTFS_TIMEOUT=30 Any other ideas? -- Regards, Peter.
Re: [gentoo-user] NFS setup
On 18 August 2019 10:01:18 CEST, Peter Humphrey wrote: >On to the next problem... > >This workstation serves as compute host to two smaller boxes on the >network. I >NFS-mount the PORTDIR of the smaller box in a chroot on this one, then >do >emerging and so on to build packages which I install later on the >smaller box. > >That works fine on one of the smaller boxes, but on the other I get a >different port being used for NFS transfer every time. So I have to >change the >holes in the firewall before anything useful happens. > >As far as I can see, everything to do with NFS is identical on the two >boxes, >in particular kernel config, /etc/conf.d/nfs and /etc/exports, but I >must have >missed something. SSH and SCP are not affected. > >Any ideas? Check the file /etc/conf.d/nfs in the nfs server. There are settings documented there (using -p and -o options to fix the port numbers for the different parts. I had the same issue in the past, which is why I remember. I solved it by moving all NFS stuff onto a seperate VLAN which is only for storage. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] NFS setup
On Sun, Aug 18, 2019 at 6:01 PM Peter Humphrey wrote: > On to the next problem... > > This workstation serves as compute host to two smaller boxes on the > network. I > NFS-mount the PORTDIR of the smaller box in a chroot on this one, then do > emerging and so on to build packages which I install later on the smaller > box. > > That works fine on one of the smaller boxes, but on the other I get a > different port being used for NFS transfer every time. > Is the output of 'mount | grep nfs' the same on the two client machines?
[gentoo-user] NFS setup
On to the next problem... This workstation serves as compute host to two smaller boxes on the network. I NFS-mount the PORTDIR of the smaller box in a chroot on this one, then do emerging and so on to build packages which I install later on the smaller box. That works fine on one of the smaller boxes, but on the other I get a different port being used for NFS transfer every time. So I have to change the holes in the firewall before anything useful happens. As far as I can see, everything to do with NFS is identical on the two boxes, in particular kernel config, /etc/conf.d/nfs and /etc/exports, but I must have missed something. SSH and SCP are not affected. Any ideas? -- Regards, Peter.
