> On Aug 6, 2015, at 6:22 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> William Hubbs posted on Thu, 06 Aug 2015 16:36:49 -0500 as excerpted:
>
>> Also, I want to talk more about netmount and localmount failing.
>>
>> If netmount and localmount are set up to fail if one of the file systems
>> t
* Zac Medico schrieb am 05.08.15 um 00:04 Uhr:
On 08/04/2015 01:16 PM, Marc Schiffbauer wrote:
hi all,
i find it a bit hard to understand how --binpkg-changed-deps is supposed
to work and what implications it has. Moreover I think the man page is
not very clear about what it does:
"--binpkg-ch
William Hubbs posted on Thu, 06 Aug 2015 16:36:49 -0500 as excerpted:
> Also, I want to talk more about netmount and localmount failing.
>
> If netmount and localmount are set up to fail if one of the file systems
> they mount fails (which is what other init systems out there do), the
> sys admin
All,
This is my previous post, added on the right thread this time.
as I have always said, my views can evolve with civil discussion, and
there has been some good feedback on this.
I also got a suggestion for handling network file systems that would mean we
wouldn't have to keep track of the spe
Folks,
disregard my previous msg on this thread, it was supposed to go
somewhere else.
William
signature.asc
Description: Digital signature
All,
as I have always said, my views can evolve with civil discussion, and
there has been some good feedback on this.
I also got a suggestion for handling network file systems that would mean we
wouldn't have to keep track of the specific clients needed to mount
network file systems; we could let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/08/15 02:58 AM, Duncan wrote:
> William Hubbs posted on Wed, 05 Aug 2015 10:26:33 -0500 as
> excerpted:
>
>> It isn't localmount that would have the issue, but mount.*
>> because they are lexically after localmount, so you would end up
>> with
