On Wed, 25 Aug 2021 at 9:28 PM, Stuart Henderson
wrote:
> On 2021-08-24, Error@Oddprotocol wrote:
> > hi all
> > i have been trying to use some tcl script for an eggdrop on openbsd 6.9
> > and im getting the following error
> >
> > Error: error reading
On 2021-08-24, Error@Oddprotocol wrote:
> hi all
> i have been trying to use some tcl script for an eggdrop on openbsd 6.9
> and im getting the following error
>
> Error: error reading "sock7": Unknown error: 50327587
>
>
> i have tested the same script on ot
hi all
i have been trying to use some tcl script for an eggdrop on openbsd 6.9
and im getting the following error
Error: error reading "sock7": Unknown error: 50327587
i have tested the same script on other linux distro and they/it works fine.
i think there is a some dependency or l
Hi,
I have a Toshiba laptop with double internal pointing device (pointer
stick and touchpad) to which I attach via USB a classic Logitech M100
mouse, wired. The mouse is working on other computers and if I enable
legacy mode, I can even use it in the BIOS to click around, so I am sure
"it c
I have a running openbsd installation on hetzner without problems.
IIRC had bought a server with one of the default Linux distributions, webt to
server settings and there somehow mounted the openbsd iso and follow the
regular openbsd install on the virtual console.
It's the regular installation a
On 22.7.2021. 16:33, Matthias Schmidt wrote:
> Hi,
>
> * Hrvoje Popovski wrote:
>> Hi all,
>>
>> I'm thinking of getting Hetzner cloud server and install OpenBSD stable
>> on it...
>>
>> Does anyone have experience with it? Is it complicated to install
>> OpenBSD on it? And of course, is it stable
q
Hi,
* Hrvoje Popovski wrote:
> Hi all,
>
> I'm thinking of getting Hetzner cloud server and install OpenBSD stable
> on it...
>
> Does anyone have experience with it? Is it complicated to install
> OpenBSD on it? And of course, is it stable?
I ran OpenBSD -stable on a Hetzner cloud server (prev
On Thursday, July 22nd, 2021 at 2:06 PM, Hrvoje Popovski wrote:
> Hi all,
>
> I'm thinking of getting Hetzner cloud server and install OpenBSD stable
>
> on it...
>
> Does anyone have experience with it? Is it complicated to install
Been using one since about 3 years, so far no problem running
Hi all,
I'm thinking of getting Hetzner cloud server and install OpenBSD stable
on it...
Does anyone have experience with it? Is it complicated to install
OpenBSD on it? And of course, is it stable?
Thank you
On Thu, Jun 24, 2021 at 02:56:16PM -0600, Theo de Raadt wrote:
> > I think the easiest path here is to incorporate the new upstream into a
> > port, unless someone is familiar with zlib and can cherrypick out the
> > commit(s) that resolve the issue. (I didn't find zlib in ports already.)
>
> That
On 2021-06-25, Theo Buehler wrote:
> If we want to go the cherry-picking route, here's a diff that fixes the
> test.csv.gz test case provided in the linked issue.
No objection to this (it won't make a future sync much harder, there
are already many changes in openbsd-zlib compared to the more com
On Thu, Jun 24, 2021 at 10:41 PM Sebastien Marie wrote:
> On Thu, Jun 24, 2021 at 08:04:37PM -0600, Matt Dowle wrote:
> >
> > > It is NOT 16 years old. You keep saying that. There is a different
> > development
> > process involved here which has upsides and downsides and which I don't
> > expe
On Thu, Jun 24, 2021 at 08:04:37PM -0600, Matt Dowle wrote:
>
> > It is NOT 16 years old. You keep saying that. There is a different
> development
> process involved here which has upsides and downsides and which I don't
> expect
> you will understand.
>
> That's right. I don't understand.
> Co
On Thu, Jun 24, 2021 at 11:09:05AM -0600, Matt Dowle wrote:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> B
> So feisty.
Seriously?
On Thu, Jun 24, 2021 at 8:33 PM Theo de Raadt wrote:
> Matt Dowle wrote:
>
> > That's right. I don't understand.
> > Could you explain it then, or point me to a document that explains what
> > your development process is?
> > Putting two and two together, it seems that
Matt Dowle wrote:
> That's right. I don't understand.
> Could you explain it then, or point me to a document that explains what
> your development process is?
> Putting two and two together, it seems that it is 16 years plus a bunch of
> cherry picked bug fixes backported over a very many years.
> I don't know either.
> That is what I am asking.
I'm not going to spend more time investigating a bug fix in zlib made 15
years ago. If that's what your policy is, then we have provided plentiful
pointers for you to do so.
> Yes, you keep saying we should just throw the new code in, and you kee
Matt Dowle wrote:
> Theo,
>
> > Instead, we got pages and pages that summarize to "must
> update", and doesn't explain what the bug is or what the fix is.
>
> > If only we had an explanation of what is actually wrong and needs fixing
>
> We know it was this news item from 1.2.3.1 (released 16
Theo,
> Instead, we got pages and pages that summarize to "must
update", and doesn't explain what the bug is or what the fix is.
> If only we had an explanation of what is actually wrong and needs fixing
We know it was this news item from 1.2.3.1 (released 16 August 2006)
https://zlib.net/Change
On 2021-06-24, Dave Voutila wrote:
> I'm in 100% agreement it sucks and it's something I believe is already
> done for ports that require OpenSSL.
Only for ports which require OpenSSL and don't require a library
which pulls in LibreSSL. For example we are now stuck on updating
Postfix (thanks to
Dave Voutila wrote:
> Theo de Raadt writes:
>
> > Dave Voutila wrote:
> >
> >> Theo de Raadt writes:
> >>
> >> >> I think the easiest path here is to incorporate the new upstream into a
> >> >> port, unless someone is familiar with zlib and can cherrypick out the
> >> >> commit(s) that resolve
Theo de Raadt writes:
> Dave Voutila wrote:
>
>> Theo de Raadt writes:
>>
>> >> I think the easiest path here is to incorporate the new upstream into a
>> >> port, unless someone is familiar with zlib and can cherrypick out the
>> >> commit(s) that resolve the issue. (I didn't find zlib in port
On 2021-06-24, Theo de Raadt wrote:
>> I think the easiest path here is to incorporate the new upstream into a
>> port, unless someone is familiar with zlib and can cherrypick out the
>> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
>
> That is completely impossible. It
Matt Dowle wrote:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> Background here: https://github.com/Rdata
Dave Voutila wrote:
> Theo de Raadt writes:
>
> >> I think the easiest path here is to incorporate the new upstream into a
> >> port, unless someone is familiar with zlib and can cherrypick out the
> >> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
> >
> > That is comp
Theo de Raadt writes:
>> I think the easiest path here is to incorporate the new upstream into a
>> port, unless someone is familiar with zlib and can cherrypick out the
>> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
>
> That is completely impossible. It must be in
> I think the easiest path here is to incorporate the new upstream into a
> port, unless someone is familiar with zlib and can cherrypick out the
> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
That is completely impossible. It must be in base. There are 3 copies
in ba
Matt Dowle writes:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> Background here: https://github.com/Rdata
On Sun, June 20, 2021 23:15, Nenhum_de_Nos wrote:
> On Sun, June 20, 2021 20:34, Nenhum_de_Nos wrote:
>> Hi,
>>
>> I updated my rpi 3B to 6.9 and after that I got this messages:
>>
>> axen0: watchdog timeout
>> axen0: usb error on tx: IN_PROGRESS
>> axen0: usb error on tx: TIMEOUT
>>
>> and the NIC
Hi,
Is it intentional or is there any good reason that OpenBSD 6.9 released May
2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
version v1.2.11 (Jan 2017) is 4 years old.
Background here: https://github.com/Rdatatable/data.table/pull/5049
Best,
Matt
Maintainer of
never happened, and I had several days uptime.
>
> Is this a known bug?
I tried here to ifconfig down and up it, and it got back to work. Will
wait till tomorrow if it repeats the behavior.
matheus
> dmesg:
>
> rpi3_obsd$ dmesg
> OpenBSD 6.9 (GENERIC.MP) #0: Thu May 20 02:2
d the cvs web and saw no changes on if_axen after 6.8 was released.
This box has 1 day uptime and this is the second time I get this. On 6.8
this never happened, and I had several days uptime.
Is this a known bug?
dmesg:
rpi3_obsd$ dmesg
OpenBSD 6.9 (GENERIC.MP) #0: Thu May 20 02:29:27 MDT 2021
rrect. When boot fails the last line I see before losing display is:
radeondrm0: CYPRESS
Snapshot dmesg from successful boot with radeondrm enabled:
OpenBSD 6.9-current (GENERIC.MP) #29: Fri May 21 13:20:08 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
rea
em is fine only when
using X the system freeze.
Any suggestions would be great.
Thanks
Jacky
OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 33679724544 (32119MB)
avail mem = 32643620864 (31131MB)
ra
On 2021-05-18, Steve Williams wrote:
> Hi,
>
> When I upgraded to OpenBSD 6.9 then did the pkg_add -u, I got
> php-php-7.4.18 installed.
>
> How do I know if it's "safe" to delete the old php-7.3.28 and all the
> associated modules?
>
> I know I'l
Am 17.05.21 18:20 schrieb Steve Williams:
> Hi,
>
> When I upgraded to OpenBSD 6.9 then did the pkg_add -u, I got php-php-7.4.18
> installed.
>
> How do I know if it's "safe" to delete the old php-7.3.28 and all the
> associated modules?
You will have to
Hi,
When I upgraded to OpenBSD 6.9 then did the pkg_add -u, I got
php-php-7.4.18 installed.
How do I know if it's "safe" to delete the old php-7.3.28 and all the
associated modules?
I know I'll have to migrate my ".ini" file changes to the new version
for b
When I start the PCB program on OpenBSB 6.9 then the window is only open
for a short moment.
Running PCB from the terminal is giving this message:
openbsd7$ pcb
(pcb:82167): Gtk-CRITICAL **: 12:25:03.067: IA__gtk_window_resize:
assertion 'width > 0' failed
(pcb:82167): Gtk-CRITICAL **: 12
Hi,
Do you mean packages upgrade by using command:
$ doas pkg_add -uvi ?
If yes, you can remove failed packages for upgrade and reinstall them manually
by the command:
$ doas pkg_add package_name
Martin
‐‐‐ Original Message ‐‐‐
On Wednesday, May 12, 2021 9:06 AM, Артём Мазуров
wrot
Den ons 12 maj 2021 kl 11:29 skrev Артём Мазуров :
> Hello.
> I'm trying to upgrade ports after upgrading os to 6.9, but I get a lot
> >|library ssl.48.2 not found
> >| /usr/lib/libssl.so.48.1 (system): minor is too small
> >| /usr/lib/libssl.so.49.0 (system): bad major
This usually means the pkg_
Hello.
I'm trying to upgrade ports after upgrading os to 6.9, but I get a lot
of failures from various packages and I don't know how to approach them.
One of those packages is python-3.8.6p0 -> python-3.8.8p0.
>quirks-4.9 signed on 2021-05-11T16:31:32Z
>Can't install python-3.8.8p0 because of libr
On 2021-05-10, Roger Marsh wrote:
> After upgrading to OpenBSD 6.9 'ValueError: ZIP does not support timestamps
> before 1980' exceptions started occuring when installing python packages by:
>
> 'python3.8 setup.py install --user' where the package was built b
After upgrading to OpenBSD 6.9 'ValueError: ZIP does not support timestamps
before 1980' exceptions started occuring when installing python packages by:
'python3.8 setup.py install --user' where the package was built by:
'python3.8 setup.py sdist --formats gztar'
Hello,
I'm running 6.9 fresh install with cwm on Thinkpad P50, OS freeze after
5 to 10 min of use, on text mode the system is fine only when using X
the system freeze.
Any suggestions would be great.
Thanks
Jacky
OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
dera...@
Thank you
You are right
Irshad
> On 8 May 2021, at 11:55 AM, Stuart Henderson wrote:
>
> On 2021-05-07, Irshad Sulaiman wrote:
>> Hi
>>How to set only one default gateway if I have multiple interface , one is
>> in DHCP and other in Static ip
>> I have set /etc/mygate 192.168.100.
On 2021-05-07, Irshad Sulaiman wrote:
> Hi
> How to set only one default gateway if I have multiple interface , one is
> in DHCP and other in Static ip
> I have set /etc/mygate 192.168.100.1 and hostname.em0 (DHCP) and
> hostname.iwn0 (static 192.168.100.163 255.255.255.0)
Sounds like you
Both in different Network , Just added route to hostname.if with -priority
lower than other interface , it worked
Thank you
> On 08-May-2021, at 5:08 AM, Daniel Jakots wrote:
>
> On Sat, 8 May 2021 02:37:41 +0300, Irshad Sulaiman
> wrote:
>
>> Thank you for the reply
>>
>>
>>
Thank you for the reply
I could do by
Delete and adding route with route command manually
But is there any better way to do this
> On 08-May-2021, at 2:28 AM, wrote:
>
>> How to set hostname.iwn0 as default gateway
>
> Probably there is a better solution. Maybe someon
> How to set hostname.iwn0 as default gateway
Probably there is a better solution. Maybe someone with more
knowledge of netstart can help. I'd try my luck with pf and create
a natting rule to check for traffic leaving em0 that's not - for
example - 192.168.1.0/24:
pass out on em0 from $int_net to
Hi
How to set only one default gateway if I have multiple interface , one is
in DHCP and other in Static ip
I have set /etc/mygate 192.168.100.1 and hostname.em0 (DHCP) and hostname.iwn0
(static 192.168.100.163 255.255.255.0)
But when I sh /etc/netstart it sets multiple gateway with follow
On Sat, 8 May 2021 02:37:41 +0300, Irshad Sulaiman
wrote:
> Thank you for the reply
>
>
> I could do by
> Delete and adding route with route command manually
> But is there any better way to do this
If you used the same network both on wired and wireless, you could use
a trun
Love song and theme, no lyrics for this one.
Jean-François
Le 01/05/2021 à 12:49, Oliver Marugg a écrit :
Hi
@Developers: Many thanks for this new release.
@all others and me: Before upgrading your boxes, this is a good moment
to donate some bucks to this project again.
Have a smooth upgr
Hi
@Developers: Many thanks for this new release.
@all others and me: Before upgrading your boxes, this is a good moment
to donate some bucks to this project again.
Have a smooth upgrade.
-oliver
- OpenBSD 6.9 RELEASED -
May 1, 2021.
We are pleased to announce the official release of OpenBSD 6.9.
This is our 50th release. We remain proud of OpenBSD's record of
On Wed, Apr 28, 2021 at 04:38:35PM +0800, Fung wrote:
> OpenBSD 6.9 RAID 1C (encrypted raid1) softraid discipline can't boot
>
> OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
>
> one disk, shell create RAID CRYPTO, install system ok, boot ok
> two di
OpenBSD 6.9 RAID 1C (encrypted raid1) softraid discipline can't boot
OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT 2021
one disk, shell create RAID CRYPTO, install system ok, boot ok
two disk, shell create RAID 1, install system ok, boot ok
two disk, shell create RAID 1C ok, in
57 matches
Mail list logo
