On 08/20/18 22:23, deloptes wrote:
Michael Stone wrote:
What on earth does this mean? How did the system get into such a state
that these were missing?
he wrote net-base was missing, but why was net-base missing?
As I wrote in one of my posts, the system was installed using
debootstrap --va
Michael Stone wrote:
> What on earth does this mean? How did the system get into such a state
> that these were missing?
he wrote net-base was missing, but why was net-base missing?
finally I think he solved the problem
regards
The package netbase was missing.
Thanks for your help
--
Pozdrawiam
Grzesiek
Wysłane z kompa wolnego od wirusów Billa Gatesa.
On Mon, Aug 20, 2018 at 05:25:07PM +0300, Reco wrote:
Note that your client advertizes NFSv4 support. Maybe that's what they
really use?
The output of `mount` or /proc/mounts will show what's actually in use.
Mike Stone
Hi.
On Mon, Aug 20, 2018 at 04:04:01PM +0200, Grzegorz Sójka wrote:
> On 08/20/18 15:12, Reco wrote:
> > Hi.
> >
> > On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote:
> > > I added /etc/services /etc/rpc and now rpcbind is starting but:
> > >
> > > #rpcinfo -p localhist
On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote:
I added /etc/services /etc/rpc
What on earth does this mean? How did the system get into such a state
that these were missing?
Mike Stone
On 08/20/18 15:12, Reco wrote:
Hi.
On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote:
I added /etc/services /etc/rpc and now rpcbind is starting but:
#rpcinfo -p localhist
program vers proto port service
104 tcp111 portmapper
103 t
Hi.
On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote:
> I added /etc/services /etc/rpc and now rpcbind is starting but:
>
> #rpcinfo -p localhist
>program vers proto port service
> 104 tcp111 portmapper
> 103 tcp111 portmapper
>
I added /etc/services /etc/rpc and now rpcbind is starting but:
#rpcinfo -p localhist
program vers proto port service
104 tcp111 portmapper
103 tcp111 portmapper
102 tcp111 portmapper
104 udp111 portmapper
1
Grzegorz Sójka wrote:
> On 08/19/18 16:52, deloptes wrote:
>> Grzegorz Sójka wrote:
>>
>>> /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash)
>>
>> and you are 100% sure you are using nfs v3 and not nfs v4 on the not
>> working client? you do not have firewalls enabled?
>
> Yes, h
Hi.
On Sun, Aug 19, 2018 at 05:11:02PM +0200, Grzegorz Sójka wrote:
> On 08/19/18 16:52, deloptes wrote:
> > Grzegorz Sójka wrote:
> >
> > > /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash)
> >
> > and you are 100% sure you are using nfs v3 and not nfs v4 on the not worki
On 08/19/18 16:52, deloptes wrote:
Grzegorz Sójka wrote:
/home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash)
and you are 100% sure you are using nfs v3 and not nfs v4 on the not working
client? you do not have firewalls enabled?
Yes, here is appropriate line from fstab:
Hermes
Grzegorz Sójka wrote:
> /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash)
and you are 100% sure you are using nfs v3 and not nfs v4 on the not working
client? you do not have firewalls enabled?
On 08/19/18 00:08, deloptes wrote:
Grzegorz Sójka wrote:
Hi there
I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop.
When I try to mount any NFS share on the desktop I always get the
following:
# mount -v /home/trash
mount.nfs: timeout set for Sat Aug 18 18:55:52 2018
mo
Grzegorz Sójka wrote:
>
> Hi there
>
> I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop.
> When I try to mount any NFS share on the desktop I always get the
> following:
>
> # mount -v /home/trash
> mount.nfs: timeout set for Sat Aug 18 18:55:52 2018
> mount.nfs: trying te
Hi there
I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop.
When I try to mount any NFS share on the desktop I always get the following:
# mount -v /home/trash
mount.nfs: timeout set for Sat Aug 18 18:55:52 2018
mount.nfs: trying text-based options 'nfsvers=3,addr=192.16
On Sat 18 Aug 2018 at 21:31:05 +0200, Grzegorz Sójka wrote:
> Hi there
>
> I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop. When
> I try to mount any NFS share on the desktop I always get the following:
>
> # mount -v /home/trash
> mount.nfs: timeout set for Sat Aug 18 18:
Hi there
I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop.
When I try to mount any NFS share on the desktop I always get the following:
# mount -v /home/trash
mount.nfs: timeout set for Sat Aug 18 18:55:52 2018
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.
18 matches
Mail list logo