Re: Kindly support this initiative for a public git repository of OpenBSD source code located at Germany!

[Kai Wetlesen]

Dinesh,

Short answer: No.

Long answer: I speak on behalf of myself only. Just what exactly is wrong
with the already existing CVS? Why is a Git repo required?

Learn CVS, then teach it to your students.

~Kai

> On Dec 28, 2017, at 10:05, Dinesh Thirumurthy  
> wrote:
> 
> Dear Everyone,
> 
>> On Thu, Dec 28, 2017 at 3:05 PM, Mikko Laine  wrote:
>> 
>> You could try https://notabug.org/, which is Dutch-owned and hosted in
>> Germany. Note larger repositories (>100 Mb) are accepted per-case.
> 
> 
> I have requested notabug.org to provide 1GB space for openbsd src git repo.
> It would be good to demonstrate that that you also want this idea
> implemented.
> 
> So, kindly help by voting Yes to my online poll.
> 
> The poll is at https://doodle.com/poll/rbg53x3dyd7i4y5d
> 
> Thanks very much.
> 
> Regards,
> Dinesh Thirumurthy

Commendations on syspatch

[Kai Wetlesen]

Hi devs,
I just wanted to say thank you for your hard work in developing syspatch. It
has made my work as an OpenBSD admin a hell of a lot easier! That is all.
Be merry, or something similar.
~Kai

Re: bug tracking system for OpenBSD

[Kai Wetlesen]

Agreed, partially, with both of you. It may be possible to automatically filter 
some of the chaff (user errors and support requests in disguise) 
in one large batch so to pressed the DB but forwarding mailing list touches 
to the bug tracker would make things ugly fast.

What would be involved to pull the current state of bugs@ and tech@?

> On Dec 25, 2017, at 12:21, Stuart Henderson  wrote:
> 
>> On 2017-12-23, Kapetanakis Giannis  wrote:
>>> On 23/12/17 12:24, Stuart Henderson wrote:
>>> Forwarded? No way! Same for bugs@ as tech@. It needs manual work to
>>> triage, identify what is a bug, follow up with the reporter to make
>>> sure the report is accurate and has enough information to be useful.
>>> Same whatever the entry point is. If reporters can add bugs to it
>>> directly, they need to go into a triage queue and *not* appear in the
>>> main system until that's done.
>>> 
>>> The idea of a bug tracking system is to spread the work and help
>>> people remember things. It should *reduce* work done by devs because
>>> they no longer have to drag even the most basic information out
>>> of a reporter and figure out whether it's a bug or user error
>>> or a support request in disguise.
>>> 
>>> If it means *extra* work for devs, it's not going to work.
>>> 
>>> 
>> 
>> I still don't agree with you about maintaining both @tech/@bugs in 
>> correlation with a web interface (bugtracking).
>> Not a gain, just extra trouble.
> 
> Probably not long term, but looking at existing unfixed bug reports on
> lists would be a good way to seed the database. And information spread
> across multiple mails can be synthesized into a coherent report,
> hopefully going some way to showing others what a proper bug
> submission should actually look like.
> 
>> What happens in other places is that if a mail comes that looks like a 
>> possible ticket (not resolvable by mail), someone replies and says 
>> "please open bug report in https://...;
>> so we can track it.
>> However you 're right with the last paragraph above and it's something I 
>> haven't thought before.
>> More people might get involved and eventually this might get some work 
>> out of the devs.
> 
> 

Re: bug tracking system for OpenBSD

[Kai Wetlesen]

> On Dec 19, 2017, at 14:54, Ted Unangst <t...@tedunangst.com> wrote:
> 
> Kai Wetlesen wrote:
>>>> you don't have to announce your bug database the first day you set it up. 
>>>> in
>>>> fact, it's better not to. but in a few months time, when somebody 
>>>> inevitably
>>>> asks misc how do i contribute, where's the todo list, you'll have this 
>>>> handy
>>>> list of unresolved bugs to point them at.
> 
>> There are many decisions that would need to be made that will piss somebody
>> off. Decisions like what software/platform to use, where to host the thing, 
>> and
>> how much the tool should integrate into existing bug reporting mechanisms
>> (right now just fancy emailing).
>> 
>> To answer your tactful question Theo, I personally haven’t done anything 
>> because
>> I do not have your blessing nor of someone who can say “yes just effing do 
>> it". But,
>> if you would be willing to give me free reign it will be done.
> 
> Imagine if you'd followed my suggestion and spent the last six months curating
> a bug database. Then today you could have sent us a link to it and everybody
> would see how useful it is. Now we have to wait another six months.

Put bluntly, I was busy with completing my bachelors degree which was far
more important. You would have waited six months regardless. Now that it’s 
done and out of the way I’ll happily take your advice.

bug tracking system for OpenBSD

[Kai Wetlesen]

> > Kai Wetlesen wrote:
> > > What would a potential curator of a bug tracker need
> > > to do besides spin up a server, install, and maintain
> > > the chosen (or written) software?
> >
> > not underestimate the effort involved.
> >
> > so this has come up before, and the answer remains the same. anyone can 
> > setup
> > a bug tracker, and feed bugs into it. close the ones that get fixed,
> > categorize the rest, etc.. do that for a few months and see how it goes.
> >
> > i'm not really interested in looking at an empty bug database. nor one 
> > that's
> > filled with crap. so yeah, there's a bootstrapping problem.
> >
> > you don't have to announce your bug database the first day you set it up. in
> > fact, it's better not to. but in a few months time, when somebody inevitably
> > asks misc how do i contribute, where's the todo list, you'll have this handy
> > list of unresolved bugs to point them at.
> >
> > like a lot of projects that seem really easy, you'd think somebody would 
> > just
> > do it if it were that simple. but the idea that nobody wants to chance
> > investing time in a deadend project suggests they kind of know the time
> > investment isn't just a saturday afternoon.
> >
>
> Theo de Raadt wrote:
> Indeed, this thread is full of volunteers, isn't it?
>
> Why haven't one of you already started doing it?
>
> (not including Ted, Ingo, or Antoine, or myself)

There are many decisions that would need to be made that will piss somebody
off. Decisions like what software/platform to use, where to host the thing, and
how much the tool should integrate into existing bug reporting mechanisms
(right now just fancy emailing).

To answer your tactful question Theo, I personally haven’t done anything because
I do not have your blessing nor of someone who can say “yes just effing do it". 
But,
if you would be willing to give me free reign it will be done.

~Kai


signature.asc
Description: Message signed with OpenPGP

Re: Read sysctl from file

[Kai Wetlesen]

> Because it's a nice way to apply configuration changes made to
> /etc/sysctl.conf without restarting the whole server?

Systemctl doesn't offer hot reload unless the 
controlled daemon offers the capability in 
the first place. The only thing systemd does 
is hits the controlling process on the head 
with a known conf-reload signal or (gasp) a 
DBus control statement. Both of these can 
be done just as well with an rc script, and
without restarting the service.

Re: bug tracking system for OpenBSD

[Kai Wetlesen]

Good morning,

In regards to this:

>> would it be possible to establish a real bug tracking system
>> for OpenBSD?
> 
> There is exactly one reason it hasn't happened yet:
> 
> No developer has been able and willing to invest the additional
> time required to set it up and to commit to maintaining it.

What would a potential curator of a bug tracker need
to do besides spin up a server, install, and maintain
the chosen (or written) software?

Cheers,
Kai 

Interest in POWER platform?

[Kai Wetlesen]

Hi all,

What is the current community interest in getting OpenBSD running on the newer 
POWER processors? I have a number of POWER based systems at work which run 
various Linux flavors, but it would be nice to bring OpenBSD to these systems 
as we’re been trying it out in different spaces throughout our division. What 
would it take to get a POWER port up and kicking?

Regards,
Kai