Look Chris, that is yet another mail is off topic for this list.
https://www.openbsd.org/mail.html
You are NOT talking about OpenBSD, rather you are blathering about
unrelated topics.
Get your shit together
Chris Bennett wrote:
> On Wed, Sep 19, 2018 at 10:48:50AM -0600, Theo de Ra
Surely this is off-topic for misc, your phone has nothing to do with openbsd.
Chris Bennett wrote:
> On Wed, Sep 19, 2018 at 06:08:19PM +0100, Kevin Chadwick wrote:
> > On Wed, 19 Sep 2018 07:03:56 -0700
> >
> >
> > > This is the thread that I wished to start that pertains to OpenBSD.
> > > If
OFF-TOPIC for this forum
Torsten wrote:
> Sadly you are not in the EU or that would cost google 500K
>
> -Original Message-
> From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
> Michael Ayres
> Sent: 19 September 2018 14:48
> To: Chris Bennett
> Cc: misc@openb
This thread is OFF-TOPIC for this list.
Take it elsewhere.
Michael Ayres wrote:
> Chrome is banned at my workplace shop, as are pretty much all of Google
> products. We use DuckDuckGo, or other one-off for search and Firefox or
> Safari for browsers.
>
> Michael Ayres
>
> Michael Ayres, MS
Olivier Regnier wrote:
> Hi,
>
> Is it possible to disable the '.aucat_cookie' file or change his location?
No.
Libraries know the specific pathname.
could be an
> unveil command
> similar to unveil(NULL, NULL) instead of a pledge command? It apparently
> knows if it is
> an increase in permissions, can't it be set to only permit them?
>
> On Thu, Aug 16, 2018 at 2:00 PM Luke Small wrote:
>
> Ok. Thanks.
> On
Jacqueline Jolicoeur wrote:
> > Finally, whether intended or not, your intention to try to SELL
> > something on this list is extraordinarily rude. Move on and go learn
> > about this on your own. The Internet is filled with useful information.
> > The mailing list archives also have a tremendous
Wow, you are not asking.
You are just doing it.
So fake.
Quite a deceitful action.
Z Ero wrote:
> I am trying to clear out some things I have in my basement. I thought
> these may be of interest to the OpenBSD community so I am mentioning
> them here. Not trying to spam or distract anybody...
Stuart Henderson wrote:
> On 2018-08-24, Aaron wrote:
> > Does anyone know if the patch for this ssh bug is going to make it
> > into the 6.3 stable/release branch?
>
> I don't know for sure but I'd think it fairly unlikely for this one.
>
> If you didn't already see djm's mail about this bug,
Chris Bennett wrote:
> On Wed, Aug 22, 2018 at 04:29:38PM +, ed...@pettijohn-web.com wrote:
> >
> > I'm curious why you have to be root to set up networking, but the operator
> > group can shut the machine off.
> >
>
> Well, there are probably additional reasons too, but my father happily
Edward Lopez-Acosta wrote:
> Can't properly reply to the thread. I need to fix my subscription, but why
> not just update the following to work on OpenBSD?
>
> https://github.com/ghostbsd/networkmgr
>
> Seems like a better use of resources than reinventing the wheel. Unless
> there is something
Luke Small wrote:
> Could you have a promise for unveil reductions only?
That won't actually help much, and people will fall into some
pretty significant traps.
Sorry it would require a really long explanation.
Ingo Schwarze wrote:
> Hi Edward,
>
> Edward Lopez-Acosta wrote on Thu, Aug 09, 2018 at 06:29:04PM -0500:
>
> > I was looking to port bleachbit, system cleanup tool, to OpenBSD
> > and one function is to make sure certain files are not in use before
> > it proceeds.
>
> Strictly speaking, that
Denis wrote:
> Is it possible to make more ttys by ./MAKEDEV ttyU* command to have:
> ttyU0a-ttyUzz?
Up to 127 such devices because of how the node's minor is split.
Felix Maschek wrote:
> After upgrading my system (using bsd.rd) I get the prompt "Exit to
> (S)hell, (H)alt or (R)eboot?".
>
> When I select S I get a shell. Now I want to mount a USB stick. when I
> insert it I get the expected log message, that the device is found and
> has the name "sd2".
Mike Larkin wrote:
> On Thu, Aug 02, 2018 at 09:22:53AM +0200, Nulani t'Acraya wrote:
> > Hello,
> >
> > Something similar also appears to also be affecting bhyve, at least on an
> > AMD Opteron 4228 HE. The error produced is different depending on
> > whether bhyve is instructed to ignore acces
This multi-vendor family of "SuperIO" chips is racy and weird, and
difficult to probe directly. They require bankswitching registers, with
an unclear locking regime against the possibility of a system BMC or SMI
also performing the same actions. In general, the code falls through to
a device whic
>I've migrated to -current to test the auto-join, but since then, my system
>is slow. Specially with libreoffice, firefox, ...
>
>By looking at top, I've saw that only 2 CPU are actually running.
You only have 2 real cpus.
the others are HT, and we disable those due to a security hole
called tlbl
Claudio Jeker wrote:
> On Sat, Jul 21, 2018 at 07:02:08PM +, Stuart Henderson wrote:
> > On 2018-07-21, Adonis Peralta wrote:
> > > Is there a reason why the offloading features shouldn???t work correctly
> > > on OpenBSD?
> >
> > If you can figure out why it doesn't work, you'll be well on
Hi Adonis,
Because.
Adonis Peralta wrote:
> Is there a reason why the offloading features shouldn???t work correctly on
> OpenBSD? i350 supports offloading just fine via the igb driver on FreeBSD. Is
> it more work on the driver thats needed?
>
> --
> Adonis
>
> > On Jul 18, 2018, at 3:39
>On Sun, 15 Jul 2018 17:59:58 -0700, Scott Vanderbilt wrote:
>
>> In /etc/mail/aliases, there is the following note:
>>
>> #>> The program "newaliases" must be run after
>> #>> NOTE >> this file is updated for any changes to
>> #>> show through to smtpd.
>
Christian Weisgerber wrote:
> On 2018-07-11, Tom Smyth wrote:
>
> > this is an odd one but I have a client that needs to
> > migrate some legacy services
> > Is there support for ISDN type interfaces in OpenBSD ?
>
> No.
>
> (Once upon a time there was something called isdn4bsd, but I don't
>
Tomasz Rola wrote:
> On Sun, Jun 24, 2018 at 10:53:37PM -0400, Steve Litt wrote:
> > On Thu, 21 Jun 2018 00:56:04 +0200
> > Tomasz Rola wrote:
> >
> [...]
> > > Craps. I have consulted OpenBSD's manpage for dd and there is no
> > > mention of iflag. So this will not work on OpenBSD. I will have
Todd C. Miller wrote:
> As someone else mentioned you would use pkill on OpenBSD.
>
> However, you will also need to use SIGINFO, not SIGUSR1, to get
> dd's status. BSD systems have traditionally used SIGINFO for this
> purpose. Linux lacks SIGINFO so there is no consistent signal for
> this k
Tuyosi T wrote:
> hi all .
>
> on Linux
>
> dd-progress.bat <
> ---
> while true
> do
> date
> killall -USR1 dd
> echo
> echo
> sleep 30
> done
>
> but killall is not possibele on OpenBSD .
> ---
> regards
true.
doesn't work for me on wind
Kevin Chadwick wrote:
> My point was that signing up in the first
> place should be criticised, if anything.
So you criticize our previous involvement in embargos where it was
neccessary?
Even in the situations where it took > a week to write a fix?
Everyone can tell that you are wrong. Adult
Kevin Chadwick wrote:
> On Thu, 21 Jun 2018 08:34:55 -0700 (MST)
>
>
> > It was a good talk either way.. It's an issue that keeps getting
> > larger as time goes on.
>
> Whilst I can see but disagree with a point of view that Open Source
> will be locked out if they don't comply with embargos
Benjamin Baier wrote:
> Anybody seen this, too? Can't be twice as fast _without_ hypertreading.
Why not?
Our scheduler doesn't know how to use HT correctly. And soon when
we all realize how broken HT is, we won't be able to use it correctly
in the super-restricted way it can be used.
> In that case, are the Chromium updates in current worth attempting to
> backport to stable?
the team does not do significant backports like that.
> Or are the stable builds safer than the backported Firefox builds
> throughout the six months or so that they remain frozen?
Answered it in the lo
Marc Espie wrote:
> Chrome is a relative newcomer to browser land, and it was designed from
> the start from a security point of view, so it got a headstart there.
In a browser, there are 2 main security components you want: The main
security advantage is privsep. The other is W^X jit. Other s
>I???d I say you certainly can. You can???t claim the image as yours or
sell it/profit from the image. Just using it on your site should be
fine.
I wrote the statement to ensure OpenBSD images aren't misused and
abused.
I have personally worked on and paid for OpenBSD artwork to be
produced. D
>On Thu, 07 Jun 2018 15:51:24 -0800, justina colmena
> wrote:
>
>> The no-profit clause is new.
>
>That's not true. It was added with
>revision 1.8
>date: 2005/03/24 01:31:13; author: deraadt; state: Exp; lines: +4 -3;
>note do not sell
>
>(on github:
>https://github.com/openbsd/www/commit/46f3
francis.dos.san...@ciudad.com.ar wrote:
> Hello,
>
> My apologies if this should've gone to bugs@. There are 3 dmesg.boot
> outputs within this text. The last successful boot of version #65 and
> two outputs of #82 (xenodm enabled and disabled).
>
> About two days ago I upgraded to the version #
>On Mon, Jun 04, 2018 at 12:24:42PM +1000, Stuart Longland wrote:
>> On 04/06/18 09:34, Leonid Bobrov wrote:
>> > After that I noticed that my micro stopped
>> > working.
>>
>> Could you define what's meant by "micro"?
>>
>> Home computers were often called "microcomputers", back around the time
>Dare I ask what lead to OpenBSD not being affected.
>
>Sorry if it is a dumb question but since this hit FreeBSD as well I am
>wondering
>what OpenBSD did differently.
>
>Was this caught in an audit?
>
>I am just curious about causality that kept OpenBSD in the clear of this one
>that made such he
A replacement file is moving it's way out to mirrors now...
>Can someone give me a link or tell me why ftp
>option was removed from installer?
Because of many reasons. Including running low of space on the
install media.
>I currently use it for packages:
>ftp://mirror.yandex.ru/pub/OpenBSD
>
>I'd like to use "https://"; instead, of course,
>but in my cou
Leonid Bobrov wrote:
> I have a plan how to completely get rid of wxallowed mount option,
> but I am not yet skilled to fix W|X ports, especially the ones
> written in C++ (I've started learning C++ recently).
Is that like
"I have a plan to build a flying car, but I don't
yet have any meta
The great thing about OpenBSD is that it comes with all these debugging
tools that let you figure out what happened, right there on your own
system, without having to engage tech support who speaks a foreign
language. If only you spend a few minutes to learn before sending
email.
Into enhle nge-O
would not have needed the 14th patches.
>
>
> --
> Patrick Harper
> paia...@fastmail.com
>
> On Tue, 17 Apr 2018, at 08:57, Theo de Raadt wrote:
> > > What changed was that there was a period after 6.3 was pushed out the
> > > door (2-15 April) in whi
> What changed was that there was a period after 6.3 was pushed out the
> door (2-15 April) in which there were effectively three active
> releases and the project felt obliged to support 6.1 until 6.3's
> projected release date. My previous post attempted to review a
> possible workaround, though
Harper
> paia...@fastmail.com
>
> On Sun, 15 Apr 2018, at 12:02, Theo de Raadt wrote:
> > Patrick Harper wrote:
> >
> > > Unless I am mistaken, the errata posted on the 14th April is the first
> > > that has been applied to more than two releases, i
IL Ka wrote:
> In FreeBSD they have /etc/make.conf
> You set CPUTYPE= there, and
> /usr/share/mk/bsd.cpu.mk will read it, and set -march for CPUCFLAGS
>
> This variable is used by ports, kernel, and any random Makefile may use it.
> (There are similar things in Linux Gentoo also)
>
> But OpenBS
Diana Eichert wrote:
> On Mon, 16 Apr 2018, Theo de Raadt wrote:
>
> > Diana Eichert wrote:
> >
> >> Hi Tom
> >>
> >> Thanks for educating the misc@ masses on Tile hardware.
> >
> > Unfortunately I don't think misc@ will do much wit
Diana Eichert wrote:
> Hi Tom
>
> Thanks for educating the misc@ masses on Tile hardware.
Unfortunately I don't think misc@ will do much with the info.
Patrick Harper wrote:
> Unless I am mistaken, the errata posted on the 14th April is the first
> that has been applied to more than two releases, implying that
> 6.1-stable is still supported. Does this signify a change to the
> lifecycle process?
No it does not indicate that.
Official release
> Hello,
> I am pretty new to OpenBSD and not sure if I should report minor issue to
> bugs@, but I just found that vgafb(4) device is supported only on macppc
> and sparc64 (according to src/sys). It has nothing to do with i386 nor with
> amd64.
>
> But for some reason it's man page sits directly
Aham Brahmasmi wrote:
> Hello misc,
>
> Recursive macros which include macros containing certain specific
> characters cause syntax errors.
>
> Steps
> $ cat pftemp.conf
> forwardslash = "100/10"
> #forwardslashrecursive = $forwardslash
> number = "100"
> numberrecursive = $number
> string = "k
Aaron Mason wrote:
> On Fri, Jan 5, 2018 at 8:26 AM, Peter N. M. Hansteen wrote:
>
> >
> > If you think you don't have the seniority to start submitting patches
> > when you see a bug (even a typo in a man page or the faq), you're most
> > likely wrong. Your first efforts will not be perfect of
Patrick Marchand wrote:
> On 04/08, Patrick Marchand wrote:
> > Compilation succeeds on the april 8 snapshot
>
> Though now I'm getting Abort Trap whenever I try to run the plumber or
> acme. I was able to compile some programs with mk though, as I compiled
> both $PLAN9/src/cmd/upas and $PLAN9/
Jordan Geoghegan wrote:
> The pc engines stuff will still have blobs in it. There's no way to
> have fully open firmware on a modern i-series chip based rig. At the
> end of the day, we all are still using proprietary hardware.
Who cares?
People just want to get the job done. We do the best we
Patrick Dohman wrote:
> As much as I’d rather not point the blame I found the APU platform
> buggy when running OpenBSD.
I doubt anyone believes your extremely vague assertions. There are
thousands of them running fine.
> I'm currently running a MikroTik 2011UiAS that is built on A mips proces
Ingo Schwarze wrote:
> Hi Kristaps,
>
> Kristaps Dzonsons BSD.LV wrote on Sat, Apr 07, 2018 at 01:37:32AM +0700:
>
> > The only reason I suggest a standalone section is that it's easier
> > to standardise across manpages.
>
> For that goal, using ".Ss Pledge promises"
> at the end of the DESCR
Kristaps Dzonsons wrote:
> The only reason I suggest a standalone section is that it's easier to
> standardise across manpages.
I do not see a way to do this in libc. So standardise isn't really
required. You are talking about doing this in a port library, not a
base library.
I don't know how
> .Sh SANDBOXING
And please stop using that word. It has been misused so many
times, by now it is misleads.
pledge is not a sandbox (whatever the hell a sandbox is)
> Shouldn't /etc/malloc.conf be in /etc/changelist? You would most likely
> want to know if it appears or is changed, and you probably don't want
> sysclean package to suggest you to remove it either.
That kind of justification would result in everything eventually being
added to the changelist.
> > How can I know if the partition needs to be checked by fsck, I'd like to
> > test that.
>
> Check the output of dumpfs. clean=0 means that the filesystem is
> dirty and fsck should be run.
It is cheaper to just run fsck. If it has no work to do, it finishes.
> No such team exists. the tool used is irrelevant
Well, we have that tool today: it is a mailing list.
Also, we have a team which triages bugs on there: the developers.
Is it perfect? No.
Do things slip through the cracks? Sure. Because not enough people
triage. Not enough developers.
Wo
Do we want the 1% solution? No.
Will we accept something which comes with a full triage team? Yes.
Is a triage team being offered? No.
> My question was serious. I am not the enemy but I think this thing
> will only work if the people who use it accept / like to use it and so
> on.
>
> > bug
> Would the devs accept / use a bug tracker ? I ask because I find start
> something without the devs is burning time (see the .ru domain, the UI
> posts ... ).
We'd be happy to accept a bug-tracker which is slavishly quality-managed
and continually purified and kept current by a team of dedicated
Way to go guys, you've completely misunderstood the problem
and therefore have no solution.
That may hint to people it should be the default.
And it should not be.
It is documented. Why does everything documented need to be in the
example? The example isn't documentation. The documentation is
documentation. We urge people to read and understand the documentation,
and not use example
Your specification and requirements are so clear.
But this isn't a pony shop.
Who cares what you want? Really, noone.
> I just don't want OpenBSD to turn into Linux where the fixation is on
> newest shiny thing rather than doing code right. Sometimes I think
> people who are excessively interes
> > Dear Mihai,
> > Although your tone in your email was not pleasant,
>
> You are posting to OpenBSD-misc. Objectionable tone is very common,
> particularly for users who *appear* to be complaining about
> immeasurably-small problems that aren't actually significant in the real
> world. If y
No.
bsd.rd is for installation. It is not a diagnostic tool.
There are other ways to do diagnostics.
> does it make sense to add acpidump to bsd.rd ?
> I've tried to install snapshot on Dell R640 and installation went well
> but booting stops with this error:
> http://kosjenka.srce.hr/~hrvoje/
> Am 16.03.2018 um 11:42 schrieb Torsten:
> > Hi!
> >
> > On my OpenBSD 6.2 syslogd is listening to port 514, even though it is
> > not started with "-r" (to receive remote syslog messages). It does not
> > actually seem to log anything if I send something to port 514 UDP,
> > however, I want the
> If the adapter is ejected before closing the laptop lid there is no
> problem waking from sleep. But is a minor inconvenience to eject the
> adapter. Would it be possible to patch the kernel some how to make it
> think the adapter is ejected before entering sleep?
It does that. The problem is s
> On Tue, Mar 13, 2018 at 10:39 PM, Theo de Raadt wrote:
> >> According to some sources, Intel and a handful of others have known about
> >> the
> >> issue since February 2017(!), so perhaps it has already been patched in the
> >> 08Jan2018 BIOS. I too hav
> According to some sources, Intel and a handful of others have known about the
> issue since February 2017(!), so perhaps it has already been patched in the
> 08Jan2018 BIOS. I too have doubts that to date any processor has been
> redesigned to avoid the flaws entirely, but then again...
Sure. A
> Running that PoC on the machine while in -current and even 6.1 (no
> patches) returns that the system is not vulnerable to meltdown. This
> processor was made in 2016 and everything I've read indicates that it
> should be vulnerable.
Such a low-grade processor may not have sufficient speculative
> If a process forks two children does the parent need separate imsg
> bufs for each? I'm thinking one will do and just use the header to
> decide who it's from. Is that correct or should they be separated?
The socket layer will conspire against you.
It is a library routine that calls a system call.
It isn't worth changing at this point.
> I find sysctl(3) in OpenBSD 6.2 is changed to system call in -current
> (please refer the manual: https://man.openbsd.org/sysctl.2).
>
> So the sysctl would be a system call instead of library function in
> On 2018-03-07, jungle Boogie wrote:
> > Hi All,
> >
> > With the latest openbsd snapshot:
> > OpenBSD 6.3-beta (GENERIC.MP) #40: Wed Mar 7 12:51:00 MST 201
> >
> > It seems I cannot build or update go projects:
> >
> > $ go get -u github.com/justwatchcom/gopass
> > Abort trap (core dump
>On Tue, 20 Feb 2018 18:45:01 +0100
>Stefan Sperling wrote:
>
>> > I download SHA256.sig abd file sets from mirror, how can I trust it?
>>
>> You run a trusted signify binary, which was not obtained from the
>> mirror but is part of your existing install, to check the signature
>> on SHA256.sig.
>If someone is able to provide a fake ISO, he will also provide fake
>SHA256.sig and/or fake public key on the ISO. So there is no gain to
>provide such material as people will think "it is safe" whereas it is
>not.
that is true.
however, the real reason it isn't on the media is that internal
sig
Unfortunately noone cares.
>The #OpenBSD IRC channel on FreeNode is listed under "OpenBSD
>Resources" at www.openbsd.org , so it is official to some degree.
>
>Blakkheim (I think he is t...@openbsd.org) is insisting with abusing his
>administrator privilege there, today by blocking me again.
>
>He
> It isn't just this. Qt 5.10 introduces new dependency on OpenSSL 1.1
> APIs for improved security, and LibreSSL does not implement those APIs
> at all.
The 1.1 API does not improve security.
If anything, the new API requires to you repeat the same or similar
arguments to many functions, and in
>When it comes to Meltdown:
>Does OpenBSD is going to release patches for 6.2? I don't see anything related
>to Meltdown in errata, but maybe it is too early. I understand other OSes
>received disclosed information about bug a few months earlier.
amd64 snapshots contain a fix, which is undergoing
> I install OpenBSD on my Fastwell CPB905 Singleboard compter. IT have
> 4-RS-232 port on same IRQ, but on different address on isa bus. Then i
> setup only one port using configure command all ports work normally. But
> when i setup 2 of them in one boot configuration i get in dmesg: irq
> already
Have you ever heard of the concept of helping yourself?
> Does any of my hardware work in -current?
> Lots of stuff fails in 6.2 stable.
> WiFi and touchpad being especially desired, of course!
>
> If WiFi isn't a go, can anyone recommend a USB WiFi stick?
>
> Thanks,
> Chris Bennett
>
>
> Ope
> Resume after suspend fails on a Zenbook UX390UA if (and only if) the
> USB hub/adapter that comes with it is connected.
Is that a pure USB dock, or is it something else? Does it connect with
a pure USB connector?
Maybe the resume-side EFI/ACPI/SMI makes assumptions about it?
At suspend time,
> So, I have to identify which ones are exactly broken (Stuart Henderson
> said this is the trickier part), contact their developers (if the
> software is not abandoned) and send patches, right?
Your approach of making the world better will be "getting in their face"?
You have some sort of list.
I think you have interpreted the situation backwards.
The wxallowed flag is not on other filesystems. Therefore, binaries
on those filesystems which misbehave will fail.
There are about 15 programs which need fixing, and the wxallowed could
become a piece of history.
Unfortunately some of those
It is software you use.
So take responsibility for it
Picking on random people to solve your problem is insane
> This is distributed DNS, so must work 24/7. It will be fixed soon.
>
> No complaints, no jumps at all.
>
> On 1/25/2018 9:34 AM, Theo de Raadt wrote:
> > So f
So fix it, or pay someone to fix it.
Do you think your complaints should make people jump to attention?
> It is clear, but what do now when potentially 'buggy' software must
> work? There is no any transient period provided.
>
> ln - s 'j' /etc/malloc.conf partially resolves the problem with bug
> On 01/19/18 01:12, Theo de Raadt wrote:
> >> FWIW, the permission I seek is from my Legal department.
> >
> > That maybe your job but it isn't the project's job.
>
> > Enough is enough. That sentence above makes it clear who is getting
>
>FWIW, the permission I seek is from my Legal department.
That maybe your job but it isn't the project's job.
We could write the document you need. Then the next comment would
probably we that we didn't publish our procedure and have a lawyer
sign off on what we did.
It is a neverending battle.
> Is there, by chance, such a breakdown available for these already?
No. We did our best.
Always interesting that the more one works in the free software
space, the more constraints get added by the public.
Sometimes it is almost like there is a stream of people who want us
to stop trying.
And
> This is the firmware i've currently installed:
>
>$ doas fw_update -i
>Installed: intel-firmware-20180108
That has nothing to do with:
>error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to
> load firmware i915/bxt_dmc_ver1.bin (-22)
I recognize something doesn't wo
> I was hoping that there was some hidden switch somewhere that would turn
> the classic crypt back on. No such luck.
That'd be like leaving a running chainsaw on the floor at a daycare center.
When something is dangerous, we get rid of it.
> I've got an old server (OpenBSD 4.7 old) with a mixed bag of password hashes
> in master.passwd. A majority of the passwords (hundreds) are old salted
> DES crypt format.
bummer
> Am I correct in my research that everything but Blowfish was removed from
> crypt() around OpenBSD 5.7? Are there a
> Ted Unangst wrote:
> > Otto Moerbeek wrote:
> > > Sparc64 and powerpc also have speculative execution, branch
> > > prediction and extensive caches. It is much wiser to assume they are
> > > also affected by (similar) bugs/explots or whatever you call it.
> >
> > A lot of the commonly available
Dinesh --
everything you say below is a giganic pile of dung. We make all our
software available to everyone. The internet spans the planet.
You are making stuff up, and it is not appreciated how you appear to
be misrepresenting the project.
Please go fluff up your sense of selfworth elsewhere
> By entering as su/doas sysctl kern.bufcachepercent=80 shows me the
> change from default=20 to 80 as expected, but after a reboot the value
> is set again/still to 20 (%).
sysctl changes the running state. It does not change that file
for future boots.
> Ada 2012? increased the use of pointers but still limits their usage.
>
> Aside from a couple of mentions in style(9) is there any info on
> OpenBSD's rules around pointers or is it simply avoid unless necessary
> and following general good practice?
Wow what a broad useless question.
>On 2017-12-06, ti...@openmailbox.org wrote:
>
>> If TRIM would be implemented someday, one thing that would be
>> neat would be that crypto and other softraid would propagate the
>> TRIM. That would be a nice combination between wear level resiliency
>> and disk data safety.
>
>That runs counter
If you self-modify /bsd, the hash will disagree.
That deactivates kernel relinking. That is used by developers.
re-create the hash
> Predrag Punosevac wrote:
> >
> > # uname -a
> > OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64
> >
> > # syspatch
> > Get/Verify syspatch62-002_fktrace...
won't help.
it does not adjust the scheduler in that way, at all
> just wondering if anyone else has tried using renice to
> de-prioritise other processes in an effort to give more cpu
> time to packet forwarding in the kernel ?
>
> While Im certain that there significant risks to system stabili
> As a response to this, Theo asked rhetorically "Where's ls, where's cat,
> where's grep, and where's sort?", implying that noone so far bothered to
> write implementations of even the basic unix utilities in such a
> language.
I wasn't implying. I was stating a fact. There has been no attempt
> My goal is not to rip off anyone, but to help the project.
You cannot help the project by begging on a mailing list that
I partake in business.
Get over yourself Jay.
801 - 900 of 3012 matches
Mail list logo
