https://homeservershow.com/forums/forum/217-microserver-gen10-plus/ is a
good resource for this server (although I doubt anyone over there has
tried OpenBSD on it). It should run fine on OpenBSD, the only issue is
it doesn't have a NVME slot, you'll have to boot off a usb stick if you
don't
readahead [readah...@protonmail.com] wrote:
> Hello,
>
> I'm currently considering purchasing a HPE ProLiant MicroServer Gen10 Plus.
> The machine is to be used mostly as a home NAS (OpenBSD, softraid(4)
> encryption and Samba).
>
> Is this a right machine to run OpenBSD on? Can you please
On Tue, Jan 18, 2022 at 04:37:00PM +0100, Harald Dunkel wrote:
> On 2022-01-17 18:02:25, Marc Espie wrote:
> >
> > Lol.
> >
> > cert.pem only contains public certificates. Insisting on only root being
> > able to read it means you are going to run code as root which doesn't
> > require
> > it.
On Tue, Jan 18, 2022 at 04:37:00PM +0100, Harald Dunkel wrote:
> On 2022-01-17 18:02:25, Marc Espie wrote:
> >
> > Lol.
> >
> > cert.pem only contains public certificates. Insisting on only root being
> > able to read it means you are going to run code as root which doesn't
> > require
> > it.
On 2022-01-17 18:02:25, Marc Espie wrote:
Lol.
cert.pem only contains public certificates. Insisting on only root being
able to read it means you are going to run code as root which doesn't require
it. That seems way more unreasonable than your original assumption.
I am not arguing about
On Jan 15 11:03:10, dera...@openbsd.org wrote:
> I think the bug is that com_acpi_match() should call ic/com.c comprobe1(),
> which verifies that an actual chip exists, rather than simply trusting the
> ACPI tables. If attach succeeds, open and ioctl become callable, and at
> that point if real
Today's mails to misc@ are bouncing back with
misc@openbsd.org: Network error on destination MXs
Jan
On Jan 17 15:49:08, mailer-dae...@stare.cz wrote:
> Hi!
>
> This is the MAILER-DAEMON, please DO NOT REPLY to this email.
>
> A message is delayed for more than 4 hours for
On Jan 14 19:10:32, kolip...@exoticsilicon.com wrote:
> On Fri, Jan 14, 2022 at 10:41:52PM +0100, Jan Stary wrote:
> > I suspect it's com1; I have yet to try commenting out just tty01.
> > But commenting out both makes it boot OK.
> >
> > com0 at acpi0 COMA addr 0x3f8/0x8 irq 4: ns16550a, 16 byte
8 matches
Mail list logo
