> On Jul 29, 2016, at 3:17 AM, Belal, Awais wrote:
>
>>> On Jul 28, 2016, at 1:49 AM, Awais Belal wrote:
>>>
>>> Using a copy would only make management of devices erroneous
>>> and makes the system unstable in some scenarios as tools will
>>> have to manipulate both files separately. A link e
init-install*: /etc/mtab make a link rather than
a copy
On Thu, Jul 28, 2016 at 1:49 AM, Awais Belal wrote:
> Using a copy would only make management of devices erroneous
> and makes the system unstable in some scenarios as tools will
> have to manipulate both files separately. A link ensur
>> On Jul 28, 2016, at 1:49 AM, Awais Belal wrote:
>>
>> Using a copy would only make management of devices erroneous
>> and makes the system unstable in some scenarios as tools will
>> have to manipulate both files separately. A link ensures that
>> both files /proc/mounts and /etc/mtab will have
On Thu, Jul 28, 2016 at 1:49 AM, Awais Belal wrote:
> Using a copy would only make management of devices erroneous
> and makes the system unstable in some scenarios as tools will
> have to manipulate both files separately. A link ensures that
> both files /proc/mounts and /etc/mtab will have the s
> On Jul 28, 2016, at 1:49 AM, Awais Belal wrote:
>
> Using a copy would only make management of devices erroneous
> and makes the system unstable in some scenarios as tools will
> have to manipulate both files separately. A link ensures that
> both files /proc/mounts and /etc/mtab will have the
Using a copy would only make management of devices erroneous
and makes the system unstable in some scenarios as tools will
have to manipulate both files separately. A link ensures that
both files /proc/mounts and /etc/mtab will have the same
information at all times and this is how it is handled
on
