Re: bridge(4) question new network setup

[patrick keshishian]

On 1/21/23, David Gwynne  wrote:
> On Sat, Jan 21, 2023 at 01:46:34PM -0800, patrick keshishian wrote:
>> On 1/20/23, David Gwynne  wrote:
>> > On Fri, Jan 20, 2023 at 11:09:47AM -0800, patrick keshishian wrote:
>> >> Hello,
>> >>
>> >> I am trying get a new ISP setup working.  The Router is
>> >> causing some pain.  There is a /28 public block assigned.
>> >> The DSL router can't be configured in transparent bridge
>> >> mode (they say).  It holds on to one of the /28 addresses.
>> >
>> > i'm sure they say that, but that doesn't mean it's impossible. this
>> > will be a lot easier and more useful if you can get a dsl modem
>> > into bridge/transparent mode and do all the routing on your own
>> > box.
>>
>> OK. So the situation was a bit worse than I had actually
>> anticipated.  After I got the described setup configured
>> I noticed that the DSL Router/Modem wouldn't send out
>> any traffic unless it had an arp entry for the source.
>> e.g., nat-to an unassigned IP from the /28 wouldn't go out.
>>
>> Again, in my limited networking knowledge, it meant I had
>> to do proxy arp entries for /28 public IPs in the $dmz.
>> This was quite frustrating.
>>
>> So I started poking around in the DSL Router/modem settings
>> (cuing off your "doesn't mean it's impossible") and I
>> have it now acting as a transparent bridge!
>>
>> I spent most of Tues on the phone with their techs, and I
>> was assured that is not possible/unsupported.  Now maybe
>> they actually meant "unsupported" mode as far as their
>> support is concerned.
>>
>> But things seem to running as expect (so far)!  So thanks
>> for the bit of "encouragement"!
>
> Does that mean you have the WAN IP on your router now? And you can do
> whatever you want with the /28?

Yep!  And it made things so much easier to set up.

>> > that would also give you the option to do fun stuff like NOT putting
>> > the /28 onto an ethernet network so you could you use all 16 of the
>> > IPs on dmz hosts instead of losing some to network/broadcast/gateway.
>>
>> I am curious how you would go about doing what you suggest:
>> Using all 16 of /28.
>
> The simple (and currently best supported) way is to set up a tunnel
> interface for every IP in the /28 and connect the tunnel to the server
> providing the service. The router would have a config like this:
>
> ifconfig gif0 create
> ifconfig gif0 tunnel $router_lan_ip $server_lan_ip
> ifconfig gif0 inet $router_gif_ip $server_slash28_ip

A bit above my pay-grade.  I'll need to study this later on.

Thanks again for the hints/help!
--patrick


>>
>> Thanks for your reply,
>> --patrick
>>
>>
>> >> The setup looks something like this:
>> >> (and hopefully the ascii "art" remains intact from gmail)
>> >>
>> >>( internet )
>> >> |
>> >> | [WAN IP]
>> >>   +-o--+
>> >>  / DSL ROUTER / <-- Transparent bridge mode NOT possible
>> >> +-o--+
>> >>   | [ one of /28 Public IPs = $dslgw_ip ]
>> >>   |
>> >>   |
>> >>   | $ext
>> >> +-o--+
>> >> ||
>> >> | OpenBSD/pf o--- ( rest of /28 Public IP network )
>> >> || $dmz  (DMZ: httpd, smtpd, ...)
>> >> +-o--+
>> >>  $lan | [10.x.x.1]
>> >>   |
>> >> ( 10.x.x.x network )
>> >>
>> >>
>> >> As far as networking goes, I need to be spoken to as if I'm
>> >> a fledgling.
>> >>
>> >> I want to do the obvious: use OpenBSD/pf(4) to:
>> >>  - Filter traffic from $ext to $dmz
>> >>  - Filter traffic from $dmz outbound
>> >>  - Filter traffic from $lan (10.x.x.x) to $dmz
>> >>  - NAT traffic from $lan (10.x.x.x) outbound to internet
>> >>
>> >>
>> >> I'm bridge(4)-ing $ext and $dmz.  Which means I must give
>> >> one of the /28 public IP addresses to either $ext or $dmz
>> >> to be able to do:
>> >>
>> >> # route add default $dslgw_ip
>> >>
>> >> (!?)
>> >>
>> >> Am I missing something?
>> >> Is there a better way to configure things?
>> >>
>> >> Thanks,
>> >> --patrick
>> >>
>> >
>

Re: bridge(4) question new network setup

[patrick keshishian]

On 1/21/23, David Gwynne  wrote:
> On Sat, Jan 21, 2023 at 01:32:18PM -0800, patrick keshishian wrote:
>> On 1/20/23, Hrvoje Popovski  wrote:
>> > On 20.1.2023. 20:09, patrick keshishian wrote:
>> >> Hello,
>> >>
>> >> I am trying get a new ISP setup working.  The Router is
>> >> causing some pain.  There is a /28 public block assigned.
>> >> The DSL router can't be configured in transparent bridge
>> >> mode (they say).  It holds on to one of the /28 addresses.
>> >>
>> >> The setup looks something like this:
>> >> (and hopefully the ascii "art" remains intact from gmail)
>> >>
>> >>( internet )
>> >> |
>> >> | [WAN IP]
>> >>   +-o--+
>> >>  / DSL ROUTER / <-- Transparent bridge mode NOT possible
>> >> +-o--+
>> >>   | [ one of /28 Public IPs = $dslgw_ip ]
>> >>   |
>> >>   |
>> >>   | $ext
>> >> +-o--+
>> >> ||
>> >> | OpenBSD/pf o--- ( rest of /28 Public IP network )
>> >> || $dmz  (DMZ: httpd, smtpd, ...)
>> >> +-o--+
>> >>  $lan | [10.x.x.1]
>> >>   |
>> >> ( 10.x.x.x network )
>> >>
>> >>
>> >> As far as networking goes, I need to be spoken to as if I'm
>> >> a fledgling.
>> >>
>> >> I want to do the obvious: use OpenBSD/pf(4) to:
>> >>  - Filter traffic from $ext to $dmz
>> >>  - Filter traffic from $dmz outbound
>> >>  - Filter traffic from $lan (10.x.x.x) to $dmz
>> >>  - NAT traffic from $lan (10.x.x.x) outbound to internet
>> >>
>> >>
>> >> I'm bridge(4)-ing $ext and $dmz.  Which means I must give
>> >> one of the /28 public IP addresses to either $ext or $dmz
>> >> to be able to do:
>> >>
>> >> # route add default $dslgw_ip
>> >>
>> >> (!?)
>> >>
>> >> Am I missing something?
>> >> Is there a better way to configure things?
>> >>
>> >> Thanks,
>> >> --patrick
>> >>
>> >
>> > Hi,
>> >
>> > If your ext interface is in same subnet as that /28 from your ISP then
>> > you could:
>> >
>> > - use veb(4) to bridge ext, dmz and vport(4) interface and add default
>> > route to dslgw_ip. vport is ip interface for veb
>>
>> I started out looking at veb(4) but I wasn't confident
>> how I could filter traffic in/out of $dmz.  Also, the
>> description of vport(4) which states "packets traversing
>> vport interfaces appear to travel in the opposite direction
>> to packets travelling over other ports" confused me even
>> more.  So I started using bridge(4).
>
> When you add a port to veb(4), it takes it over completely and by
> default it only uses it to switch traffic at layer 2 (Ethernet).
> In other words, by default veb(4) does not run pf against packets
> on ports.
>
> vport is an exception because it operates as if it is a normal
> ethernet interface plugged into a switchport, it's just that the
> switch in this situation is veb, and the other ports on that switch
> are the non-vport interfaces you added to the veb.

Thanks for taking the time to explain in these two paragraphs.
I definitely have a better sense of veb/vport now.

> So, by default veb lets you build a switch out of other interfaces
> in the system, and vport lets you plug the kernel network stack
> into that virtual switch. Because packets from a normal switch coming
> into a normal physical interface go in to the network stack, that is
> also how it behaves with vport. ie, you write rules in pf like this for
> packets coming from a veb into a vport:
>
>   pass in on vport0 inet tcp from any to port ssh

Nice.

> If you do enable IP filtering on veb (ie, you ifconfig veb0 link1 as per
> the ifconfig manpage), then packets coming from the "wire" into the
> interface are filtered by pf too. This means that if a packet is coming
> from the wire and is destined to your network stack via a vport
> interface, it will be going through pf twice: once when it comes into
> the physical interface and again when it goes over vport.
>
> pf is not designed for a packet to be processed twice. TCP packets in
> particular going through pf twice will confuse the window tracking. If
> you're doing NAT or something like that, it can also get confused.
>
> So if you're going 

Re: bridge(4) question new network setup

[patrick keshishian]

On 1/20/23, David Gwynne  wrote:
> On Fri, Jan 20, 2023 at 11:09:47AM -0800, patrick keshishian wrote:
>> Hello,
>>
>> I am trying get a new ISP setup working.  The Router is
>> causing some pain.  There is a /28 public block assigned.
>> The DSL router can't be configured in transparent bridge
>> mode (they say).  It holds on to one of the /28 addresses.
>
> i'm sure they say that, but that doesn't mean it's impossible. this
> will be a lot easier and more useful if you can get a dsl modem
> into bridge/transparent mode and do all the routing on your own
> box.

OK. So the situation was a bit worse than I had actually
anticipated.  After I got the described setup configured
I noticed that the DSL Router/Modem wouldn't send out
any traffic unless it had an arp entry for the source.
e.g., nat-to an unassigned IP from the /28 wouldn't go out.

Again, in my limited networking knowledge, it meant I had
to do proxy arp entries for /28 public IPs in the $dmz.
This was quite frustrating.

So I started poking around in the DSL Router/modem settings
(cuing off your "doesn't mean it's impossible") and I
have it now acting as a transparent bridge!

I spent most of Tues on the phone with their techs, and I
was assured that is not possible/unsupported.  Now maybe
they actually meant "unsupported" mode as far as their
support is concerned.

But things seem to running as expect (so far)!  So thanks
for the bit of "encouragement"!

> that would also give you the option to do fun stuff like NOT putting
> the /28 onto an ethernet network so you could you use all 16 of the
> IPs on dmz hosts instead of losing some to network/broadcast/gateway.

I am curious how you would go about doing what you suggest:
Using all 16 of /28.

Thanks for your reply,
--patrick


>> The setup looks something like this:
>> (and hopefully the ascii "art" remains intact from gmail)
>>
>>( internet )
>> |
>> | [WAN IP]
>>   +-o--+
>>  / DSL ROUTER / <-- Transparent bridge mode NOT possible
>> +-o--+
>>   | [ one of /28 Public IPs = $dslgw_ip ]
>>   |
>>   |
>>   | $ext
>> +-o--+
>> ||
>> | OpenBSD/pf o--- ( rest of /28 Public IP network )
>> || $dmz  (DMZ: httpd, smtpd, ...)
>> +-o--+
>>  $lan | [10.x.x.1]
>>   |
>> ( 10.x.x.x network )
>>
>>
>> As far as networking goes, I need to be spoken to as if I'm
>> a fledgling.
>>
>> I want to do the obvious: use OpenBSD/pf(4) to:
>>  - Filter traffic from $ext to $dmz
>>  - Filter traffic from $dmz outbound
>>  - Filter traffic from $lan (10.x.x.x) to $dmz
>>  - NAT traffic from $lan (10.x.x.x) outbound to internet
>>
>>
>> I'm bridge(4)-ing $ext and $dmz.  Which means I must give
>> one of the /28 public IP addresses to either $ext or $dmz
>> to be able to do:
>>
>> # route add default $dslgw_ip
>>
>> (!?)
>>
>> Am I missing something?
>> Is there a better way to configure things?
>>
>> Thanks,
>> --patrick
>>
>

Re: bridge(4) question new network setup

[patrick keshishian]

On 1/20/23, Hrvoje Popovski  wrote:
> On 20.1.2023. 20:09, patrick keshishian wrote:
>> Hello,
>>
>> I am trying get a new ISP setup working.  The Router is
>> causing some pain.  There is a /28 public block assigned.
>> The DSL router can't be configured in transparent bridge
>> mode (they say).  It holds on to one of the /28 addresses.
>>
>> The setup looks something like this:
>> (and hopefully the ascii "art" remains intact from gmail)
>>
>>( internet )
>> |
>> | [WAN IP]
>>   +-o--+
>>  / DSL ROUTER / <-- Transparent bridge mode NOT possible
>> +-o--+
>>   | [ one of /28 Public IPs = $dslgw_ip ]
>>   |
>>   |
>>   | $ext
>> +-o--+
>> ||
>> | OpenBSD/pf o--- ( rest of /28 Public IP network )
>> || $dmz  (DMZ: httpd, smtpd, ...)
>> +-o--+
>>  $lan | [10.x.x.1]
>>   |
>> ( 10.x.x.x network )
>>
>>
>> As far as networking goes, I need to be spoken to as if I'm
>> a fledgling.
>>
>> I want to do the obvious: use OpenBSD/pf(4) to:
>>  - Filter traffic from $ext to $dmz
>>  - Filter traffic from $dmz outbound
>>  - Filter traffic from $lan (10.x.x.x) to $dmz
>>  - NAT traffic from $lan (10.x.x.x) outbound to internet
>>
>>
>> I'm bridge(4)-ing $ext and $dmz.  Which means I must give
>> one of the /28 public IP addresses to either $ext or $dmz
>> to be able to do:
>>
>> # route add default $dslgw_ip
>>
>> (!?)
>>
>> Am I missing something?
>> Is there a better way to configure things?
>>
>> Thanks,
>> --patrick
>>
>
> Hi,
>
> If your ext interface is in same subnet as that /28 from your ISP then
> you could:
>
> - use veb(4) to bridge ext, dmz and vport(4) interface and add default
> route to dslgw_ip. vport is ip interface for veb

I started out looking at veb(4) but I wasn't confident
how I could filter traffic in/out of $dmz.  Also, the
description of vport(4) which states "packets traversing
vport interfaces appear to travel in the opposite direction
to packets travelling over other ports" confused me even
more.  So I started using bridge(4).

> - or on ext interface put ip alias with ip addresses from /28 public
> range and than do binat-to or nat-to in pf to hosts in dmz
>
> or maybe i totally misunderstood you  :)

I think you understood me fine. I'm just not too familiar
with how networking actually works.

Thanks,
--patrick

bridge(4) question new network setup

[patrick keshishian]

Hello,

I am trying get a new ISP setup working.  The Router is
causing some pain.  There is a /28 public block assigned.
The DSL router can't be configured in transparent bridge
mode (they say).  It holds on to one of the /28 addresses.

The setup looks something like this:
(and hopefully the ascii "art" remains intact from gmail)

   ( internet )
|
| [WAN IP]
  +-o--+
 / DSL ROUTER / <-- Transparent bridge mode NOT possible
+-o--+
  | [ one of /28 Public IPs = $dslgw_ip ]
  |
  |
  | $ext
+-o--+
||
| OpenBSD/pf o--- ( rest of /28 Public IP network )
|| $dmz  (DMZ: httpd, smtpd, ...)
+-o--+
 $lan | [10.x.x.1]
  |
( 10.x.x.x network )


As far as networking goes, I need to be spoken to as if I'm
a fledgling.

I want to do the obvious: use OpenBSD/pf(4) to:
 - Filter traffic from $ext to $dmz
 - Filter traffic from $dmz outbound
 - Filter traffic from $lan (10.x.x.x) to $dmz
 - NAT traffic from $lan (10.x.x.x) outbound to internet


I'm bridge(4)-ing $ext and $dmz.  Which means I must give
one of the /28 public IP addresses to either $ext or $dmz
to be able to do:

# route add default $dslgw_ip

(!?)

Am I missing something?
Is there a better way to configure things?

Thanks,
--patrick

Re: Bluetooth support status

[patrick keshishian]

On Wed, Aug 7, 2019 at 10:40 AM Theo de Raadt  wrote:

> Wow, look -- more useless chatter on the topic.
>
> The bt stack we had was designed as "network code", and all sorts of
> complex layer violations and device hand-offs were very complicated and
> troublesome.
>
> The code was not deleted because bluetooth is shit.  The code was
> deleted *because it was shitty and unsuited to the purpose*
>
> And then noone stepped up to write new code.  THAT IS THE WHOLE STORY.
>
> People on misc often want some complicated conspiracy, and fails to
> understand it is ALWAYS that "someone has to write the code and maintain
> it", and if such a person doesn't exist then either (a) the code doesn't
> exist, or (b) the code sucks and people complain about it until (c) we
> delete it and then (d) people on misc try to invent fake history.
>
> Since no such person existed, (a) led to (c) and here we are at (d).
>
> I wish everyone would stop making uneducated guesses and trying to
> rewrite history that isn't STUDIED and understand.  In particular what
> bothers me is the LACK OF STUDY, but this is misc, STUDYING stuff is
> clearly too hard, and making uneducated guesses is the norm.
>

Might find following from "Axis of Easy #109" by Mark E. Jeftovic of
easyDNS:

Major bluetooth security flaw discovered.

Researchers at the Center for IT-Security, Privacy and Accountability
 (CISPA) have discovered a major new vulnerability in the 20+ year-old
Bluetooth protocol.  The “Key Negotiation of Bluetooth”, aka “KNOB” attack
lets attackers, without any prior knowledge of details of either side of
the conversation, trick two endpoints in a Bluetooth handshake into using
an encryption key that can then be brute-forced (I think they do this by
tricking each side into using a 1-byte encryption key).

Of course, once the key is cracked the attacker has access to all
communications on the Bluetooth channel.

The Bluetooth spec is being upgraded to specify longer encryption keys, and
users are urged to remain current with all manufacturer updates.

Read:
https://www.forbes.com/sites/zakdoffman/2019/08/15/critical-new-bluetooth-security-issue-leaves-your-devices-and-data-open-to-attack/
And: https://knobattack.com/


And if your "manufacturer" has EOLed your product, you're SOOL.
--patrick



> John Brahy  wrote:
>
> > Right, without reading the code and only reading this commit message
> it's all conjecture.
> > I was just hoping to hear something more if someone was inclined to
> share.
> >  inclined. The commit message seems like some sort of inside joke.
> >
> > Log message:
> > "It's not the years, honey; it's the mileage."
> >
> > bluetooth support doesn't work and isn't going anywhere. the current
> > design is a dead end, and should not be the basis for any future support.
> > general consensus says to whack it so as to not mislead the unwary.
> >
> > On Wed, Aug 7, 2019 at 10:06 AM Theo de Raadt 
> wrote:
> >
> >  Bryan Wright  wrote:
> >
> >  > Are there technical/philosophical problems that make all versions of
> >  > Bluetooth incompatible with the project, or is it a just matter of
> >  > removing what is not being maintained?
> >
> >  I'm sure a bunch of you can come up with theories about what actually
> >  transpired, without reading any of the code that used to be here, or
> >  the commit messages.
> >
> >  Basically, feel free to keep making up stuff.
> >
>
>

Re: HP OfficeJet 5610 Scanner

[patrick keshishian]

On Wed, Feb 13, 2019 at 3:57 PM Joe M  wrote:

> Hello,
>
> I have an HP OfficeJet 5610 All-In-One that worked fine with scanimage on
> linux.
>
> On Openbsd, sane-find-scanner recognises the device but scanimage
> --list-devices cannot find it. Just want to check if anyone has it
> working on OpenBSD?


this may be relevant:
https://marc.info/?l=openbsd-tech=149516134609273=2




> joe:10362$ d sane-find-scanner
>
>   # sane-find-scanner will now attempt to detect your scanner. If the
>   # result is different from what you expected, first make sure your
>   # scanner is powered up and properly connected to your computer.
>
>   # No SCSI scanners found. If you expected something different, make sure
> that
>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>
> could not fetch string descriptor: Input/output error
> could not fetch string descriptor: Input/output error
> found USB scanner (vendor=0x03f0 [HP], product=0x4f11 [Officejet 5600
> series]) at libusb:005:002
> found USB scanner (vendor=0x1b1c [Corsair Components, Inc.],
> product=0x0c09 [H100i v2]) at libusb:006:003
>   # Your USB scanner was (probably) detected. It may or may not be
> supported by
>   # SANE. Try scanimage -L and read the backend's manpage.
>
>   # Not checking for parallel port scanners.
>
>   # Most Scanners connected to the parallel port or other proprietary ports
>   # can't be detected by this program.
> joe:10370$ d scanimage --list-devices
> [bjnp] create_broadcast_socket: ERROR - bind socket to local address
> failed - Can't assign requested address
> [bjnp] create_broadcast_socket: ERROR - bind socket to local address
> failed - Can't assign requested address
> [bjnp] create_broadcast_socket: ERROR - bind socket to local address
> failed - Can't assign requested address
> [bjnp] create_broadcast_socket: ERROR - bind socket to local address
> failed - Can't assign requested address
> [bjnp] create_broadcast_socket: ERROR - bind socket to local address
> failed - Can't assign requested address
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
>
> Thanks
> Joe
>
>

Re: What programming languages and operating systems will be used after Jesus returns?

[patrick keshishian]

On Sat, Feb 9, 2019 at 12:33 PM Ingo Schwarze  wrote:

> Hi Mihai,
>
> please don't feed trolls.
>
> The original BSD mascot happens to be the beast,
> but apart from that, this thread is off-topic even on misc@.
>

also you have got daemons running in the system.



> Yours,
>   Ingo
>
>

Re: spam and pf

[patrick keshishian]

On 11/18/17, Edgar Pettijohn  wrote:
> I read an article written I believe by Mr. Hansteen about using
> pf queues to mess with email spammers. Now that I have time to
> play around with it I can't seem to find it again. Does anyone
> know the article I speak of and can possibly provide a link.
>
> Thanks,

this?
http://bsdly.blogspot.com/2014/02/effective-spam-and-malware.html

Re: Abort Trap question

[patrick keshishian]

On 11/15/17, Philip Guenther  wrote:
> On Wed, Nov 15, 2017 at 11:08 AM, Mike Coddington 
> wrote:
>
>> On Wed, Nov 15, 2017 at 10:01:09AM -0600, Daniel Boyd wrote:
>> > I've installed OpenBSD/macppc twice on my G4 Cube now and it seems to
>> > be working fine until I go to untar src.tar.gz at which point it throws
>> > some abort trap errors and crashes.  If I reboot, I get a bunch of
>> > abort traps during the boot process followed by several:
>> >
>> > init: can't exec getty '/usr/libexec/getty' for pot /dev/ttyC3: ...
>> >
>> > What do you guys think this is...?  Hard drive failure...?
>>
>> Out of curiosity, does the same thing happen if you extract the tar with
>> the pax(1) program? That'll at least let you know if it's tar causing
>> the problem or not.
>>
>
> tar _is_ pax:
> : corwin; ls -li /bin/tar /bin/pax
> 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/pax
> 52015 -r-xr-xr-x  3 root  bin  433472 Nov  1 11:15 /bin/tar
> : corwin;
>
> Fundamentally, unless a userspace process is poking at devices or similar,
> it should be unable to panic the kernel.  An abort trap in the kernel is
> either a kernel bug or a hardware bug.  IIRC there's some pmap bug on
> macppc that no one has managed to track down which causes crashes on some
> machines, but not others.  I've never hit it on the Macbook I use for
> builds, but the ports build boxes, whatever model they are, seem to hit it
> periodically...

I read it as the tar process is the one aborting. which, if true,
sounds like user-land and kernel are out-of-sync.

Unfortunately, specific info is missing from the problem report.

--patrick

Re: Mac G4 Cube Problems

[patrick keshishian]

On 10/24/17, Daniel Boyd  wrote:
> I'm into week 2 of trying to get OpenBSD installed on my G4 Cube.
>
> I first tried installing via CD, but the CD-ROM drive is broken.
>
> I then tried DHCP/TFTP/NFS booting but couldn't get that working.
>
> I then tried attaching another IDE CD-ROM drive to the Cube, but I
> couldn't get the CD to boot (tried install62.iso and cd62.iso).
>
> boot cd:,ofwboot /6.2/macppc/bsd.rd DISK-LABEL: read of block 0 failed
> ATAPI-DISK: open of DISK-LABEL failed can't OPEN: cd:,ofwboot
>
> I guess maybe the IDE drive is having issues reading the CD?  I have no
> idea.
>
> Abandoning that idea, I am now attempting to boot the installer from
> the internal hard drive.  I read in INSTALL.macppc that the bootloader
> has to be on a DOS partition (or HFS if dual booting which I'm not), so
> I looked at the macppc install.md for clues as to how this works.
> Here's what I've done so far:
>
> 1) Installed OpenBSD 6.2 on old spare Dell with IDE hard drive/CD-ROM
> 2) Bought Torx T10 screw driver off Amazon
> 3) unscrewed some things to get to the IDE connector and then hooked
> the Cube hard drive up to the Dell as IDE secondary master
> 4) copied /usr/mdec/mbr from macppc base62.tgz
> 5) reading from macppc install.md:
> 5a) dd if=/dev/zero of=/dev/rwd1c bs=1M count=1  #assume this is
> wiping out the old MBR
> 5b) fdisk -f mbr -iy wd1 #write default macppc mbr to disk
> 6) newfs -t msdos wd1i

my guess is this step screws your process. You are running into an
endianess issue. Your DELL is little endian while MacPPC is bigendian
and OpenBSD assumes native endianness on file-systems (I am pretty
sure I've read that somewhere).

Need to find another MacPPC based system to run your steps through.

--patrick


> 7) newfs all the openbsd partitions
> 8) mount dos partition and wd1a ffs partition
> 9) copy ofwboot to dos partition
> 10) copy bsd.rd and installation tgz files to ffs partition
>
> 11) Hooked the hard drive back into the Cube, powered it on and then
> typed this into OpenFirmware
>
> 0 > boot hd:,ofwboot /bsd.rd
>
> the system added things to the end of that line after I pressed enter:
> 0 > boot hd:,ofwboot /bsd.rd load-size=fcbc adler32=c626975c
>
> and...
>
> Loading ELF
>>> OpenBSD/macppc BOOT 1.6
> /pci@f200/mac-io@17/ata-4@1f000/disk@0:/etc/boot.conf: line too
> long
> boot >
> booting /pci@f200/mac-io@17/ata-4@1f000/disk@0:/bsd.rd /pci@f20
> 0/mac-io@17/ata-4@1f000/disk@0:/bsd.rd: Inappropriate file type or
> format
>  failed(12304). will try /bsd
>
> So...what am I doing wrong?  It's finding ofwboot, but not the kernel.
> Where is ofwboot looking for bsd.rd??  I assume it shouldn't go in the
> DOS partition since it's only recommended to be 1MB.
>
>

Re: OpenBSD 6.0 CDs arrived today

[patrick keshishian]

Also arrived in Southern California USA

http://sidster.org/gallery/obsd/60/img_2538.sml.jpg

Fantastic work folks and great tee-shirt design!
Also a "thank you" to Lyn at OpenBSD Store.

--patrick


On 9/7/16, Kenneth Gober  wrote:
> Shipments of OpenBSD 6.0 CDs have started arriving, I'm in the USA,
> New York area.
>
> -ken

Re: xpdf crashes when going fullscreen

[patrick keshishian]

On 8/24/16, Karel Gardas  wrote:
> Please also type `bt' and hit enter after run in gdb -- this will
> instruct gdb to print whole stack trace which may show how you get
> into the crash situation or at least help a little bit more.

Also, OP might consider contacting xpdf's author: Derek B. Noonburg[0].
He was very responsive on the one occasion I contacted him about
xpdf's performance[1].

--patrick

[0] contact info over here: http://www.foolabs.com/xpdf/home.html
[1] http://marc.info/?l=openbsd-ports=140056429615423=2


> On Wed, Aug 24, 2016 at 7:30 AM, Alessandro DE LAURENZIS
>  wrote:
>> Dear misc@ readers,
>>
>> just noticed that xpdf receives a bus error as soon as the fullscreen mode
>> is
>> activated.  A gdb trace follows, hoping it gives some hints:
>>
>> GNU gdb 6.3
>> Copyright 2004 Free Software Foundation, Inc.
>> GDB is free software, covered by the GNU General Public License, and you
>> are
>> welcome to change it and/or distribute copies of it under certain
>> conditions.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB.  Type "show warranty" for
>> details.
>> This GDB was configured as "amd64-unknown-openbsd6.0"...(no debugging
>> symbols found)
>>
>> (gdb) run
>> Starting program: /usr/local/bin/xpdf
>>
>> Program received signal SIGBUS, Bus error.
>> 0x1693d3cabc78 in XtWindowOfObject () from
>> /usr/X11R6/lib/libXt.so.11.0
>>
>> --
>> Alessandro DE LAURENZIS
>> [mailto:jus...@atlantide.t28.net]
>> LinkedIn: http://it.linkedin.com/in/delaurenzis

6.0 Poster Sighting

[patrick keshishian]

22/08/2016 - midday - Southern California, USA

Re: DPB can't do it's job in 6.0

[patrick keshishian]

On 8/19/16, Christian Weisgerber  wrote:
> On 2016-08-19, Stuart Henderson  wrote:
>
>> The chroot support is currently optional, but you do need to create the
>> user accounts if sysmerge didn't do it for you (_pbuuld, _pfetch), and
>> start dpb as root.
>
> No, running dpb as root is also optional.

true, but then it doesn't switch users to _p{build,fetch}. it runs
as user starting it.  Or am I missing a subtlety?

--patrick

Re: Copy-Paste not possible from a xterm

[patrick keshishian]

On 8/8/16, Stefan Wollny  wrote:
>> Gesendet: Montag, 08. August 2016 um 21:36 Uhr
>> Von: "Mihai Popescu" 
>> An: misc@openbsd.org
>> Betreff: Re: Copy-Paste not possible from a xterm
>>
>> > For some time now I cannot copy-paste text from a xterm window by
>> > simultaneously \
>> > pressing left and right mouse buttons.
>>
>> > Anyone an idea?
>>
>> Um, carpal tunnel syndrome?
>>
> Nice - but no.
>
>> I know somebody unable to double click after a heavy drinking night.
>> But he was able to manage this by clicking one time followed by Enter
>> key. So, no panic.
>>
> Looks to me that I missed to find the right words to explain the issue
> correctly. My bad.
>
> New try:
> I open an xterm and e.g. want to see the content of /etc/fstab. So I issue
> $ cat /etc/fstab
>
> Now I want to copy one line to thunderbird or a web client via firefox. I
> used to do this by marking the relevant line, change to the other
> application (say: the web client) and press left and right mouse buttons
> simultaneously. Until some time ago this procedure inserted the marked-up
> line at the position of the cursor. No double-click, no Enter. Standard Unix
> - right?

Can you paste the "copied" line into the same xterm or another xterm
window using your outlined procedure?

--patrick


> Exactly this procedure is disfunct on my system. No idea why, no idea where
> to look at. No big thing, just wondering if I missed s.th. or else.
>
> I know how to circumvent this non-behaviour in most cases.
>
> Just wanted to know if s.o. else witnessed the same and maybe has an answer.
> Maybe I need to additionally post some specific settings I am not aware of.
>
> OK?
>
> Best,
> STEFAN

Re: Question on Theo's dotSecurity paper

[patrick keshishian]

On 7/21/16, Ted Unangst <t...@tedunangst.com> wrote:
> patrick keshishian wrote:
>> Hi,
>>
>> Quick question about Theo de Raadt's "Presentations: dotSecurity
>> 2016"[1]. Slide 11 says "Most violations result in process being killed",
>> not all violations?
>>
>> Just wanted clarification here.
>
> If you look at kern_pledge.c, you'll see a couple instances where EPERM is
> returned instead of killing the process.

Thank you

Question on Theo's dotSecurity paper

[patrick keshishian]

Hi,

Quick question about Theo de Raadt's "Presentations: dotSecurity
2016"[1]. Slide 11 says "Most violations result in process being killed",
not all violations?

Just wanted clarification here.

Thanks,
--patrick


[1] http://www.openbsd.org/papers/dot2016.pdf

2016-MAR-30 amd64 snapshot won't wake from sleep

[patrick keshishian]

Hi,

Just upgraded my laptop/netbook to 2016-MAR-30 amd64 snapshot.
I build a few ports, things seemed fine. Made it sleep by shutting the
lid. Trying to wake it up by opening lid, pressing a key (e.g., space-bar)
as it used to work previously by waking up the machine. However,
with this snapshot, it seems like it is tries to wake up -- screen lights
up for a second, but then the speaker chirps, and it goes back to sleep.
Pressing the button (or another button) repeats the screen light-up,
chirp and sleep cycle over again.

Is there anything I should try (or rather a dev would like me to try)
before I force reboot it to get you a dmesg?

Thanks,
--patrick

Re: Industrial use of line printers, does/would your company/organization use them with our lpd?

[patrick keshishian]

On 2/17/16, Andy Bradford  wrote:
> Anyway,  just  some  musings.  Is  there anyone  else  out  there  using
> lpr/lpd/lprm from base? Maybe I'm the only one?

yep. been using it for many years with many different HP and Brother
network printers.

--patrick

Re: libGL error: failed to open drm device: Permission denied

[patrick keshishian]

On 12/27/15, Jonathan Gray  wrote:
> On Mon, Dec 28, 2015 at 12:25:25AM +0200, Mihai Popescu wrote:
>> Hello,
>>
>> I am running cwm and I had some problems starting chrome from the menu
>> - it starts for the very first time when i click on the menu, then i
>> have to click 2 or 3 times on menu entry to start chrome again. This
>> is not a big deal, maybe a cwm glitch.
>>
>> I went to start chrome from xterm, and I got these errors:
>>
>> $ chrome
>> libGL error: failed to open drm device: Permission denied
>> libGL error: failed to load driver: r600
>> libGL error: failed to open drm device: Permission denied
>> libGL error: failed to load driver: r600
>>
>> Is it normal, can it be fixed on my side?
>
> The ownership of /dev/drm0 should be changed according to
> /etc/fbtab to your user after logging in.

I have noticed (in the past), switching from X to virtual term
(Ctrl+Shift+Fx) will override/revert the ownership of /dev/drm0,
resulting in above (or similar) errors when I switch back to X
and run something like xlock.

I say "in the past", as I have avoided above switching since.

Hope this sheds some light onto the problem (or possibly
as-designed behavior).

--patrick


> Can you include the output of ls -l /dev/drm0 and
> the contents of /var/log/Xorg.0.log ?
>
> How are you starting X, xdm/startx/?

Re: Connection refused *.openbsd.org

[patrick keshishian]

On 11/6/15, Raul Miller  wrote:
> On Fri, Nov 6, 2015 at 10:26 AM, Ted Unangst  wrote:
>> If I'm not mistaken, machines that do hardware checksumming will show an
>> incorrect checksum in tcpdump.
>
> That sounds like it should be a problem with some specific machines,
> rather than a protocol issue.

What Ted means, is the software driver for the NIC does not
calculate the checksum for the packet if the hardware is capable*
of taking on that task. Therefore, in those cases, tcpdump will
show "bad checksum". This is expected as the HW hasn't seen
the packet yet; once it does, the packet will be sent out with
correct/updated checksum.

--patrick

* This assumes the HW is capable of checksum offloading and the
driver is enabling said feature (hence, not calculating the checksum
itself, in software).



> Do you recall which machines exhibited this problem?
>
> Thanks,
>
> --
> Raul

Re: 5.8-release building mutt from ports fails

[patrick keshishian]

On 11/4/15, Tati Chevron  wrote:
> On Wed, Nov 04, 2015 at 07:21:39AM -0800, Chris Cappuccio wrote:
>>Tati Chevron [chev...@swabsit.com] wrote:
>>> Hi,
>>>
>>> On a freshly installed 5.8-release, I am unable to build mutt from source
>>> using the ports tree.
>>>
>>> I've never had any difficulty building the mutt port since at least
>>> 5.0-release.
>>>
>>> systrace: deny user: root, prog: /bin/cp, pid: 24101(0)[7002], policy:
>>> /usr/bin/env, filters: 248, syscall: native-chflagsat(107), filename:
>>> /usr/ports/pobj/db-4.6.21-no_java-bootstrap-no_tcl/fake-amd64-no_java-bootstrap-no_tcl/usr/local/share/doc/db4/articles/inmemory,
>>> flags: cp: chflags:
>>> /usr/ports/pobj/db-4.6.21-no_java-bootstrap-no_tcl/fake-amd64-no_java-bootstrap-no_tcl/usr/local/share/doc/db4/articles/inmemory:
>>> Operation not permitted
>>
>>Unfortunately you'll have to turn off systrace to build this port. Are you
>>using any custom systrace rules?
>
> No, no custom rules on this machine, just a standard installation.  But
> what's changed to cause this new behaviour?

does this patch help your case:

http://marc.info/?l=openbsd-ports=143346045720505=2

--patrick

Re: Keyboard and touchpad aren't working properly in X

[patrick keshishian]

On 11/2/15, Артур Истомин <art.is...@yandex.ru> wrote:
> On Mon, Nov 02, 2015 at 10:22:08PM +0100, Mike Burns wrote:
>> On 2015-11-03 01.11.13 +0500, Артур Истомин wrote:
>> > On Mon, Nov 02, 2015 at 09:07:05AM -0800, patrick keshishian wrote:
>> > > On 11/2/15, Артур Истомин <art.is...@yandex.ru> wrote:
>> > > > I have strange behaviour with keyboard and touchpad.
>> > > >
>> > > > Keyboard. It is like I am in console/terminal. All keyboard
>> > > > shortcuts
>> > > behave
>> > > > like
>> > > > I am in console/terminal. E.g. Ctrl+A does not selecting all in
>> > > > firefox
>> > > > address bar,
>> > > > but instead move cursor to beginning; Ctrl+U delets all from the
>> > > > left;
>> > > > Ctrl+W delets one word from the left etc. (I even study some new
>> > > > shortcuts)
>> > >
>> > > This has always been the behavior for text-input fields/widgets.
>> >
>> > Wow, I didn't know it. I always thought it was a problem with my
>> > hardware.
>> > Is it possible to make it worked like in Linux?
>>
>> If you don't want that, you'll have to undo it:
>> http://kb.mozillazine.org/Emacs_Keybindings_%28Firefox%29
>
> But it's exactly the behavior that I'm trying to avoid :)
> I want crossplatform keybindings in GUI applications:
>
> Ctrl+A - select all in input field
> Ctrl+W - close tab

You mentioned Firefox, my first response was with regard
to text-input fields/widgets. e.g., address bar, search box, etc.
However, at least with Firefox, if focus is not owned by any
text-entry field/widget, CTRL+A and CTRL+W do behave as
you wish. i.e., The former selects content of the page/pane
and the latter will close the current tab/window.

Is this not what you see happen?

--patrick

Re: Keyboard and touchpad aren't working properly in X

[patrick keshishian]

On 11/2/15, Артур Истомин  wrote:
> I have strange behaviour with keyboard and touchpad.
>
> Keyboard. It is like I am in console/terminal. All keyboard shortcuts
behave
> like
> I am in console/terminal. E.g. Ctrl+A does not selecting all in firefox
> address bar,
> but instead move cursor to beginning; Ctrl+U delets all from the left;
> Ctrl+W delets one word from the left etc. (I even study some new shortcuts)

This has always been the behavior for text-input fields/widgets.


> Touchpad. It is Clickpad (without buttons, like on Macbook Air). Driver -
> synaptics. Click & Drug does not work. I can't click left "button" and at
> the same
> time drug cursor with second finger, it is just does not work.

It might just be that you need to configure it via synclient(1).

hth,
---patrick


> Such behaviour last from OpenBSD 5.6, time when I migrated from Linux to
> OpenBSD.
>
> I would be grateful for any help.
>
> Xorg.log and dmesg below
>
> OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 6209654784 (5921MB)
> avail mem = 6017564672 (5738MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0840 (27 entries)
> bios0: vendor Phoenix Technologies Ltd. version "V1.20" date 12/12/2012
> bios0: Acer Aspire V5-571G
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S1 S3 S4 S5
> acpi0: tables DSDT FACP SLIC SSDT ASF! HPET APIC MCFG FPDT SSDT SSDT UEFI
> UEFI POAT SSDT UEFI
> acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S3)
> PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S5) RP03(S5) PXSX(S4) RP04(S4)
> PXSX(S4) RP05(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz, 1397.05 MHz
> cpu0:
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz, 1396.83 MHz
> cpu1:
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 1, core 0, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz, 1396.83 MHz
> cpu2:
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 1, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz, 1396.84 MHz
> cpu3:
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (P0P1)
> acpiprt2 at acpi0: bus 2 (RP01)
> acpiprt3 at acpi0: bus -1 (RP02)
> acpiprt4 at acpi0: bus 3 (RP03)
> acpiprt5 at acpi0: bus 4 (RP04)
> acpiprt6 at acpi0: bus -1 (RP05)
> acpiprt7 at acpi0: bus -1 (RP06)
> acpiprt8 at acpi0: bus -1 (RP07)
> acpiprt9 at acpi0: bus -1 (RP08)
> acpiprt10 at acpi0: bus 1 (PEG0)
> acpiprt11 at acpi0: bus -1 (PEG1)
> acpiprt12 at acpi0: bus -1 (PEG2)
> acpiprt13 at acpi0: bus -1 (PEG3)
> acpiec0 at acpi0
> acpicpu0 at acpi0: C3(200@109 mwait.1@0x30), C2(500@80 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C3(200@109 mwait.1@0x30), C2(500@80 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C3(200@109 mwait.1@0x30), C2(500@80 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C3(200@109 mwait.1@0x30), C2(500@80 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpitz0 at acpi0: critical temperature is 98 degC
> acpitz1 at acpi0: critical 

Re: CD's arrived

[patrick keshishian]

On 10/14/15, Amarendra Godbole  wrote:
> And in San Francisco, CA.
>
> Now I can attach a face to a name!

Neato... but I spy a typo in ratchov's index :)

Excellent work everyone and Happy 20th!

--patrick

Re: network config question

[patrick keshishian]

On 9/24/15, Kapetanakis Giannis <bil...@edu.physics.uoc.gr> wrote:
> On 24/09/15 22:41, patrick keshishian wrote:
>> Hi,
>>
>> I'm pretty sure I'm over-thinking this, so I thought I'd step back and
>> see if I can get some hints as how this sort of a set-up is done
>> "properly" by pros.
>>
>>
>> Say, existing set up:
>>
>> [internet] -- [pf] -- [ public-ip-net/24 ]
>>
>>
>> Want to add/connect a private 192.168.0/24 to existing [
>> public-ip-net/24]:
>>
>> ... [ public-ip-net/24] -?- [ obsd box ] -- [ 192.168.0/24 ]
>>
>>
>> Goals:
>> 1. Hosts in both networks "talk" with one another freely.
>> e.g., hosts in existing network see hosts in to-be-added 192
>> network, as they are; i.e., not NAT-ed. And vice versa.
>> 2. Hosts in 192.168.0/24 have access to the internet through
>> the same/existing gateway.
>>
>>
>> I lack some knowledge wrt to the subject, where I think, I am
>> filling the "holes" with, possibly, far too complicated ideas.
>>
>> Appreciate any and all help offered.
>>
>> Thanks,
>> --patrick
>
> First of all you don't need a second obsd/pf router for this.
>
> Either put the private network on a secondary ip on the same
> vlan/interface as the public
> or use a new vlan/interface for the private network.
>
> pf can be tuned to fit you filtering needs.
>
> Do the nat on [pf] box only for packets going out on its egress interface.

Thanks Daniel and Kapetanakis for replies.

I read some on vlans (as I knew next to nothing about them).
I think I'm still not completely clear on how they would work,
unless vlan-capable switch is used, which the current set-up lacks;
The only reference I found, which explicitly states this, is M. Lucas's
book ("Absolute OpenBSD...").

--patrick

network config question

[patrick keshishian]

Hi,

I'm pretty sure I'm over-thinking this, so I thought I'd step back and
see if I can get some hints as how this sort of a set-up is done
"properly" by pros.


Say, existing set up:

[internet] -- [pf] -- [ public-ip-net/24 ]


Want to add/connect a private 192.168.0/24 to existing [ public-ip-net/24]:

... [ public-ip-net/24] -?- [ obsd box ] -- [ 192.168.0/24 ]


Goals:
1. Hosts in both networks "talk" with one another freely.
   e.g., hosts in existing network see hosts in to-be-added 192
   network, as they are; i.e., not NAT-ed. And vice versa.
2. Hosts in 192.168.0/24 have access to the internet through
   the same/existing gateway.


I lack some knowledge wrt to the subject, where I think, I am
filling the "holes" with, possibly, far too complicated ideas.

Appreciate any and all help offered.

Thanks,
--patrick

Re: odd behaviour of spamdb

[patrick keshishian]

On 7/13/15, Markus Rosjat ros...@ghweb.de wrote:
 hi there,

 I have a script the following script to delete spam mx ip from the spamd
 whitelist and write them in my own blacklist. After that I reload the
 blacklist with spamd- setup.  This seems to work but I noticed when the
 same ip has another mail in the greylist the ip becomes whitelisted if
 the delivery attempt is successful (which it shouldnt in the first place
 because I trapped the ip and put it in my blacklist). This seems like an
 odd behaviour to me, its not the end of the world but it feels kinda
 wrong :)

If i understand your message correctly, after removal of the ip
from the WHITE list, it still remains in the GREY, which will be
WHITE-listed again, on the next spamd scan (60 second interval),
thus, allowing for the successful delivery.

To see this with an IP that has been WHITE-listed, but still in
the GREY, do:

$ spamdb | grep $ip
WHITE|$ip|...
GREY|$ip|...
$ spamdb -d $ip
$ spamdb | grep $ip
GREY|$ip|...
$ sleep 60
$ spamdb | grep $ip
WHITE|$ip|...
GREY|$ip|...


As a side note, your awk bit can be replaced by a `cut -d \| -f 2'.

--patrick


 here is the script:

 ip_range=$1

 for i in `spamdb | grep $ip_range | grep WHITE | awk -F | '{print $2}'`;
   do
echo $i
/usr/sbin/spamdb -d $i
/usr/sbin/spamdb -a -t $i
echo $i  /etc/mail/blacksheep.txt
   done

 /usr/libexec/spamd-setup

 maybe someone give me some hints for improvement

 regards

 --
 Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

 G+H Webservice GbR Gorzolla, Herrmann
 Königsbrücker Str. 70, 01099 Dresden

 http://www.ghweb.de
 fon: +49 351 8107220   fax: +49 351 8107227

 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you
 print it, think about your responsibility and commitment to the ENVIRONMENT

Re: X error: Maximum number of clients reached

[patrick keshishian]

On 7/6/15, luke...@onemodel.org luke...@onemodel.org wrote:
 I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches.  When I simply
 launch xfce (from ports), an xterm, and ~34 xedit windows, I get:
 Maximum number of clients reachedError: Can't open display: :0.0. I
 think I also had the same problem earlier when running fvwm instead
 of xfce.


these threads might interest you:

freedesktop-xorg-devel:
[PATCH RFC] configurable maximum number of clients
http://marc.info/?t=14328287932r=1w=2
[PATCH RFC xserver v2] configurable maximum number of clients
http://marc.info/?l=freedesktop-xorg-develm=143291631231526w=2
[PATCH v3] configurable maximum number of clients
http://marc.info/?t=14333428952r=1w=2

--patrick


 I've searched thru code (not yet exhaustively), searched the mailing
 lists,  the web with DuckDuckGo(DDG), and tried various things.
 Most DDG search results talk about buggy apps, or closing
 windows, but I don't think that's my problem as I don't have that
 many windows open.

 Three of the search results say this (though the info could be
 old, by several years or more):
  By default, the X server has a limit of just 128. In order to
   increase this limit, you need to run at least Solaris 8 or an
   earlier release with the Xserver patch applies that fixes bug:
   4185418 the X server should support more connections .Then
   change the Xservers configuration file and add the -clients
 1024
   option to the X commandline.
 However, I've passed -clients 1024 to the startx command with no
 effect, and I don't see that as a parameter in 'man X' or 'man Xservers'.
 Maybe that parameter needs to go in a config file somewhere, but
 I'm floundering at this point in the X config stuff.

 When I searched through the xenocara code, I found that the error
 comes from xserver/os/connection.c, where a constant NOROOM
 contains the error message, and interesting functions being called
 include AllocNewConnection, ErrorConnMax, and
 InitConnectionLimits which is where the variable MaxClients is
 being set.

 When I opened enough xedit windows to reproduce the error, just
 now, then closed one of them and ran xwininfo -root -children|wc I
 got a result of 213.  Then I killed those 17 xedit windows (I have other
 things open now also) and xwininfo -root -children|wc said 94.

 That's about as far as I've got, since I'm new enough with this to
 be unsure whether I'm going in a good direction, diagnostically;
 my ignorance might be causing this to take longer than needed,
 and I'm hoping not to have to run X in gdb

 I don't see anything interesting in /var/log/messages or in
 Xorg.0.log: I think it's all just repeated output telling me it
 un- and re-found my external USB mouse and keyboard.

 Should I use sendbug for this?

 Any ideas appreciated. Thanks!!

 Luke

Re: regression with wsdisplay? 2015-06-30 amd64 snap

[patrick keshishian]

On 7/2/15, Mike Larkin mlar...@azathoth.net wrote:
 On Thu, Jul 02, 2015 at 11:50:06AM -0700, patrick keshishian wrote:
 p.s., and evidently, after the sleep/wake, the laptop does not
 care to shutdown, neither by reboot(8) nor the power-button
 press (requires 10s hold of the power-button).


 You're looking at not too much time between a working kernel
 and the broken one, bisecting diffs might help us track down what
 failed more quickly.

reverting dev/acpi/acpicpu.c back to 1.63 from 1.64 seems
to fix my issue.

Unfortunately, 1.63-1.64 contains a mass of changes.


 Also, please use sendbug so we get an acpidump.

will do.

--patrick


 -ml

 On 7/2/15, patrick keshishian pkesh...@gmail.com wrote:
  Just noticed this issue with:
 
  OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
  dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 
  After a sleep/wake cycle I noticed that key-repeat stopped working.
 
  Running top(1) I see that the display isn't being updated, requiring
  pressing the space-bar to force an update.
 
  Last snapshot on this laptop without any major issues was:
 
  OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
  dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 
  One change was I installed a new 9-Cell battery on this laptop.
 
  Ideas?
 
  I'll try a new snap in a few days.
 
  --patrick
 
 
  dmesg diff:
 
  --- dmesg.boot-snap-20150602   Wed Jun  3 20:38:38 2015
  +++ dmesg.boot-snap-20150630   Thu Jul  2 11:29:46 2015
  @@ -1,7 +1,7 @@
  -OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
  +OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
   dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
   real mem = 1861025792 (1774MB)
  -avail mem = 1800888320 (1717MB)
  +avail mem = 180082 (1717MB)
   mpath0 at root
   scsibus0 at mpath0: 256 targets
   mainbus0 at root
  @@ -15,7 +15,7 @@ acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3)
  EHCI(
   acpitimer0 at acpi0: 3579545 Hz, 32 bits
   acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
   cpu0 at mainbus0: apid 0 (boot processor)
  -cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz
  +cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
   cpu0:
  FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
   cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
  64b/line 16-way L2 cache
   cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
  associative
  @@ -34,10 +34,10 @@ acpiprt5 at acpi0: bus -1 (PB7_)
   acpiprt6 at acpi0: bus 9 (P2P_)
   acpiprt7 at acpi0: bus 1 (AGP_)
   acpiec0 at acpi0
  -acpicpu0 at acpi0: C3, C2
  +acpicpu0 at acpi0: C3(@83 io@0x8015), C2(@18 io@0x8014)
   acpitz0 at acpi0: critical temperature is 100 degC
   acpiac0 at acpi0: AC unit online
  -acpibat0 at acpi0: BAT1 model UM09A41 serial 22962 type LION oem
  SONY
  +acpibat0 at acpi0: BAT1 model UM09A41 serial 14 type LION oem SONY
   acpibtn0 at acpi0: LID_
   acpibtn1 at acpi0: SLPB
   acpibtn2 at acpi0: PWRB
 
 
  Full dmesg:
 
  OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
  dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
  real mem = 1861025792 (1774MB)
  avail mem = 180082 (1717MB)
  mpath0 at root
  scsibus0 at mpath0: 256 targets
  mainbus0 at root
  bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1010 (17 entries)
  bios0: vendor Phoenix Technologies LTD version v1.3307 date
  05/31/2010
  bios0: Gateway LT31
  acpi0 at bios0: rev 2
  acpi0: sleep states S0 S3 S4 S5
  acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC
  acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3)
  acpitimer0 at acpi0: 3579545 Hz, 32 bits
  acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
  cpu0 at mainbus0: apid 0 (boot processor)
  cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
  cpu0:
  FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
  cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
  64b/line 16-way L2 cache
  cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
  associative
  cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully
  associative
  mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
  cpu0: apic clock running at 199MHz
  ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins
  acpimcfg0 at acpi0 addr 0xe000, bus 0-8
  acpihpet0 at acpi0: 14318180 Hz
  acpiprt0 at acpi0: bus 0 (PCI0)
  acpiprt1 at acpi0: bus -1 (PB3_)
  acpiprt2 at acpi0: bus -1 (PB4_)
  acpiprt3 at acpi0: bus 3 (PB5_)
  acpiprt4 at acpi0: bus 4 (PB6_)
  acpiprt5 at acpi0: bus -1 (PB7_)
  acpiprt6 at acpi0: bus 9 (P2P_)
  acpiprt7 at acpi0: bus 1 (AGP_)
  acpiec0 at acpi0

regression with wsdisplay? 2015-06-30 amd64 snap

[patrick keshishian]

Just noticed this issue with:

OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

After a sleep/wake cycle I noticed that key-repeat stopped working.

Running top(1) I see that the display isn't being updated, requiring
pressing the space-bar to force an update.

Last snapshot on this laptop without any major issues was:

OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

One change was I installed a new 9-Cell battery on this laptop.

Ideas?

I'll try a new snap in a few days.

--patrick


dmesg diff:

--- dmesg.boot-snap-20150602Wed Jun  3 20:38:38 2015
+++ dmesg.boot-snap-20150630Thu Jul  2 11:29:46 2015
@@ -1,7 +1,7 @@
-OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
+OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 1861025792 (1774MB)
-avail mem = 1800888320 (1717MB)
+avail mem = 180082 (1717MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
@@ -15,7 +15,7 @@ acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(
 acpitimer0 at acpi0: 3579545 Hz, 32 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
-cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz
+cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
 cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
 cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
@@ -34,10 +34,10 @@ acpiprt5 at acpi0: bus -1 (PB7_)
 acpiprt6 at acpi0: bus 9 (P2P_)
 acpiprt7 at acpi0: bus 1 (AGP_)
 acpiec0 at acpi0
-acpicpu0 at acpi0: C3, C2
+acpicpu0 at acpi0: C3(@83 io@0x8015), C2(@18 io@0x8014)
 acpitz0 at acpi0: critical temperature is 100 degC
 acpiac0 at acpi0: AC unit online
-acpibat0 at acpi0: BAT1 model UM09A41 serial 22962 type LION oem SONY
+acpibat0 at acpi0: BAT1 model UM09A41 serial 14 type LION oem SONY
 acpibtn0 at acpi0: LID_
 acpibtn1 at acpi0: SLPB
 acpibtn2 at acpi0: PWRB


Full dmesg:

OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1861025792 (1774MB)
avail mem = 180082 (1717MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1010 (17 entries)
bios0: vendor Phoenix Technologies LTD version v1.3307 date 05/31/2010
bios0: Gateway LT31
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC
acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-8
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PB3_)
acpiprt2 at acpi0: bus -1 (PB4_)
acpiprt3 at acpi0: bus 3 (PB5_)
acpiprt4 at acpi0: bus 4 (PB6_)
acpiprt5 at acpi0: bus -1 (PB7_)
acpiprt6 at acpi0: bus 9 (P2P_)
acpiprt7 at acpi0: bus 1 (AGP_)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(@83 io@0x8015), C2(@18 io@0x8014)
acpitz0 at acpi0: critical temperature is 100 degC
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 model UM09A41 serial 14 type LION oem SONY
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCD_
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00
ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00
drm0 at radeondrm0
radeondrm0: msi
ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00: msi
pci2 at ppb1 bus 3
re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102EL
(0x2480), msi, address 00:23:8b:ef:11:11
rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1
ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00: msi
pci3 at ppb2 bus 4
ral0 at pci3 dev 0 function 0 

Re: regression with wsdisplay? 2015-06-30 amd64 snap

[patrick keshishian]

p.s., and evidently, after the sleep/wake, the laptop does not
care to shutdown, neither by reboot(8) nor the power-button
press (requires 10s hold of the power-button).

On 7/2/15, patrick keshishian pkesh...@gmail.com wrote:
 Just noticed this issue with:

 OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

 After a sleep/wake cycle I noticed that key-repeat stopped working.

 Running top(1) I see that the display isn't being updated, requiring
 pressing the space-bar to force an update.

 Last snapshot on this laptop without any major issues was:

 OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

 One change was I installed a new 9-Cell battery on this laptop.

 Ideas?

 I'll try a new snap in a few days.

 --patrick


 dmesg diff:

 --- dmesg.boot-snap-20150602  Wed Jun  3 20:38:38 2015
 +++ dmesg.boot-snap-20150630  Thu Jul  2 11:29:46 2015
 @@ -1,7 +1,7 @@
 -OpenBSD 5.7-current (GENERIC) #973: Tue Jun  2 09:37:26 MDT 2015
 +OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
  dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
  real mem = 1861025792 (1774MB)
 -avail mem = 1800888320 (1717MB)
 +avail mem = 180082 (1717MB)
  mpath0 at root
  scsibus0 at mpath0: 256 targets
  mainbus0 at root
 @@ -15,7 +15,7 @@ acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(
  acpitimer0 at acpi0: 3579545 Hz, 32 bits
  acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
  cpu0 at mainbus0: apid 0 (boot processor)
 -cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz
 +cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
  cpu0:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
  cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
 64b/line 16-way L2 cache
  cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 @@ -34,10 +34,10 @@ acpiprt5 at acpi0: bus -1 (PB7_)
  acpiprt6 at acpi0: bus 9 (P2P_)
  acpiprt7 at acpi0: bus 1 (AGP_)
  acpiec0 at acpi0
 -acpicpu0 at acpi0: C3, C2
 +acpicpu0 at acpi0: C3(@83 io@0x8015), C2(@18 io@0x8014)
  acpitz0 at acpi0: critical temperature is 100 degC
  acpiac0 at acpi0: AC unit online
 -acpibat0 at acpi0: BAT1 model UM09A41 serial 22962 type LION oem SONY
 +acpibat0 at acpi0: BAT1 model UM09A41 serial 14 type LION oem SONY
  acpibtn0 at acpi0: LID_
  acpibtn1 at acpi0: SLPB
  acpibtn2 at acpi0: PWRB


 Full dmesg:

 OpenBSD 5.8-beta (GENERIC) #1050: Tue Jun 30 11:10:13 MDT 2015
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 1861025792 (1774MB)
 avail mem = 180082 (1717MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1010 (17 entries)
 bios0: vendor Phoenix Technologies LTD version v1.3307 date 05/31/2010
 bios0: Gateway LT31
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC
 acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3)
 acpitimer0 at acpi0: 3579545 Hz, 32 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: AMD Athlon(tm) Processor L110, 1197.19 MHz
 cpu0:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
 64b/line 16-way L2 cache
 cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
 cpu0: apic clock running at 199MHz
 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins
 acpimcfg0 at acpi0 addr 0xe000, bus 0-8
 acpihpet0 at acpi0: 14318180 Hz
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus -1 (PB3_)
 acpiprt2 at acpi0: bus -1 (PB4_)
 acpiprt3 at acpi0: bus 3 (PB5_)
 acpiprt4 at acpi0: bus 4 (PB6_)
 acpiprt5 at acpi0: bus -1 (PB7_)
 acpiprt6 at acpi0: bus 9 (P2P_)
 acpiprt7 at acpi0: bus 1 (AGP_)
 acpiec0 at acpi0
 acpicpu0 at acpi0: C3(@83 io@0x8015), C2(@18 io@0x8014)
 acpitz0 at acpi0: critical temperature is 100 degC
 acpiac0 at acpi0: AC unit online
 acpibat0 at acpi0: BAT1 model UM09A41 serial 14 type LION oem SONY
 acpibtn0 at acpi0: LID_
 acpibtn1 at acpi0: SLPB
 acpibtn2 at acpi0: PWRB
 acpivideo0 at acpi0: VGA_
 acpivout0 at acpivideo0: LCD_
 pci0 at mainbus0 bus 0
 pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00
 ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00
 pci1 at ppb0 bus 1
 radeondrm0 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00
 drm0 at radeondrm0
 radeondrm0: msi
 ppb1 at pci0

Re: Why does my 5.7 laptop suspend when I close the lid?

[patrick keshishian]

On 6/30/15, Alan Corey alan01...@gmail.com wrote:
 I didn't ask it to do that and I don't know how to unsuspend.  As far
 as I'm concerned this is an undocumented feature.  If I want to
 suspend I'll type zzz.  I haven't found a way to turn this off.

$ sysctl | grep suspend
machdep.lidsuspend=1


to un-suspend, it depends on your machine. One laptop I own
will wake by pressing the spacebar, and another wakes if I press
the Fn key. I would try the power-button as a last possibility
as well.

--patrick

Re: jwm ; speedy window manager

[patrick keshishian]

On 4/6/15, L.R. D.S. arrowscr...@mail.com wrote:
At 6 Apr 2015 23:12:43 + (UTC) from Brian Callahan bcal...@devio.us:

Or, and this is just a hypothesis, you don't have all those other things
and FVWM lists those for convenience.

 No, I can load everything normally...
 ok, I'm a bit worried now. I always check the signatures before/after
 install.
 You folks just have the Fvwm and no more?

$ echo /usr/X11R6/bin/*wm*
/usr/X11R6/bin/cwm /usr/X11R6/bin/fvwm /usr/X11R6/bin/twm

--patrick


 I usually don't use X, but that's what I see here. No joking.



 dmesg
 **

 OpenBSD 5.7-current (GENERIC.MP) #781: Wed Mar 18 19:03:42 MDT 2015
 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
 cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class)
 2.01 GHz
 cpu0:
 FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF
 real mem  = 3217440768 (3068MB)
 avail mem = 3152490496 (3006MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: date 02/05/09, BIOS32 rev. 0 @ 0xfb080, SMBIOS rev. 2.4 @
 0xf0100 (33 entries)
 bios0: vendor Award Software International, Inc. version F6 date
 02/05/2009
 bios0: Gigabyte Technology Co., Ltd. G31M-ES2C
 acpi0 at bios0: rev 0
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP MCFG APIC
 acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5)
 HUB0(S5) UAR1(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USBE(S3) AZAL(S5)
 PCI0(S5)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpimcfg0 at acpi0 addr 0xc000, bus 0-255
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
 cpu0: apic clock running at 182MHz
 cpu0: mwait min=45313, max=22512 (bogus)
 cpu1 at mainbus0: apid 1 (application processor)
 cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class)
 2.01 GHz
 cpu1:
 FPU,V86,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,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF
 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
 ioapic0: misconfigured as apic 0, remapped to apid 2
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus 1 (PEX0)
 acpiprt2 at acpi0: bus 2 (PEX1)
 acpiprt3 at acpi0: bus -1 (PEX2)
 acpiprt4 at acpi0: bus -1 (PEX3)
 acpiprt5 at acpi0: bus -1 (PEX4)
 acpiprt6 at acpi0: bus -1 (PEX5)
 acpiprt7 at acpi0: bus 3 (HUB0)
 acpicpu0 at acpi0
 acpicpu1 at acpi0
 acpibtn0 at acpi0: PWRB
 bios0: ROM list: 0xc/0xb400!
 cpu0: Enhanced SpeedStep disabled by BIOS
 pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 pchb0 at pci0 dev 0 function 0 Intel 82G33 Host rev 0x10
 vga1 at pci0 dev 2 function 0 Intel 82G33 Video rev 0x10
 intagp0 at vga1
 agp0 at intagp0: aperture at 0xd000, size 0x1000
 inteldrm0 at vga1
 drm0 at inteldrm0
 inteldrm0: 1920x1080
 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
 wsdisplay0: screen 1-5 added (std, vt100 emulation)
 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 2 int 16
 pci1 at ppb0 bus 1
 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: apic 2 int 17
 pci2 at ppb1 bus 2
 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102E (0x3480),
 msi, address 00:24:1d:fb:96:f7
 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1
 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23
 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19
 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18
 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 16
 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 2 int 23
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1
 pci3 at ppb2 bus 3
 ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM
 disabled
 pciide0 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA,
 channel 0 configured to native-PCI, channel 1 configured to native-PCI
 pciide0: using apic 2 int 19 for native-PCI interrupt
 wd0 at pciide0 channel 0 drive 1: HTS541060G9SA00
 wd0: 16-sector PIO, LBA48, 57230MB, 117208127 sectors
 wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
 atapiscsi0 at pciide0 channel 1 drive 0
 scsibus1 at atapiscsi0: 2 targets
 cd0 at scsibus1 targ 0 lun 0: TSSTcorp, DVD+-RW TS-H653G, D200 ATAPI
 5/cdrom removable
 cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: apic 2 int
 19
 iic0 at ichiic0
 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5
 spdmem1 at iic0 addr 0x52: 2GB 

Re: make build errors on me (perl does not install properly)

[patrick keshishian]

On 3/17/15, Gregory Edigarov ediga...@qarea.com wrote:
 On 03/16/2015 10:21 PM, Stuart Henderson wrote:
 On 2015-03-16, Gregory Edigarov ediga...@qarea.com wrote:
 Hello,

 I know I am re-asking the same question again, but what are the possible
 reasons of such behaviour?
 Obviously the system builds ok, but perl doesn't install correctly.
 I need my system to be correctly built from sources because i am going
 to make some experimental changes. (I am starting from the most fresh
 binary snapshot available).

 # env make clean obj build
 [skip many correct lines]
 I don't know if it's implicated in this problem, but don't run the
 multiple targets on one line like that, run them separately or do
 make clean  make obj  make build.

 Also check you don't have any bogus files in your checkout (cvs
 up -Pd -I \! -I obj -I CVS) and it's a good idea to clean /usr/obj
 if you're having problems.
 Hi, Stuart.

 I've tried your advice.
 did
 # cvs up -Pd -I \! -I obj -I CVS

Just a WAG, do you possible have a (or a few) file(s) with
a sticky Tag? If you are working off head of the CVS tree
use a -APd to clear out any possible Tags.

--patrick


 # rm -rf  /usr/obj/*
 # env make clean  env make obj  env make build

 and it again errors on me:

 ./tls.h - ./tls.ph
 ./siphash.h - ./siphash.ph
 *** Error 1 in gnu/usr.bin/perl (Makefile.bsd-wrapper:112 'install')
 *** Error 1 in gnu/usr.bin (bsd.subdir.mk:48 'realinstall')
 *** Error 1 in gnu (bsd.subdir.mk:48 'realinstall')
 *** Error 1 in . (bsd.subdir.mk:48 'realinstall')
 *** Error 1 in /usr/src (Makefile:82 'build')
 # make clean  make obj  make build

 what could be the reason?
 --
 With best regards,
Gregory Edigarov

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

On 3/4/15, Martin Pieuchot mpieuc...@nolizard.org wrote:
 On 04/03/15(Wed) 10:49, patrick keshishian wrote:
 On 3/4/15, Martin Pieuchot mpieuc...@nolizard.org wrote:
  Hello again
 
  On 27/02/15(Fri) 11:40, patrick keshishian wrote:
 
  I can confirm this change alone causes no adverse, observable
  change on my x120e's touchpad.
 
  Could you guys confirm that the last fix from Ulf also fixes your
  issue?
 
  https://marc.info/?l=openbsd-techm=142513927519879w=2

 Hi,

 Apologies. I thought that patch was sent for comment
 by experts (there was a lot of questions/second guesses
 accompanying the referenced post/patch).

 Testing is always welcome!

 Is this to be tested on its own or in conjunction with
 sys/dev/wscons/wsmouse.c patch from this thread?

 On its own :)

This patch seems to work fine. I don't see the issue I
reported.

Thank you,
--patrick


 Thanks,
 Martin

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

On 3/4/15, Martin Pieuchot mpieuc...@nolizard.org wrote:
 Hello again

 On 27/02/15(Fri) 11:40, patrick keshishian wrote:

 I can confirm this change alone causes no adverse, observable
 change on my x120e's touchpad.

 Could you guys confirm that the last fix from Ulf also fixes your issue?

 https://marc.info/?l=openbsd-techm=142513927519879w=2

Hi,

Apologies. I thought that patch was sent for comment
by experts (there was a lot of questions/second guesses
accompanying the referenced post/patch).

Is this to be tested on its own or in conjunction with
sys/dev/wscons/wsmouse.c patch from this thread?

--patrick

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

Hi,

On 2/26/15, Ulf Brosziewski ulf.brosziew...@t-online.de wrote:
 On 02/27/2015 03:31 AM, Ulf Brosziewski wrote:
 ...
 It might be that the following patch to wsmouse.c solves the problem
 with the new version of wsconscomm. Tests would be welcome (I could
 only verify that the patch does no harm to other touchpad types, i.e.,
 Elantech-v4 and Alps Glidepoint).
[...]

 Sorry, the change was in the wrong place and would only do a half of
 the work. It should look like:

 Index: wsmouse.c
 ===
 RCS file: /cvs/src/sys/dev/wscons/wsmouse.c,v
 retrieving revision 1.26
 diff -u -p -r1.26 wsmouse.c
 --- wsmouse.c 27 Oct 2014 13:55:05 -  1.26
 +++ wsmouse.c 27 Feb 2015 02:50:06 -
 @@ -433,6 +433,9 @@ wsmouse_input(struct device *wsmousedev,
   }
   }

 + if (sc-sc_z == 0)
 + sc-sc_w = INVALID_W;
 +
   mb = sc-sc_mb;
   while ((d = mb ^ ub) != 0) {
   /*

I can confirm this change alone causes no adverse, observable
change on my x120e's touchpad.

With -r1.11 of xenocara/driver/xf86-input-synaptics/wsconscomm.c,
in combination with above patch, I no longer seem to notice the
issue for which this message thread was originated.

However, I would appreciate it if someone could enlighten me
as to what the Z and W axis refer.

Thanks,
--patrick

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

On 2/26/15, Ulf Brosziewski ulf.brosziew...@t-online.de wrote:
 On 02/26/2015 02:32 AM, patrick keshishian wrote:
 On 2/25/15, Ulf Brosziewskiulf.brosziew...@t-online.de  wrote:
 On 02/25/2015 11:53 PM, patrick keshishian wrote:
 Hi,

 On 2/25/15, joshua steinj...@openbsd.org   wrote:
 On Tue, 24 Feb 2015 at 12:32:10 -0800, patrick keshishian wrote:
 I'm noticing slight annoyance with recent update from 20141121
 snapshot to 20150217.

 My touchpad, while two-finger scrolling (up/down) sometimes ignores
 the scrolls. I have to lift my fingers and retry the gesture to
 initiate
 the scroll.

 There was a change to pms(4) (r1.57) but it should only affect
 elantech touchpads, so it's probably the r1.11 change to the
 synaptics xorg driver which affects all of them:

 http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/driver/xf86-input-synaptics/src/wsconscomm.c

 Can you try recompiling that driver with that last revision backed
 out and see if it fixes the problem?

 Thanks for the reply and hint.
 Took me a while longer as I made the mistake of rebuilding
 the entire xenocara.

 Indeed this revision seems to be the cause of the issue; at
 least I've not been able to run into the issue in the last 10
 minutes or so, whilst trying my best.

 Thanks to Henrik Friedrichsen for also confirming the issue
 and the fix.

 Cheers,
 --patrick



 Unfortunately that fix might reintroduce other problems, at least
 with other touchpads, and maybe even with yours. For example, if you
 start a scrolling operation by making two touches at the same time,
 I would expect that it begins with a jump. Would you mind check that?
 I can't make any tests myself, there is no synaptics touchpad around
 here.

 Hi,

 I'm not sure what you mean exactly by making two touches
 at the same time.

 The way I initiate a scroll is by placing two fingers (typically my
 index and middle fingers) on the touchpad and moving them
 up/down or left/right.

 It has never begun with any jump.

 The change which prompted this thread, was absolutely annoying.
 e.g., While reading a PDF document. I'd have to remove my fingers
 and touch the touchpad again, very frequently, in order to continue
 scrolling. Where as before (and now with the revision rollback) I can
 completely concentrate on reading the document.

 Best,
 --patrick



 Hi Patrick,

 thanks for the reply. What I meant was this: There can be a (possibly
 small) time interval between the contacts, or this interval can be
 (nearly) zero. In the first case, the finger count of the driver
 should change from 0 to 1, then from 1 to 2. If the hardware is not
 extremely accurate it may change directly from 0 to 2 in the second
 case. If the hardware *is* very accurate, it may be difficult to produce
 these double contacts. The test I had in mind could look like this: You
 move the cursor over a scrollable document, lift the moving finger, then
 make a double contact on a position that has a noticeable (vertical)
 distance from the previous contact point. If the document moves/jumps
 when the double contact is made, there's something wrong. This can
 happen when the driver doesn't count properly.

Hello and thanks for the clarification of your test-case.
I have been attempting it this morning, but not able to
see any jumps. It seems/feels pretty solid.

Sorry,
--patrick


 Regards,
 Ulf

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

On 2/26/15, Ulf Brosziewski ulf.brosziew...@t-online.de wrote:
 On 02/26/2015 06:06 PM, patrick keshishian wrote:
 On 2/26/15, Ulf Brosziewskiulf.brosziew...@t-online.de  wrote:
 On 02/26/2015 02:32 AM, patrick keshishian wrote:
 On 2/25/15, Ulf Brosziewskiulf.brosziew...@t-online.de   wrote:
 ...

 Hi Patrick,

 thanks for the reply. What I meant was this: There can be a (possibly
 small) time interval between the contacts, or this interval can be
 (nearly) zero. In the first case, the finger count of the driver
 should change from 0 to 1, then from 1 to 2. If the hardware is not
 extremely accurate it may change directly from 0 to 2 in the second
 case. If the hardware *is* very accurate, it may be difficult to produce
 these double contacts. The test I had in mind could look like this:
 You
 move the cursor over a scrollable document, lift the moving finger, then
 make a double contact on a position that has a noticeable (vertical)
 distance from the previous contact point. If the document moves/jumps
 when the double contact is made, there's something wrong. This can
 happen when the driver doesn't count properly.

 Hello and thanks for the clarification of your test-case.
 I have been attempting it this morning, but not able to
 see any jumps. It seems/feels pretty solid.

 Sorry,
 --patrick


 Regards,
 Ulf


 Hi Patrick, may I ask you a last question? Does tapping work with the
 reverted version?

Hi Ulf,

Yes. Tapping works. Double tap to select words, tap + tap-
hold-and-drag to select sequence of characters or drag/move
windows, etc. Two finger tap to bring up contextual menus ..

I've really not had any issues with my touchpad. In fact, I was
pleasantly surprised when it just worked out-of-the-box, so to
speak.

HTH,
--patrick

man pages ending in .1x from ports

[patrick keshishian]

Just noticed this, I imagine this may be known already, but
here it is just in case it isn't.

$ man xsel
man: /usr/local/man/man1/xsel.1: ERROR: No such file or directory

$ pkg_info -L xsel
Information for inst:xsel-1.2.0p1

Files:
/usr/local/bin/xsel
/usr/local/man/man1/xsel.1x

$ ls -l /usr/local/man/man1/xsel.1x
-r--r--r--  1 root  bin  4406 Feb 17 21:56 /usr/local/man/man1/xsel.1x

$ file /usr/local/man/man1/xsel.1x
/usr/local/man/man1/xsel.1x: ASCII English text

This used to work fine with 20141121 snapshot, last one
before 20150217 upgrade.

I'm guessing requesting following x11/ ports' man pages
will behave (fail?) similar fashion:

x11/aewm
x11/afterstep
x11/qvwm
x11/sisctrl
x11/uwm

--patrick

$ sysctl kern.version
kern.version=OpenBSD 5.7-beta (GENERIC.MP) #856: Tue Feb 17 12:43:12 MST 2015
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

full dmesg: http://marc.info/?l=openbsd-miscm=142491406821636w=2

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

 detached
uvideo0 detached
uhub3 detached
uhub0 at usb2 ATI OHCI root hub rev 1.00/1.00 addr 1
uhub1 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1
uhub2 at usb3 ATI OHCI root hub rev 1.00/1.00 addr 1
uhub3 at usb1 ATI EHCI root hub rev 2.00/1.00 addr 1
umass0 at uhub3 port 2 configuration 1 interface 0 Generic
USB2.0-CRW rev 2.00/58.88 addr 2
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
sd1 at scsibus2 targ 1 lun 0: Generic-, Multi-Card, 1.00 SCSI0
0/direct removable serial.0bda015811417340
uvideo0 at uhub3 port 5 configuration 1 interface 0 Image Processor
Integrated Camera rev 2.00/0.29 addr 3
video0 at uvideo0
uhidev0 at uhub0 port 2 configuration 1 interface 0 Microsoft
Microsoft 3-Button Mouse with IntelliEye(TM) rev 1.10/3.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 3 buttons, Z dir
wsmouse2 at ums0 mux 0


On 2/25/15, Martin Pieuchot mpieuc...@nolizard.org wrote:
 On 25/02/15(Wed) 14:53, patrick keshishian wrote:
 Hi,

 On 2/25/15, joshua stein j...@openbsd.org wrote:
  On Tue, 24 Feb 2015 at 12:32:10 -0800, patrick keshishian wrote:
  I'm noticing slight annoyance with recent update from 20141121
  snapshot to 20150217.
 
  My touchpad, while two-finger scrolling (up/down) sometimes ignores
  the scrolls. I have to lift my fingers and retry the gesture to
  initiate
  the scroll.
 
  There was a change to pms(4) (r1.57) but it should only affect
  elantech touchpads, so it's probably the r1.11 change to the
  synaptics xorg driver which affects all of them:
 
  http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/driver/xf86-input-synaptics/src/wsconscomm.c
 
  Can you try recompiling that driver with that last revision backed
  out and see if it fixes the problem?

 Thanks for the reply and hint.
 Took me a while longer as I made the mistake of rebuilding
 the entire xenocara.

 Indeed this revision seems to be the cause of the issue; at
 least I've not been able to run into the issue in the last 10
 minutes or so, whilst trying my best.

 Thanks to Henrik Friedrichsen for also confirming the issue
 and the fix.

 Do you guys mind sharing a dmesg?  On which touchpad/firmware version do
 you see this regression?

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

Hi,

On 2/25/15, joshua stein j...@openbsd.org wrote:
 On Tue, 24 Feb 2015 at 12:32:10 -0800, patrick keshishian wrote:
 I'm noticing slight annoyance with recent update from 20141121
 snapshot to 20150217.

 My touchpad, while two-finger scrolling (up/down) sometimes ignores
 the scrolls. I have to lift my fingers and retry the gesture to initiate
 the scroll.

 There was a change to pms(4) (r1.57) but it should only affect
 elantech touchpads, so it's probably the r1.11 change to the
 synaptics xorg driver which affects all of them:

 http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/driver/xf86-input-synaptics/src/wsconscomm.c

 Can you try recompiling that driver with that last revision backed
 out and see if it fixes the problem?

Thanks for the reply and hint.
Took me a while longer as I made the mistake of rebuilding
the entire xenocara.

Indeed this revision seems to be the cause of the issue; at
least I've not been able to run into the issue in the last 10
minutes or so, whilst trying my best.

Thanks to Henrik Friedrichsen for also confirming the issue
and the fix.

Cheers,
--patrick

Re: touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

On 2/25/15, Ulf Brosziewski ulf.brosziew...@t-online.de wrote:
 On 02/25/2015 11:53 PM, patrick keshishian wrote:
 Hi,

 On 2/25/15, joshua steinj...@openbsd.org  wrote:
 On Tue, 24 Feb 2015 at 12:32:10 -0800, patrick keshishian wrote:
 I'm noticing slight annoyance with recent update from 20141121
 snapshot to 20150217.

 My touchpad, while two-finger scrolling (up/down) sometimes ignores
 the scrolls. I have to lift my fingers and retry the gesture to
 initiate
 the scroll.

 There was a change to pms(4) (r1.57) but it should only affect
 elantech touchpads, so it's probably the r1.11 change to the
 synaptics xorg driver which affects all of them:

 http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/driver/xf86-input-synaptics/src/wsconscomm.c

 Can you try recompiling that driver with that last revision backed
 out and see if it fixes the problem?

 Thanks for the reply and hint.
 Took me a while longer as I made the mistake of rebuilding
 the entire xenocara.

 Indeed this revision seems to be the cause of the issue; at
 least I've not been able to run into the issue in the last 10
 minutes or so, whilst trying my best.

 Thanks to Henrik Friedrichsen for also confirming the issue
 and the fix.

 Cheers,
 --patrick



 Unfortunately that fix might reintroduce other problems, at least
 with other touchpads, and maybe even with yours. For example, if you
 start a scrolling operation by making two touches at the same time,
 I would expect that it begins with a jump. Would you mind check that?
 I can't make any tests myself, there is no synaptics touchpad around
 here.

Hi,

I'm not sure what you mean exactly by making two touches
at the same time.

The way I initiate a scroll is by placing two fingers (typically my
index and middle fingers) on the touchpad and moving them
up/down or left/right.

It has never begun with any jump.

The change which prompted this thread, was absolutely annoying.
e.g., While reading a PDF document. I'd have to remove my fingers
and touch the touchpad again, very frequently, in order to continue
scrolling. Where as before (and now with the revision rollback) I can
completely concentrate on reading the document.

Best,
--patrick

touchpad slight regression (snap: 20141121-20150217)

[patrick keshishian]

Hi,

I'm noticing slight annoyance with recent update from 20141121
snapshot to 20150217.

My touchpad, while two-finger scrolling (up/down) sometimes ignores
the scrolls. I have to lift my fingers and retry the gesture to initiate
the scroll.

Full Xorg.0.log at the end, but here is a diff with last snapshot's one
where I did not have this issue.

two notes:
1. Only thing different w/respect to my configuration is, I removed
   sections I used to have for usbtablet. b/c after a sleep/wake cycle
   the usbtablet would not reattach to X (requiring an X restart).
2. two entries seen in this diff with Applying InputClass ... are marked
with (**)' from config file. This is a lie. my current xorg.conf follows.

--- /tmp/a  Tue Feb 24 12:12:49 2015
+++ /tmp/b  Tue Feb 24 12:12:32 2015
@@ -6,12 +6,12 @@
 [  ]   linear framebuffer access unavailable
 [  ] (--) Using wscons driver on /dev/ttyC4 in pcvt
compatibility mode (version 3.32)
 [  ]
-[  ]er 1.16.1
-[  ]: 2014-09-21
+[  ]er 1.16.4
+[  ]: 2014-12-20
 [  ] X Protocol Version 11, Revision 0
-[  ] Build Operating System: OpenBSD 5.6 amd64
-[  ] Current Operating System: OpenBSD noir.boxsoft.com 5.6
GENERIC.MP#592 amd64
-[  ] Build Date: 18 November 2014  01:12:21AM
+[  ] Build Operating System: OpenBSD 5.7 amd64
+[  ] Current Operating System: OpenBSD noir.boxsoft.com 5.7
GENERIC.MP#856 amd64
+[  ] Build Date: 17 February 2015  12:12:30PM
 [  ]
 [  ] Current version of pixman: 0.32.6
 [  ]   Before reporting problems, check http://wiki.x.org
@@ -19,17 +19,15 @@
 [  ] Markers: (--) probed, (**) from config file, (==) default setting,
 [  ]ommand line, (!!) notice, (II) informational,
 [  ]g, (EE) error, (NI) not implemented, (??) unknown.
-[  ] (==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 23
14:10:20 2014
+[  ] (==) Log file: /var/log/Xorg.0.log, Time: Thu Feb 19
11:03:10 2015
 [  ] (==) Using config file: /etc/X11/xorg.conf
 [  ] (==) Using system config directory
/usr/X11R6/share/X11/xorg.conf.d
-[  ] (==) ServerLayout Layout0
+[  ] (==) No Layout section.  Using the first Screen section.
 [  ] (==) No screen section available. Using defaults.
 [  ] (**) |--Screen Default Screen Section (0)
 [  ] (**) |   |--Monitor default monitor
 [  ] (==) No monitor specified for screen Default Screen Section.
 [  ]ault monitor configuration.
-[  ] (**) |--Input Device w_stylus
-[  ] (**) Option AllowMouseOpenFail True
 [  ] (==) Disabling SIGIO handlers for input devices
 [  ] (==) Automatically adding devices
 [  ] (==) Automatically enabling devices
@@ -48,7 +46,7 @@
 [  ] (==) ModulePath set to /usr/X11R6/lib/modules
 [  ] (II) The server relies on wscons to provide the list of
input devices.
 [  ]es become available, reconfigure wscons or disable AutoAddDevices.
-[  ] (II) Loader magic: 0x1adf0cd0a040
+[  ] (II) Loader magic: 0xd9c9eb0b6e0
 [  ] (II) Module ABI versions:
 [  ]   X.Org ANSI C Emulation: 0.4
 [  ]   X.Org Video Driver: 18.0
@@ -58,7 +56,7 @@
 [  ] (II) LoadModule: glx
 [  ] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
 [  ] (II) Module glx: vendor=X.Org Foundation
-[  ]   compiled for 1.16.1, module version = 1.0.0
+[  ]   compiled for 1.16.4, module version = 1.0.0
 [  ]   ABI class: X.Org Server Extension, version 8.0
 [  ] (==) AIGLX enabled
 [  ] (==) Matched ati as autoconfigured driver 0
@@ -67,28 +65,21 @@
 [  ] (II) LoadModule: ati
 [  ] (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so
 [  ] (II) Module ati: vendor=X.Org Foundation
-[  ]   compiled for 1.16.1, module version = 7.3.0
+[  ]   compiled for 1.16.4, module version = 7.3.0
 [  ]   Module class: X.Org Video Driver
 [  ]   ABI class: X.Org Video Driver, version 18.0
 [  ] (II) LoadModule: radeon
 [  ] (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.so
 [  ] (II) Module radeon: vendor=X.Org Foundation
-[  ]   compiled for 1.16.1, module version = 7.3.0
+[  ]   compiled for 1.16.4, module version = 7.3.0
 [  ]   Module class: X.Org Video Driver
 [  ]   ABI class: X.Org Video Driver, version 18.0
 [  ] (II) LoadModule: vesa
 [  ] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so
 [  ] (II) Module vesa: vendor=X.Org Foundation
-[  ]   compiled for 1.16.1, module version = 2.3.3
+[  ]   compiled for 1.16.4, module version = 2.3.3
 [  ]   Module class: X.Org Video Driver
 [  ]   ABI class: X.Org Video Driver, version 18.0
-[  ] (II) LoadModule: usbtablet
-[

netstat output shuffles (new feature?)

[patrick keshishian]

Hi,

Just installed 2015-FEB-17 amd64 snapshot[1] and at first I thought
the order of daemon start-up had changed, and for some strange
reason sshd was started after smtpd, and X?

$ netstat -afinet
Active Internet connections (including servers)
Proto   Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp  0  0  *.ssh  *.*LISTEN
tcp  0  0  *.6000 *.*LISTEN
tcp  0  0  localhost.smtp *.*LISTEN
Active Internet connections (including servers)
Proto   Recv-Q Send-Q  Local Address  Foreign Address(state)
udp  0  0  build.3815 otherbox.ntp
udp  0  0  *.syslog   *.*


Quick look in /etc/rc didn't confirm this.

*shrug*

about 5 minutes later:

$ netstat -afinet
Active Internet connections (including servers)
Proto   Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp  0  0  *.6000 *.*LISTEN
tcp  0  0  localhost.smtp *.*LISTEN
tcp  0  0  *.ssh  *.*LISTEN
Active Internet connections (including servers)
Proto   Recv-Q Send-Q  Local Address  Foreign Address(state)
udp  0  0  build.3815 otherbox.ntp
udp  0  0  *.syslog   *.*


This is what I'm used to seeing. The first processes (based
on start-up/socket bind time) at the bottom of the list (stack)
and the newest at the top.

I figured not to bother misc@ about this, but the order
changed again next time I looked at netstat.

Is this caused by some change in the kernel or netstat?

Thanks,
--patrick



[1] sysctl kern.version
kern.version=OpenBSD 5.7-beta (GENERIC) #801: Tue Feb 17 12:38:11 MST 2015
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

Re: netstat output shuffles (new feature?)

[patrick keshishian]

On 2/18/15, patrick keshishian pkesh...@gmail.com wrote:
 Hi,

 Just installed 2015-FEB-17 amd64 snapshot[1] and at first I thought
 the order of daemon start-up had changed, and for some strange
 reason sshd was started after smtpd, and X?

 $ netstat -afinet
 Active Internet connections (including servers)
 Proto   Recv-Q Send-Q  Local Address  Foreign Address
 (state)
 tcp  0  0  *.ssh  *.*LISTEN
 tcp  0  0  *.6000 *.*LISTEN
 tcp  0  0  localhost.smtp *.*LISTEN
 Active Internet connections (including servers)
 Proto   Recv-Q Send-Q  Local Address  Foreign Address
 (state)
 udp  0  0  build.3815 otherbox.ntp
 udp  0  0  *.syslog   *.*


 Quick look in /etc/rc didn't confirm this.

 *shrug*

 about 5 minutes later:

 $ netstat -afinet
 Active Internet connections (including servers)
 Proto   Recv-Q Send-Q  Local Address  Foreign Address
 (state)
 tcp  0  0  *.6000 *.*LISTEN
 tcp  0  0  localhost.smtp *.*LISTEN
 tcp  0  0  *.ssh  *.*LISTEN
 Active Internet connections (including servers)
 Proto   Recv-Q Send-Q  Local Address  Foreign Address
 (state)
 udp  0  0  build.3815 otherbox.ntp
 udp  0  0  *.syslog   *.*


 This is what I'm used to seeing. The first processes (based
 on start-up/socket bind time) at the bottom of the list (stack)
 and the newest at the top.

 I figured not to bother misc@ about this, but the order
 changed again next time I looked at netstat.

 Is this caused by some change in the kernel or netstat?

it is due to new qsort code in netstat.

... so never mind.

I see another difference testing this with nc. but
that would need another topic.

'nite.
--patrick




 Thanks,
 --patrick



 [1] sysctl kern.version
 kern.version=OpenBSD 5.7-beta (GENERIC) #801: Tue Feb 17 12:38:11 MST 2015
 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

macppc install56.iso - CD issues

[patrick keshishian]

Hi,

I must be doing something wrong here and need some hints
to figure out what.

My attempts to burn macppc install56.iso to a CD seems to
produce un-bootable discs. I'm using cdrecord(1) to perform
the burns.

At the Open Firmware prompt I issue:

0  boot cd:,ofwboot /5.6/macppc/bsd.rd

and that results in:

DISK-LABEL: read of block0 failed
ATAPI-DISK: open of DISK-LABEL failed can't OPEN: cd:,ofwboot
Can't open device or file
 ok
0 

I went through four different burn attempts; one with Dec
7th snapshot. And three right now with Dec 8th one.

I tested with official 5.6 CD and that CD boots just fine.

This is how the image was burned to disc:

# cdrecord -v dev=/dev/rcd0c install56.iso
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent default
s.
Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.6) Copyright (C) 1995-2
[...]
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
Sending CUE sheet...
cdrecord: WARNING: Drive returns wrong startsec (0) using -150
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01:  218 of  218 MB written (fifo 100%) [buf  99%]  33.1x.
Track 01: Total bytes read/written: 228696064/228696064 (111668 sectors).
Writing  time:   75.670s
Average write speed  22.3x.
Min drive buffer fill was 97%
Fixating...
Fixating time:3.591s
cdrecord: fifo had 3723 puts and 3723 gets.
cdrecord: fifo was 0 times empty and 1843 times full, min fill was 95%.
# echo $?
0

Note the WARNING.

Also note that burning an amd64 image works just fine
(with same WARNING during cdrecord phase).

On a related note, how can base tools (cdio(1)?) be used
instead of cdrecord(1) (from ports) to burn these images
to disc?

Thanks in advance,
--patrick

Re: macppc install56.iso - CD issues

[patrick keshishian]

Hi Fred,

On 12/9/14, Fred open...@crowsons.com wrote:
 On 12/09/14 08:10, patrick keshishian wrote:
 Hi,

 I must be doing something wrong here and need some hints
 to figure out what.

 My attempts to burn macppc install56.iso to a CD seems to
 produce un-bootable discs. I'm using cdrecord(1) to perform
 the burns.

 At the Open Firmware prompt I issue:

 0  boot cd:,ofwboot /5.6/macppc/bsd.rd

 and that results in:

 DISK-LABEL: read of block0 failed
 ATAPI-DISK: open of DISK-LABEL failed can't OPEN: cd:,ofwboot
 Can't open device or file
   ok
 0 

 I went through four different burn attempts; one with Dec
 7th snapshot. And three right now with Dec 8th one.

 I tested with official 5.6 CD and that CD boots just fine.

 This is how the image was burned to disc:

 # cdrecord -v dev=/dev/rcd0c install56.iso
 cdrecord: No write mode specified.
 cdrecord: Assuming -sao mode.
 cdrecord: If your drive does not accept -sao, try -tao.
 cdrecord: Future versions of cdrecord may have different drive dependent
 default
 s.
 Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.6) Copyright (C)
 1995-2
 [...]
 BURN-Free is ON.
 Turning BURN-Free off
 Performing OPC...
 Sending CUE sheet...
 cdrecord: WARNING: Drive returns wrong startsec (0) using -150
 Writing pregap for track 1 at -150
 Starting new track at sector: 0
 Track 01:  218 of  218 MB written (fifo 100%) [buf  99%]  33.1x.
 Track 01: Total bytes read/written: 228696064/228696064 (111668 sectors).
 Writing  time:   75.670s
 Average write speed  22.3x.
 Min drive buffer fill was 97%
 Fixating...
 Fixating time:3.591s
 cdrecord: fifo had 3723 puts and 3723 gets.
 cdrecord: fifo was 0 times empty and 1843 times full, min fill was 95%.
 # echo $?
 0

 Note the WARNING.

 Also note that burning an amd64 image works just fine
 (with same WARNING during cdrecord phase).

 On a related note, how can base tools (cdio(1)?) be used
 instead of cdrecord(1) (from ports) to burn these images
 to disc?

 Thanks in advance,
 --patrick


 Hi,

 What happens when you hold the 'c' key during reboot?

I get gray screen with folder and flashing ?.

 If you mount the disks under a working system is ofwboot in the / ?

Yes sir.

$ sudo mount /dev/cd0a /mnt/cd
$ ls /mnt/cd
5.6/ ofwboot

--patrick


 hth

 Fred

Re: macppc install56.iso - CD issues

[patrick keshishian]

On 12/9/14, Maurice McCarthy m...@mythic-beasts.com wrote:
 Check out http://www.openbsd.org/faq/faq4.html#MkCD-ROM
 and faq13.

 It reads:

 # cdio tao cd56.iso

Thanks Maurice and Dennis for point me to the FAQ on
cdio(1) usage.

Richard Toohey was first to respond in private with the
hint as well.

I didn't want to muddy the unbootable iso image issue
with cdio(1) usage, so I didn't mention that I had tried
the following based on reading cdio(1) man-page:

$ sudo cdio -v -f /dev/rcd0c  tao -d install56.iso
Features:
0x Profile List (60 bytes of data)
  * 0x0009 Write once Compact Disc [Current Profile]
0x0001 Core (8 bytes of data)
0x0002 Morphing (4 bytes of data)
0x0003 Removable Medium (4 bytes of data)
0x0021 Incremental Streaming Writable (8 bytes of data)
0x002d CD Track at Once (TAO) (4 bytes of data)
0x002e CD Mastering (Session at Once) (4 bytes of data)
0x0100 Power Management
0x0105 Timeout (4 bytes of data)
0x0107 Real Time Streaming (4 bytes of data)
0x0108 Drive Serial Number (12 bytes of data)
0x010c Firmware Information (16 bytes of data)
cdio: mode select failed: 3

I just assumed I was missing something subtle in its
usage or perhaps another needed tool. I should have
verified with the FAQ indeed.

--patrick




 Regards

Re: macppc install56.iso - CD issues

[patrick keshishian]

On 12/9/14, Fred open...@crowsons.com wrote:
 On 12/09/14 19:07, patrick keshishian wrote:
 On 12/9/14, Fred open...@crowsons.com wrote:
 What happens when you hold the 'c' key during reboot?

 I get gray screen with folder and flashing ?.

 I have had that when I messed up an install (I dual boot my iBook) and
 ended up to use my Mac OS X disks to reformat the drive - with a bigger
 OpenBSD partition.

Not quite the situation with my macppc, as it is not
dual booting and it is dealing with CD media not HDD.

I believe the issue has to do with the newly burned CD
or the source install56.iso image.

As I pointed out the official 5.6 CD boots just fine. Later

I also don't think it is the CD-R media, as I verified I can
burn an amd64 image (install56.iso file) and it boots
fine (on an amd64 hw of course).

Best,
--patrick

Re: macppc install56.iso - CD issues

[patrick keshishian]

On 12/9/14, Fred Crowson f...@crowsons.net wrote:
 On 12/09/14 20:51, patrick keshishian wrote:
 On 12/9/14, Fred open...@crowsons.com wrote:
 On 12/09/14 19:07, patrick keshishian wrote:
 On 12/9/14, Fred open...@crowsons.com wrote:
 What happens when you hold the 'c' key during reboot?

 I get gray screen with folder and flashing ?.

 I have had that when I messed up an install (I dual boot my iBook) and
 ended up to use my Mac OS X disks to reformat the drive - with a bigger
 OpenBSD partition.

 Not quite the situation with my macppc, as it is not
 dual booting and it is dealing with CD media not HDD.

 I believe the issue has to do with the newly burned CD
 or the source install56.iso image.

 As I pointed out the official 5.6 CD boots just fine. Later

 I also don't think it is the CD-R media, as I verified I can
 burn an amd64 image (install56.iso file) and it boots
 fine (on an amd64 hw of course).

 Best,
 --patrick


Hi Fred,

 Using:

 -rw-r--r--1 ftp  ftp  228696064 Dec 09 01:32 install56.iso

 from mirror.ox.ac.uk - I have successfully upgraded by burning a cdrom:

Thanks for *this* info. I was hoping someone would
provide something like this.

That's the exact install56.iso I was using yesterday from
Colorado (US) mirror (IIRC):

$ cksum -a sha256 install56.iso
SHA256 (install56.iso) =
586ab0c9d30fba85c19e6c45071fc0dfbe78190bfaf89f244bfbebceeae611ff

$ strings 5.6/macppc/bsd* | grep -A1 ^OpenBSD\ 5.6-current
OpenBSD 5.6-current (GENERIC) #344: Mon Dec  8 17:57:34 MST 2014
dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC
OpenBSD 5.6-current (GENERIC.MP) #396: Mon Dec  8 18:14:39 MST 2014
dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC.MP
OpenBSD 5.6-current (RAMDISK) #344: Mon Dec  8 18:30:19 MST 2014
dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/RAMDISK


 ibook:fred ~ uname -a; dmesg|head
 OpenBSD ibook.crowsons.com 5.6 GENERIC#344 macppc
 [ using 551184 bytes of bsd ELF symbol table ]
 console out [ATY,Via_A]console in [keyboard] , using ADB
 using parent ATY,ViaParent:: memaddr 9800 size 800, : consaddr
 9c008000, : ioaddr 9002, size 2: width 1024 linebytes 1024
 height 768 depth 8
 Copyright (c) 1982, 1986, 1989, 1991, 1993
  The Regents of the University of California.  All rights reserved.
 Copyright (c) 1995-2014 OpenBSD. All rights reserved.
 http://www.OpenBSD.org

 OpenBSD 5.6-current (GENERIC) #344: Mon Dec  8 17:57:34 MST 2014
  dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC
 real mem = 536870912 (512MB)

 Could the issue be the CD drive in the box?

(this is on a Mac mini G4)
It is starting to look that way, except the fact it boots
with the official 5.6 CD :-)

Couple of experiments I just did:

Pulled my iBook G4 out and it seems OK with the burned
CD image.

so...

   macmini boot off of official 5.6 CD
   macmini drop down to shell
   macmini disklabel cd0

# /dev/rcd0c:
type: ATAPI
disk: OpenBSD5.6 CD 2
label: www.OpenBSD.org
duid: 
flags:
bytes/sector: 2048
sectors/track: 100
tracks/cylinder: 1
sectors/cylinder: 100
cylinders: 3255
total sectors: 325488
boundstart:0
boundend: 325488
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  a:   3254880  ISO9660
  c:   3254880  ISO9660

   macmini eject cd0

   - insert burnt CD (that doesn't boot)

   macmini disklabel cd0

# /dev/rcd0c:
type: ATAPI
disk: ATAPI CD-ROM
label: fictitious
duid: 
flags:
bytes/sector: 2048
sectors/track: 100
tracks/cylinder: 1
sectors/cylinder: 100
cylinders: 4001
total sectors: 40
boundstart: 0
boundend: 0
drivedata: 0

0 partitions:
#size   offset  fstype [fsize bsize  cpg]

   macmini eject cd0

   - insert it into iBook

   ibook disklabel cd0

# /dev/rcd0c:
type: ATAPI
disk: OpenBSD/macppc
label: 5.6 install CD
duid: 
flags:
bytes/sector: 2048
sectors/track: 100
tracks/cylinder: 1
sectors/cylinder: 100
cylinders: 1117
total sectors: 111664
boundstart: 0
boundend: 111664
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  a:   1116640  ISO9660
  c:   1116640  ISO9660


I don't understand this. The Mac mini isn't seeing the
burnt media. It has in the past, as I have/had a May 4th
2014 snapshot on it.

Thanks for persisting Fred.

If anyone has any ideas ...

--patrick

Re: missing packages for SPARC

[patrick keshishian]

On 12/3/14, Christian Weisgerber na...@mips.inka.de wrote:
 On 2014-12-02, Riccardo Mottola riccardo.mott...@libero.it wrote:

 I was pkg_add'ing some essential packages on a freshly installed SPARC
 machine. I noticed that several packages are missing. I thought it was
 the mirror, but they are missing on the master ftp too.
 I know that some packages might not build on sparc or do not have sense
 on that platform, however I was looking for pretty general stuff:
 libxmsl, libxslt or subversion.

 They didn't build.  I can't tell whether that's due to the package
 building process (the sparc build machines are very unstable) or
 problems with the ports themselves.  Peter Hessler may be able to
 comment.

 Unfortunately, that's the usual course when an architecture becomes
 less and less common.  Build failures pile up, compounded by slowness
 and general reliability problems, and the set of available packages
 keeps shrinking.

 Somebody needs to care.

 There is no magic bullet.  If, say, two hundred ports fail to build
 and take out thousands more for which they serve as dependencies,
 then the only way to fix this is for somebody to sit down and examine
 and fix the failing ports.  One by one.

 If nobody steps up to do this, then it won't happen.

 We keep having this tail of zombie architectures.  Long obsolete
 hardware, run by few people, with pitiful best effort package
 builds happening each release and with luck once between.  They
 slowly sink under the accumulating bitrot that nobody cares to fix,
 but at the same time people can't bring themselves to completely
 abandon those archs.  *shrug*

how do you guys deal with disk space with sparc machines?
NFS?

I will dust off my ss20 this weekend see if it powers up.

--patrick

Re: USB hub stopped working

[patrick keshishian]

Hi Martin,

On 11/25/14, Martin Pieuchot mpieuc...@nolizard.org wrote:
 Hello Patrick,

 On 24/11/14(Mon) 23:48, patrick keshishian wrote:
 Hi,

 I have this USB hub, which is connected to my desktop
 PC; it makes the USB ports accessible w/o need to crawl
 under the desk. I'll seldom need to transfer files (to/fro)
 with a USB stick, which I plug into one of the hub ports.

 I don't quite recall when it was last used. But with 2014-NOV-21
 snapshot it doesn't seem to work.

 OpenBSD 5.6-current (GENERIC) #563: Fri Nov 21 10:09:03 MST 2014
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

 Could you try a more recent snapshot?  This should already be fixed.
 Let me know if that's not the case.

Thanks for the quick reply. Unfortunately, same result with:

OpenBSD 5.6-current (GENERIC) #578: Tue Nov 25 05:55:06 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

--patrick


 Martin

Re: USB hub stopped working

[patrick keshishian]

On 11/25/14, Jack Woehr jwo...@softwoehr.com wrote:
 patrick keshishian wrote:
 Hi Martin,

 On 11/25/14, Martin Pieuchot mpieuc...@nolizard.org wrote:
 Hello Patrick,

 On 24/11/14(Mon) 23:48, patrick keshishian wrote:
 Hi,

 I have this USB hub, which is connected to my desktop
 PC;

 External powered? Is it plugged in? Excuse me for asking.

It accepts external power, but it has not been necessary.
I tried with the wall wart plugged in with today's snapshot
just in case, but no difference.

--patrick




 --
 Jack Woehr   # There's too much emphasis on things
 Box 51, Golden CO 80402  #  like pawn structure in modern chess.
 http://www.softwoehr.com #  Checkmate ends the game. - N. Short

USB hub stopped working

[patrick keshishian]

Hi,

I have this USB hub, which is connected to my desktop
PC; it makes the USB ports accessible w/o need to crawl
under the desk. I'll seldom need to transfer files (to/fro)
with a USB stick, which I plug into one of the hub ports.

I don't quite recall when it was last used. But with 2014-NOV-21
snapshot it doesn't seem to work.

OpenBSD 5.6-current (GENERIC) #563: Fri Nov 21 10:09:03 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC

Plug it in, and it is detected:
uhub5 at uhub0 port 1 Genesys Logic USB2.0 Hub rev 2.00/7.02 addr 3


Plug in a USB mem-stick and nothing.
Unplug the USB stick from hub: nothing.
Unplug hub from computer's USB port:

uhub5 detached


Plug the USB stick directly into the same USB port on the
computer:

umass0 at uhub0 port 1 configuration 1 interface 0 Kingston DT 101
G2 rev 2.00/1.00 addr 3
umass0: using SCSI over Bulk-Only
scsibus4 at umass0: 2 targets, initiator 0
sd1 at scsibus4 targ 1 lun 0: Kingston, DT 101 G2, PMAP SCSI0
0/direct removable serial.09511EFEFA510245
sd1: 7640MB, 512 bytes/sector, 15646720 sectors


Note, that above is pulled from a Gateway LT31 netbook,
b/c of easier access, and b/c w/2014-SEP-09 snapshot, the
unplugging of the USB stick (or any other USB device) from
the USB hub would dump into ddb.

Unfortunately I couldn't gather much info from ddb as my
USB keyboard wouldn't respond, also, I wanted to try with
a newer -current, which doesn't seem to trigger the crash
(at least on this netbook it does not).

The crash, from memory, was in usb_allocmem().


Regardless, am I missing something with respect to the
hub not working, or did something break?

Plugging the USB hub into an OSX running MacBook Pro
seems to work as expected. USB mem-stick shows up
on desktop and files stored within can be accessed.

Thoughts?
--patrick


OpenBSD 5.6-current (GENERIC) #563: Fri Nov 21 10:09:03 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1861025792 (1774MB)
avail mem = 1807745024 (1724MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1010 (17 entries)
bios0: vendor Phoenix Technologies LTD version v1.3307 date 05/31/2010
bios0: Gateway LT31
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC
acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) Processor L110, 1197.20 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,SVM,EAPICSP,AMCR8,3DNOWP
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-8
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PB3_)
acpiprt2 at acpi0: bus -1 (PB4_)
acpiprt3 at acpi0: bus 3 (PB5_)
acpiprt4 at acpi0: bus 4 (PB6_)
acpiprt5 at acpi0: bus -1 (PB7_)
acpiprt6 at acpi0: bus 9 (P2P_)
acpiprt7 at acpi0: bus 1 (AGP_)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2
acpitz0 at acpi0: critical temperature is 100 degC
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 model UM09A41 serial 22962 type LION oem SONY
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCD_
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00
ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00
drm0 at radeondrm0
radeondrm0: msi
ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00: msi
pci2 at ppb1 bus 3
re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102EL
(0x2480), msi, address 00:23:8b:ef:ef:ef
rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1
ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00: msi
pci3 at ppb2 bus 4
ral0 at pci3 dev 0 function 0 Ralink RT3090 rev 0x00: apic 1 int 18,
address 00:24:1d:f4:3d:86
ral0: MAC/BBP RT3071 (rev 0x0213), RF RT3020 (MIMO 1T1R)
ahci0 at pci0 dev 18 function 0 ATI SB600 SATA rev 0x00: apic 1 int
22, AHCI 1.1
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: ATA, HGST HTS545050A7, GG2O SCSI3
0/direct fixed naa.5000cca71eed589f
sd0: 476940MB, 512 bytes/sector, 976773168 sectors
ohci0 at pci0 dev 19 function 0 ATI SB600 USB rev 0x00: apic 1 int
16, version 1.0, legacy support
ohci1 at pci0 dev 19 function 1 ATI SB600 USB rev 0x00: apic 1 int
17, 

Re: Temperature

[patrick keshishian]

Hi,

On 11/14/14, Etienne etienne.m...@magickarpet.org wrote:
 Hello list,

 I seem to have a little hardware related problem. I have been using a
 Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As
 soon as I upgraded to 5.5, and from quite early after kernel loading,
 the console started showing and repeating at regular intervals:

  acpitz0: critical temperature reached 93C, shutting down
  acpithinkpad0: Unknown event 0x6022

I don't believe I have ever seen the issue you describe with
my x120e.

hw.vendor=LENOVO
hw.version=ThinkPad X120e

hw.sensors.acpitz0.temp0=75.00 degC (zone temperature)
hw.sensors.acpithinkpad0.temp0=75.00 degC
hw.sensors.acpithinkpad0.temp1=0.00 degC
hw.sensors.acpithinkpad0.temp2=75.00 degC
hw.sensors.acpithinkpad0.temp3=0.00 degC
hw.sensors.acpithinkpad0.temp4=0.00 degC
hw.sensors.acpithinkpad0.temp5=0.00 degC
hw.sensors.acpithinkpad0.temp6=27.00 degC
hw.sensors.acpithinkpad0.temp7=0.00 degC
hw.sensors.km0.temp0=75.88 degC

hw.sensors.acpithinkpad0.fan0=441 RPM


 (93C is just a typical value, I've seen any between 92 and 98). I
 usually have just the time to log in before the system logs me out and
 shuts down. This laptop normally runs at around 80°C, and I think the
 temperature reading in OpenBSD is correct, because I get similar
 warnings
 and temperature values when I reboot immediately into another OS.

That may be a hint that something may be wrong
with your cooling. Dust blockage, etc.


 Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as
 I restarted the system, the same situation happened. Feeling
 adventurous,
 I tried to disable acpitz* during the boot process, which made the
 messages
 go away. The system ran just below 100°C (as reported by sysctl) for
 some time without any problem, until I didn't want to take the risk for
 any longer and shut it down manually. I also have an x100e from the same
 brand, quite similar even if older and slower, which does _NOT_ show the
 same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of
 both
 machines running 5.6.

 Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I
 should
 do to diagnose the problem any better?

As I say, I never have had this issue with x120e, which I've
been using for over 3 years with OpenBSD, mainly following
snapshots.

Running older snapshot atm:
$ sysctl kern.version
kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep  9 00:28:20 MDT 2014
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

I have a Gateway LT31 (?) that used to have similar issue as
you describe. After first cold boot, it would immediately
shutdown because of temperature warning. Next boot, it
would be fine.

However, since the last snapshot I put on it, from Sep. It
hasn't exhibited this behavior. Then again, the Gateway isn't
used much; so it could be that I've been lucky.

--patrick


 Cheers!

 --
 Étienne
 OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug  8 00:20:21 MDT 2014
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 real mem = 1861025792 (1774MB)
 avail mem = 1802760192 (1719MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries)
 bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010
 bios0: LENOVO 35089CU
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC
 acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3)
 P2P_(S5) LID_(S3)
 acpitimer0 at acpi0: 3579545 Hz, 32 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz
 cpu0:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB
 64b/line 16-way L2 cache
 cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
 cpu0: apic clock running at 199MHz
 cpu1 at mainbus0: apid 1 (application processor)
 cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz
 cpu1:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
 cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB
 64b/line 16-way L2 cache
 cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully
 associative
 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
 acpimcfg0 at acpi0 addr 0xe000, bus 0-3
 acpihpet0 at 

Re: Temperature

[patrick keshishian]

On 11/14/14, Mike Larkin mlar...@azathoth.net wrote:
 On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote:
 Hi,

 On 11/14/14, Etienne etienne.m...@magickarpet.org wrote:
  Hello list,
 
  I seem to have a little hardware related problem. I have been using a
  Lenovo x120e for some time, and OpenBSD ran nicely on it until April.
  As
  soon as I upgraded to 5.5, and from quite early after kernel loading,
  the console started showing and repeating at regular intervals:
 
   acpitz0: critical temperature reached 93C, shutting down
   acpithinkpad0: Unknown event 0x6022

 I don't believe I have ever seen the issue you describe with
 my x120e.

 hw.vendor=LENOVO
 hw.version=ThinkPad X120e

 hw.sensors.acpitz0.temp0=75.00 degC (zone temperature)
 hw.sensors.acpithinkpad0.temp0=75.00 degC
 hw.sensors.acpithinkpad0.temp1=0.00 degC
 hw.sensors.acpithinkpad0.temp2=75.00 degC
 hw.sensors.acpithinkpad0.temp3=0.00 degC
 hw.sensors.acpithinkpad0.temp4=0.00 degC
 hw.sensors.acpithinkpad0.temp5=0.00 degC
 hw.sensors.acpithinkpad0.temp6=27.00 degC
 hw.sensors.acpithinkpad0.temp7=0.00 degC
 hw.sensors.km0.temp0=75.88 degC

 hw.sensors.acpithinkpad0.fan0=441 RPM


  (93C is just a typical value, I've seen any between 92 and 98). I
  usually have just the time to log in before the system logs me out and
  shuts down. This laptop normally runs at around 80?C, and I think the
  temperature reading in OpenBSD is correct, because I get similar
  warnings
  and temperature values when I reboot immediately into another OS.

 That may be a hint that something may be wrong
 with your cooling. Dust blockage, etc.


  Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon
  as
  I restarted the system, the same situation happened. Feeling
  adventurous,
  I tried to disable acpitz* during the boot process, which made the
  messages
  go away. The system ran just below 100?C (as reported by sysctl) for
  some time without any problem, until I didn't want to take the risk for
  any longer and shut it down manually. I also have an x100e from the
  same
  brand, quite similar even if older and slower, which does _NOT_ show
  the
  same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of
  both
  machines running 5.6.
 
  Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I
  should
  do to diagnose the problem any better?

 As I say, I never have had this issue with x120e, which I've
 been using for over 3 years with OpenBSD, mainly following
 snapshots.

 Running older snapshot atm:
 $ sysctl kern.version
 kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep  9 00:28:20
 MDT 2014
 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

 I have a Gateway LT31 (?) that used to have similar issue as
 you describe. After first cold boot, it would immediately
 shutdown because of temperature warning. Next boot, it
 would be fine.

 However, since the last snapshot I put on it, from Sep. It
 hasn't exhibited this behavior. Then again, the Gateway isn't
 used much; so it could be that I've been lucky.


 I fixed the bogus shutdowns at the last hackathon (the ones where acpitz(4)
 would
 return temperatures in the 4000-5000K range).

Nice!

--patrick

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

[patrick keshishian]

Hi,

On 11/1/14, ropers rop...@gmail.com 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: uscom/ucom hardware question [was: OpenBSD 5.6 Released]

[patrick keshishian]

On 11/1/14, Christian Weisgerber na...@mips.inka.de wrote:
 On 2014-11-01, patrick keshishian pkesh...@gmail.com 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!

[patrick keshishian]

On 10/27/14, Michael W. Lucas mwlu...@michaelwlucas.com wrote:
 On Mon, Oct 27, 2014 at 09:04:48PM +0100, Peter N. M. Hansteen wrote:
 Michael W. Lucas mwlu...@michaelwlucas.com writes:

  BAH! You think you can steal my idea for supporting OpenBSD? I don't
  think it's that easy.
 
  MY auction raised $1145.
 
  There is no way that BoPF3 can POSSIBLY raise more than that!
 
  Consider the gauntlet thrown.

 :D

 After two days, the highest bit lists as US $493.88, which means

 a) that bid was likely entered in a non-USD currency (or
somebody has an odd sense of humor, I'm fine with both)

 b) we're on a pretty good trajectory for beating Mr. Lucas on
the fundraising front

 Humpf.

 It is just BARELY possible that Mr. Hansteen's work will raise more
 money than mine. If so, it will clearly be the result of nepotism,
 collusion, and intrigue.

 If this happens, I'll have to write another OpenBSD book. One that
 will raise EVEN MORE MONEY than this petty little BoPF3 auction.

 ==ml

 One again, the auction is at

 http://www.ebay.com/itm/The-Book-of-PF-3rd-ed-signed-by-the-author-First-Copy-signed-/321563281902?


Just to give this a bump: Interesting bid patterns by two
high bidders.

--patrick


 The blog post with the nice pictures is at
 http://bsdly.blogspot.no/2014/10/the-book-of-pf-3rd-edition-is-here.html

 And if your bid turns out not to be the successful one, please make
 the amount of your highest bid a direct donation to OpenBSD instead.

 Even if you wouldn't consider bidding, go on, head over to
 http://www.openbsd.org/orders.html or
 http://www.openbsd.org/donations.html
 and spend some money!

  - Peter

Re: OpenBSD 5.6 pre-orders in Germany possible

[patrick keshishian]

On 9/30/14, OpenBSD Europe m...@openbsdeurope.com wrote:
 Am 09/30/14 um 14:42 schrieb Martijn van Duren:

 The openbsdstore.com has opend.

 Guess what I just did? ;-)

 Cheers,
 STEFAN

 Yep.

 We had a some issues to start with.

 *Please*, if you order and hit a problem, email it to
 ord...@openbsdstore.com and not on these lists. It's *much* easier for us
 to deal with. They seem to have settled now.

I'm not sure where exactly to send these questions, so
i'm simply replying to all.

Two questions:
1. Is there no option for guest checkout? Must I be
forced to create an account?

2. Is the system smart enough so to understand, if
I were to purchase say, 10 CDs, but only wish to have
1 shipped, to properly calculate the shipping costs for
the single CD being shipped to me?

--patrick

Re: OpenBSD 5.6 pre-orders in Germany possible

[patrick keshishian]

On 9/30/14, OpenBSD Europe m...@openbsdeurope.com wrote:
 On 9/30/14, OpenBSD Europe m...@openbsdeurope.com wrote:
 Am 09/30/14 um 14:42 schrieb Martijn van Duren:

 The openbsdstore.com has opend.

 Guess what I just did? ;-)

 Cheers,
 STEFAN

 Yep.

 We had a some issues to start with.

 *Please*, if you order and hit a problem, email it to
 ord...@openbsdstore.com and not on these lists. It's *much* easier for
 us
 to deal with. They seem to have settled now.

 I'm not sure where exactly to send these questions, so
 i'm simply replying to all.

 Two questions:
 1. Is there no option for guest checkout? Must I be
 forced to create an account?

 No, just email us the order. You can pay via PayPal or over the phone with
 your CC.

Excellent!

 2. Is the system smart enough so to understand, if
 I were to purchase say, 10 CDs, but only wish to have
 1 shipped, to properly calculate the shipping costs for
 the single CD being shipped to me?

 Do you mean buy 10CDs but only ship one? and the rest being a donation? In
 that case, just buy one CD and donate the other 9 directly. The project
 does much better that way.

Yes. I've been doing that in the past with the old
ordering system. My understanding is that CD sales
help Theo directly; I believe that is still the case.

Cheers,
--patrick

X11 Focus Issue (2014-SEP-09 snapshot)

[patrick keshishian]

Hi,

Moving to 2014-SEP-09 snapshot (amd64)[1] I started to notice
something strange with my wm (blackbox) and window focus
events. I have it set to sloppy focus, where focus follows the
mouse, but doesn't leave the last visited window, until the mouse
enters a new window.

Every so often moving the mouse from one window to another,
the latter does not get focus.

I tried to capture the condition with xev. Here the first sequence
of EnterNotify - KeymapNotify - FocusIn - LeaveNotify -
FocusOut shows an expected behavior where mouse moved
from xterm to xev window, xev window:

1. EnterNotify (mouse moved from xterm - xev window)
2. FocusIn (xev window got focus)
3. bunch of MotionNotify events as mouse moved around
4. LeaveNotify (mouse left xev window)
5. FocusOut (mouse entered xterm window)

EnterNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741873, (13,137), root:(960,467),
mode NotifyNormal, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 35, synthetic NO, window 0x0,
keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741877, (13,137), root:(960,467),
state 0x0, is_hint 0, same_screen YES

FocusIn event, serial 35, synthetic NO, window 0x1c1,
mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 35, synthetic NO, window 0x0,
keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741889, (47,139), root:(994,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741903, (72,139), root:(1019,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741913, (82,139), root:(1029,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741926, (84,139), root:(1031,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82741937, (84,139), root:(1031,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742392, (79,139), root:(1026,469),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742404, (67,138), root:(1014,468),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742416, (41,134), root:(988,464),
state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742428, (10,133), root:(957,463),
state 0x0, is_hint 0, same_screen YES

LeaveNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742433, (-22,131), root:(925,461),
mode NotifyNormal, detail NotifyAncestor, same_screen YES,
focus YES, state 0

FocusOut event, serial 35, synthetic NO, window 0x1c1,
mode NotifyNormal, detail NotifyNonlinear


This next sequence shows the problem:

1. EnterNotify (mouse moved from xterm - xev window)
2. FocusIn (xev window got focus - briefly?)
3. FocusOut (mouse still in xev window, but window w/o focus)
XXX What happened here?
4. bunch of MotionNotify events as mouse moved around
5. LeaveNotify (mouse left xev window)

Notice no FocusOut event at the end of the sequence. Why
did the FocusOut event happen early? What causes this?


EnterNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742834, (23,139), root:(970,469),
mode NotifyNormal, detail NotifyAncestor, same_screen YES,
focus NO, state 0

KeymapNotify event, serial 35, synthetic NO, window 0x0,
keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

MotionNotify event, serial 35, synthetic NO, window 0x1c1,
root 0x2b8, subw 0x0, time 82742837, (23,139), root:(970,469),
state 0x0, is_hint 0, same_screen YES

FocusIn event, serial 35, synthetic NO, window 0x1c1,
mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 35, synthetic NO, window 0x0,
keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

FocusOut event, serial 35, synthetic NO, 

Re: X11 Focus Issue (2014-SEP-09 snapshot)

[patrick keshishian]

Visual aid demonstraiting the issue described here:

http://youtu.be/gl49UBVOUog

--patrick

On 9/14/14, patrick keshishian pkesh...@gmail.com wrote:
 Hi,

 Moving to 2014-SEP-09 snapshot (amd64)[1] I started to notice
 something strange with my wm (blackbox) and window focus
 events. I have it set to sloppy focus, where focus follows the
 mouse, but doesn't leave the last visited window, until the mouse
 enters a new window.

 Every so often moving the mouse from one window to another,
 the latter does not get focus.

 I tried to capture the condition with xev. Here the first sequence
 of EnterNotify - KeymapNotify - FocusIn - LeaveNotify -
 FocusOut shows an expected behavior where mouse moved
 from xterm to xev window, xev window:

 1. EnterNotify (mouse moved from xterm - xev window)
 2. FocusIn (xev window got focus)
 3. bunch of MotionNotify events as mouse moved around
 4. LeaveNotify (mouse left xev window)
 5. FocusOut (mouse entered xterm window)

 EnterNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741873, (13,137), root:(960,467),
 mode NotifyNormal, detail NotifyAncestor, same_screen YES,
 focus NO, state 0

 KeymapNotify event, serial 35, synthetic NO, window 0x0,
 keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0
  0
0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741877, (13,137), root:(960,467),
 state 0x0, is_hint 0, same_screen YES

 FocusIn event, serial 35, synthetic NO, window 0x1c1,
 mode NotifyNormal, detail NotifyNonlinear

 KeymapNotify event, serial 35, synthetic NO, window 0x0,
 keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0
  0
0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741889, (47,139), root:(994,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741903, (72,139), root:(1019,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741913, (82,139), root:(1029,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741926, (84,139), root:(1031,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82741937, (84,139), root:(1031,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742392, (79,139), root:(1026,469),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742404, (67,138), root:(1014,468),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742416, (41,134), root:(988,464),
 state 0x0, is_hint 0, same_screen YES

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742428, (10,133), root:(957,463),
 state 0x0, is_hint 0, same_screen YES

 LeaveNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742433, (-22,131), root:(925,461),
 mode NotifyNormal, detail NotifyAncestor, same_screen YES,
 focus YES, state 0

 FocusOut event, serial 35, synthetic NO, window 0x1c1,
 mode NotifyNormal, detail NotifyNonlinear


 This next sequence shows the problem:

 1. EnterNotify (mouse moved from xterm - xev window)
 2. FocusIn (xev window got focus - briefly?)
 3. FocusOut (mouse still in xev window, but window w/o focus)
 XXX What happened here?
 4. bunch of MotionNotify events as mouse moved around
 5. LeaveNotify (mouse left xev window)

 Notice no FocusOut event at the end of the sequence. Why
 did the FocusOut event happen early? What causes this?


 EnterNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742834, (23,139), root:(970,469),
 mode NotifyNormal, detail NotifyAncestor, same_screen YES,
 focus NO, state 0

 KeymapNotify event, serial 35, synthetic NO, window 0x0,
 keys:  4294967224 0   0   0   0   0   0   0   0   0   0   0   0   0   0
  0
0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

 MotionNotify event, serial 35, synthetic NO, window 0x1c1,
 root 0x2b8, subw 0x0, time 82742837, (23,139), root:(970,469),
 state 0x0, is_hint 0, same_screen YES

 FocusIn event, serial 35, synthetic NO, window 0x1c1,
 mode NotifyNormal, detail NotifyNonlinear

Re: wildcard poisoning

[patrick keshishian]

On 9/9/14, Stefan Olsson stur...@hotmail.com wrote:
 I came across an interesting article on wildcards in shell:
 http://www.defensecode.com/public/DefenseCode_Unix_WildCards_Gone_Wild.txt


 Tested some of the above in pdksh on a current OpenBSD-host:
 $ mkdir test
 $ cd test
 $ touch file1 file2 file3 -rf
 $ mkdir DIR1 DIR2
 $ ls -al
 total 16
 -rw-r--r--   1 sturban  sturban 0 Sep 10 04:26 -rf
 drwxr-xr-x   4 sturban  sturban   512 Sep 10 04:26 ./
 drwxr-xr-x  10 sturban  sturban  1024 Sep 10 04:25 ../
 drwxr-xr-x   2 sturban  sturban   512 Sep 10 04:26 DIR1/
 drwxr-xr-x   2 sturban  sturban   512 Sep 10 04:26 DIR2/
 -rw-r--r--   1 sturban  sturban 0 Sep 10 04:26 file1
 -rw-r--r--   1 sturban  sturban 0 Sep 10 04:26 file2
 -rw-r--r--   1 sturban  sturban 0 Sep 10 04:26 file3
 $ rm *
 $ ls -al
 total 8
 -rw-r--r--   1 sturban  sturban 0 Sep 10 04:26 -rf
 drwxr-xr-x   2 sturban  sturban   512 Sep 10 04:26 ./
 drwxr-xr-x  10 sturban  sturban  1024 Sep 10 04:25 ../

$ touch file1 file2 file3 -rf
$ mkdir DIR1 DIR2
$ ls -al
total 16
-rw-r--r--  1 sidster  wheel 0 Sep  9 21:19 -rf
drwxr-xr-x  4 sidster  wheel   512 Sep  9 21:19 ./
drwxrwxrwt  8 root wheel  1024 Sep  9 21:19 ../
drwxr-xr-x  2 sidster  wheel   512 Sep  9 21:19 DIR1/
drwxr-xr-x  2 sidster  wheel   512 Sep  9 21:19 DIR2/
-rw-r--r--  1 sidster  wheel 0 Sep  9 21:19 file1
-rw-r--r--  1 sidster  wheel 0 Sep  9 21:19 file2
-rw-r--r--  1 sidster  wheel 0 Sep  9 21:19 file3
$ rm ./*
rm: ./DIR1: is a directory
rm: ./DIR2: is a directory
noir $ ls -al
total 16
drwxr-xr-x  4 sidster  wheel   512 Sep  9 21:20 ./
drwxrwxrwt  8 root wheel  1024 Sep  9 21:19 ../
drwxr-xr-x  2 sidster  wheel   512 Sep  9 21:19 DIR1/
drwxr-xr-x  2 sidster  wheel   512 Sep  9 21:19 DIR2/

be smarter than that.

--patrick

Re: Managed DNS recommendation

[patrick keshishian]

On 8/29/14, Predrag Punosevac punoseva...@gmail.com wrote:
 This is not strictly OpenBSD based question but I highly value advises
 from this list.

 I just logged into our ZoneEdit account which is recently acquired by
 EasyDNS of Toronto. To my horror I found out that our renewal date has
 conveniently changed from August of 2018 to two weeks from now. I called
 EasyDNS customer service who conceded that transition is very tricky and
 they can't help me with my ZoneEdit account but would be happy to open
 their own account. ZoneEdit can be reached only via  e-mail.

 Long story short I am going to pull the trigger and changed our managed
 DNS provider. I just learnt that EasyDNS is BIND based. Any
 recommendation in particular for NSD based providers.

For what it's worth, I've been using EasyDNS since mid 90s.
My experience with their support staff has been _fantastic_!
I don't use them specifically for DNS, however.

Disclaimer, I am acquainted with EasyDNS founder, Mark J.,
who is super nice guy. That said, I've had more 1-on-1
correspondences with a handful of OBSD developers in the
past, say, year, than I have in a decade with Mark.

--patrick

Re: Does OpenBGPd suffer collateral damage with this?

[patrick keshishian]

On 8/17/14, Rod Whitworth glis...@witworx.com wrote:
 http://www.smh.com.au/technology/technology-news/how-flakey-is-the-inter
 net-20140816-104t8p.html

Internal Server Error

Cannot serve request to
/content/desktop/smh/technology/technology-news/how-flakey-is-the-inter%0Anet-20140816-104t8p.html
on this server

--patrick


 I would love to hear that our beloved BGP routers are the only ones
 that don't get screwed or at least we are one of the few.

 I haven't heard any noises from the hosting site that I look after.


 *** NOTE *** Please DO NOT CC me. I am subscribed to the list.
 Mail to the sender address that does not originate at the list server is
 tarpitted. The reply-to: address is provided for those who feel compelled to
 reply off list. Thankyou.

 Rod/
 ---
 This life is not the real thing.
 It is not even in Beta.
 If it was, then OpenBSD would already have a man page for it.

Re: Donations to OpenBSD

[patrick keshishian]

On 8/13/14, Worik Stanton worik.stan...@gmail.com wrote:
 I changed the subject line

 On 14/08/14 10:52, Eric Furman wrote:
 Fine, buy a T-shirt, but realize that only a small fraction of the cost
 actually goes to OpenBSD. When you buy a CD the vast majority
 of the cost goes to OpenBSD. Who cares whether you need the
 CD or not. Buy if for the cool stickers. Throw the CD in the trash
 for all I and the OpenBSD developers care.

 Respectfully I find that a bit offensive.  Ask me for a donation if you
 want.  But do not expect me to by an object to be manufactured, shipped
 1/3 of the way around the globe and then I'll through it in the trash.
 Not cool at all.

You can do what I do. I purchase the CDs but request
the vendor not to send me the actual, physical CDs. That's
my preferred donation method.

Cheers,
--patrick


 OpenBSD is, it seems, very cool and worth supporting.  I am
 investigating using the mechanism detailed in
 http://www.openbsd.org/bank-donation.html...

 Looking at https://https.openbsd.org/cgi-bin/order there seems to be no
 difference in CDs and T'Shirts in so far as where the money goes.  I do
 understand from conversations I have had that there is a difference.

 Lastly: IMO It is time to change.  CDs are no longer useful.  I have
 OpenBSD on a VPS so stickers are a waste of time too.  I would like to
 donate some money, but it is not easy.  I would like to know for sure
 that the money goes to the project.  For expenses or to developers, who
 spend so much time on this, to spend on whatever they want (beer, fish,
 little rubber balls...) But I will not buy things I cannot use.

 Worik



 --
 Why is the legal status of chardonnay different to that of cannabis?
worik.stan...@gmail.com 021-1680650, (03) 4821804
   Aotearoa (New Zealand)

 [demime 1.01d removed an attachment of type application/pgp-signature which
 had a name of signature.asc]

Re: Donations to OpenBSD

[patrick keshishian]

On 8/13/14, Worik Stanton worik.stan...@gmail.com wrote:
 On 14/08/14 11:45, patrick keshishian wrote:
 You can do what I do. I purchase the CDs but request
 the vendor not to send me the actual, physical CDs. That's
 my preferred donation method.

 Cool.  Where does the money all go in that case?  Definitely the most
 simple option so far.

I believe it goes to the project, no different than if I had received
the CDs.

 How does it compare for using the SWIFT method outlined on the website?

I'm not familiar that method, therefore, I can't comment.

Best,
--patrick


 Worik
 --
 Why is the legal status of chardonnay different to that of cannabis?
worik.stan...@gmail.com 021-1680650, (03) 4821804
   Aotearoa (New Zealand)

Re: openbsd and badusb

[patrick keshishian]

#badbios redux?
I seem to recall it was suspected that badbios started
with an infected USB stick.

On 8/1/14, Ted Unangst t...@tedunangst.com wrote:
 You may have heard about the badusb talk coming at blackhat. In
 theory, we should wait to watch the talk and see what it's actually
 about, but since some people can't wait that long, here's a few
 thoughts. (I'm a little surprised nobody has asked here already. I have
 some time free, thought I'd beat the rush. :))

 The claims on the main page, https://srlabs.de/badusb/, are fairly
 reasonable if a little vague. Other claims I'm reading elsewhere
 appear a little overhyped. In order of increasing danger...

 0. The final claim is that once infected, you'll always be infected
 because disinfection is nigh impossible. Meh. The same could be said
 of the firefox exploit of the week. It too can reprogram your bios or
 persist itself in any number of ways.

 1. They're exploiting all manner of Windows specific autorun
 functionality to install or configure drivers. By default, OpenBSD
 will do just about nothing when a USB device is plugged in, so this is
 not a serious concern.

 2. They have created a rogue keyboard device which will type naughty
 commands. In theory, the same keyboard could type rm -rf ~ into an
 xterm. This is a tiny bit more challenging since it probably depends
 on your desktop environment and window manager, but presumably your
 attacker will know all that. So yeah, vulnerable. But at the same
 time, I could also train a monkey to type that command and strap it to
 your normal not backdoored keyboard. Beware the badmonkey attack, too.

 3. A storage device may lie about the contents of a file. Sometimes it
 will say one thing (so it looks safe on this computer), sometimes it
 will say another (so it installs a backdoor on that computer). Don't
 install OpenBSD from media you don't control. Technically, signing the
 sets won't help since the backdoor installer might have a bogus key on
 it (or a bogus installer that doesn't check). You can always pxeboot
 and hope that the firmware in your ethernet card is more trustworthy.

 They don't appear to mention two other avenues of exploitation,
 which may be more practical. I refer specifically to OpenBSD,
 though there's no such limitation. First, the USB stack has a number
 of known races and other bugs, especially around attach/detach and
 error handling. If a rogue device attached and detached itself several
 times, it could likely corrupt the kernel heap. Game over.

 Second, any USB disk, even one with a normal firmware, can have an evil
 filesystem image on it. By this, I mean the metadata that the kernel
 reads is corrupt, not that it has naughty files. There have been crash
 reports when mounting corrupted (and even not corrupted) (e.g.)
 MSDOSFS disks. The kernel is a little too trusting that a filesystem
 is what it claims to be. There are probably exploitable vulns here,
 too.

 All that to basically say don't panic (that's the kernel's job).
 Fixing filesystem bugs is something we'll do, of course, but it's not
 a priority for me to sit down and start fuzzing Right Now. Same for
 miscellaneous bugs in the USB stack.

Re: openbsd and badusb

[patrick keshishian]

On 8/1/14, Gustav Fransson Nyvell gus...@nyvell.se wrote:
 On 08/01/14 23:01, Ted Unangst wrote:
 You may have heard about the badusb talk coming at blackhat. In
 theory, we should wait to watch the talk and see what it's actually
 about, but since some people can't wait that long, here's a few
 thoughts. (I'm a little surprised nobody has asked here already. I have
 some time free, thought I'd beat the rush. :))

 The claims on the main page, https://srlabs.de/badusb/, are fairly
 reasonable if a little vague. Other claims I'm reading elsewhere
 appear a little overhyped. In order of increasing danger...

 0. The final claim is that once infected, you'll always be infected
 because disinfection is nigh impossible. Meh. The same could be said
 of the firefox exploit of the week. It too can reprogram your bios or
 persist itself in any number of ways.

 1. They're exploiting all manner of Windows specific autorun
 functionality to install or configure drivers. By default, OpenBSD
 will do just about nothing when a USB device is plugged in, so this is
 not a serious concern.

 2. They have created a rogue keyboard device which will type naughty
 commands. In theory, the same keyboard could type rm -rf ~ into an
 xterm. This is a tiny bit more challenging since it probably depends
 on your desktop environment and window manager, but presumably your
 attacker will know all that. So yeah, vulnerable. But at the same
 time, I could also train a monkey to type that command and strap it to
 your normal not backdoored keyboard. Beware the badmonkey attack, too.

 3. A storage device may lie about the contents of a file. Sometimes it
 will say one thing (so it looks safe on this computer), sometimes it
 will say another (so it installs a backdoor on that computer). Don't
 install OpenBSD from media you don't control. Technically, signing the
 sets won't help since the backdoor installer might have a bogus key on
 it (or a bogus installer that doesn't check). You can always pxeboot
 and hope that the firmware in your ethernet card is more trustworthy.

 They don't appear to mention two other avenues of exploitation,
 which may be more practical. I refer specifically to OpenBSD,
 though there's no such limitation. First, the USB stack has a number
 of known races and other bugs, especially around attach/detach and
 error handling. If a rogue device attached and detached itself several
 times, it could likely corrupt the kernel heap. Game over.

 Second, any USB disk, even one with a normal firmware, can have an evil
 filesystem image on it. By this, I mean the metadata that the kernel
 reads is corrupt, not that it has naughty files. There have been crash
 reports when mounting corrupted (and even not corrupted) (e.g.)
 MSDOSFS disks. The kernel is a little too trusting that a filesystem
 is what it claims to be. There are probably exploitable vulns here,
 too.

 All that to basically say don't panic (that's the kernel's job).
 Fixing filesystem bugs is something we'll do, of course, but it's not
 a priority for me to sit down and start fuzzing Right Now. Same for
 miscellaneous bugs in the USB stack.

 This wouldn't be such a big problem if hardware manufacturers weren't so
 mysterious about their firmware and ways to install such firmware. I
 mean from the owner/operator/maintenance perspective. Maybe the EU
 should force them to help us...

oh the irony...

Re: Patch: porters guide chapter 2.2, item no. 23

[patrick keshishian]

On 7/25/14, Edward edw...@rdtan.net wrote:
 Hi,

 The original wording doesn't seems to flow too well:

 Create pkg/PLIST. After the install is complete use the developer's
 command, make plist which makes the file PLIST in the pkg directory.
 This file is a candidate packing list.

 I would like to suggest changing to the followig:

 Create pkg/PLIST. After the installation is done, use the developer's
 command make plist, which creates the file PLIST in pkg sub-directory.
 It will be a template for this port.

I don't think definition of the word template fits this
use-case. What issue do you have with the original
wording?

--patrick



 The patch to my suggestion is at the bottom of this mail, ok?

 Regards,
 Edward.

 Index: guide.html
 ===
 RCS file: /cvs/www/faq/ports/guide.html,v
 retrieving revision 1.29
 diff -u -p -r1.29 guide.html
 --- guide.html21 Jun 2014 12:17:47 -  1.29
 +++ guide.html25 Jul 2014 08:08:35 -
 @@ -498,10 +498,9 @@ generated packing-lists). Remember that
  For automatic updating of tt/etc/tt, sysmerge(8) may help.
  brbrli
  Create ttpkg/PLIST/tt.
 -After the install is complete use the developer's command,
 -ttbmake plist/b/tt which makes the file ttPLIST/tt in the
 -ttpkg/tt directory.
 -This file is a candidate packing list.
 +After the installation is done, use the developer's command
 +ttbmake plist/b/tt, which creates the file ttPLIST/tt in
 +ttpkg/tt sub-directory. It will be a template for this port.
  p
  Peruse ttPLIST/tt and verify that everything was installed and that it
 was
  installed in the proper locations.

Re: crowding out bsd using systemd?

[patrick keshishian]

On 6/28/14, Henning Brauer lists-open...@bsws.de wrote:
 * ian kremlin i...@kremlin.cc [2014-06-29 01:05]:
 due to its unportability (as it's written in pure C)

 that doesn't make the slightest sense.

 pure C can be and often is perfectly portable.

i took it as sarcasim.

--patrick

Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change

[patrick keshishian]

On 6/27/14, Theo de Raadt dera...@cvs.openbsd.org wrote:
 On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
  Having done a little man page reading on boot-time configuration, I
  learned about the existence of ukc. I'm wondering whether something
  like
 
 ukc disable acpi0
 
  might circumvent the kernel panic and allow the boot to successfully
  complete. I'm hoping that since this is a server, ACPI is non-essential.
 
  Just grasping at straws in an effort to get this machine up and running
 
  again.

 I think you should consider ACPI essential on pretty much any x86
 machine from the last 4-5 years or so - servers, laptops, standard PCs.

 Yes, ACPI is essential.  It is the modern way to interface to the hardware;
 it is the modern BIOS API.

viva pragmatism!
http://www.openbsd.org/lyrics.html#45
:)
--patrick


 The other BIOS interfaces (MPBIOS and PCIBIOS) are totally unreliable and
 rotting on most machines these days.   The vendors include support, but
 they
 do not verify their correctness.

 In an emergency such as this you might get away with it briefly, but
 some devices are likely not to work, and it's not recommended leaving
 it like that for any length of time, ACPI is involved in a lot of
 system controls (thermal controls, power etc) and most modern machines
 are just not designed/tested to work without it.

 Stuart is correct.  Those of you turning off ACPI are relying on an
 interface model we have repeatedly described as broken.

Re: mail.ssh with netstat command

[patrick keshishian]

On 6/20/14, Indunil Jayasooriya induni...@gmail.com wrote:
 Dear ALL,

 netstat gives below output on my openbsd 5 64 bit firewall. it is a VM.

 tcp  0128  mail.ssh   192.168.x.y.57850
  ESTABLISHED


 I think it is unusual?

you do not expect an ssh connection from 192.168.x.y
to the machine you ran netstat on, which has an interface
named mail?

--patrick

Re: _XData32() crash: long* vs int* on amd64 (LP64)

[patrick keshishian]

On 6/17/14, Matthew Dempsky matt...@dempsky.org wrote:
 I think the issue is that xsel.c allocates int nr_bytes; in
 change_property(), and then passes it to XChangeProperty with
 format==32.  However, XChangeProperty() documents that format==32
 specifically means a pointer to long (even on LP64 platforms).

Very good catch on the documentation!

 I suspect changing int nr_bytes to long nr_bytes should fix the bug.

I'm running it with suggested change. Let's see ...

--patrick


 On Tue, Jun 17, 2014 at 1:56 AM, patrick keshishian pkesh...@gmail.com
 wrote:
 Hi,

 I use xsel (from ports) pretty often, and every so often it
 crashes:

 $ gdb `which xsel` xsel.core
 GNU gdb 6.3
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB.  Type show warranty for
 details.
 This GDB was configured as amd64-unknown-openbsd5.5...
 Core was generated by `xsel'.
 Program terminated with signal 11, Segmentation fault.
 Loaded symbols ...
 [...]
 #0  0x05adb1e28f40 in _XData32 () from /usr/X11R6/lib/libX11.so.16.0
 (gdb) bt
 #0  0x05adb1e28f40 in _XData32 () from /usr/X11R6/lib/libX11.so.16.0
 #1  0x05adb1e05629 in XChangeProperty () from
 /usr/X11R6/lib/libX11.so.16.0
 #2  0x05aba4a03d75 in change_property (display=0x5adb3b07000,
 requestor=20978267, property=482, target=4, format=32, mode=0,
 data=0x5ada9647fc0 3\001, nelements=9, selection=1,
 time=3242522763,
 mparent=0x0) at
 /usr/build/ports/pobj/xsel-1.2.0/xsel-1.2.0/xsel.c:1177
 #3  0x05aba4a042f9 in handle_targets (display=0x5adb3b07000,
 requestor=20978267, property=482, selection=1, time=3242522763,
 mparent=0x0) at
 /usr/build/ports/pobj/xsel-1.2.0/xsel-1.2.0/xsel.c:1307
 #4  0x05aba4a04b48 in handle_selection_request (event=
 {type = 30, xany = {type = 30, serial = 22, send_event = 0,
 display = 0x5adb3b07000, window = 18874369}, xkey = {type = 30, serial
 = 22, send_event = 0, display = 0x5adb3b07000, window = 18874369, root
 = 20978267, subwindow = 1, time = 311, x = 482, y = 0, x_root =
 -1052444533, y_root = 0, state = 0, keycode = 0, same_screen = 0},
 xbutton = {type = 30, serial = 22, send_event = 0, display =
 0x5adb3b07000, window = 18874369, root = 20978267, subwindow = 1, time
 = 311, x = 482, y = 0, x_root = -1052444533, y_root = 0, state = 0,
 button = 0, same_screen = 0}, xmotion = {type = 30, serial = 22,
 send_event = 0, display = 0x5adb3b07000, window = 18874369, root =
 20978267, subwindow = 1, time = 311, x = 482, y = 0, x_root =
 -1052444533, y_root = 0, state = 0, is_hint = 0 '\0', same_screen =
 0}, xcrossing = {type = 30, serial = 22, send_event = 0, display =
 0x5adb3b07000, window = 18874369, root = 20978267, subwindow = 1, time
 = 311, x = 482, y = 0, x_root = -1052444533, y_root = 0, mode = 0,
 detail = 0, same_screen = 0, focus = 0, state = 0}, xfocus = {type =
 30, serial = 22, send_event = 0, display = 0x5adb3b07000, window =
 18874369, mode = 20978267, detail = 0}, xexpose = {type = 30, serial =
 22, send_event = 0, display = 0x5adb3b07000, window = 18874369, x =
 20978267, y = 0, width = 1, height = 0, count = 311}, xgraphicsexpose
 = {type = 30, serial = 22, send_event = 0, display = 0x5adb3b07000,
 drawable = 18874369, x = 20978267, y = 0, width = 1, height = 0, count
 = 311, major_code = 0, minor_code = 482}, xnoexpose = {type = 30,
 serial = 22, send_event = 0, display = 0x5adb3b07000, drawable =
 18874369, major_code = 20978267, minor_code = 0}, xvisibility = {type
 = 30, serial = 22, send_event = 0, display = 0x5adb3b07000, window =
 18874369, state = 20978267}, xcreatewindow = {type = 30, serial = 22,
 send_event = 0, display = 0x5adb3b07000, parent = 18874369, window =
 20978267, x = 1, y = 0, width = 311, height = 0, border_width = 482,
 override_redirect = 0}, xdestroywindow = {type = 30, serial = 22,
 send_event = 0, display = 0x5adb3b07000, event = 18874369, window =
 20978267}, xunmap = {type = 30, serial = 22, send_event = 0, display =
 0x5adb3b07000, event = 18874369, window = 20978267, from_configure =
 1}, xmap = {type = 30, serial = 22, send_event = 0, display =
 0x5adb3b07000, event = 18874369, window = 20978267, override_redirect
 = 1}, xmaprequest = {type = 30, serial = 22, send_event = 0, display =
 0x5adb3b07000, parent = 18874369, window = 20978267}, xreparent =
 {type = 30, serial = 22, send_event = 0, display = 0x5adb3b07000,
 event = 18874369, window = 20978267, parent = 1, x = 311, y = 0,
 override_redirect = 482}, xconfigure = {type = 30, serial = 22,
 send_event = 0, display = 0x5adb3b07000, event = 18874369, window =
 20978267, x = 1, y = 0, width = 311, height = 0, border_width = 482,
 above = 3242522763, override_redirect = 0}, xgravity = {type = 30,
 serial = 22, send_event = 0, display = 0x5adb3b07000, event

_XData32() crash: long* vs int* on amd64 (LP64)

[patrick keshishian]

Hi,

I use xsel (from ports) pretty often, and every so often it
crashes:

$ gdb `which xsel` xsel.core
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as amd64-unknown-openbsd5.5...
Core was generated by `xsel'.
Program terminated with signal 11, Segmentation fault.
Loaded symbols ...
[...]
#0  0x05adb1e28f40 in _XData32 () from /usr/X11R6/lib/libX11.so.16.0
(gdb) bt
#0  0x05adb1e28f40 in _XData32 () from /usr/X11R6/lib/libX11.so.16.0
#1  0x05adb1e05629 in XChangeProperty () from /usr/X11R6/lib/libX11.so.16.0
#2  0x05aba4a03d75 in change_property (display=0x5adb3b07000,
requestor=20978267, property=482, target=4, format=32, mode=0,
data=0x5ada9647fc0 3\001, nelements=9, selection=1, time=3242522763,
mparent=0x0) at /usr/build/ports/pobj/xsel-1.2.0/xsel-1.2.0/xsel.c:1177
#3  0x05aba4a042f9 in handle_targets (display=0x5adb3b07000,
requestor=20978267, property=482, selection=1, time=3242522763,
mparent=0x0) at /usr/build/ports/pobj/xsel-1.2.0/xsel-1.2.0/xsel.c:1307
#4  0x05aba4a04b48 in handle_selection_request (event=
{type = 30, xany = {type = 30, serial = 22, send_event = 0,
display = 0x5adb3b07000, window = 18874369}, xkey = {type = 30, serial
= 22, send_event = 0, display = 0x5adb3b07000, window = 18874369, root
= 20978267, subwindow = 1, time = 311, x = 482, y = 0, x_root =
-1052444533, y_root = 0, state = 0, keycode = 0, same_screen = 0},
xbutton = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, window = 18874369, root = 20978267, subwindow = 1, time
= 311, x = 482, y = 0, x_root = -1052444533, y_root = 0, state = 0,
button = 0, same_screen = 0}, xmotion = {type = 30, serial = 22,
send_event = 0, display = 0x5adb3b07000, window = 18874369, root =
20978267, subwindow = 1, time = 311, x = 482, y = 0, x_root =
-1052444533, y_root = 0, state = 0, is_hint = 0 '\0', same_screen =
0}, xcrossing = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, window = 18874369, root = 20978267, subwindow = 1, time
= 311, x = 482, y = 0, x_root = -1052444533, y_root = 0, mode = 0,
detail = 0, same_screen = 0, focus = 0, state = 0}, xfocus = {type =
30, serial = 22, send_event = 0, display = 0x5adb3b07000, window =
18874369, mode = 20978267, detail = 0}, xexpose = {type = 30, serial =
22, send_event = 0, display = 0x5adb3b07000, window = 18874369, x =
20978267, y = 0, width = 1, height = 0, count = 311}, xgraphicsexpose
= {type = 30, serial = 22, send_event = 0, display = 0x5adb3b07000,
drawable = 18874369, x = 20978267, y = 0, width = 1, height = 0, count
= 311, major_code = 0, minor_code = 482}, xnoexpose = {type = 30,
serial = 22, send_event = 0, display = 0x5adb3b07000, drawable =
18874369, major_code = 20978267, minor_code = 0}, xvisibility = {type
= 30, serial = 22, send_event = 0, display = 0x5adb3b07000, window =
18874369, state = 20978267}, xcreatewindow = {type = 30, serial = 22,
send_event = 0, display = 0x5adb3b07000, parent = 18874369, window =
20978267, x = 1, y = 0, width = 311, height = 0, border_width = 482,
override_redirect = 0}, xdestroywindow = {type = 30, serial = 22,
send_event = 0, display = 0x5adb3b07000, event = 18874369, window =
20978267}, xunmap = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, event = 18874369, window = 20978267, from_configure =
1}, xmap = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, event = 18874369, window = 20978267, override_redirect
= 1}, xmaprequest = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, parent = 18874369, window = 20978267}, xreparent =
{type = 30, serial = 22, send_event = 0, display = 0x5adb3b07000,
event = 18874369, window = 20978267, parent = 1, x = 311, y = 0,
override_redirect = 482}, xconfigure = {type = 30, serial = 22,
send_event = 0, display = 0x5adb3b07000, event = 18874369, window =
20978267, x = 1, y = 0, width = 311, height = 0, border_width = 482,
above = 3242522763, override_redirect = 0}, xgravity = {type = 30,
serial = 22, send_event = 0, display = 0x5adb3b07000, event =
18874369, window = 20978267, x = 1, y = 0}, xresizerequest = {type =
30, serial = 22, send_event = 0, display = 0x5adb3b07000, window =
18874369, width = 20978267, height = 0}, xconfigurerequest = {type =
30, serial = 22, send_event = 0, display = 0x5adb3b07000, parent =
18874369, window = 20978267, x = 1, y = 0, width = 311, height = 0,
border_width = 482, above = 3242522763, detail = 0, value_mask = 0},
xcirculate = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, event = 18874369, window = 20978267, place = 1},
xcirculaterequest = {type = 30, serial = 22, send_event = 0, display =
0x5adb3b07000, parent = 18874369, 

Re: Firefox download progress always reported as failed

[patrick keshishian]

On 6/14/14, Alessandro DE LAURENZIS just22@gmail.com wrote:
 On Sun 15/06 08:52, Alessandro DE LAURENZIS wrote:
 Greetings,

 I'm facing a weird Firefox behavior: when downloading a file, the
 progress indicator stays always switched off and in the download
 window the current operation is reported as failed.

 Actually, the download is properly on going (the part file is growing
 in size and, if I try to quit from the browser before it completes,
 the message If you exit now, 1 download will be cancelled appears,
 confirming that it is progressing.

 I tried with a brand-new Firefox installation, without any extensions
 loaded or custom config.

 Always reproducible on 5.5, GENERIC.MP.

 It's worth noting that the behavior is the same mounting the /home
 partition both with and without the noatime flag, just in case it
 could have any kinds of side-effect.

similar to what is discussed here last month:
http://marc.info/?t=14006906821r=1w=2

--patrick

Re: hplip

[patrick keshishian]

On 6/10/14, Maurice McCarthy m...@mythic-beasts.com wrote:
 OK, I think I've got it licked. the dj2540 being alarmingly cheap was never
 intended for use over the usb. After hp-setup has run it does not even
 advertise itself as present. After a reboot, lsusb does not show up the
 printer. The usb connection is only there for the setup program.

 Did some wholesale surgery deleting cups, hplip and a shedful of stuff. I'd
 thought that hpijs and cups would have given me usb printing. It did not.
 Cups could not find any printers on the usb even though it was listed in
 lsusb. There was no way to install it as a usb printer _and have it _work.

 What was confusing was that hp-setup said in was configured as hp:/usb/...
 whereas in fact it ends configured as hp:/net/... HP even say, somewhere, it
 is best to remove the usb cable after set up.

I think I read in your original post that one of the first things
you did was to set up the wireless interface of the printer
(ignore my post if I am misremembering).

I don't know about this specific printer, but my Brother printer
has USB, Ethernet and Wifi interfaces, but, once Wifi interface
is configured, for example, Ethernet port will not work. Until
the printer is reconfigured/reset and Ethernet selected.

I wouldn't be surprised if your printer acts similarly. i.e.,
abandoning other interfaces in favor of the configure one.
See your printer's documentation, it should specify this info.
Mine did.

--patrick


 Scanning was cured once I installed the correct version of sane-backends,
 i.e. sane-backends-1.0.24-snmp.

 hp-makeuri had to be run with the usb cable unplugged to give the scanner
 device name for scanimage to work

 $ hp-makeuri -s 192.168.0.3
 hpaio:/net/Deskjet_2540_series?ip=192.168.0.3

 It did mean having to start inetd and saned also. Hmmm. Ok I'll live with it
 for now.

 dj2540 natively uses PCL3gui so it does not understand postscript. Still,
 the print quality is good.

 Thanks
 Moss

Re: bash(1) 'read -n 1' in ksh(1)?

[patrick keshishian]

On 6/4/14, Marcus MERIGHI mcmer-open...@tor.at wrote:
 Hello,

 In my attempts to write a simple script that lets the user select
 options with a single key stroke I found no other way than to use bash
 and its built-in read command with -n 1.

 I am looking for a way to do this in ksh(1). Any ideas? Please...

maybe something like this:

--- 8 ---
#!/bin/sh

# TODO handle signals!
stty -icanon

# ask question
echo 1. Sing a song.
echo 2. Read a book.
echo 3. Go to sleep.
echo -n Make a choice: 
# read answer
ans=`dd count=1 2/dev/null`

# TODO validation

# print answer
echo 
echo ans=$ans

# reset
stty icanon
--- 8 ---

--patrick


 Some snippets from the bash(1) man page:

 read [-ers] [-a aname] [-d delim] [-i text] [-n nchars] [-N nchars] [-p
 prompt] [-t timeout] [-u fd] [name ...]
 One line is read from the standard input, or from the file [...]
 -n nchars
 read returns after reading nchars characters rather than
 waiting for a complete line of input, but honor a
 delimiter if fewer than nchars characters are read
 before the delimiter.

 Thanks in advance, Marcus

Re: Cannot get sound to work on a T60

[patrick keshishian]

On 5/25/14, Christian Schulte c...@schulte.it wrote:
 Am 05/25/14 06:49, schrieb patrick keshishian:
 On 5/24/14, Philip Guenther guent...@gmail.com wrote:
 On Sat, May 24, 2014 at 9:03 PM, Christian Schulte c...@schulte.it
 wrote:

 Am 05/25/14 04:21, schrieb Philip Guenther:
 On Sat, May 24, 2014 at 5:59 PM, Christian Schulte c...@schulte.it
 wrote:

 please see the output of 'dmesg', 'audioctl -f /dev/audio' and
 'mixerctl'
 included in this message. Is it correct that executing 'aucat -i
 something.wav' should produce audible output with things setup like
 this ?

 I don't have a .wav file on hand, but my T60 running i386 works Just
 Fine
 using mplayer.

 Internal speakers or do you have any external speakers connected ?


 Works both with internal speakers and with ear buds plugged in.

 So when did audio stop working on your box?

 Does your audio not work completely? Does it work
 through headphones? Speakers?


 I have not plugged in anything external to the machine. I am just
 heading after the internal speakers to provide something. Hmm. It does
 not even beep currently.

I ask to see if it your issue is at all related/similar to mine:
http://marc.info/?l=openbsd-miscm=139317761904835w=2

--patrick

Re: Error while compiling postfix with mysql and sasl2 (stable) on openBSD 5.5 - release

[patrick keshishian]

On 5/24/14, Mika mikas2...@gmx.at wrote:
 Hi,

 i tried to compile postfix with mysql and sasl2 from stable (on
 openBSD 5.5 - fresh install) and ended up this error message:

 # cd /usr/ports/mail/postfix/stable/
 # env FLAVOR=mysql sasl2 make
 install
 ===  Faking installation for postfix-2.11.0-sasl2-mysql
 install -d -o root -g bin -m 755
 /usr/ports/pobj/postfix-2.11.0-sasl2-mysql/fake-amd64-sasl2-mysql/usr/local/share/examples/postfix
 /bin/sh: cd: /usr/ports/pobj/postfix-2.11.0/postfix-2.11.0 - No such
 file or directory
 *** Error 1 in /usr/ports/mail/postfix/stable (../Makefile.inc:109
 'do-install': @(cd /usr/ports/pobj/postfix-2.11.0/postfix-2.11.0; sh
 post...)
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2748
 '/usr/ports/pobj/postfix-2.11.0-sasl2-mysql/fake-amd64-sasl2-mysql/.fake_done')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1874
 '/usr/ports/packages/amd64/all/postfix-2.11.0-sasl2-mysql.tgz')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2426
 '_internal-package')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2406 'package')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1891
 '/var/db/pkg/postfix-2.11.0-sasl2-mysql/+CONTENTS')
 *** Error 1 in /usr/ports/mail/postfix/stable
 (/usr/ports/infrastructure/mk/bsd.port.mk:2406 'install')

 I used google to look for a way to solve this problem but did not find one.
 As far I understand this compiling is fine but installing messed up.
 It looks like make install is looking in the wrong directory
 (/usr/ports/pobj/postfix-2.11.0/postfix-2.11.0 instead of /usr/ports
 /pobj/postfix-2.11.0-sasl2-mysql/fake-amd64-sasl2-mysql/postfix-
 2.11.0/).

You need use SUDO=sudo -E. The FLAVOR environment
variable is getting lost during making fake it looks like.

--patrick


 #cat
 /usr/ports/pobj/postfix-2.*

 
 total 144
 drwxr-xr-x   5 root  wheel   1024 May 24 13:00 .
 drwxr-xr-x  12 root  wheel512 May 24 13:18 ..
 -rw-r--r--   1 root  wheel  0 May 24 13:00 .build_done
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .buildwantlibs
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .configure_done
 -rw-r--r--   1 root  wheel 22 May 24 12:59 .dep-databases-mysql
 -rw-r--r--   1 root  wheel 10 May 24 12:48 .dep-devel-pcre
 -rw-r--r--   1 root  wheel 21 May 24 12:49 .dep-security-cyrus-sasl2
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .distpatch_done
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .extract_done
 -rw-r--r--   1 root  wheel  0 May 24 12:48 .extract_started
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .patch_done
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-c
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-crypto
 -rw-r--r--   1 root  wheel  0 May 24 12:59
 .spec-lib-mysql-mysqlclient-ge-10
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-pcre
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-pthread
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-sasl2
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-sqlite3
 -rw-r--r--   1 root  wheel  0 May 24 12:59 .spec-ssl
 drwxr-xr-x   2 root  wheel512 May 24 12:48 bin
 drwxr-xr-x   5 root  wheel512 May 24 13:00 fake-amd64-sasl2-mysql
 drwxr-xr-x  16 root  wheel   1536 May 24 12:59 postfix-2.11.0
 -rw-r--r--   1 root  wheel  57001 May 24 12:48 systrace.policy

 Any hints how to solve this problem?

 Thx for your help.

 Mika


 # dmesg
 OpenBSD 5.5 (GENERIC) #271: Wed Mar  5 09:31:16 MST 2014
 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 17127964672 (16334MB)
 avail mem = 16663453696 (15891MB)
 warning: no entropy supplied by boot loader
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (62 entries)
 bios0: vendor American Megatrends Inc. version 0603 date 09/21/2011
 bios0: ASUSTeK Computer INC. M5A78L-M/USB3
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S1 S3 S4 S5
 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT
 acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4)
 PCE7(S4) PCE9(S4) PCEA(S4) RLAN(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S4)
 PS2M(S4) UAR1(S4) P0PC(S4) [...]
 acpitimer0 at acpi0: 3579545 Hz, 32 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: AMD Phenom(tm) II X6 1055T Processor, 2812.98 MHz
 cpu0:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,NODEID,ITSC
 cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache
 cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully
 associative
 cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully
 associative
 cpu0: AMD erratum 721 detected and fixed
 cpu0: smt 0, core 0, package 0
 mtrr: Pentium Pro MTRR support, 

Re: Error while compiling postfix with mysql and sasl2 (stable) on openBSD 5.5 - release

[patrick keshishian]

On 5/24/14, Mika mikas2...@gmx.at wrote:
 I tried... but did not work...


 # cat
 /etc/mk.conf


 SUDO=/usr/bin/sudo -E

if you are setting it in /etc/mk.conf, leave off the quotation
marks.

--patrick


 # pwd
 /usr/ports/mail/postfix/stable
 # env FLAVOR=mysql sasl2 make install
 /bin/sh: trap: bad signal -E rm -rf /tmp/dep_cache.hYjum72Vb
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2426
 '_internal-package')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2406 'package')
 *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1891
 '/var/db/pkg/postfix-2.11.0-sasl2-mysql/+CONTENTS')
 *** Error 1 in /usr/ports/mail/postfix/stable
 (/usr/ports/infrastructure/mk/bsd.port.mk:2406 'install')

 Or did I missed something?

 Thx, Mika.

Re: Cannot get sound to work on a T60

[patrick keshishian]

On 5/24/14, Philip Guenther guent...@gmail.com wrote:
 On Sat, May 24, 2014 at 9:03 PM, Christian Schulte c...@schulte.it wrote:

 Am 05/25/14 04:21, schrieb Philip Guenther:
  On Sat, May 24, 2014 at 5:59 PM, Christian Schulte c...@schulte.it
 wrote:
 
  please see the output of 'dmesg', 'audioctl -f /dev/audio' and
 'mixerctl'
  included in this message. Is it correct that executing 'aucat -i
  something.wav' should produce audible output with things setup like
 this ?
 
  I don't have a .wav file on hand, but my T60 running i386 works Just
  Fine
  using mplayer.

 Internal speakers or do you have any external speakers connected ?


 Works both with internal speakers and with ear buds plugged in.

 So when did audio stop working on your box?

Does your audio not work completely? Does it work
through headphones? Speakers?

--patrick

Re: 5.5 CDs arriving

[patrick keshishian]

MONTH  DAY  YEAR  o AM  HOUR   MIN
 MAY01  2014  * PM   02  : 32
 DESTINATION TIME
  [LOS ANGELES, CA USA]

MONTH  DAY  YEAR  o AM  HOUR   MIN
 MAY01  2014  * PM   05  : 26
  PRESENT TIME

MONTH  DAY  YEAR  * AM  HOUR   MIN
 APR28  2014  o PM   09  : 22
   LAST TIME DEPARTED


On 5/1/14, Maurice McCarthy m...@mythic-beasts.com wrote:
 5.5 arrived Swansea, UK.

Re: On the way...Yay!

[patrick keshishian]

On 4/28/14, Rod Whitworth glis...@witworx.com wrote:
 Snip from an email this morning (GMT+10):
 Shipment from Canada via small packet AIR is confirmed via:
 CN22  28 April 2014 (ship date). 

Ha! I got you beat... my notice came Sunday evening ;)

Just checked and my stuff (at least the CDs) are in Great Falls,
MT as of tonight.

--patrick

 OpenBSD 5.5 CD sets.
 Now I just have to wait for airmail and customs here in Australia.

 If you have been slack about ordering now is the time to do it.
 Lots of new adventures with the first OS to kill the Y2K38 bug.

 Remember that sales of CD and various swag help the progress of the
 great product that is OpenBSD.

 Thanks to everyone who played any part in getting the latest disks to
 me.

Re: FYA: http://heartbleed.com/

[patrick keshishian]

| [NSA] knew for at least two years about ... the
| Heartbleed bug, and regularly used it to gather
| critical intelligence, two people familiar with
| the matter said.

I was waiting for someone to say this.

| ... the NSA has more than 1,000 experts
| devoted to ferreting out such flaws using
| sophisticated analysis techniques, many of them
| classified. The agency found Heartbleed shortly
| after its introduction, according to one of the
| people familiar with the matter, and it became a
| basic part of the agency's toolkit for stealing
| account passwords and other common tasks.

found! OK. so it wasn't implanted in there... what
a relief!

| Currently, the NSA has a trove of thousands of
| such vulnerabilities that can be used to breach
| some of the world's most sensitive computers,
| according to a person briefed on the matter.
| Intelligence chiefs have said the country's
| ability to spot terrorist threats and understand
| the intent of hostile leaders would be vastly
| diminished if their use were prohibited.

source: 
http://www.businessweek.com/news/2014-04-11/nsa-said-to-have-used-heartbleed-bug-exposing-consumers

See? This was all for the good of freedom loving people
after all!

I wonder when they'll leak the backdoor implan...I mean
they found in OpenBSD.

--patrick


On 4/10/14, Carlos Alberto Lopez Perez clo...@igalia.com wrote:
 On 08/04/14 21:40, Theo de Raadt wrote:
 On Tue, Apr 08, 2014 at 15:09, Mike Small wrote:
 nobody openbsd.as.a.desk...@gmail.com writes:

 read overrun, so ASLR won't save you

 What if malloc's G option were turned on? You know, assuming the
 subset of the worlds' programs you use is good enough to run with that.

 No. OpenSSL has exploit mitigation countermeasures to make sure it's
 exploitable.

 What Ted is saying may sound like a joke...

 So years ago we added exploit mitigations counter measures to libc
 malloc and mmap, so that a variety of bugs can be exposed.  Such
 memory accesses will cause an immediate crash, or even a core dump,
 then the bug can be analyed, and fixed forever.

 Some other debugging toolkits get them too.  To a large extent these
 come with almost no performance cost.

 But around that time OpenSSL adds a wrapper around malloc  free so
 that the library will cache memory on it's own, and not free it to the
 protective malloc.

 You can find the comment in their sources ...

 #ifndef OPENSSL_NO_BUF_FREELISTS
  /* On some platforms, malloc() performance is bad enough that you can't
 just


 OH, because SOME platforms have slow performance, it means even if you
 build protective technology into malloc() and free(), it will be
 ineffective.  On ALL PLATFORMS, because that option is the default,
 and Ted's tests show you can't turn it off because they haven't tested
 without it in ages.

 So then a bug shows up which leaks the content of memory mishandled by
 that layer.  If the memoory had been properly returned via free, it
 would likely have been handed to munmap, and triggered a daemon crash
 instead of leaking your keys.

 OpenSSL is not developed by a responsible team.



 Just for completion on this interesting debate about this malloc wrapper
 issue that has been raised here, I have forwarded it to the OpenSSL
 developers:

 http://thread.gmane.org/gmane.comp.encryption.openssl.devel/24208

 I guessed that you might be interested in knowing that.

 Regards!

 [demime 1.01d removed an attachment of type application/pgp-signature which
 had a name of signature.asc]

Re: PPTP after removing of userland ppp(8)

[patrick keshishian]

On 3/20/14, Stefan Sperling s...@openbsd.org wrote:
[...]
 And, as goes without saying, if possible, please consider using a different
 protocol. PPTP's weaknesses have been well understood for a long time now.
 Much better alternatives are available in the base system and the ports
 tree.

The statement much better alternatives are available suggests
the user has a choice in picking these alternatives. This isn't the
case some of the time.

In my case, in the recent past, I was either to use PPTP or some
other proprietary solution in order to connect to my employer's
network. The proprietary solution would require lugging around
a Windows or Mac laptop, which made PPTP the much better
alternative, allowing work in my preferred environment.

--patrick

Re: PPTP after removing of userland ppp(8)

[patrick keshishian]

On 3/20/14, Stuart Henderson s...@spacehopper.org wrote:
 On 2014-03-20, patrick keshishian pkesh...@gmail.com wrote:
 On 3/20/14, Stefan Sperling s...@openbsd.org wrote:
 [...]
 And, as goes without saying, if possible, please consider using a
 different
 protocol. PPTP's weaknesses have been well understood for a long time
 now.
 Much better alternatives are available in the base system and the ports
 tree.

 The statement much better alternatives are available suggests
 the user has a choice in picking these alternatives. This isn't the
 case some of the time.

 In my case, in the recent past, I was either to use PPTP or some
 other proprietary solution in order to connect to my employer's
 network. The proprietary solution would require lugging around
 a Windows or Mac laptop, which made PPTP the much better
 alternative, allowing work in my preferred environment.

 Which particular proprietary solution? If by any chance it's Cisco
 anyconnect, see ports/net/openconnect...

Don't recall. Maybe Juniper something?

--patrick

Re: No audio

[patrick keshishian]

On 2/23/14, Chris Bennett chrisbenn...@bennettconstruction.us wrote:
 On Sat, Feb 22, 2014 at 05:07:32PM -0600, Chris Bennett wrote:
 On Sat, Feb 22, 2014 at 04:47:25PM -0600, Chris Bennett wrote:
  I noticed error message on boot a while ago, but wasn't paying much
  attention until right now.
 
  I get:
  mixerctl outputs.master=200
  mixerctl: /dev/mixer: Device not configured
 
  home $ mixerctl
  mixerctl: /dev/mixer: Device not configured
 
  Sound wasn't a problem in the past.
 
  Using snap from today, but saw problem a good time ago, wish I had paid
  attention sooner.
 

 OK, I did a power off reboot and problem went away.
 But I have seen above errors on boot screen various times before.
 I did a soft reboot for this snapshot.
 BIOS said is a Crystal 4205 for sound.
 Is this a problem with snapshots or is my old laptop having hardware
 problems?



 OK, I haven't had any trouble repeating this problem today.
 Just comes and goes. One boot good, another bad.

I am not sure if this problem I noticed recently is related
or not. but I'll just throw it in the mix in case it jars some
memories.

running older snapshot (reason I haven't brought it up)
Planning to update to a newer one soon-ish.

kern.version=OpenBSD 5.4-current (GENERIC.MP) #222: Fri Dec 27 22:33:50 MST 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP


Playing music (e.g., via mpg123) and notice the audio goes
silent after a short while. stopping and restarting audio player
does not help. Restarting sndiod does not help either.

However, in another tmux window, if cause an audible bell,
e.g., pressing tab at the start of a ksh prompt, with each bell
sounds i hear the audio bits.

Only thing that seems to restore audio is zzz-wake cycle,
but only for a short while.

--patrick

Re: Documentation on rc.conf.local lacks important warning

[patrick keshishian]

On 2/12/14, Giancarlo Razzolini grazzol...@gmail.com wrote:
 Em 12-02-2014 07:48, Ingo Schwarze escreveu:
 Hi,

 Giancarlo Razzolini wrote on Mon, Feb 10, 2014 at 03:18:39PM -0200:

 The main issue here is, that, the human brain, although being this
 wonderful machine, makes a lot of assumptions to fill in the gaps, even
 when there are *no *gaps to be filled. I don't know if the documentation
 needs to be clearer in this specific case.
 Even though the misunderstanding does not seem to occur often,
 it does seem somewhat unsurprising because a lot of other software
 encourages the (imho questionable) practice of copying example
 configuration files.

 So here is what i came up with to make this clearer without
 making it longer or more redundant.

 OK?
   Ingo


 Index: rc.conf.8
 ===
 RCS file: /cvs/src/share/man/man8/rc.conf.8,v
 retrieving revision 1.20
 diff -u -r1.20 rc.conf.8
 --- rc.conf.817 Mar 2012 14:46:40 -  1.20
 +++ rc.conf.812 Feb 2014 09:40:09 -
 @@ -49,9 +49,9 @@
  .Nm rc.conf
  untouched, and instead create and edit a new
  .Nm rc.conf.local
 -file.
 -Variables set in this file will override variables previously set in
 -.Nm rc.conf .
 +file, setting just those variables whose
 +.Nm rc.conf
 +default values are intended to be overridden.
  .Pp
  Some variables are used to turn features on or off.
  For example, whether the system runs the
 HI Ingo,

 I've sent a patch on tech@, and there was a discussion about it, but
 there wasn't a consensus. I encourage you to join tech and the
 discussion. Send your proposal there too.

maybe some people should lurk more.

--patrick

Re: They are watching you

[patrick keshishian]

On 2/3/14, Giancarlo Razzolini grazzol...@gmail.com wrote:
 Em 02-02-2014 20:04, Jason Barbier escreveu:
 On 02/02/14 11:45, Chris Cappuccio wrote:
 Christian Weisgerber [na...@mips.inka.de] wrote:
 http://www.cbc.ca/news/politics/csec-used-airport-wi-fi-to-track-canadian-travellers-edward-snowden-documents-1.2517881


 If you didn't know already, this is your cue to look up ifconfig(8)'s
 lladdr random.

 And when you visit the US, Canada, or a number of other countries, the
 NSA has keeps record of every control and text message sent or
 received by
 your cellular phone. You know, things like your location and who you are
 calling. They aren't quite watching you, it's more like, they're
 sleeping
 with you :)
 Think it would be inappropriate to ask them for dinner since they are
 so far up my bisness?

 The truth is that any nerd with a decent hardware can do what was done
 in this specific case. Tracking people with wifi? It can be done with a
 laptop. It would be nice to have an agent to take me out for dinner. But
 I believe that we would run out of topics to talk about very quickly,
 since they already know so much about me.


why? you could have them show you how they did this using
just a laptop: accessing wifi hotspots starting from the
airport, to hotels, restaurants and cafe's across town
cataloging and cross-referencing all the data.. err...meta-
data. all allegedly without help from or knowledge of the
hotspot operator. could make a nifty youtube DIY vid.

Re: They are watching you

[patrick keshishian]

not sure how it is in canada, but traveling out of the us, you are essentially 
subjected to a physical exam. tracking my mac address is least of my worries.

--patrick

 On Jan 31, 2014, at 17:59, na...@mips.inka.de (Christian Weisgerber) wrote:
 
 http://www.cbc.ca/news/politics/csec-used-airport-wi-fi-to-track-canadian-travellers-edward-snowden-documents-1.2517881
 
 If you didn't know already, this is your cue to look up ifconfig(8)'s
 lladdr random.
 
 -- 
 Christian naddy Weisgerber  na...@mips.inka.de

Re: Trouble with Huawei e3276

[patrick keshishian]

On 1/24/14, Кирилл Каплин night...@gmail.com wrote:
 After update firmware on the modem I made some changes to the your patch
 (change id), it writes in dmesg:
 umsm0 at uhub2 port 5 configuration 1 interface 0 HUAWEI Technology HUAWEI
 Mobile rev 2.00/1.02 addr 3
 umsm0 detached
 umsm0 at uhub2 port 5 configuration 1 interface 0 HUAWEI Technology HUAWEI
 Mobile rev 2.00/1.02 addr 3
 ucom0 at umsm0
 umsm1 at uhub2 port 5 configuration 1 interface 1 HUAWEI Technology HUAWEI
 Mobile rev 2.00/1.02 addr 3
 umsm2 at uhub2 port 5 configuration 1 interface 2 HUAWEI Technology HUAWEI
 Mobile rev 2.00/1.02 addr 3
 ucom1 at umsm2
 umsm3 at uhub2 port 5 configuration 1 interface 3 HUAWEI Technology HUAWEI
 Mobile rev 2.00/1.02 addr 3
 umsm3: missing endpoint
 umsm4 at uhub2 port 5 configuration 1 interface 4 HUAWEI Technologies
 HUAWEI Mobile E3276 rev 2.00/1.02 addr 3
 umsm5 at uhub2 port 5 configuration 1 interface 5 HUAWEI Technologies
 HUAWEI Mobile E3276 rev 2.00/1.02 addr 3
 ucom2 at umsm5

 but that devices no appears in /dev

which devices exactly were you expecting to appear
in /dev?

--patrick




 On Fri, Jan 24, 2014 at 5:32 PM, Кирилл Каплин
 night...@gmail.com wrote:

 but it succesfully connects to it with program my huawei terminal under
 windows.
 anyway, thanks!


 On Fri, Jan 24, 2014 at 5:03 PM, David Coppa dco...@gmail.com wrote:

 On Fri, Jan 24, 2014 at 1:52 PM, Кирилл Каплин
 night...@gmail.com
 wrote:
  sorry for delay!
  after this patch, after attach in dmesg:
  umsm0 at uhub2 port 5 configuration 1 interface 0 Technology Mobile
 rev
  2.00/1.02 addr 3
  umsm0 detached
  urndis0 at uhub2 port 5 configuration 1 interface 0 Technology
  Mobile
 rev
  2.00/1.02 addr 3
  urndis0: using Vendorurndis0: ctrl message error: wrong size
  3735928559
 
  1024
  urndis0: unable to get query response
  : unable to get hardware address
  urndis1 at uhub2 port 5 configuration 1 interface 2 Technology
  Mobile
 rev
  2.00/1.02 addr 3
  urndis1: using Vendorurndis1: ctrl message error: wrong size
  3736059565
 
  1024
  urndis1: unable to get query response
  : unable to get hardware address
  umass0 at uhub2 port 5 configuration 1 interface 4 Technology Mobile
 rev
  2.00/1.02 addr 3
  umass0: using SCSI over Bulk-Only
  scsibus4 at umass0: 2 targets, initiator 0
  sd7 at scsibus4 targ 1 lun 0: , TF CARD Storage, 2.31 SCSI2 0/direct
  removable
  urndis2 at uhub2 port 5 configuration 1 interface 5 Technology
  Mobile
 rev
  2.00/1.02 addr 3
  urndis2: no data interface


 Oh, so this seems to be a LTE device!
 This particular modem has no modem interface, only NDIS.
 I know nothing about these devices, I'm sorry.

 Ciao,
 David

  On Thu, Jan 23, 2014 at 1:36 PM, David Coppa dco...@openbsd.org
 wrote:
 
 
   From: night...@gmail.com
   Date: Thu, Jan 23, 2014 at 10:01 AM
   Subject: Re: Trouble with Huawei e3276
   To: misc misc@openbsd.org
 
  ...
 
port 6 addr 3: high speed, power 500 mA, config 1, Mobile(0x155b),
   Technology(0x12d1), rev 1.02
  umass1
 
  ...
 
  Please try the attached diff:
 
  $ cd /usr/src/sys/dev/usb  patch -NE -i /path/to/e3276.diff
 
  And rebuild your kernel.
 
  Ciao,
  David
 
  Index: umsm.c
  ===
  RCS file: /cvs/src/sys/dev/usb/umsm.c,v
  retrieving revision 1.96
  diff -u -p -u -p -r1.96 umsm.c
  --- umsm.c  13 Dec 2013 17:43:07 -  1.96
  +++ umsm.c  23 Jan 2014 09:27:57 -
  @@ -138,6 +138,7 @@ static const struct umsm_type umsm_devs[
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E1820 },
 DEV_UMASS5},
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E220 },
  DEV_HUAWEI},
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E303 },
  DEV_UMASS5},
  +   {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E3276 },
 DEV_UMASS5},
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E353_INIT },
  DEV_UMASS5},
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E510 },
  DEV_HUAWEI},
  {{ USB_VENDOR_HUAWEI,   USB_PRODUCT_HUAWEI_E618 },
  DEV_HUAWEI},
  Index: usbdevs
  ===
  RCS file: /cvs/src/sys/dev/usb/usbdevs,v
  retrieving revision 1.622
  diff -u -p -u -p -r1.622 usbdevs
  --- usbdevs 22 Jan 2014 01:25:41 -  1.622
  +++ usbdevs 23 Jan 2014 09:28:02 -
  @@ -2153,6 +2153,7 @@ product HUAWEI K4510  0x14c5
  HUAWEI
 Mob
   product HUAWEI E353_INIT   0x14fe  HUAWEI Mobile E353 Initial
   product HUAWEI E392_INIT   0x1505  HUAWEI Mobile E392 Initial
   product HUAWEI K3765_INIT  0x1520  HUAWEI Mobile K3765 Initial
  +product HUAWEI E3276   0x155b  HUAWEI Mobile E3276
   product HUAWEI E173S   0x1c05  HUAWEI Mobile E173s
   product HUAWEI E173S_INIT  0x1c0b  HUAWEI Mobile E173s Initial
   product HUAWEI E3030x1f01  HUAWEI Mobile E303
  Index: usbdevs.h
  ===
  RCS file: 

Re: restoring keyboard layout after suspend or hibernate

[patrick keshishian]

On 1/23/14, Miod Vallat m...@online.fr wrote:
 Something is inconsistent here. Do you mean the uk is not the
 default? Or there is a difference between mux default and new attach
 default? How does one know whether plugging a keyboard in is
 reattaching it or attachning a new one?

 There is a difference between a keyboard which can provide accurate
 layout information, and one which can not.

 The Sun USB keyboard provides accurate layout information, and will
 always attach with the layout computed from this information, because
 this matches the writings on the key caps. (and power-users know enough
 to override that after the keyboard has been connected)

 The other keyboard do not know their actual layout, and thus the
 keyboard driver attaches with `I'd like the default layout, please, and
 if there isn't, please give me the us layout'.

 If there has been a default layout set on the mux (with kbd or
 wsconsctl, or with a ``strong knowledge'' keyboard being plugged before)
 before this cheap keyboard attaches, then it will get that layout.
 Otherwise it will get the us default.

 There is no way to please all users here. Some people will prefer
 keyboards to always attach as `us' layout, and only change the
 international keyboard they might connect for a while, and some people,
 on the other hand, will expect further keyboards to reuse the last-used
 layout.

 (And that's only in console. X is another nightma^Wstory)

Yes!
After I sent my question/comments on CapsLock, I recalled
a post about it some time ago. I can go dig it up ... OK dug.
the gist of it was that X changed, where it used to allow multiple
keyboard layouts when multiple keyboards were attached,
but at some point this stopped (IIRC):

This is Alexandr Shadchin's answer to me from Oct 2011:
http://marc.info/?l=openbsd-miscm=13181205625w=2
and this later from him as well:
http://marc.info/?l=openbsd-miscm=131851950413336w=2

To be honest, I don't think heard back nor have I attempted
testing this.

--patrick

Re: OpenBSD funding status

[patrick keshishian]

On 1/18/14, Eric Furman ericfur...@fastmail.net wrote:
 On Sat, Jan 18, 2014, at 06:23 PM, MJ wrote:
 (a lot of garbage snipped)

 additionally stick in a side comment regarding antiquity, then give up
 the FTP already - it’s a dinosaur, it’s unnecessarily complex, and it
 serves no specific purpose when HTTP is available.)

 BWHAHAHAH!
 This was really funny. Thank you, you made my day.

hashtagFTPemulationOverHTTP
hashtagEmailSo80s

Re: Request for Funding our Electricity

[patrick keshishian]

On 1/16/14, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
 The installer or man page asks for donations, how about the ssh login
 banner or initial output which might get perhaps 100s of thousands more
 eyefall?

I see where this is headed: In app purchases! e.g., after
couple of failed attempts/insults by sudo, it prompts you
to purchase your 'access' for only $1.99!

(:
--patrick



 --
 ___

 'Write programs that do one thing and do it well. Write programs to work
 together. Write programs to handle text streams, because that is a
 universal interface'

 (Doug McIlroy)

 In Other Words - Don't design like polkit or systemd
 ___

Re: Request for Funding our Electricity

[patrick keshishian]

On 1/14/14, Theo de Raadt dera...@cvs.openbsd.org wrote:
 On Tue, Jan 14, 2014 at 3:03 PM, Bob Beck b...@openbsdfoundation.org
 wrote:
 Just to bring this issue back to the forefront.
 
  In light of shrinking funding, we do need to look for a source to
  cover project expenses.  If need be the OpenBSD Foundation can be
  involved in receiving donations to cover project electrical costs.
 
  But the fact is right now, OpenBSD will shut down if we do not have
  the funding to keep the lights on.
 
  If you or a company you know are able to assist us, it would be
  greatly appreciated, but right now we are looking at a significant
  funding shortfall for the upcoming year - Meaning the project won't be
  able to cover 20 thousand dollars in electrical expenses before being
  able to use money for other things. That sort of situation is not
  sustainable.

 There's an equation that has to be satisfied here. It has a demand
 side and a supply side. You demand a certain amount of electricity and
 someone has to supply the money to pay for it. I'm going to be blunt
 here, in an effort to be helpful (it's also not foreign to the OpenBSD
 style). I get the impression that the demand for electricity is viewed
 as a given:  you use what you use and people need to step up and
 provide the money to pay for it. If I'm wrong, please say so. But if
 I'm right, the demand can be adjusted. Sometimes you need to eat
 cornflakes instead of caviar.  For example, I've never understood why
 this project supports the old architectures it does, considering the
 associated costs.

 The answer to that is not news.

 On a regular basis, we find real and serious bugs which affect all
 platforms, but they are incidentally made visible on one of the
 platforms we run, following that they are fixed.  It is a harsh
 reality which static and dynamic analysis tools have not yet resolved.

 Now, If you don't realize this is the reason we try to run on the
 older platforms, I am sorry but you have really not tried to stay in
 the loop of what makes OpenBSD a vibrant ecosystem.  If you aren't in
 the loop regarding this, then your mail comes off pretty darn preachy.

 The recent discussion of a need for a replacement
 Vax for package-building illustrates that.

 The vaxes being asked for draw almost no power, but it supplies the
 same benefits as the other architectures.

 Regarding shutting them down, there other social problems.

 Yes, we remove about 10 of the architectures.  We'd slowly lose the
 developers who like to work on those areas.  They also work in other
 areas, but ... I suspect they would another BSD that supports them.

 Perhaps this is an opportunity to reassess the scope of the project
 and trim some things that can no longer be justified on a cost-benefit
 basis.

 And maybe we've been doing that assessment continually for two
 decades.

 If the choice is between shutting the project down and reducing its
 scope to something sustainable, it's a no-brainer. This project has
 made really significant contributions, both in the obvious area,
 security, but also to the art of managing and building complex
 software that is reliable. To have it go away rather than trim its
 sails in way that acknowledges reality would really be a shame.

 This project has made?  How about this project will continue to.

 I really love how we keep getting advice.

I think you misunderstood the concept of supply and demand
pointed out in the message you replied to. We are so used to
leeching off the project, and for so long, that we feel entitled to
/demand/ that you and your project /supply/ what we feel entitled
to. Because of our dependence to this entitlement feeling, should
anything threaten the supply of what you produce, must not be
allowed. Even if we should need to go to our government
representatives to address this threat!

I can see it now: OBSD=OBama Software Distribution. It will
be provided to everyone and anyone, whether or not they feel
they need it. If anyone chooses to not use it, they still will be
charged a fee for the CD set they don't need now, but /might/
need in the future. This program will be sustained by inflated
CD prices (say $750 a copy), and by cutting bits of the project
which will be deemed unnecessary, such as old and obsolete
hardware support (VAX, Sparc, ...), stickers will be discontinued,
OpenSSH will be removed from base; let's be honest about it,
you really need encryption if you have something to hide (from
the government).

I understand they now have worked out all the glitches in their
web-site, which will now host the new OBSD.

Cheers,
--patrick