On Mon, 17 Nov 2014 13:14:49 +0100 intrigeri wrote:
> Hi,
>
> Michael Biebl wrote (03 Jul 2014 21:07:36 GMT) :
> > Am 03.07.2014 20:57, schrieb Michal Suchanek:
> >> Also candidate for big fat release note.
>
> > Nod. I guess the recommendation here is to simply mark non-critical
> > mounts as
Hi,
Michael Biebl wrote (03 Jul 2014 21:07:36 GMT) :
> Am 03.07.2014 20:57, schrieb Michal Suchanek:
>> Also candidate for big fat release note.
> Nod. I guess the recommendation here is to simply mark non-critical
> mounts as nofail.
> [...]
> So maybe just documenting the fact that this needs t
Am 03.07.2014 20:57, schrieb Michal Suchanek:
> Package: systemd
> Version: 204-14
> Followup-For: Bug #748056
>
> Hello,
>
> since this is a 'feature' I expect this is still present.
>
> I encountered this problem when one of my drive cables went loose and
> the drive became inaccessible.
>
>
Package: systemd
Version: 204-14
Followup-For: Bug #748056
Hello,
since this is a 'feature' I expect this is still present.
I encountered this problem when one of my drive cables went loose and
the drive became inaccessible.
The drive was ad-hoc connected while placed physically outside of the
Hello,
Thank you for pointing that out! By the way, fstab man page says that
nofail means "do not report errors for this device if it does not exist",
although the HDD partition obviously always exists. I also thought that
nofail was meant to be used for things like removable devices, not for
"mar
Am 13.05.2014 22:57, schrieb Nikita Pichugin:
> Package: systemd
> Version: 204-10
> Severity: important
>
> Dear Maintainer,
>
> I use a dualboot machine with Debian and Windows 8. I want the windows
> partition to automount on boot, so I added it to the /etc/fstab. The problem
> is
> that I ca
