Re: RAID controller

2018-03-31 Thread Jonathan Matthew
On Sat, Mar 31, 2018 at 11:38:52AM -0300, Friedrich Locke wrote:
> Hi folks.
> 
> Does OBSD 6.2 support  DELL H840 and DELL H740p raid controllers ?

No, but 6.3 will.



Re: print usb printer by [ Google Cloud Print for Chromium ]

2018-03-31 Thread Tuyosi T
using [ Google Cloud Print for Chromium ] ,
i  also print text files besides pdf files .

for example
1)  chrome test.txt

2)  right click , then the print menu appears .
(cups is not installed)


Re: bug tracking system for OpenBSD

2018-03-31 Thread Theo de Raadt
Way to go guys, you've completely misunderstood the problem
and therefore have no solution.



Re: bug tracking system for OpenBSD

2018-03-31 Thread Sergey Bronnikov
On 21:17 Fri 30 Mar , Mike Burns wrote:
> On 2018-03-30 23.01.16 +0300, Sergey Bronnikov wrote:
> > I have made a first step forward in direction to OpenBSD bugtracker
> > and imported bugs@ archive to a Fossil SCM -
> > https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
> 
> Ran it through curl:
> 
> - Your cert is invalid.
> - Why does every ticket go to /cgi-bin/b.cgi/honeypot ?

https://www.fossil-scm.org/xfer/help?cmd=/honeypot

The "/honeypot" page:
This page is a honeypot for spiders and bots.

> > Let's discuss a next step.
> 
> Are these triaged?



Re: bug tracking system for OpenBSD

2018-03-31 Thread Sergey Bronnikov
On 21:04 Sat 31 Mar , Consus wrote:
> On 23:01 Fri 30 Mar, Sergey Bronnikov wrote:
> > I have made a first step forward in direction to OpenBSD bugtracker
> > and imported bugs@ archive to a Fossil SCM -
> > https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
> > Let's discuss a next step.
>
> The first obvious problem: you've imported every message in the mailing
> list as a separate ticket:

It is not so. Each ticket in bugtracker is a separate mail thread.  The
problem comes from mail archive on marc.info which I used as reports
archive - each mail is a separate thread. I believe it is due to broken
In-Reply-To field. Each ticket contains a link to the appropriate mail
thread and you can check it yourself with links below.

>   c541065d62 ... kernel/515: Byte-order confusion in CD-ROM drivers
https://marc.info/?l=openbsd-bugs&m=90222460531616&w=2

>   4136fcdc4e ... Re: kernel/515
https://marc.info/?l=openbsd-bugs&m=90222460531621&w=2

> or
>
>   3989e0a08b ... documentation/532: man page 'curs_terminfo' does not 
> exist
 https://marc.info/?l=openbsd-bugs&m=90222460531656&w=2

>   0486b260d2 ... Re: documentation/532
https://marc.info/?l=openbsd-bugs&m=90222460531658&w=2

> So the main advantage of the bug tracking system (ability to follow the
> history of actions) is lost.
>
> Or I got something wrong, the UI is kinda strange.

Setup another bugtracker which you like, connect it to bugs@ and send a
link to this thread.



Re: bug tracking system for OpenBSD

2018-03-31 Thread Consus
On 21:04 Sat 31 Mar, Consus wrote:
> On 23:01 Fri 30 Mar, Sergey Bronnikov wrote:
> > I have made a first step forward in direction to OpenBSD bugtracker
> > and imported bugs@ archive to a Fossil SCM -
> > https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
> > Let's discuss a next step.
> 
> The first obvious problem: you've imported every message in the mailing
> list as a separate ticket:
> 
>   c541065d62 ... kernel/515: Byte-order confusion in CD-ROM drivers 
>   4136fcdc4e ... Re: kernel/515
> 
> or
> 
>   3989e0a08b ... documentation/532: man page 'curs_terminfo' does not 
> exist
>   0486b260d2 ... Re: documentation/532
> 
> So the main advantage of the bug tracking system (ability to follow the
> history of actions) is lost.
> 
> Or I got something wrong, the UI is kinda strange.

Oh, I got it. User comments are being added properly only if replies to

subsytem/id: subject

are in form

RE: subsystem/id: subject

which is not always the case as

RE: subsystem/id

is also frequent.

Also ALL tickets are opened.



Re: bug tracking system for OpenBSD

2018-03-31 Thread Consus
On 23:01 Fri 30 Mar, Sergey Bronnikov wrote:
> I have made a first step forward in direction to OpenBSD bugtracker
> and imported bugs@ archive to a Fossil SCM -
> https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
> Let's discuss a next step.

The first obvious problem: you've imported every message in the mailing
list as a separate ticket:

c541065d62 ... kernel/515: Byte-order confusion in CD-ROM drivers 
4136fcdc4e ... Re: kernel/515

or

3989e0a08b ... documentation/532: man page 'curs_terminfo' does not 
exist
0486b260d2 ... Re: documentation/532

So the main advantage of the bug tracking system (ability to follow the
history of actions) is lost.

Or I got something wrong, the UI is kinda strange.



howto configure a virtual switch for vmd network

2018-03-31 Thread niya

hi

how do i configure a virtual switch to connect the interfaces of several 
vm's together.
the interfaces will have fixed addresses and i will also be bridging the 
interfaces to the host.

i know how to set up the bridge and then configure it with vm.conf
but i not sure how to setup the switch and add the vio interfaces to the 
switch.


shadrock



Re: bug tracking system for OpenBSD

2018-03-31 Thread Rupert Gallagher
Just use github, and be happy.


RAID controller

2018-03-31 Thread Friedrich Locke
Hi folks.

Does OBSD 6.2 support  DELL H840 and DELL H740p raid controllers ?

Thanks a lot.


Re: bug tracking system for OpenBSD

2018-03-31 Thread Eric Furman
On Fri, Mar 30, 2018, at 4:01 PM, Sergey Bronnikov wrote:
> I have made a first step forward in direction to OpenBSD bugtracker
> and imported bugs@ archive to a Fossil SCM -
> https://bronevichok.ru/cgi-bin/b.cgi/rptview?rn=1
> Let's discuss a next step.
> 

You think I'm going to visit a .ru website?