Re: softraid(4)/bioctl(8) vs. non-512-byte sectors disks

[Kenneth R Westerback]

On 10/08, Marcus MERIGHI wrote:
> kwesterb...@gmail.com (Kenneth Westerback), 2014.03.19 (Wed) 17:09 (CET):
> > Alas, softraid only supports 512 byte block devices at the moment.
> >  Ken
> 
> Any news on this one? No answer as always means 'no'. 
> 
> I saw plus58.html:
> * Use DEV_BSIZE instead of 512 where appropriate in the kernel. This
>   starts laying the groundwork to allow disks with other sector sizes.
> 
> 
> Just asking because some time has gone by and krw@ thought it was a
> pitty [0]: 
> 
> [0] http://dictionary.reference.com/browse/alas
> used as an exclamation to express sorrow, grief, pity, concern, or
> apprehension of evil.
> 
> Thanks+Bye, Marcus
> 

The 4K problem was 'solved' at c2k15 but unfortunately has not been
committed yet. The most likey diff is below. More expressions of
interest in getting it committed (especially if accompanied by test
reports) would help. Of course finding bugs would be good too!

 Ken

> > On Mar 19, 2014 11:36 AM, "Marcus MERIGHI"  wrote:
> > 
> > > Reference:
> > > ``Softraid 3TB Problems''
> > > http://marc.info/?l=openbsd-misc=136225193931620
> > >
> > > Difference:
> > > My HDDs show up as 4096 bytes/sector in dmesg.
> > >
> > > Short:
> > > Are there any options for disks that come with 4096 bytes/sector to use
> > > with softraid(4)/bioctl(8)?
> > >
> > > Long:
> > >
> > > So I got these lovely large disks:
> > >
> > > DMESG (full one at the end):
> > >
> > > umass4 at uhub5 port 4 configuration 1 interface 0 "Intenso USB 3.0
> > >   Device" rev 2.10/1.00 addr 9
> > > umass4: using SCSI over Bulk-Only
> > > scsibus5 at umass4: 2 targets, initiator 0
> > > sd5 at scsibus5 targ 1 lun 0:  SCSI4
> > >   0/direct fixed serial.174c55aa22DF
> > > sd5: 2861588MB, 4096 bytes/sector, 732566646 sectors
> > > 
> > > I suppose right above is my problem?
> > >
> > > FDISK:
> > >
> > > Disk: sd5   geometry: 45600/255/63 [732566646 4096-byte Sectors]
> > > Offset: 0   Signature: 0xAA55
> > > Starting Ending LBA Info:
> > >  #: id  C   H   S -  C   H   S [   start:size ]
> > >
> > >
> > -
> > --
> > >  0: 00  0   0   0 -  0   0   0 [   0:   0 ]
> > >   unused
> > >  1: 00  0   0   0 -  0   0   0 [   0:   0 ]
> > >   unused
> > >  2: 00  0   0   0 -  0   0   0 [   0:   0 ]
> > >   unused
> > > *3: A6  0   1   2 -  45599 254  63 [  64:   732563936 ]
> > >   OpenBSD
> > >
> > > DISKLABEL:
> > >
> > > # /dev/rsd5c:
> > > type: SCSI
> > > disk: SCSI disk
> > > label: whoknows
> > > duid: 470974d3647801b8
> > > flags:
> > > bytes/sector: 4096
> > > sectors/track: 63
> > > tracks/cylinder: 255
> > > sectors/cylinder: 16065
> > > cylinders: 45600
> > > total sectors: 732566646
> > > boundstart: 64
> > > boundend: 732564000
> > > drivedata: 0
> > >
> > > 16 partitions:
> > > #size   offset  fstype [fsize bsize  cpg]
> > >   a:732563936   64RAID
> > >   c:7325666460  unused
> > >
> > > BIOCTL output
> > >
> > > $ sudo bioctl -h -v -c C -l /dev/sd3a softraid0
> > > softraid0: sd3a has unsupported sector size (4096)
> > > softraid0: invalid metadata format
> > >
> > > Thanks in advance, Marcus
> > >

This is the diff that makes softraid of all kinds work on disks
with non-512-byte-sector disks. In fact it allows softraid volumes
to be constructed out of disks with different sector sizes. It will
present the constructed volume as having a sector size equal to the
largest sector of the devices used to contruct the softraid volume.

Test would be appreciated! As would ok's.

I manage to install a snap on a 4K device with an encrypted disk.
Couldn't boot it but if anybody has a BIOS that will boot a 4K drive
that would be an excellent test.

Index: softraid.c
===
RCS file: /cvs/src/sys/dev/softraid.c,v
retrieving revision 1.360
diff -u -p -r1.360 softraid.c
--- softraid.c  21 Jul 2015 03:30:51 -  1.360
+++ softraid.c  21 Jul 2015 04:02:14 -
@@ -944,6 +944,7 @@ sr_meta_validate(struct sr_discipline *s
 */
if (sm->ssd_data_blkno == 0)
sm->ssd_data_blkno = SR_META_V3_DATA_OFFSET;
+   sm->ssdi.ssd_secsize = DEV_BSIZE;
 
} else if (sm->ssdi.ssd_version == 4) {
 
@@ -953,14 +954,22 @@ sr_meta_validate(struct sr_discipline *s
 */
if (sm->ssd_data_blkno == 0)
sm->ssd_data_blkno = SR_DATA_OFFSET;
+   sm->ssdi.ssd_secsize = DEV_BSIZE;
 
-   } else if (sm->ssdi.ssd_version == SR_META_VERSION) {
+   } else if (sm->ssdi.ssd_version == 5) {
 
/*
 * Version 5 - variable 

Microsoft Now OpenBSD Foundation Gold Contributor

[Kenneth R Westerback]

The OpenBSD Foundation is happy to announce that Microsoft has made
a significant financial donation to the Foundation. This donation
is in recognition of the role of the Foundation in supporting the
OpenSSH project. This donation makes Microsoft the first Gold level
contributor in the OpenBSD Foundation's 2015 fundraising campaign.

Donations to the Foundation can be made on our Donations Page at

www.openbsdfoundation.org/donations.html

We can be contacted regarding corporate sponsorship at

fundrais...@openbsdfoundation.org.

OpenBSD Foundation 2014/2015 News Fundraising

[Kenneth R Westerback]

2014 was the most successful year to date for the OpenBSD Foundation.
Both in the amount of money we raised and in the support we provided
for the OpenBSD and related projects. We are extremely grateful for
the support shown by our contributers large and small.

A detailed summary of the Foundation's activities in 2014 can be seen at

http://www.openbsdfoundation.org/activities.html

But here are some highpoints.

We received $397,000 in new donations and paid out $129,000 to support the
activities of the OpenBSD and related projects.

Some of the things the $129,000 made happen were higher speed network
links to the project's machine room; new servers, UPSs, network
switches, serial consoles and network monitoring equipment for the
machine room; development machines for several developers; participation
in GSOC 2014; and hackathons in Lujbljana, Dunedin, Berlin, and
Marrakesh.

As you can see, 2014 was a very good year for the Foundation. This
can be attributed to a number of unique events. A very public
finanical crisis at the start of the year generated extensive
community support, and the releases of LibreSSL generated significant
interest and support.

But it is important for us not to rely on one time events for our
success.

Which brings us to our 2015 Fundraising Campaign, described at

http://www.openbsdfoundation.org/campaign2015.html

The OpenBSD Foundation needs your help to achieve our fundraising
goal of $200,000 for 2015. We need both Individual and Corporate
sponsorship of the Foundation.

Reaching this goal will ensure the continued health of the projects
we support, will enable us to help them do more, and will avoid the
distraction of financial emergencies that could spell the end of
the projects.

In particular it would allow us to fund more dedicated developer
time for targeted development of specific projects.

If $10 were given for every installation of OpenBSD in the last
year from the master site we would be at our goal.

If $2 were given for every download of the OpenSSH source code in
the last year from the master site we would be at our goal.

If a penny was donated for every pf or OpenSSH installed with a
mainstream operating system or phone in the last year we would be
at our goal.

As an individual or corporation, the best kind of donation we can
receive is a recurring donation. This allows longer term planning
on our part, instead of hoping for one time cash infusions. The
easiest way for an individual to support us in this way is a recurring
Paypal donation, which is our preference.

Donations to the foundation can be made on our Donations Page.

http://www.openbsdfoundation.org/donations.html

We can be contacted regarding corporate sponsorship at
fundrais...@openbsdfoundation.org

Re: dhcpd(8) support for option domain-search

[Kenneth R Westerback]

On Mon, Dec 23, 2013 at 12:03:13AM -0700, Darren Spruell wrote:
 Wanted to verify my understanding that the included dhcpd(8) in base
 does not currently support the domain-search option:
 
 
 option domain-search domain-list; The domain-search option specifies a
 'search list' of Domain Names to be used by the client to locate
 not-fully-qualified domain names. The difference between this option
 and historic use of the domain-name option for the same ends is that
 this option is encoded in RFC1035 compressed labels on the wire. For
 example:
 
 option domain-search example.com, sales.example.com,
  eng.example.com;
 
 
 dhcpd.conf(5) and dhcp-options(5) don't mention the option.

option 119 (domain search, specified in rfc 3397) is not supported
in the base version of dhcpd.

One *could* provide it with the syntax

option-119 nn:nn:nn:nn:nn...

where you provide the appropriate hex digits to specify the contents
of the option. Not a nice solution. :-)


 
 I can currently override the search domains on clients, and it seems
 like it might be supported in isc-dhcp-server package. Anything likely
 to make it into base? Simply a matter of patch not having been
 submitted, or anything deeper than that?

Nothing deeper than that, as far as I know. Is option 119 in wide use as
far as you know?

 Ken

Re: resolver question

[Kenneth R Westerback]

On Mon, Dec 23, 2013 at 02:37:47PM +0100, Peter J. Philipp wrote:
 I'm trying to track down the code in the libasr that causes this behaviour:
 
 Whenever I go to a IPv4 site and IPv6 query is made for domain+mydomain
 like a search.  So with logging turned on, on my nameserver I get this:
 
 pjp@americas$ grep canoe.ca.centroid.eu /var/log/all
 Dec 20 17:00:37 americas wildcarddnsd[29850]: request on descriptor 17
 interface em0 from 212.114.242.132 (ttl=54, region=255) for
 chealth.canoe.ca.centroid.eu. type=(28) class=1, answering NXDOMAIN
 
 The problem is that my nameservers are in china and latin america and
 I'M sorta worried about these leaks.  This particular log came from my
 nameserver in panama and the packet passes miami.

I'm not clear on what the leak you are worried about is.

 Ken

 
 My resolv.conf file looks like this on the workstation here in germany:
 
 jupiter$  more /etc/resolv.conf
 # Generated by re0 dhclient
 search centroid.eu
 nameserver 192.168.34.1
 domain centroid.eu
 lookup file bind
 family inet6 inet4
 
 
 The leak only happens with  queries, like said.  Any hints on
 tracking this down and squelching it?
 
 Regards,
 
 -peter

Re: netstat segfault on -current

[Kenneth R Westerback]

On Tue, Dec 24, 2013 at 12:31:56AM +0200, Alexey Suslikov wrote:
 On Tue, Dec 24, 2013 at 12:26 AM, Jirimie Courrhges-Anglas
 j...@wxcvbn.org wrote:
  Alexey Suslikov alexey.susli...@gmail.com writes:
 
  On Tue, Dec 24, 2013 at 12:16 AM, Chris Smith obsd_m...@chrissmith.org 
  wrote:
  On Mon, Dec 23, 2013 at 5:10 PM, Alexey E. Suslikov
  alexey.susli...@gmail.com wrote:
  blind guess - you have kernel and userland out of sync.
 
  Not so.
 
  It doesn't matter how so: ABI is either in sync, or it is out of sync 
  (hence
  the issue). cvs up and rebuild/reinstall netstat.
 
  This may very well be a real issue, not just another case of
  out-of-sync.
 
 ... but *first* cvs up and rebuild/reinstall netstat, right?
 

It is a real issue, due to errors I made replacing CIRCLEQ with TAILQ.

A fix is being worked on, and a workaround probably sooner than that.

 Ken

Re: dhcpd: rejecting bogus offer

[Kenneth R Westerback]

On Mon, Dec 09, 2013 at 01:25:30PM -0500, Chris Smith wrote:
 What might be the implications of the following messages in the log?
 
 
 Dec  6 15:09:39 firewall dhcpd[29710]: option option-79 (119) larger
 than buffer.
 Dec  6 15:09:39 firewall dhcpd[29710]: rejecting bogus offer.
 
 Dec  9 12:15:35 firewall dhcpd[29710]: option tftp-server-name (111)
 larger than buffer.
 Dec  9 12:15:35 firewall dhcpd[29710]: rejecting bogus offer.
 
 
 Besides the bogus offer entries I'm seeing other things like:
 
 Dec  5 16:02:11 firewall dhcpd[29710]: IP address 172.28.65.139
 answers a ping after sending a release
 Dec  5 16:02:11 firewall dhcpd[29710]: Possible release spoof - Not
 releasing address 172.28.65.139
 Dec  5 23:03:36 firewall dhcpd[29710]: Abandoning IP address
 172.28.65.121 for 3600 seconds: pinged before offer
 Dec  6 09:09:41 firewall dhcpd[29710]: Abandoning IP address
 172.28.65.123 for 3600 seconds: pinged before offer
 
 
 Possible network issues? Malicious client? Or?

Malicious or confused. Or truncated packets. The log message
means that the option length as given in the packet would run
the option data outside the received packet. The confusion
might have started in an earlier option, unless you are
actually providing Novell Service Location Protocol info?

Not sure what the 'Possible release spoof' is. I'd have to go
read the code. Ditto 'Abandoning IP address'.

tcpdump might be your best friend here to see what packets are
coming and going.

 Ken

 
 Thank you,
 
 Chris

Re: Help troubleshooting performance problem

[Kenneth R Westerback]

On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
 I'm having some trouble figuring out what is causing a systemic performance
 issue.  By systemic I mean that running even seemingly trivial things
 (i.e. 'ls' on a directory with only a few files in it) is accompanied by a
 substantial delay before any response, say, of 15-30 seconds.  Not *every*
 single time, but pretty frequently.  Looking at top, load average is higher
 than expected on a largely idle web  smtp server, usually between .7 and
 1.6.  This is a dual-core opteron box (Sun Fire X2100) with 8GB RAM. (dmesg
 below).
 
 Sorting top by CPU utilization shows that the CPUs are mostly idle.
 vmstat/iostat isn't making anything leap out at me as getting stuck in
 paging or waiting for I/O.  The disc is a softraid RAID1 volume, bioctl
 shows that it's OK.  This does not appear to be network bandwidth-related,
 at least, I can get the expected throughput testing with iperf.
 
 Posting something on the forum software that it's running can take 3-4
 minutes to complete, and it's writing the posted info to a mysql database.
 Neither httpd nor mysqld seem to wind up much load while this is occurring.
 
 So, what should I be looking at to figure out where things are getting
 stalled up?
 
 Thanks for any ideas,
 
 -John
 
 dmesg:
 
 OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013
 j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/
 GENERIC.MP

Try 5.4 or -current.

Issues with non-home-compiled kernels are more interesting.

 Ken

Re: Help troubleshooting performance problem

[Kenneth R Westerback]

On Sat, Nov 30, 2013 at 07:04:44PM -0600, Shawn K. Quinn wrote:
 On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote:
  On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote:
   OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013
   j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/
   GENERIC.MP
  
  Try 5.4 or -current.
  
  Issues with non-home-compiled kernels are more interesting.
 
 I thought as long as it was an unmodified GENERIC or GENERIC.MP that the
 issue was still valid. Is this no longer the case?
 
 -- 
   Shawn K. Quinn
   skqu...@rushpost.com
 

Sure - but if it's unmodified, why compile a new one? And John did
not state in his email that it was unmodified.

 Ken

Re: mac mini

[Kenneth R Westerback]

On Wed, Nov 20, 2013 at 04:09:07PM -0200, Friedrich Locke wrote:
 Does anyone here run Open/FreeBSD on mac mini ?
 
 Does the OS fully supports macmini hadrwared ?
 
 Thank you for the answers.
 
 Fried.
 

I'm typing this on OpenBSD on the last generation of powerpc mac
mini's if that helps.

 Ken

Re: make release problem with -current

[Kenneth R Westerback]

On Tue, Nov 05, 2013 at 11:23:26PM -0500, Scott McEachern wrote:
 On 11/05/13 23:02, Philip Guenther wrote:
 On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern sc...@blackstaff.ca wrote:
 On 11/05/13 22:29, Ted Unangst wrote:
 On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote:
 Anyone else running into this when running make release with -current?
 vnconfig -v -c vnd0 /var/tmp/image.11200
 vnconfig: VNDIOCSET: Device busy
 Are you already using vnd0?
 No, not intentionally at least.
 So you've used vnconfig -l to see what it's currently bound to and...
 
 
 # vnconfig -l
 vnd0: covering /var/tmp/image.28401 on sd0e, inode 12
 vnd1: not in use
 vnd2: not in use
 vnd3: not in use

This is why I ended up with 

/sbin/umount /mnt
/sbin/vnconfig -u vnd0

in the script I use to invoke make build  make release. :-)

 Ken

 
 I'm not sure if that's from something earlier in the build process,
 or possibly from a failed build the other night.
 
 Either way, I'm going to just nuke it all, install from scratch, and
 see how that goes.  I'll bet it will work just fine..
 
 -- 
 Scott McEachern
 
 https://www.blackstaff.ca
 
 Beware the Four Horsemen of the Information Apocalypse: terrorists, drug 
 dealers, kidnappers, and child pornographers. Seems like you can scare any 
 public into allowing the government to do anything with those four.  -- 
 Bruce Schneier

Re: MBR Mishap!

[Kenneth R Westerback]

On Mon, Nov 04, 2013 at 06:12:15PM -0500, mia wrote:
 On 11/03/13 10:35, Nick Holland wrote:
 On 11/02/13 20:38, mia wrote:
 On 11/02/13 22:35, Nick Holland wrote:
 On 11/02/13 14:18, mia wrote:
 Hi All,
 
 I have a system with a sata disk or the OS and a areca pcie raid card
 with 4 1.5 Tb drives in a raid5 configuration.  The raid has data on it
 and the OS drive was blank.
 
 I was doing a fresh install on the OS, unfortuntately I forgot that the
 OpenBSD install sees the OS drive as sd1.  I chose sd0 and got some
 message, wasn't on a console so didn't capture it, about drive too large
 for fdisk.  I went on and then saw the number of sectors and realized
 immediately I chose the wrong disk.  I did a control+C, rebooted and
 then installed on the sd1 drive.
 
 Now that i'm back in the OS I went to mount the raid and got a device
 not configured message for /dev/sd0a.  I did a disklable -E sd0 and to
 my horror there is no a partition left on the raid.  :-(
 
 Is there any way to get this back?  Can I simply use disklable to use
 all space on the drive to recreate the mbr and my data will be
 available?  I'm desperate, ANY help will be GREATLY appreciated.
 ok, if I followed this, you changed the MBR with fdisk -- AND NOTHING ELSE.
 
 IF that's true...and you know what and where partitions were, yes, you
 are in not bad shape.
 
 I'd start by using fdisk to recreate the OpenBSD partition as it was
 (hopefully, whole disk.  probably starting at either sector 64 (if
 newer) or sector 63 (if older).  Do that, reboot (I'm not sure
 that's needed, but it prolongs the suspense), and you should see your
 disklabel partitions just come back from the not-quite-dead.  If you
 aren't sure about your starting partition, try both 64 and 63, see which
 one brings back your disklabel.
 
 A few more tips here:
 http://www.openbsd.org/faq/faq14.html#OhBugger
 
 Good luck.
 
 Nick.
 Hi Nick,
 
 Thanks for the reply, I didn't directly use fdisk.  This was part of a
 fresh install of 5.4.  I chose the wrong disk, fdisk looked at the
 drive, complained about it being too big, I hit enter and then  did a
 ctrl+c to get out before it did any damage/write (i thought).  I'm
 guessing when it warned about the partition being too big and I hit
 enter, it did something that wiped my mbr at that point.
 
 The partition was originally W (WHOLE DISK), yes, with a single
 partition.  This raid drive was just for data and usually mounted ro
 unless I need to add something.
 
 The old system was 5.3, so it is newer (weird that current does 63 on my
 ssd).
 
 So if i'm following you, I should use fdisk and not use disklable at
 all?  I thought I'd go into disklable -E  do an a a with no newfs
 afterward and I should be able to just do a mount /dev/sd0a
 /mnt/point  (I'm glad i didn't proceed.)  I'm really hoping to not lose
 this data.. mostly centimental stuff that I can't replace.
 
 Thanks again,
 
 Aaron
 definitely start with fdisk, NOT disklabel.
 The hope is that by defining a proper MBR, you will end up with your
 (untouched) disklabel just appearing where OpenBSD expects it to be.
 
 Nick.
 
 
 Hi Nick,
 
 Thanks,
 
 I'm not sure what I would do with fdisk, it appears as though it's
 how it should be.
 
 # fdisk sd0
 fdisk: disk too large (8789061120 sectors). size truncated.
 Disk: sd0   geometry: 267349/255/63 [4294961685 Sectors]
 Offset: 0   Signature: 0xAA55
 Starting Ending LBA Info:
  #: id  C   H   S -  C   H   S [   start:size ]
 ---
  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 *3: A6  0   1   2 - 267348 254  63 [  64:  4294961621 ] OpenBSD
 # disklabel sd0
 # /dev/rsd0c:
 type: SCSI
 disk: SCSI disk
 label: ARC-1210-VOL#00
 duid: 
 flags:
 bytes/sector: 512
 sectors/track: 63
 tracks/cylinder: 255
 sectors/cylinder: 16065
 cylinders: 547093
 total sectors: 8789061120
 boundstart: 64
 boundend: 4294961685
 drivedata: 0
 
 16 partitions:
 #size   offset  fstype [fsize bsize  cpg]
   c:   87890611200  unused
 
 I have the backup for the old disklable and it looks like this:
 # cat disklabel.sd0.current
 # /dev/rsd0c:
 type: SCSI
 disk: SCSI disk
 label: ARC-1210-VOL
 duid: b040b4952bec09ff
 flags:
 bytes/sector: 512
 sectors/track: 63
 tracks/cylinder: 255
 sectors/cylinder: 16065
 cylinders: 547093
 total sectors: 8789061120
 boundstart: 512
 boundend: 199019008
 drivedata: 0
 
 16 partitions:
 #size   offset  fstype [fsize bsize  cpg]
   a:   8789060608  512  4.2BSD   8192 655361
   c:   87890611200  unused
 
 
 I ran scan_ffs as the link you provided suggested and got the 

Re: Problems receiving IP with dhclient

[Kenneth R Westerback]

On Tue, Nov 05, 2013 at 08:38:49AM +0100, Marc Peters wrote:
 Hi misc,
 
 i upgraded my Router at home from 5.3-STABLE to 5.4-RELEASE on Friday.
 After some hours, dhclient has problems to receive the DHCPOFFER
 anymore. Surfing the logs shows a lot of DHCPREQUEST without an IP.
 Sometimes the dhclient gets the DHCPOFFER, but more often not. When i
 restart dhclient, it receives it immediatly and sits there happily for
 some hours. Then i have to restart it again.
 
[[ snip ]]

 I didn't notice this behaviour on 5.3. Where there any changes to
 dhclient or should i talk to my ISP?
 
 Cheers,
 Marc

There were many changes to dhclient, but this problem was obviously
not intended.

What would help is

1) Your dhclient.conf
2) Any command line options you start dhclient with
3) A tcdump of the conversation. Something like

tcpdump -i blah -s 2000 -vv -X 

if you want to capture the text output, or

tcpdump -i blah -s 2000 -w file to send me

if you want to just capture the packets.

 Ken

Re: USB stick geometry question

[Kenneth R Westerback]

I've had similar things happen on my current build-box, but just
wrote it off to a weird bios thing. Tweaking the MBR never occurred
to me that I can recall.

I'll see if it is still happening to me.

 Ken

On Fri, Nov 01, 2013 at 09:09:21PM +0100, Stefan Sperling wrote:
 I have run into a small issue with an x130e thinkpad and a 4GB USB stick.
 
 After running fdisk -i on the USB stick, having the stick inserted
 at power-on prevents the laptop from booting. It gets stuck with a
 black screen, before even showing the first 'Thinkpad' logo screen
 where I can enter the BIOS by pressing F1. Eventually the system
 resets automatically, but then hangs again as before.
 
 When I remove the stick while the system hangs, the system instantly
 resumes booting. I can reinsert the stick and 'reboot' from the boot
 loader, and the system comes up properly. 'machine diskinfo' shows
 this for the stick:
 
 Disk  BIOSTypeCylsHeads   SecsFlags   Checksum
 hd1   0x81label   492 255 63  0x0 0xd1aa95e2
 
 This is the partition table created by fdisk -i:
 
 Disk: sd1   geometry: 491/255/63 [7892992 Sectors]
 Offset: 0   Signature: 0xAA55
 Starting Ending LBA Info:
  #: id  C   H   S -  C   H   S [   start:size ]
 ---
  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
 *3: A6  0   1   2 -490 254  63 [  64: 7887851 ] OpenBSD   
 
 Disabling USB boot support in the BIOS fixes the issue but makes
 it impossible to use the USB stick as keydisk since the stick
 doesn't show up in 'machine diskinfo' anymore.
 
 Zeroing the first MB of the stick also fixes the issue.
 'machine diskinfo' now shows:
 
 Disk  BIOSTypeCylsHeads   SecsFlags   Checksum
 hd1   0x81label   490 255 63  0x0 
 
 The problem also goes away if I manually create a partition table with
 'fdisk -e  -c 490 -h 255 -s 63 sd1' that looks as follows:
 
 Disk: sd1   geometry: 490/255/63 [7871850 Sectors]
 Offset: 0   Signature: 0x0
 Starting Ending LBA Info:
  #: id  C   H   S -  C   H   S [   start:size ]
 ---
  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  3: A6  0   1   2 -489 254  63 [  64: 7871786 ] OpenBSD 
 
 'machine diskinfo' for that is:
 Disk  BIOSTypeCylsHeads   SecsFlags   Checksum
 hd1   0x81label   490 255 63  0x0 0x2c0f040e
 
 I bought 3 of these USB sticks and ran into this problem with 2 of them.
 I then unwrapped the third one from the packaging and tested it unmodified.
 The system boots fine and 'machine diskinfo' shows:
 
 Disk  BIOSTypeCylsHeads   SecsFlags   Checksum
 hd1   0x81label   985 128 63  0x0 0xb919a6ea
 
 The partition table looks like this in fdisk:
 
 Disk: sd1   geometry: 491/255/63 [7892992 Sectors]
 Offset: 0   Signature: 0xAA55
 Starting Ending LBA Info:
  #: id  C   H   S -  C   H   S [   start:size ]
 ---
 *0: 0C  0   1   1 -491  80  37 [  63: 7892929 ] Win95 
 FAT32L
  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused   
 
 Can anyone explain this problem?
 
 Is it a BIOS/UEFI firmware bug?
 Is it an incompability between OpenBSD's fdisk and the BIOS that can
 happen due to diferences in disk geometry detection heuristics?
 Is it a bug in OpenBSDs fdisk?

Re: Request to OpenBSD Dev's - Beer on offer

[Kenneth R Westerback]

On Tue, Oct 29, 2013 at 03:01:22PM +, Andy wrote:
 On Tue 29 Oct 2013 14:55:05 GMT, Adam Thompson wrote:
 On 13-10-28 11:54 AM, Andy wrote:
 Would any of the esteemed OpenBSD developers be interested in adding
 support for BFD (Bidirectional Forward Detection) to OpenBSD.
 [...]
 '+1's welcome from others who would be interested to show signs of
 support/interest..
 
 I can only agree, BFD support would be a very nice thing to have,
 considering that in other ways OpenBSD is already a very capable
 router.  I'm not in a position right now to pay someone properly to
 implement it, but I can sustain the cost of another case or three of
 beer.
 
 
 Amazing!
 
 So we just need to find an alcoholic developer and we're on our way
 ;) Could maybe send some caffeine and pro plus in the mean time ..
 

Finding an alcoholic developer is not a challenge. :-)

 Ken

newfs_msdos(8) creates faulty filesystems

[Kenneth R Westerback]

While harmless it seesm pointless to create a filesystem that generates
warnings when fsck'd.

So check for -1 (an allowed value) in FSFree and FSNext fields, and
set FSNext to -1 in newfs_msdos, rather than setting it to a
value sure to be not a free cluster.

Anybody know of reasons to not do this?

 Ken

Index: fsck_msdos/fat.c
===
RCS file: /cvs/src/sbin/fsck_msdos/fat.c,v
retrieving revision 1.18
diff -u -p -r1.18 fat.c
--- fsck_msdos/fat.c27 Oct 2009 23:59:33 -  1.18
+++ fsck_msdos/fat.c21 Oct 2013 09:53:56 -
@@ -527,7 +527,7 @@ checklost(int dosfs, struct bootblock *b
 
if (boot-FSInfo) {
ret = 0;
-   if (boot-FSFree != boot-NumFree) {
+   if (boot-FSFree != -1  boot-FSFree != boot-NumFree) {
pwarn(Free space in FSInfo block (%d) not correct 
(%d)\n,
  boot-FSFree, boot-NumFree);
if (ask(1, fix)) {
@@ -535,7 +535,8 @@ checklost(int dosfs, struct bootblock *b
ret = 1;
}
}
-   if (boot-NumFree  fat[boot-FSNext].next != CLUST_FREE) {
+   if (boot-NumFree  boot-FSNext != -1 
+   fat[boot-FSNext].next != CLUST_FREE) {
pwarn(Next free cluster in FSInfo block (%u) not 
free\n,
  boot-FSNext);
if (ask(1, fix))
Index: newfs_msdos/newfs_msdos.c
===
RCS file: /cvs/src/sbin/newfs_msdos/newfs_msdos.c,v
retrieving revision 1.20
diff -u -p -r1.20 newfs_msdos.c
--- newfs_msdos/newfs_msdos.c   18 May 2010 04:41:14 -  1.20
+++ newfs_msdos/newfs_msdos.c   21 Oct 2013 09:48:48 -
@@ -626,7 +626,7 @@ main(int argc, char *argv[])
mk4(img, 0x41615252);
mk4(img + bpb.bps - 28, 0x61417272);
mk4(img + bpb.bps - 24, 0x);
-   mk4(img + bpb.bps - 20, bpb.rdcl);
+   mk4(img + bpb.bps - 20, 0x);
mk2(img + bpb.bps - 2, DOSMAGIC);
} else if (lsn = bpb.res  lsn  dir 
   !((lsn - bpb.res) %

Re: installboot invalid boot record signature, yaifo

[Kenneth R Westerback]

On Tue, Sep 24, 2013 at 09:31:52PM +0200, Jona Joachim wrote:
 Hi,
 I'm currently patching yaifo to make it work with -CURRENT. The build is
 going fine, however I'm stuck at an installboot error which I don't
 understand.
 
 /usr/bin/sudo /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot
 /dev/rvnd0c
 boot: /mnt/boot proto: /usr/mdec/biosboot device: /dev/rvnd0c
 installboot: disklabel type unknown

Fascinating. This error occurs when d_type is 0 in the disklabel. i.e. it
hasn't been set to one of DTYPE_ST506, _ESDI, _FLOPPY, etc. As you seem 
to using vnd I would expect d_type to be set to DTYPE_VND. But 
somehow the disklabel you are reading does not have this field 
initialized.

Do you know how the disklabel was created?

 Ken

 /mnt/boot is 9 blocks x 8192 bytes
 fs block shift 1; part offset 0; inode block 32, offset 936
 master boot record (MBR) at sector 0
 installboot: invalid boot record signature (0x) @ sector 0
 
 I don't understand why installboot fails here and I can't find a reference
 to the error.
 Can anybody explain to me what is going wrong?
 You can find the whole log attached.
 
 Best regards,
 Jona
 
 [demime 1.01d removed an attachment of type application/octet-stream which 
 had a name of make2.log]

Re: Verified OS concerns

[Kenneth R Westerback]

On Thu, Sep 19, 2013 at 10:29:39PM +0200, josef.win...@email.de wrote:
 Does OpenBSD plan to varify its (main) components, to
 reach the level of zero-bug software?

No. Zeno convinced us that you can't get there from here.

 
 If not, isn't there any concern that (future) varified OS
 will render OBSD redundant one day?

No. Think of it as evolution in action.

 Ken

Re: cvsync, rsync

[Kenneth R Westerback]

On Tue, Sep 17, 2013 at 03:22:16PM +, hru...@gmail.com wrote:
 I wrote to the list. If you have something to say about the thema,
 then please to the list. Your impolite mails are not welcome in 
 my mailbox.
 
 Rodrigo.

And your endless meanderings around the pointless questions you pose
are not welcome on the list. They certainly have NOTHING to do with
OpenBSD.

 Ken

 
 Jan Stary h...@stare.cz wrote:
 
  On Sep 17 13:21:04, hru...@gmail.com wrote:
   Raimo Niskanen raimo+open...@erix.ericsson.se wrote:
   
When you have two different real world contents the collision 
probability
is just that; 2^-160 for SHA-1. It is when you deliberately craft a
second content to match a known hash value there may be weaknesses
in cryptographic hash functions, but this is not what rsync nor Git
does, as Marc Espie pointed out in this thread.
   
   You have strings A and B, and you know only that hash(A)=hash(B): what
   is the probability that A=B? 2^-160?  
 
  No. The probability that A!= B is 2^-160.
 
  However, this is irrelevant to the problem you are describing.
  Please don't enbarass yourself any further and take this silly
  issue somewhere else; preferably to your English teacher.

Re: cvsync, rsync

[Kenneth R Westerback]

On Tue, Sep 17, 2013 at 06:18:48PM +, hru...@gmail.com wrote:
 Kenneth R Westerback kwesterb...@rogers.com wrote:
 
  And your endless meanderings around the pointless questions you pose
  are not welcome on the list. They certainly have NOTHING to do with
  OpenBSD.
 
 What you say in the last sentence is exactly what I hope. One
 of my questions was:
 
 This is a conjecture. Do you have a proof that the probability is so
 small? For me it is difficult to accept it. Is this conjecture used
 elsewhere?
 
 Rodrigo.

Wow. Missing the point again. Please go away. Bother some non-OpenBSD
list. As with others I am torn between recommending an english-as-a-second
language list, or a math-for-idiots list. OpenBSD lists provide neither
service.

In any case. PLEASE GO AWAY.

 Ken

Re: cvsync, rsync

[Kenneth R Westerback]

On Sat, Sep 14, 2013 at 01:59:50PM +, hru...@gmail.com wrote:
 Dear Sirs!
 
 I have a question, perhaps a little of-topic, but it arose as I
 read about cvsync in openbsd web page. And OpenBsd people sure know
 a lot about cryptography :)
 
 Does rsync suppose that a part of a file in the server is equal to
 a part of a file in the client, if a hash value of these parts are
 equal?
 
 Does cvsync do the same?
 
 Is this reliable? Mathematicaly not a catastrophe? (equal if the
 images under a non-injective function are equal)?
 
 Is there a reliable way to make a local copy of the repository and
 update it from time to time (I have only very elementary knowledge 
 about cvs and few experience)?

People use cvsync or rsync to create/maintain a local copy or copies
of the repository. I use cvsync to sync one repository with an
external source and then run cvsyncd on that box if I want repositories
on other local machines.

Not sure what your 'reliable' metrics are, but works for me.

 Ken

 
 Thanks
 Rodrigo

Re: How does one use adduser in OpenBSD (stuck inEnter username[] loop)?

[Kenneth R Westerback]

On Sat, Sep 14, 2013 at 06:41:58PM -0400, Jeffrey Walton wrote:
 I'm trying to add myself to sudoers. I used `su -` to get root, and
 then `adduser jwalton sudo`.
 
 Now I'm stuck a loop of:
 
   Enter username[]:
 
 When I try and add my name, I'm told its there. When I try to RETURN
 (no name), I looped back to the prompt. I have to break out with a ^C.
 
 After the ^C break and exit from root, I'm told I'm not in sudoers again.
 
 How does one use adduser in OpenBSD?
 

rtfm?

adduser(8) should explain things. Looking at the synopsis it's not clear
what you typed would do. Certainly I can't see such a command line in
the examples section.

If you're just working with sudoers, perhaps you want visudo(8) and not
adduser(8).

 Ken

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

[Kenneth R Westerback]

Geez, not much changed in the 89 years between now and 2102. :-)

 Ken

Re: 5.3 Installer Hangs After Entering Netmask (Broadcom NIC)

[Kenneth R Westerback]

On Sun, Sep 01, 2013 at 10:45:50PM -0700, andrew fabbro wrote:
 I have a Shuttle SD11G5, which is a small Celeron-based PC (1.5Ghz Celeron,
 2GB RAM, a couple SATA drives).
 
 The OpenBSD 5.3 installer consistently hangs after I enter the Netmask for
 the onboard NIC.
 
 I'm booting the 32-bit x86 install53.iso.  I start configuring bge0 (which
 is a BCM5789) and after IPv4 address for bge0, the installer asks for
 Netmask and after I enter it (255.255.255.0), the installer sits there
 forever.
 
 Same thing if I DHCP - after Issuing hostname-associated DHCP request for
 bge0 the installer hangs.
 
 I also have an Intel Pro/1000 gig-E card (82574L) in the PCI Express slot,
 which shows up on em0.  Unfortunately dmesg says couldn't map interrupt
 and I'm not offered the chance to configure it.  I haven't found anything
 useful via searching for fixing this.
 
 This box previously ran Debian Linux with no problems, so I'm skeptical
 it's a hardware problem.  The BMC578x series is listed as supported on the
 bge(4) man page.
 
 Any advice?
 

Read http://openbsd.org/report.html.

Try 5.4 snapshot or -current.

 Ken

Re: 10GBit OpenBSD Firewall

[Kenneth R Westerback]

On Mon, Sep 02, 2013 at 01:41:58PM +0200, Denis Fondras wrote:
 Hi Mike,
 
 Le 02/09/2013 13:21, Mike Belopuhov a ?crit :
  We are trying to address problems with MP networking right now,
  but due to the lack of manpower the progress is slow.
  
 
 What would you need to accelerate ? Developpers, testers, time, money,
 hardware, something else ?
 
 Denis

All of the above. If you can provide time especially I'm sure Mike would
be very interested in having more of it. :-)

 Ken

Re: bioctl replacing a failed mirror

[Kenneth R Westerback]

On Mon, Sep 02, 2013 at 07:50:41AM -0400, John Hynes wrote:
 Greetings All,
 
 I have a softraid device, sd3, which was created as follows:
 
 bioctl -c 1 -l /dev/sd0a,/dev/sd1a,/dev/sd2a softraid0
 
 The chunk sd2a failed.  bioctl shows the RAID1 as degraded, and chunk sd2a
 as OFFLINE.
 
 In order to rebuild, I'd need to set up the new sd2.  After replacing and
 zeroing the drive, I replaced the MBR with fdisk -yi /dev/sd2, which worked
 fine.  Next, I copied the disklabel from sd0 to sd2, but disklabel refused
 to write the new label, saying:
 
 disklabel: ioctl DIOCWDINFO: Open partition would move or shrink
 disklabel: unable to write label

How exactly are you copying the disklabel? Is sd2 the same size as sd0?

As always a dmesg would help. In this case by answering the latter. :-)

 Ken

 
 I could use another slot I suppose, but is there a way to label the chunk
 in the same slot and rebuild onto it that I'm missing?
 
 Thanks,
 
 -John

Re: bioctl replacing a failed mirror

[Kenneth R Westerback]

On Mon, Sep 02, 2013 at 08:20:11AM -0400, John Hynes wrote:
 On Mon, Sep 2, 2013 at 8:07 AM, Kenneth R Westerback kwesterb...@rogers.com
  wrote:
 
  On Mon, Sep 02, 2013 at 07:50:41AM -0400, John Hynes wrote:
   Greetings All,
  
   I have a softraid device, sd3, which was created as follows:
  
   bioctl -c 1 -l /dev/sd0a,/dev/sd1a,/dev/sd2a softraid0
  
   The chunk sd2a failed.  bioctl shows the RAID1 as degraded, and chunk
  sd2a
   as OFFLINE.
  
   In order to rebuild, I'd need to set up the new sd2.  After replacing and
   zeroing the drive, I replaced the MBR with fdisk -yi /dev/sd2, which
  worked
   fine.  Next, I copied the disklabel from sd0 to sd2, but disklabel
  refused
   to write the new label, saying:
  
   disklabel: ioctl DIOCWDINFO: Open partition would move or shrink
   disklabel: unable to write label
 
  How exactly are you copying the disklabel? Is sd2 the same size as sd0?
 
 
 disklabel sd0  disklabel.sd2; disklabel -R sd2 disklabel.sd0
 
 The new sd2 is identical to the old, which is identical to the other
 disks.

Further information should be elicited by running a kernel with the diff
below. Which should at least tell us the (first) partition being rejected,
and whether it is the size or location that is problematic.

Coincidentally I'm working in this exact code, so there are some bonus
fixes in there.

 Ken


Index: subr_disk.c
===
RCS file: /cvs/src/sys/kern/subr_disk.c,v
retrieving revision 1.151
diff -u -p -r1.151 subr_disk.c
--- subr_disk.c 8 Aug 2013 23:25:06 -   1.151
+++ subr_disk.c 2 Sep 2013 13:40:03 -
@@ -645,22 +645,30 @@ setdisklabel(struct disklabel *olp, stru
 
/* XXX missing check if other dos partitions will be overwritten */
 
-   while (openmask != 0) {
-   i = ffs(openmask) - 1;
-   openmask = ~(1  i);
-   if (nlp-d_npartitions = i)
-   return (EBUSY);
+   for (i = 0; i  MAXPARTITIONS; i++) {
opp = olp-d_partitions[i];
npp = nlp-d_partitions[i];
-   if (DL_GETPOFFSET(npp) != DL_GETPOFFSET(opp) ||
-   DL_GETPSIZE(npp)  DL_GETPSIZE(opp))
-   return (EBUSY);
+   if (openmask  (1  i)) {
+   if (DL_GETPOFFSET(npp) != DL_GETPOFFSET(opp)) {
+   printf(Can't move open partition '%c'
+from offset %lld to offset %lld\n,
+   'a' + i, DL_GETPOFFSET(opp),
+   DL_GETPOFFSET(npp));
+   return (EBUSY); 
+   }
+   if (DL_GETPSIZE(npp)  DL_GETPSIZE(opp)) {
+   printf(Can't shrink open partition '%c'
+   from %lld sectors to %lld sectors\n,
+   'a' + i, DL_GETPSIZE(opp),
+   DL_GETPSIZE(npp));
+   return (EBUSY);
+   }
+   }
/*
 * Copy internally-set partition information
 * if new label doesn't include it. XXX
 */
if (npp-p_fstype == FS_UNUSED  opp-p_fstype != FS_UNUSED) {
-   npp-p_fstype = opp-p_fstype;
npp-p_fragblock = opp-p_fragblock;
npp-p_cpg = opp-p_cpg;
}

Re: bioctl replacing a failed mirror

[Kenneth R Westerback]

On Mon, Sep 02, 2013 at 08:20:11AM -0400, John Hynes wrote:
 On Mon, Sep 2, 2013 at 8:07 AM, Kenneth R Westerback kwesterb...@rogers.com
  wrote:
 
  On Mon, Sep 02, 2013 at 07:50:41AM -0400, John Hynes wrote:
   Greetings All,
  
   I have a softraid device, sd3, which was created as follows:
  
   bioctl -c 1 -l /dev/sd0a,/dev/sd1a,/dev/sd2a softraid0
  
   The chunk sd2a failed.  bioctl shows the RAID1 as degraded, and chunk
  sd2a
   as OFFLINE.
  
   In order to rebuild, I'd need to set up the new sd2.  After replacing and
   zeroing the drive, I replaced the MBR with fdisk -yi /dev/sd2, which
  worked
   fine.  Next, I copied the disklabel from sd0 to sd2, but disklabel
  refused
   to write the new label, saying:
  
   disklabel: ioctl DIOCWDINFO: Open partition would move or shrink
   disklabel: unable to write label
 
  How exactly are you copying the disklabel? Is sd2 the same size as sd0?
 
 
 disklabel sd0  disklabel.sd2; disklabel -R sd2 disklabel.sd0
 
 The new sd2 is identical to the old, which is identical to the other
 disks.

Then the output from 'disklabel sd0', 'disklabel sd2', 'fdisk sd0' and
'fdisk sd2' would be useful. I suspect the 'c' partition location/size
is the cause of the confusion. I thought 'c' was ignored by '-R', but
a quick glance at the code does not support that. :-)

 Ken

 
 
 
  As always a dmesg would help. In this case by answering the latter. :-)
 
 
 Here's the dmesg from earlier, before the drive croaked:
 
 OpenBSD 5.3 (GENERIC.MP) #0: Thu Aug 15 09:24:05 EDT 2013
 r...@flotsam.primebuchholz.com:/usr/src/sys/arch/amd64/compile/
 GENERIC.MP
 real mem = 17160536064 (16365MB)
 avail mem = 16681234432 (15908MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9f000 (40 entries)
 bios0: vendor American Megatrends Inc. version 3.0a date 05/07/2013
 bios0: Supermicro H8SGL
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S1 S4 S5
 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SRAT SSDT EINJ BERT ERST HEST
 acpi0: wakeup devices PC02(S4) PC03(S4) PC04(S4) PC05(S4) PC06(S4) PC07(S4)
 PC09(S4) PC0A(S4) PC0B(S4) PC0C(S4) SBAZ(S4) PSKE(S4) PSMS(S4) ECIR(S4)
 P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) UHC5(S4) UHC6(S4) UHC7(S4)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 32 (boot processor)
 cpu0: AMD Opteron(tm) Processor 6344 , 2600.38 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,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
 64b/line 16-way L2 cache, 12MB 64b/line 128-way L3 cache
 cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully
 associative
 cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully
 associative
 cpu0: apic clock running at 199MHz
 cpu1 at mainbus0: apid 33 (application processor)
 cpu1: AMD Opteron(tm) Processor 6344 , 249.48 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,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
 cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
 64b/line 16-way L2 cache, 12MB 64b/line 128-way L3 cache
 cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully
 associative
 cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully
 associative
 cpu2 at mainbus0: apid 34 (application processor)
 cpu2: AMD Opteron(tm) Processor 6344 , 249.45 MHz
 cpu2:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
 cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
 64b/line 16-way L2 cache, 12MB 64b/line 128-way L3 cache
 cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully
 associative
 cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully
 associative
 cpu3 at mainbus0: apid 35 (application processor)
 cpu3: AMD Opteron(tm) Processor 6344 , 249.47 MHz
 cpu3:
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1
 cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB
 64b/line 16-way L2 cache, 12MB 64b/line 128-way L3 cache
 cpu3: ITLB

Re: What should we look before buying a laptop?

[Kenneth R Westerback]

On Sun, Aug 25, 2013 at 10:19:11PM -0600, Michael Paul Zamot wrote:
 Hello, my name is Michael Paul Zamot, I'm from Costa Rica.
 I'm using OpenBSD since two months ago and I'm in love with it.
 
 I'm planning buying a laptop, perhaps a screen of 11 or 12 inches.
 
 I would like to know if you know about a compatible model, under $400.
 What should I look before buying one? Any recommendations?
 
 With recent addition of AMD KMS and Intel KMS I don't think video
 would be an issue.

Stilll must avoid nvidia.

 Ken

 
 Thanks!

Re: In some man pages Mb means MB, in others it means Mb/s

[Kenneth R Westerback]

On Mon, Aug 26, 2013 at 03:06:22PM +0200, Erling Westenvik wrote:
 On Mon, Aug 26, 2013 at 11:27:36AM +, Stuart Henderson wrote:
  you will then end up with some of them switching to dreadful MiB etc. ;)
 
 Kinda off topic and I take it you were being sarcastic, but your
 mentioning of the dreadful MiB reminded me about the LibreOffice
 spreadsheet I'm using to calculate from GiB/GB to sectors so that I can
 have disklabel(8) partition my harddisks according to standard units.
 
 Are there strong opinions against following standards and start
 converting to the proper terms for gigabytes (decimal, base 10, 1GB =
 1000^3 bytes) and gibibytes (binary, base 2, 1 GiB = 1024^3 bytes)?

There are violent and possibly homicidal opinions against such a
move. Mine being one. gibi is gibberish.

 Ken

 
 After all it's been a while since it was logical (!) to infer that since
 1024^1 (kibi) is *almost* 1000^1 (kilo), then 1024^3 (gibi) must
 *almost* be 1000^3 (giga).. ;)
 
 Personally I would love to see disklabel(8) default to display sizes in
 base-10 and with something like an optional -i or -2 switch to display
 information in the old (current) base 2 definition. At least it would be
 nice if it were using proper units - like GiB instead of GB.
 
 Cheers,
 
 Erling

Re: OpenBSD pxe automated install

[Kenneth R Westerback]

On Mon, Aug 12, 2013 at 08:59:27PM +0200, Lo?c BLOT wrote:
 Hello @misc.
 
 Today i'm working on automated deploy with PXE. I have successful found
 and made automated PXE install on Debian with pxelinux.
 
 I know OpenBSD have a pxe boot image to netinstall the system
 http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution
 -environment/
 
 Is there any options to automate the installation ?
 I want a machine to boot on bsd.rd, read a configuration file (url
 passed by etc/boot.conf, for example) and install with the read
 parameters.
 Is there any issue to do this or i do it myself ?
 
 Thanks for advance
 --
 Best regards,
 Lo??c BLOT,
 UNIX systems, security and network expert
 http://www.unix-experience.fr
 
 [demime 1.01d removed an attachment of type application/pgp-signature which 
 had a name of signature.asc]
 

There is no 'offical' method. If you check the mailing list archives you'll
find a few people have come up with something that works for them.

 Ken

Re: C partition of type 4.2BSD

[Kenneth R Westerback]

On Fri, Aug 09, 2013 at 11:38:16AM +0200, Federico Giannici wrote:
 I don't know how I made it (probably in previous releases of OS),
 but now I have a disk with the following disklabel:
 
 # /dev/rsd2c:
 type: SCSI
 disk: SCSI disk
 label: ST1000DM003-9YN1
 duid: b0e3fc037df87899
 flags:
 bytes/sector: 512
 sectors/track: 63
 tracks/cylinder: 255
 sectors/cylinder: 16065
 cylinders: 121601
 total sectors: 1953525168
 boundstart: 64
 boundend: 1953520065
 drivedata: 0
 
 16 partitions:
 #size   offset  fstype [fsize bsize  cpg]
   a:   1953519936   64  4.2BSD   8192 655361 # /bu
   c:   19535251680  4.2BSD   2048 163841
 
 
 As you can see the c partition is not of type unused, and some
 commands complain of this.
 
 I wasn't able to change this situation. I tried with disklabel -E
 sd2, disklabel -d sd2, disklabel -R sd2 proto (with a proper
 proto file), but nothing changed.
 
 What is the proper way to handle this?
 Please note that a partition contains data that must be preserved
 (I umounted that partition before all disklabel commands).
 
 The system is a 5.3 amd64, and sd2 is a normal SATA disk.
 
 Thanks.
 

disklabel(8) contains a description of the 'z' command available
in the -E mode. It should kill 'c' dead. Just add 'a' back with the
same parameters it had brfore.

Not that Nick's solution isn't more fun!

 Ken

Re: C partition of type 4.2BSD

[Kenneth R Westerback]

On Fri, Aug 09, 2013 at 04:54:01PM -0400, Kenneth R Westerback wrote:
 On Fri, Aug 09, 2013 at 11:38:16AM +0200, Federico Giannici wrote:
  I don't know how I made it (probably in previous releases of OS),
  but now I have a disk with the following disklabel:
  
  # /dev/rsd2c:
  type: SCSI
  disk: SCSI disk
  label: ST1000DM003-9YN1
  duid: b0e3fc037df87899
  flags:
  bytes/sector: 512
  sectors/track: 63
  tracks/cylinder: 255
  sectors/cylinder: 16065
  cylinders: 121601
  total sectors: 1953525168
  boundstart: 64
  boundend: 1953520065
  drivedata: 0
  
  16 partitions:
  #size   offset  fstype [fsize bsize  cpg]
a:   1953519936   64  4.2BSD   8192 655361 # /bu
c:   19535251680  4.2BSD   2048 163841
  
  
  As you can see the c partition is not of type unused, and some
  commands complain of this.
  
  I wasn't able to change this situation. I tried with disklabel -E
  sd2, disklabel -d sd2, disklabel -R sd2 proto (with a proper
  proto file), but nothing changed.
  
  What is the proper way to handle this?
  Please note that a partition contains data that must be preserved
  (I umounted that partition before all disklabel commands).
  
  The system is a 5.3 amd64, and sd2 is a normal SATA disk.
  
  Thanks.
  
 
 disklabel(8) contains a description of the 'z' command available
 in the -E mode. It should kill 'c' dead. Just add 'a' back with the
 same parameters it had brfore.
 
 Not that Nick's solution isn't more fun!
 
  Ken
 

Or it could be a nifty snare in the kernel that is accidentally preserving
info that should not be preserved. This is probably not the best patch, but
it does let me use 'disklabel -e sd2' to set 'c' to 'unused'.

 Ken

Index: subr_disk.c
===
RCS file: /cvs/src/sys/kern/subr_disk.c,v
retrieving revision 1.150
diff -u -p -r1.150 subr_disk.c
--- subr_disk.c 3 Jul 2013 15:21:40 -   1.150
+++ subr_disk.c 10 Aug 2013 03:23:26 -
@@ -655,6 +674,8 @@ setdisklabel(struct disklabel *olp, stru
if (DL_GETPOFFSET(npp) != DL_GETPOFFSET(opp) ||
DL_GETPSIZE(npp)  DL_GETPSIZE(opp))
return (EBUSY);
+   if (i == RAW_PART)
+   continue;
/*
 * Copy internally-set partition information
 * if new label doesn't include it. XXX

Re: Pfsync bulk for 6 states takes 13 minutes

[Kenneth R Westerback]

On Fri, Aug 02, 2013 at 12:04:24PM +0200, Dariusz Binkul wrote:
 Hello,
 
 I have 2 openbsd systems (OpenBSD 5.3 (GENERIC.MP) #62: Tue Mar 12 18:21:20
 MDT 2013) in active-backup configuration.
 During boot of OS, pfsync bulk takes 13 minutes to sync with master server
 no matter how many states there are to sync.
 
 I've reproduced this problem in my testing environment. Even with no
 traffic (only 6 states in PF State Table) pfsync bulk took 13 minutes.

As you have a test setup, you might get more immediate attention
if you reproduced the problem on the latest 5.4 snapshot.

 Ken

Re: 4k-sector drives

[Kenneth R Westerback]

On Sat, Aug 03, 2013 at 01:09:24AM +0200, Robert wrote:
 On Sun, 21 Jul 2013 13:19:11 -0400
 Kenneth R Westerback kwesterb...@rogers.com wrote:
  Disks with logical sector sizes other than 512-bytes are supported.
  I am unaware of any outstanding issues with support for 4K sector
  devices.
   Ken
 
 It's not possible to create softraid volumes (e.g. encryption) on 4k disks.
 See also: http://marc.info/?l=openbsd-miscm=136228918607382
 
 http://www.openbsd.org/cgi-bin/man.cgi?query=bioctlsektion=8arch=apropos=0manpath=OpenBSD+Current
 Only devices with 512-byte sectors are supported.
 
 While some disks emulate their 4k sectors as 512b, some don't.
 E.g., I have a WD My Book 1140 3TB external USB disk, which reports 4k. 
 Softraid doesn't work with it, I have to use vnd instead (for encryption).
 

softraid volume are not 'disks' in the context of my statement. You
are correct that those volumes do not support 4K-byte sector devices.
Largely because the original author did not believe in the existance
of 4K-byte sector devices devices. :-)

 Ken

 # /dev/rsd6c:
 type: SCSI
 disk: SCSI disk
 label: My Book 1140
 duid: 
 flags:
 bytes/sector: 4096
 sectors/track: 63
 tracks/cylinder: 255
 sectors/cylinder: 16065
 cylinders: 45599
 total sectors: 732558336
 boundstart: 64
 boundend: 732547935
 drivedata: 0 
 
 kind regards,
 Robert

Re: Automatically direct to serial console BEFORE passphrase prompt on FDE (i386)

[Kenneth R Westerback]

On Mon, Jul 22, 2013 at 07:49:21AM -0400, Jiri B wrote:
 On Mon, Jul 22, 2013 at 09:36:25PM +1000, Joel Sing wrote:
  Otherwise you could use a modified boot(8), which defaulted to serial - see 
  constab in sys/arch/i386/stand/boot/conf.c for example.
 
 What about installboot to have an option telling it to switch to serial
 by default (still keeping possibility to override funcionality with
 /etc/boot.conf)? This would save us from kung-fu with tiny 'a' partition
 holding /etc/boot.conf...
 
 jirib

You can Kung Fu it now or Kung Fu it later. More flags always makes
developers cringe. Fiddling with partitions seems way easier. :-)

 Ken

Re: 4k-sector: wrong sector size in disk label

[Kenneth R Westerback]

On Mon, Jul 22, 2013 at 01:56:16PM +0200, David Vasek wrote:
 Hello.
 
 From the experiment below it seems that the kernel modifies its
 knowledge of a sector size of a disk hardware according to what can
 be found in the disk label sector. It does so even if the value
 found does not make sense hardware-wise and in spite of a sector
 size the hardware device driver works with. It can make the device
 completly inaccessible. The disklabel(8) command doesn't allow to
 set/change the sector size value even if it were accessible.

The kernel obtains the sector size from the hardware device whenever
the disklabel is created. It does trust the disklabel it reads from
the disk. People can abuse that trust. The interesting gyrations to
automatically convert all the fields in the disklabel from one
sector size to another are, well, *interesting*. And have never been
considered useful since there is no general mechanisms for the kernel
to read incorrectly blocked data from the disk.

 
 Such situation also occurs if the disk label is read from a sector
 where a disk label is not expected - this was already a subject of
 my previous report.

Still working on puzzling out that report.

 
 It effectively means that if there is wrong data on the drive, you
 don't have a chance to analyze the situation or fix it. You can't
 even view the fdisk (MBR) partition table.

Correct.

 
 In the following example I copied an image of a 512-byte sector USB
 drive (sd5) to a clean 4k-sector USB drive (sd4). The source drive
 contained an OpenBSD fdisk partition with a disklabel partition and
 a functional filesystem. After that, kernel can't read any data from
 that 4k-sector drive, causing errors at umass(4) driver level.
 Please note the output of disklabel sd4 before and after copying
 the image and the difference in sector size there.

Bits directly plopped from a device with one sector size to another
device with a different sector size all pass through a gate having
a large sign over it containing the words: Lasciate ogne speranza,
voi ch'intrate.

 
 My guess is that this issue could be related to this one about a year ago:
 http://marc.info/?l=openbsd-miscm=134027998905971w=2

Nope. That problem had to do with wd(4) not supporting 4K sectors.
Only sd(4) will even make an attempt to handle sector sizes other
than 512 bytes.

 Ken

Re: 4k-sector: wrong sector size in disk label

[Kenneth R Westerback]

On Mon, Jul 22, 2013 at 06:15:38PM +0200, David Vasek wrote:
 On Mon, 22 Jul 2013, Kenneth R Westerback wrote:
 
 On Mon, Jul 22, 2013 at 01:56:16PM +0200, David Vasek wrote:
 Hello.
 
 From the experiment below it seems that the kernel modifies its
 knowledge of a sector size of a disk hardware according to what can
 be found in the disk label sector. It does so even if the value
 found does not make sense hardware-wise and in spite of a sector
 size the hardware device driver works with. It can make the device
 completly inaccessible. The disklabel(8) command doesn't allow to
 set/change the sector size value even if it were accessible.
 
 The kernel obtains the sector size from the hardware device whenever
 the disklabel is created. It does trust the disklabel it reads from
 the disk. People can abuse that trust. The interesting gyrations to
 automatically convert all the fields in the disklabel from one
 sector size to another are, well, *interesting*. And have never been
 considered useful since there is no general mechanisms for the kernel
 to read incorrectly blocked data from the disk.
 
 Well, it trusts the disk label in what it says the sector size is,
 but on the other hand it ignores what the disklabel says about the
 total number of sectors (and the size of the 'c' partition).
 Strange.

Not at all. It always ensures the magic 'c' partition reflects the
current hardware provided information. The other partitions sizes
are in the units of the original disklabel, and are left alone with
the original sector size so the two are consistant.

 
 Such situation also occurs if the disk label is read from a sector
 where a disk label is not expected - this was already a subject of
 my previous report.
 
 Still working on puzzling out that report.
 
 Don't hesitate to ask if anything is not clear in that report.
 
 It effectively means that if there is wrong data on the drive, you
 don't have a chance to analyze the situation or fix it. You can't
 even view the fdisk (MBR) partition table.
 
 Correct.
 
 One would hope there is a chance to edit (fix) the sector size value
 with disklabel(8). But obviously, once it has been changed, the disk
 label cannot be written to disk again.
 
 Bits directly plopped from a device with one sector size to another
 device with a different sector size all pass through a gate having
 a large sign over it containing the words: Lasciate ogne speranza,
 voi ch'intrate.
 
 In some cases disks can be connected to computers in more than on
 way and in each way its host will be presented with a different
 sector size. I made an attemt to simulate it. I just didn't expect
 it could silently influence hardware drivers.

Doesn't influence hardware drivers, outside of the drivers doing
what the hardware tells them. If the disk tells one story when
plugged in via A and another story when plugged in via B I not sure
how A or B are supposed to determine they should ignore what they
are told.

 
 My guess is that this issue could be related to this one about a year ago:
 http://marc.info/?l=openbsd-miscm=134027998905971w=2
 
 Nope. That problem had to do with wd(4) not supporting 4K sectors.
 Only sd(4) will even make an attempt to handle sector sizes other
 than 512 bytes.
 
 I don't think so. If I see the number of sector the drive reported
 both when inside an USB enclosure and connected directly to SATA
 controller, I believe that it was a standard 512-byte sector SATA
 hard drive and only the kernel got fooled by the disk label it found
 on it.

I think so since I have the subsquent email trail with the submitter
and others, and that is what we concluded to close that issue. His
bios had no AHCI option for the disk controller, so the disk always
appeared as a wd(4) when plugged in directly. And wd(4) does not
support 4K size sectors. When plugged in via usb(4) it appears as
an sd(4) disk and worked fine.

 
 In fact, that was the real life situation I wanted to model in my
 experiments - what will happen if the disk is taken out from a USB
 enclosure which pretends it to be a 4k-sector drive and is connected
 to a SATA controller as a standard 512-byte/sector drive.

It won't work, at least in the sense that you could reliably access
existing information. Even worse if you go the other way. And it's
not intended to work.

 Ken

Re: 4k-sector drives

[Kenneth R Westerback]

On Sun, Jul 21, 2013 at 04:55:35PM +0200, David Vasek wrote:
 Hello misc@,
 
 are disks with logical sector sizes other than 512-bytes supported?
 I can get basic functionality with a 4k-sector drive, still there
 are some flaws. Does it make sense to report these bugs now, or is
 it too early?
 
 Regards,
 David
 

Disks with logical sector sizes other than 512-bytes are supported.
I am unaware of any outstanding issues with support for 4K sector
devices.

 Ken

Re: 4k-sector NTFS can't be mounted

[Kenneth R Westerback]

On Sun, Jul 21, 2013 at 11:45:47PM +0200, David Vasek wrote:
 On Sun, 21 Jul 2013, Kenneth R Westerback wrote:
 
 A 4k-sector NTFS filesystem
 can't be mounted as of 5.3/i386.
 
 At least one person is using a 4K-sector disk with NTFS partition(s)
 without problems. So I suspect something local to your setup is causing
 the problem by traversing new and exciting code paths.
 
 The filesystem was on external USB hard drive, as it came from the
 manufacturer, which is HGST, formerly Hitachi GST, now part of WD.
 The filesystem didn't work with OpenBSD 5.3/i386, but Windows XP
 seemed happy with it. The filesystem was empty and from original 4
 TB it could be compressed with bzip2 to under 3 MB. I can send the
 compressed image to you if you want to play with it and have extra
 disk space.
 
 Regards,
 David
 

No need. I've got my own 4K-byte sector, 4TB USB disks with NTFS
partitions. And an absolute disinterest in NTFS. :-)

 Ken

Re: current/macppc on Mac Mini

[Kenneth R Westerback]

On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
  What troubles me is that whatever device (device name) I try,
  it is the 'ofwboot' which is not found.
  I don't mind calling my disk 'cd' in the boot sequence
  or altering the devaliases, or setenv boot-device cd:,ofwboot,
  but that doesn't work either, as shown above.
  How can I make sure that the installer
  has actually put the ofwboot on my disk?
 
 I mean, the ofwboot is supposed to be _somewhere_
 on my disk, right? Where? In the small DOS partition
 at the beginning of the disk?
 

Yes. From macppc install.md:

md_installboot() {
local _disk=$1

# If there is an MSDOS partition on the boot disk, copy ofwboot
# into it.
if fdisk $_disk | grep -q 'Signature: 0xAA55'; then
if fdisk $_disk | grep -q '^..: 06 '; then
if mount /dev/${_disk}i /mnt2 /dev/null 21; then
# Use cat to avoid holes created by cp(1)
cat /mnt/usr/mdec/ofwboot  /mnt2/ofwboot
umount /mnt2
fi
fi
fi
}

 Ken

Re: current/macppc on Mac Mini

[Kenneth R Westerback]

On Sat, Jul 20, 2013 at 08:23:35PM +0200, Jan Stary wrote:
 On Jul 20 11:23:01, kwesterb...@rogers.com wrote:
  On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
What troubles me is that whatever device (device name) I try,
it is the 'ofwboot' which is not found.
I don't mind calling my disk 'cd' in the boot sequence
or altering the devaliases, or setenv boot-device cd:,ofwboot,
but that doesn't work either, as shown above.
How can I make sure that the installer
has actually put the ofwboot on my disk?
   
   I mean, the ofwboot is supposed to be _somewhere_
   on my disk, right? Where? In the small DOS partition
   at the beginning of the disk?
   
  
  Yes. From macppc install.md:
  
  md_installboot() {
  local _disk=$1
  
  # If there is an MSDOS partition on the boot disk, copy ofwboot
  # into it.
  if fdisk $_disk | grep -q 'Signature: 0xAA55'; then
  if fdisk $_disk | grep -q '^..: 06 '; then
  if mount /dev/${_disk}i /mnt2 /dev/null 21; then
  # Use cat to avoid holes created by cp(1)
  cat /mnt/usr/mdec/ofwboot  /mnt2/ofwboot
  umount /mnt2
  fi
  fi
  fi
  }
  
 
 Ha! This seems to assume that the (fdisk) DOS partition
 is the 'i' partition in the disklabel - it is not;
 I created a [c]ustom disklabel.

It does make the assumption that the DOS partition is the first spoofed
partition, i.e. 'i'. This should probably be revisited since we relaxed
the rules on partition naming a while ago.

 
 When in the install sequence is this copy of ofwboot done?

It's done at the very end in the finish_up() function in install.sub.

 Even my real wd0i partition, which is /usr/xobj
 (untouched since install) does not contain ofwboot.

Your wd0i isn't an MBR partition.

 That leads me to speculate that this ofwboot copy
 is performed _before_ the installing user edits
 the disklabel; but perhaps at that moment,
 wd0i _is_ really the DOS partiton, and later
 I can make the disklabel what I want?

Nope. See above. :-)

 
 Or did I miss it somewhere in the macppc install documentation
 to leave 'i' alone so that ofwboot gets copied to the right place?

In INSTALL.macppc:

If you have DOS or Linux partitions defined on the disk, these will
usually show up as 'i', 'j', and so on.

and

If the disk is partitioned using MBR, the bootloader will be
automatically installed if you setup a small (a few MB) MSDOS
partition as position `i' in the label.

 
 Anyway, I tried getting to that copy ofwboot now, as follows: 
 I enlarged the disklabel-maintained area to the whole disk ('b')
 and created a partion for the DOS piece of the disk. Looking at
 
 Disk: wd0 geometry: 155061/16/63 [156301488 Sectors]
 Offset: 0 Signature: 0xAA55
 Starting Ending LBA Info:
  #: id  C   H   S -  C   H   S [   start:size ]
 ---
 *0: 06  0   0   2 -  2   0  33 [   1:2048 ] DOS  
 32MB  
  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
   
  3: A6  4   1   2 - 155060  15  63 [4096:   156297392 ] OpenBSD   
   
 
 I made the DOS partition start at 512 (and then 1024
 and then everything under 4096 wherethe obsd part starts),
 but never could I mount that DOS partition ...
 
 I will reinstall again, leaving the [a]uto disklabel untouched.
 

Good plan.

 Ken

Re: dhcp address in /etc/hosts

[Kenneth R Westerback]

On Sat, Jul 20, 2013 at 08:42:21PM -0400, Sam Fourman Jr. wrote:
 I don't like this diff.
 
 
  But perhaps because I totally hate that the installer is placing that
  name there.  I believe that dynamically learned names should not be
  saved in that fashion.
 
 
 
 I don't really get a vote as i'm not a developer, however cookies to anyone
 who fixes this the correct way.
 
 -- 
 
 Sam Fourman Jr.
 

Define 'correct way'. :-)

 Ken

Re: Automatically direct to serial console BEFORE passphrase prompt on FDE (i386)

[Kenneth R Westerback]

On Fri, Jul 19, 2013 at 06:15:49PM +0200, Erling Westenvik wrote:
 Maybe a stupid question, but is it possible to have a i386 machine
 configured with FDE to automatically direct to serial console BEFORE the
 passphrase prompt?
 
 The steps below require the machine to have an attached keyboard
 and monitor initially.
 
 If I hit Enter at the passphrase prompt, the boot prompt will
 appear and let me switch to serial console:
 
  set tty com0
 
 From the serial console I can the type:
 
  boot sr0a:/bsd
 
 which gives me the passphrase prompt again on the console machine.
 
 It would be really nice to be able to boot a headless FDE. Am I missing
 something? Is this design by intention?
 
 Cheers,
 
 Erling
 

There's always boot.conf(5), into which you can put 'set tty com0' last
I checked.

 Ken

Re: panic: ext2fs_dirbadentry

[Kenneth R Westerback]

On Wed, Jul 17, 2013 at 12:11:34PM +0400, Sergey Bronnikov wrote:
 Bug was catched by fsfuzzer. Probably that bug cannot be
 found in real life with real usecase, but anyway it is a bug.

Why? A failed consistency check means a bad fs, not necessarily a
bug. inode out of range seems clear. A tool which creates initial
(valid) filesystem images and then manipulates their binary format
and structure for detecting flaws/bugs/design problems in the
parsing/handling code is almost certain to eventually create
something that blows up I would think.

So, can you please explain why failing this consistency check
indicates a bug in the code?

Since fsfuzzer is supposed to create logs and allow reproducible
tests, sharing those logs and directions on reproducing the failure
would also be nice.

 Ken

 
 panic: ext2fs_dirbadentry
 Stopped atDebugger+0x5:   leave
 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
 DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
 ddb Debugger() at Debugger+0x5
 panic() at panic+0xe4
 ext2fs_lookup() at ext2fs_lookup+0x68f
 VOP_LOOKUP() at VOP_LOOKUP+0x2c
 vfs_lookup() at vfs_lookup+0x271
 namei() at namei+0x21c
 vn_open() at vn_open+0x91
 doopenat() at doopenat+0x125
 syscall() at syscall+0x162
 --- syscall (number 5) ---
 end of kernel
 end trace frame: 0x, count: -9
 acpi_pdirpa+0x4253fa:
 
 Full logs are below:
 
 OpenBSD 5.4-beta (GENERIC) #0: Mon Jul 15 23:06:59 MSK 2013
 es...@.xxx:/usr/src/sys/arch/amd64/compile/GENERIC
 real mem = 4168839168 (3975MB)
 avail mem = 4050149376 (3862MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries)
 bios0: vendor LENOVO version 7VET80WW (3.10 ) date 10/02/2009
 bios0: LENOVO 406257G
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT
 acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) 
 EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) 
 EHC1(S3) HDEF(S4)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpiec0 at acpi0
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 798.13 MHz
 cpu0: 
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF
 cpu0: 6MB 64b/line 16-way L2 cache
 cpu0: smt 0, core 0, package 0
 cpu0: apic clock running at 266MHz
 cpu at mainbus0: not configured
 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
 ioapic0: misconfigured as apic 2, remapped to apid 1
 acpimcfg0 at acpi0 addr 0xe000, bus 0-63
 acpihpet0 at acpi0: 14318179 Hz
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus -1 (AGP_)
 acpiprt2 at acpi0: bus 2 (EXP0)
 acpiprt3 at acpi0: bus 3 (EXP1)
 acpiprt4 at acpi0: bus 4 (EXP2)
 acpiprt5 at acpi0: bus 5 (EXP3)
 acpiprt6 at acpi0: bus 13 (EXP4)
 acpiprt7 at acpi0: bus 21 (PCI1)
 acpicpu0 at acpi0: C3, C2, C1, PSS
 acpipwrres0 at acpi0: PUBS
 acpitz0 at acpi0: critical temperature is 127 degC
 acpitz1 at acpi0: critical temperature is 100 degC
 acpibtn0 at acpi0: LID_
 acpibtn1 at acpi0: SLPB
 acpibat0 at acpi0: BAT0 model 42T4620 serial   929 type LION oem Panasonic
 acpibat1 at acpi0: BAT1 not present
 acpiac0 at acpi0: AC unit online
 acpithinkpad0 at acpi0
 acpidock0 at acpi0: GDCK not docked (0)
 cpu0: Enhanced SpeedStep 798 MHz: speeds: 2801, 2800, 2133, 1600, 800 MHz
 pci0 at mainbus0 bus 0
 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07
 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07
 intagp0 at vga1
 agp0 at intagp0: aperture at 0xd000, size 0x1000
 inteldrm0 at vga1
 drm0 at inteldrm0
 inteldrm0: 1920x1200
 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
 wsdisplay0: screen 1-5 added (std, vt100 emulation)
 Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured
 Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured
 em0 at pci0 dev 25 function 0 Intel ICH9 IGP M rev 0x03: msi, address 
 00:22:68:18:b1:0f
 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20
 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21
 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22
 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: msi
 azalia0: codecs: Conexant CX20561, 0x/0x, using Conexant CX20561
 audio0 at azalia0
 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: msi
 pci1 at ppb0 bus 2
 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: msi
 pci2 at ppb1 bus 3
 iwn0 at pci2 dev 0 function 0 Intel WiFi Link 5100 

Re: 802.11n support

[Kenneth R Westerback]

On Sat, Jun 22, 2013 at 10:21:10AM +1000, John Tate wrote:
 I have an Atheros AR9227, there is at the moment no support for
 802.11n in the patch branch. Is there support in current or some
 unoffical patch I can apply to the source code? Support for this would
 be good.
 
 --
 www.johntate.org
 

No support in -current or any unoffical patch I know of.

 Ken

Re: max RAM

[Kenneth R Westerback]

On Sat, Jun 15, 2013 at 07:37:06PM +0200, Tony Berth wrote:
 Dear group,
 
 what is the max RAM the current release can support?
 
 Thanks
 
 Tony
 

Define 'support'.

 Ken

Re: dhcp devices getting the wrong default route on one subnet

[Kenneth R Westerback]

On Fri, Jun 14, 2013 at 02:38:48PM +0100, Stuart Henderson wrote:
 On 2013/06/14 21:49, John Tate wrote:
  On Fri, Jun 14, 2013 at 9:16 PM, Stuart Henderson s...@spacehopper.org 
  wrote:
   On 2013-06-14, John Tate j...@johntate.org wrote:
   It doesn't complain about it but I've never done much with routing
   before. If I wanted to do it on the machine I'd do
   # route add -net 192.168.0.0/24 192.168.1.1
  
   Why would you need to do this at all, it seems you are already using
   192.168.1.1 as your default route?
  I thought I needed it so 192.168.0/24 can access 192.168.1/24
 
 Try e.g. route -n get 192.168.1.5 with and without a route to the subnet.
 In one case there will be a default route pointing at 192.168.0.1 and in the
 other case there will be a 192.168.1.0/24 route pointing at 192.168.0.1.
 
 
  
   I can't seem to find how to do this in dhcp-options(5)
  
   Named won't even start with this...
   option static-routes 192.168.1/24 192.168.0.1;
   Or this...
   option static-routes 192.168.1.0/24 192.168.0.1;
  
   option static-routes is for classful (class A/B/C) addresses, you may
   not specify a subnet mask there.
  
   I have the following dhcpd.conf...
   shared-network kab {
  
   Why do you have shared-network?
  
  Can't remember why I did that so I just got rid of it. I added option
  routers 192.168.0.1, 192.168.1.1; before the subnets at the top of
  the file and now I am getting the right default gateway.
 
 Routers should be set in the subnet block, you shouldn't hand
 192.168.1.1 as a possible router to hosts which are in 192.168.0.x.
 
  I got rid of the static routes, they were not working anyway. I must
  need to add something to pf to route between subnets 192.168.0/24 and
  192.168.1.1/24 and visa-versa.
 
 This is usually easy enough to work out. Add 'log' in relevant places
 in pf.conf and watch tcpdump -neipflog0
 

Also, support for static-routes was just added in the last week or so
and you've not mentioned what versions of OpenBSD/dhcpd/dhclient you
are running.

 Ken

Re: ASC/ASCQ: Unrecovered Read Error

[Kenneth R Westerback]

On Wed, Jun 12, 2013 at 01:03:39PM +0300, Claudiu Tanaselia wrote:
 Hello all,
 
 Today is the second day in a row when my OpenBSD 5.2 machine became
 unresponsive: would not accept remote ssh connection and it hangs after the
 username input using local keyboard. The error message I receive on ttyC0
  is the following:
 
 sd0(mpi0:0): Check Condition (error 0x70) on opcode 0x28
 SENSE KEY: Media Error
 INFO: 0x259fce4 (VALID flag on)
 ASC/ASCQ: Unrecovered Read Error
 sd0(mpi0:0:0): Check Condition (error 0x70) on opcode 0x28
 SENSE KEY: Media Error
 INFO: 0x259fce5 (VALID flag on)
 ASC/ASCQ: Unrecovered Read Error
 
 Thanks for any of your hints,
 Claudiu.
 

Your disk is likely dying or that spot can't be read.

 Ken

Re: 5.3 change affecting hostname.if, dhcp

[Kenneth R Westerback]

On Thu, Jun 06, 2013 at 07:09:05PM -0400, gpon...@spamcop.net wrote:
 I recently updated from 5.2 to 5.3 and one ethernet port got broken.
 The port connected to a cable modem and was configured for DHCP.
 With 5.3, the DHCP assigned address is getting lost when I add an
 alias.

Mixing dhcp and aliases is not supported in 5.3 as we search for a
consistant and reliable way to accomplish it. dhclient will always
remove all addresses present on the interface when applying the
lease.

 Ken

The alias and a route table addition give the LAN a way to
 communicate with the modem's web interface which is fixed at
 192.168.100.1. My hostname.em2 contents are:
 
 dhcp rdomain 1
 alias 192.168.100.2 255.255.255.0
 !route -T 1 add 192.168.100.0/24 192.168.100.2
 
 I also have a DSL modem on em1 with fixed IP that should not be
 affected by the DHCP response, so my implementation used a separate
 routing table for the two WAN ports.
 
 /etc  sh /etc/netstart em2
 
 DHCPREQUEST on em2 to 255.255.255.255 port 67
 DHCPACK from 73.70.192.1 (00:01:5c:33:0e:01)
 bound to 98.207.205.23 -- renewal in 5572 seconds.
 route: writing to routing socket: File exists
 add net 192.168.100.0/24: gateway 192.168.100.2: File exists
 
 
 /etc  ifconfig em2
 em2: 
 flags=28b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6
 rdomain 1 mtu 1500
 lladdr 00:24:81:7f:ee:0b
 priority: 0
 media: Ethernet autoselect (1000baseT full-duplex,master)
 status: active
 inet 192.168.100.2 netmask 0xff00 broadcast 192.168.100.255
 /etc 
 
 I would have expect to see two inet lines, one with the DHCP
 assigned address and another with the alias. As it is, the LAN can't
 get to the cable modem and the LAN can't route through the
 DHCP-assigned gateway. Removing the alias solves the routing problem
 but not the cable modem management access. Any thoughts or
 suggestions for how to fix this, or an alternate solution ?
 
 GP

Re: Western Digital - Advanced Format

[Kenneth R Westerback]

On Sat, Jun 01, 2013 at 07:38:50AM +0100, MD wrote:
 Recently obtained WD7500-BPKT (750g) hard drive that apparently
 possesses Advanced Format technology.
 On Intel D525MW board through ACPI.
 
 On installation of 5.3-release, offered FFS (not FFS2) - ok ;-)
 
 First partition auto-aligned at sector 64.
 I did not ensure partitions were at 4k multiples. Naughty!
 
 Will Advanced Format Just Work(TM)?
 
 disklabel seemed to broadly (rather than precisely) follow
 my 4.0g, 12.0g, etc. partition sizes
 OR do I need to go back in, use Expert mode now, and
 MAKE SURE those partitions are exact multiples of 8 sectors
 i.e. 64 to 2097216 = 1.0g for /?
 
 I probably need to DBAN it again anyway but maybe I don't...
 
 I can only find David Gwynne's comments on this so far...
 Your observations much appreciated.
 
 Mike
 
 P.S. I ignored the suggestion of only formatting 300g for /home
 and forced the whole lot at the end ;-) I expect I should have
 aligned the end of this too? (You numpty, Mike!)
 

You do not show the dmesg so it's impossible to tell what the
kernel thinks the drive is claiming.

If the drive claims to be using 512-byte sectors, everything should
work but potentially be slow due to the drive compensating for
i/o into the middle of 4K sectors.

If the drive is claiming to be using 4K sectors then the partitions
should all have been automatically adjusted to start on 4K boundaries.

 Ken

Re: Hackathon

[Kenneth R Westerback]

On Wed, May 29, 2013 at 07:54:39PM -0400, Scott McEachern wrote:
 As a person who was born and raised in Toronto, and currently lives
 a bit outside of the city, I wanted to extend a warm welcome to our
 OpenBSD hackathon guests!
 
 I hope the major storm that happened last night, which caused some
 flooding complicating commutes, didn't inconvenience you too badly.
 
 Please enjoy the city, and if you happen to read any local media,
 have a laugh.  We currently have a handful of local and provincial
 scandals unfolding, which if it weren't for the costs involved,
 would be almost as entertaining as the most recent troll on @misc.
 (Please don't feed the trolls.)
 
 Have fun, and thanks for the work you're putting in.  Just out of
 curiosity, what is the focus of this hackathon?  I don't know what
 t2k13 means.

t == toronto

2k == 2000

13 == 13

 Ken

 
 Cheers to all involved,
 
 -- 
 Scott McEachern
 
 https://www.blackstaff.ca
 
 Those who would give up essential liberty to purchase a little temporary 
 safety deserve neither liberty nor safety. -- Benjamin Franklin

Re: Hackathon

[Kenneth R Westerback]

On Wed, May 29, 2013 at 08:35:12PM -0400, Scott McEachern wrote:
 On 05/29/13 20:22, Kenneth R Westerback wrote:
 On Wed, May 29, 2013 at 07:54:39PM -0400, Scott McEachern wrote:
 Have fun, and thanks for the work you're putting in.  Just out of
 curiosity, what is the focus of this hackathon?  I don't know what
 t2k13 means.
 t == toronto
 
 2k == 2000
 
 13 == 13
 
 
 Sorry for not being clear.  I understood the 2k13 part, it was the
 t I was wondering about.  I feel a little dense for not putting
 the t with Toronto, which was also pointed out to me privately.
 Suddenly I feel like Homer Simpson. :)

It is a general. Doh, and I could have had a free beer.

 Ken

 
 So I guess it's a general hackathon then?  Please, no cute retorts
 or else I'll have to drive down there and buy a round.  And I
 *really* dislike driving back to the city.
 
 -- 
 Scott McEachern
 
 https://www.blackstaff.ca
 
 Those who would give up essential liberty to purchase a little temporary 
 safety deserve neither liberty nor safety. -- Benjamin Franklin

Re: how long should CD orders take?

[Kenneth R Westerback]

On Thu, May 23, 2013 at 12:03:48PM +0100, Michael Stevens wrote:
 On Tue, May 21, 2013 at 07:52:01PM +0200, mxb wrote:
  Try openbsdeurope.com next time. I already got mine. Last week.
  
  //mxb
  
  On 21 maj 2013, at 19:26, Peter J. Philipp p...@centroid.eu wrote:
  
   I ordered my CD through a german bookstore that is listed at 
   www.openbsd.org/orders.html.  Only it's now the 21st of May and my 
   computers have all been upgraded via FTP around the 1st of May.  And I 
   still have no CD (and no stickers).
   
   Last year they were slow as well, which leads me to believe that the 
   store is sloppy in its orders.  Can someone confirm that the CD's have 
   all been sent out from Calgary?  It's really a shame that I must use 
   resources of OpenBSD when not needed, my order went in around the end of 
   March 2013 and there was lots of time to deliver this as a pre-order.
   
   -peter
 
 My openbsdeurope order arrived very quickly after release.
 
 I think the t-shirt sizes may be a little smaller this time though which
 makes me sad.
 
 Michael

Either they're smaller or ... :-).

 Ken

Re: provide option to dhclient at boot

[Kenneth R Westerback]

On Mon, May 20, 2013 at 11:56:15AM +0200, Daniel Polak wrote:
 I'd like to use the -l option to have dhclient use an alternate location
 for the leases file.
 Netstart starts dhclient at boot but I don't see a way to supply the -l
 option to dhclient other than to modify netstart.
 
 Am I missing something?
 
 
 Daniel
 

Nope. If you want to change the parameters netstart uses, you must
modify netstart. Excellent point. May have to think up a better
way.

 Ken

Re: provide option to dhclient at boot

[Kenneth R Westerback]

On Mon, May 20, 2013 at 07:29:45AM -0400, Jiri B wrote:
 On Mon, May 20, 2013 at 11:56:15AM +0200, Daniel Polak wrote:
  I'd like to use the -l option to have dhclient use an alternate location
  for the leases file.
  Netstart starts dhclient at boot but I don't see a way to supply the -l
  option to dhclient other than to modify netstart.
  
  Am I missing something?
  
  Daniel
 
 Changed my mind, dhclient_flags would be mess and it
 would lead to freebsd way... Maybe removing 'dhcp' from
 hostname.if and adding !dhclient -l ...' would be more
 clear.
 
 jirib

This is probably the best way at the moment. One possible future
alternative would be to add a '-l' equivalent into the dhclient.conf
syntax.

 Ken

Re: dhclient exiting on lease expiry

[Kenneth R Westerback]

On Mon, May 13, 2013 at 09:40:59AM +0100, Mike Williams wrote:
 Hi,
 
 I have been upgrading my machines to 5.3 this weekend and I am
 seeing some strange behaviours with dhclient.  The config is simple:
 
 /etc/dhclient.conf
 send host-name pc-1;
 request subnet-mask, broadcast-address, routers, domain-name,
 domain-name-servers, host-name;
 
 (FWIW The dhcp server serves up constant IP addresses based on the MAC)
 
 There is only one i/f with the wrinkle that I am temporarily running
 an inet alias off the i/f as well:
 
 /etc/hostname.re0
 dhcp NONE NONE NONE NONE
 inet alias 192.168.67.24 255.255.255.0 NONE

Upgraded from what version?

Yes, the 5.3 dhclient will remove all aliases as part of taking
control of the interface. So a renewal will remove the interface. In
fact adding the alias should either cause dhclient to exit, or the
alias will be removed when the lease is obtained.

This behaviour was mentioned in the release notes:

all existing addresses on the interface are deleted when binding
a new lease.

 
 Up to the upgrade this was ticking along with no problems.
 
 Now, whenever the lease expires the dhclient daemon exits taking the
 inet alias with it, and I have no connectivity.  I can restart
 dhclient but this leaves the inet alias dead.
 
 /var/log/daemon shows the following (*):
 
 May 13 03:50:46 pc-1 dhclient[28001]: DHCPREQUEST on re0 to
 192.168.67.2 port 67
 May 13 03:50:46 pc-1 dhclient[28001]: DHCPACK from 192.168.67.2
 (00:40:63:dd:9f:c0)
 ...
 May 13 03:50:46 pc-1 dhclient[28001]: 192.168.67.40, not
 192.168.67.40, deleted from re0; exiting

Now that is an unfortunate and insufficiently useful error message.

 
 However if I force a renewal with pkill -HUP dhclient I see this:
 
 May 13 09:10:41 pc-1 dhclient[25646]: bound to 192.168.67.40 --
 renewal in 43200 seconds.

And that does NOT remove the alias? That would be contrary to my
expectation.

 
 So it looks like an issue when the lease times out.  There was
 nothing in the upgrade notes, and a search through the lists on
 marc.info only brings up to release note improvements, nothing about
 any configuration changes that may be needed.
 
 (*) For full context I have avahi-daemon installed so the full
 daemon log for the time the lease expired is as follows:
 
 May 13 01:32:24 pc-1 identd[23433]: Connection from xxx.yyy.zzz
 May 13 03:50:46 pc-1 dhclient[28001]: DHCPREQUEST on re0 to
 192.168.67.2 port 67
 May 13 03:50:46 pc-1 dhclient[28001]: DHCPACK from 192.168.67.2
 (00:40:63:dd:9f:c0)
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Withdrawing address record
 for 192.168.67.40 on re0.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Withdrawing address record
 for 192.168.67.24 on re0.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Leaving mDNS multicast
 group on interface re0.IPv4 with address 192.168.67.24.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: IP_DROP_MEMBERSHIP failed:
 Can't assign requested address
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Interface re0.IPv4 no
 longer relevant for mDNS.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Joining mDNS multicast
 group on interface re0.IPv4 with address 192.168.67.40.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: New relevant interface
 re0.IPv4 for mDNS.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Registering new address
 record for 192.168.67.40 on re0.IPv4.
 May 13 03:50:46 pc-1 dhclient[28001]: 192.168.67.40, not
 192.168.67.40, deleted from re0; exiting
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Withdrawing address record
 for 192.168.67.40 on re0.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Leaving mDNS multicast
 group on interface re0.IPv4 with address 192.168.67.40.
 May 13 03:50:46 pc-1 avahi-daemon[10755]: IP_DROP_MEMBERSHIP failed:
 Can't assign requested address
 May 13 03:50:46 pc-1 avahi-daemon[10755]: Interface re0.IPv4 no
 longer relevant for mDNS.
 May 13 04:10:10 pc-1 ntpd[18186]: 0 out of 1 peers valid
 
 Let the beatings with the clue bat begin.
 
 -- 
 Mike
 

Not sure what Avahi is doing. :-) If you capture the output from
'route monitor', you can see what RTM_NEWADDR, RTM_DELADDR, etc.
messages are flying around that dhclient will be paying attention
to.

Bottom line: alias and dhclient do not play well together. They never have
in a general sense, and 5.3 tightens things up significantly. We are looking
at making them work together safely and reliably.

 Ken

Re: DHCLIENT v5.3

[Kenneth R Westerback]

On Thu, May 09, 2013 at 07:38:55AM -0400, Jiri B wrote:
 On Wed, May 08, 2013 at 07:58:26PM -0700, Chris Cappuccio wrote:
  For now you'll need to call your dns script from dhclient. A system() will 
  do the trick.
 
 Is planned to have an ability to fire a script/command from dhclient
 in the future? I used to be putting on/off various dns servers for
 my pdnsd setup...
 
 j.

At the moment it is not planned.

 Ken

Re: adsuck start at boot

[Kenneth R Westerback]

On Fri, May 03, 2013 at 02:52:06PM -0700, Scott wrote:
 Good day,
 I can't get adsuck to start at boot on OpenBSD 5.3. I copied strings like a
 monkey and thought them over (even testing them in shell), but no luck.
 
 # grep adsuck /etc/rc.conf.local:
 adsuck_flags=-c /var/adsuck -f /files/resolv.conf /files/hosts.small
 
 # cat /etc/rc.local:
 if [ $adsuck_flags != NO -a -x /usr/local/sbin/adsuck ]; then
 echo -n ' adsuck'
 /usr/local/sbin/adsuck $adsuck_flags
 fi

You may want to use the pkg_scripts variable in rc.conf.local. i.e.
rather than modifying /etc/rc.local.

 
 # which adsuck:
 /usr/local/sbin/adsuck
 
 Adsuck does work properly if started manually using:
 sudo adsuck -c /var/adsuck -f /files/resolv.conf /files/hosts.small

As far as I can see from a quick install of adsuck, I don't think it has
been adapted to the removal of the dhclient-script from dhclient's
operation. So if you are using dhcp you may be out of luck at the moment. Or
if you are using dhcp and aduck is working on 5.3 I'd be interested in more
details on your setup, and where you got directions on setting it up.

 
 So I know it's just something I'm doing wrong with my rc scripts. I read
 the readme in /usr/local/shar/docs/pkg-readmes/, but that only covers
 interaction with dhclient and resolv.conf.

And, alas, does it wrong. 'script' is no longer a valid statement
in dhclient.conf and thus the provided /usr/local/sbin/dhclient-adsuck
will not be invoked by dhclient.

 Ken

 
 
 Any help would be MUCH appreciated.
 
 -Scott

Re: adsuck start at boot

[Kenneth R Westerback]

On Fri, May 03, 2013 at 06:08:15PM -0700, Scott wrote:
 Ken,
 Thanks for the tip! pkg_scripts did the trick (I'd never seen that
 mechanism before). With regards to making adsuck play nice with dhcp (yes,
 I tired the script line from the readme only to get errors), maybe the
 dhclient-adsuck script was rewritten? I've done nothing special and yet it
 all just works. Following is my setup on 5.3 i386 (after your advice):
 
 # grep adsuck /etc/rc.conf.local:
 pkg_scripts=adsuck# notice I've removed the adsuck_flags variable
 
 # grep nameserver /etc/resolv.conf:
 nameserver 127.0.0.1
 
 # cat /etc/dhclient.conf:
 supersede domain-name-servers 127.0.0.1;
 request subnet-mask, broadcast-address, routers,
   domain-name-servers, domain-name, host-name;
 
 # grep nameserver /var/adsuck/files/resolv.conf:
 nameserver 75.75.75.75
 nameserver 75.75.76.76
 
 # ls /var/adsuck/files/hosts.small:
 /var/adsuck/files/hosts.small
 
 Although I thrashed around a lot trying to get it to work, once I rolled
 back all my changes I guess all that needs to happen (in my case) is:
 
 cp /etc/resolv.conf /var/adsuck/files/
 print 'pkg_scripts=adsuck' /etc/rc.conf.local
 print prepend domain-name-servers 127.0.0.1; /etc/dhclient.conf
 
 and change /etc/resolv.conf to contain only:
 nameserver 127.0.0.1
 
 Thanks again for your help.
 -Scott

Excellent. The only problem I see with your setup (not being an
adsuck user, so all advice should be taken with a grain of salt)
is that if the domain name server info that dhclient gets changes,
your setup may fail. Obviously, if it does you simply need to manually
refresh the contents of /var/asuck/files/resolv.conf.

Thanks for the update.

 Ken

 
 
 On Fri, May 3, 2013 at 3:40 PM, Kenneth R Westerback kwesterb...@rogers.com
  wrote:
 
  On Fri, May 03, 2013 at 02:52:06PM -0700, Scott wrote:
   Good day,
   I can't get adsuck to start at boot on OpenBSD 5.3. I copied strings
  like a
   monkey and thought them over (even testing them in shell), but no luck.
  
   # grep adsuck /etc/rc.conf.local:
   adsuck_flags=-c /var/adsuck -f /files/resolv.conf /files/hosts.small
  
   # cat /etc/rc.local:
   if [ $adsuck_flags != NO -a -x /usr/local/sbin/adsuck ]; then
   echo -n ' adsuck'
   /usr/local/sbin/adsuck $adsuck_flags
   fi
 
  You may want to use the pkg_scripts variable in rc.conf.local. i.e.
  rather than modifying /etc/rc.local.
 
  
   # which adsuck:
   /usr/local/sbin/adsuck
  
   Adsuck does work properly if started manually using:
   sudo adsuck -c /var/adsuck -f /files/resolv.conf /files/hosts.small
 
  As far as I can see from a quick install of adsuck, I don't think it has
  been adapted to the removal of the dhclient-script from dhclient's
  operation. So if you are using dhcp you may be out of luck at the moment.
  Or
  if you are using dhcp and aduck is working on 5.3 I'd be interested in more
  details on your setup, and where you got directions on setting it up.
 
  
   So I know it's just something I'm doing wrong with my rc scripts. I read
   the readme in /usr/local/shar/docs/pkg-readmes/, but that only covers
   interaction with dhclient and resolv.conf.
 
  And, alas, does it wrong. 'script' is no longer a valid statement
  in dhclient.conf and thus the provided /usr/local/sbin/dhclient-adsuck
  will not be invoked by dhclient.
 
   Ken
 
  
  
   Any help would be MUCH appreciated.
  
   -Scott

Re: install fixes address in /etc/hosts

[Kenneth R Westerback]

On Mon, Apr 29, 2013 at 01:41:52PM +0200, Jan Stary wrote:
 Installed yesterday's current/i386, using dhcpd and pxeboot
 from another machine. After the installation, I noticed
 that the address that was assigned to me during the install
 via DHCP was written into /etc/hosts. Is that intended?
 Should an arbitrary dhcp-assigned address be written into
 /etc/hosts to stay there? Should that be mentioned in afterboot?
 
 The user might want to just use DHCP during the install,
 and only during afterboot, while setting everything up,
 decide on a fixed address and put that into hostname.if
 - but the arbitrary dhcp-assigned address will still be
 in /etc/hosts, possbily conflicting.
 
   Jan

Aha! To quote the commit message to /usr/src/distrib/miniroot/install.sub
from 2009:
Sat Mar 14 14:23:05 2009 UTC (4 years, 1 month ago) by krw
Branches: MAIN
Diff to: previous 1.448: preferred, coloured
Changes since revision 1.448: +11 -6 lines
There should only be one ::1 and one 127.0.0.1 entry in the hosts
file.  And 'localhost' don't need no stinkin' domain names.

Insert line(s) with the address(es) of last interface defined instead
of duplicate ::1 and 127.0.0.1 entries, Thus dhcp configured
interfaces may eventually drift away from the value in hosts file.

Much discussed just before tree lock. Time to see what happens.
-

So what happens is that four years later somebody notices. :-)

Your points are valid. I no longer recall the discussions that took
place at the time, and am open to any new discussion.

 Ken

Re: dhclient drops address on re-exec in 5.3 bsd.rd

[Kenneth R Westerback]

On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
 Confirmed in 5.3-current downloaded several minutes ago.
 
 Steps to reproduce:
 - Boot bsd.rd
 - Select upgrade, hit enter until dhclient gets and assigns an address
 - Complete upgrade or control-C, then restart the upgrade process
 - dhclient on 2nd run REMOVES the assigned address
 
 Probably affects the bsd.rd install option as well. This does not
 happen with 5.2 bsd.rd.
 
 Easy to work around, but probably not right.
 
 Thanks!
 
 --david
 

dhclient will *always* remove all existing address on interfaces it is
binding a lease to. Are you saying that the 2nd time around it is not
re-assigning the address? Is your easy workaround to re-run dhclient, or
is it something else?

As soon as some builds finish here I will try to reproduce.

 Ken

Re: dhclient drops address on re-exec in 5.3 bsd.rd

[Kenneth R Westerback]

On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
 Confirmed in 5.3-current downloaded several minutes ago.
 
 Steps to reproduce:
 - Boot bsd.rd
 - Select upgrade, hit enter until dhclient gets and assigns an address
 - Complete upgrade or control-C, then restart the upgrade process
 - dhclient on 2nd run REMOVES the assigned address
 
 Probably affects the bsd.rd install option as well. This does not
 happen with 5.2 bsd.rd.
 
 Easy to work around, but probably not right.
 
 Thanks!
 
 --david
 

Can't reproduce on amd64 -current here. I did control-C after getting
dhclient lease, entered 'upgrade' at command prompt, and re-started
upgrade. dhclient worked fine. Checked 'ifconfig' and the expected
address was present.

So more info you what exactly you are doing, on what machine are
you doing it, and perhaps anything interesting in your dhclient.conf
would be helpful. Thanks.

 Ken

Re: dhclient drops address on re-exec in 5.3 bsd.rd

[Kenneth R Westerback]

On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote:
 On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
 kwesterb...@rogers.com wrote:
  On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
  Confirmed in 5.3-current downloaded several minutes ago.
 
  Steps to reproduce:
  - Boot bsd.rd
  - Select upgrade, hit enter until dhclient gets and assigns an address
  - Complete upgrade or control-C, then restart the upgrade process
  - dhclient on 2nd run REMOVES the assigned address
 
  Probably affects the bsd.rd install option as well. This does not
  happen with 5.2 bsd.rd.
 
  Easy to work around, but probably not right.
 
  Thanks!
 
  --david
 
 
  Can't reproduce on amd64 -current here. I did control-C after getting
  dhclient lease, entered 'upgrade' at command prompt, and re-started
  upgrade. dhclient worked fine. Checked 'ifconfig' and the expected
  address was present.
 
  So more info you what exactly you are doing, on what machine are
  you doing it, and perhaps anything interesting in your dhclient.conf
  would be helpful. Thanks.
 
   Ken
 
 I would have provided output, but I haven't figured out how to log
 console output from VMware images.  Hopefully this will suffice:
 
 i386 / 5.3-current / RAMDISK_CD #120
 
 dhclient #1 (good)
 DHCPDISCOVER on vic0 to 255.255.255.255 port 67 interval 1
 DHCPOFFER from 172.16.223.254 (mac addr)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.131 -- renewal in 900 seconds
 
 dhclient #2 (bad)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 Active address (172.16.223.131) deleted; exiting

Is there a configured ip address on the interface at this point?
This is a message emitted by one dhclient on noticing that another
one is active and has deleted the address the first one configured.
It *shouldn't* mean that no ip address is configured.

Now what is different in the virtual environment you are using that
makes i386 timing different than amd64 ... dunno.

 Ken

 
 dhclient #3 (good)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.131 -- renewal in 900 seconds
 
 amd64 / 5.3-current / RAMDISK_CD #132
 
 dhclient #1 (good)
 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1
 DHCPOFFER from 172.16.223.254 (mac addr)
 DHCPREQUEST on em0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.130 -- renewal in 900 seconds
 
 dhclient #2 (still good)
 DHCPREQUEST on em0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.130 -- renewal in 900 seconds
 
 /etc/dhclient.conf appears to be identical to between i386 and amd64.
 I am sending an identical hostname FWIW, but I am only launching only
 one VM at a time.
 
 initial-interval 1;
 send host-name vm;
 request subnet-mask, broadcast-address, routers, domain-name,
 domain-name-servers, host-name;
 
 Let me know if you want me to try anything else.
 
 --david

Re: dhclient drops address on re-exec in 5.3 bsd.rd

[Kenneth R Westerback]

On Sun, Apr 28, 2013 at 05:29:05PM -0400, David Higgs wrote:
 On Sun, Apr 28, 2013 at 4:00 PM, Kenneth R Westerback
 kwesterb...@rogers.com wrote:
  On Sun, Apr 28, 2013 at 02:41:36PM -0400, David Higgs wrote:
  Confirmed in 5.3-current downloaded several minutes ago.
 
  Steps to reproduce:
  - Boot bsd.rd
  - Select upgrade, hit enter until dhclient gets and assigns an address
  - Complete upgrade or control-C, then restart the upgrade process
  - dhclient on 2nd run REMOVES the assigned address
 
  Probably affects the bsd.rd install option as well. This does not
  happen with 5.2 bsd.rd.
 
  Easy to work around, but probably not right.
 
  Thanks!
 
  --david
 
 
  Can't reproduce on amd64 -current here. I did control-C after getting
  dhclient lease, entered 'upgrade' at command prompt, and re-started
  upgrade. dhclient worked fine. Checked 'ifconfig' and the expected
  address was present.
 
  So more info you what exactly you are doing, on what machine are
  you doing it, and perhaps anything interesting in your dhclient.conf
  would be helpful. Thanks.
 
   Ken
 
 I would have provided output, but I haven't figured out how to log
 console output from VMware images.  Hopefully this will suffice:
 
 i386 / 5.3-current / RAMDISK_CD #120
 
 dhclient #1 (good)
 DHCPDISCOVER on vic0 to 255.255.255.255 port 67 interval 1
 DHCPOFFER from 172.16.223.254 (mac addr)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.131 -- renewal in 900 seconds
 
 dhclient #2 (bad)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 Active address (172.16.223.131) deleted; exiting

Trying the exact same RAMDISK_CD #120 on 'real' i386 hardware with
an nfe(4) interface, I cannot reproduce. So I suspect (assuming it
is not just an errant log message) something is broken in the i386/vm
interface you are trying.

 Ken

 
 dhclient #3 (good)
 DHCPREQUEST on vic0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.131 -- renewal in 900 seconds
 
 amd64 / 5.3-current / RAMDISK_CD #132
 
 dhclient #1 (good)
 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1
 DHCPOFFER from 172.16.223.254 (mac addr)
 DHCPREQUEST on em0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.130 -- renewal in 900 seconds
 
 dhclient #2 (still good)
 DHCPREQUEST on em0 to 255.255.255.255 port 67
 DHCPACK from 172.16.223.254 (mac addr)
 bound to 172.16.223.130 -- renewal in 900 seconds
 
 /etc/dhclient.conf appears to be identical to between i386 and amd64.
 I am sending an identical hostname FWIW, but I am only launching only
 one VM at a time.
 
 initial-interval 1;
 send host-name vm;
 request subnet-mask, broadcast-address, routers, domain-name,
 domain-name-servers, host-name;
 
 Let me know if you want me to try anything else.
 
 --david

Re: Why does OpenBSD use CVS?

[Kenneth R Westerback]

On Sat, Apr 20, 2013 at 01:06:44PM +0200, Franco Fichtner wrote:
 On Apr 20, 2013, at 1:02 PM, na...@mips.inka.de (Christian Weisgerber) wrote:
 
  Alokat MacMoneysack mail...@alokat.org wrote:
  
  I find it a little bit difficult to see the commits from the developers.
  Because I have to check out the single files and not a single commit.
  
  You might find the cvsps package useful.
 
 Or use https://bitbucket.org/braindamaged/openbsd-src to catch up on
 commits or skim through the history of -current.
 
 
 Franco
 

Or use cvsync to keep a repository local and then look at the Changelog
files.

 Ken

Re: OpenBSD Foundation benefit Auction / Absolute OpenBSD 2nd Ed.

[Kenneth R Westerback]

On Tue, Apr 16, 2013 at 05:17:21PM -0400, Michael W. Lucas wrote:
 Auction is over. $1,145 for the Foundation.
 
 http://blather.michaelwlucas.com/archives/1660
 
 ==ml
 
 -- 
 Michael W. Lucas  -  mwlu...@michaelwlucas.com, Twitter @mwlauthor 
 http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
 Latest book: Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e
 coupon code ILUVMICHAEL gets you 30% off  helps me.
 

The Foundation is grateful!

 Ken

Re: Perl fails to build in -current

[Kenneth R Westerback]

On Fri, Mar 29, 2013 at 09:08:25AM -0400, Ryan Kavanagh wrote:
 I downloaded a snapshot on the 27th or so, and am trying to update by 
 compiling
 from source, but get the FTBFS below. This may or may not have to do with the
 perl update (my snapshot came with perl 5.16.3, so I assumed I would be past
 that). I haven't found anything helpful with Google, any thoughts on how to
 resolve it? The files are there, but they seem to be missing from @INC:
 
 $ locate '/usr*Escapes.pm'
 /usr/libdata/perl5/Pod/Escapes.pm
 /usr/obj/gnu/usr.bin/perl/cpan/Pod-Escapes/lib/Pod/Escapes.pm
 /usr/src/gnu/usr.bin/perl/cpan/Pod-Escapes/lib/Pod/Escapes.pm
 
 Best wishes,
 Ryan

Are you using -j N in the build? It's currently not working in the newly
updated perl.

 Ken

 
 LD_LIBRARY_PATH=/usr/src/gnu/usr.bin/perl/obj  ./miniperl -Ilib make_ext.pl 
 ext/Pod-Functions/pm_to_blib MAKE=make LIBPERL_A=libperl.so.13.0
 Making Pod::Functions (all)
 
 Running Makefile.PL in ext/Pod-Functions
 ../../miniperl -I../../lib Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none 
 INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=libperl.so.13.0
 Writing Makefile for Pod::Functions
 Making all in ext/Pod-Functions
  make all PERL_CORE=1 LIBPERL_A=libperl.so.13.0
 ../../miniperl -I../../lib -I../../lib Functions_pm.PL 
 ../../pod/perlfunc.pod
 Can't locate Pod/Escapes.pm in @INC (@INC contains: 
 /usr/obj/gnu/usr.bin/perl/cpan/AutoLoader/lib 
 /usr/obj/gnu/usr.bin/perl/dist/Carp/lib /usr/obj/gnu/usr.bin/perl/dist/Cwd 
 /usr/obj/gnu/usr.bin/perl/dist/Cwd/lib 
 /usr/obj/gnu/usr.bin/perl/dist/ExtUtils-Command/lib 
 /usr/obj/gnu/usr.bin/perl/dist/ExtUtils-Install/lib 
 /usr/obj/gnu/usr.bin/perl/cpan/ExtUtils-MakeMaker/lib 
 /usr/obj/gnu/usr.bin/perl/dist/ExtUtils-Manifest/lib 
 /usr/obj/gnu/usr.bin/perl/cpan/File-Path/lib /usr/obj/gnu/usr.bin/perl/ext/re 
 /usr/obj/gnu/usr.bin/perl/dist/Term-ReadLine/lib 
 /usr/obj/gnu/usr.bin/perl/lib .) at 
 /usr/obj/gnu/usr.bin/perl/lib/Pod/Simple.pm line 8.
 BEGIN failed--compilation aborted at 
 /usr/obj/gnu/usr.bin/perl/lib/Pod/Simple.pm line 8.
 Compilation failed in require at 
 /usr/obj/gnu/usr.bin/perl/lib/Pod/Simple/SimpleTree.pm line 7.
 BEGIN failed--compilation aborted at 
 /usr/obj/gnu/usr.bin/perl/lib/Pod/Simple/SimpleTree.pm line 7.
 Compilation failed in require at Functions_pm.PL line 3.
 BEGIN failed--compilation aborted at Functions_pm.PL line 3.
 *** Error 2 in /usr/obj/gnu/usr.bin/perl/ext/Pod-Functions (Makefile:816 
 'Functions.pm')
 Unsuccessful make(ext/Pod-Functions): code=512 at make_ext.pl line 466.
 *** Error 25 in gnu/usr.bin/perl/obj (makefile:681 
 'ext/Pod-Functions/pm_to_blib')
 *** Error 2 in gnu/usr.bin/perl (Makefile.bsd-wrapper:74 'perl.build')
 *** Error 2 in gnu/usr.bin (bsd.subdir.mk:48 'all')
 *** Error 2 in gnu (bsd.subdir.mk:48 'all')
 *** Error 2 in . (bsd.subdir.mk:48 'all')
 *** Error 2 in /usr/src (Makefile:85 'build')
 
 -- 
 |_)|_/Ryan Kavanagh   | Debian Developer
 | \| \http://ryanak.ca/   | GPG Key 4A11C97A

Re: Why to use packages?

[Kenneth R Westerback]

On Sat, Mar 16, 2013 at 03:59:59PM +0400, Alexander Nusov wrote:
 Got it, thanks!
 As far I understood one reason to use packages is bootstrapping? So
 install packages first then update all needed software from ports?

a) Packages are built on correct versions of software. So 5.2 packages
work on 5.2. *MANY* people incorrectly try to build -current ports
on -stable or -relase. This does not work. And if using ports was
recommended there would be even more such carping.

b) Building from ports means building a *LOT* of build dependencies.
Like extra compilers. These are not needed when you just install
packages. e.g.  just building my normal set of packages (because I
always have experimental system and X diffs to test on top of
-current) takes 12 hours on an 8xi7 8GB amd64.

c) Building from ports means the developers do not know what you
did, what your environment looked like, etc. So bug reports are
much harder to deal with.

If you want to run the latest versions of 3rd party software you
must keep your systems at -current and either use the latest built
packages or keep rebuilding your ports.

 Ken

 
 On Sat, Mar 16, 2013 at 3:55 PM, Patrick Lamaiziere
 patf...@davenulle.org wrote:
  Le Sat, 16 Mar 2013 12:36:35 +0400,
  Alexander Nusov alexander.nu...@gmail.com a ?crit :
 
  Hello,
 
  I'm trying to get why to use binary packages if they are not updated?
 
  I don't see any reason to use packages too (IMHO).
 
  For example, this package confuses me: lighttpd
 
  ftp://ftp.openbsd.org/pub/OpenBSD/5.2/packages/amd64/
  lighttpd-1.4.31p0-ldap-mysql.tgz339 kB31.07.12 0:00:00
  lighttpd-1.4.31p0-ldap.tgz335 kB31.07.12 0:00:00
  lighttpd-1.4.31p0-mysql.tgz337 kB31.07.12 0:00:00
  lighttpd-1.4.31p0.tgz
 
  It was updated in the stable port tree (but there are no package
  available). You can build your own packages from it and deploy them.
 
  Regards.

Re: dhcpd issues with Android phone

[Kenneth R Westerback]

On Thu, Mar 14, 2013 at 09:46:04PM +1100, John Tate wrote:
 I have an android phone that requests a least regularly from my dhcpd
 server on OpenBSD 5.2 which eventually starts failing with this error in
 /var/log/daemon
 
 Mar 14 21:40:42 menger dhcpd[7088]: DHCPREQUEST for 10.0.0.4 from
 0c:14:20:6b:08:e5 via fxp0
 Mar 14 21:40:42 menger dhcpd[7088]: DHCPNAK on 10.0.0.4 to
 0c:14:20:6b:08:e5 via fxp0
 Mar 14 21:40:43 menger dhcpd[7088]: DHCPDISCOVER from 0c:14:20:6b:08:e5 via
 fxp0
 Mar 14 21:40:43 menger dhcpd[7088]: DHCPOFFER on 10.0.0.4 to
 0c:14:20:6b:08:e5 via fxp0
 Mar 14 21:40:43 menger dhcpd[7088]: Both dynamic and static leases present
 for 10.0.0.4.
 
 If I remove the entry for 10.0.0.4 from /var/db/dhcpd.leases and restart it
 works again but only for a few hours.
 
 lease 10.0.0.4 {
 starts 4 2013/03/14 10:08:12;
 ends 4 2013/03/14 22:08:12;
 hardware ethernet ac:81:12:98:de:f3;
 uid 01:ac:81:12:98:de:f3;
 client-hostname MURPHY;
 }
 
 I think I've done something wrong and I have very little experience with
 dhcpd.
 
 -- 
 www.johntate.org
 

Your /etc/dhcpd.conf file might be useful. Off the top of my head you
have static leases set up in the same range as your dynamic leases.

 Ken

Re: dhcpd and sync

[Kenneth R Westerback]

On Tue, Mar 12, 2013 at 06:15:27PM +0200, Kapetanakis Giannis wrote:
 Hi,
 
 I'm testing dhcpd sync features and I'm getting errors due to wrong
 HMAC calculation.
 (not getting back note(DHCP_SYNC_LEASE from).
 
 sync_recv() is exiting in HMAC calculation in /* Compute and
 validate HMAC */ (line 283)
 
 After applying the diff bellow problem seems to be solved. Could
 someone have a look?
 
 regards,
 
 Giannis
 
 Index: sync.c
 ===
 RCS file: /cvs/src/usr.sbin/dhcpd/sync.c,v
 retrieving revision 1.10
 diff -u -r1.10 sync.c
 --- sync.c  23 Dec 2010 17:38:04 -  1.10
 +++ sync.c  12 Mar 2013 16:11:02 -
 @@ -426,7 +426,7 @@
 hdr.sh_version = DHCP_SYNC_VERSION;
 hdr.sh_af = AF_INET;
 hdr.sh_counter = sync_counter++;
 -   hdr.sh_length = htons(sizeof(hdr) + sizeof(ld) + sizeof(end));
 +   hdr.sh_length = htons(sizeof(hdr) + leaselen + padlen +
 sizeof(end));
 iov[i].iov_base = hdr;
 iov[i].iov_len = sizeof(hdr);
 HMAC_Update(ctx, iov[i].iov_base, iov[i].iov_len);
 

Why replace sizeof(ld) with leaselen? a few lines up we have 'leaselen = 
sizeof(ld)'. Adding '+ padlen' should be all that is needed.

 Ken

Re: em(4) watchdog timeouts on 5.0-release

[Kenneth R Westerback]

On Thu, Mar 07, 2013 at 12:10:08PM +0100, mxb wrote:
 What about 5.2? Same issues?

Even better, what about -current or 5.3 snaps?

 Ken

Re: installer - moving sets location right after network for automated installation

[Kenneth R Westerback]

On Thu, Mar 07, 2013 at 12:19:22PM -0500, Jiri B wrote:
 Hi,
 
 I was thinking that if we would move part in the installer which let the user
 locate installation sets right after setting networking, we could introduce
 some install.site alternative which could feed installer with configuration
 for setting disks etc...
 
 Or is there any (semi)official idea how should automated/configurable
 OpenBSD installer look like in the future?

Several people have talked about and even implemented such systems. No
official idea's currently exist.

 Ken

 
 jirib

Re: Softraid 3TB Problems

[Kenneth R Westerback]

On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
 Joel,
 
 Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
 reason I wasn't getting it working then?

Both of the drives in the dmesg you posted report 512-byte sectors.

 Ken

 
 I will try to zero the drives and start from scratch again, and see if that
 works too. I had a feeling that deleting the disklabels with 'z' option
 wasn't actually getting things back to the way they were when I first
 started out.
 
 Thank you for your input!
 
 -Brandon
 
 
 On Sat, Mar 2, 2013 at 11:38 PM, Joel Sing j...@sing.id.au wrote:
 
  On Sun, 3 Mar 2013, Brandon Tanner wrote:
   By the way, does softraid on amd64 support 4096 bytes per sector?
 
  No. There is a large amount of work required to fix this since everything
  in
  softraid was originally designed around 512-byte blocks. It is somewhere on
  my TODO list, however I do not currently even have the hardware for
  development/testing.
  --
 
  Reason is not automatic. Those who deny it cannot be conquered by it.
   Do not count on them. Leave them alone. -- Ayn Rand

Re: Softraid 3TB Problems

[Kenneth R Westerback]

On Sun, Mar 03, 2013 at 07:54:07PM +0100, Robert wrote:
 On Sun, 3 Mar 2013 12:35:29 -0500
 Kenneth R Westerback kwesterb...@rogers.com wrote:
  On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
   Joel,
   
   Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
   reason I wasn't getting it working then?
  
  Both of the drives in the dmesg you posted report 512-byte sectors.
  
   Ken
 
 The Seagate datasheet [1] claims that this drive (ST3000DM001) uses 4k 
 sectors.
 
 Otherwise can I confirm that a Western Digital WD30EFRX 3TB drive with 512b 
 sectors works fine with crypto softraid.
 
 kind regards,
 Robert
 
 [1] 
 http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-desktop-hdd-ds-1770-1-1212us.pdf
 

Many drives use 4K internally but still report to the outside world that
they use 512 byte sectors. Handling the translation/packing/unpacking
themselves. OpenBSD just reports (and trusts) what the drive reports
in response to READ_CAPACITY/READ_CAPACITY_16.

 Ken

Re: dhclient not receiving dhcpoffers with wep connection but fine with wpa

[Kenneth R Westerback]

On Sun, Mar 03, 2013 at 03:10:38PM -0800, Jeff Richards wrote:
 I have been trying to configure a HP Pavilion dv5000(5210us) laptop to connect
 to a WEP network.? I have tried OBSD 5.2 and CURRENT without success using WEP
 but can connect with WPA --personal hotspot.
 
 
 The network interfaces I have
 tried are 
 
 
 Integrated wireless (bwi0 at pci3 dev 2 function 0 Broadcom
 BCM4318 rev 0x02: apic 1 int 21) 
 
 
 USB adapter (rum0 at uhub0 port 1 Ralink
 Technology RT2573 EV 2.00/0.01 addr 2 MAC/BBP RT2573 (rev 0x2573a), RF
 RT2528)
 
 Both adapters fail to obtain a DHCP configuration with No acceptable
 DHCPOFFERS received when using WEP but have no issue when configured for WPA.
 I have used ifconfig interface scan to extract information? to specify the
 channel and BSSID for my hostname.if WEP configuration.
 
 Any ideas will be
 appreciated.
 
 Thanks.
 

Idea 1: Supply the information requested for problem reports in

http://openbsd.org/report.html

including your logs, and a tcpdump of any received DHCPOFFER packets.

Idea 2: manually configure the interface and see if ANY network
traffic (e.g. ping) makes it in or out.

 Ken

Re: Summer Code

[Kenneth R Westerback]

On Sat, Mar 02, 2013 at 12:41:28AM -0500, Shoufu Luo wrote:
 Is there any google summer code project in obsd community?
 
 -Shoufu
 

Read the archives for a history of failed attempts to get Google
to let OpenBSD sponsers in. Short answer: no. Long answer: maybe
in the future.

 Ken

Re: Softraid 3TB Problems

[Kenneth R Westerback]

On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote:
 Anyone else having trouble getting bioctl to see more than 2TB when
 creating softraid0?
 
 I've got 2 x 3TB drives, BIOS sees them fine.
 
 dmesg on bootup:
 
 sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct
 fixed naa.5000c5005e0bcda5
 sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors
 sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct
 fixed naa.5000c5005e15ec80
 sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors
 
 notice the correct # of sectors above.
 
 disklabel -E sd1
 
  p T
 OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
 #size   offset  fstype [fsize bsize  cpg]
   a: 2.7T   64RAID
   c: 2.7T0  unused
 
 disklabel -E sd2
 
  p T
 OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
 #size   offset  fstype [fsize bsize  cpg]
   a: 2.7T   64RAID
   c: 2.7T0  unused
 
 # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0
 softraid0: SR RAID 1 volume attached as sd3
 
 sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed
 sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors
 
 Yet, bioctl only sees it for 4294961093 sectors :(

Softraid apparently truncates at 32 bits somewhere along the line.

You might try instrumenting places where ssd_size is set, and where
READ_CAPACITY/READ_CAPACITY_16 are processed.

A quick scan did not cause a 32 bit truncation to leap out at me.

 Ken

 
 # bioctl -h sd3
 Volume  Status   Size Device
 softraid0 0 Online   2.0T sd3 RAID1
   0 Online   2.0T 0:0.0   noencl sd1a
   1 Online   2.0T 0:1.0   noencl sd2a
 
 I have been troubleshooting this issue with the help of Scott McEachern
 extensively, and we are both stumped. He suggested I put this on misc to
 see if jsing might know anything. I have an Intel Desktop Motherboard model
 DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's
 only when trying to make a softraid volume that it doesn't see more than
 2TB.
 
 I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at:
 http://pastebin.com/jqnpSsnC
 
 Anyone else experiencing this?
 http://search.gmane.org/?author=Scott+McEachernsort=date

Re: Disk layout: OpenBSD OT

[Kenneth R Westerback]

On Sat, Mar 02, 2013 at 10:04:50PM +0100, Matthias Appel wrote:
 Am 02.03.2013 20:59, schrieb Miod Vallat:
 just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0
 is in the inner or outter track ?
 Which tracks are faster: the inner ones or the outter ?
 Only the manufacturer knows.
 
 Disks have been reporting fake geometries since more than 20 years. The
 electronic on the disk will do the necessary work to use the disk
 physical characteristic (with a varying number of sector per track) as
 cleverly as it can.
 
 Nowadays, you can't even be sure a given `software' is even contiguous
 on the disk.
 
 So, how is defrag (or avoiding fragmentation) done, if you can't be
 certain how the blocks are aligned?

You can't. You can only de-frag the 'view' the hardware provides you. You
can't outsmart it, so just be happy.

 Ken

 
 AFAIK, the last blocks are on the outside of the platters so, given
 a CAV, the speed is higher.
 The different speeds are measurablebut I don't know if
 noticeable (but I dont think so!)
 
 How SSDs handle block alignment is anoter story (wear-leveling et.al.)
 
 
 Regards,
 
 Matthias

Re: Softraid 3TB Problems

[Kenneth R Westerback]

On Sat, Mar 02, 2013 at 07:25:18PM -0600, Brandon Tanner wrote:
 By the way, does softraid on amd64 support 4096 bytes per sector?

I don't think so, but I haven't refreshed my memory of that recently.

 Ken

 
 
 On Sat, Mar 2, 2013 at 5:05 PM, Kenneth R Westerback kwesterb...@rogers.com
  wrote:
 
  On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote:
   Anyone else having trouble getting bioctl to see more than 2TB when
   creating softraid0?
  
   I've got 2 x 3TB drives, BIOS sees them fine.
  
   dmesg on bootup:
  
   sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3
  0/direct
   fixed naa.5000c5005e0bcda5
   sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors
   sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3
  0/direct
   fixed naa.5000c5005e15ec80
   sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors
  
   notice the correct # of sectors above.
  
   disklabel -E sd1
  
p T
   OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
   #size   offset  fstype [fsize bsize  cpg]
 a: 2.7T   64RAID
 c: 2.7T0  unused
  
   disklabel -E sd2
  
p T
   OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
   #size   offset  fstype [fsize bsize  cpg]
 a: 2.7T   64RAID
 c: 2.7T0  unused
  
   # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0
   softraid0: SR RAID 1 volume attached as sd3
  
   sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct
  fixed
   sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors
  
   Yet, bioctl only sees it for 4294961093 sectors :(
 
  Softraid apparently truncates at 32 bits somewhere along the line.
 
  You might try instrumenting places where ssd_size is set, and where
  READ_CAPACITY/READ_CAPACITY_16 are processed.
 
  A quick scan did not cause a 32 bit truncation to leap out at me.
 
   Ken
 
  
   # bioctl -h sd3
   Volume  Status   Size Device
   softraid0 0 Online   2.0T sd3 RAID1
 0 Online   2.0T 0:0.0   noencl sd1a
 1 Online   2.0T 0:1.0   noencl sd2a
  
   I have been troubleshooting this issue with the help of Scott McEachern
   extensively, and we are both stumped. He suggested I put this on misc to
   see if jsing might know anything. I have an Intel Desktop Motherboard
  model
   DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's
   only when trying to make a softraid volume that it doesn't see more than
   2TB.
  
   I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at:
   http://pastebin.com/jqnpSsnC
  
   Anyone else experiencing this?
   http://search.gmane.org/?author=Scott+McEachernsort=date

Re: Bug (?) - softraid

[Kenneth R Westerback]

On Sat, Feb 02, 2013 at 03:02:51PM +0100, Maxime Villard wrote:
 Hi,
 I have a Thinkpad T61, with an extractible cd drive like this one:
 http://www.notebookcheck.biz/typo3temp/pics/b7bc6b4b90.jpg
 
 If I unplug this drive when the system is fully booted - and logged
 in -, I get a strange bug.
 
 When I unplug:
   cd0 detached
   scsibus0 detached
   atapiscsi0 detached
   softraid0: i/o error on block 162290672 target 0 b_error 6  -- SOMETIMES 
 IT'S 'b_error 0'
 
 here, nothing works. Most of the time, the keyboard goes off and I
 cannot do anything like switching tty or simply typing 'reboot'.
 Sometimes it also writes '/home: create/symlink failed, no inodes free'.
 
 Is that a bug or a missing feature? I should be able to keep control on
 the system even if I unplug the drive like a savage, no?

Depends what your softraid configuration is.

 Ken

 
 
 OpenBSD 5.3-beta (GENERIC.MP) #25: Fri Feb  1 16:29:00 MST 2013
 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 real mem = 4217044992 (4021MB)
 avail mem = 4082298880 (3893MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (73 entries)
 bios0: vendor LENOVO version 7LETC7WW (2.27 ) date 04/08/2010
 bios0: LENOVO 64644YG
 acpi0 at bios0: rev 2
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT ASF! SSDT 
 SSDT SSDT SSDT SSDT
 acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) IGBE(S4) EXP0(S4) 
 EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB2(S3) USB3(S3) 
 USB4(S3) EHC0(S3) EHC1(S3) HDEF(S4)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpiec0 at acpi0
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, 2194.86 MHz
 cpu0: 
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
 cpu0: 4MB 64b/line 16-way L2 cache
 cpu0: apic clock running at 199MHz
 cpu1 at mainbus0: apid 1 (application processor)
 cpu1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, 1995.00 MHz
 cpu1: 
 FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
 cpu1: 4MB 64b/line 16-way L2 cache
 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
 ioapic0: misconfigured as apic 2, remapped to apid 1
 acpimcfg0 at acpi0 addr 0xf000, bus 0-63
 acpihpet0 at acpi0: 14318179 Hz
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus -1 (AGP_)
 acpiprt2 at acpi0: bus 2 (EXP0)
 acpiprt3 at acpi0: bus 3 (EXP1)
 acpiprt4 at acpi0: bus 4 (EXP2)
 acpiprt5 at acpi0: bus 5 (EXP3)
 acpiprt6 at acpi0: bus 13 (EXP4)
 acpiprt7 at acpi0: bus 21 (PCI1)
 acpicpu0 at acpi0: C3, C2, C1, PSS
 acpicpu1 at acpi0: C3, C2, C1, PSS
 acpipwrres0 at acpi0: PUBS
 acpitz0 at acpi0: critical temperature is 127 degC
 acpitz1 at acpi0: critical temperature is 100 degC
 acpibtn0 at acpi0: LID_
 acpibtn1 at acpi0: SLPB
 acpibat0 at acpi0: BAT0 model 93P5030 serial   290 type LION oem SANYO
 acpibat1 at acpi0: BAT1 not present
 acpiac0 at acpi0: AC unit online
 acpithinkpad0 at acpi0
 acpidock0 at acpi0: GDCK not docked (0)
 cpu0: Enhanced SpeedStep 2194 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz
 pci0 at mainbus0 bus 0
 pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c
 vga1 at pci0 dev 2 function 0 Intel GM965 Video rev 0x0c
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 intagp0 at vga1
 agp0 at intagp0: aperture at 0xe000, size 0x1000
 inteldrm0 at vga1: apic 1 int 16
 drm0 at inteldrm0
 Intel GM965 Video rev 0x0c at pci0 dev 2 function 1 not configured
 em0 at pci0 dev 25 function 0 Intel ICH8 IGP M AMT rev 0x03: msi, address 
 00:1e:37:d4:07:a5
 uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: apic 1 int 20
 uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: apic 1 int 21
 ehci0 at pci0 dev 26 function 7 Intel 82801H USB rev 0x03: apic 1 int 22
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
 azalia0 at pci0 dev 27 function 0 Intel 82801H HD Audio rev 0x03: msi
 azalia0: codecs: Analog Devices AD1984, Conexant/0x2bfa, using Analog Devices 
 AD1984
 audio0 at azalia0
 ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x03: msi
 pci1 at ppb0 bus 2
 ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x03: msi
 pci2 at ppb1 bus 3
 iwn0 at pci2 dev 0 function 0 Intel Wireless WiFi Link 4965 rev 0x61: msi, 
 MIMO 2T3R, MoW2, address 00:1f:3b:69:98:83
 ppb2 at pci0 dev 28 function 2 Intel 82801H PCIE rev 0x03: msi
 pci3 at ppb2 bus 4
 ppb3 at pci0 dev 28 function 3 Intel 82801H PCIE rev 0x03: msi
 pci4 at ppb3 bus 5
 ppb4 at pci0 dev 28 function 4 Intel 82801H PCIE rev 0x03: msi
 pci5 at ppb4 

Re: How to configure pppoe client on OpenBSD?

[Kenneth R Westerback]

On Sun, Jan 13, 2013 at 08:42:37PM +0100, Peter N. M. Hansteen wrote:
 Jay Jennings l...@equineform.com writes:
 
  Rudeness is why people find openbsd hard for newbies; and potentially
  new funders of the projects and buyers of cds and merchandise.??
 
  As a 5 year user ... apropos is a new page for me too.
 
 In this case I'd call it 'terseness' rather than 'rudeness', but then in
 text-only communication there is I suppose scope for interpretation.
 
 I'm a bit surprised if the apropos command is not general knowledge. I
 think it's been available in some form on all unixishes I can remember,
 but I could have suppressed memories of some. ;)

apropos apropos ? :-)

 Ken

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

Re: vi vs ed in bsd.rd - proposal

[Kenneth R Westerback]

On Sat, Jan 12, 2013 at 01:34:44AM -0300, Carlo Borelli wrote:
 2013/1/12 Nick Holland n...@holland-consulting.net
 
  On 01/11/13 16:38, Paolo Aglialoro wrote:
  ...
   Btw, how many are really using ed everyday, now in 2013? I believe I'm
  not
   the only one who thinks this. My guess is that vi could be more
  appreciated
   by most of the user base more than ed.
 
  If you claim to be a unix administrator, learn ed.
 
 
 Sorry, completely wrong. An unix admin use only vi not wordstar or ed.
 

If you replace 'unix admin' with PFY, perhaps.

 Ken

Re: Foxconn NanoPC nT-i1250 fails to boot after install

[Kenneth R Westerback]

On Fri, Jan 11, 2013 at 01:16:53PM +0100, Martin Pieuchot wrote:
 On 10/01/13(Thu) 14:08, Kent Fritz wrote:
  On Thu, Jan 10, 2013 at 9:26 AM, Stefan Sperling s...@openbsd.org wrote:
   Can you please try to find out which protocol probe routine is
   responsible for hanging the machine?
  
  None of them.  I tried as you suggested, then just #if'd  out every
  entry in that structure.  No change in behavior.
  
  (BTW: First time compiling my own kernel.  The FAQ rocks!)
 
 Do you have any usb legacy option or similar turned on in your bios?
 If yes you can try to turn it off.
 
 M.
 

It was USB Legacy Storage on one of my machines. If this was on, then
booting hung in the BIOS if a USB disk was plugged in and then the boot
was attempted.

 Ken

Re: dhcrelay Can't find free bpf: No such file or directory

[Kenneth R Westerback]

On Tue, Jan 08, 2013 at 06:37:45PM +0100, Ulrich Drolshagen wrote:
 Hi,
 
 I am running an openbsd router attached to several vlans. On one of
 them there is running a box with an isc-dhcp server.
 For one of the vlans I have started a dhcrelay  to forward the dhcp
 broadcasts of the respective subnet to the server
 
 dhcrelay -i vlan5 172.16.1.4
 
 This is working fine for some time now. If I try to start it a
 second time, I get this:
 
 root:42# dhcrelay -d -i vlan6  172.16.1.4
 Can't find free bpf: No such file or directory
 Jan  8 18:33:05 router dhcrelay: Can't find free bpf: No such file
 or directory
 exiting.
 
 To my understanding dhcrelay should support whatever vlan requires
 forwarding the broadcasts. For me it does not make sense to only
 support just one subnet. Or am I missing something here?
 
 Thank you for looking into this
 
 Ulrich
 
 -- 
 http://www.ulrich-drolshagen.de
 

http://openbsd.org/report.html

 Ken

Re: Jan 4, 2013 snapshot fails with DHCP

[Kenneth R Westerback]

On Fri, Jan 04, 2013 at 02:10:02PM -0800, James A. Peltier wrote:
 - Original Message -
 | On Jan 04 12:05:53, jpelt...@sfu.ca wrote:
 |  I just tried to use the latest amd64 snapshot to prepare for an
 |  upgrade to our firewall.  We use DHCP during initial installation
 |  to PXE boot and perform the install at which point we configure
 |  through site52.tgz.  However, during installation and after boot
 |  DHCP reports the following error
 |  
 |Cannot lstat() '/var/db/dhclient.leases.bge0': No such file or
 |directory
 |  
 |  it does this for all interfaces and DHCP fails to configure the
 |  interface.  This does not happen with 5.2-RELEASE.
 | 
 | I've had the same problem with this snapshot.
 | Simply escaping to shell and doing
 | 
 |  /var/db/dhclient.leases.bge0
 | dhclient bge0
 | 
 | solved that.
 
 Yes, I am aware of that, but it doesn't work by default and that doesn't help 
 if you reboot and you are not at the console.  It's a bug and so I am 
 reporting it. ;)

It was fixed a day or so ago, so newer snaps should not have the problem.

 Ken

 
 -- 
 James A. Peltier
 Manager, IT Services - Research Computing Group
 Simon Fraser University - Burnaby Campus
 Phone   : 778-782-6573
 Fax : 778-782-3045
 E-Mail  : jpelt...@sfu.ca
 Website : http://www.sfu.ca/itservices
   http://blogs.sfu.ca/people/jpeltier
 
 The smartest people are constantly revising their understanding, 
 reconsidering a problem they thought they???d already solved. They???re open 
 to new points of view, new information, new ideas, contradictions, and 
 challenges to their own way of thinking. - Jeff Bezos

Re: 5.2 vs 5.1

[Kenneth R Westerback]

On Sun, Dec 30, 2012 at 09:01:41AM +, J Boehm wrote:
 I have recently tried out 5.2 on a slightly dated hardware (nvidia based,
 Athlon, 500MB Ram). Working with Seamonkey or Xombrero seems to be slow,
 pages load reluctantly in 5.2. Videos on Youtube are almost impossible to
 view. I tried changing settings in pf, cache, network cards etc but had to
 go back to 5.1. It seems there is some I/O problem with 5.2.
 
 Regards / J
 

Can you try a -current snapshot to see if the many fixes have helped the
situation?

 Ken

Re: A point about the BSD license I'm feeling edgy about

[Kenneth R Westerback]

On Sat, Dec 29, 2012 at 05:00:11PM +0100, Live user wrote:
 On 29/12/2012 16:50, Peter N. M. Hansteen wrote:
 If all you've done is compile something, you did not contribute anything
 copyrightable.  If you did contribute something copyrightable, you are
 free to add a copyright notice of your own, in addition to simliar
 notices from previous contributors.
 
 The point I want to reach here is,
 
 I get some BSD code, for example nginx, I improve it and add my
 copyright besides the original one.
 
 And I distribute object code only. I don't see how does this help
 nginx, It only helps me.

That's what we call 'freedom'. You are free to help others. Or not.
Your choice. Just don't claim you wrote something you didn't.

 Ken

Re: Goodbye to you my file descriptor - take 3

[Kenneth R Westerback]

On Thu, Dec 27, 2012 at 02:04:24PM +0100, Maxime Villard wrote:
 Well, as no one seems to give a fuck on tech@, I put a more
 glamourous title here.
 
 btw, i wonder why you don't put -Wextra to the makefile, you would
 see that there are a lot of unused parameters, comparisons between
 signed and unsigned, uninitialized vars, ...

Too many false positives to be useful.

People are running various static analysis packages over the tree
periodically to find such things. None are perfect so if you actually
find any you think are bugs, diffs are always appreciated.

 Ken

 
 
  Message original 
 Sujet: [PATCH] pfctl: leak  stuff
 Date : Sat, 22 Dec 2012 08:16:09 +0100
 De : Maxime Villard rusty...@gmx.fr
 Pour : t...@openbsd.org
 
 Hi,
 here are my small changes for pfctl.
 
 1) There are cases where we could leak a file descriptor by
returning.
 
 2) We don't need to check memory before freeing it, as
free() already does that.
 
 3) Just replaced a snprintf() by strlcpy(), it's faster.
 
 Ok/Comments ?
 
 
 
 Index: pfctl.c
 ===
 RCS file: /cvs/src/sbin/pfctl/pfctl.c,v
 retrieving revision 1.314
 diff -u -r1.314 pfctl.c
 --- pfctl.c   19 Sep 2012 15:52:17 -  1.314
 +++ pfctl.c   22 Dec 2012 07:08:28 -
 @@ -1377,8 +1377,7 @@
   err(1, DIOCXROLLBACK);
   exit(1);
   } else {/* sub ruleset */
 - if (path)
 - free(path);
 + free(path);
   return (-1);
   }
  
 @@ -1867,10 +1866,6 @@
   unsigned int len = 0;
   size_t n;
  
 - f = fopen(file, w);
 - if (f == NULL)
 - err(1, open: %s, file);
 -
   memset(ps, 0, sizeof(ps));
   for (;;) {
   ps.ps_len = len;
 @@ -1893,6 +1888,10 @@
   return; /* no states */
   len *= 2;
   }
 +
 + f = fopen(file, w);
 + if (f == NULL)
 + err(1, open: %s, file);
  
   n = ps.ps_len / sizeof(struct pfsync_state);
   if (fwrite(inbuf, sizeof(struct pfsync_state), n, f)  n)
 Index: pfctl_osfp.c
 ===
 RCS file: /cvs/src/sbin/pfctl/pfctl_osfp.c,v
 retrieving revision 1.18
 diff -u -r1.18 pfctl_osfp.c
 --- pfctl_osfp.c  18 Oct 2010 15:55:28 -  1.18
 +++ pfctl_osfp.c  22 Dec 2012 07:08:28 -
 @@ -112,16 +112,11 @@
  
   while ((line = fgetln(in, len)) != NULL) {
   lineno++;
 - if (class)
 - free(class);
 - if (version)
 - free(version);
 - if (subtype)
 - free(subtype);
 - if (desc)
 - free(desc);
 - if (tcpopts)
 - free(tcpopts);
 + free(class);
 + free(version);
 + free(subtype);
 + free(desc);
 + free(tcpopts);
   class = version = subtype = desc = tcpopts = NULL;
   memset(fp, 0, sizeof(fp));
  
 @@ -250,16 +245,11 @@
   add_fingerprint(dev, opts, fp);
   }
  
 - if (class)
 - free(class);
 - if (version)
 - free(version);
 - if (subtype)
 - free(subtype);
 - if (desc)
 - free(desc);
 - if (tcpopts)
 - free(tcpopts);
 + free(class);
 + free(version);
 + free(subtype);
 + free(desc);
 + free(tcpopts);
  
   fclose(in);
  
 @@ -513,7 +503,7 @@
   return (buf);
  
  found:
 - snprintf(buf, len, %s, class_name);
 + strlcpy(buf, class_name, len);
   if (version_name) {
   strlcat(buf,  , len);
   strlcat(buf, version_name, len);
 Index: pfctl_radix.c
 ===
 RCS file: /cvs/src/sbin/pfctl/pfctl_radix.c,v
 retrieving revision 1.29
 diff -u -r1.29 pfctl_radix.c
 --- pfctl_radix.c 27 Jul 2011 00:26:10 -  1.29
 +++ pfctl_radix.c 22 Dec 2012 07:08:28 -
 @@ -499,8 +499,7 @@
  {
   if (b == NULL)
   return;
 - if (b-pfrb_caddr != NULL)
 - free(b-pfrb_caddr);
 + free(b-pfrb_caddr);
   b-pfrb_caddr = NULL;
   b-pfrb_size = b-pfrb_msize = 0;
  }

Re: Strange behaviour on OpenBSD 5.2 and usb disk

[Kenneth R Westerback]

On Wed, Dec 19, 2012 at 05:23:55PM -0300, Marcos Laufer wrote:
 This is a DL360G3 running OpenBSD 5.2 . I can't use a  WD My Passport 
 USB disk, i get input/output error, here is what i got:
 
 # dmesg 
 OpenBSD 5.2 (GENERIC) #0: Fri Dec 14 23:58:18 ART 2012
 root@private:/u/system/src/sys/arch/i386/compile/GENERIC
 cpu0: Intel(R) Xeon(TM) CPU 3.06GHz (GenuineIntel 686-class) 3.07 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,SBF,CNXT-ID,xTPR
 real mem  = 3220738048 (3071MB)
 avail mem = 3157274624 (3011MB)
 mainbus0 at root
 bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf, 
 SMBIOS rev. 2.3 @ 0xec000 (42 entries)
 bios0: vendor HP version P31 date 01/28/2004
 bios0: HP ProLiant DL360 G3
 acpi0 at bios0: rev 0
 acpi0: sleep states S0 S4 S5
 acpi0: tables DSDT FACP APIC SPCR
 acpi0: wakeup devices
 acpitimer0 at acpi0: 3579545 Hz, 32 bits
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: apic clock running at 133MHz
 cpu at mainbus0: not configured
 cpu at mainbus0: not configured
 cpu at mainbus0: not configured
 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 16 pins
 ioapic1 at mainbus0: apid 3 pa 0xfec01000, version 11, 16 pins
 ioapic2 at mainbus0: apid 4 pa 0xfec02000, version 11, 16 pins
 ioapic3 at mainbus0: apid 5 pa 0xfec03000, version 11, 16 pins
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus 1 (PCI1)
 acpiprt2 at acpi0: bus 4 (PCI2)
 acpicpu0 at acpi0
 acpitz0 at acpi0: critical temperature is 31 degC
 bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xee000/0x2000!
 pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 pchb0 at pci0 dev 0 function 0 ServerWorks CNB20-HE Host (GC-LE) rev 0x33
 pchb1 at pci0 dev 0 function 1 ServerWorks CNB20-HE Host (GC-LE) rev 0x00
 pchb2 at pci0 dev 0 function 2 ServerWorks CNB20-HE Host (GC-LE) rev 0x00
 pci1 at pchb2 bus 1
 bge0 at pci1 dev 2 function 0 Broadcom BCM5703X rev 0x02, BCM5702/5703 A2 
 (0x1002): apic 3 int 14, address 00:0f:20:96:8c:de
 brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
 vga1 at pci0 dev 3 function 0 ATI Rage XL rev 0x27
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 ciss0 at pci0 dev 4 function 0 Compaq Smart Array 5i/532 rev.2 rev 0x01: 
 apic 3 int 15
 ciss0: 1 LD, HW rev 1, FW 2.36/2.36
 scsibus0 at ciss0: 1 targets
 sd0 at scsibus0 targ 0 lun 0: COMPAQ, LOGICAL VOLUME, 2.36 SCSI0 0/direct 
 fixed
 sd0: 17359MB, 512 bytes/sector, 35553120 sectors
 Compaq iLO rev 0x01 at pci0 dev 5 function 0 not configured
 Compaq iLO rev 0x01 at pci0 dev 5 function 2 not configured
 piixpm0 at pci0 dev 15 function 0 ServerWorks CSB5 rev 0x93: polling
 iic0 at piixpm0
 spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM registered ECC PC2100CL2.5
 spdmem1 at iic0 addr 0x52: 512MB DDR SDRAM registered ECC PC2100CL2.5
 spdmem2 at iic0 addr 0x54: 1GB DDR SDRAM registered ECC PC2100CL2.5
 spdmem3 at iic0 addr 0x56: 1GB DDR SDRAM registered ECC PC2100CL2.5
 pciide0 at pci0 dev 15 function 1 ServerWorks CSB5 IDE rev 0x93: DMA
 atapiscsi0 at pciide0 channel 0 drive 0
 scsibus1 at atapiscsi0: 2 targets
 cd0 at scsibus1 targ 0 lun 0: TEQC0 0, TV=28E=C0 0 0 0, R.4F ATAPI 5/cdrom 
 removable
 cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 1
 ohci0 at pci0 dev 15 function 2 ServerWorks OSB4/CSB5 USB rev 0x05: apic 2 
 int 10, version 1.0, legacy support
 pchb3 at pci0 dev 15 function 3 ServerWorks CSB5 LPC rev 0x00
 pchb4 at pci0 dev 17 function 0 ServerWorks CIOB-X2 PCIX rev 0x05
 pchb5 at pci0 dev 17 function 2 ServerWorks CIOB-X2 PCIX rev 0x05
 pci2 at pchb5 bus 4
 bge1 at pci2 dev 2 function 0 Broadcom BCM5703X rev 0x02, BCM5702/5703 A2 
 (0x1002): apic 3 int 13, address 00:0f:20:96:8c:e1
 brgphy1 at bge1 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
 usb0 at ohci0: USB revision 1.0
 uhub0 at usb0 ServerWorks OHCI root hub rev 1.00/1.00 addr 1
 isa0 at mainbus0
 isadma0 at isa0
 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
 pckbc0 at isa0 port 0x60/5
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard, using wsdisplay0
 pms0 at pckbc0 (aux slot)
 pckbc0: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0
 pcppi0 at isa0 port 0x61
 spkr0 at pcppi0
 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
 mtrr: Pentium Pro MTRR support
 umass0 at uhub0 port 4 configuration 1 interface 0 Western Digital My 
 Passport 0748 rev 2.10/10.15 addr 2
 umass0: using SCSI over Bulk-Only
 scsibus2 at umass0: 2 targets, initiator 0
 sd1 at scsibus2 targ 1 lun 0: WD, My Passport 0748, 1015 SCSI4 0/direct 
 fixed
 sd1: 953837MB, 512 bytes/sector, 1953458176 sectors
 ses0 at scsibus2 targ 1 lun 1: WD, SES Device, 1015 SCSI4 13/enclosure 
 services fixed
 

Re: PRIMERGY RX200 S2 installation problems

[Kenneth R Westerback]

On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
 here is the installation dmesg when trying to install the 5.2 i386 snapshot:

And the installation dmesg from a -current snapshot would be even
more useful.

 Ken

 
 -
 LSI Logic Corp. MPT IME  BIOS
 Copyright 1995-2005 LSI Logic Corp.
 MPTBIOS-IME-5.13.08
 
 CD-ROM: 9F
 Loading /5.2/I386/CDBOOT
 probing: pc0 apm pci mem[616K 2046M a20=on]
 disk: hd0+* cd0
  OpenBSD/i386 CDBOOT 3.17
 boot
 booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c
 entry point at 0x200128
 Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California. All rights reserved.
 Copyright (c) 19995-2012 OpenBSD. All rights reserved.
 http://www.OpenBSD.org
 OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
 der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
 cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz (GenuineIntel 686-class)
 cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR, PGE,MCA,
 CMOV, PAT, PSE36, CF
 LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
 ID,
 CX16,xTPR
 real mem = 2146414592 (2046MB)
 avail mem = 2183640064 (2006MB)
 mainbus0 at root
 bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418,
 SMBIOS
 rev. 2.33 @ 0xdc010 (58 entries)
 bios0: vendor FSC version 6.8 Rev. R04A5F1.1790 date 09/16/2005
 bios0: FUJITSU SIEMENES PRIMERGY RX200S2
 acpi0 at bios0: rev 0
 acpi0: sleep states S0 S1 S4 S5
 acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
 acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: apic clock running at 200MHz
 cpu at mainbus0: not configured
 cpu at mainbus0: not configured
 cpu at mainbus0: not configured
 ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
 ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
 ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
 acpiprt0 at acpi0: bus 2 (P2P3)
 acpiprt1 at acpi0: bus 3 (P2P4)
 acpiprt2 at acpi0: bus 0 (PCI0)
 acpiprt3 at acpi0: bus 4 (PCIB)
 bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
 pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 pchb0 at pci0 dev 0 function 0 Intel E7520 Host rev 0x09
 Intel E7520 Error Reporting rev 0x09 at pci0 dev 0 function 1 not
 configured
 ppb0 at pci0 dev 2 function 0 Intel E7520 PCIE rev 0x09
 pci1 at ppb0 bus 1
 ppb1 at pci1 dev 0 function 0 Intel 6700PXH PCIE-PCIX rev 0x09
 pci2 at ppb1 bus 2
 Intel IOxAPIC rev 0x09 at pci1 dev 0 function 1 not configured
 ppb2 at pci1 dev 0 function 2 Intel 6700PXH PCIE-PCIX rev 0x09
 pci3 at ppb2 bus 3
 em0 at pci3 dev 3 function 0 Intel PRO/1000MT (82545CM) rev 0x04: apic 2
 int1
 6, address 00:04:23:c4:01:16
 mpi0 at pci3 dev 5 function 0 Symbios Logic 53c1030 rev 0x07: msi
 scsibus0 at mpi0: 16 targets, initiator 7
 sd0 at scsibus0 targ 1 lun 0: LSILOGIC, 1030 IM, 1000 SCSI2 0/direct fixed
 sd0: 34700MB, 512 bytes/sector, 71065600 sectors
 mpi0: timeout
 mpi0: timeout
 mpi0: timeout
 mpi0: timeout
 mpi0: timeout
 mpi0: timeout
 mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
 em1 at pci3 dev 6 function 0 Intel PRO/100MT (82546GB) rev 0x03: apic 2
 int 1
 6uvm_fault (0xd07f31d8, 0x0, 0, 1) - e
 fatal page fault (6) in supervisor mode
 trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
 panic: trap type 6, code=0, pc=0
 The operating system has halted
 Please press any key to reboot
 ---
 
 Thanks
 
 On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
 n...@holland-consulting.netwrote:
 
  On 11/29/12 06:42, Tony Berth wrote:
   Thanks
  
   Both i386 and amd64 fail! But, are that many differences between stable
  and
   current?
 
  You caught us, nothing has changed in OpenBSD since 1995, we just drink
  beer and increment the version number every six months.
  /sarcasm
 
  The most significant changes tend to take place just AFTER unlocking of
  a new version of OpenBSD -- i.e., BEFORE the CDs ship.  So yes, -current
  is significantly different than the most recent release.
 
  Now, step away from the ! key, and lets see if we can help you help us
  help you.
 
  Here's the situation... apparently, no one has been installing OpenBSD
  on this particular machine before.  Never heard of it myself, whatever
  that means.  A quick google showed me a lot of PDF files I don't wish to
  look at, but apparently it is a rack-mount server.
 
  There's apparently a problem between this machine and OpenBSD.
 
  You have three choices I see:
  1) provide one or two of these machines to developers.
  2) provide useful information to developers
  3) give up, as without either 1 or 2, we aren't going to be able to help
  you.
 
  I'm going to guess you don't have the spare money/machine to provide a
  few machines to the project.
 
  The first piece of useful information we could use would be a COMPLETE
  dmesg, collected via a serial port as an install kernel boots.  

Re: OpenBSD hangs when i unplug USB disk

[Kenneth R Westerback]

On Fri, Nov 16, 2012 at 12:02:11PM -0300, Marcos Laufer wrote:
 
 Kenneth R Westerback wrote:
 On Thu, Nov 15, 2012 at 12:48:03PM -0300, Marcos Laufer wrote:
 Kenneth R Westerback wrote:
 On Wed, Nov 14, 2012 at 04:22:20PM -0300, Marcos Laufer wrote:
 Hello, i'd like to inform a problem when dettaching an external 1TB
 USB disk drive , the system just freezes, i can't type anything.
 Also It stops responding to ping.
 If i don't unplug it then i can use the disk normally, i can copy
 and delete files with no problem. But as soon as i unplug the USB
 cord, the machine freezes.
 I've tested it on several machines, different OpenBSD versions
 starting from 4.3, i'm not asking for support, i know old OpenBSD
 versions are no longer supported, but this seemed pretty odd, i
 suppose that plugging and unplugging a USB disk should not cause any
 problems on any OS version.
 
 These are the lines on dmesg about this disk:
 
 
 Nov 14 16:00:31 hq /bsd: umass0 at uhub0
 Nov 14 16:00:31 hq /bsd:  port 5 configuration 1 interface 0
 Western Digital My Passport 0748 rev 2.10/10.15 addr 2
 Nov 14 16:00:31 hq /bsd: umass0: using SCSI over Bulk-Only
 Nov 14 16:00:31 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
 Nov 14 16:00:31 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My
 Passport 0748, 1015 SCSI4 0/direct fixed
 Nov 14 16:00:38 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec 
 total
 Nov 14 16:00:38 hq /bsd: ses0 at scsibus0 targ 1 lun 1: WD, SES
 Device, 1015 SCSI4 13/enclosure services fixed
 Nov 14 16:00:38 hq /bsd: ses0: unable to read enclosure configuration
 
 Best regards,
 Marcos
 
 As an experiment, try going into boot's config (-c at the boot) and
 disable ses. Then see if a) the ses device is still present, and b)
 if the absence of the ses device(s) alleviate the symptoms.
 
  Ken
 
 
 Hello, i've just tried this. The ses device is not present when i
 disable it at boot time, but the problem persists, if i unplug the
 USB cord (no matter if the partition is mounted or not) the OS just
 freezes. So i guess it is not related to the ses driver.
 
 This are the dmesg lines of this experiment:
 
 Nov 15 12:32:52 hq /bsd: umass0 at uhub0
 Nov 15 12:32:52 hq /bsd:  port 5 configuration 1 interface 0
 Western Digital My Passport 0748 rev 2.10/10.15 addr 2
 Nov 15 12:32:52 hq /bsd: umass0: using SCSI over Bulk-Only
 Nov 15 12:32:52 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
 Nov 15 12:32:52 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My
 Passport 0748, 1015 SCSI4 0/direct fixed
 Nov 15 12:32:59 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
 Nov 15 12:32:59 hq /bsd: uk0 at scsibus0 targ 1 lun 1: WD, SES
 Device, 1015 SCSI4 13/enclosure services fixed
 
 
 Arrg. Need to kill all reference to that second device. Try a kernel with
 this diff. It should prevent probing anything but lun 0.
 
  Ken
 
 Index: umass_scsi.c
 ===
 RCS file: /cvs/src/sys/dev/usb/umass_scsi.c,v
 retrieving revision 1.38
 diff -u -p -r1.38 umass_scsi.c
 --- umass_scsi.c 17 Jul 2011 22:46:48 -  1.38
 +++ umass_scsi.c 15 Nov 2012 17:17:06 -
 @@ -92,7 +92,7 @@ umass_scsi_attach(struct umass_softc *sc
  scbus = umass_scsi_setup(sc);
  scbus-sc_link.adapter_target = UMASS_SCSIID_HOST;
 -scbus-sc_link.luns = sc-maxlun + 1;
 +scbus-sc_link.luns =  1;
  scbus-sc_link.flags = ~SDEV_ATAPI;
  scbus-sc_link.flags |= SDEV_UMASS;
 
 
 Ken, i've applied your patch on an old OpenBSD 4.5 i use for testing
 purposes and the problem got solved. Now i can unplug the USB disk
 and no freeze at all. Is it safe to apply it on older and newer
 OpenBSD versions as well?
 
 These are the new dmesg lines:
 
 umass0 at uhub0 port 5 configuration 1 interface 0 Western Digital
 My Passport 0748 rev 2.10/10.15 addr 2
 umass0: using SCSI over Bulk-Only
 scsibus0 at umass0: 2 targets, initiator 0
 sd0 at scsibus0 targ 1 lun 0: WD, My Passport 0748, 1015 SCSI4
 0/direct fixed
 sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
 
 and after unpluggin the USB cord i get:
 
 sd0 detached
 scsibus0 detached
 umass0 detached
 
 And the OS does not freeze anymore.
 
 Thank you very much!
 

I had deliberately NOT copied misc@ so random diagnostic  patches are not
floating around for the more excitable of our community to apply and
forget about. :-)

The diff is not the solution. It merely confirms that it is the ses*
devices that are the problem.

http://wdc.custhelp.com/app/answers/detail/a_id/3739/~/what-is-the-ses-driver,-why-is-it-needed,-and-how-to-get-the-driver-popup-to

is a fascinating page that google found for me. If you have windows or os x
available you might be able to disable the ses functionality, which would
be a better solution.

The proper OpenBSD solution is likely to involve upgrading the ses driver
to properly get disconnected.

 Ken

Re: OpenBSD hangs when i unplug USB disk

[Kenneth R Westerback]

On Wed, Nov 14, 2012 at 04:22:20PM -0300, Marcos Laufer wrote:
 Hello, i'd like to inform a problem when dettaching an external 1TB
 USB disk drive , the system just freezes, i can't type anything.
 Also It stops responding to ping.
 If i don't unplug it then i can use the disk normally, i can copy
 and delete files with no problem. But as soon as i unplug the USB
 cord, the machine freezes.
 I've tested it on several machines, different OpenBSD versions
 starting from 4.3, i'm not asking for support, i know old OpenBSD
 versions are no longer supported, but this seemed pretty odd, i
 suppose that plugging and unplugging a USB disk should not cause any
 problems on any OS version.
 
 These are the lines on dmesg about this disk:
 
 
 Nov 14 16:00:31 hq /bsd: umass0 at uhub0
 Nov 14 16:00:31 hq /bsd:  port 5 configuration 1 interface 0
 Western Digital My Passport 0748 rev 2.10/10.15 addr 2
 Nov 14 16:00:31 hq /bsd: umass0: using SCSI over Bulk-Only
 Nov 14 16:00:31 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
 Nov 14 16:00:31 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My
 Passport 0748, 1015 SCSI4 0/direct fixed
 Nov 14 16:00:38 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
 Nov 14 16:00:38 hq /bsd: ses0 at scsibus0 targ 1 lun 1: WD, SES
 Device, 1015 SCSI4 13/enclosure services fixed
 Nov 14 16:00:38 hq /bsd: ses0: unable to read enclosure configuration
 
 Best regards,
 Marcos
 

I procured the device and tried it here. It's interesting that some
laptops get the ses device and some don't.

Will play with it some more on the device that can see the ses to see
if we can reproduce the problem and perhaps get a solution. So far
no machine has hung even when they see the ses device, although we
haven't tried doing any i/o to it.

 Ken

Re: OpenBSD hangs when i unplug USB disk

[Kenneth R Westerback]

On Wed, Nov 14, 2012 at 04:22:20PM -0300, Marcos Laufer wrote:
 Hello, i'd like to inform a problem when dettaching an external 1TB
 USB disk drive , the system just freezes, i can't type anything.
 Also It stops responding to ping.
 If i don't unplug it then i can use the disk normally, i can copy
 and delete files with no problem. But as soon as i unplug the USB
 cord, the machine freezes.
 I've tested it on several machines, different OpenBSD versions
 starting from 4.3, i'm not asking for support, i know old OpenBSD
 versions are no longer supported, but this seemed pretty odd, i
 suppose that plugging and unplugging a USB disk should not cause any
 problems on any OS version.
 
 These are the lines on dmesg about this disk:
 
 
 Nov 14 16:00:31 hq /bsd: umass0 at uhub0
 Nov 14 16:00:31 hq /bsd:  port 5 configuration 1 interface 0
 Western Digital My Passport 0748 rev 2.10/10.15 addr 2
 Nov 14 16:00:31 hq /bsd: umass0: using SCSI over Bulk-Only
 Nov 14 16:00:31 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
 Nov 14 16:00:31 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My
 Passport 0748, 1015 SCSI4 0/direct fixed
 Nov 14 16:00:38 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
 Nov 14 16:00:38 hq /bsd: ses0 at scsibus0 targ 1 lun 1: WD, SES
 Device, 1015 SCSI4 13/enclosure services fixed
 Nov 14 16:00:38 hq /bsd: ses0: unable to read enclosure configuration
 
 Best regards,
 Marcos
 

As an experiment, try going into boot's config (-c at the boot) and
disable ses. Then see if a) the ses device is still present, and b)
if the absence of the ses device(s) alleviate the symptoms.

 Ken

Re: Possible regression on dhclient (current)

[Kenneth R Westerback]

On Tue, Nov 13, 2012 at 12:01:31AM +0200, Ville Valkonen wrote:
 Hello all,
 
 I was surfing on a Web when suddenly all traffic stopped. Closer examination
 revealed Too many open files failure with the dhclient. Since there have 
 been

You are not sufficiently current. That should have been fixed a couple of
days ago.

 Ken

 improvements in the dhclient lately, could this be related?
 
 Tried to do pkill -TERM dhclient  sudo dhclient trunk0 but no cigar. Any
 hints what to try the next time if this occurs? Uptime was 3 days if it 
 happens
 to matter. I'm also testing Brain Fuck Scheduler patch since it makes videos
 playable. Yes, I can rule it out by running GENERIC if necessary.
 
 Complete dmesg at the bottom of this message.
 
 But now, here's some information:
 $ dmesg |tail -100
 ...
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 ...
 
 /var/log/daemon:
 Nov 12 23:08:38  dhclient[9627]: DHCPDISCOVER on trunk0 to
 255.255.255.255 port 67 interval 3
 Nov 12 23:08:38  dhclient[9627]: DHCPOFFER from 192.168.50.101
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[9627]: DHCPREQUEST on trunk0 to
 255.255.255.255 port 67
 Nov 12 23:08:38  dhclient[9627]: DHCPACK from 192.168.50.101 
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[7427]: socket open failed: Too many open files
 Nov 12 23:08:38  dhclient[9627]: bound to 192.168.50.102 -- renewal in
 300 seconds.
 Nov 12 23:08:38  dhclient[9627]: DHCPDISCOVER on trunk0 to
 255.255.255.255 port 67 interval 3
 Nov 12 23:08:38  dhclient[9627]: DHCPOFFER from 192.168.50.101
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[9627]: DHCPREQUEST on trunk0 to
 255.255.255.255 port 67
 Nov 12 23:08:38  dhclient[9627]: DHCPACK from 192.168.50.101 
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[7427]: socket open failed: Too many open files
 Nov 12 23:08:38  dhclient[9627]: bound to 192.168.50.102 -- renewal in
 300 seconds.
 
 /var/log/messages
 Nov 12 23:11:59  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:12:21  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:14:58  last message repeated 15 times
 Nov 12 23:22:22  last message repeated 32 times
 Nov 12 23:22:24  dhclient[9276]: SIOCDIFADDR failed (192.168.50.102):
 Can't assign requested address
 Nov 12 23:22:24  dhclient[9276]: SIOCDIFADDR failed (192.168.50.102):
 Can't assign requested address
 Nov 12 23:22:27  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:23:04  last message repeated 5 times
 
 $ ulimit -a
 time(cpu-seconds)unlimited
 file(blocks) unlimited
 coredump(blocks) unlimited
 data(kbytes) 716800
 stack(kbytes)4096
 lockedmem(kbytes)1298308
 memory(kbytes)   3881796
 nofiles(descriptors) 500
 processes128
 
 NOTICE: Closed Chromium since it had several descriptors opened. After that
 fstat |wc -l   showed ~400. Tried to restart dhclient again but with no luck.
 
 
 $ route -n show # (not using inet6)
 Routing tables
 
 Internet:
 DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
 default192.168.50.101 UGS4  192 - 8 trunk0
 127/8  127.0.0.1  UGRS   00 33152 8 lo0
 127.0.0.1  127.0.0.1  UH 2 2935 33152 4 lo0
 192.168.50/24  link#5 UC 10 - 4 trunk0
 192.168.50.101 00:30:18:a4:f8:e3  UHLc   0   55 - 4 trunk0
 192.168.50.102 127.0.0.1  UG 00 3315256 lo0
 224/4  127.0.0.1  URS00 33152 8 lo0
 
 
 OpenBSD 5.2-current (GENERIC.MP) #0: Fri Nov  9 15:19:24 EET 2012
 weezel@:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 real mem = 4121640960 (3930MB)
 avail mem = 3989434368 (3804MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe0010 (44 entries)
 bios0: vendor LENOVO version 6JET93WW (1.51 ) date 03/26/2012
 bios0: LENOVO 284756G
 acpi0 at bios0: rev 4
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP HPET MCFG APIC BOOT SLIC SSDT SSDT SSDT
 acpi0: wakeup devices P0P2(S4) P0P1(S4) USB0(S3) USB1(S3) USB2(S3)
 USBR(S3) EHC1(S3) USB3(S3) USB4(S3) USB5(S3) EHC2(S3) HDEF(S4)
 PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4)
 RP04(S4) PXSX(S4) RP05(S4) RP06(S4) BLAN(S4) LID_(S3) SLPB(S3)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpihpet0 at acpi0: 14318179 Hz
 acpimcfg0 at acpi0 addr 0xe000, bus 0-255
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz, 1995.34 MHz
 cpu0: 
 

Re: Major dhclient(8) changes - no more dhclient-script

[Kenneth R Westerback]

On Sat, Nov 10, 2012 at 10:01:34AM +, johnw wrote:
 I have some problem after upgrade to new dhclient.
 my /etc/dhclient.conf:
 initial-interval 1;
 supersede domain-name .;
 supersede domain-name-servers 127.0.0.1;
 request subnet-mask,
 broadcast-address,
 routers;
 
 before upgrade, my /etc/resolv.conf
 search .
 nameserver 127.0.0.1
 lookup file bind
 
 after upgrade, my /etc/resolv.conf (only one line)
 lookup file bind

What is the date of the snapshot or source tree you upgraded to? I just
tried this configuration and it worked fine for me on -current.

Are there any messages in /var/log/daemon that might shed light on
what happened?

 Ken

 
 ??? johnw ?? Google  Major dhclient(8) changes - 
 no
 more dhclient-script ?? gmane.os.openbsd.tech Kenneth R Westerback ???
 (? 2012/11/9)
 
 Those of you following -current or running very recent snaps may have
 noticed a lot of changes to dhclient in the last couple of weeks. Aside
 from some major clean up, these changes revolve around the elimination
 of the dhclient-script as both detrimental to sanity and our ability to
 move forward to better network configuration automation. So far a
 couple of uses for dhclient-script have been reported and workarounds
 have to be developed for these scenarios. But now that most of the
 changes are committed we are very interested in making sure that
 scenarios that lead people to modify dhclient-script are identified
 sooner rather than later. So please test the new dhclient(8) in as many
 situations as possible and report both 'noraml' bugs/regressions and
 problems you have not been able to solve without dhclient-script.
 Thanks.  Ken
 
 
 - ?? Google ??? gmane.os.openbsd.tech
 -  Google 
 

Re: nfs_server=YES in /etc/rc.conf.local does not work

[Kenneth R Westerback]

On Sun, Oct 28, 2012 at 11:45:02AM +0400, Mike Korbakov wrote:
 Last chance to not mix up the problem. So I see the following problems:
 
 1. Search engine for the official site.
 Search should be available by simple actions: text entry and one-click (or 
 Enter)
 Search results from the official website should lead to also official 
 responses.
 All results on this page 
 http://www.google.com/search?q=%22nfs_server%22domains=www.openbsd.orgsitesearch=www.openbsd.orgbtnG=Search
 are located in the domain openbsd.org, their text looks correct. Without 
 special knowledge,
 no one can determine their relevance to real life.
 If I had special knowledge, then would not have used the search. 
 Someone does not agree?

Entering 'nfs_server' in the OpenBSD.org main page search *does*
find a spanish version of the FAQ from 2004 which has a single
reference to nfs_server. Unfortunately I can't read spanish so I
don't know what it says. However, as it is from 2004 it is undoubtably
wrong.

Going to the source tree and doing a find /usr/src/www -type f |
xargs grep nfs_server finds four mentions of nfs_server (es, pl,
pt, and zh faq6.html).

Going into the cvs repository via the web front end shows that
nfs_server got removed in r1.149 of rc.conf in 2011/07/08, as part
of the move to the rc.d framework.

Going into /etc/rc.conf itself shows some 'backward compatibility'
mentions of nfs_server. Which I guess are not sufficient to make
nfs_server work as you desire.

It looks to me like it's almost time to remove that backward
compatibility code and dead language translations of the FAQ, lest
others be misled.

 Ken

Re: nfs_server=YES in /etc/rc.conf.local does not work

[Kenneth R Westerback]

On Sun, Oct 28, 2012 at 02:43:51PM +0100, Antoine Jacoutot wrote:
 On Sun, Oct 28, 2012 at 09:25:24AM -0400, Kenneth R Westerback wrote:
  On Sun, Oct 28, 2012 at 11:45:02AM +0400, Mike Korbakov wrote:
   Last chance to not mix up the problem. So I see the following problems:
   
   1. Search engine for the official site.
   Search should be available by simple actions: text entry and one-click 
   (or Enter)
   Search results from the official website should lead to also official 
   responses.
   All results on this page 
   http://www.google.com/search?q=%22nfs_server%22domains=www.openbsd.orgsitesearch=www.openbsd.orgbtnG=Search
   are located in the domain openbsd.org, their text looks correct. Without 
   special knowledge,
   no one can determine their relevance to real life.
   If I had special knowledge, then would not have used the search. 
   Someone does not agree?
  
  Entering 'nfs_server' in the OpenBSD.org main page search *does*
  find a spanish version of the FAQ from 2004 which has a single
  reference to nfs_server. Unfortunately I can't read spanish so I
  don't know what it says. However, as it is from 2004 it is undoubtably
  wrong.
  
  Going to the source tree and doing a find /usr/src/www -type f |
  xargs grep nfs_server finds four mentions of nfs_server (es, pl,
  pt, and zh faq6.html).
  
  Going into the cvs repository via the web front end shows that
  nfs_server got removed in r1.149 of rc.conf in 2011/07/08, as part
  of the move to the rc.d framework.
  
  Going into /etc/rc.conf itself shows some 'backward compatibility'
  mentions of nfs_server. Which I guess are not sufficient to make
  nfs_server work as you desire.
  
  It looks to me like it's almost time to remove that backward
 
 This I am all for.
 
  compatibility code and dead language translations of the FAQ, lest
  others be misled.
 
 I don't really agree with that. The outdated translations are not linked from 
 the main OpenBSD page, I always make sure of it.
 Of course you can still see them by going directly to the URL but well...

The problem is that they are still visible to the search function. Well,
at least the spanish one was.

 Ken

 
 -- 
 Antoine

Re: The little ssh that (sometimes) couldn't

[Kenneth R Westerback]

On Sun, Oct 28, 2012 at 04:02:08PM +0100, Peter N. M. Hansteen wrote:
 I stumbled across this little gem of a blog post, I think this deserves
 a wider audience, via my twitter feed:
 http://mina.naguib.ca/blog/2012/10/22/the-little-ssh-that-sometimes-couldnt.html
 
 To be filed under tcpdump is your friend and I must say I admire their
 perseverance in finding the root cause of the problem.
 
 - Peter
 -- 
 Peter N. M. Hansteen, member of the first RFC 1149 implementation team
 http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
 Remember to set the evil bit on all malicious network traffic
 delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
 

Very nice story!

 Ken

Re: OpenBSD-5.1 hangs on Supermicro X9DR3-F

[Kenneth R Westerback]

On Thu, Oct 11, 2012 at 12:30:56PM +0600,  ??? wrote:
 Hello!
 
 we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs about 1
 times a day.
 5.1 does not understand i350 chip, so we put external Intel PRO/1000 MT
 (82574L) nic.
 
 we have ddb.panic=1, but no ddb appears on screen on hang.
 also, it says savecore: no core dump during boot.
 
 we tested RAM with memtest, so we do not suspect it for memory related
 issue.
 
 
 how can we diagnose those hangs ?
 is it ok to run 5.1 on X9DR3-F ?
 
 do I need to provide dmesg output ? any other kind of diagnostics ?
 
 Cheers,
 Ilya Shipitsin
 

http://openbsd.org/report.html

 Ken