emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#40158: closed (mount point is not created if mount? is #f)


From: GNU bug Tracking System
Subject: bug#40158: closed (mount point is not created if mount? is #f)
Date: Sun, 29 Aug 2021 06:09:01 +0000

Your message dated Sun, 29 Aug 2021 02:08:35 -0400
with message-id <87mtp0rdek.fsf@gmail.com>
and subject line Re: bug#40158: mount point is not created if mount? is #f
has caused the debbugs.gnu.org bug report #40158,
regarding mount point is not created if mount? is #f
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
40158: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40158
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: mount point is not created if mount? is #f Date: Fri, 20 Mar 2020 19:13:36 -0400
Consider the following file system record:

(file-system
  (device "some-server:/mnt/scratch/yocto-sstate")"
  (mount-point "/mnt/scratch/yocto-sstate")
  (create-mount-point? #t)
  (type "nfs")
  (mount? #f)
  (options "soft")
  (flags '(no-exec)))

Even though a user would think the mount point would be created, it is
not, I'm guessing because mount? is #f.

Maxim



--- End Message ---
--- Begin Message --- Subject: Re: bug#40158: mount point is not created if mount? is #f Date: Sun, 29 Aug 2021 02:08:35 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hello,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello,
>
> maxim.cournoyer@gmail.com writes:
>
>> Consider the following file system record:
>>
>> (file-system
>>   (device "some-server:/mnt/scratch/yocto-sstate")"
>>   (mount-point "/mnt/scratch/yocto-sstate")
>>   (create-mount-point? #t)
>>   (type "nfs")
>>   (mount? #f)
>>   (options "soft")
>>   (flags '(no-exec)))
>>
>> Even though a user would think the mount point would be created, it is
>> not, I'm guessing because mount? is #f.
>>
>> Maxim
>
> I had the "chance" again today to meet this issue, so I took it by the
> horns and came up with the attached patch, which fixes it:
>
>
>
> Thanks,
>
> Maxim

Pushed with 8ad6624b96.  Closing!

Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]