On 7/1/24 12:49, Edward Toroshchyn wrote:
Then try `mplayer -ao alsa:device=hw=2` (again, 2 is the card number).
Hah!,
That worked:
$ mplayer -ao alsa:device=hw=0 -loop 0 -playlist
http://playerservices.streamtheworld.com/pls/KDAQHD2.pls
Though I'm quite curious why since this is card
On 7/1/24 05:36, Genes Lists wrote:
The new openssh works just fine and this is just a little note to those
of us with remote machines.
After updating both client and remote machine(s) its important to
restart sshd.
If you don't restart sshd, and then attempt to ssh into the remote, it
may fai
On Mon, 1 Jul 2024 20:57:31 +0200
mpan wrote:
> > (…) If you don't restart sshd, and then attempt to ssh into the remote,
> > it may fail with: (…)
>Note that one *must* restart sshd regardless. Updating the files
> isn’t fixing the vulnerability. The old, vulnerable version of the
> proc
(…) If you don't restart sshd, and then attempt to ssh into the remote,
it may fail with: (…)
Note that one *must* restart sshd regardless. Updating the files
isn’t fixing the vulnerability. The old, vulnerable version of the
process is still running until the service is restarted.
Cheers
Peter,
I understand you don't have much experience with Docker, and you totally
don't have to use it, especially if you don't plan to use it for more
advanced purposes, such as actual deployment of your production envs.
You could just download the binary archives with the JDK and JRE versions
you
David,
Try the following. Use `aplay -l` to find the hardware ID which you want to
use, e.g. in my case I want to use card number 2:
```
card 2: prime [Dr.DAC prime], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
Then run `alsamixer -c 2` (2 is the card numbe
On Mon, Jul 01, 2024 at 12:59:05 +0200, Geert Hendrickx wrote:
> More specifically, the upgraded server logs the following:
> sshd: -R not supported here
>
> (when forked by a not-restarted master process)
>
> I can't immediatly spot in the ChangeLog what is causing this, but it
> certainly warra
On Mon, Jul 01, 2024 at 06:36:50 -0400, Genes Lists wrote:
> After updating both client and remote machine(s) its important to
> restart sshd.
>
> If you don't restart sshd, and then attempt to ssh into the remote,
> it may fail with:
>
>kex_exchange_identification: read: Connection reset by
The new openssh works just fine and this is just a little note to those
of us with remote machines.
After updating both client and remote machine(s) its important to
restart sshd.
If you don't restart sshd, and then attempt to ssh into the remote, it
may fail with:
kex_exchange_identificatio
Hello Edward,
thank You for Your reply. In the mean time I could solve the problem
after noticing the missing version id in the update package by addition
of these lines in my pacman.conf:
IgnorePkg = openjdk-doc openjdk-src
IgnorePkg = jre-openjdk jdk-openjdk jre-openjdk-headless
This g
10 matches
Mail list logo
