, the system is reset on timer expiry - so
it is definitely working.
Best Regards,
Strahil Nikolov
OpenBSD 6.7 (GENERIC.MP) #5: Tue Jul 21 13:50:07 MDT 2020
r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8491597824 (8098MB)
avail mem = 8221622272 (7840MB
ogic is the same, then each login can create a separate device and
later just remove it on logout. Yet, from security perspective it could be a
bad solution ...
Best Regards,
Strahil Nikolov
На 2 август 2020 г. 23:42:08 GMT+03:00, Mihai Popescu написа:
>> can somwone explain me ...
>
>
Hi All,
can somwone explain me why all login sessions use /dev/drm0 and not /dev/drm1
or something like that ?
Best Regards,
Strahil Nikolov
На 2 август 2020 г. 18:22:23 GMT+03:00, li...@wrant.com написа:
>Fri, 31 Jul 2020 17:36:53 +0200 Nils Reuße
>> Hi Theo,
>>
>> tha
And if the FS is mounted rw, do you have the issue ?
Best Regards,
Strahil Nikolov
На 11 юли 2020 г. 10:22:53 GMT+03:00, Vertigo Altair
написа:
> Hello Again,
>I followed Stuart's recommendations,
>
>in fstab, / has read-write permissions;
>also, I mounted /dev as ramdisk
'softdep' represents the behaviour of 'write barriers' in Linux ?
Best Regards,
Strahil Nikolov
На 13 юни 2020 г. 19:56:18 GMT+03:00, "Todd C. Miller"
написа:
>On Sat, 13 Jun 2020 12:12:05 -0400, Nick Holland wrote:
>
>> On 2020-06-11 12:07, Strahil Nikolov wrote:
>> &
I always thought that 'sync' mount option is enough to avoid corruption of
the FS.
Am I just "fooling" myself ?
Best Regards,
Strahil Nikolov
На 10 юни 2020 г. 7:46:48 GMT+03:00, Dirk Coetzee написа:
>I have been in a similar situation of power being unreliable and
Hello Community,
did anyone manage to install openBSD on a ASUS c202sa-ys02 chromebook ?
What about any other chromebook?
If yes, would you share some thoughts/warning/recommendations ?
Thanks in advance.
Best Regards,
Strahil Nikolov
he expiration?
>
>Thanks much...
Short googling shows me:
In the case of protocols without "start" and "end" packets, PF simply keeps
track of how long it has been since a matching packet has gone through. If the
timeout is reached, the state is cleared. The timeout values can be set in the
options section of the pf.conf file.
What is your conf having as a timeout ?
Best Regards,
Strahil Nikolov
and sees
>the internal drive as well.
>
>-f
Have you tried to edit the windows boot loader and somehow boot the openBSD?
I have done that approach ages ago where grub was on second disk and I made
windows boot loader (legacy mode) to boot from the next disk and then grub
kicked in.
Of course , you can try the opposite - somehow openBSD to boot the windows :)
Best Regards,
Strahil Nikolov
> might want more than 16 partitions. I stand corrected on that
>> speculation if I'm wrong.
>
>Reality hasn't changed. A sector is still 512 bytes, and
>disklabel has to fit in it.
>
>You are not LISTENING.
Does this mean that with a sector of 4096 (modern HDDs/SSDs) and a patch - we
can have larger disklabel ?
Best Regards,
Strahil Nikolov
gt;>
Some of these e-mails were useful others not...
So, can I setup openBSD labels on x86_64 without legacy/GPT partition first ?
And who the hell needs more than 16 partitions ? Why not we just port ZFS from
FreeBSD, or LVM from Linux and get over it ?
P.S.: The last one was not a real question, but I would like to hear if
anyone has attempted to port any of these 2 .
Best Regards,
Strahil Nikolov
rely host VMs and in such use - ZFS or LVM can be
quite useful.
Best Regards,
Strahil Nikolov
t configured
>> uhidev0 at uhub0 port 3 configuration 1 interface 0 "KINESIS
>FREESTYLE KB800 KB800 Kinesis Freestyle" rev 1.10/1.22 addr 2
>> uhidev0: iclass 3/1
>> ukbd0 at uhidev0: 8 variable keys, 6 key codes
>> wskbd1 at ukbd0 mux 1
>> uhidev1 at uhub0 port 3 configuration 1 interface 1 "KINESIS
>FREESTYLE KB800 KB800 Kinesis Freestyle" rev 1.10/1.22 addr 2
>> uhidev1: iclass 3/0, 3 report ids
>> uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
>> uhid1 at uhidev1 reportid 3: input=2, output=0, feature=0
>> uhub5 at uhub1 port 1 configuration 1 interface 0 "GenesysLogic
>USB2.0 Hub" rev 2.00/92.24 addr 2
>> uhub5: device problem, disabling port 1
>> uhidev2 at uhub5 port 3 configuration 1 interface 0 "Logitech USB
>Receiver" rev 2.00/12.07 addr 3
>> uhidev2: iclass 3/1
>> ukbd1 at uhidev2: 8 variable keys, 6 key codes
>> wskbd2 at ukbd1 mux 1
>> uhidev3 at uhub5 port 3 configuration 1 interface 1 "Logitech USB
>Receiver" rev 2.00/12.07 addr 3
>> uhidev3: iclass 3/1, 8 report ids
>> ums0 at uhidev3 reportid 2: 16 buttons, Z and W dir
>> wsmouse0 at ums0 mux 0
>> uhid2 at uhidev3 reportid 3: input=4, output=0, feature=0
>> uhid3 at uhidev3 reportid 4: input=1, output=0, feature=0
>> uhid4 at uhidev3 reportid 8: input=1, output=0, feature=0
>> uhidev4 at uhub5 port 3 configuration 1 interface 2 "Logitech USB
>Receiver" rev 2.00/12.07 addr 3
>> uhidev4: iclass 3/0, 33 report ids
>> uhid5 at uhidev4 reportid 16: input=6, output=6, feature=0
>> uhid6 at uhidev4 reportid 17: input=19, output=19, feature=0
>> uhid7 at uhidev4 reportid 32: input=14, output=14, feature=0
>> uhid8 at uhidev4 reportid 33: input=31, output=31, feature=0
>> uvideo0 at uhub2 port 4 configuration 1 interface 0 "Chicony
>Electronics USB2.0 VGA UVC WebCam" rev 2.00/99.16 addr 2
>> video0 at uvideo0
>> vscsi0 at root
>> scsibus2 at vscsi0: 256 targets
>> softraid0 at root
>> scsibus3 at softraid0: 256 targets
>> sd1 at scsibus3 targ 1 lun 0: SCSI2
>0/direct fixed
>> sd1: 953868MB, 512 bytes/sector, 1953523553 sectors
>> root on sd1a (6759d2c493c65bb1.a) swap on sd1b dump on sd1b
>> initializing kernel modesetting (KAVERI 0x1002:0x130D 0x1043:0x17FD).
>> radeondrm0: 1366x768, 32bpp
>> wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using
>wskbd0
>> wskbd1: connecting to wsdisplay0
>> wskbd2: connecting to wsdisplay0
>> wsdisplay0: screen 1-5 added (std, vt100 emulation)
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> iridium[2535]: pledge "rpath", syscall 5
>> iridium[32155]: pledge "rpath", syscall 5
>> iridium[15840]: pledge "rpath", syscall 5
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> uhidev5 at uhub0 port 4 configuration 1 interface 0 "vendor 0x
>USB OPTICAL MOUSE" rev 1.10/1.00 addr 3
>> uhidev5: iclass 3/1, 1 report id
>> ums1 at uhidev5 reportid 1: 3 buttons, Z dir
>> wsmouse1 at ums1 mux 0
>> wsmouse1 detached
>> ums1 detached
>> uhidev5 detached
>> iridium[36082]: pledge "rpath", syscall 5
>> iridium[58077]: pledge "rpath", syscall 5
>> iridium[16854]: pledge "rpath", syscall 5
>> uhidev5 at u
Hi Luke,
Have you tried to reuse ssh connections.
In linux you can use something like this:
ControlMaster auto
ControlPath ~/.ssh/sockets/%r@%h-%p
ControlPersist 600
I guess it's still valid for openBSD.
Best Regards,
Strahil Nikolov
an use a backup one in your command.
Yet, I've never done crypto on openBSD - just LUKS on Linux.
Best Regards,
Strahil Nikolov
gt;> pci3 at ppb2 bus 3
>>> re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
>(0x4c00), msi, address b8:ae:ed:34:f1:a7
>>> rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
>>> pcib0 at pci0 dev 31 function 0 "Intel Bay Trail LPC" rev 0x0e
>>> ichiic0 at pci0 dev 31 function 3 "Intel Bay Trail SMBus" rev 0x0e:
>apic 1 int 18
>>> iic0 at ichiic0
>>> spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-10600 SO-DIMM
>>> isa0 at pcib0
>>> isadma0 at isa0
>>> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
>>> pckbd0 at pckbc0 (kbd slot)
>>> wskbd0 at pckbd0: console keyboard
>>> pcppi0 at isa0 port 0x61
>>> spkr0 at pcppi0
>>> it0 at isa0 port 0x2e/2: IT8728F rev 2, EC port 0xa40
>>> vmm0 at mainbus0: VMX/EPT (using slow L1TF mitigation)
>>> efifb at mainbus0 not configured
>>> uhub1 at uhub0 port 2 configuration 1 interface 0 "Genesys Logic
>USB2.0 Hub" rev 2.00/32.98 addr 2
>>> vscsi0 at root
>>> scsibus2 at vscsi0: 256 targets
>>> softraid0 at root
>>> scsibus3 at softraid0: 256 targets
>>> sd2 at scsibus3 targ 1 lun 0:
>>> sd2: 7577604MB, 512 bytes/sector, 15518933033 sectors
>>> root on sd2a (ec7ef108fc3d18e6.a) swap on sd2b dump on sd2b
>>> drm:pid0:connector_bad_edid *WARNING* HDMI-A-2: EDID is invalid:
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>>[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> inteldrm0: 1024x768, 32bpp
>>> wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using
>wskbd0
>>> wsdisplay0: screen 1-5 added (std, vt100 emulation)
>>>
>>
Hi Nick,
Can you test removing '-w 10' from the daemon's flags in order to test with the
default 2min timeout.
I have a vague feeling that 10 seconds is way too short...
Best Regards,
Strahil Nikolov
d the day when so much spam will cover this mailing list.
Don't we have 's...@openbsd.org' for that purpose ? If not, now is the time
to consider creating one.
Anyway, perl is not my favourite - but at least it does the job in a
predictable manner.
Best Regards,
Strahil Nikolov
В неделя, 22 декември 2019 г., 20:15:20 ч. Гринуич+2, Stuart Longland
написа:
On 23/12/19 4:03 am, Strahil Nikolov wrote:
> did anyone try to install openBSD on Raspberry Pi 4B ?
> I know it's not supported , but maybe it does work :)
>Or maybe not as it's a very different So
Hello Misc,
did anyone try to install openBSD on Raspberry Pi 4B ?
I know it's not supported , but maybe it does work :)
Best Regards,
Strahil Nikolov
On November 14, 2019 11:04:15 AM GMT+02:00, Dimitrios Moustos
wrote:
>Hello Strahil,
>
>I get this very often when pf does not allow traffic out.
>First check that pf allows traffic out.
>
>Hope it helps, Dimitrios
>
>On Wed, Nov 13, 2019 at 10:51:45PM +, Strahil
working for you ?
Thanks in advance.
Best Regards,
Strahil Nikolov
d to take a stab at fixing it,
>but my knowledge of pkg_add internals is limited.
Have you checked if anything in pkg_check(8) can help you ?
Source: https://www.openbsd.org/faq/faq15.html
Best Regards,
Strahil Nikolov
ant to try the gui... yet, there are a lot of stuff this
BSD can be used for - from a firewall/router to a full blown Laptop distro.
And Of course, I love the documentation.
Best Regards,
Strahil Nikolov
>I first started using it around version 4.3. I was trying BSD's after
>using Linux for
't matterfor users of the system.If your
>choice of operating system depends on any kind of formalitiesrather
>than on technical quality, OpenBSD is not the project youare looking
>for.Yours, Ingo
I can only add that ,from all the mailing lists I'm subscribed ,
misc@openbsd is the m
On June 19, 2019 8:23:59 AM GMT+03:00, Theo de Raadt
wrote:
>Strahil Nikolov wrote:
>
>> I was wondering if CVE-2019-5598 is actually affecting openBSD. I'm
>> asking as FreeBSD is usually several versions behind and this one
>> might not affect PF in recent op
Hi All,
I was wondering if CVE-2019-5598 is actually affecting openBSD.
I'm asking as FreeBSD is usually several versions behind and this one might not
affect PF in recent openBSD versions.
Best Regards,
Strahil Nikolov
On May 4, 2019 10:11:07 AM GMT+03:00, Nick Holland
wrote:
>On 5/3/19 2:32 PM, Strahil Nikolov wrote:
>> On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland
>> wrote:
>>> On 5/2/19 1:52 AM, Consus wrote:
>>>> Hi,
>>>>
>>>> I've upgraded
stem upgrade is a very complicated and error prone procedure.
P.S.: No offence here, just sharing my thoughts.
Best Regards,
Strahil Nikolov
Great.
What about CPU/RAM usage. Do you believe it will be possible to report it to
the management layer ?
If not - there will be no use of qemu-ga at all on openBSD.
Best Regards,
Strahil Nikolov
On April 29, 2019 2:49:43 PM GMT+03:00, Stuart Henderson
wrote:
>On 2019-04-29, Stra
4AM +0000, Strahil Nikolov wrote:
>> Hi All,
>> I am new to openBSD and I really like the idea. Sadly I do not have
>> suitable hardware to run on , thus I use KVM and I would be happy if
>> anyone hint me of a working solution for Qemu Guest Agent.
>> Anything I dig
our life easier.
Best Regards,
Strahil Nikolov
On April 29, 2019 12:07:32 AM GMT+03:00, Tom Smyth
wrote:
>Hello Strahil,
>what are you trying to achieve with the Qemu Guest Agent ?
>
>is it quiescing during backups .>?
>
>
>
>
>
>
>On Sun, 28 Apr 201
is well appreciated.
Best Regards,Strahil Nikolov
to be polite , despite the attitude of the opposite side.
Best Regards,
Strahil Nikolov
В неделя, 28 април 2019 г., 6:29:53 ч. Гринуич-4, Anders Andersson
написа:
On Sun, Apr 28, 2019 at 10:04 AM Martijn van Duren
wrote:
>
> You mean something like this the following?
> https://www.op
Hello All,
can someone point me to the link of the OpenBSD code of Conduct ?
It seems that I can't find it even with the help of google.
Best Regards,
Strahil Nikolov
33 matches
Mail list logo
