On 01/10/2019 21:17, Lyndon Nerenberg wrote:
>> SYS-5018A-FTN4
>
> If you have any of these, replace them. They have known buggy CPUs
> and will randomly fail without warning. We replaced about a dozen
> of them after >50% failed within the first year of installation.
I have several of these bo
On 15/11/2019 10:11, gwes wrote:
On 11/14/19 3:52 PM, Andrew Luke Nesbit wrote:
On 15/11/2019 07:44, Raymond, David wrote:
I hadn't heard about file corruption on OpenBSD. It would be good to
get to the bottom of this if it occurred.
I was surprised when I read mention of it too, wi
Hi Dave,
On 15/11/2019 07:44, Raymond, David wrote:
I hadn't heard about file corruption on OpenBSD. It would be good to
get to the bottom of this if it occurred.
I was surprised when I read mention of it too, without any real claim or
detailed analysis to back it up. This is why I added my
On 05/11/2019 17:38, Ingo Schwarze wrote:
Hi,
Hello Ingo!
Andrew wrote on Sun, Nov 03, 2019 at 12:56:58PM +:
[ Pandoc ]
is one of the most useful tools I have ever used. If you are writing
any sort of documentation then I *highly* recommend checking it out
I strongly oppose that poin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/11/2019 10:55, Frank Beuth wrote:
> Not sure about the original poster but I would be interested in
> any end-to-end encrypted video/audio/chat programs that are
> available.
Have a look at Tox. It might work out for you on a technical level.
On 22/07/2019 16:13, Raul Miller wrote:
Both git and OpenBSD run on patches.
That said, OpenBSD has a cultural restriction of requiring people to
inspect the patches before incorporating them. Adopting git would be a
step away from that practice.
Does that help make sense of the current situati
On 21/06/2019 19:02, Frank Beuth wrote:
> I don't want to re-open the hostilities, but installing OpenBSD via
> Ansible is very relevant to my interests.
I feel exactly the same way and am surprised that Ansible caused
hostilities. Can you send me a link to the thread where this happened
please?
On 15/06/2019 10:36, Jonathan Gray wrote:
> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>>
>> Hello,
>>
>> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
>> Atom CPU (Denverton). The board boots but most devices are not
>> detected because ACPI can't b
On 13/06/2019 07:17, Theo de Raadt wrote:
> Mihai Popescu wrote:
>
>>> ... if no account is provided, root is the default
>>
>> I always considered that su is coming from _s_uper _u_ser. But maybe I
>> am wrong, I am not from old UNIX days.
>
> incorrect.
>
> NAME
> su - substitute user id
On 19/05/2019 02:08, Don Jackson wrote:
> I recently acquired a Supermicro 1019D-FRN8TP server with a X11SDV-8C-TP8
> motherboard.
>
> When i attempt to install 6.5, (via PXE or USB), none of the network
> interfaces are detected.
> A dmesg appears below, followed by a dmesg and ifconfig -a from
On 09/05/2019 14:56, Allan Streib wrote:
> Unless https://www.openbsd.org/plat.html is out of date, it doesn't look
> like OpenBSD is currently supporting POWER8 or POWER9 plaftorms.
I wonder what is the best way to determine interest in getting OpenBSD
to work on POWER8/9?
My first thought is to
On 09/05/2019 14:26, Henry Bonath wrote:
> I'm not sure how many folks out there are PowerPC users
What exactly do you mean by PowerPC?
I am a user of Apple PowerBook G4, POWER8, and POWER9. I am new to
OpenBSD and I intend to experiment with it on these architectures.
Andrew
--
OpenPGP key: E
12 matches
Mail list logo
