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
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
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.
> >
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
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
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,
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
>
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
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 |
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
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
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
12 matches
Mail list logo
