Hi there!
I need help or some hints on how to proceed:
My system a laptop running amd64-current fully encrypted, key-based. I start
from BIOS, not UEFI.
Two days ago I updated to the then latest snapshot and apparently s.th. went
wrong: At reboot the system stops after
>> OpenBSD/amd64 BOOT
Hi,
I've yet to stumble upon the first provider which actually uses OpenBSD
as the hypervisor, instead of VMware, Xen, KVM, etc. That, in fact,
would be an awesome development. I have been thinkering with this
thought back and forth, but the IT company I work for isn't big enough
to facilitate
Thanks for the info, I got a picture there needs to be a default one
from last thread. Ill read docs more carefully next time.
On Thu, Mar 8, 2018 at 8:49 AM, Maurice McCarthy wrote:
> On 08/03/18 05:16, Luka Kosanovic wrote:
>> Hi, Im a new user and I have a problem with
We all know Bare metal is more secure (ignoring physical security)
especially with OpenBSD but if you need cost effective global resources
on tap then I believe you need cloud.
We all know microsoft have a huge user base and userland issues that
are problematic however despite some recent Linux
Cloud poses a risk to privacy that you cannot and must not ignore in business.
Ignore everyone that says otherwise. --- If you are a fabless company, for
example, it is easy for a cloud sysadmin to exploit the latest vulnerabilities
to read your data bank and sell your secrets. Email (yahoo,
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
Von: Kevin Chadwick
Gesendet: Donnerstag, 8. März 2018 17:28
An: misc@openbsd.org
Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
On Thu, 8 Mar 2018 14:47:43 +0100
> Has anyone a clue what might have happend
hi
i working out my ideas for modelling my home network,
the network will have four vether interfaces to cover the needs of my
firewall,
which will have a lan, demilitarised zone, carp redundancy and
connection to the wan,
should i bridge all four vether interfaces to one bridge or a
Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
> Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
>> Gesendet von meinem BlackBerry 10-Smartphone.
>> Originalnachricht
>> Von: Kevin Chadwick
>> Gesendet: Donnerstag, 8. März 2018 17:28
>> An: misc@openbsd.org
>> Betreff: Re: booting hd0a:/bsd:
Am 08.03.2018 um 23:25 schrieb Stefan Wollny:
> Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
>
>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
>>> Gesendet von meinem BlackBerry 10-Smartphone.
>>> Originalnachricht
>>> Von: Kevin Chadwick
>>> Gesendet: Donnerstag, 8. März 2018 17:28
>>> An:
Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
>
> Gesendet von meinem BlackBerry 10-Smartphone.
> Originalnachricht
> Von: Kevin Chadwick
> Gesendet: Donnerstag, 8. März 2018 17:28
> An: misc@openbsd.org
> Betreff: Re: booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
>
> On Thu, 8 Mar 2018
Am 08.03.2018 um 23:25 schrieb Stefan Wollny:
> Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
>
>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
>>> Gesendet von meinem BlackBerry 10-Smartphone.
>>> Originalnachricht
>>> Von: Kevin Chadwick
>>> Gesendet: Donnerstag, 8. März 2018 17:28
>>> An:
Hi all,
Greetings from me!
I meet a weird issue: there is a file which contains only "1":
# cat a
1
While use vim to open it, it displays "0". I find the number behind
cursor will decrease 1.
Does anyone bump into this issue? Thanks very much in advance!
P.S., my OpenBSD is 6.2 release, and
On Thu, Mar 08, 2018 at 05:48:05PM +, niya wrote:
> hi
>
> i working out my ideas for modelling my home network,
>
> the network will have four vether interfaces to cover the needs of my
> firewall,
>
> which will have a lan, demilitarised zone, carp redundancy and connection
> to the wan,
Am 09.03.2018 um 00:09 schrieb Stefan Wollny:
> Am 08.03.2018 um 23:25 schrieb Stefan Wollny:
>> Am 08.03.2018 um 22:11 schrieb Stefan Wollny:
>>
>>> Am 08.03.2018 um 17:44 schrieb Stefan Wollny:
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
Von: Kevin Chadwick
On Thu, 8 Mar 2018 14:47:43 +0100
> Has anyone a clue what might have happend and how to solve the issue?
> I searched the net but didn't find any substantial infos on this. As
> the error happends with all three USB-keys I have this is unlikely to
> be cause of the trouble.
The bootloader
15 matches
Mail list logo