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

[Kenneth Westerback]

On 8 October 2015 at 07:13, Marcus MERIGHI  wrote:
> mcmer-open...@tor.at (Marcus MERIGHI), 2015.10.08 (Thu) 12:26 (CEST):
>> 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'.
>
> After reading the commit log for softraid I am pretty sure the answer
> is 'no'. Therefore I have a) a patch for softraid(4) and b) another
> question.
>
> Question: searching for large (>1TB) HDDs I found there's '512e' [1]. Is
> this enough for softraid to work? The wikipedia article reads good, just
> to make sure.

Yes, disks that are 4K internally but present as 512-byte devices work fine.

 Ken

>
> Index: softraid.4
> ===
> RCS file: /cvs/src/share/man/man4/softraid.4,v
> retrieving revision 1.41
> diff -u -p -u -r1.41 softraid.4
> --- softraid.4  14 Apr 2015 19:10:13 -  1.41
> +++ softraid.4  8 Oct 2015 10:53:25 -
> @@ -208,3 +208,5 @@ due to component failure.
>  RAID is
>  .Em not
>  a substitute for good backup practices.
> +.Pp
> +Only disks with 512 bytes per sector are supported.
>
> [1] https://en.wikipedia.org/wiki/Advanced_Format#512e
>
> Bye, Marcus
>
>> 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
>>
>> > On Mar 19, 2014 11:36 AM, "Marcus MERIGHI"  wrote:
>> >
>> > > Reference:
>> > > ``Softraid 3TB Problems''
>> > > http://marc.info/?l=openbsd-misc&m=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 [f

OpenBSD Foundation GSOC 2015

[Kenneth Westerback]

The OpenBSD Foundation is pleased to announce that we have been
accepted as a mentoring organization for Google Summer of Code 2015.
As such if you are a student who qualifies to apply for GSOC, you will
be able to find us in Google's Summer of Code Application process.For
details on the application process and the relevant timelines please see

https://www.google-melange.com/gsoc/homepage/google/gsoc2015

We have an ideas page which is located at

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

I will repeat my usual disclaimer here on behalf of the foundation -
doing anything with GSOC does *not* guarantee the result will end up
in OpenBSD or any related project. That having been said
we hope to be able to put some mentors together with students to
accomplish things that may become useful to the community at large.

 Ken Westerback, The OpenBSD Foundation 

Re: crowding out bsd using systemd?

[Kenneth Westerback]

On 28 June 2014 13:55, frank ernest  wrote:
> Hello, I'm ballsystemlord from the Opensuse forums and I've been reading
> a lot about how systemd is unportable, even for use with some linux
> programs and the systemd devs are not concerned about it. I, as a single
> person, can't possibly hope to maintain the old sysVinit system and also
> systemd is a dameon controlling process, not restricted to only boot. A
> usr of bsd showed up
> http://forums.opensuse.org/showthread.php/498290-systemd/page4 mentioning
> that bsd is being crowded out, a thought that had not crossed my mind. I
> wanted to know, before assuming that it is the case everywhere, do people
> really not like systemd and is it really hurting bsd? If so, I'd be
> interested in doing something about it. Thanks, David
>

Yep, people really do not like systemd. Leaving aside the problem that
it seems to be so Linux-centric it is impossible to port elsewhere.

Note that OpenBSD has never used sysVinit or variants. We have a much
simpler system that works well as long as the software being
controlled is well written.

That said there is a GSOC project underway as we type to bring a much
slimmed down systemd look-alike functionality to OpenBSD to allow more
not-well written software to be ported.

 Ken

Re: PXE auto_install

[Kenneth Westerback]

On 24 June 2014 11:10, ML mail  wrote:
> Hi,
>
> The new OpenBSD auto_install with PXE works like a charm and just have 2 
> questions regarding the install.conf file I did not manage to find out yet:
>
> 1) how can I install the bsd.mp instead of the standard bsd image?

bsd.mp should be copied and used by default on systems with >1 CPU.
There is no way I know of to force bsd.mp to be used on uniprocessor
systems, although it can be copied to the target system.

> 2) how can I custom partition my disk (I would like 1 partition for root and 
> one for swap) ?

At the moment you can't.

 Ken

>
> Regards
> ML

Re: dhclient question

[Kenneth Westerback]

On 23 June 2014 06:24, Avi Cohen  wrote:
> Hello
> In my application  (it is a router in the access)  I'm initially  running
> dhclient daemon without any  interface specified for dhcp.
> Then - on user request - we  add  interfaces  to dhclient.conf on run-time
>
> I have 3 questions  - that I'll appreciate if you can answer

You can read dhclient(8) and dhclient.conf(5) man pages for details.
But to summarize ...

(You seem to ask 4 questions, so which one will you not appreciate an
answer to? :-))

>
> 1.   Is it possible to append  interfaces  to an existing dhclient.conf ?
> or just to add a new (for example)  dhclient.conf-eth1?  [BTW - where to
> locate this file ?]

You can append as many 'interface' statements as you like in the
dhclient.conf file. If you want to run with a separate config file for
a particular instance of dhclient you can use the '-c' option to
specify the non-default file.

>
> 2.When the daemon will  start the dhcp-request for this new  interface
> ?

When you start it. Every interface's dhclient must be started
separately. If you start a dhclient without specifying the interface
it attempts to find an interface in the 'egress' group. If there is
one and only one such interface then dhclient will use it. For other
interfaces you must start other instances of dhclient, usually by
creating a /etc/hostname. file for that interface. The
/etc/hostname. file will be used at system startup or you can 'sh
/etc/netstart ' as root.

>
> 3.   Our application need to be informed whenever a new IP-address (dhcp)
> is assigned for the interface.  How to do it ? by polling the dhclient.leases
> ?  is there a notification from dhclient to  our application that we can use
> ?

The best way to do that is with a program that monitors the routing
socket, where you can see all address changes.

Alternatively you can monitor the leases file or use the '-L' option
to write out the offered and effective lease information if you want
complete information on what is being received and used. Some people
use the entr port (/usr/ports/sysutils/entr, http://entrproject.org/)
to monitor the file(s).

>
> 4.   4 - if I start the dhclient daemon without interface specified - I
> see that it sends  dhcp-request for all my exiting interfaces ? why ? how to
> disable this behavior and to send request for only
>
> Specified interfaces ? (but without specifying  it in the command line- but
> via dhclient.conf  ?

Now you make me doubt you are running OpenBSD. Our dhclient does not
send dhcp-request for all interfaces -- it sends dhcp-requests out one
and only one interface. At least for the last 10 years or more.

You must specify the interface via the command line, or have the
/etc/netstart command build the command line for you from a
hostname. file.

 Ken

>
>
>
> Regards,
> Avi

Re: signing release files

[Kenneth Westerback]

On 17 June 2014 07:37, Nick Holland  wrote:
> On 06/17/14 02:40, Jiri B wrote:
>> On Mon, Jun 16, 2014 at 05:47:03PM -0400, Nick Holland wrote:
>>> [diff to easily allow different keys]
>>>
>>> I think focus has been lost.
>>>
>>> What's the point of signing releases?  To say "This came from the
>>> OpenBSD project".
>>>
>>> Why?  To make sure your release is a pure, untampered with version.
>>>
>>> Signed releases is not a goal, the goal is an install that is
>>> trusted by the installer (you).  Signed releases are a way to help
>>> reach that goal.  Don't forget that.
>>>
>>> IF your release is from the OpenBSD project, the signing should work
>>> fine.  If your release is from some other souce...I WANT an alert
>>> saying "This is not signed by OpenBSD"!  I don't want to squish the
>>> alert.  It isn't there to hit a checkbox "Code signed by someone".
>>>
>>> If your use is such that you DO want to certify that YOU created the
>>> files in question, that's great, ok, you have got a great
>>> "mini-fork" -- you can easily build your own release with your own
>>> keys and manage them appropriately, but a knob to get around the
>>> very point of release file signing is not really what I want to see.
>>>
>>> Nick.
>>
>> The problem is political. Does OpenBSD make life easier for people
>> who want to customize release build/installation by default or
>> these people should maintain their diffs separately.
>
> OpenBSD is quite different from many open source projects, where they
> have a fear of offending any one person or group, and thus end up with
> three different packet filters, several different packing management
> systems, etc.
>
> Internally, one of the biggest insults in the project is to call a
> suggestion a "usless knob", and great pride is taken in deleting code
> and options that just shouldn't be there.  I think this falls under that
> category.
>
>> Technically, how does verification of siteXX.tgz work? IIUC it does
>> not.
>
> It "works" exactly as intended: your siteXX.tgz file is something YOU
> generated, OpenBSD has no idea what's in it.  If you can't trust your
> siteXX.tgz file and how it gets from you to you, you have much bigger
> problems that signing isn't going to fix.
>
> Again, you are confusing the goal with the tool used to help achieve the
> goal.  "signing" is NOT the goal.
>
> I've had this discussion often.  It often goes like this:
>"We want to implement two factor authentication" (followed by a
> description that is much more based on convenience than security)
>me: "Two factor authentication should not be the goal, it should be
> the means to the goal: security.  You are subverting the security of TFA"
>"Oh, I know." (followed by a return to the subverted two-factor
> authentication system again)
>me: "You are undoing the benefits of two-factor authentication"
>"But two-factor is good!"  (at which point, I think about driving a
> truck for a living)
>
>> I don't see what's the problem to provide one variable.
>
> much the same reason why we don't have a magic switch to disable stack
> smash protection or W^X protection.  The point of the signing is simple
> and limited.  Having worked with some systems which offer the kind of
> feature you request and speaking only for myself, I'm happy with this.
>
>> Why are
>> there MD* variables and override functions one could use but are not
>> used by default (override/add into install.md)?
>
> because they add features /the developers desire/ without disabling
> security?
>
> Nick.
>

Nick once more hits the nail on the head. Driving it fully into the
wood one can only hope.

As, to the best of my recollection, the originator of the MD*
variables I can say that they were intended - nay, forced upon us - to
support differences between the needs of different architectures. Not
to provide knobs to allow site customization. The ideal would be to
completely eliminate them and the install.md files.

 Ken

Re: Wrong Shutdown

[Kenneth Westerback]

On May 26, 2014 9:53 AM, "Walter Souza"  wrote:
>
> Why OpenBSD has no interest in using journal file system?
>

OpenBSD has great interest in using journal filesystem. Nobody has sent us
the diffs that would add one.

 Ken

>
> On Mon, May 26, 2014 at 10:48 AM, Theo de Raadt wrote:
>
> > > I have a machine with a HardDrive with a slice of 2.7TB, and I have no
> > > UPS.. when sometimes I have power failure, and consequently a wrong
> > > shutdown, The fsck spends much time to recover the filse system, what
> > can I
> > > do? I need to be faster.
> >
> > Get a UPS.
> >
> > fsck is required to ensure the directory hierarchy is coherent.
> >
>
>
>
> --
> Walter Neto
> Analista Desenvolvedor

Re: Snapshot and packages

[Kenneth Westerback]

On 24 May 2014 09:59, Stan Gammons  wrote:
>
> On 05/24/2014 08:51 AM, Kenneth Westerback wrote:
>>
>> On 24 May 2014 09:31, Stan Gammons  wrote:
>>>
>>> I thought I understood the different flavors of OpenBSD but apparently
>>> not since I keep getting version errors when I try to add packages to
>>> sparc64 snapshots. The packages I'm trying are from the
>>> /snapshot/packages/sparc64 folder on the same mirror I got the snapshot .iso
>>> from.  Are these the packages one is suppose to use?  If not, how does one
>>> determine which packages will work with a snapshot?
>>>
>>>
>>> Stan
>>>
>> Can you be more specific about what 'version errors' you are seeing?
>> And the dates of the snapshots you are using?
>>
>>  Ken
>
>
> Ken, the snapshot .iso is 05-24-2014.  The packages are 05-23-2014. Below is
> the error.  I take it it's want libc.so.74 and the installed version is
> libc.so.75
>
>
>
> Stan

Well, mismatches like that happen a lot during library changes. Not
much we can do about it giving the differing speeds of building a snap
and generating a new set of packages.

In this case the bump to 75.0 took place on May 12th, so that seems a
bit long, but not impossible. The only solution is to wait for the
packages to be updated.

 Ken

>
>
> # pkg_add -v bison
> Can't install libiconv-1.14p1 because of libraries
> |library c.74.2 not found
> | /usr/lib/libc.so.75.0 (system): bad major
> Can't install gettext-0.18.2p4: can't resolve libiconv-1.14p1
> Can't install bison-2.3p1: can't resolve gettext-0.18.2p4,libiconv-1.14p1
> #
> # ls /usr/lib
> crt0.o  libedit.a   libfuse.a libmenu.so.6.0
> libocurses.alibpcap_p.a libsndio_p.alibtermlib_p.a
> crtbegin.o  libedit.so.5.1  libfuse.so.1.1 libmenu_p.a
> libocurses.so.6.0   libperl.a libsqlite3.alibusbhid.a
> crtbeginS.o libedit_p.a libfuse_p.a libmenuw.a
> libocurses_p.a  libperl.so.15.0 libsqlite3.so.27.0  libusbhid.so.7.0
> crtend.olibevent.a  libiberty.a libmenuw.so.6.0
> libossaudio.a   libpthread.a libsqlite3_p.a  libusbhid_p.a
> crtendS.o   libevent.so.4.1 libiberty.so.11.0 libmenuw_p.a
> libossaudio.so.4.0  libpthread.so.18.0 libssl.alibutil.a
> debug   libevent_p.alibiberty_p.a libmilter.a
> libossaudio_p.a libpthread_p.a libssl.so.24.1  libutil.so.12.1
> gcc-lib libexpat.a  libkeynote.a libmilter.so.3.0
> libotermcap.a   libreadline.a libssl_p.a  libutil_p.a
> gcrt0.o libexpat.so.11.0libkeynote_p.a libmilter_p.a
> libotermcap.so.6.0  libreadline.so.4.0 libstdc++.a liby.a
> libc.a  libexpat_p.alibkvm.a libncurses.a
> libotermcap_p.a libreadline_p.a libstdc++.so.57.0   liby_p.a
> libc.so.75.0libfl.a libkvm.so.16.0 libncurses.so.14.0
> libpanel.a  librpcsvc.a libstdc++_p.a   libz.a
> libc_p.alibfl_p.a   libkvm_p.a libncurses_p.a
> libpanel.so.6.0 librpcsvc.so.2.0 libsupc++.a libz.so.5.0
> libcrypto.a libform.a   libl.a libncursesw.a
> libpanel_p.alibrpcsvc_p.a libsupc++_p.a   libz_p.a
> libcrypto.so.27.0   libform.so.6.0  libl_p.a libncursesw.so.14.0
> libpanelw.a libskey.a libtermcap.apkgconfig
> libcrypto_p.a   libform_p.a libm.a libncursesw_p.a
> libpanelw.so.6.0libskey.so.6.0 libtermcap.so.14.0
> libcurses.a libformw.a  libm.so.9.0 libobjc.a
> libpanelw_p.a   libskey_p.a libtermcap_p.a
> libcurses.so.14.0   libformw.so.6.0 libm_p.a libobjc.so.6.0
> libpcap.a   libsndio.a libtermlib.a
> libcurses_p.a   libformw_p.alibmenu.a libobjc_p.a
> libpcap.so.8.0  libsndio.so.6.0 libtermlib.so.14.0
> #

Re: Snapshot and packages

[Kenneth Westerback]

On 24 May 2014 09:31, Stan Gammons  wrote:
> I thought I understood the different flavors of OpenBSD but apparently not 
> since I keep getting version errors when I try to add packages to sparc64 
> snapshots. The packages I'm trying are from the /snapshot/packages/sparc64 
> folder on the same mirror I got the snapshot .iso from.  Are these the 
> packages one is suppose to use?  If not, how does one determine which 
> packages will work with a snapshot?
>
>
> Stan
>

Can you be more specific about what 'version errors' you are seeing?
And the dates of the snapshots you are using?

 Ken

Re: Get rid of /bsd: arp info overwritten for ?

[Kenneth Westerback]

On 21 May 2014 07:20, bodie  wrote:
> On 21.05.2014 12:50, bodie wrote:
>>
>> On 21.05.2014 11:18, bodie wrote:
>>>
>>> Hi,
>>>
>>> testing http://marc.info/?t=14002453903&r=1&w=2 further and now I
>>> hit issue with corporate WIFI. I can connect perfectly fine to 2 of
>>> them provided with WPA2-PSK, either with regular ifconfig or with
>>> wpa_supplicant from packages, but the thing is that my
>>> /var/log/messages is flooded by these messages repeating like every
>>> 3s:
>>>
>>> /bsd: arp info overwritten for GW_IP by MAC_1 on iwn0
>>> /bsd: arp info overwritten for GW_IP by MAC_2 on iwn0
>>>
>>> arp -a shows only one MAC all the time and that's MAC_2 no matter if
>>> I reboot or just reconnect to network. Info from inside about setup of
>>> those APs is:
>>>
>>> There actually are 2 gateways having the same IP address GW_IP and
>>> the mac addresses belong to them. They work as failover and also load
>>> balacer.
>>>
>>> Not sure if it's because of that or because of ARP flooding in
>>> /var/log/messages, but performance of those WiFi is quite strange like
>>> ping replies over 20ms, a lot of web services doesn't work, takes
>>> years to connect, some are running perfectly fine immediately and
>>> such.
>>>
>>> So.
>>>
>>> 1) Is there anything I can do with ARP messages in /var/log/messages?
>>> Nothing in man arp and some sysctl switch I found only in FreeBSD
>>> 2) Is there anything what can be tweaked from OpenBSD side to improve
>>> general performance of WiFi connection or is it just either AP fix or
>>> nothing?
>>>
>>> Thanks a lot
>>
>>
>>
>> Still trying to get much more info, but that setup must be horrible.
>> Trying arping results in:
>>
>> 30 packets sent, 60 received. Always doubled response with MAC_1 and MAC_2
>>
>> When trying to ping some of the internal servers they all have
>> 123.123.123.123 IP which is of course totally wrong. Same if tried
>> with dig @GW_IP server_IP (as GW_IP is set as DNS by dhclient)
>>
>> So now not so sure if it's terrible AP setup or if it's something in
>> ARP, dhclient, ieee80211 code in OpenBSD
>
>
>
> Even more suspicious details:
>
> option dhcp-client-identifier 1:0:c2:c6:1c:af:ac in lease from dhclient, but
> my MAC is 00:c2:c6:1c:af:ac. It got mangled or is it on purpose?

This one I can solve. :-) It's on purpose and according to spec. the
prepended '1' indicates the type of identifier. In this case an
ethernet MAC.

> (investigating in the meantime of course :-))
> dhcp-server-identifier is IP of totally different subnet (10..) instead of

You can always add a 'reject' statement in your dhclient.conf to
ignore suspicious dhcp servers. As the man page says "although it
should be a last resort - better to track down the bad DHCP server and
fix it.". Assuming it turns out to be a rogue or misconfigured dhcp
server. It seems unlikely from the other symptoms you mention.


> 192... of that AP/GW
>

Well, there is no reason the dhcp server should be on the AP/GW. Of
course, no reason it shouldn't.

A tcpdump  (tcpdump -i  -s 2000 -vv -X) might show you who is
sending what.

 Ken

Re: smtpd stops immediately after starting in -current

[Kenneth Westerback]

On 18 May 2014 15:19, Norman Golisz  wrote:
> Hi Gilles,
>
> On Sun May 18 2014 13:45, Gilles Chehade wrote:
>> can you share your configuration file ?
>>
>> i'm unable to reproduce no matter what i try :-/
>
> I'm also able to reproduce this crash:
>
> $ echo test | mail norman && sudo smtpd -dv
>
> debug: init ssl-tree
> info: OpenSMTPD 5.4.3 starting
> debug: bounce warning after 4h
> debug: using "fs" queue backend
> debug: using "ramqueue" scheduler backend
> debug: using "ram" stat backend
> info: startup [debug mode]
> debug: init ssl-tree
> debug: parent_send_config_ruleset: reloading
> debug: parent_send_config: configuring pony process
> debug: parent_send_config: configuring ca process
> debug: init private ssl-tree
> debug: queue: done loading queue into scheduler
> debug: ca_engine_init: using RSAX engine support
> debug: smtp: listen on 127.0.0.1 port 25 flags 0x0 pki ""
> debug: smtp: listen on IPv6:fe80::1%lo0 port 25 flags 0x0 pki ""
> debug: smtp: listen on IPv6:::1 port 25 flags 0x0 pki ""
> debug: smtp: will accept at most 501 clients
> debug: smtpd: scanning offline queue...
> debug: smtpd: enqueueing offline message
> /var/spool/smtpd/offline/1400440122.uj4xYO8YaC
> debug: smtpd: offline scanning done
> debug: smtp: new client on listener: 0x14804c2680c0
> smtp-in: New session 80dc422d384e8c2d from host 1000@localhost [local]
> warn: parent -> pony: pipe closed
> warn: queue -> pony: pipe closed
> warn: ca -> pony: pipe closed
> warn: control -> pony: pipe closed
> warn: scheduler -> queue: pipe closed
> warn: lka -> pony: pipe closed
>
>
> smtpd.conf:
>
> listen on lo0
>
> table aliases db:/etc/mail/aliases.db
>
> table secrets { me => me.local:whoohoo}
>
> accept for local alias  deliver to maildir
> accept for any relay via tls+auth://m...@smtp.me.local:587 auth 
>
>
> dmesg:
>
> OpenBSD 5.5-current (GENERIC.MP) #132: Fri May 16 10:26:11 MDT 2014
> t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Try with something newer. Others (including me) have found today's
snap to work. For as yet unknown reasons.

 Ken

> real mem = 4166717440 (3973MB)
> avail mem = 4047036416 (3859MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries)
> bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012
> bios0: LENOVO 6475BE3
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA 
> DMAR 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 P8400 @ 2.26GHz, 2261.31 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,NXE,LONG,LAHF,PERF
> cpu0: 3MB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
> cpu0: apic clock running at 266MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF
> cpu1: 3MB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 2, remapped to apid 1
> acpimcfg0 at acpi0 addr 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 -1 (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, resource for USB0, USB3, USB5, EHC0, EHC1
> 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 "42T5264" serial  3499 type LION oem "Panasonic"
> acpibat1 at acpi0: BAT1 not present
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock0 at acpi0: GDCK docked (15)
> cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 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
>

Re: smtpd stops immediately after starting in -current

[Kenneth Westerback]

On 18 May 2014 07:52, Gilles Chehade  wrote:
> On Sun, May 18, 2014 at 07:37:26AM -0400, Kenneth Westerback wrote:
>> On 18 May 2014 05:37, Gilles Chehade  wrote:
>> > On Sat, May 17, 2014 at 10:40:13PM -0400, Allan Streib wrote:
>> >> On Sat, May 17, 2014, at 05:30 PM, Allan Streib wrote:
>> >>
>> >> > Just upgraded to -current from my local mirror. Was previously working
>> >> > with a recent-ish -current (late April or early May)
>> >>
>> >> By "current" I meant "snapshot" sorry if that caused any confusion.
>> >>
>> >
>> > I'll have a look at this, thanks
>> >
>> > --
>> > Gilles Chehade
>> >
>> > https://www.poolp.org  @poolpOrg
>> >
>>
>> I've found that if there is anything processed from the offline queue
>> then smtpd stops immediately. If I remove all offline files then smtpd
>> starts up fine but as soon as I send an email (using mutt) it exits.
>>
>
> strange :-/
>
> I am running an opensmtpd -current on top of a snapshot one week-old and
> no matter what I try I can't reproduce with the default configuration.

Oddly enough, I upgraded a working machine that had a week old
snapshot to -current and that's when the problem surfaced. :-)

I suspect some LibreSSL fall out, but only because of the churn there,
not because of anything I saw go by that I can link to the issue.

 Ken

>
> I just tried to enqueue offline mails after reading your mail:
>
> $ echo test | mail gilles && sudo smtpd -dv
> debug: init ssl-tree
> info: OpenSMTPD 5.4.3 starting
> [...]
> debug: smtpd: scanning offline queue...
> debug: smtpd: enqueueing offline message 
> /var/spool/smtpd/offline/1400413673.u5SMhBkRCh
> debug: smtpd: offline scanning done
> debug: smtp: new client on listener: 0x13b5a7e68100
> smtp-in: New session 4af9e1d27b2d9096 from host 0@localhost [local]
> debug: 0x13b7b4d9c000: end of message, msgflags=0x
> smtp-in: Accepted message 1540150a on session 4af9e1d27b2d9096: 
> from=, to=, size=169, ndest=1, 
> proto=ESMTP
> debug: scheduler: evp:1540150aac11ccde scheduled (mda)
> smtp-in: Closing session 4af9e1d27b2d9096
> debug: smtp: 0x13b7b4d9c000: deleting session: done
> mda: new user 4af9e1d38d21e391 for ":gilles"
> debug: lka: userinfo :gilles
> debug: mda: new session 4af9e1d4e7c887ea for user ":gilles" evpid 
> 1540150aac11ccde
> debug: mda: no more envelope for ":gilles"
> debug: mda: got message fd 4 for session 4af9e1d4e7c887ea evpid 
> 1540150aac11ccde
> debug: mda: querying mda fd for session 4af9e1d4e7c887ea evpid 
> 1540150aac11ccde
> debug: smtpd: forking mda for session 4af9e1d4e7c887ea: 
> "/home/gilles/Maildir" as gilles
> debug: mda: got mda fd 5 for session 4af9e1d4e7c887ea evpid 1540150aac11ccde
> debug: mda: end-of-file for session 4af9e1d4e7c887ea evpid 1540150aac11ccde
> debug: mda: all data sent for session 4af9e1d4e7c887ea evpid 1540150aac11ccde
> debug: smtpd: mda process done for session 4af9e1d4e7c887ea: exited okay
> delivery: Ok for 1540150aac11ccde: from=, 
> to=, user=gilles, method=maildir, delay=0s, 
> stat=Delivered
> debug: mda: session 4af9e1d4e7c887ea done
> debug: mda: user "gilles" becomes runnable
> debug: mda: all done for user ":gilles"
>
>
>>
>> When I had four files in offline, then there were 4 "New session"
>> lines before the 'warn' messages start.
>>
>> All on -current as of yesterday, including mutt.
>>
>
> I have no idea right now what could cause that but I'm looking into it
> and hopefully I can find a way to crash this afternoon.
>
>
> --
> Gilles Chehade
>
> https://www.poolp.org  @poolpOrg

Re: smtpd stops immediately after starting in -current

[Kenneth Westerback]

On 18 May 2014 05:37, Gilles Chehade  wrote:
> On Sat, May 17, 2014 at 10:40:13PM -0400, Allan Streib wrote:
>> On Sat, May 17, 2014, at 05:30 PM, Allan Streib wrote:
>>
>> > Just upgraded to -current from my local mirror. Was previously working
>> > with a recent-ish -current (late April or early May)
>>
>> By "current" I meant "snapshot" sorry if that caused any confusion.
>>
>
> I'll have a look at this, thanks
>
> --
> Gilles Chehade
>
> https://www.poolp.org  @poolpOrg
>

I've found that if there is anything processed from the offline queue
then smtpd stops immediately. If I remove all offline files then smtpd
starts up fine but as soon as I send an email (using mutt) it exits.

Running '/usr/sbin/smtpd -v -d' and then using mutt I see

$ sudo /usr/sbin/smtpd -v -d
debug: init ssl-tree
info: OpenSMTPD 5.4.3 starting
debug: bounce warning after 4h
debug: using "fs" queue backend
debug: using "ramqueue" scheduler backend
debug: using "ram" stat backend
info: startup [debug mode]
debug: init ssl-tree
debug: ca_engine_init: using RSAX engine support
debug: queue: done loading queue into scheduler
debug: parent_send_config_ruleset: reloading
debug: parent_send_config: configuring pony process
debug: parent_send_config: configuring ca process
debug: smtp: listen on 127.0.0.1 port 25 flags 0x0 pki ""
debug: init private ssl-tree
debug: smtp: listen on IPv6:fe80::1%lo0 port 25 flags 0x0 pki ""
debug: smtp: listen on IPv6:::1 port 25 flags 0x0 pki ""
debug: smtp: will accept at most 501 clients
debug: smtpd: scanning offline queue...
debug: smtpd: offline scanning done
debug: smtp: new client on listener: 0x8a03e068120
smtp-in: New session 7d58bb784abfedee from host 1000@localhost [local]
warn: ca -> pony: pipe closed
warn: control -> pony: pipe closed
warn: lka -> pony: pipe closed
warn: queue -> pony: pipe closed
warn: parent -> pony: pipe closed
warn: scheduler -> control: pipe closed
$

When I had four files in offline, then there were 4 "New session"
lines before the 'warn' messages start.

All on -current as of yesterday, including mutt.

 Ken

Re: firefox-26.0p1.tgz signature verification FAIL

[Kenneth Westerback]

On 14 May 2014 11:26, Stuart Henderson  wrote:
> On 2014/05/14 11:21, Ted Unangst wrote:
>> On Wed, May 14, 2014 at 12:44, Stuart Henderson wrote:
>> >>> $ \time -l signify -C -p /etc/signify/openbsd-55-pkg.pub -x SHA256.sig
>> > moo-1.3p1.tgz
>> >>> Signature Verified
>> >>> moo-1.3p1.tgz: FAIL
>> >>>65.83 real31.48 user34.32 sys
>> >
>> > This was due to malloc flags 'S' or more specifically the 'G' (guard
>> > pages) component of this. (yes, from 0.06s to 65.83s).
>>
>> There is a preposterously inefficient realloc loop used to parse
>> SHA256 files. As long as it's only checking the base checksums, it's
>> ok. Really, the feature was only added to make checking bsd.rd easier
>> when upgrading.
>>
>> It won't be hard to fix, but as also noted, the ports SHA256 format
>> isn't acceptable either. Now I have two problems...
>
> As so often, /bin/rm may well be the answer :-)
>

If only /bin wasn't full we could add a link /bin/tedu -> /bin/rm.

 Ken

Re: Unable to set the server to download the sets with autoinstall

[Kenneth Westerback]

On 8 May 2014 05:33, Xavier Claude  wrote:
> Hello,
>
> I'm trying to use autoinstall with OpenBSD 5.5 but the Server line in
> the configuration file is not read set according to the install.conf
> and instead is used for the ntp server.
>
> Here is my install.conf file:
> System hostname = testbsd
> Password for root = $2a$06$8APgDGjoEAAq85b3S.QZzer...dmiwcummDpa
> Start sshd(8) by default = yes
> Start ntpd(8) by default = yes
> Do you expect to run the X Window System = no
> Change the default console to com0 = no
> Which speed should com0 use = 19200
> Setup a user = conostix
> Password for user = $2a$06$6IqO/zjUnFgrsI76g2/be.../YWDIA3T/mGdO
> What timezone are you in = Europe/Luxembourg
> Location of sets = http
> Server = 192.168.42.1
> Server directory = plop
>
> And in the ai.log file, I have:
>>
>> NTP server? (hostname or 'default') [default] 192.168.42.1
>
>
> And at the end of the log:
>>
>> Let's install the sets!
>> HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none] none
>> (Was not able to get ftplist from ftp.openbsd.org, but that is OK)
>> Server? (hostname or 'done')
>> Question has no answer in response file.
>
>
> The install.conf retrieved by the installer is the same as the one on
> the web server (checked with the installer shell).
>
> Thank you for your help.
> --
> Xavier Claude
> cont...@xavierclaude.be
>

Since the 'NTP Server' question contains 'Server', it will match the
install.conf question, and since the NTP question comes first ...

I think you will have to put a 'NTP Server = default' line in the
install.conf, so it can be consumed before the 'Server' line is called
for.

Perhaps we should change 'Server?' to 'HTTP Server?' now that ftp is
no longer an install method, thus allowing unambiguous selection.

 Ken

Re: Weird disklabel problem

[Kenneth Westerback]

On 4 May 2014 14:47, Andreas Bartelt  wrote:
> On 05/03/14 20:22, Kenneth Westerback wrote:
>>
>> On 3 May 2014 10:13, Andreas Bartelt  wrote:
>>>
>>> On 05/03/14 15:01, Kenneth Westerback wrote:
>>>>
>>>>
>>>> On 3 May 2014 08:49, Andreas Bartelt  wrote:
>>>>>
>>>>>
>>>>> On 05/03/14 14:10, Kenneth Westerback wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 3 May 2014 06:27, Martijn Rijkeboer  wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> So marking a partition as 'Active/Bootable', (the 00 -> 80 change)
>>>>>>>> causes your system to hang. Apparently Linux does this when you
>>>>>>>> 'Label' it. The OpenBSD installer does it for you when you
>>>>>>>> select 'Whole disk'. Nothing obviously to do with the disklabel. You
>>>>>>>> could test this by manually
>>>>>>>> setting the 'Active' flag on the working Linux MBR. Or, conversely
>>>>>>>> unsetting the flag with fdisk
>>>>>>>> after the OpenBSD install but before rebooting. In either case does
>>>>>>>> it
>>>>>>>> get further before noticing that it can't boot?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I did some testing with the following results:
>>>>>>>
>>>>>>> 1. Partition disk with Linux gparted and use cfdisk to set partition
>>>>>>> type to A6 and OpenBSD disklabel to set disklabel.
>>>>>>> (partition: 0; start: 2048; size: 1953519616)
>>>>>>> - Bootflag off, no disklabel   -> boot
>>>>>>> - Bootflag on,  no disklabel   -> boot
>>>>>>> - Bootflag off, with disklabel -> freeze
>>>>>>> - Bootflag on,  with disklabel -> freeze
>>>>>>>
>>>>>>> 2. Partition disk with OpenBSD fdisk + disklabel (installer start +
>>>>>>> size).
>>>>>>> (partition: 3, start: 64; size: 1953520001)
>>>>>>> - Bootflag off, no disklabel   -> freeze
>>>>>>> - Bootflag on,  no disklabel   -> freeze
>>>>>>> - Bootflag off, with disklabel -> freeze
>>>>>>> - Bootflag on,  with diskalbel -> freeze
>>>>>>>
>>>>>>> 3. Partition disk with OpenBSD fdisk + disklabel (linux start +
>>>>>>> size).
>>>>>>> (partition: 3: start: 2048; size: 1953519616)
>>>>>>> - Bootflag off, no disklabel   -> boot
>>>>>>> - Bootflag on,  no disklabel   -> boot
>>>>>>> - Bootflag off, with disklabel -> freeze
>>>>>>> - Bootflag on,  with disklabel -> freeze
>>>>>>>
>>>>>>> 4. Partition disk with OpenBSD fdisk with type 83 (installer start +
>>>>>>> size).
>>>>>>> (partition: 3, start: 64; size: 1953520001)
>>>>>>> - Bootflag off -> freeze
>>>>>>> - Bootflag on  -> freeze
>>>>>>>
>>>>>>> It looks like the motherboard doesn't like the partition to start at
>>>>>>> 64
>>>>>>> and
>>>>>>> it also doesn't like disklabels.
>>>>>>>
>>>>>>> Any suggestions on what to try next or should I just buy a different
>>>>>>> motherboard?
>>>>>>>
>>>>>>> Kind regards,
>>>>>>>
>>>>>>>
>>>>>>> Martijn Rijkeboer
>>>>>>>
>>>>>>
>>>>>> Looking around I found that one of my machines has a gigabyte
>>>>>> GA-Z87-D3HP board, and I scrounged up a 1TB WD 10EARS disk. The disk
>>>>>> was from another machine and had a working OpenBSD system. Lo and
>>>>>> behold, plugged it into the GA-Z87-D3HP board and the system hung in
>>>>>> the POST. Put the disk back on the other system, dd'ed /dev/zero over
>>>>>> the disklabel, moved it back and the system booted.
>>>>>>
>>>>

Re: Weird disklabel problem

[Kenneth Westerback]

On 3 May 2014 10:13, Andreas Bartelt  wrote:
> On 05/03/14 15:01, Kenneth Westerback wrote:
>>
>> On 3 May 2014 08:49, Andreas Bartelt  wrote:
>>>
>>> On 05/03/14 14:10, Kenneth Westerback wrote:
>>>>
>>>>
>>>> On 3 May 2014 06:27, Martijn Rijkeboer  wrote:
>>>>>>
>>>>>>
>>>>>> So marking a partition as 'Active/Bootable', (the 00 -> 80 change)
>>>>>> causes your system to hang. Apparently Linux does this when you
>>>>>> 'Label' it. The OpenBSD installer does it for you when you
>>>>>> select 'Whole disk'. Nothing obviously to do with the disklabel. You
>>>>>> could test this by manually
>>>>>> setting the 'Active' flag on the working Linux MBR. Or, conversely
>>>>>> unsetting the flag with fdisk
>>>>>> after the OpenBSD install but before rebooting. In either case does it
>>>>>> get further before noticing that it can't boot?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I did some testing with the following results:
>>>>>
>>>>> 1. Partition disk with Linux gparted and use cfdisk to set partition
>>>>> type to A6 and OpenBSD disklabel to set disklabel.
>>>>> (partition: 0; start: 2048; size: 1953519616)
>>>>> - Bootflag off, no disklabel   -> boot
>>>>> - Bootflag on,  no disklabel   -> boot
>>>>> - Bootflag off, with disklabel -> freeze
>>>>> - Bootflag on,  with disklabel -> freeze
>>>>>
>>>>> 2. Partition disk with OpenBSD fdisk + disklabel (installer start +
>>>>> size).
>>>>> (partition: 3, start: 64; size: 1953520001)
>>>>> - Bootflag off, no disklabel   -> freeze
>>>>> - Bootflag on,  no disklabel   -> freeze
>>>>> - Bootflag off, with disklabel -> freeze
>>>>> - Bootflag on,  with diskalbel -> freeze
>>>>>
>>>>> 3. Partition disk with OpenBSD fdisk + disklabel (linux start + size).
>>>>> (partition: 3: start: 2048; size: 1953519616)
>>>>> - Bootflag off, no disklabel   -> boot
>>>>> - Bootflag on,  no disklabel   -> boot
>>>>> - Bootflag off, with disklabel -> freeze
>>>>> - Bootflag on,  with disklabel -> freeze
>>>>>
>>>>> 4. Partition disk with OpenBSD fdisk with type 83 (installer start +
>>>>> size).
>>>>> (partition: 3, start: 64; size: 1953520001)
>>>>> - Bootflag off -> freeze
>>>>> - Bootflag on  -> freeze
>>>>>
>>>>> It looks like the motherboard doesn't like the partition to start at 64
>>>>> and
>>>>> it also doesn't like disklabels.
>>>>>
>>>>> Any suggestions on what to try next or should I just buy a different
>>>>> motherboard?
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>
>>>>> Martijn Rijkeboer
>>>>>
>>>>
>>>> Looking around I found that one of my machines has a gigabyte
>>>> GA-Z87-D3HP board, and I scrounged up a 1TB WD 10EARS disk. The disk
>>>> was from another machine and had a working OpenBSD system. Lo and
>>>> behold, plugged it into the GA-Z87-D3HP board and the system hung in
>>>> the POST. Put the disk back on the other system, dd'ed /dev/zero over
>>>> the disklabel, moved it back and the system booted.
>>>>
>>>> How extremely interesting. And weird.
>>>>
>>>>  Ken
>>>>
>>>>
>>>
>>> such problems also seem to occur on some ASUS boards -- but only when
>>> SATA
>>> drives are used. OpenBSD did boot fine from a USB stick:
>>> http://marc.info/?l=openbsd-misc&m=137862502730004&w=2
>>>
>>> Best Regards
>>> Andreas
>>
>>
>> Indeed. Experiments here show that plugging in a pci <-> sata card to
>> avoid the Intel SATA chip makes the disk work fine.
>>
>> Disks smaller than 1TB also work. So I'm guessing it's something
>> magical about 4K-sector disks presenting themselves as 512-byte sector
>> disks that is the source of problems. I'm still a bit fogged as to how
>> a disklabel triggers the problem.
>>
>
> I also saw these problems with a Chronos MKNSSDCR120GB SSD drive. I don't
> know which sector size these drives use internally...
>
> Actually, I didn't get any of my drives to work with OpenBSD on this
> mainboard. I don't know if it helps -- I've also unsuccessfully tested a
> 320GB WD3200AAKS from 08/2010.
>
> Best Regards
> Andreas

OK, I got it booting. In a fairly useless config, but ...

Booting from a -current amd64 cd55.iso cd-rom, I (E)dited the MBR so
that the OpenBSD 'A6' partition started on sector 2048, and was 500MB
in size.

I accepted the auto configured disklabel (i.e. all space in 'a') and
installed w/o X, Compiler or games sets.

Removing the CD and rebooting got me to the usual login prompt.

I'm going to experiment some more, but I'm now suspicious that the old
'512MB' limit is coming into play somehow.

So for those following along, try a tiny OpenBSD MBR partition
starting at sector 2048 and see what happens. And of course if it
works, how big can your partition be before it stops working.

 Ken

Re: Weird disklabel problem

[Kenneth Westerback]

On 3 May 2014 08:49, Andreas Bartelt  wrote:
> On 05/03/14 14:10, Kenneth Westerback wrote:
>>
>> On 3 May 2014 06:27, Martijn Rijkeboer  wrote:
>>>>
>>>> So marking a partition as 'Active/Bootable', (the 00 -> 80 change)
>>>> causes your system to hang. Apparently Linux does this when you
>>>> 'Label' it. The OpenBSD installer does it for you when you
>>>> select 'Whole disk'. Nothing obviously to do with the disklabel. You
>>>> could test this by manually
>>>> setting the 'Active' flag on the working Linux MBR. Or, conversely
>>>> unsetting the flag with fdisk
>>>> after the OpenBSD install but before rebooting. In either case does it
>>>> get further before noticing that it can't boot?
>>>
>>>
>>>
>>> I did some testing with the following results:
>>>
>>> 1. Partition disk with Linux gparted and use cfdisk to set partition
>>> type to A6 and OpenBSD disklabel to set disklabel.
>>> (partition: 0; start: 2048; size: 1953519616)
>>> - Bootflag off, no disklabel   -> boot
>>> - Bootflag on,  no disklabel   -> boot
>>> - Bootflag off, with disklabel -> freeze
>>> - Bootflag on,  with disklabel -> freeze
>>>
>>> 2. Partition disk with OpenBSD fdisk + disklabel (installer start +
>>> size).
>>> (partition: 3, start: 64; size: 1953520001)
>>> - Bootflag off, no disklabel   -> freeze
>>> - Bootflag on,  no disklabel   -> freeze
>>> - Bootflag off, with disklabel -> freeze
>>> - Bootflag on,  with diskalbel -> freeze
>>>
>>> 3. Partition disk with OpenBSD fdisk + disklabel (linux start + size).
>>> (partition: 3: start: 2048; size: 1953519616)
>>> - Bootflag off, no disklabel   -> boot
>>> - Bootflag on,  no disklabel   -> boot
>>> - Bootflag off, with disklabel -> freeze
>>> - Bootflag on,  with disklabel -> freeze
>>>
>>> 4. Partition disk with OpenBSD fdisk with type 83 (installer start +
>>> size).
>>> (partition: 3, start: 64; size: 1953520001)
>>> - Bootflag off -> freeze
>>> - Bootflag on  -> freeze
>>>
>>> It looks like the motherboard doesn't like the partition to start at 64
>>> and
>>> it also doesn't like disklabels.
>>>
>>> Any suggestions on what to try next or should I just buy a different
>>> motherboard?
>>>
>>> Kind regards,
>>>
>>>
>>> Martijn Rijkeboer
>>>
>>
>> Looking around I found that one of my machines has a gigabyte
>> GA-Z87-D3HP board, and I scrounged up a 1TB WD 10EARS disk. The disk
>> was from another machine and had a working OpenBSD system. Lo and
>> behold, plugged it into the GA-Z87-D3HP board and the system hung in
>> the POST. Put the disk back on the other system, dd'ed /dev/zero over
>> the disklabel, moved it back and the system booted.
>>
>> How extremely interesting. And weird.
>>
>>  Ken
>>
>>
>
> such problems also seem to occur on some ASUS boards -- but only when SATA
> drives are used. OpenBSD did boot fine from a USB stick:
> http://marc.info/?l=openbsd-misc&m=137862502730004&w=2
>
> Best Regards
> Andreas

Indeed. Experiments here show that plugging in a pci <-> sata card to
avoid the Intel SATA chip makes the disk work fine.

Disks smaller than 1TB also work. So I'm guessing it's something
magical about 4K-sector disks presenting themselves as 512-byte sector
disks that is the source of problems. I'm still a bit fogged as to how
a disklabel triggers the problem.

 Ken

Re: Weird disklabel problem

[Kenneth Westerback]

On 3 May 2014 06:27, Martijn Rijkeboer  wrote:
>> So marking a partition as 'Active/Bootable', (the 00 -> 80 change)
>> causes your system to hang. Apparently Linux does this when you
>> 'Label' it. The OpenBSD installer does it for you when you
>> select 'Whole disk'. Nothing obviously to do with the disklabel. You
>> could test this by manually
>> setting the 'Active' flag on the working Linux MBR. Or, conversely
>> unsetting the flag with fdisk
>> after the OpenBSD install but before rebooting. In either case does it
>> get further before noticing that it can't boot?
>
>
> I did some testing with the following results:
>
> 1. Partition disk with Linux gparted and use cfdisk to set partition
> type to A6 and OpenBSD disklabel to set disklabel.
> (partition: 0; start: 2048; size: 1953519616)
> - Bootflag off, no disklabel   -> boot
> - Bootflag on,  no disklabel   -> boot
> - Bootflag off, with disklabel -> freeze
> - Bootflag on,  with disklabel -> freeze
>
> 2. Partition disk with OpenBSD fdisk + disklabel (installer start + size).
> (partition: 3, start: 64; size: 1953520001)
> - Bootflag off, no disklabel   -> freeze
> - Bootflag on,  no disklabel   -> freeze
> - Bootflag off, with disklabel -> freeze
> - Bootflag on,  with diskalbel -> freeze
>
> 3. Partition disk with OpenBSD fdisk + disklabel (linux start + size).
> (partition: 3: start: 2048; size: 1953519616)
> - Bootflag off, no disklabel   -> boot
> - Bootflag on,  no disklabel   -> boot
> - Bootflag off, with disklabel -> freeze
> - Bootflag on,  with disklabel -> freeze
>
> 4. Partition disk with OpenBSD fdisk with type 83 (installer start + size).
> (partition: 3, start: 64; size: 1953520001)
> - Bootflag off -> freeze
> - Bootflag on  -> freeze
>
> It looks like the motherboard doesn't like the partition to start at 64 and
> it also doesn't like disklabels.
>
> Any suggestions on what to try next or should I just buy a different
> motherboard?
>
> Kind regards,
>
>
> Martijn Rijkeboer
>

Looking around I found that one of my machines has a gigabyte
GA-Z87-D3HP board, and I scrounged up a 1TB WD 10EARS disk. The disk
was from another machine and had a working OpenBSD system. Lo and
behold, plugged it into the GA-Z87-D3HP board and the system hung in
the POST. Put the disk back on the other system, dd'ed /dev/zero over
the disklabel, moved it back and the system booted.

How extremely interesting. And weird.

 Ken

Re: Weird disklabel problem

[Kenneth Westerback]

On 1 May 2014 14:59, Martijn Rijkeboer  wrote:
>> Can you provide a hex dump of the MBR Linux produces? The evidence would
>> seem to point at the boot code stored in the MBR. To which I made a
>> recent minor tweak. So you might also try a 5.4 install to see if it
>> works.
>
> Below are the hexdumps of the MBR. The "before" was created with Linux and
> before labeling. The "after" was created with Linux and after labeling. The
> "obsd-55" was created with the OpenBSD 5.5 installer with the "whole" disk
> option. The "obsd-54" was created with the OpenBSD 5.4 installer with the
> "whole" disk option.
>
> The "before" and "after" differ only on line "1b0". The "obsd-55" and
> "obsd-54" are identical. The problem occurs with all except "before".
>

So marking a partition as 'Active/Bootable', (the 00 -> 80 change)
causes your system to hang. Apparently Linux does this when you
'Label' it. The OpenBSD installer does it for you when you
select 'Whole disk'. Nothing obviously to do with the disklabel. You
could test this by manually
setting the 'Active' flag on the working Linux MBR. Or, conversely
unsetting the flag with fdisk
after the OpenBSD install but before rebooting. In either case does it
get further before
noticing that it can't boot?

 Ken

> Kind regards,
>
>
> Martijn Rijkeboer
>
>
>
> before
> ==
> 000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
> 010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
> 020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
> 030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
> 040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
> 050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
> 060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
> 070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
> 080 c726 fe06 0001 f600 b406 0101 3175 1488
> 090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
> 0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
> 0b0 0e89 0112 b456 be42 010a 13cd 735e b019
> 0c0 e83b 003a 748a 8b01 024c 01b8 3102 cddb
> 0d0 7313 be05 0152 81eb 7dbe e801 0014 8126
> 0e0 fe3e 5501 75aa ea05 7c00  61be e901
> 0f0 ff67 fc50 84ac 74c0 e80f 0002 f6eb 5350
> 100 0eb4 01bb cd00 5b10 c358 0010 0001 
> 110 07c0     5521 6973 676e
> 120 6420 6972 6576 5820 202c 6170 7472 7469
> 130 6f69 206e 0059 424d 2052 6e6f 6620 6f6c
> 140 7070 2079 726f 6f20 646c 4220 4f49 0d53
> 150 000a 0a0d 6552 6461 6520 7272 726f 0a0d
> 160 4e00 206f 2f4f 0d53 000a 6f4e 6120 7463
> 170 7669 2065 6170 7472 7469 6f69 0d6e 000a
> 180 0090       
> 190        
> *
> 1b0    784f b8e7 0009  2000
> 1c0 0021 fea6  0800  5800 7470 
> 1d0        
> *
> 1f0        aa55
> 200
>
>
> after
> =
> 000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
> 010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
> 020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
> 030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
> 040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
> 050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
> 060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
> 070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
> 080 c726 fe06 0001 f600 b406 0101 3175 1488
> 090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
> 0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
> 0b0 0e89 0112 b456 be42 010a 13cd 735e b019
> 0c0 e83b 003a 748a 8b01 024c 01b8 3102 cddb
> 0d0 7313 be05 0152 81eb 7dbe e801 0014 8126
> 0e0 fe3e 5501 75aa ea05 7c00  61be e901
> 0f0 ff67 fc50 84ac 74c0 e80f 0002 f6eb 5350
> 100 0eb4 01bb cd00 5b10 c358 0010 0001 
> 110 07c0     5521 6973 676e
> 120 6420 6972 6576 5820 202c 6170 7472 7469
> 130 6f69 206e 0059 424d 2052 6e6f 6620 6f6c
> 140 7070 2079 726f 6f20 646c 4220 4f49 0d53
> 150 000a 0a0d 6552 6461 6520 7272 726f 0a0d
> 160 4e00 206f 2f4f 0d53 000a 6f4e 6120 7463
> 170 7669 2065 6170 7472 7469 6f69 0d6e 000a
> 180 0090       
> 190        
> *
> 1b0    784f b8e7 0009  2080
> 1c0 0021 fea6  0800  5800 7470 
> 1d0        
> *
> 1f0        aa55
> 200
>
>
> obsd-55
> ===
> 000 05ea c000 8c07 8ec8 bcd0 fffc d88e a0b8
> 010 8e07 31c0 31f6 b9ff 0200 f3fc eaa4 0022
> 020 07a0 071e 1f0e 02b4 16cd 03a8 0a74 07b0
> 030 cbe8 8000 b40e 0101 c2f6 7580 be08 0136
> 040 afe8 b200 be80 01be 04b9 8a00 3c04 7480
> 050 830f 10c6 f5e2 6abe e801 0096 f4fb fceb
> 060 d088 0f24 3004 27a2 b001 2834 a2c8 0134
> 070 be56 011a 06f6 01b4 7501 4601 73e8 5e00
> 080 c726 fe06 0001 f600 b406 0101 3175 1488
> 090 aabb b455 cd41 8a13 7214 8124 55fb 75aa
> 0a0 f61e 01c1 1974 2eb0 53e8 6600 4c8b 6608
> 0b0 0e89 0112 b456 be42

Re: Weird disklabel problem

[Kenneth Westerback]

On 30 Apr 2014 03:28, "Martijn Rijkeboer"  wrote:
>
> Hello,
>
> I've got a weird disklabel related problem (or so it seems). When I
> partition my harddisk with fdisk and add an OpenBSD (A6) primary
> partition the system can still boot, but once I place a disklabel
> on the partition (disklabel -E sd0) I can't boot the system anymore
> (it freezes during the post).
>
> System Info:
> - OS: OpenBSD-current AMD64
> - CPU: Intel Core i3 4130T
> - Motherboard: Gigabyte GA-B85M-DS3H
> - Harddisk: WD Green 1TB (SATA)
>
> It is possible that it's a Gigabyte specific problem since Karl
> Karlsson has the same problem with his Gigabyte GA-Z87MX-DH3
> motherboard.
>
> The other strange thing is that if I use an USB-stick instead
> of the harddisk I can install and boot OpenBSD without problems.
> Even with the harddisk present, but without a disklabel, I can
> still boot from the USB stick, but as soon as I place a disklabel
> on the harddisk (although it isn't used, nor in the boot sequence)
> the system freezes during the post again.
>
> Any suggestions on how to fix this or should I just buy a different
> motherboard?
>
> Kind regards,
>
>
> Martijn Rijkeboer
>

Can you provide a hex dump of the MBR Linux produces? The evidence would
seem to point at the boot code stored in the MBR. To which I made a recent
minor tweak. So you might also try a 5.4 install to see if it works.

 Ken

Re: Weird disklabel problem

[Kenneth Westerback]

On 30 Apr 2014 15:57, "Kenneth Westerback"  wrote:
>
>
> On 30 Apr 2014 15:39, "Martijn Rijkeboer"  wrote:
> >
> > > Please post at least a dmesg with the disk attached but no disklabel
> > > plus fdisk and disklabel output after setting the label but before the
> > > (failing) reboot.
> >
> > Below you will find the dmesg and output from fdisk and disklabel before
> > and after labeling. I used Linux to partition the harddisk, because if I
> > use the "Whole" option from the OpenBSD installer in can't boot...
> >
> > Kind regards,
> >
> >
> > Martijn Rijkeboer
> >
> > dmesg
> > =
> >
> > OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014
> > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > real mem = 8443088896 (8051MB)
> > avail mem = 8209612800 (7829MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries)
> > bios0: vendor American Megatrends Inc. version "F2" date 01/18/2014
> > bios0: Gigabyte Technology Co., Ltd. B85M-DS3H
> > acpi0 at bios0: rev 2
> > acpi0: sleep states S0 S3 S4 S5
> > acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR
> > acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4)
RP06(S4) PXSX(S4) RP07(S4) [...]
> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.72 MHz
> > cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A
ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
> > cpu0: 256KB 64b/line 8-way L2 cache
> > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 99MHz
> > cpu0: mwait min=25345, max=46847 (bogus)
> > cpu1 at mainbus0: apid 2 (application processor)
> > cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 MHz
> > cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A
ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
> > cpu1: 256KB 64b/line 8-way L2 cache
> > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> > acpihpet0 at acpi0: 14318179 Hz
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus 1 (RP01)
> > acpiprt2 at acpi0: bus 2 (RP03)
> > acpiprt3 at acpi0: bus -1 (P0P2)
> > acpiprt4 at acpi0: bus -1 (P0PA)
> > acpiprt5 at acpi0: bus -1 (P0PB)
> > acpiprt6 at acpi0: bus -1 (PEG0)
> > acpiprt7 at acpi0: bus -1 (PEG1)
> > acpiprt8 at acpi0: bus -1 (PEG2)
> > acpiec0 at acpi0: Failed to read resource settings
> > acpicpu0 at acpi0: C2, C1, PSS
> > acpicpu1 at acpi0: C2, C1, PSS
> > acpipwrres0 at acpi0: FN00, resource for FAN0
> > acpipwrres1 at acpi0: FN01, resource for FAN1
> > acpipwrres2 at acpi0: FN02, resource for FAN2
> > acpipwrres3 at acpi0: FN03, resource for FAN3
> > acpipwrres4 at acpi0: FN04, resource for FAN4
> > acpitz0 at acpi0: critical temperature is 90 degC
> > acpitz1 at acpi0: critical temperature is 90 degC
> > acpibat0 at acpi0: BAT0 not present
> > acpibat1 at acpi0: BAT1 not present
> > acpibat2 at acpi0: BAT2 not present
> > acpibtn0 at acpi0: PWRB
> > acpibtn1 at acpi0: LID0
> > acpivideo0 at acpi0: GFX0
> > acpivout0 at acpivideo0: DD1F
> > cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500,
2300, 2200, 2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz
> > pci0 at mainbus0 bus 0
> > pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
> > vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06
> > intagp0 at vga1
> > agp0 at intagp0: aperture at 0xe000, size 0x1000
> > inteldrm0 at vga1
> > drm0 at inteldrm0
> > error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register
before writing to 10
> > inteldrm0: 1920x1200
> > wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
> > wsdisplay0: screen 1-5 added (std, vt100 emulation)
> 

Re: Weird disklabel problem

[Kenneth Westerback]

On 30 Apr 2014 15:39, "Martijn Rijkeboer"  wrote:
>
> > Please post at least a dmesg with the disk attached but no disklabel
> > plus fdisk and disklabel output after setting the label but before the
> > (failing) reboot.
>
> Below you will find the dmesg and output from fdisk and disklabel before
> and after labeling. I used Linux to partition the harddisk, because if I
> use the "Whole" option from the OpenBSD installer in can't boot...
>
> Kind regards,
>
>
> Martijn Rijkeboer
>
> dmesg
> =
>
> OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014
> t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8443088896 (8051MB)
> avail mem = 8209612800 (7829MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries)
> bios0: vendor American Megatrends Inc. version "F2" date 01/18/2014
> bios0: Gigabyte Technology Co., Ltd. B85M-DS3H
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR
> acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4)
RP06(S4) PXSX(S4) RP07(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.72 MHz
> cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A
ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
> cpu0: 256KB 64b/line 8-way L2 cache
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=25345, max=46847 (bogus)
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 MHz
> cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A
ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC
> cpu1: 256KB 64b/line 8-way L2 cache
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (RP01)
> acpiprt2 at acpi0: bus 2 (RP03)
> acpiprt3 at acpi0: bus -1 (P0P2)
> acpiprt4 at acpi0: bus -1 (P0PA)
> acpiprt5 at acpi0: bus -1 (P0PB)
> acpiprt6 at acpi0: bus -1 (PEG0)
> acpiprt7 at acpi0: bus -1 (PEG1)
> acpiprt8 at acpi0: bus -1 (PEG2)
> acpiec0 at acpi0: Failed to read resource settings
> acpicpu0 at acpi0: C2, C1, PSS
> acpicpu1 at acpi0: C2, C1, PSS
> acpipwrres0 at acpi0: FN00, resource for FAN0
> acpipwrres1 at acpi0: FN01, resource for FAN1
> acpipwrres2 at acpi0: FN02, resource for FAN2
> acpipwrres3 at acpi0: FN03, resource for FAN3
> acpipwrres4 at acpi0: FN04, resource for FAN4
> acpitz0 at acpi0: critical temperature is 90 degC
> acpitz1 at acpi0: critical temperature is 90 degC
> acpibat0 at acpi0: BAT0 not present
> acpibat1 at acpi0: BAT1 not present
> acpibat2 at acpi0: BAT2 not present
> acpibtn0 at acpi0: PWRB
> acpibtn1 at acpi0: LID0
> acpivideo0 at acpi0: GFX0
> acpivout0 at acpivideo0: DD1F
> cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500, 2300,
2200, 2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06
> intagp0 at vga1
> agp0 at intagp0: aperture at 0xe000, size 0x1000
> inteldrm0 at vga1
> drm0 at inteldrm0
> error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
writing to 10
> inteldrm0: 1920x1200
> wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
> wsdisplay0: screen 1-5 added (std, vt100 emulation)
> azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi
> azalia0: No codecs found
> "Intel 8 Series xHCI" rev 0x05 at pci0 dev 20 function 0 not configured
> "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
> puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 1 com
> com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo
> com4: probed fifo depth: 0 bytes
> ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int
16
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x05: msi
> azalia1: codecs: Realtek/0x0887
> audio0 at azalia1
> ppb0 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi
> pci1 at ppb0 bus 1
> ppb1 at pci0 dev 

Re: A misconfigured disklabel can crash the kernel on listing its mounted directory contents (5.4)

[Kenneth Westerback]

I'm pretty sure that Linux does not manufacture disklabels that are
compatible with OpenBSD. And visa versa! And if you're
creating/mounting filesystems you are *not* an unprivileged user and
you *definitely* can crash systems if you're not careful. :-)

That said, if you can provide details on the crash this particular one
may be avoidable.

 Ken


On 26 April 2014 11:41, Z  wrote:
> Hi, I've never used mailing lists so please correct mistakes and forgive
> me if this is not a bug, but as I understand it you should not be able
> to crash the kernel as an unpriviledged user.
>
> In brief, I was trying to format a usb stick as ext2, and was going back
> and forth between linux and openbsd to get it working on both (I'm
> fairly new to openbsd). The disklabel I ended up with is pasted below.
> It seems misconfigured, but is the result of using (on arch linux)
> cfdisk to delete all partitions and create a new one, and then mkfs.ext2
> to create the filesystem. Previously I had created a working ext2
> partition on openbsd, but linux could not read it.
>
> I can mount this disk fine, but when I go to list the mount directory
> with ls -l, the whole computer crashes. I've verified this is true many
> times both at the console and also when ssh'd into the pc. It just
> freezes and accepts no input. The ssh connection hangs. Nothing except a
> physical poweroff does anything.
>
> I should point out that the usb stick can be read and written to
> normally on linux, so it doesn't seem to be a physical hardware problem.
> I should also say that the method I'm using to mount the stick as a non
> priviledged user seems a little fishy - namely chmodding 660 /dev/sd1*
> and making my user a member of the operators group. Or perhaps this is
> the normal way on OpenBSD, I don't know.
>
> I'm using 5.4 on an IBM Thinkpad T60. I'm happy to post a full
> dmesg/usbdevs/pcidump etc if it helps, but thought it might be too much
> for a first post.
>
>> disklabel sd1
> # /dev/rsd1c:
> type: SCSI
> disk: SCSI disk
> label: Cruzer Blade
> duid: 704ebc363be23fd4
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 973
> total sectors: 15633408
> boundstart: 0
> boundend: 15633408
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   a: 156334080  ext2fs   # 
> /home/z/mounts/key
>   c: 156334080 ISO9660
>
>> disklabel -d sd1
> # /dev/rsd1c:
> type: SCSI
> disk: SCSI disk
> label: Cruzer Blade
> duid: 
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 973
> total sectors: 15633408
> boundstart: 0
> boundend: 15633408
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   c: 156334080  unused
>   i: 15633346   62  ext2fs
>
>
> PS - excuse the email username "z" - I haven't got around to properly
> configuring smtpd yet.

Re: How to apply a patch in OpenBSD?

[Kenneth Westerback]

On 16 April 2014 19:20, Liviu Daia  wrote:
> On 15 April 2014, ohh, whyyy  wrote:
>> Hey, Thanks! yes, it looks like the sys.tar.gz was missing.. I created a
>> small howto for it (for patching 5.4):
>> cd /root && ftp http://ftp.openbsd.org/pub/OpenBSD/`uname -r`/src.tar.gz &&
> [...]
>
> Nit pick: with automatically chosen partitions:
>
> # df -h /root
> Filesystem SizeUsed   Avail Capacity  Mounted on
> /dev/wd0a  129M110M   12.9M89%/
>
> Regards,
>
> Liviu Daia
>

What nit are you picking?

 Ken

Re: OpenBSD Foundation 2014 Fundraising Campaign.

[Kenneth Westerback]

On 11 April 2014 11:15, Jan Stary  wrote:
> On Apr 11 11:46:12, openbsd.as.a.desk...@gmail.com wrote:
>> Hi all,
>>
>> -
>> 1)
>> If I search for "openbsdfoundation" on:
>>
>> - Facebook
>> - Twitter
>> - Youtube
>> - Instagram
>> - Flickr
>> - Slideshare
>> - etc..
>>
>> I get ZERO results regarding the topic.
>
> If I search for "openbsdfoundation" on Google,
> I get the right thing as the first hit.
>
>> We are writing 2014.
>> The people are on "social sites"..
>> More could be reached if these mentioned sites would have marketing for the
>> foundation too.
>
> Ah, so there are people willing to donate to OpenBSD,
> but they don't even know about it, as it is only
> to be found on Google, right?
>
> That's bullshit. But if you really think so, go ahead:
> set yourself up on all those sites and make OpenBSD visible.
>
>> -
>> 2)
>> If I go to:
>> http://www.openbsdfoundation.org
>> I just can't see any page on the website that has logos, html codes (that
>> can be CTRL+C'ed simply), what can people put out on their blogs,
>
> You mean, such as "www.openbsdfoundation.org"?

I must be dense. I fire up lynx(1) with 'www.openbsdfoundation.org'
and once the page has loaded, I type CTRL+C. I get "Exiting via
interrupt: 2". Seems pretty simple already and does not appear to rely
on adding any pages. Of course it also seems kinda pointless.

 Ken

>
>
>> webpages
>> (openbsdfoundation logo/donate/etc. - a little picture that is an URL to
>> the foundations website - donations.html page), so that their visitors can
>> see that there is a good project waiting for foundations.
>
> Dear search engines (twitter etc), please spread this:
> http://www.openbsdfoundation.org/donations.html";> src="kitten.gif">a good project waiting for foundations
> (Now let's wait for the money pouring in.)

Re: OpenBSD on IBM Power

[Kenneth Westerback]

On 9 April 2014 12:24, Fil Di Noto  wrote:
> Is there any hope of OpenBSD running on IBM Power hardware (System P,
> LPAR) in the future?
>
> I've recently been working with this hardware and it's pretty amazing.
> I can't speak to its future market share but there seems to be a lot
> of propaganda from IBM regarding "Linux on Power" which suggests to me
> that IBM is trying to be more supportive of other operating systems
> besides AIX on their hardware.
>
> I've heard IBM contributes code to RHEL to make it work well on Power
> hardware. Would a project like OpenBSD have any hope of being a solid
> OS on that hardware without cooperation from IBM? I don't see any
> Linux distros that do not have a relationship with IBM that run on
> Power.
>

No developers interested that I know of. So it's not likely.

 Ken

Re: Only two holes in a heck of a long time, but why?

[Kenneth Westerback]

On 3 April 2014 22:04, Martin Braun  wrote:
> As we all know on the front page of OpenBSD it says "Only two remote holes
> in the default install, in a heck of a long time".
>
> I don't understand why this is "such a big deal".
>
> A part from the base system in xBSD, OpenBSD - so far - also contains a
> chrooted web server, that can't be used for much else than serving static
> content, and then the X system, which also can't be used for anything
> before installing some third party application.
>
> All in all the default install is pretty useless in itself and I am going
> to quote "Absolute OpenBSD" by Michael Lucas:
>
>   «You're installed OpenBSD and rebooted into a bare-bones system. Of
> course, a minimal Unix-like system is actually pretty boring. While it
> makes a powerful foundation, it doesn't actually do much of anything.»
>
> So we need those third party applications to start the party, yet none of
> these applications receives the same code audit, security development and
> quality control as OpenBSD does.
>
> As soon as we install a single third party application our entire operating
> system is, in theory at least, compromised as these third party
> applications gets installed as root.
>
> Maybe I am just plain stupid, but could someone explain to me the point in
> "bragging" about only two remote holes in the default install, when the
> default install is useless before you add some content to the system,
> unless you're running a web server serving static content only.

Firewalls? BGP Routers? Email servers? Relayd load balancers? All
base-only external facing devices that might be nice to not have
exploits in by default.

 Ken


>
> Best regards.
>
> Martin

Re: upgrades no longer allow ftp for sets

[Kenneth Westerback]

On 27 March 2014 11:30, Boris Goldberg  wrote:
> Hello misc,
>
> Thursday, March 27, 2014, 9:14:00 AM, Jiri wrote:
>
> JB> Could you please elaborate why not sftp for sets (and/or
> JB> for pkg_add)?
>
>   I'll rephrase: can someone besides Theo elaborate? It was an obvious
> mistake to reply to his email (to be fair, I've addressed it to misc, not
> to him).
>   In his "long email" Theo was talking about openssl. It's my understanding
> that openssh is going away from openssl, so I don't see a direct
> connection. I also see that psftp (from the putty) is about 300K, and I
> don't believe it has any important dependencies (kerberos could be ignored
> in this case).
>   BTW, what is limiting the bsd.rd size? It's not for a floppy. I've tried
> searching and found only a "rumor" that there is might be the size limit.
>
> --
> Best regards,
>  Borismailto:bo...@twopoint.com
>

1) It's not useful.
2) It's too complicated.
3) It's impossible to fit on the install media.

 Ken

Re: Seagate ST3250310AS not recognized

[Kenneth Westerback]

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

On 26 March 2014 16:59, Charlie Farinella
 wrote:
> I'm trying to install OpenBSD 5.4 on a Dell Vostro 400, it's several years 
> old but not ancient.  4GB RAM, 250GB Seagate ST3250310AS hard drive.  The 
> installation goes normally until it tries to find the hard drive and then 
> tells me no hard drive is available.
>
> I've wiped the drive (it had ESXi on it before), repartitioned it, 
> unpartitioned it, installed Linux, installed FreeBSD all without problem, but 
> no matter what I do to it, OpenBSD won't see it.
>
> I would really like to get this working so any suggestions or guidance is 
> very much appreciated.
>
> Thanks,
>
> --charlie
>
> --
> Charles Farinella
> Systems Administrator
> Appropriate Solutions, Inc.
> 603-924-6079

Re: upgrades no longer allow ftp for sets

[Kenneth Westerback]

On 26 March 2014 13:46, Ted Unangst  wrote:
> On Wed, Mar 26, 2014 at 10:41, Marc Espie wrote:
>> One other reason is that our ftp *client* is a pile of crud.
>>
>> Almost anyone who approaches it  runs away screaming (or becomes berserk,
>> grabs an axe, and starts cutting madly at the rest of the tree)
>
> I have seen no evidence of this ever happening.
>

The first thing and last thing axed is always the log. :-)

 Ken

Re: Suspend and Hibernate Issues with 3/5 Snapshot and ThinkPad T42p

[Kenneth Westerback]

5.2 to 5.5 is a big jump. Can you try 5.3 and/or 5.4 to narrow down
when the problem began? Bisecting the tree would be the next step. :-)

 Ken

On 20 March 2014 20:34, Daniel Melameth  wrote:
> With OpenBSD 5.2, I had no issue doing suspend and hibernate:  when I
> closed the lid, it suspended, when I hit Fn+F12 the BIOS took over,
> with it's own pretty text interface, and hibernated the system.
> iwi(4) also worked flawlessly with suspend/hibernate.  Fast forward to
> upgrading to "5.5" with ACPI:  setting machdep.lidsuspend=1 allows the
> system to suspend when I close the lid, but iwi(4) is broken upon
> resume (iwi0: could not load boot firmware) and Fn+F12 or ZZZ leaves
> me with a blank screen and an eternal flashing moon LED (swap is RAM +
> 1GB).  If I disable ACPI in UKC, which is enabled by default,
> everything works as it did in 5.2 with the exception of hibernate
> which behaves as if ACPI was enabled.
>
> Any recommendations on how to fix?
>
> Thanks.
>
>
> dmesg with ACPI enabled (default):
>
> OpenBSD 5.5 (GENERIC) #276: Wed Mar  5 09:57:06 MST 2014
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) M processor 2.00GHz ("GenuineIntel" 686-class) 2 GHz
> cpu0: 
> FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,EST,TM2,PERF
> real mem  = 2146332672 (2046MB)
> avail mem = 2098974720 (2001MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @
> 0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (61 entries)
> bios0: vendor IBM version "1RETDRWW (3.23 )" date 06/18/2007
> bios0: IBM 2373C61
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
> acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4)
> DOCK(S4) USB0(S3) USB1(S3) AC9M(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (PCI1)
> acpicpu0 at acpi0: C3, C2, C1, PSS
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
> acpitz0 at acpi0: critical temperature is 93 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> acpibat0 at acpi0: BAT0 model "IBM-08K8198" serial   153 type LION oem "SANYO"
> acpibat1 at acpi0: BAT1 not present
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock0 at acpi0: DOCK not docked (0)
> bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000
> 0xdc000/0x4000! 0xe/0x1
> cpu0 at mainbus0: (uniprocessor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: Enhanced SpeedStep 1999 MHz: speeds: 2000, 1800, 1600, 1400,
> 1200, 1000, 800, 600 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
> intelagp0 at pchb0
> agp0 at intelagp0: aperture at 0xd000, size 0x1000
> ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M10" rev 0x80
> drm0 at radeondrm0
> radeondrm0: irq 11
> uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
> uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
> uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
> ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x81
> pci2 at ppb1 bus 2
> 2:0:0: mem address conflict 0xb000/0x1000
> 2:0:1: mem address conflict 0xb100/0x1000
> cbb0 at pci2 dev 0 function 0 "TI PCI4520 CardBus" rev 0x01: irq 11
> cbb1 at pci2 dev 0 function 1 "TI PCI4520 CardBus" rev 0x01: irq 11
> em0 at pci2 dev 1 function 0 "Intel 82540EP" rev 0x03: irq 11, address
> 00:01:6c:eb:89:64
> iwi0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2915ABG" rev 0x05:
> irq 11, address 00:12:f0:5b:30:42
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0
> pcmcia0 at cardslot0
> cardslot1 at cbb1 slot 1 flags 0
> cardbus1 at cardslot1: bus 6 device 0 cacheline 0x8, lattimer 0xb0
> pcmcia1 at cardslot1
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x01
> pciide0 at pci0 dev 31 function 1 "Intel 82801DBM IDE" rev 0x01: DMA,
> channel 0 configured to compatibility, channel 1 configured to
> compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0:  ATAPI
> 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: irq 11
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM non-parity P

Re: Unbound in base, yes, what about ldns?

[Kenneth Westerback]

On 19 March 2014 18:09, Chris Smith  wrote:
> Great to see Unbound in base, thanks.
>
> But what about ldns? I still have that installed as a package -
> removed the unbound package as per the -current instructions, but
> shouldn't the ldns package package be removed as well as I believe
> unbound requires it and therefore it would have to be built by base as
> well. Or am I off-base?
>
> Thanks,
>
> Chris
>

The unbound in base has it's own cut down version of ldns. No need for
the package.

... Ken

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

[Kenneth Westerback]

Alas, softraid only supports 512 byte block devices at the moment.

 Ken
On Mar 19, 2014 11:36 AM, "Marcus MERIGHI"  wrote:

> Reference:
> ``Softraid 3TB Problems''
> http://marc.info/?l=openbsd-misc&m=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
>
> DMESG FULL:
> This is -current with a patch from brad@ to get the NICs (re) working.
>
> OpenBSD 5.5-current (GENERIC.MP) #3: Tue Mar 11 14:18:33 CET 2014
> r...@fofo.fifi.at:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4161052672 (3968MB)
> avail mem = 4041580544 (3854MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
> bios0: vendor American Megatrends Inc. version "1.03" date 08/09/2013
> bios0: Shuttle Inc. DS47D
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT MCFG SLIC HPET SSDT SSDT SSDT
> acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3)
> USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4)
> RP03(S4) PXSX(S4) RP04(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Celeron(R) CPU 847 @ 1.10GHz, 1097.67 MHz
> cpu0:
>
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,NXE,LONG,LAHF,PERF,ITSC
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Celeron(R) CPU 847 @ 1.10GHz, 1097.51 MHz
> cpu1:
>
>
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE
,NXE,LONG,LAHF,PERF,ITSC
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (P0P1)
> acpiprt2 at acpi0: bus 1 (RP01)
> acpiprt3 at acpi0: bus 2 (RP02)
> acpiprt4 at acpi0: bus 3 (RP03)
> acpiprt5 at acpi0: bus 4 (RP04)
> acpiprt6 at acpi0: bus -1 (RP05)
> acpiprt7 at acpi0: bus -1 (RP06)
> acpiprt8 at acpi0: bus -1 (RP07)
> acpiprt9 at acpi0: bus -1 (RP08)
> acpiprt10 at acpi0: bus -1 (PEG0)
> acpiprt11 at acpi0: bus -1 (PEG1)
> acpiprt12 at acpi0: bus -1 (PEG2)
> acpiprt13 at acpi0: bus -1 (PEG3)
> acpiec0 at acpi0: Failed to read resource settings
> acpicpu0 at acpi0: C1, PSS
> acpicpu1 at acpi0: C1, PSS
> acpipwrres0 at acpi0: FN00, resource for FAN0
> acpipwrres1 at acpi0: FN01, resource for FAN1
> acpipwrres2 at acpi0:

Re: Linux partition appears as ext2 partition in disklabel

[Kenneth Westerback]

On 6 March 2014 13:59, Dmitrij D. Czarkoff  wrote:
> Kenneth Westerback said:
>> delete the partition 'i'. You don't need it, as it will be
>> automatically created when necessary.

Something would have been added. Again, the output of
'disklabel -d sd0' would be useful.

 Ken

>
> Thanks!
>
> Apparently it wasn't re-created automatically, but I could rebuild my
> disklabel using "disklabel -dE sd0", so now it works as expected.
>
> --
> Dmitrij D. Czarkoff

Re: Linux partition appears as ext2 partition in disklabel

[Kenneth Westerback]

On 6 March 2014 13:23, Dmitrij D. Czarkoff  wrote:
> Ted Unangst said:
>> On Thu, Mar 06, 2014 at 18:49, Dmitrij D. Czarkoff wrote:
>> > Hello!
>> >
>> > I have a strange problem. Recently I added following to my /etc/fstab:
>> >
>> >   /dev/sd0i /mnt/arch ext2fs rw,nodev,nosuid,noexec 0 0
>> >
>> > I can't mount this partition using "mount -a":
>> >
>> >   $ sudo mount -a
>> >   mount: /dev/sd0i: fstab type ext2fs != disklabel type ntfs
>>
>> >   i:104857600 2048NTFS   # 
>> > /mnt/arch
>>
>> Edit the disklabel to say ext2fs?
>
> I was under impression that fdisk edits MBR partitions and disklabel
> only edits BSD labels. Anyway:
>
>   $ sudo disklabel -E sd0
>   Label editor (enter '?' for help at any prompt)
>   > p
>   OpenBSD area: 104859648-625137345; size: 520277697; free: 15
>   #size   offset  fstype [fsize bsize  cpg]
> a: 33556384104859648  4.2BSD   2048 16384 1 # /
> b:  8385938138416032swap   # none
> c:6251424480  unused
> d:478335360146801984  4.2BSD   4096 327681 # /home
> i:104857600 2048NTFS   #
>   /mnt/arch
>   > m i
>   offset: [2048]
>   The offset must be >= 104859648 and < 625137345, the limits of the
>   OpenBSD portion
>   of the disk. The 'b' command can change these limits.
>   >
>
> Any other ideas?

delete the partition 'i'. You don't need it, as it will be
automatically created when necessary.

 Ken

>
> --
> Dmitrij D. Czarkoff

Re: Linux partition appears as ext2 partition in disklabel

[Kenneth Westerback]

On 6 March 2014 12:49, Dmitrij D. Czarkoff  wrote:
> Hello!
>
> I have a strange problem. Recently I added following to my /etc/fstab:
>
>   /dev/sd0i /mnt/arch ext2fs rw,nodev,nosuid,noexec 0 0
>
> I can't mount this partition using "mount -a":
>
>   $ sudo mount -a
>   mount: /dev/sd0i: fstab type ext2fs != disklabel type ntfs
>
> The same message appears on boot. Still, I can mount it by hand:
>
>   $ sudo mount /mnt/arch
>   $ mount
>   /dev/sd0a on / type ffs (local)
>   /dev/sd0d on /home type ffs (local, nodev, nosuid)
>   /dev/sd0i on /mnt/arch type ext2fs (local, nodev, noexec, nosuid)
>
> The partition is actually of type 0x83, and the first 2 Mb of disk were
> zero-outed before Linux and OpenBSD were installed. If it is of any
> importance, the system is Lenovo ThinkPad E325, and the Linux partition
> contains working, bootable Archlinux installation. Bootloader is
> Syslinux.
>
> I'm running OpenBSD-current from snapshots, updating every several days.
> First time I tried it was probably about a week ago and it consistently
> keeps behaving the same.
>
>
> ==
>   Fdisk
> ==
>
> Disk: sd0   geometry: 38913/255/63 [625142448 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
> *0: 83  0  32  33 -   6527  53  54 [2048:   104857600 ] Linux 
> files*
>  1: A6   6527  53  55 -  38912 254  63 [   104859648:   520277697 ] OpenBSD
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>
>
> ==
>   Disklabel
> ==
>
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: ST320LT007-9ZV14
> duid: d02babcb5f5d80c4
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 38913
> total sectors: 625142448
> boundstart: 104859648
> boundend: 625137345
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   a: 33556384104859648  4.2BSD   2048 163841 # /
>   b:  8385938138416032swap   # none
>   c:6251424480  unused
>   d:478335360146801984  4.2BSD   4096 327681 # /home
>   i:104857600 2048NTFS   # /mnt/arch

Your disklabel seems to have NTFS down as the file system for 'i'.
Which might explain the error and inconsistant behaviour. This may be
an old disklabel, since zero'ing out the first 2MB doesn't look like
it would have reached the OpenBSD partition where the disklabel would
be stored.

I created an MBR with partition 0 of type 0x83, and disklabel here
spoofs that correctly to 'ext2fs'.

What does 'disklabel -d sd0' show?

 Ken

Re: sysmerge trouble

[Kenneth Westerback]

On 24 February 2014 07:56, Ed Ahlsen-Girard  wrote:
> On 2014-02-24 "Shawn K. Quinn"  wrote:
> Date:   2014-02-24 10:49:03
>
>> On Sun, Feb 23, 2014, at 03:45 PM, Ed Ahlsen-Girard wrote:
>> > Took a while to submit this, but for the past ~ six weeks of
>> > snapshots sysmerge fails thus:
>> >
>> > ERROR: failed to populate from /usr/src and create checksum file
>>
>> sysmerge works fine for me on amd64 sans the occasional incident of
>> operator error.
>>
>> What's under your /usr/src? What's your sysmerge command line?
>>
>> --
>>   Shawn K. Quinn
>>   skqu...@rushpost.com
>
> My /usr/src appears to contain a source tree. I would post the results
> of find /usr/src if asked, but that'd be a long message.
>
> sysmerge command line is:
>
> sysmerge
>
> which I have been using for a few years.
>
> --
>
> Edward Ahlsen-Girard
> Ft Walton Beach, FL
>

Do you perhaps have to switch to 'sysmerge -S'?

 Ken

Re: DVD ISO and mount_udf: FSD does not lie within the partition!

[Kenneth Westerback]

On 18 February 2014 02:57, Philippe Meunier  wrote:
> Hello,
>
> I have problems mounting Windows 7 DVD ISO images on OpenBSD 5.4
> stable.  For example, you can download X17-59463.iso from
> http://www.mydigitallife.info/official-windows-7-sp1-iso-from-digital-river/
>
> # ls -l X17-59463.iso
> -rw---  1 meunier  users  2564476928 Feb 16 01:24 X17-59463.iso
>
> Then:
>
> # vnconfig vnd0 X17-59463.iso
> # disklabel vnd0
> # /dev/rvnd0c:
> type: vnd
> disk: GSP1RMCULFRER_EN
> label: _DVD
> duid: 
> flags:
> bytes/sector: 512

I'm pretty sure that DVD's don't come with a disk sector size of 512
bytes. So trying to access it with 512 byte sectors could be one
problem. You can play with the vnconfig '-t' option and add an
appropriate entry to /etc/disktab that specifies the more likely
sector size of 2048 bytes. Or you can burn the .iso to a physical
device.

If you burn it to a physical device, what does disklabel show?

 Ken

> sectors/track: 100
> tracks/cylinder: 1
> sectors/cylinder: 100
> cylinders: 50087
> total sectors: 5008744
> boundstart: 0
> boundend: 5008744
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   a:  50087440 ISO9660
>   c:  50087440 ISO9660
> # mount_cd9660 /dev/vnd0a /mnt
> # ls -la /mnt
> total 4
> dr-xr-xr-x   1 root  wheel  112 Apr 12  2011 .
> drwxr-xr-x  14 root  wheel  512 Dec 31 18:44 ..
> -r-xr-xr-x   1 root  wheel  135 Apr 12  2011 README.TXT
> # cat /mnt/README.TXT
> This disc contains a "UDF" file system and requires an operating system
> that supports the ISO-13346 "UDF" file system specification.
> # umount /mnt
> # mount_udf /dev/vnd0a /mnt
> FSD does not lie within the partition!
> mount_udf: mount: Invalid argument
> #
>
> So... how do I access the UDF file system on such a DVD ISO image?
>
> For reference, here's what I get using Linux (booting Ubuntu from a
> USB stick on the same computer):
>
> me@pc:~$ sudo mount -t ufs -o ufstype=44bsd,ro /dev/sda8 /mnt
> me@pc:~$ sudo mount -o loop /mnt/meunier/X17-59463.iso /mnt2
> me@pc:~$ mount | egrep iso
> /mnt/meunier/X17-59463.iso on /mnt2 type udf (ro)
> me@pc:~$ ls /mnt2
> autorun.inf  boot  bootmgr  efi  setup.exe  sources  support  upgrade
> me@pc:~$
>
> Is there any way to get the same thing on OpenBSD, or am I out of
> luck?
>
> Thanks,
>
> Philippe

Re: Xorg: Segmentation fault at address 0x28 w/ Intel HD Graphics 4600

[Kenneth Westerback]

On 10 February 2014 13:11, RD Thrush  wrote:
> With a somewhat recent i7 desktop, using startx, X seems to run ok; however, 
> at 1024x768 rather than the expected 1920x1200 resolution. ctl-alt-keypad+ or 
> - have no effect on resolution.  ctl-alt-backspace  correctly reverts to text 
> mode.  I then tried Xorg -configure to look for hints to improve resolution; 
> however, that resulted in a segfault almost immediately.
>

I'm pretty sure

vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06

is not supported in the sense of working as opposed to being
recognized. i.e. 1024x768 is likely as good as it gets until support
is added. Even 4400 is problematic at the moment.

But I'm willing to be corrected by people more in the know. :-)

 Ken

Re: new to OpenBSD and have a few questions

[Kenneth Westerback]

On 9 February 2014 16:58, d...@genunix.com  wrote:
> warning: really long post with some questions and thinking.
>
> Hello dear OpenBSD types.
>
> I have been using UNIX in various forms and flavours for a long time now
> and could even go so far as to say a "very" long time. Therefore it just
> seems so very familiar to me and yet, a bit new.
>
> First thing I see is that it was so very easy to install. I was almost
> expecting to need to curse and recurse but the install was trivial. I
> kept a log of the whole process in case something went wrong but nope,
> it is just a nice simple log.

Perhaps you can share this log. At least give us a clue what machine you
are installing on.

>
> However upon first boot I see that my disk slices are a bit odd in terms
> of size. I would have liked to arrange things differently. Certainly I
> will need to create a mount point for a /opt filesystem and that means I
> need to read fdisk and disklabel man pages over and over.
>
> The questions on my mind, in order of importance seem to be :
>
> 1) how do I do a full low level backup and then verify that I
>can restore the system ?  To an NFS mount or tape or whatever.

Why? If you just installed, I would simply install again rather than
trying to preserve the installed bits.

>
> 2) how do I edit the disk slices or "partitions" to be what I want?

disklabel(8) is the  normal tool to edit disklabels. fdisk(8) the tool
to edit MBRs. Both are on offer during install. Although fdisk(8) will
only be offered on MBR reliant
architectures like i386 and amd64.

>
> 3) how do I eventually contribute software packages or similar?

Read the documentation, especially ports(7), create a port, don the
obligatory asbestoes undergarments and send it to po...@openbsd.org.

>
> So number (1) would seem to need a dump command and I see a lot of very
> friendly and familiar looking goodness in dump(8). The disk low level
> bits seem to use 512 byte blocks and so I am going to guess that I can
> do a level 0 dump of each filesystem one at a time to some NFS mounted
> location and that would suffice for the filesystem level. Not too sure
> how to deal with the partition table and boot records etc. I see from
> the fdisk command this :
>
> # fdisk -e sd0
> Enter 'help' for information
> fdisk: 1> print
> Disk: sd0   geometry: 7508/19/248 [35378533 Sectors]
> Offset: 0   Signature: 0xD6BC
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 55  64103   7  97 -  64111  12 157 [   302055168:   38997 ] EZ-Drive
>  1: D5 103269   3  18 - 103270  17  37 [   486604289:8204 ]  ID>
>  2: 92 153115  15 134 - 153118  17  75 [   721481733:   14574 ]  ID>
>  3: 86 338260   4  10 - 106301  12  65 [  1593882121:  3201978528 ] NT FAT VS
> fdisk: 1> exit

So this MBR is complete garbage. First clue: signature 0xD6BC. This is
not an MBR, and
most certainly not one created by an OpenBSD install.

>
> Looks like there is some black magix at work in partition id 0 through
> 2 and then one big fat large chunk at id 3 wherein my OpenBSD 5.4 install
> must live. I am not too sure how to dump or backup the partition table
> info such that a totally blank disk could be inserted and then a restore
> done. Perhaps my whole thinking appoach here is old school wrong?
>
> Whatever the case the disklabel tool shows me this :
>
> # disklabel sd0
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: ST318404LSUN18G
> duid: c5cd4c19ed688052
> flags: vendor
> bytes/sector: 512
> sectors/track: 248
> tracks/cylinder: 19
> sectors/cylinder: 4712
> cylinders: 7508
> total sectors: 35378533
> boundstart: 0
> boundend: 35378533
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   a:  12015600  4.2BSD   2048 163841 # /
>   b:  1201560  1201560swap   # none
>   c: 353785330  unused
>   d:  1903648  2403120  4.2BSD   2048 163841 # /tmp
>   e:  2855472  4306768  4.2BSD   2048 163841 # /var
>   f:  2879032  7162240  4.2BSD   2048 163841 # /usr
>   g:  1672760 10041272  4.2BSD   2048 163841 # /usr/X11R6
>   h:  6266960 11714032  4.2BSD   2048 163841 # /usr/local
>   i:  2511496 17980992  4.2BSD   2048 163841 # /usr/src
>   j:  3491592 20492488  4.2BSD   2048 163841 # /usr/obj
>   k: 11393616 23984080  4.2BSD   2048 163841 # /home
> #

In the complete absence of a valid MBR disklabel(8) simply assumed you
were using the entire disk and wrote a disklabel at block 0. Or
perhaps 1 depending on the
architecture you are installing on. Clue here is that partition 'a'
starts at offset 0., i.e.
the f

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

[Kenneth Westerback]

rc.conf(8) says "create and edit a rc.conf.local". Not copy rc.conf.
I'm not sure what the FAQ says but I'd think it would be similar
advice.

 Ken

On 9 February 2014 13:28, VaZub  wrote:
> Hi all,
>
> There is a small nuisance I've stumbled upon during my first
> experiments with OpenBSD.
>
> Both the man page for rc.conf(8) as well as the official OpenBSD FAQ
> (10.3) suggest to avoid editing /etc/rc.conf directly and instead copy
> it to /etc/rc.conf.local and edit afterwards. Yet it seems both fail
> to mention, that in order to prevent your system from going ballistic
> after doing this, you should also comment out or delete a particular
> line of code in /etc/rc.conf.local, namely this one:
> "[ -f /etc/rc.conf.local ] && . /etc/rc.conf.local". Not good,
> especially for those who do follow official instructions and still
> suddenly find themselves with a broken system on their hands for no
> apparent reason.
>
> This might seem like a trivial issue for old-timers, and one is sure
> to find the appropriate solution with a little bit of deeper googling,
> but having short relevant notices in the aforementioned manuals could
> save newcomers some introductory frustration. What do you think? Is
> there anyone among those looking after the official documentation up
> to consider such a suggestion?
>
> Regards,
> Vasyl Zubko

Re: Upgrade path from 4.1?

[Kenneth Westerback]

On 6 February 2014 12:40, Chris Cappuccio  wrote:
> L. V. Lammert [l...@omnitec.net] wrote:
>> On Thu, 6 Feb 2014, davy wrote:
>>
>> > Can I do a 4.1 -> 5.4 in one shot?
>> >
>> Nope. One version at a time, .. though the better solution would be to do
>> a fresh install and copy data.
>>
>
> What I'm recommending isn't really an upgrade so much as using the old
> box to bootstrap a newest snapshot. As long as the bootblocks are still
> compatible, you can do it.

Re: Upgrade path from 4.1?

[Kenneth Westerback]

On 6 February 2014 12:40, Chris Cappuccio  wrote:
> L. V. Lammert [l...@omnitec.net] wrote:
>> On Thu, 6 Feb 2014, davy wrote:
>>
>> > Can I do a 4.1 -> 5.4 in one shot?
>> >
>> Nope. One version at a time, .. though the better solution would be to do
>> a fresh install and copy data.
>>
>
> What I'm recommending isn't really an upgrade so much as using the old
> box to bootstrap a newest snapshot. As long as the bootblocks are still
> compatible, you can do it.
>

And, surprise!, boot blocks do change. 5.5 will be an example as things are
rearranged and unified.

 Ken

Re: Upgrade path from 4.1?

[Kenneth Westerback]

On 6 February 2014 12:31, L. V. Lammert  wrote:
> On Thu, 6 Feb 2014, Kenneth Westerback wrote:
>
>> Well, that would imply waiting for May 1 or whenever the physical CD's
>> are available.
>>
> 5.4 is available now, ..
>
>> Starting now with a -current snapshot means getting everything working
>> in the meantime and then ordering the new CD's and installing the
>>
> Far better to recommend CD installs, .. -current or -release may require a
> tad more expertise to manage.
>
> Lee

I violently disagree! And particularly in this case. Where it would be
far better to
avoid one whole upgrade cycle by getting the environment working with
-current and moving to 5.5-stable safe in the knowledge that you don't
have to re-check for flag days,  configuration parsing changes, etc.

Now, *buying* CD's is always highly recommended. The more the better!

 Ken

Re: Upgrade path from 4.1?

[Kenneth Westerback]

On 6 February 2014 11:44, L. V. Lammert  wrote:
> On Thu, 6 Feb 2014, Kenneth Westerback wrote:
>
>> Shudder. NO! :-)
>>
>> Aside from the very valid hardware concerns Nick mentioned, there are
>> too many flag days of various kinds strewn along that path. Skip them
>> all, start fresh with a -current
>> snapshot.
>>
> Much better to start with new CD set, eh?

Well, that would imply waiting for May 1 or whenever the physical CD's
are available.

Starting now with a -current snapshot means getting everything working
in the meantime and then ordering the new CD's and installing the
-release (or -stable) files without worrying about flag days. We are
very close to locking 5.5 so very little major will be changing
between now and CD delivery.

 Ken

>
> Lee

Re: Upgrade path from 4.1?

[Kenneth Westerback]

Shudder. NO! :-)

Aside from the very valid hardware concerns Nick mentioned, there are
too many flag days of various kinds strewn along that path. Skip them
all, start fresh with a -current
snapshot.

 Ken

On 6 February 2014 05:49, davy  wrote:
> Hi,
>
> I've recently was asked to take over the maintenance of an old OpenBSD 
> machine, which has not been updated in the last 7 years.
>
> Currently the machine has been running for close to 1000 days on 4.1. It has 
> been a while since I worked with OpenBSD (shame on me), and I'm really not 
> sure what the best way would be to upgrade this machine, knowning I don't 
> have a serial or local access to the box.
>
> Can I do a 4.1 -> 5.4 in one shot?
>
> thx!
> Davy

Re: dhclient

[Kenneth Westerback]

On 5 February 2014 06:35, Holger Glaess  wrote:
> Am 03.02.2014 17:54, schrieb Kenneth Westerback:
>
>> Reactivating the dhclient-script is not going to happen.
>>
>> I am interested in what you would see syntax in dhclient.conf looking
>> like.
>>
>> Would multi-path routing modifications to all routes be needed? How should
>> this
>> be combined with supersede/default/append commands for the relevant
>> options? Would it apply to all members of each option, or route by
>> route?
>>
>> If all else fails you can always use the ISC dhclient from ports to
>> gain access to a dhclient-script again.
>>
>>  Ken
>>
>> On 31 January 2014 02:04, Holger Glaess  wrote:
>>>
>>> Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
>>>
>>>> Em 29-01-2014 18:13, Holger Glaess escreveu:
>>>>>
>>>>> hi
>>>>>
>>>>> i try to setup and multipath configuration with 2 line provider
>>>>>
>>>>> 1 cable with dhcp(client)
>>>>> 1 with pppoe
>>>>>
>>>>> just dynamic ips.
>>>>>
>>>>> the pppoe config create well the new default route with -math
>>>>> but dhclient dont.
>>>>>
>>>>> [snip pppoe config]
>>>>>
>>>>> inet 0.0.0.0 255.255.255.255 NONE \
>>>>> pppoedev msk0 authproto pap \
>>>>> authname 'bla@blub' authkey 'blub' up
>>>>> dest 0.0.0.1
>>>>> !/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
>>>>>
>>>>> [/snip pppoe config]
>>>>>
>>>>>
>>>>> after a couple of days i found that the dhclient not use the
>>>>> dhclient-script since 5.3 anymore.
>>>>>
>>>>>
>>>>> so how can i setup the -math option at the dhclient config ?
>>>>>
>>>>>
>>>>> or it is possible to add some lines in dhclient that he check the
>>>>> sysctl and , if net.inet.ip.multipath=1 ,
>>>>> he add the default route with ( for ) multipathing.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> holger
>>>>>
>>>> Check if your dhcp server always gives you the same router ip address.
>>>> If so, you can tweak with your dhclient.conf to reject and not ask for
>>>> routers, and then set it up manually as you do in your hostname.pppoe0.
>>>> And you can always run a script that is run after the dhcp negotiation,
>>>> looks for the gateway related entry, deletes it and then re-adds it with
>>>> the mpath modifier. There are a lot of options in this regard.
>>>>
>>>> Cheers,
>>>>
>>> hi
>>>
>>> shure , i can write a wrap around solution for the but this not the
>>> "dynamic" way like
>>> pppoe or  dhcp  to get and set ips.
>>>
>>> i'm not the C programmer but i think  it is not mutch work to add a
>>> solution
>>> in dhclient,
>>> or as option to reaktivate the dhclient-script part.
>>>
>>>
>>> holger
>
> hi
>
> at moment i have following setup
>
> # cat hostname.pppoe0
>
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev msk0 authproto pap \
> authname 'bla' authkey 'blub' up
> dest 0.0.0.1
> #!/sbin/route add default -ifp pppoe0 0.0.0.1
> #!/sbin/route add -inet6 default -ifp pppoe0 ::0.0.0.1
>
> #
> !/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
> !/sbin/route add -inet6 -mpath default -ifp pppoe0 ::0.0.0.1
>
> # cat /etc/hostname.vlan5
> dhcp vlandev msk1
> !/sbin/route add -mpath default xww.x.yy.zz.
>
>
> # cat /etc/dhclient.conf
>
> timeout 15;
> retry 5;
> reboot 2;
> select-timeout 5;
> initial-interval 2;
>
>
> interface "vlan5" {
> ignore domain-name-servers;
> ignore host-name;
> ignore routers;
> send dhcp-lease-time 3600;
> request subnet-mask, broadcast-address, time-offset, routers,
> domain-name-servers, host-name, ntp-servers;
> }
>
>
> it work for a while with the mpath settings after the start but if the
> dhclient renew his setting he set the default route
> i his standard way , hi ignore the settings in his config ( is this right ?
> )

I've never tried mixing vlans and dhclient, so I'm not 100% sure what
the behaviour is going to be. :-)

If you can run dhclient from the command line, and specify the '-L' option and a
file location, I'd be interested in what the offered and effective
dhcp leases look
like. Also a tcpdump of the interaction could supply valuable
information. Again,
not sure of tcpdump vs vlan interfaces, but something like

tcpdump -i msk1 -s 2000 -w 

running when you start dhclient should generate a useful file I can peruse.

After that I can send you some dhclient debugging diffs if necessary.

 Ken

>
>
> holger

Re: Is [binary] package signing planned?

[Kenneth Westerback]

On 4 February 2014 11:25, Marc Espie  wrote:
> 2014-02-04 Kim Twain :
>> Does pkg_add automatically check these signatures, or, as of now, I'd need
>> to manually download the packages, verify them with signify and then install
>> them locally with pkg_add?
>
> In -current, if you don't use any flags to pkg_add, and you don't see any
> message at the end, the packages were signed and verified.
>
> (and by default, post 5.5, pkg_add will probably error out if the packages
> are not signed if you don't use -Dunsigned !)
>
> Maybe you're already using signed packages and haven't noticed.
> (there were two or hiccups in some snapshots, but apart from that, things
> have been working great).
>
>
> Getting a streamlined process WAS the difficult part in getting signed
> packages out, NOT the technical feat of having signed packages...
>
> After all, pkg_create/pkg_add has known how to sign stuff for 3 years by now.
>
> signify(1) makes things more transparent: no chain of trust, pure keys.
>
> One cool thing is that the signatures are small enough that they can be
> embedded directly in the package (which already has sha256 for everything).
>
> This has the advantage of decentralization: package snapshots can be partially
> synchronized, and still each package carries its own signature. Less margin
> for strange errors -> stuff that works most of the time -> more trustworthy.
>
> Remember that message about ssh keys that changed that you used to get when
> admins weren't savvy about getting keys around, or all those self-signed
> https certificates you've been trained to ignore ? signatures are the same.
> if they're not 100% present by default, people will be trained to ignore them.
>
>
> If you think security is a technicality, you only have 1/3rd of the
> story.Getting the process right and making sure the users don't do
> anything stupid is the right part.
>

Maybe even the hard part. 

 Ken

Re: dhclient

[Kenneth Westerback]

Reactivating the dhclient-script is not going to happen.

I am interested in what you would see syntax in dhclient.conf looking like.

Would multi-path routing modifications to all routes be needed? How should this
be combined with supersede/default/append commands for the relevant
options? Would it apply to all members of each option, or route by
route?

If all else fails you can always use the ISC dhclient from ports to
gain access to a dhclient-script again.

 Ken

On 31 January 2014 02:04, Holger Glaess  wrote:
> Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
>
>> Em 29-01-2014 18:13, Holger Glaess escreveu:
>>>
>>> hi
>>>
>>> i try to setup and multipath configuration with 2 line provider
>>>
>>> 1 cable with dhcp(client)
>>> 1 with pppoe
>>>
>>> just dynamic ips.
>>>
>>> the pppoe config create well the new default route with -math
>>> but dhclient dont.
>>>
>>> [snip pppoe config]
>>>
>>> inet 0.0.0.0 255.255.255.255 NONE \
>>> pppoedev msk0 authproto pap \
>>> authname 'bla@blub' authkey 'blub' up
>>> dest 0.0.0.1
>>> !/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
>>>
>>> [/snip pppoe config]
>>>
>>>
>>> after a couple of days i found that the dhclient not use the
>>> dhclient-script since 5.3 anymore.
>>>
>>>
>>> so how can i setup the -math option at the dhclient config ?
>>>
>>>
>>> or it is possible to add some lines in dhclient that he check the
>>> sysctl and , if net.inet.ip.multipath=1 ,
>>> he add the default route with ( for ) multipathing.
>>>
>>>
>>>
>>>
>>>
>>>
>>> holger
>>>
>> Check if your dhcp server always gives you the same router ip address.
>> If so, you can tweak with your dhclient.conf to reject and not ask for
>> routers, and then set it up manually as you do in your hostname.pppoe0.
>> And you can always run a script that is run after the dhcp negotiation,
>> looks for the gateway related entry, deletes it and then re-adds it with
>> the mpath modifier. There are a lot of options in this regard.
>>
>> Cheers,
>>
>
> hi
>
> shure , i can write a wrap around solution for the but this not the
> "dynamic" way like
> pppoe or  dhcp  to get and set ips.
>
> i'm not the C programmer but i think  it is not mutch work to add a solution
> in dhclient,
> or as option to reaktivate the dhclient-script part.
>
>
> holger

Re: The "unknown" in i386-unknown-openbsd5.4

[Kenneth Westerback]

i386-donatetoopenbsdfoundationtoday-openbsd5.4?

. Ken


On 2 February 2014 12:10, Adam Jensen  wrote:
> On Sun, 2 Feb 2014 16:17:08 + (UTC)
> na...@mips.inka.de (Christian Weisgerber) wrote:
>
>> At least it's consistent.  FreeBSD's collection of
>>   -undermydesk- (gcc)
>>   -marcel-  (gdb)
>>   -unknown- (clang, binutils, occasionally in ports)
>>   -portbld- (most ports)
>> would never confuse anybody, would it?
>>
>
> It would certainly be disappointing to see something like that
> in OpenBSD. A new naming convention wouldn't necessarily need to
> be whimsical and inconsistent, would it? (That's a rhetorical
> question, but you get my point, right?)

Re: newfs_msdos(8) creates faulty filesystems

[Kenneth Westerback]

Neither field is required. 'Free Space' in fsinfo can be -1 or just wrong,
and 'Next Free Cluster' is a  hint only. Hence in either case you can fix
them up, or ignore their incorrectness and the filesystem is still
considered ok.

And since they are not required I guess newfs never bothered to fill them
out correctly.

 Ken






On Sun, Oct 20, 2013 at 2:13 PM, David Vasek  wrote:

> Hello,
>
> a filesystem created by newfs_msdos(8) is reported as faulty by
> fsck_msdos(8). And it is indeed. Repeatable. There must be something wrong.
> The media itself (a USB flash drive) doesn't have any issues.
>
> # newfs -t msdos /dev/rsd4i /dev/rsd4i: 31224352 sectors in 3903044 FAT32
> clusters (4096 bytes/cluster)
> bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=63 hds=255 hid=8064 bsec=31285376
> bspf=30493 rdcl=2 infs=1 bkbs=2
>
> # fsck -n /dev/rsd4i
> ** /dev/rsd4i (NO WRITE)
> ** Phase 1 - Read and Compare FATs
> ** Phase 2 - Check Cluster Chains
> ** Phase 3 - Check Directories
> ** Phase 4 - Check for Lost Files
> Free space in FSInfo block (-1) not correct (3903043)
> fix? no
> Next free cluster in FSInfo block (2) not free
> fix? no
> 1 files, 3029260 free (3903043 clusters)
>
> # fsck /dev/rsd4i
> ** /dev/rsd4i
> ** Phase 1 - Read and Compare FATs
> ** Phase 2 - Check Cluster Chains
> ** Phase 3 - Check Directories
> ** Phase 4 - Check for Lost Files
> Free space in FSInfo block (-1) not correct (3903043)
> fix? [Fyn] y
> Next free cluster in FSInfo block (2) not free
> fix? [Fyn] y
> 1 files, 3029260 free (3903043 clusters)
>
> # fsck /dev/rsd4i ** /dev/rsd4i
> ** Phase 1 - Read and Compare FATs
> ** Phase 2 - Check Cluster Chains
> ** Phase 3 - Check Directories
> ** Phase 4 - Check for Lost Files
> 1 files, 3029260 free (3903043 clusters)
>
>
> OpenBSD 5.3 (GENERIC.MP) #53: Fri Mar  1 09:34:37 MST 2013
> 
> dera...@i386.openbsd.org:/usr/**src/sys/arch/i386/compile/GENE**RIC.MP
>
> umass1 at uhub0 port 4 configuration 1 interface 0 "Kingston DT 101 G2"
> rev 2.00/1.00 addr 3
> umass1: using SCSI over Bulk-Only
> scsibus4 at umass1: 2 targets, initiator 0
> sd4 at scsibus4 targ 1 lun 0:  SCSI0 0/direct
> removable serial.09511642BC81D71A0189
> sd4: 15280MB, 512 bytes/sector, 31293440 sectors
>
> # fdisk sd4
> Disk: sd4   geometry: 1947/255/63 [31293440 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> --**--**
> ---
> *0: 0C  0 128   1 -   1947 236  17 [8064:31285376 ] 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
>
> # disklabel sd4
> # /dev/rsd4c:
> type: SCSI
> disk: SCSI disk
> label: DT 101 G2 duid: 
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 1947
> total sectors: 31293440
> boundstart: 0
> boundend: 31293440
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize  cpg]
>   c: 312934400  unused
>   i: 31285376 8064   MSDOS
>
> Regards,
> David

Re: OpenZFS announcement

[Kenneth Westerback]

http://open-zfs.org/wiki/About_OpenZFS

Under 'Other' at the bottom:

"ZFS source code is copyright various contributors, and available under the
CDDL open-source license."

The second paragraph is amusing:

"OpenZFS is not associated with openzfs.org. Don't forget the dash in our
URS: open-zfs.org"

 Ken



On Wed, Sep 18, 2013 at 2:37 AM, patric conant
wrote:

> http://www.open-zfs.org/wiki/Announcement
>
> It supposed to be open-er. I didn't find a license, thought it might be of
> mild interest.

Re: Root file system is growing strangely

[Kenneth Westerback]

On Sat, Dec 19, 2009 at 7:50 AM, ropers  wrote:
> 2009/12/18 Daniel Zhelev :
>> after log in I sow that the root file system
>> is over 100%.
>
> *Over* 100%? How is that even possible?
>
>

Because this is Unix? Not a sarcastic reply, pointing out that this is
a well known feature of ffs. Although finding a nice Goggle phrase to
pull up an historical discussion seem unexpectedly difficult.

 Ken

Re: New Western Digital disks will have 4KB block size - issue?

[Kenneth Westerback]

On Wed, Dec 16, 2009 at 9:21 PM, Aaron Mason 
wrote:
> On Thu, Dec 17, 2009 at 12:46 PM, Kenneth Westerback
>  wrote:
>> On Wed, Dec 16, 2009 at 7:12 PM, Marco Peereboom 
wrote:
>>> yes
>>>
>>> On Thu, Dec 17, 2009 at 12:30:46AM +0100, Robert wrote:
>>>> Hi,
>>>>
>>>> I just read [1,2] that Western Digital (and probably others) will start
>>>> to sell disks with an internal block size of 4KB instead of 512 byte.
>>>>
>>>> The article mentions that this might lead to a considerable performance
>>>> impact if the  logical partition alignment is not in sync with the
>>>> physical one ("e.g. if partitions starts at sector 63 wich is not a
>>>> multiple of 4KB" [1]):
>>>> "If a block of 4KB should be written, which is (logically) aligned, but
>>>> physically in fact 2 sectors, then both physical sectors will need to be
>>>> read, partially modified and then written back which leads to a serious
>>>> performance hit." [1]
>>>>
>>>> Any comments from someone who has a good knowledge of this area? Will
>>>> this affect OpenBSD?
>>>>
>>>> regards,
>>>> Robert
>>>>
>>>> [1] (german)
>>>>
>>
http://www.heise.de/newsticker/meldung/Festplatten-mit-4-KByte-Sektorgroesse-
>> 887759.html
>>>> [2] http://www.wdc.com/wdproducts/library/whitepapers/en/2579-771430.pdf
>>>
>>>
>>
>> 4K sectors themselves should work ok as we already do that for ffs on
>> CD media. Which works the last I checked. Ensuring alignment on blocks
>> will have to be checked. It sounds like some should donate a few of
>> these 4K devices to the project so we can fix any issues asap.
>>
>>  Ken
>>
>>
>
> I'm looking into the possibility of modifying QEMU for testing this.
> Not sure how close such things would be to reality, but it's worth a
> look in any case and would drop the cost of development significantly.
>
> --
> Aaron Mason - Programmer, open source addict
> I've taken my software vows - for beta or for worse
>

If you just want to see what you can do with/to 4K sectors, read the
vnconfig man page (-t option) and create yourself some 4K sector
devices in your disktab.

However without hardware testing you never know what the clever dicks
at the vendor have done. :-).

 Ken

Re: New Western Digital disks will have 4KB block size - issue?

[Kenneth Westerback]

On Wed, Dec 16, 2009 at 7:12 PM, Marco Peereboom  wrote:
> yes
>
> On Thu, Dec 17, 2009 at 12:30:46AM +0100, Robert wrote:
>> Hi,
>>
>> I just read [1,2] that Western Digital (and probably others) will start
>> to sell disks with an internal block size of 4KB instead of 512 byte.
>>
>> The article mentions that this might lead to a considerable performance
>> impact if the  logical partition alignment is not in sync with the
>> physical one ("e.g. if partitions starts at sector 63 wich is not a
>> multiple of 4KB" [1]):
>> "If a block of 4KB should be written, which is (logically) aligned, but
>> physically in fact 2 sectors, then both physical sectors will need to be
>> read, partially modified and then written back which leads to a serious
>> performance hit." [1]
>>
>> Any comments from someone who has a good knowledge of this area? Will
>> this affect OpenBSD?
>>
>> regards,
>> Robert
>>
>> [1] (german)
>>
http://www.heise.de/newsticker/meldung/Festplatten-mit-4-KByte-Sektorgroesse-
887759.html
>> [2] http://www.wdc.com/wdproducts/library/whitepapers/en/2579-771430.pdf
>
>

4K sectors themselves should work ok as we already do that for ffs on
CD media. Which works the last I checked. Ensuring alignment on blocks
will have to be checked. It sounds like some should donate a few of
these 4K devices to the project so we can fix any issues asap.

 Ken