On 2022-12-12, Randall Gellens wrote:
> Changing the /etc/hostname.if files for the U-Verse and client ports to
> add an 'inet' line with a dummy IP address made it all start working.
> Before, they just had a line with "description" and text.
> Questions:
>
> (1) I'd like to understand the
On 2022-12-11, void wrote:
> Hello misc@
>
> I get the following error when trying to install go (for mips64/octeon):
>
> # pkg_add go
> quirks-6.42 signed on 2022-10-08T21:12:07Z
> Ustar
>
On Sun, Dec 11, 2022 at 04:10:41PM -0800, Jeremy Mates wrote:
> ...
> 42136 ex RET read -1 errno 35 Resource temporarily unavailable
> 42136 ex CALL read(0,0x3d94b585400,0xff)
> 42136 ex RET read -1 errno 35 Resource temporarily unavailable
> 42136
On Sun, Dec 11, 2022 at 04:20:53PM -0800, Randall Gellens wrote:
> I have a Protectli box that is the router for my home network. The home
> network uses U-Verse to connect to the outside, and has separate Ethernet
> networks for servers, wired clients, and Wi-Fi IoT clients. U-Verse supplies
>
Hi All,
Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> # sysupgrade -s -n
> Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/
> SHA256.sig 100%
>
retry, and all should be ok.
On Mon, Dec 12, 2022 at 7:18 AM Why 42? The lists account.
wrote:
>
>
> Hi All,
>
> Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> > # sysupgrade -s -n
> > Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/
> > SHA256.sig 100%
On 2022-12-12 10:01:05 +0100, Claudio Jeker wrote:
> I think this is the wrong way around. The callers need to be fixed to pass
> a blocking stdin to programs since that is what every unix utility
> expects. What you propose it to fix every unix utility to have such a check
> at the start of main.
On 2022-12-12, Amit Kulkarni wrote:
> retry, and all should be ok.
No, there is a problem with the files.
>> I have never really used signify before, but this command from the man
>> page also generates an error:
>> > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p
>> >
On Mon, Dec 12, 2022 at 07:39:49AM -0600, Amit Kulkarni wrote:
> retry, and all should be ok.
What's the basis of your statement, did something change?
It still fails for me (now @16:15 CET).
I also tried a different mirror, same failure (below).
@Stuart: Although sysupgrade output says that
PS: An update - I have updated the bios on the lenovo L13 gen 3 and, of
course, it continues to give trouble.
If anyone has one of these modern thinkpads and comes up with a magic
combination of MS switches in the BIOS to switch off/on which allows S3 to
work again, I would be very thankful if you
Claudio Jeker wrote:
> I think this is the wrong way around. The callers need to be fixed to pass
> a blocking stdin to programs since that is what every unix utility
> expects. What you propose it to fix every unix utility to have such a check
> at the start of main. Sorry but no.
That's
Thanks for the detailed review Martijn,
I'll follow up with the vendors and see if they can address the issue with a
firmware update.
On Sat, Dec 10, 2022, at 01:42, Martijn van Duren wrote:
> On Fri, 2022-12-09 at 13:35 -0700, Byron Klippert wrote:
>> On Fri, Dec 9, 2022, at 12:57, Stuart
Hey folks,
I noticed this line in the VMM FAQ (
https://www.openbsd.org/faq/faq16.html#VMMnet):
"...the IEEE 802.11 standard prevents wireless interfaces from
participating in network bridges."
Just wanted to confirm what is meant by this - are we just trying to say
that WDS isn't part of the
On Mon, Dec 12, 2022 at 08:52:28AM -, Stuart Henderson wrote:
This *shouldn't* break like this, but it's possible that if writing to
the filesystem is very slow you have a timeout fetching the file. (The go
package has a *lot* of small files and with the default mount options,
creating a
Hi Cory,
Just to clarify, bridging typically works from a wireless Access Point
ie bridging a wirieless access point to an ethernet interface and vice
versa
that (should) work and is catered for in the 802.11 standard.
however a wireless interface in station / client mode bridged to an
ethernet
On 2022-12-12, c0ry wrote:
> Hey folks,
>
> I noticed this line in the VMM FAQ (
> https://www.openbsd.org/faq/faq16.html#VMMnet):
>
> "...the IEEE 802.11 standard prevents wireless interfaces from
> participating in network bridges."
>
> Just wanted to confirm what is meant by this - are we just
On Mon, Dec 12, 2022 at 08:52:28AM -, Stuart Henderson wrote:
Or you maybe able to workaround by downloading the package and installing
it from local atorage rather than over the network.
Yes this worked. After downloading it, ran "pkg_add -v -v -m go-1.19.1p0.tgz"
which installed it.
On 12 Dec 2022, at 2:31, Zé Loff wrote:
On Sun, Dec 11, 2022 at 04:20:53PM -0800, Randall Gellens wrote:
I have a Protectli box that is the router for my home network. The
home
network uses U-Verse to connect to the outside, and has separate
Ethernet
networks for servers, wired clients, and
Hi misc@
I'd like to have it so a pppoe FTTP connection doesn't automatically
obtain and apply the ISP's nameservers to /etc/resolv.conf. The machine
already runs unbound, so resolv.conf has loopback for ipv4 and ipv6 in
it. pppoe adds "nameserver isp.name.server.addr # resolvd: pppoe0" at
the
On Tue, Dec 13, 2022 at 01:32:53AM +, void wrote:
> Hi misc@
>
> I'd like to have it so a pppoe FTTP connection doesn't automatically
> obtain and apply the ISP's nameservers to /etc/resolv.conf. The machine
> already runs unbound, so resolv.conf has loopback for ipv4 and ipv6 in
> it. pppoe
On Tue, Dec 13, 2022 at 12:59:10PM +1100, Jonathan Gray wrote:
It can be avoided by disabling resolvd. In /etc/rc.conf.local:
resolvd_flags=NO
Thank you! (for the explanation also)
--
On 12/12/22 07:22, Why 42? The lists account. wrote:
Hi All,
Today sysupgrade failed for me, but I'm not sure why? Here's the output:
[ ... ]
There is a problem with the distribution network currently. Hopefully
will be resolved soon.
Doing a quick check, looks like only amd64 is
On Mon, Dec 12, 2022 at 8:19 AM Stuart Henderson
wrote:
>
> On 2022-12-12, Amit Kulkarni wrote:
> > retry, and all should be ok.
>
> No, there is a problem with the files.
>
Sorry for that Robb and Stuart.
Hi,
I wanted to clarify.
In manpage for rdist I see that we can use option -o remove .
remove Remove extraneous files. If a directory is being
updated, any files that exist on the remote host that do
not exist in the master directory are removed. This
Hello,
I have a question regarding: set skip on in pf.conf(5).
I have a host that has a number of dynamic virtual interfaces. I don't
want my ruleset to apply to those interfaces, however, as they are
created and removed dynamically, I don't know what the numbers will be
assigned to those
Am 13.12.2022 06:02 schrieb J Doe:
set skip on { lo0, vif* }
in pf.conf(5) the GRAMMAR shows:
ifspec = ( [ "!" ] ( interface-name | interface-group ) ) |
"{" interface-list "}"
So you could do "set skip on { lo0 vif0 vif1 }" for explicit, or you
use
Den sön 11 dec. 2022 kl 17:42 skrev void :
> Alternatively, is it feasible to build an amd64 vm and cross-compile
> there, for mips64/octeon?
I think it is. I think I have tried it for simpler stuff but unless I
am very mistaken you just set GOARCH and fire off the build, then move
the binary
27 matches
Mail list logo
