On Thu, Jun 25, 2020 at 09:51:41PM -0400, sven falempin wrote:
> I have a script that mostly untar stuff on a vnd device.
> And i have the same problem with syspatch
> The program state gets into needbuf forever, ( the top state ).
> I'm trying to figure out what is happening,
chormium-bsu(6) is a fun and hard top down shooter game. Try it out from
the ports. By default the controls are arrow keys and space.
At least try out the first level for 5 miinutes. Spoiler ahead.
You have been warned.
It's hard, right? If you use a
I have a script that mostly untar stuff on a vnd device.
And i have the same problem with syspatch
The program state gets into needbuf forever, ( the top state ).
I'm trying to figure out what is happening,
I have a feeling it may be an entropy exhaustion
but it's just a guess.
On 2020-06-25, Why 42? The lists account. wrote:
> On Wed, Jun 24, 2020 at 09:55:05AM -, Stuart Henderson wrote:
>> > Disable uftdi in your kernel config (boot -c, disable uftdi, quit) and
>> > see if that works. The device is attaching as a serial port, but libftdi
>> > probably wants
the chat script seems working, it got all commands recognized.
For the peer parameters I can provide the following, which works:
/dev/cuaU1 < or /dev/cuaU0
user telekom <--- change to your setting
abort on (BUSY)
abort on (NO CARRIER)
abort on (VOICE)
timeout set to 20 seconds
-- got it
-- got it
On Sun, Jun 21, 2020 at 04:33:14PM -0400, Sonic wrote:
> On Sun, Jun 21, 2020 at 12:11 PM Patrick Wildt wrote:
> > If you want to use a specific address for a policy, you can use the
> > "local" keyword to specify it. This is part of the policy, not a global
> > option.
> > Then iked(8)
On Wed, Jun 24, 2020 at 09:55:05AM -, Stuart Henderson wrote:
> > Disable uftdi in your kernel config (boot -c, disable uftdi, quit) and
> > see if that works. The device is attaching as a serial port, but libftdi
> > probably wants it attaching to ugen. If that helps maybe we can add a
I have several Ryzen 3 and Ryzen 7 systems running OpenBSD 6.6 and
6.7, and they work great. 6.6 had some minor issues with Ryzen 3
graphics but these appear to be resolved in 6.7.
On 6/23/20, Joe Barnett wrote:
> On 2020-06-23 08:56, Gregory Edigarov wrote:
Disclaimer: the topic isn't strictly OpenBSD related, but I'd love
hearing comments from this community.
I'm trying to get used (after a very long long time) to Thunderbird
(mutt user for last 10 years or so...) and I'm struggling with mailing
In partucular, in mutt
yes please provide /etc/ppp/connect-errors as mentioned and also a complete
> -Ursprüngliche Nachricht-
> Von: Whistle
> Gesendet: Donnerstag, 25. Juni 2020 13:31
> An: Kapfhammer, Stefan
> Cc: Misc
> Betreff: Re: E3372: LCP: timeout sending
On 2020/06/25 14:59, Salvatore Cuzzilla wrote:
> Unfortunately the only think i know for sure is that the /var folder is
> constantly loosing free space & When i restart tor it gets back to
> normal. I can't (I don't know how to) figure out the involved files ...
> "du" is not really helping
Unfortunately the only think i know for sure is that the /var folder is
constantly loosing free space & When i restart tor it gets back to
normal. I can't (I don't know how to) figure out the involved files ...
"du" is not really helping nor "fstat" ... Is there anything else
i could test?
no it's not Deutsche Telekom, it giffgaff in uk.
Do you still want the logs ?
Also tried to reboot on a linux image and it switchmode with
usb_switchmode then I rebooted (without detach it and without poweroff
the laptop) in openbsd and I found a ethernet interface (cdce0). I run
On 2020-06-24, Salvatore Cuzzilla wrote:
> After few attempts, I can't still don't understand what's going on
> it seems that the only way to free up the /var folder is to restart the
> tor's daemon.
> "pkill -HUP -u _tor -U _tor -x tor" didn't help ...
> Other ideas?
Did you figure out what
On 2020-06-24, Jan Stary wrote:
> This is current/amd64 on a Sun Fire X2100.
> The boot sequence stops at the "root on wd0a ..." line
> and nothing else happens.
> No, it's not redirecting the console.
> Am I missing something obvious?
> Is anyoney seeing the same?
> Below is the last working
> On Mon, Jun 22, 2020 at 4:24 PM Mogens Jensen
>> +# NOTE: The do_fsck() function has been patched to run 'fsck -y' if an
>> +# automatic file system check fails with exit code 8.
I have quite a few machines patched like this.
On 2020-06-24, Aaron Mason wrote:
> Auto filesystem
do you want to connect to the german 'Deutsche Telekom' ?
Please delete /etc/ppp/connect-errors and make ONE more run with
'pppd call telekom'. Then post this file here.
> -Ursprüngliche Nachricht-
> Von: owner-m...@openbsd.org Im Auftrag
> von Whistle
OpenBSD + Digital Rights Management = <3
Good luck to you community of hypocrites, enjoy pseudo security!
On Wednesday, June 24, 2020 10:58 PM, Aaron Mason
> Auto filesystem repair is bad juju.
Indeed, but an unbootable network appliance thousands of miles away,
is much much worse.
Mail list logo