Hey,
getting following error on OpenBSD-current as of yesterdays 'cvs up’:
unable to load Private Key
30008934842236:error:0906D064:PEM routines:PEM_read_bio:bad base64
decode:/usr/src/lib/libcrypto/crypto/../../libssl/src/crypto/pem/pem_lib.c:822:
Cmd issued: 'openssl rsa -noout -modulus -in k
So, for newcomers from other systems the practical approach would be to
follow snapshots to be able to upgrade all (packages on top of base).
Install first (once)
1) download a snapshot set (or only bsd.rd for network install)
2) install latest snapshot base OS
3) install your packages with pkg_a
> Who are you? What is your name? That's the first step to establish
> trust.
I would not think in this way Theo. If you need a name and a "social status"
to "trust" someone, then you're fucked, because everyone can fake this, and
a name is just a name, symbols of some language together, nothing
Hi,
I would just do some comments inline.
On Sun, Jun 28, 2015 at 07:20:51PM +0200, Carlos Fenollosa wrote:
> Hi,
>
> I’ve recently discovered OpenBSD after using Linux for more than 15 years. I
> wrote
> a blog article with my impressions and some other users suggested me to patch
> faq9.htm
On Thu, Feb 19, 2015 at 01:50:59PM +, Wei Liu wrote:
> Hi all
>
> When I was trying to debug a double fault on 5.6, I found the trap frame
> looked a bit strange. After some investigation and reading source
> code, I found that double fault handling looked problematic.
>
> Per Intel SDM volum
> > Well, not near one, but I volunteer for binary errata patch on current
> > for i386 and amd64 (the only archs I own for now).
>
> People are going to use binary patches from you?
I was hoping to try help with testing at least.
> Who are you? What is your name? That's the first step to esta
On Sun, 28 Jun 2015 20:26:31 +0200, Alexander Bluhm wrote:
> Why? And what should I document in the manpage then?
So you don't break existing scripts that might use it. You don't
need to document it.
- todd
2015-06-26 9:20 GMT+03:00 Claudio Jeker :
> On Fri, Jun 26, 2015 at 04:59:32AM +0300, Sergey Ryazanov wrote:
>> Hello,
>>
>> during building l2tp tunnel with xl2tpd-1.3.1 I was faced with its too
>> low upload performance. When download, the speed is 20 mbit/s at
>> nearly 100% CPU utilizati
> Well, not near one, but I volunteer for binary errata patch on current
> for i386 and amd64 (the only archs I own for now).
People are going to use binary patches from you?
Who are you? What is your name? That's the first step to establish
trust.
Boy, that's a pretty clever joke!
> I think you've already said enough nasty stuff
Right.
> I personally am not going to spend a second working on binary updates
> until I know there are 20+ other developers also dedicated to making
> it happen, and once it starts happening -- keeps happening forever.
Well, not near one, but I v
> So the discussion is to probably best put these upgrade details in the
> upgrade guide, not in the migration guide in the meantime.
>
> Without delegating resources until deemed necessary and no need to
> state explicitly "they have no binary upgrades" on the migration guide.
I think you've alr
> > > Lack of
> > > resources is about the only good reason there is for not providing
> > > binary updates.
> >
> > That's not true.
>
> It must feel absolutely glorious to bask in your anonymity and make
> such a strong claim.
There are no strong claims. The other good reasons are to manage th
> > Lack of
> > resources is about the only good reason there is for not providing
> > binary updates.
>
> That's not true.
It must feel absolutely glorious to bask in your anonymity and make
such a strong claim.
I personally am not going to spend a second working on binary updates
until I know
> Lack of
> resources is about the only good reason there is for not providing
> binary updates.
That's not true.
Further, base + packages are updated frequently in snapshots, which is
exactly a binary upgrade path for users without worry.
This works exceedingly well and is well stated in the fo
> Without reading much of the documentation to gain reasonable production
> usage, you're trying to mend the OpenBSD site to say it is lacking
> something that you thought worth having according to your current
> limited to Linux experience.
>
> Never occurred to you it may be intentional?
> The
On Mon, Jun 29, 2015 at 01:02:44AM +0300, li...@wrant.com wrote:
> > Do you have a patch that achieves the same goal (that is, the goal he
> > stated, not the one you're reading into) that is up to your standards?
>
> One that reversed the submission of the proposed patch, correcting it
> and this
On Sun, 28 Jun 2015, Mark Kettenis wrote:
> I have an x41 that prints the following in dmesg:
>
> acpicpu0 at acpi0
> C1: unknown FFH vendor 8: !C3(250@85 io@0x1015), C2(500@1 io@0x1014), PSS
>
> The relevant AML indead has that strange value in the "Bit Width" field:
...
> Obviously this ACPI BI
> Do you have a patch that achieves the same goal (that is, the goal he
> stated, not the one you're reading into) that is up to your standards?
One that reversed the submission of the proposed patch, correcting it
and this thread to an empty string.
> I understand that OpenBSD owes me nothing (and vice versa) and I was just
> trying to help. The decision to merge that information is not mine to do,
> however, I honestly thought it could help people looking for a more thorough
> comparison between Linux and the BSDs.
Are you by chance being
Hi,
I’m sorry that it came off that way. Did you read the whole article? No that
you should have, but it addresses most of the points that you mention
I understand that OpenBSD owes me nothing (and vice versa) and I was just
trying to help. The decision to merge that information is not mine to
On 2015-06-29 00.03.09 +0300, li...@wrant.com wrote:
> And you consider this a service to other Linux long time users? Or a
> way to try push some notion of yours - criticise and try to lobby for
> some other entity's interests.
Do you have a patch that achieves the same goal (that is, the goal he
> I’ve recently discovered OpenBSD after using Linux for more than 15 years.
Long time, no see? And you blogged and achieved your goal of... making
yourself expressed, critically on your own controlled web space.
> I wrote
> a blog article with my impressions and some other users suggested me
On Sun, Jun 28, 2015 at 07:20:51PM +0200, Carlos Fenollosa wrote:
> This patch is regarding the fact that there are no binary updates,
> which is a given thing in most Linux distributions, and some tips on
> how to keep the system updated.
It may be worthwhile to mention that updates are comparati
> What do you mean? The author mentioned mtier.org both in his original
> blog post and the patch sent to this mailing list.
Author? Exactly whose ground are you defending here, Adam?
> If it's going to be merged then it's probably worth to mention that
if... and you're on top of each other argu
On Sun, Jun 28, 2015 at 08:42:21AM -0600, Todd C. Miller wrote:
> On Sun, 28 Jun 2015 12:43:40 +0200, Alexander Bluhm wrote:
>
> > After removing the p_swtime from the kernel, ps always prints 0.0
> > as %cpu time. The simple fix is to remove the calculation in ps
> > that includes the process li
On Sun, 28 Jun 2015 19:55:58 +0200
Denis Fondras wrote:
> > This patch is regarding the fact that there are no binary updates,
> > which is a given thing
> >
>
> What you missed : https://stable.mtier.org/
What do you mean? The author mentioned mtier.org both in his original
blog post and the
> This patch is regarding the fact that there are no binary updates, which is a
> given thing
>
What you missed : https://stable.mtier.org/
Hi,
I’ve recently discovered OpenBSD after using Linux for more than 15 years. I
wrote
a blog article with my impressions and some other users suggested me to patch
faq9.html to help other users migrating.
This patch is regarding the fact that there are no binary updates, which is a
given th
I have an x41 that prints the following in dmesg:
acpicpu0 at acpi0
C1: unknown FFH vendor 8: !C3(250@85 io@0x1015), C2(500@1 io@0x1014), PSS
The relevant AML indead has that strange value in the "Bit Width" field:
Name (CST1, Package (0x02)
{
0x01,
On Sun, 28 Jun 2015 12:43:40 +0200, Alexander Bluhm wrote:
> After removing the p_swtime from the kernel, ps always prints 0.0
> as %cpu time. The simple fix is to remove the calculation in ps
> that includes the process lifetime. Just print the p_pctcpu.
I think you want to keep the case 'C':
Hi,
After removing the p_swtime from the kernel, ps always prints 0.0
as %cpu time. The simple fix is to remove the calculation in ps
that includes the process lifetime. Just print the p_pctcpu.
This was already done when ps -C was used, now ps always behaves
this way.
ok?
bluhm
Index: bin/p
Hi,
I want to store all syslog messages received from a specific host
into a single log file. For programs this is already implemented
for !prog blocks. So do the same with +host for hostnames.
This implementation is based on a diff that Gregory Edigarov sent
to me. So there is at least one ot
32 matches
Mail list logo
