On 2018-06-15, Alexandre Ratchov wrote:
> On Fri, Jun 15, 2018 at 09:10:44AM +0200, Maximilian Pichler wrote:
>>
>> For the raw device (rsd1c):
>> $ doas cat /dev/rsd1c | pv -bra -Ss500m | sha1
>> 500MiB [25.5MiB/s] [25.5MiB/s]
>> ca17bdb9a657bbcf654a60057861be8fe02df0b1
>>
>
> I don't
On 2018-06-15, Asbel Kiprop wrote:
> Sooo, current behaviour when i have everything in /home/ with
> "myuser:myuser" ownership and "wheel:*:0:root, myuser" in /etc/group the
> correct one?
That's one common way. As for whether it's "correct", that depends how
you want to administer your system.
On 15/06/2018 00:12, Fred wrote:
I like mythic beasts[1] - they have data centres in Cambridge and London
- they are technically literate and both my OpenBSD VM are with them.
Cheers
Fred
[1]https://www.mythic-beasts.com/
Aha. Looks interesting. Thanks.
Steve
On Thu, Jun 14, 2018 at 08:40:56AM +0300, Максим wrote:
> The first problem is: when I listen to music (cmus) and browse in the
> internet (Firefox) cmus sometimes stops playing for a second.
> This happens when I click a link on a page or receive some notification from
> the web page (which may
No, it is not. boot(8) has no knowledge of usb.
On 2018 Jun 15 (Fri) at 15:18:29 -0400 (-0400), Filippo Valsorda wrote:
:Is boot(8) on amd64 capable of using a ucom(4) device as a console for status
and single user mode? I'd like to control the bootloader on a board without
native serial
On 15/06/18 22:10, Asbel Kiprop wrote:
> Sooo, current behaviour when i have everything in /home/ with
> "myuser:myuser" ownership and "wheel:*:0:root, myuser" in /etc/group the
> correct one?
>
That is correct.
Is boot(8) on amd64 capable of using a ucom(4) device as a console for status
and single user mode? I'd like to control the bootloader on a board without
native serial ports.
I tried "set tty ucom0" per FAQ 7 but it did not work.
I suspect the answer is no, but looking for confirmation, or
Sooo, current behaviour when i have everything in /home/ with
"myuser:myuser" ownership and "wheel:*:0:root, myuser" in /etc/group the
correct one?
пт, 15 июн. 2018 г. в 21:07, Maurice McCarthy :
> On 15/06/18 20:52, Asbel Kiprop wrote:
> > hello @misc!
> > Kinda simple question here, but didnt
On 15/06/18 20:52, Asbel Kiprop wrote:
> hello @misc!
> Kinda simple question here, but didnt fount any answer.
> After fresh install i've created new user, added to 'wheel' group.
> But /home/user/ direstory and everything in it has "user:user" owner, but
> shouldnt it be like "user:wheel"
hello @misc!
Kinda simple question here, but didnt fount any answer.
After fresh install i've created new user, added to 'wheel' group.
But /home/user/ direstory and everything in it has "user:user" owner, but
shouldnt it be like "user:wheel" instead?
sorry for bad english, hope for some help
Hej Steve,
I would recommend Henning Brauer (he is developing pf and OpenBGPD) and
his "BS Web Services" (BSWS) located in germany (so probably no
NSA-Backdoor). A well known OpenBSD-Developer doing ISP cant be
wrong. :)
http://www.bsws.de/en/
Michael
Am Thu, 14 Jun 2018 21:50:00 +0100
Hello,
Yes no problem, here is my dmesg : https://pastebin.com/iB4X5T9M
Regards,
Guillaume.
Le ven. 15 juin 2018 à 15:24, Stephane HUC "PengouinBSD" <
b...@stephane-huc.net> a écrit :
> Please, add your dmesg as explain into FAQ:
>
> https://www.openbsd.org/faq/faq4.html#SendDmesg
>
> ;)
>
> Le
Please, add your dmesg as explain into FAQ:
https://www.openbsd.org/faq/faq4.html#SendDmesg
;)
Le 06/15/18 à 15:12, Guillaume DUALÉ a écrit :
> Hello,
> I just bought this card : TP-LINK TL-WN725N(EU) Ver:3.0
> And it works fine !
>
> In the man of the used driver «urtwn» :
Hello,
I just bought this card : TP-LINK TL-WN725N(EU) Ver:3.0
And it works fine !
In the man of the used driver «urtwn» : http://man.openbsd.org/urtwn only
the version 2 is listed.
So you can add this new version in the list.
If you want I do tests, I can, just ask.
Regards,
Guillaume.
Thanks for the detailed explanation! As both you and Alexandre hinted
at I was using the wrong tool. dd(1) indeed yields the expected speed
on rsd1c. At least for this particular SD card a block size of 64k
appears to be optimal:
$ doas dd if=/dev/rsd1c of=/dev/null bs=32k count=16k
16384+0
I posted this before, and the first time around it was pointed out I had out of
date firmware, that was addressed. Anyway I am on current, the last snapshot I
grabbed was from 6-9. These 2 errors persist in my dmesg:
error: [drm:pid0:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo
On Fri, Jun 15, 2018 at 08:09:40AM +1000, Stuart Longland wrote:
> On 15/06/18 06:50, Steve Fairhead wrote:
> > I gather Amazon are not quite there yet re OpenBSD virtual machines. Can
> > anyone here provide a cluebat as to prospects or alternatives? I don't
> > want to move away from OpenBSD -
Hiya Steve,
On Thu, 14 Jun 2018 21:50:00 +0100 Steve Fairhead wrote:
> ... make the hardware somebody else's problem
Have you considered dedicated hosting, where you rent a real server?
Various people have had success with these firms:
Pulsant (Edinburgh)
IOMart (Glasgow)
ByteMark (York)
Am 15.06.2018 10:27 schrieb Holger Glaess:
ist see the forwarded bootreqest from dhcrelay but it is not possible ,
for me ,
to shift this reqest to an other rdom .
just lift the outgoing (directed) request from dhcrelay with pf?
--
pb
hi
how can i forward the bootrequest from dhcrelay that listen in rdom 5 ,
example , to
rdom 0 where my dhcpd server listen ?
ist see the forwarded bootreqest from dhcrelay but it is not possible ,
for me ,
to shift this reqest to an other rdom .
holger
OpenBSD 6.3 amd64
filebeat 5.6.4p0
Running first step in Filebeat pkg-readme to load the template in
~recent ES results in failure:
#
$OpenBSD: README,v 1.2 2017/04/27 09:14:40 jasper Exp $
+---
| Running filebeat-5.6.4p0
On Fri, Jun 15, 2018 at 09:10:44AM +0200, Maximilian Pichler wrote:
>
> For the raw device (rsd1c):
> $ doas cat /dev/rsd1c | pv -bra -Ss500m | sha1
> 500MiB [25.5MiB/s] [25.5MiB/s]
> ca17bdb9a657bbcf654a60057861be8fe02df0b1
>
I don't understand above commads. If you do:
$ dd if=/dev/rsd1c
Factors that affect speed are:
/dev/sd*
* are cached (cache has a 3GB cap presently since the DMA pushback
diff not was experienced as stable and therefore rolled back), which
may make access appear faster
* I think the underlying hardware access is always split to 512B (or
in
I'm getting much faster read speeds from an SD card when mounting the
card and reading files (~50MB/s) than when reading the raw device
rsd1c (~25MB/s). If anything, shouldn't it be the other way round,
given that the file system has some overhead?
Here are the measurements when mounting and
24 matches
Mail list logo