On Sun, Dec 15, 2019 at 08:29:42PM +, Tom Smyth wrote:
> Hi Denis,
>
> ok ..I hadnt read your email fully sorry about that...
>
> what are you trying to achieve here?
>
> you have a 172.16.0.249/30 address on em3 which includes
> 172.16.0.248-127.16.0.251
>
> and then you have a 172.16.0.
On Sun, Dec 15, 2019 at 08:57:48PM +0100, Denis Fondras wrote:
> Hi,
>
> I have this setup :
>
> em3: flags=8843 mtu 1500
> lladdr
> index 4 priority 0 llprio 3
> media: Ethernet autoselect (1000baseSX full-duplex)
> status: active
> inet6 fe80::aa9:b803:8
On Mon, Dec 16, 2019 at 10:55:17AM +0530, putridsou...@gmail.com wrote:
> Currently I'm running the -stable OPENBSD-6.6
> I want to set up the ports repository so
> I followed the faqs to set up a /usr/ports partition,
> changed the group to wsrc and file modes to 775.
> Then I added my local user
The error does not seem to be a faulty mouse and I
don't use a KVM switch anyway so it is not the source.
Following on pervious reply, I tried on a new mouse.
But was greeted with the same error:
wsmouse0 detached
ums0 detached
uhidev0 detached
uhidev0 at uhub0 port 4 configuration 1 interface 0
I get similar stuff on console 1 but not on the others on all my
OpenBSD machines. As I use X windows and have clean consoles 2-4
available if necessary, I just ignore it.
Dave Raymond
On 12/16/19, putridsou...@gmail.com wrote:
> The error does not seem to be a faulty mouse and I
> don't use a
USB subsystem bugs.
Whoever said it was your mouse or cable is being an inaccurate jerk.
Raymond, David wrote:
> I get similar stuff on console 1 but not on the others on all my
> OpenBSD machines. As I use X windows and have clean consoles 2-4
> available if necessary, I just ignore it.
>
>
Hello misc,
Background: I'm running OpenBSD i386 6.6 stable:
$ uname -mrsv
OpenBSD 6.6 GENERIC.MP#3 i386
I've found that mkdir("/", mode) sets errno to EISDIR. Is this intended?
By reading the manpage I expected mkdir(2) to fail with EEXIST.
I know it's a bit silly to mkdir /, b
On Sun, Dec 15, 2019 at 12:28 PM Nick Holland
wrote:
>
> Well...yeah.
> If the boot loader echoed anything, it's behaving As Desired -- a char at
> the command line means "STOP ALL BOOTING, I have something special I want
> you to do".
>
> [...]
> However, I think there are a few things you might
On 12-16 10:48, Raymond, David wrote:
> I get similar stuff on console 1 but not on the others on all my
> OpenBSD machines. As I use X windows and have clean consoles 2-4
> available if necessary, I just ignore it.
I get similar messages in dmesg (used to be on the first console),
and every coup
Hello,
I tried SR-IOV and intel I350 1Gb/s nic hardware being passed through
to OpenBSD 6.6 amd64
the intel i350 passed through as a physical function on PCI-E is
detected as an em(4) nic
and these dont suffer from the same jitter as the IXL(4) or the
AVF(4) drivers
so i'm thinking there is so
10 matches
Mail list logo
