date:20141101

On 1 November 2014 23:56, noah pugsley  wrote:
>
> Relayd basically contained (as I understand it) most of the
> functionality of a stand alone web server. Reyk pulled that
> functionality out and made it one. He talks all about it in this
> interview:
>
> http://www.bsdnow.tv/episodes/2014_09_03-its_hammer_time

Skip forward to 8m56s for reyk@. Direct link:

https://www.youtube.com/watch?v=Ofr_izIdKaU&t=8m56s

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

>On 11/02/14 00:51, Theo de Raadt wrote:
>>> On 2 November 2014 06:15, Theo de Raadt  wrote:
 A "serial console" is a serial port on a machine exposing it's boottime
 console.  OpenBSD cannnot use select a USB serial connector as a console
 tty, no more than it can select some random serial pci card.  The logic
 for finding the device happens too late.

 If this is the other way around, then the laptop is just doing serial.
 What's console about it.  It is just talking serial, to something else
 which is console.  You don't need the word console, nor do we need
 to know the colour of the cable you choose.

 Naddy is precise.  You used the wrong words.
>>> Ah, okay. Thank you. But even if the laptop end of the setup wouldn't
>>> properly be called a serial console, do I understand correctly then
>>> that it would work to use it with a run-of-the-mill USB-to-serial
>>> adapter in the way I describe? Meaning, use it as a terminal (or
>>> terminal emulator, or technically, laptop, running OpenBSD, running a
>>> terminal emulat-- arrgh!). Anyway, do I understand correctly that it
>>> would work the way I expect, and that (my imprecise terminology
>>> notwithstanding) Patrick's reply is applicable?
>>>
>>> And further, just to make sure I'm really getting this, is it actually
>>> correct then to call the (bog standard) physical RS-232 port on the
>>> headless computer the serial console? Or am I still on the wrong
>>> track, and does a real, genuine, proper serial console involve custom
>>> hardware beyond a standard physical serial port?
>> That is a lot of words.  I do not understand your questions.
>>
>> Can a device which does serial console expose it's console over serial
>> to another device which does serial?
>>
>> Yes.
>>
>> Because serial ports can talk to each other.
>>
>> Whatever you want, just try it.  Unbelievable..
>>
>
>
>Sounds like the question, in a very around about way, is can you use a 
>laptop or desktop with a USB to serial converter with  a given terminal 
>program to communicate with an OpenBSD machine that uses a serial console.
>
>The answer is yes and I fail to see why this is such a problem.


It is a problem because he doesn't have the hardware in the first
place!



So I have a question.  I don't wood work, and I don't have any wood,
and I don't have any wood working tools, but if I was to, er, what is
the word -- is it "lathe"?  That spinny thing?  What happens if my
power cable gets unplugged while I am doing that.  Do I just plug it
in?  Thanks.  I was curious.  So excited to hear the answers.

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

>On 2 November 2014 06:51, Theo de Raadt 
>> Whatever you want, just try it.  Unbelievable..
>
>I don't actually have a USB-to-serial adapter yet. I was trying to ask
>before buying something that wouldn't work.
>I'm dimly aware that USB-to-serial can be problematic in some cases. I
>wasn't sure if this would be one of those.
>
>Sorry for the noise.

So let's get this clear.

Don't have it, but if you did you might try something you don't
understand.

So, let's go bother some people with non-understanding questions
and see what pops out.

Go a few cycles.

Then when you realize you don't understand hardware you don't have,
you apologize.

Amazing.

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

2014-11-01 Thread Stan Gammons


On 11/02/14 00:51, Theo de Raadt wrote:

On 2 November 2014 06:15, Theo de Raadt  wrote:

A "serial console" is a serial port on a machine exposing it's boottime
console.  OpenBSD cannnot use select a USB serial connector as a console
tty, no more than it can select some random serial pci card.  The logic
for finding the device happens too late.

If this is the other way around, then the laptop is just doing serial.
What's console about it.  It is just talking serial, to something else
which is console.  You don't need the word console, nor do we need
to know the colour of the cable you choose.

Naddy is precise.  You used the wrong words.

Ah, okay. Thank you. But even if the laptop end of the setup wouldn't
properly be called a serial console, do I understand correctly then
that it would work to use it with a run-of-the-mill USB-to-serial
adapter in the way I describe? Meaning, use it as a terminal (or
terminal emulator, or technically, laptop, running OpenBSD, running a
terminal emulat-- arrgh!). Anyway, do I understand correctly that it
would work the way I expect, and that (my imprecise terminology
notwithstanding) Patrick's reply is applicable?

And further, just to make sure I'm really getting this, is it actually
correct then to call the (bog standard) physical RS-232 port on the
headless computer the serial console? Or am I still on the wrong
track, and does a real, genuine, proper serial console involve custom
hardware beyond a standard physical serial port?

That is a lot of words.  I do not understand your questions.

Can a device which does serial console expose it's console over serial
to another device which does serial?

Yes.

Because serial ports can talk to each other.

Whatever you want, just try it.  Unbelievable..




Sounds like the question, in a very around about way, is can you use a 
laptop or desktop with a USB to serial converter with  a given terminal 
program to communicate with an OpenBSD machine that uses a serial console.


The answer is yes and I fail to see why this is such a problem.


Stan

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

On 2 November 2014 06:51, Theo de Raadt 
> Whatever you want, just try it.  Unbelievable..

I don't actually have a USB-to-serial adapter yet. I was trying to ask
before buying something that wouldn't work.
I'm dimly aware that USB-to-serial can be problematic in some cases. I
wasn't sure if this would be one of those.

Sorry for the noise.

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

>On 2 November 2014 06:15, Theo de Raadt  wrote:
>> A "serial console" is a serial port on a machine exposing it's boottime
>> console.  OpenBSD cannnot use select a USB serial connector as a console
>> tty, no more than it can select some random serial pci card.  The logic
>> for finding the device happens too late.
>>
>> If this is the other way around, then the laptop is just doing serial.
>> What's console about it.  It is just talking serial, to something else
>> which is console.  You don't need the word console, nor do we need
>> to know the colour of the cable you choose.
>>
>> Naddy is precise.  You used the wrong words.
>
>Ah, okay. Thank you. But even if the laptop end of the setup wouldn't
>properly be called a serial console, do I understand correctly then
>that it would work to use it with a run-of-the-mill USB-to-serial
>adapter in the way I describe? Meaning, use it as a terminal (or
>terminal emulator, or technically, laptop, running OpenBSD, running a
>terminal emulat-- arrgh!). Anyway, do I understand correctly that it
>would work the way I expect, and that (my imprecise terminology
>notwithstanding) Patrick's reply is applicable?
>
>And further, just to make sure I'm really getting this, is it actually
>correct then to call the (bog standard) physical RS-232 port on the
>headless computer the serial console? Or am I still on the wrong
>track, and does a real, genuine, proper serial console involve custom
>hardware beyond a standard physical serial port?

That is a lot of words.  I do not understand your questions.

Can a device which does serial console expose it's console over serial
to another device which does serial?

Yes.

Because serial ports can talk to each other.

Whatever you want, just try it.  Unbelievable..

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

On 2 November 2014 06:15, Theo de Raadt  wrote:
> A "serial console" is a serial port on a machine exposing it's boottime
> console.  OpenBSD cannnot use select a USB serial connector as a console
> tty, no more than it can select some random serial pci card.  The logic
> for finding the device happens too late.
>
> If this is the other way around, then the laptop is just doing serial.
> What's console about it.  It is just talking serial, to something else
> which is console.  You don't need the word console, nor do we need
> to know the colour of the cable you choose.
>
> Naddy is precise.  You used the wrong words.

Ah, okay. Thank you. But even if the laptop end of the setup wouldn't
properly be called a serial console, do I understand correctly then
that it would work to use it with a run-of-the-mill USB-to-serial
adapter in the way I describe? Meaning, use it as a terminal (or
terminal emulator, or technically, laptop, running OpenBSD, running a
terminal emulat-- arrgh!). Anyway, do I understand correctly that it
would work the way I expect, and that (my imprecise terminology
notwithstanding) Patrick's reply is applicable?

And further, just to make sure I'm really getting this, is it actually
correct then to call the (bog standard) physical RS-232 port on the
headless computer the serial console? Or am I still on the wrong
track, and does a real, genuine, proper serial console involve custom
hardware beyond a standard physical serial port?

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

>> On 2014-11-01, ropers  wrote:
>>> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
>>> as a serial console? (You know, instead of hardware that has a native
>>> RS-232 port?
>
>On 1 November 2014 23:51, Christian Weisgerber  wrote:
>> This is impossible.  The serial part is on the wrong end.  The
>> console code would have to drive a USB device with all the USB bus
>> complexity.
>
>I'm having one heck of a hard time understanding why it's impossible,
>or maybe we're talking at cross-purposes.
>Maybe I've expressed myself imprecisely or incorrectly. Are we even
>talking about the same thing?
>
>When I said I wanted to use a USB-only laptop *as* a serial console,
>what I meant was this:

A "serial console" is a serial port on a machine exposing it's boottime
console.  OpenBSD cannnot use select a USB serial connector as a console
tty, no more than it can select some random serial pci card.  The logic
for finding the device happens too late.

If this is the other way around, then the laptop is just doing serial.
What's console about it.  It is just talking serial, to something else
which is console.  You don't need the word console, nor do we need
to know the colour of the cable you choose.

Naddy is precise.  You used the wrong words.

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

> On 2014-11-01, ropers  wrote:
>> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
>> as a serial console? (You know, instead of hardware that has a native
>> RS-232 port?

On 1 November 2014 23:51, Christian Weisgerber  wrote:
> This is impossible.  The serial part is on the wrong end.  The
> console code would have to drive a USB device with all the USB bus
> complexity.

I'm having one heck of a hard time understanding why it's impossible,
or maybe we're talking at cross-purposes.
Maybe I've expressed myself imprecisely or incorrectly. Are we even
talking about the same thing?

When I said I wanted to use a USB-only laptop *as* a serial console,
what I meant was this:

1. There is a headless computer that has a physical RS-232. This is
not the laptop.
2. There is a laptop that has USB but lacks a built-in RS-232.
3. I want to buy a USB-to-serial adapter to plug into that laptop.
Then I want to use a null-modem cable to connect that
serial-port-on-a-dongle to the headless computer's physical serial
port.
4. I do not expect to capture the laptop's bootup kernel messages. I
do not expect to run the laptop in single user mode. The laptop would
be fully booted up and running a (fancy or barebones tty) terminal
emulator program. I would however hope to be able to capture the
headless computer's output (from the point where it's redirected to
serial) and give it keyboard input from the laptop.

Is that what we're both talking about?
And if so, is that actually impossible?
And if so, could you elaborate on why that is? I'm not sure I've
understood your explanation correctly.
Corollary question: Is Patrick's advice applicable or yours?

regards,
ropers

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

2014-11-01 Thread patrick keshishian

On 11/1/14, Christian Weisgerber  wrote:
> On 2014-11-01, patrick keshishian  wrote:
>
>>> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
>>> as a serial console? (You know, instead of hardware that has a native
>>> RS-232 port?
>>
>> Yes. I use such a setup on one "server". You need to add the
>> appropriate /dev/ttyUx in your /etc/ttys and ensure ttyflags(8)
>> runs after the device attaches.
>
> Running a getty(8) on a serial port is not a console.  You have no
> access to boot(8), boot_config(8), the bootup kernel messages, or
> single-user mode.

of course it isn't. I took some liberty in interpreting what
functionally the OP was after.

--patrick

Re: The Book of PF, 3rd ed: You own the first author signed copy and support OpenBSD!

2014-11-01 Thread Michael W. Lucas

On Sat, Nov 01, 2014 at 09:23:35PM +0100, Peter N. M. Hansteen wrote:
> pe...@bsdly.net (Peter N. M. Hansteen) writes:
> The amount is certainly in the comfortable zone for me, and with three
> days to go it's entirely possible that this auction will indeed bring
> in more money than Michael Lucas' Absolute OpenBSD, 2nd edition
> auction[2].

Bah! Not a chance.

If by some bizarre failure of natural law that should happen, I'll be
compelled to write an OpenBSD book next year to auction off. Just so
MY next auction can CRUSH HANSTEEN'S ABSURD FLUKE OF LUCK AND RESTORE
THE NATURAL ORDER.

I mean, the footnotes in BoPF3 all contain actual *facts* -- how lame
is that?

> One other point worth considering is that with both Michael Lucas and
> me setting up these auctions, we have essentially created a new rule:
> If you write an OpenBSD book, you are morally obliged to auction off
> the first signed copy for the benefit of the project. That should not
> be seen as a barrier to entry, rather the opposite.

Only if you want to be one of the cool kids.

==ml

-- 
Michael W. Lucas  -  mwlu...@michaelwlucas.com, Twitter @mwlauthor 
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/

Re: Logging Password change attempts

2014-11-01 Thread Stuart Henderson

On 2014-10-31, David Coppa  wrote:
> Or you can log every command issued on the system...
> Your management would be very happy! ;) ;)
>
> http://pastebin.com/FZw4rT3T

That adds an easy DoS on a machine with serial console ;)

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

2014-11-01 Thread Christian Weisgerber

On 2014-11-01, patrick keshishian  wrote:

>> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
>> as a serial console? (You know, instead of hardware that has a native
>> RS-232 port?
>
> Yes. I use such a setup on one "server". You need to add the
> appropriate /dev/ttyUx in your /etc/ttys and ensure ttyflags(8)
> runs after the device attaches.

Running a getty(8) on a serial port is not a console.  You have no
access to boot(8), boot_config(8), the bootup kernel messages, or
single-user mode.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: OpenBSD 5.6 Released

2014-11-01 Thread noah pugsley

On Sat, Nov 1, 2014 at 3:10 PM, bofh  wrote:
> Thank you!  By the way, I read this on undeadly.  Any pointers?  What is
> this internally developed httpd server?  Thanks.
>
> *Advanced notice: Big changes coming for future releases!*
> There are some big changes coming up in OpenBSD 5.7 (NOT 5.6!) that you may
> wish to think about and plan for.
>
>- OpenBSD's version of nginx will be removed from base in favor of an
>internally developed httpd server in 5.7. nginx will be available as a
>package 
> for those with applications dependent upon it.
>
> [oops:  the original was sent only to Antoine]
>

Relayd basically contained (as I understand it) most of the
functionality of a stand alone web server. Reyk pulled that
functionality out and made it one. He talks all about it in this
interview:

http://www.bsdnow.tv/episodes/2014_09_03-its_hammer_time

Oh, and thanks y'all for the release.

-noah

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

2014-11-01 Thread Christian Weisgerber

On 2014-11-01, ropers  wrote:

> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
> as a serial console? (You know, instead of hardware that has a native
> RS-232 port?

This is impossible.  The serial part is on the wrong end.  The
console code would have to drive a USB device with all the USB bus
complexity.

For laptops with Intel AMT, it should be possible to use the
serial-over-LAN feature (cf. the comms/amtterm port).

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: still loosing connections

An other case of TL:DR???

Please help me with a 'clue-stick' on how to investigate further.

By now I use the very latest version as of Novemnber 1st:
OpenBSD 5.6-current (GENERIC.MP) #509: Sat Nov  1 00:18:49 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

The settings are the same yet the issue is still unsolved - and I have
no idea what I am doing wrong...

BTW: Received my two copies of 5.6 yesterday in Germany: One for my
shelf, one to give away.

Again: Please help me as I am lost.

Thanks,
STEFAN



Am 10/26/14 um 09:59 schrieb Stefan Wollny:
> Hi misc@!
> 
> I run OpenBSD-{amd64,i386}-current for several years now on 3
> machines, having reinstalled everything late this summer because
> s.th. related to either adsuck, ftp, cvs, pf or the netstack in
> general feels broken.
> 
> I have complained before in the last weeks but unfortunatelly the 
> usually reliable strategy "shut up - the devs know already - use
> the next shnapshot" seems to be not really successfull this
> time...
> 
> Let me describe what I am doing and what happens (the laptop being 
> "idefix" @ 192.168.178.31): Running -current I try to use the
> latest snapshot, being ~amd64 #477 from yesterday (dmesg below).
> This is how I do it:
> 
> 
> #!/bin/sh # print "Laufwerk wechseln" cd
> /home//Downloads/amd64/ print "Dateien loeschen" rm * print
> "Dateien neu holen" #wget 
> ftp://openbsd.cs.fau.de/pub/OpenBSD/snapshots/amd64/{IN*,SHA*,bsd*,*tgz}
>
> 
#wget
> ftp://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/{IN*,SHA*,bsd*,*tgz}
>
> 
#wget ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/{IN*,SHA*,bsd*,*tgz}
> wget
> http://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/INSTALL.amd64 
> wget
> http://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/SHA256{,.sig} 
> wget
> http://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/bsd{,.rd,.mp} 
> wget 
> http://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/{base,comp,game,man}56.tgz
>
> 
wget
> http://ftp.hostserver.de/pub/OpenBSD/snapshots/amd64/x{base,font,serv,share}56.tgz
>
> 
print "Altes /bsd.rd sichern"
> sudo cp /bsd.rd /bsd.rd.1 print "Neues /bsd.rd kopieren" sudo cp -p
> bsd.rd / print "Neues bsd.mp als /bsd kopieren" sudo cp -p bsd.mp
> /bsd print "/usr RW mounten" sudo mount -uw /usr print "untar
> xfonts" sudo tar -C / -xzphf xfont*.tgz print "untar xserv" sudo
> tar -C / -xzphf xserv*.tgz print "untar xshare" sudo tar -C /
> -xzphf xshare*.tgz print "untar man" sudo tar -C / -xzphf man*.tgz 
> print "untar comp" sudo tar -C / -xzphf comp*.tgz print "untar
> xbase" sudo tar -C / -xzphf xbase*.tgz print "untar base" sudo tar
> -C / -xzphf base*.tgz print "run sysmerge" sudo sysmerge print
> "mount /usr RO" sudo mount -ur /usr cd
> 
> I switched to the "http"-protocol because of the issue desribed
> below though it didn't help.
> 
> After updating the snapshot I _always_ update the apps and sources
> like so:
> 
> #!/bin/sh # cd /tmp sudo mount -uw /usr print "/usr/src updaten" cd
> /usr/src sudo cvs -q up -Pd print "/usr/xenocara updaten" cd
> /usr/xenocara sudo cvs -q up -Pd print "/usr/ports updaten" cd
> /usr/ports sudo cvs -q up -Pd cd print "packages updaten" sudo
> pkg_add -ui print "locate-db updaten" sudo
> /usr/libexec/locate.updatedb sudo mount -ur /usr
> 
> So my guess is that my system is "up2date". Except that since
> several weeks now both scripts suffer from the same shortcomming: 
> After some (non repeatable) time the network looses it's
> connection. Not always, but way too often. And it doesn't matter if
> I am at home wired or travelling using the mobile or the
> hotel-wlan. It doesn't matter which mirror I use.
> 
> Simplyfying the observation it seems that the very moment the load 
> increases the connection decreases to zero.
> 
> I have gkrellm running at the side showing the network performance.
> So please be patient with me as I have no scientifically valid test
> data - only visual observation: The system is getting the fresh
> data, at first at an acceptabel pace (e.g. 800 KB/s) but then
> quickly gets slower and slower until connection to the net is 
> entirely lost. Not only ftp but http as well. Please do not get
> mislead by the fact that /var/log/messages mentions adsuck -
> without the behaviour is the same:
> 
> ~ $ tail -f /var/log/messages Oct 25 23:28:28 idefix /bsd: drm:
> PCIE GART of 512M enabled (table at 0x0004). Oct 25
> 23:28:28 idefix /bsd: radeondrm0: 1400x1050 Oct 25 23:28:28 idefix
> /bsd: wsdisplay0 at radeondrm0 mux 1: console (std, vt100
> emulation), using wskbd0 Oct 25 23:28:28 idefix /bsd: wskbd1:
> connecting to wsdisplay0 Oct 25 23:28:28 idefix /bsd: wsdisplay0:
> screen 1-5 added (std, vt100 emulation) Oct 25 23:28:44 idefix
> savecore: no core dump Oct 25 23:29:09 idefix apmd: battery status:
> high. external power status: connected. estimated battery life
> 100% Oct 25 23:30:09 idefix sensorsd[12040]: acpithinkpad0.temp5:
> marked invalid Oct 25 23:30:09 idefix sensorsd

Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

2014-11-01 Thread patrick keshishian

Hi,

On 11/1/14, ropers  wrote:
>> o New uscom(4) driver for simple USB serial adapters.
>
> This reminds me of something I've been meaning to ask for some time:
>
> * Has anyone here used a USB-only laptop with a USB-to-serial adapter
> as a serial console? (You know, instead of hardware that has a native
> RS-232 port?

Yes. I use such a setup on one "server". You need to add the
appropriate /dev/ttyUx in your /etc/ttys and ensure ttyflags(8)
runs after the device attaches. I haven't automated this on
the one box; hotplugd(8) may be the tool for this task.

> * Does uscom(4) make this any easier/is it more compatible than ucom(4)?
> * If I buy a random USB-to-serial dongle, is it likely that it'll work
> with either uscom(4) or ucom(4)? If not, does anyone have any hardware
> recommendations, i.e. what do you use?

I have about four such usb/serial devices. I purchased all
of them blindly, at different times, and all of them happen
to "just work".

One I have handy right now shows up as:
uplcom0 at uhub0 port 1 "Prolific Technology Inc. USB-Serial
Controller D" rev 1.10/4.00 addr 3
ucom0 at uplcom0

Another as:
uftdi0 at uhub1 port 5 "FTDI usb serial controler" rev 1.10/4.00 addr 2
ucom0 at uftdi0 portno 1.

I don't think I paid anything more than $12USD for each.

--patrick

> Thanks for any input
>
> regards,
> ropers

Re: OpenBSD 5.6 Released

2014-11-01 Thread bofh

Thank you!  By the way, I read this on undeadly.  Any pointers?  What is
this internally developed httpd server?  Thanks.

*Advanced notice: Big changes coming for future releases!*
There are some big changes coming up in OpenBSD 5.7 (NOT 5.6!) that you may
wish to think about and plan for.

   - OpenBSD's version of nginx will be removed from base in favor of an
   internally developed httpd server in 5.7. nginx will be available as a
   package 
for those with applications dependent upon it.

[oops:  the original was sent only to Antoine]

OpenBSD MinGW Error: windows.h: No such file or directory

2014-11-01 Thread Jorge Castillo

The following applies to OpenBSD 5.5 & 5.6, I didn't tried this with any
previous release. I am runnig OpenBSD in VirtualBox.

This:
/usr/local/share/doc/pkg-readmes/mingw-1.0.1p3

Says that all you have to do to compile an exe is:

$ export PATH=/usr/local/mingw32/bin:${PATH}
$ g++ CreateFile.cpp -o CreateFile.exe

But I get a bunch of errors. After googling and trying a few things,
I got this to work by doing it this way:

$ g++ -I/usr/local/mingw32/include CreateFile.cpp -o CreateFile.exe

I tested this solution with the provided test code in the pkg-readme &
a very small non GUI program I did for a school assignment. The exes
worked fine in a Windows7 x64 virtual machine.

Is this the obvious solution to the error or am I doing something wrong?

uscom/ucom hardware question [was: OpenBSD 5.6 Released]

> o New uscom(4) driver for simple USB serial adapters.

This reminds me of something I've been meaning to ask for some time:

* Has anyone here used a USB-only laptop with a USB-to-serial adapter
as a serial console? (You know, instead of hardware that has a native
RS-232 port?
* Does uscom(4) make this any easier/is it more compatible than ucom(4)?
* If I buy a random USB-to-serial dongle, is it likely that it'll work
with either uscom(4) or ucom(4)? If not, does anyone have any hardware
recommendations, i.e. what do you use?

Thanks for any input

regards,
ropers

Re: 5.4 instead of 5.5 in faq1.html

2014-11-01 Thread Clint Sand

On Sat, Nov 01, 2014 at 04:44:17PM -0400, Nick Holland wrote:
> On 11/01/14 15:26, Eduardo Lopes wrote:
> > In http://www.openbsd.org/faq/faq1.html#WhatsNew:
> > 
> > "The complete list of changes made to OpenBSD 5.4 to create OpenBSD 5.6 
> > can[...]"
> > 
> > I think that 5.4 was left behind, wasn't it? 
> > 
> 
> yep, thanks
> 
> Nick.

I found a few similar things in reading today but wasn't sure to expect them 
all to be changed yet on day one. 

"Our policy requires mirrors to carry at least the last two releases in binary 
form (currently 5.4 and 5.5)",

on http://www.openbsd.org/ftp.html for example.

Re: 5.4 instead of 5.5 in faq1.html

2014-11-01 Thread Nick Holland

On 11/01/14 15:26, Eduardo Lopes wrote:
> In http://www.openbsd.org/faq/faq1.html#WhatsNew:
> 
> "The complete list of changes made to OpenBSD 5.4 to create OpenBSD 5.6 
> can[...]"
> 
> I think that 5.4 was left behind, wasn't it? 
> 

yep, thanks

Nick.

Re: The Book of PF, 3rd ed: You own the first author signed copy and support OpenBSD!

2014-11-01 Thread Peter N. M. Hansteen

pe...@bsdly.net (Peter N. M. Hansteen) writes:

> It's that scribe from the fjords again. Today I took delivery of my
> The Book of PF 3rd edition author copies, and I blogged about it:
> http://bsdly.blogspot.no/2014/10/the-book-of-pf-3rd-edition-is-here.html

On OpenBSD 5.6 release day, auction status after one week is this (see
[1] for details):

A total of 20 bids, with the current high bid at US $1,009.99.

The amount is certainly in the comfortable zone for me, and with three
days to go it's entirely possible that this auction will indeed bring
in more money than Michael Lucas' Absolute OpenBSD, 2nd edition
auction[2].

If that happens I'll be very pleased, but regardless of the final
amount I hope the successful bidder will allow me to publish their
name and that the unsuccessful bidders will make direct donations to
the OpenBSD Foundation equal to or larger than the amount of their
highest bid.

One other point worth considering is that with both Michael Lucas and
me setting up these auctions, we have essentially created a new rule:
If you write an OpenBSD book, you are morally obliged to auction off
the first signed copy for the benefit of the project. That should not
be seen as a barrier to entry, rather the opposite.

Now enjoy the weekend and the newly arrived OpenBSD 5.6 release, I'll
be back with useful updates as soon as I have them.

- Peter

[1]
http://www.ebay.com/itm/The-Book-of-PF-3rd-ed-signed-by-the-author-First-Copy-signed-/321563281902?
[2] http://blather.michaelwlucas.com/archives/1646
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: OpenBSD 5.6 Released

2014-11-01 Thread Vijay Sankar


Quoting Antoine Jacoutot :


November 1, 2014.

We are pleased to announce the official release of OpenBSD 5.6.
This is our 36th release on CD-ROM (and 37th via FTP/HTTP).  We remain
proud of OpenBSD's record of more than ten years with only two remote
holes in the default install.



Thank you all for the best OS!! The 5.6 CD art work is the best one  
since I started collecting. Congratulations on 5.6 as well as the CD  
artwork and song.


Also wanted to mention that the new folks who took over from the  
computer shop  did a great job with shipping/handling. Based on the  
date on the postage, it took only 5 days to get it from England (from  
Calgary to Winnipeg it used to take 4 days!)


Vijay

Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca

-
This message was sent using ForeTell-POST 4.9

Re: still loosing connections

An other case of TL:DR???

Please help me with a 'clue-stick' on how to investigate further.

By now I use the very latest version as of Novemnber 1st:
OpenBSD 5.6-current (GENERIC.MP) #509: Sat Nov  1 00:18:49 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

The settings are the same yet the issue is still unsolved - and I have
no idea what I am doing wrong...

BTW: Received my two copies of 5.6 yesterday in Germany: One for my
shelf, one to give away.

Again: Please help me as I am lost.

Thanks,
STEFAN


New DMESG:

OpenBSD 5.6-current (GENERIC.MP) #509: Sat Nov  1 00:18:49 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3203203072 (3054MB)
avail mem = 3109294080 (2965MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version "79ETC9WW (2.09 )" date 12/22/2006
bios0: LENOVO 2007VG2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4)
EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3)
HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.61 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.34 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "92P1139" serial  2887 type LION oem
"Panasonic"
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1300 M52-64"
rev 0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog
Devices AD1981HD
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address
00:15:58:81:15:fb
ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
msi, MoW2, address 00:19:d2:85:6f:4d
ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: msi
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: msi
pci5 at ppb4 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb5 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci6 at ppb5 bus 21
cbb0 at pci6 dev 0 function 0 "TI PCI1510 CardBus" rev 0x00: apic 1 int 16
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0
pcmcia0

Calligra won't start

hi there,

I came across another issue with an app:

Calligra won't start, neither if installed from packages nor compiled
from ports.

~ $ calligra
calligra:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.16.0 :
WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch,
relink your program
Legacy integer arithmetics implementation
calligra(29349) in free(): error: bogus pointer (double free?) 0x5a74325d9a0
KCrash: Application 'calligra' crashing...
calligra(29349) in calloc(): error: recursive call
Unable to start Dr. Konqi

What can I do to investigate further into this problem???

Thanks for any help!

Cheers,
STEFAN


OpenBSD 5.6-current (GENERIC.MP) #509: Sat Nov  1 00:18:49 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3203203072 (3054MB)
avail mem = 3109294080 (2965MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version "79ETC9WW (2.09 )" date 12/22/2006
bios0: LENOVO 2007VG2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4)
EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3)
HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.61 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.34 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "92P1139" serial  2887 type LION oem
"Panasonic"
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1300 M52-64"
rev 0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog
Devices AD1981HD
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address
00:15:58:81:15:fb
ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci3 at ppb2 bus 3
wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
msi, MoW2, address 00:19:d2:85:6f:4d
ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: msi
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: msi
pci5 at ppb4 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb5 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci6 at ppb5 bus 21
cbb0 at pci6 dev 0 function 0 "TI PCI1510 CardBus" rev 0x00: apic 1 int 16
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, latt

Re: Some radeon / drm error?

A case of TL:DR???

Am 10/20/14 um 15:39 schrieb Stefan Wollny:
> HI there!
> 
> As my system (amd64-current) still looses sometimes the routes (?) I am
> checking the logs to investigate before asking for help. Doing so I run
> tail -f /var/log/messages in a xterm.
> I just noticed the following error:
> 
> ~~~
> Oct 20 13:31:13 idefix /bsd: error: [drm:pid4037:radeon_cs_ioctl]
> *ERROR* Failed to parse relocation -12!
> Oct 20 13:32:08 idefix last message repeated 2 times
> ~~~
> (This is also at the end of the dmesg, see below. I have also attached
> the output of 'sysctl -a' and Xorg.0.log)
> 
> What does this mean? Anything that I should be aware of? Any other info
> needed to investigate further?
> 
> BTW: I didn't notice any shortcommings while working at the system.
> I'd appreciate if s.o. could give me a hint about this. TIA.
> 
> Cheers,
> STEFAN
> 
> 
> 
> OpenBSD 5.6-current (GENERIC.MP) #451: Sun Oct 19 22:33:08 MDT 2014
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 3203203072 (3054MB)
> avail mem = 3109289984 (2965MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
> bios0: vendor LENOVO version "79ETC9WW (2.09 )" date 12/22/2006
> bios0: LENOVO 2007VG2
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
> SSDT SSDT SSDT
> acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4)
> EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3)
> HDEF(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.61 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
> cpu0: 4MB 64b/line 16-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 166MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.33 MHz
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
> cpu1: 4MB 64b/line 16-way L2 cache
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 2, remapped to apid 1
> acpimcfg0 at acpi0 addr 0xf000, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (EXP0)
> acpiprt3 at acpi0: bus 3 (EXP1)
> acpiprt4 at acpi0: bus 4 (EXP2)
> acpiprt5 at acpi0: bus 12 (EXP3)
> acpiprt6 at acpi0: bus 21 (PCI1)
> acpicpu0 at acpi0: C3, C2, C1, PSS
> acpicpu1 at acpi0: C3, C2, C1, PSS
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
> acpitz0 at acpi0: critical temperature is 127 degC
> acpitz1 at acpi0: critical temperature is 99 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> acpibat0 at acpi0: BAT0 model "92P1139" serial  2887 type LION oem
> "Panasonic"
> acpibat1 at acpi0: BAT1 not present
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock0 at acpi0: GDCK not docked (0)
> cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: msi
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1300 M52-64"
> rev 0x00
> drm0 at radeondrm0
> radeondrm0: apic 1 int 16
> azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
> azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog
> Devices AD1981HD
> audio0 at azalia0
> ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
> pci2 at ppb1 bus 2
> em0 at pci2 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address
> 00:15:58:81:15:fb
> ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
> pci3 at ppb2 bus 3
> wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
> msi, MoW2, address 00:19:d2:85:6f:4d
> ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: msi
> pci4 at ppb3 bus 4
> ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: msi
> pci5 at ppb4 bus 12
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
> uhci3 at pci0 dev 29 function 3 "Intel 8280

5.4 instead of 5.5 in faq1.html

2014-11-01 Thread Eduardo Lopes

In http://www.openbsd.org/faq/faq1.html#WhatsNew:

"The complete list of changes made to OpenBSD 5.4 to create OpenBSD 5.6 
can[...]"

I think that 5.4 was left behind, wasn't it?

Re: OpenBSD 5.6 Released

2014-11-01 Thread Alessandro Gallo

Thank you so much for everything.
Il 01/Nov/2014 18:26 "Antoine Jacoutot"  ha scritto:

>
> November 1, 2014.
>
> We are pleased to announce the official release of OpenBSD 5.6.
> This is our 36th release on CD-ROM (and 37th via FTP/HTTP).  We remain
> proud of OpenBSD's record of more than ten years with only two remote
> holes in the default install.
>
> As in our previous releases, 5.6 provides significant improvements,
> including new features, in nearly all areas of the system:
>
>  - LibreSSL:
> o This release forks OpenSSL into LibreSSL, a version of the
>   TLS/crypto stack with goals of modernizing the codebase, improving
>   security, and applying best practice development processes.
> o No support for legacy MacOS, Netware, OS/2, VMS and Windows
>   platforms, as well as antique compilers.
> o Removal of the IBM 4758, Broadcom ubsec, Sureware, Nuron, GOST,
>   GMP, CSwift, CHIL, CAPI, Atalla and AEP engines, either because
>   the hardware is irrelevant, or because they require external
>   non-free libraries to work.
> o No support for FIPS-140 compliance.
> o No EBCDIC support.
> o No support for big-endian i386 and amd64 platforms.
> o Use standard routines from the C library (malloc, strdup,
>   snprintf...) instead of rolling our own, sometimes badly.
> o Remove the old OpenSSL PRNG, and rely upon arc4random_buf from
>   libc for all the entropy needs.
> o Remove the MD2 and SEED algorithms.
> o Remove J-PAKE, PSK and SRP (mis)features.
> o Aggressive cleaning of BN memory when no longer used.
> o No support for Kerberos.
> o No support for SSLv2.
> o No support for the questionable DTLS heartbeat extension.
> o No support for TLS compression.
> o No support for US-Export SSL ciphers.
> o Do not use the current time as a random seed in libssl.
> o Support for ChaCha and Poly1305 algorithm.
> o Support for Brainpool and ANSSI elliptic curves.
> o Support for AES-GCM and ChaCha20-Poly1305 AEAD modes.
>
>  - Improved hardware support, including:
> o SCSI Multipathing support via mpath(4) and associated path drivers
>   on several architectures.
> o New qlw(4) driver for QLogic ISP SCSI HBAs.
> o New qla(4) driver for QLogic ISP2100/2200/2300 Fibre Channel HBAs.
> o New upd(4) sensor driver for USB Power Devices (UPS).
> o New brswphy(4) driver for Broadcom BCM53xx 10/100/1000TX Ethernet
>   PHYs.
> o New uscom(4) driver for simple USB serial adapters.
> o New axen(4) driver for ASIX Electronics AX88179 10/100/Gigabit USB
>   Ethernet devices.
> o The inteldrm(4) and radeondrm(4) drivers have improved
>   suspend/resume support.
> o The userland interface for the agp(4) driver has been removed.
> o The rtsx(4) driver now supports card readers based on the RTS5227
>   and RTL8402 chipsets.
> o The firmware for the run(4) driver has been updated to version 0.33.
> o The run(4) driver now supports devices based on the RT3900E
>   chipset.
> o The zyd(4) driver, which was broken for some time, has been fixed.
> o The bwi(4) driver now works in systems with more than 1GB of RAM.
> o The re(4) driver now supports devices based on the RTL8168EP/8111EP,
>   RTL8168G/8111G, and RTL8168GU/8111GU chipsets.
>
>  - Generic network stack improvements:
> o divert(4) now supports checksum offload.
> o IPv6 is now turned off on new interfaces by default. Assigning an
>   IPv6 address will enable IPv6 on an interface.
> o Support for RFC4620 IPv6 Node Information Queries has been removed.
> o The kernel no longer supports the SO_DONTROUTE socket option.
> o The getaddrinfo(3) function now supports the AI_ADDRCONFIG flag
>   defined in RFC 3493.
> o Include router alert option (RAO) in IGMP packets, as required by
>   RFC2236.
> o ALTQ has been removed.
> o The hash table for Protocol Control Block (PCB) of TCP and UDP now
>   resize automatically on load.
>
>  - Installer improvements:
> o Remove ftp and tape as install methods.
> o Preserve the disklabel (and next 6 blocks) when installing boot
>   block on 4k-sector disk drives.
> o Change the "Server?" question to "HTTP Server?" to allow unambiguous
>   autoinstall(8) handling.
> o Allow autoinstall(8) to fetch and install sets from multiple
>   locations.
> o Many sample configuration files have moved from /etc to
>   /etc/examples.
>
>  - Routing daemons and other userland network improvements:
> o When used with the -v flag, tcpdump(8) now shows the actual bad
>   checksum within the IP/protocol header itself and what the good
>   checksum should be.
> o ftp(1) now allows its User-Agent to be changed via the -U
>   command-line option.
> o The -r option of ping(8) and traceroute(8) has been removed.
> o ifconfig(8) can now explicitly assign an IPv6 l

Re: OpenBSD 5.6 Released

2014-11-01 Thread Peter N. M. Hansteen

Antoine Jacoutot  writes:

> November 1, 2014.
> 
> We are pleased to announce the official release of OpenBSD 5.6.
> This is our 36th release on CD-ROM (and 37th via FTP/HTTP).  We remain
> proud of OpenBSD's record of more than ten years with only two remote
> holes in the default install.

Congratulations on yet another excellent release!

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Mirror openbsd.cs.toronto.edu is currently broke

2014-11-01 Thread Clint Sand

On Sat, Nov 01, 2014 at 02:24:11PM -0400, Nick Holland wrote:
> On 11/01/14 13:53, Clint Sand wrote:
> > On Sat, Nov 01, 2014 at 04:00:04PM +0100, Jan Stary wrote:
> >> On Nov 01 09:07:15, n...@holland-consulting.net wrote:
> >> > For the curious, and perhaps as an educational lesson, what happened:
> >> > Late last night (error one: scripting when tired) I was editing the
> >> > scripts that download from the upstream mirror to include updates to the
> >> > new release.  Totally routine.
> >> 
> >> Just out of curiosity (I am not even affected):
> >> is there such a script somewhere in the tree,
> >> or do mirror maintainers write their own?
> > 
> > Jan, details here: http://www.openbsd.org/anoncvs.shar
> 
> Um. no. nothing to do with it.
> this script is for CVS, which I explicitly said was NOT impacted.  It is
> also only ONE part of what it takes to run even a CVS mirror.
> 

Got it. Thanks Nick. I totally missread. I had just looked at the anoncvs docs 
the other day and it was on my mind.

Re: Mirror openbsd.cs.toronto.edu is currently broke

2014-11-01 Thread Nick Holland

On 11/01/14 13:53, Clint Sand wrote:
> On Sat, Nov 01, 2014 at 04:00:04PM +0100, Jan Stary wrote:
>> On Nov 01 09:07:15, n...@holland-consulting.net wrote:
>> > For the curious, and perhaps as an educational lesson, what happened:
>> > Late last night (error one: scripting when tired) I was editing the
>> > scripts that download from the upstream mirror to include updates to the
>> > new release.  Totally routine.
>> 
>> Just out of curiosity (I am not even affected):
>> is there such a script somewhere in the tree,
>> or do mirror maintainers write their own?
> 
> Jan, details here: http://www.openbsd.org/anoncvs.shar

Um. no. nothing to do with it.
this script is for CVS, which I explicitly said was NOT impacted.  It is
also only ONE part of what it takes to run even a CVS mirror.

To answer the OP, mirror systems are all a little different, hardware
running over a range of capabilities, so there's no one set or even
template of scripts mirror maintainers use.

Sitting down and writing up a set of notes for mirror maintainers is on
my list of things to do.

Nick.
--
It's impossible for words to describe what is necessary to those who do
not know what Heartbleed means.

Re: Mirror openbsd.cs.toronto.edu is currently broke

2014-11-01 Thread Clint Sand

On Sat, Nov 01, 2014 at 04:00:04PM +0100, Jan Stary wrote:
> On Nov 01 09:07:15, n...@holland-consulting.net wrote:
> > For the curious, and perhaps as an educational lesson, what happened:
> > Late last night (error one: scripting when tired) I was editing the
> > scripts that download from the upstream mirror to include updates to the
> > new release.  Totally routine.
> 
> Just out of curiosity (I am not even affected):
> is there such a script somewhere in the tree,
> or do mirror maintainers write their own?

Jan, details here: http://www.openbsd.org/anoncvs.shar

# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#  Makefile
#  README
#  anoncvssh.c

less README

So, you want to run an anoncvs server.

A summary of the steps you'll need to do is:

and so on...

Re: OpenBSD 5.6 Released

2014-11-01 Thread Mxher

Le 01/11/2014 18:22, Antoine Jacoutot a écrit :
> Ports tree and package building by Jasper Lievisse Adriaanse,
> Pierre-Emmanuel Andre, Landry Breuil, Stuart Henderson, Peter Hessler,
> Nick Holland, Paul Irofti, Sebastian Reitenbach, Miod Vallat, and
> Christian Weisgerber.  System builds by Jasper Lievisse Adriaanse,
> Kenji Aoyama, Theo de Raadt, Nick Holland, and Miod Vallat.
> X11 builds by Jasper Lievisse Adriaanse, Kenji Aoyama, Todd Fries,
> Nick Holland, and Miod Vallat.  ISO-9660 filesystem layout by
> Theo de Raadt.
> 
> We would like to thank all of the people who sent in bug reports, bug
> fixes, donation cheques, and hardware that we use.  We would also like
> to thank those who pre-ordered the 5.6 CD-ROM or bought our previous
> CD-ROMs.  Those who did not support us financially have still helped
> us with our goal of improving the quality of the software.
> 
> Our developers are:
> 
> Aaron Bieber, Alexander Bluhm, Alexander Hall, Alexandr Shadchin,
> Alexandre Ratchov, Andrew Fresh, Anil Madhavapeddy,
> Anthony J. Bentley, Antoine Jacoutot, Austin Hook, Benoit Lecocq,
> Bob Beck, Brad Smith, Brandon Mercer, Brent Cook, Bret Lambert,
> Brett Mahar, Brian Callahan, Camiel Dobbelaar, Charles Longeau,
> Chris Cappuccio, Christian Weisgerber, Christopher Zimmermann,
> Claudio Jeker, Damien Miller, Daniel Dickman, Darren Tucker,
> David Coppa, David Gwynne, Doug Hogan, Edd Barrett, Eric Faurot,
> Federico G. Schwindt, Florian Obser, Gerhard Roth, Gilles Chehade,
> Giovanni Bechis, Gleydson Soares, Gonzalo L. Rodriguez,
> Henning Brauer, Ian Darwin, Igor Sobrado, Ingo Schwarze,
> Jakob Schlyter, James Turner, Jason McIntyre,
> Jasper Lievisse Adriaanse, Jeremie Courreges-Anglas, Jeremy Evans,
> Jim Razmus II, Joel Sing, Joerg Jung, Jonathan Armani,
> Jonathan Gray, Jonathan Matthew, Jordan Hargrave, Joshua Elsasser,
> Joshua Stein, Juan Francisco Cantero Hurtado, Kazuya Goda,
> Kenji Aoyama, Kenneth R Westerback, Kirill Bychkov, Kurt Miller,
> Landry Breuil, Lawrence Teo, Loganaden Velvindron, Luke Tymowski,
> Marc Espie, Marco Pfatschbacher, Mark Kettenis, Mark Lumsden,
> Markus Friedl, Martin Pelikan, Martin Pieuchot, Martin Reindl,
> Martynas Venckus, Masao Uebayashi, Mats O Jansson, Matthew Dempsky,
> Matthias Kilian, Matthieu Herrb, Mike Belopuhov, Mike Larkin,
> Miod Vallat, Naoya Kaneko, Nayden Markatchev, Nicholas Marriott,
> Nick Holland, Nigel Taylor, Okan Demirmen, Otto Moerbeek,
> Pascal Stumpf, Paul de Weerd, Paul Irofti, Peter Hessler,
> Philip Guenther, Pierre-Emmanuel Andre, Raphael Graf, Remi Pointel,
> Renato Westphal, Reyk Floeter, Robert Nagy, Robert Peichaer,
> Ryan Thomas McBride, Sasano Takayoshi, Sebastian Benoit,
> Sebastian Reitenbach, Simon Perreault, Stefan Fritsch,
> Stefan Sperling, Stephan Rickauer, Steven Mestdagh, Stuart Cassoff,
> Stuart Henderson, Sylvestre Gallon, Ted Unangst, Theo de Raadt,
> Tobias Stoeckmann, Tobias Ulmer, Todd C. Miller, Todd Fries,
> Vadim Zhukov, William Yodlowsky, Wouter Wijngaards,
> Yasuoka Masahiko, Yojiro Uo
> 


That sounds amazing!

Thanks to everyone !

OpenBSD 5.6 Released

2014-11-01 Thread Antoine Jacoutot

November 1, 2014.

We are pleased to announce the official release of OpenBSD 5.6.
This is our 36th release on CD-ROM (and 37th via FTP/HTTP).  We remain
proud of OpenBSD's record of more than ten years with only two remote
holes in the default install.

As in our previous releases, 5.6 provides significant improvements,
including new features, in nearly all areas of the system:

 - LibreSSL:
o This release forks OpenSSL into LibreSSL, a version of the
  TLS/crypto stack with goals of modernizing the codebase, improving
  security, and applying best practice development processes.
o No support for legacy MacOS, Netware, OS/2, VMS and Windows
  platforms, as well as antique compilers.
o Removal of the IBM 4758, Broadcom ubsec, Sureware, Nuron, GOST,
  GMP, CSwift, CHIL, CAPI, Atalla and AEP engines, either because
  the hardware is irrelevant, or because they require external
  non-free libraries to work.
o No support for FIPS-140 compliance.
o No EBCDIC support.
o No support for big-endian i386 and amd64 platforms.
o Use standard routines from the C library (malloc, strdup,
  snprintf...) instead of rolling our own, sometimes badly.
o Remove the old OpenSSL PRNG, and rely upon arc4random_buf from
  libc for all the entropy needs.
o Remove the MD2 and SEED algorithms.
o Remove J-PAKE, PSK and SRP (mis)features.
o Aggressive cleaning of BN memory when no longer used.
o No support for Kerberos.
o No support for SSLv2.
o No support for the questionable DTLS heartbeat extension.
o No support for TLS compression.
o No support for US-Export SSL ciphers.
o Do not use the current time as a random seed in libssl.
o Support for ChaCha and Poly1305 algorithm.
o Support for Brainpool and ANSSI elliptic curves.
o Support for AES-GCM and ChaCha20-Poly1305 AEAD modes.

 - Improved hardware support, including:
o SCSI Multipathing support via mpath(4) and associated path drivers
  on several architectures.
o New qlw(4) driver for QLogic ISP SCSI HBAs.
o New qla(4) driver for QLogic ISP2100/2200/2300 Fibre Channel HBAs.
o New upd(4) sensor driver for USB Power Devices (UPS).
o New brswphy(4) driver for Broadcom BCM53xx 10/100/1000TX Ethernet
  PHYs.
o New uscom(4) driver for simple USB serial adapters.
o New axen(4) driver for ASIX Electronics AX88179 10/100/Gigabit USB
  Ethernet devices.
o The inteldrm(4) and radeondrm(4) drivers have improved
  suspend/resume support.
o The userland interface for the agp(4) driver has been removed.
o The rtsx(4) driver now supports card readers based on the RTS5227
  and RTL8402 chipsets.
o The firmware for the run(4) driver has been updated to version 0.33.
o The run(4) driver now supports devices based on the RT3900E
  chipset.
o The zyd(4) driver, which was broken for some time, has been fixed.
o The bwi(4) driver now works in systems with more than 1GB of RAM.
o The re(4) driver now supports devices based on the RTL8168EP/8111EP,
  RTL8168G/8111G, and RTL8168GU/8111GU chipsets.

 - Generic network stack improvements:
o divert(4) now supports checksum offload.
o IPv6 is now turned off on new interfaces by default. Assigning an
  IPv6 address will enable IPv6 on an interface.
o Support for RFC4620 IPv6 Node Information Queries has been removed.
o The kernel no longer supports the SO_DONTROUTE socket option.
o The getaddrinfo(3) function now supports the AI_ADDRCONFIG flag
  defined in RFC 3493.
o Include router alert option (RAO) in IGMP packets, as required by
  RFC2236.
o ALTQ has been removed.
o The hash table for Protocol Control Block (PCB) of TCP and UDP now
  resize automatically on load.

 - Installer improvements:
o Remove ftp and tape as install methods.
o Preserve the disklabel (and next 6 blocks) when installing boot
  block on 4k-sector disk drives.
o Change the "Server?" question to "HTTP Server?" to allow unambiguous
  autoinstall(8) handling.
o Allow autoinstall(8) to fetch and install sets from multiple
  locations.
o Many sample configuration files have moved from /etc to
  /etc/examples.

 - Routing daemons and other userland network improvements:
o When used with the -v flag, tcpdump(8) now shows the actual bad
  checksum within the IP/protocol header itself and what the good
  checksum should be.
o ftp(1) now allows its User-Agent to be changed via the -U
  command-line option.
o The -r option of ping(8) and traceroute(8) has been removed.
o ifconfig(8) can now explicitly assign an IPv6 link-local address
  and turn IPv6 autoconf on or off.
o ifconfig(8) has been made smarter about parsing WEP keys on the
  command line.
o ifconfig(8) scan now shows the encryption type of wireless networks
  (WEP, WPA, WPA2, 802.1x).
o MS-CHAPv1 (RFC243

Re: Large number of netlivelocks

2014-11-01 Thread Stuart Henderson

On 2014/11/01 15:31, Federico Giannici wrote:
> >
> >This is expected if you increase HZ without changing how livelock
> >detection works. It sets a timer every clock tick, when that timer has
> >triggered it checks how many ticks elapsed, if >1 livelock is detected.
> >This triggers livelock avoidance which will slow down your network
> >traffic so yes you do want to pay attention to them. sys/net/if.c
> 
> Thank you for your reply.
> Unfortunately I haven't enough expertise in kernel programming to really
> understand where is the problem.
> However, are you saying that the kernel doesn't correctly handle the case
> where HZ != 100?
> So, is this a kernel bug?

In my opinion, no - if somebody modifies the kernel (including by changing
the config), it's up to them to work out the implications of that change
and make other adjustments that may be necessary. Expertise isn't needed
but testing and experimentation is.

> >Also note, if you're graphing by calling sysctl(8) that may be locking
> >the kernel for long enough to trigger livelock detection!
> 
> I read the sysctl value only once per five minutes, so this is not a
> problem.

That's OK then (just wanted to mention it as I noticed it on my
home adsl router where I've been experimenting with HZ changes).

Re: Mirror openbsd.cs.toronto.edu is currently broke

2014-11-01 Thread Jan Stary

On Nov 01 09:07:15, n...@holland-consulting.net wrote:
> For the curious, and perhaps as an educational lesson, what happened:
> Late last night (error one: scripting when tired) I was editing the
> scripts that download from the upstream mirror to include updates to the
> new release.  Totally routine.

Just out of curiosity (I am not even affected):
is there such a script somewhere in the tree,
or do mirror maintainers write their own?

wanted: good 1U machine in Toronto