Re: Why isn't OpenBSD in Google Summer of Code 2017?...

[ludovic coues]

On 6 Apr 2017 12:59 am, "Luke Small"  wrote:

I suspect that unless you really know what you are doing, you'll never
satisfy
the OpenBSD gods. I suspect that there is a good reason that pkg_add was
rewritten in perl. I suspect because it may have been written in perl. And
just like that a
good idea wasn't completely done in another way.

There are no "OpenBSD" gods. Only a few developer with something like 20
years of experience writing C code.
They managed to work for a project that value good work as much as they do.

So of course they won't let any junk in the tree. And saying stuff like "we
could do privsep later" won't help.
If you need an example of how to do it the right way, look at xwallpaper.
Someone found something to improve. They have done that and put the code
somewhere accessible. I might end up in the tree, it might not. Who know ?

Two years ago, I was told there is a lot of work to do on the usb stack.

Substitute for other variables in pkg.conf(5)

[bytevolcano]

Since pkg.conf(5) is no longer used, how would you set fullwidth,
loglevel, nochecksum, ntogo?

In particular, I am interested in fullwidth, loglevel, and ntogo.

msdosfs filenames encoding

[Manos Pitsidianakis]

I have some FAT32 devices (Rockbox firmware only supports that,
unfortunately), mounted with `mount -t msdos ...` and in them I have
many files in non-ascii filenames.  While I can see encoding inside the
files (eg: cat-ing a text file), I get mangled filenames:

% \ls _*
___ү_~1:
1985-_~1 1987-_~1 1990-_~1 1993-_~1 1996-_~1 1999-_~1

~1:
2000-_~1 2000-_~2 2003-_~1 2008-_~1

__ٯ__~1:
1994-_~1 1997-_~1 1999-_~1 2003-_~1 2005-_~1 2008-?~1

~1:
1981-_~1 1985-_~1 1988-_~1 1991-_~1 2005-_~1 2007-_~1 2009-2~1

etc.

I get the same behaviour on bash, zsh, ksh. The filesystem and files have
been created on a linux machine.

Is this a msdosfs bug? I see in sys/msdosfs/msdosfs_conv.c that
filenames are converted in through an ascii table, instead of passing
the raw bytes (If I am not mistaken). I don't know why 0x5f (underscore)
would be there instead. How should I begin looking to correct this?

Re: Topics for revised PF and networking tutorial

[lists]

Wed, 5 Apr 2017 17:46:18 +0200 Marko Cupać 
> On Sat, 1 Apr 2017 10:52:20 +0200
> "Peter N. M. Hansteen"  wrote:
>
> > Hi,
> >
> > I thought I'd like to give you a heads up that there will be a "PF and
> > networking" tutorial at BSDCan 2017 in Ottawa this June.
> >
> > The session will however not be the Nth rerun of the old one, we're
> > starting from scratch this time, and were looking for input on what to
> > include.
> >
> > Do you have questions on PF and related matters, or are there specific
> > topics you would like to see covered?
> >
> > We want to hear from you, either contact us directly at the reply-to
> > address use the list.
>
> Queueing. Prioritization. Throttling.

Hi Peter, misc@,

I would second the coherent practical examples in: queues, priorities,
bandwidth caps, normalisation & reordering to have quality of service.

And all required steps to achieve an advanced fully functional feature
full typical home, office, lab, ISP, enterprise, etc setups iterative,
each time incrementally enhancing the previous set of tricks and skill
one game at a time, much more a practical hands on approach to the PF.

Including performing common tasks of monitoring, maintenance, upgrade,
conflict resolve, capturing, post processing, sanitation, enhancement.
My personal interests have always been practical application examples,
especially these extending the previous ones in a connected structure.

>From the default rule set after installation, through getting Internet
working, and then fixing most common pitfalls of poor packet scheduler
practices (or lack of) in (dumb) broadband equipment.. through solving
all aspects to realisation of complete deployments, as YOU learned it.

The PF features got implemented over time, to solve real actual needs.
The typical new user begins with small common tasks up to their needs.
The full example shows a complete configuration addressing most needs.
The best tutorials give a practical approach to fulfil the real needs.

I dream of a revised PF and networking tutorial from sketch to artist.
Thank you ALL for the hard work over the years to complement OpenBSD..

Kind regards,
Anton Lazarov

> I have hard time configuring these since years now. The fact (or is
> it rumour?) that prio works only when physical interface bandwidth is
> saturated couldn't be read in manpages, pf faq, or other 'official'
> docs, I heard about it by chance:
> [https://marc.info/?l=openbsd-misc&m=145261341431381&w=2]
>
> I still haven't found a way to throttle down queues to desired values
> without using fixed min and max values. Adding NAT to the mix
> complicates things further. What about queueing of traffic inside GRE
> tunnels in transport mode protected with IPSEC? Where to read about it?
>
> Optimistic me believes that devs are too busy making stuff work and
> have no time to explain it to us poor admins (by means of manpages,
> faqs or howtos). But how can I know how to use it if I can't read about
> it anywhere?
>
> Pessimistic me starts to notice that less and less free knowledge can be
> found around the 'net. If I want answers to my questions, is the
> best way to start saving money for paying OpenBSD consultants hourly
> rates for tuition?
>
> If there's any way I could help, don't hesitate to contact me.
> --
> Before enlightenment - chop wood, draw water.
> After  enlightenment - chop wood, draw water.
>
> Marko Cupać
> https://www.mimar.rs/