All:
For client tracking and recovery on reboots NFS provides some mechanisms.
My understanding is that nfsdcld is considered replaced by nfsdcltrack.
However, while there is a system service unit for nfsdcld there is
nothing for nfsdcltrack. The binary for both is available. Only the
systemd
On 21-07-19 21:46:42 +0200, Ralf Mardorf via arch-general wrote:
despite strange messages, it works when using mpv :).
Yeah, those are just probing for nvidia stuff; not exactly errors.
I also found that vp9 is pretty good with software decoding but things
take a nosedive when you have to
On Sun, 2019-07-21 at 21:22 +0200, Jan Alexander Steffens wrote:
> On Sun, Jul 21, 2019 at 4:01 PM Ralf Mardorf via arch-general
> wrote:
> > Hi,
> >
> > when playing youtube videos hardware video acceleration seems to gain
> > absolutely nothing on my machine or I've done something wrong ;).
>
On Sun, 2019-07-21 at 18:16 +0100, Ralph Corderoy wrote:
> have you tried ‘mpv foo.mp4’ so you can see what it outputs about its
> video out, ‘VO’, choice before it starts playing?
Hi,
thank you Ralph.
$ ffmpeg -i IMG_2907.MOV -vcodec libx264 mp4_2907.mp4
[snip]
$ mpv mp4_2907.mp4
Playing:
On Sun, Jul 21, 2019 at 4:01 PM Ralf Mardorf via arch-general
wrote:
>
> Hi,
>
> when playing youtube videos hardware video acceleration seems to gain
> absolutely nothing on my machine or I've done something wrong ;).
>
> Am I missing something?
Neither Chrome nor Firefox support accelerated
Hi Ralf,
> when playing youtube videos hardware video acceleration seems to gain
> absolutely nothing on my machine or I've done something wrong ;).
Rather than use Firefox, have you tried ‘mpv foo.mp4’ so you can see
what it outputs about its video out, ‘VO’, choice before it starts
playing?
On 7/21/19 4:11 AM, Stephen Gregoratto wrote:
On 2019-07-21 02:42, Eli Schwartz via arch-general wrote:
How does renaming the file from SHA256.sig to SHA256 help you validate
the contents using signify?
I rename it in the source array:
"SHA256::${_mirrorurl}/${pkgver}/amd64/SHA256.sig"
On 7/21/19 9:19 AM, brent s. wrote:
i can't speak for why it bothers Eli, but it bothers me because that's
exactly what GPG detached sigs are already: signed hash checksums. The
signify method is a signed hash checksum of a (list of) hash
checksum(s). To me it feels like an unnecessary
On Sun, 2019-07-21 at 16:00 +0200, Ralf Mardorf wrote:
> The percent values playing a youtube video with and without enhanced-
> h264ify are raw estimated values
^^
average values ;) based upon the
Hi,
when playing youtube videos hardware video acceleration seems to gain
absolutely nothing on my machine or I've done something wrong ;).
Am I missing something?
The percent values playing a youtube video with and without enhanced-
h264ify are raw estimated values, based upon my impression,
On 7/21/19 4:40 AM, Ralf Mardorf via arch-general wrote:
> On Sun, 21 Jul 2019 02:42:39 -0400, Eli Schwartz via arch-general wrote:
>> The latter problem is why I'm incredibly frustrated by projects that
>> use PGP, too -- when the only thing they sign is a file containing
>> checksums, and not
On Sun, 21 Jul 2019 02:42:39 -0400, Eli Schwartz via arch-general wrote:
>The latter problem is why I'm incredibly frustrated by projects that
>use PGP, too -- when the only thing they sign is a file containing
>checksums, and not the actual source file.
But it doesn't matter, since when the
On 2019-07-21 02:42, Eli Schwartz via arch-general wrote:
> How does renaming the file from SHA256.sig to SHA256 help you validate
> the contents using signify?
I rename it in the source array:
"SHA256::${_mirrorurl}/${pkgver}/amd64/SHA256.sig"
That way makepkg doesn't think it's a PGP
On 7/21/19 2:19 AM, Stephen Gregoratto via arch-general wrote:
I recently adopted the openbsd-manpages package[1], and wanted to verify
downloaded files using OpenBSD's signify(1) tool. For each release of
OpenBSD, you download the base public key[2], the architecture-specific
files and the
I recently adopted the openbsd-manpages package[1], and wanted to verify
downloaded files using OpenBSD's signify(1) tool. For each release of
OpenBSD, you download the base public key[2], the architecture-specific
files and the SHA256.sig[3] for those files.
The files are verified by running:
15 matches
Mail list logo
