2011/5/31 Kay Sievers
> 2011/5/31 Björn Busse :
> > I do have some removeable devices configured in fstab with the
> > comment=systemd.automount option. Now whenever an application scans the
> > filesystem it gets stuck while doing stat() on the mountpoint of those
> > devices until I plugin thos
2011/5/31 Björn Busse :
> I do have some removeable devices configured in fstab with the
> comment=systemd.automount option. Now whenever an application scans the
> filesystem it gets stuck while doing stat() on the mountpoint of those
> devices until I plugin those.
> Reading the man page of syste
Hi,
I do have some removeable devices configured in fstab with the
comment=systemd.automount option. Now whenever an application scans
the filesystem it gets stuck while doing stat() on the mountpoint of
those devices until I plugin those.
Reading the man page of systemd.mount i could possi
On Monday, May 30, 2011 14:54:54 Kay Sievers wrote:
> On Mon, May 30, 2011 at 10:20, Andreas Jaeger wrote:
> > Looking at the os-release information, I wonder how to encode in the best
> > way the Beta or Milestone versions of a product, e.g. "openSUSE 12.1
> > Milestone 1"
> >
> > Is this one ad
On Mon, May 30, 2011 at 10:20, Andreas Jaeger wrote:
>
> Looking at the os-release information, I wonder how to encode in the best way
> the Beta or Milestone versions of a product, e.g. "openSUSE 12.1 Milestone 1"
>
> Is this one added as part of version? e.g.:
> VERSION="12.1 Milestone 1 (Codena
Looking at the os-release information, I wonder how to encode in the best way
the Beta or Milestone versions of a product, e.g. "openSUSE 12.1 Milestone 1"
Is this one added as part of version? e.g.:
VERSION="12.1 Milestone 1 (Codename)"
VERSION_ID="12.1 milestone 1"
Or is there some other logi
