date:20141202

On Mon, Dec 01, 2014 at 09:52:18PM -0600, Boris Goldberg wrote:

 Hello misc,
 
   I've reported a detailed bug two months ago. The short story - grace
 period end time isn't being reset if the over_soft_quota stage is reached
 by chown command. I've confirmed it on i386 5.0 through current (as of
 month ago) and on amd64 5.4.
   Developers seemed to don't have time for it, so I've asked our
 consultant, Ed Bartosh bart...@gmail.com (not subscribed to the list), to
 look into this. It seems like he has fixed it. Here is the patch for 5.4
 (tested on i386 only yet):
 

Cool, but your mailer mangled the diff. Here it is for current.

BTW, let's take this to tech@, that's a better place. So anybody
replying, please rm misc@.

-Otto

Index: ufs_vnops.c
===
RCS file: /cvs/src/sys/ufs/ufs/ufs_vnops.c,v
retrieving revision 1.116
diff -u -p -r1.116 ufs_vnops.c
--- ufs_vnops.c 3 Nov 2014 21:28:35 -   1.116
+++ ufs_vnops.c 2 Dec 2014 08:10:42 -
@@ -498,6 +498,7 @@ ufs_chown(struct vnode *vp, uid_t uid, g
int error = 0;
daddr_t change;
enum ufs_quota_flags quota_flags = 0;
+   struct ucred *newcr;
 
if (uid == (uid_t)VNOVAL)
uid = DIP(ip, uid);
@@ -534,16 +535,23 @@ ufs_chown(struct vnode *vp, uid_t uid, g
if ((error = getinoquota(ip)) != 0)
goto error;
 
-   if ((error = ufs_quota_alloc_blocks2(ip, change, cred, 
-quota_flags)) != 0) 
+   newcr = crget();
+   newcr-cr_uid = uid;
+   newcr-cr_gid = gid;
+
+   if ((error = ufs_quota_alloc_blocks2(ip, change, newcr,
+   quota_flags)) != 0) {
+   crfree(newcr);
goto error;
+   }
 
-   if ((error = ufs_quota_alloc_inode2(ip, cred ,
-quota_flags)) != 0) {
-   (void)ufs_quota_free_blocks2(ip, change, cred, 
-   quota_flags);   
+   if ((error = ufs_quota_alloc_inode2(ip, newcr, quota_flags)) != 0) {
+   (void)ufs_quota_free_blocks2(ip, change, newcr, quota_flags);
+   crfree(newcr);
goto error;
}
+
+   crfree(newcr);
 
if (getinoquota(ip))
panic(chown: lost quota);

Re: -current hangs during boot from xhci controller on MacbookAir6,1

2014-12-02 Thread Martin Pieuchot

On 01/12/14(Mon) 15:41, Scott Bonds wrote:
 While investigating the slow hard drive on my MacbookAir6,1, I decided
 to take a working installation of -current (20141201 snapshot) on a USB
 drive and try booting it on the MBA6,1. I discovered that booting off of
 a usb drive (with a full install, i.e. bsd.mp NOT bsd.rd) hangs once the
 boot reaches this line:
 
 uhub0 at usb0 Intel xHCI root hub rev 3.00/1.00 addr 1
 
 This behavior manifests while using a 'normal' boot--I did not use the
 OSX bless utility to get the builtin USB controller into ehci mode
 instead of xhci mode. When I *do* do that (use bless to set the usb
 controller into ehci mode) the boot progresses to:
 
 scsibus4 at softraid0: 256 targets
 
 then pauses there for 5 minutes, then proceeds to boot just fine. When
 booting this way, I observe the same pauses/slowness when operating on
 the builtin hard drive as mentioned in the thread I started on that
 topic:
 
 http://marc.info/?l=openbsd-miscm=141747241629431w=2
 
 Anyway, I mention the xhci boot hang behaviour because I know xhci
 development is active, and I thought this result may be
 interesting/useful for that.

Such long hang generally means that timeouts are occurring.  If you
can compile a kernel with XHCI_DEBUG and UHUB_DEBUG defined and send
me a dmesg, it will be much appreciated.

Martin

Re: ffs and utf8

2014-12-02 Thread Joel Rees

(apologies for the html.)

2014/12/02 9:52 Dmitrij D. Czarkoff czark...@gmail.com:

 Joel Rees said:
  Now, what would you do with this?
 
  ã¸ã§ã¨ã«
 
  Why not decompose it to the following?
 
  ï½¼ï¾ï½®ï½´ï¾

 Because it is not what Unicode normalization is.

Well, it definitely isn't Unicode normalization. And there is a reason, it
isn't, even though there were many who thought the Unicode standard
shouldn't include code points for wide form glyphs.

Let's try one more. I think you have said enough that I can infer that your
preferred normal form is the decomposit form. So, given that your
normalization has resulted in a file named

ã·ãã§ã¨ã«ã®æ

and the necessity to send it back where it came from, how do you know
whether or not it should be restored to

ã¸ã§ã¨ã«ã®æ

before you send it back?

 [...]

--
Joel Rees

Re: Staying -current with cvsup or cvsync

2014-12-02 Thread Stuart Henderson

On 2014-11-28, Jungle Boogie jungleboog...@gmail.com wrote:
 Hello All,

 For the last several updates I've applied to my system, I've used plain CVS: 
 cvs -q up -Pd

 This is pretty slow for some reason, but I understand that's just how CVS 
 works.

I just timed an update of /usr/ports on my laptop at 63 seconds. That's fetching
from a good anoncvs server, with /usr/ports on SSD and mounted like this

/dev/sd1j on /usr/ports type ffs (local, noatime, nodev, nosuid, softdep)

 Does this mean cvssup is no longer used?

Correct, the server side was written in Modula-3 which on OpenBSD has only
ever been ported to i386 (most anoncvs servers are now running amd64) and
it was not widely used, so wasn't worth the maintenance headache and extra
exposure on servers.

 Then I came across cvsync: http://www.openbsd.org/cvsync.html

 Is cvsync preferred now?

CVSup was able to either mirror the full repository, or make a checkout.
The method you were looking at for CVSup was just for making a checkout.
(This was quite widely used by FreeBSD in the past, but in OpenBSD the main
method of users fetching the tree was from anoncvs mirrors).

cvsync is only used for mirroring the full repo. Useful if connectivity
between you and an anoncvs mirror isn't very fast, or if you want to hack
offline and still be able to make diffs etc. Unlike CVSup it cannot do
a direct checkout.

I used to run a local cvsync mirror at home. But then the anoncvs server
I used had some upgrades and got much faster so I now just fetch directly
from there, unless I am going to be travelling and want an up-to-date
local copy of the tree on my laptop.

Upgrade guide 5.5 to 5.6: sysmerge options

Hi there, reading the upgrade-guide 5.5 to 5.6
on http://www.openbsd.org/faq/upgrade56.html I came across an issue with
sysmerge options: The guide advises to run sysmerge like so:sysmerge -s
${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
*tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and runsysmerge
-s etc56.tgz -x xetc56.tgz What I get is the following 
comment:/usr/sbin/sysmerge[612]:
-s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me
(http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
 sysmerge
[-bdp] Question:Is my system outdated or should the FAQ get a review?
Cheers,STEFAN

Re: Upgrade guide 5.5 to 5.6: sysmerge options

On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:

 Hi there, reading the upgrade-guide 5.5 to 5.6
 on http://www.openbsd.org/faq/upgrade56.html I came across an issue with
 sysmerge options: The guide advises to run sysmerge like so:sysmerge -s
 ${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
 *tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and 
 runsysmerge
 -s etc56.tgz -x xetc56.tgz What I get is the following 
 comment:/usr/sbin/sysmerge[612]:
 -s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me
 (http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
  sysmerge
 [-bdp] Question:Is my system outdated or should the FAQ get a review?
 Cheers,STEFAN

Looks like you are running a current sysmerge. Likely you did not
upgrade to 5.6-release, but 5.6-current, using a snapshot.

-Otto

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread Chris Cappuccio

Stan Gammons [sg063...@gmail.com] wrote:
 
 The APU1C works fine for a home network.  The only 2 things I dislike are
 the CPU temperature and the link LED's are off when the Ethernet ports are
 linked at 1 gig. I've complained about the link LED issue on the PC Engines
 support forum, but I guess there's no desire to fix it. Oh well.
 

Call me crazy, but when OpenBSD takes over control of the Realtek chips,
isn't it OpenBSD's responsibility to program them properly, not the BIOS?

In any event, I'm using a redundant pair of APUs with crucial/plextor msata
for DNS, DHCP, NTP, and another pair for FreeRadius with master-master mysql
back-end. I also use one at home and in other low-power environments. They
run a little warm, like everyone says. They are VERY fast compared to the
ALIX.

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread lists

On Tue, Dec 02, 2014 at 07:51:19AM -0800, Chris Cappuccio wrote:
 Stan Gammons [sg063...@gmail.com] wrote:
 Call me crazy, but when OpenBSD takes over control of the Realtek chips,
 isn't it OpenBSD's responsibility to program them properly, not the BIOS?

Wouldn't this generally be controlled by the firmware?

Re: Upgrade guide 5.5 to 5.6: sysmerge options


Am 02.12.2014 16:46 schrieb Otto Moerbeek:

On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:


Hi there, reading the upgrade-guide 5.5 to 5.6
on http://www.openbsd.org/faq/upgrade56.html I came across an issue 
with
sysmerge options: The guide advises to run sysmerge like so:sysmerge 
-s

${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
*tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and 
runsysmerge
-s etc56.tgz -x xetc56.tgz What I get is the following 
comment:/usr/sbin/sysmerge[612]:

-s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me
(http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS 
sysmerge

[-bdp] Question:Is my system outdated or should the FAQ get a review?
Cheers,STEFAN


Looks like you are running a current sysmerge. Likely you did not
upgrade to 5.6-release, but 5.6-current, using a snapshot.

-Otto


Hi Otto,

thanks for the quick reply.

Yes - your assumption is correct, I run 5.6-current. Nevertheless: What 
would the correct usage of sysmerge be as the online-version of 'man(8) 
sysmerge' does not know about the options '-s' and '-x'?


Best,
STEFAN

Re: Upgrade guide 5.5 to 5.6: sysmerge options

2014-12-02 Thread trondd

 What would the correct usage of sysmerge be as the online-version of
 'man(8) sysmerge' does not know about the options '-s' and '-x'?


If they are not valid parameters anymore, did you try it without them?

The *etc.tgz tarballs are not standalone anymore, they are part of base and
exist in a known location as per the man page.

Tim.

Re: Upgrade guide 5.5 to 5.6: sysmerge options

On Tue, Dec 02, 2014 at 05:04:39PM +0100, Stefan Wollny wrote:

 Am 02.12.2014 16:46 schrieb Otto Moerbeek:
 On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:
 
 Hi there, reading the upgrade-guide 5.5 to 5.6
 on http://www.openbsd.org/faq/upgrade56.html I came across an issue with
 sysmerge options: The guide advises to run sysmerge like so:sysmerge -s
 ${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
 *tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and
 runsysmerge
 -s etc56.tgz -x xetc56.tgz What I get is the following
 comment:/usr/sbin/sysmerge[612]:
 -s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me
 (http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
 sysmerge
 [-bdp] Question:Is my system outdated or should the FAQ get a review?
 Cheers,STEFAN
 
 Looks like you are running a current sysmerge. Likely you did not
 upgrade to 5.6-release, but 5.6-current, using a snapshot.
 
  -Otto
 
 Hi Otto,
 
 thanks for the quick reply.
 
 Yes - your assumption is correct, I run 5.6-current. Nevertheless: What
 would the correct usage of sysmerge be as the online-version of 'man(8)
 sysmerge' does not know about the options '-s' and '-x'?
 
 Best,
 STEFAN

Run it without arguments,

-Otto

Re: Upgrade guide 5.5 to 5.6: sysmerge options


Am 02.12.2014 17:15 schrieb Otto Moerbeek:

On Tue, Dec 02, 2014 at 05:04:39PM +0100, Stefan Wollny wrote:


Am 02.12.2014 16:46 schrieb Otto Moerbeek:
On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:

Hi there, reading the upgrade-guide 5.5 to 5.6
on http://www.openbsd.org/faq/upgrade56.html I came across an issue with
sysmerge options: The guide advises to run sysmerge like so:sysmerge -s
${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
*tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and
runsysmerge
-s etc56.tgz -x xetc56.tgz What I get is the following
comment:/usr/sbin/sysmerge[612]:
-s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me
(http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
sysmerge
[-bdp] Question:Is my system outdated or should the FAQ get a review?
Cheers,STEFAN

Looks like you are running a current sysmerge. Likely you did not
upgrade to 5.6-release, but 5.6-current, using a snapshot.

-Otto

Hi Otto,

thanks for the quick reply.

Yes - your assumption is correct, I run 5.6-current. Nevertheless: 
What
would the correct usage of sysmerge be as the online-version of 
'man(8)

sysmerge' does not know about the options '-s' and '-x'?

Best,
STEFAN


Run it without arguments,

-Otto


Thanks - this is how I usually do it but got confused by the upgrade 
guide. There haven't been any change-notices by sysmerge lately so I 
thought I have done s.th. wrong.


I just noticed that the online-version of 'man(8) sysmerge' refers to 
OpenBSD-current - guess this added to my confusion.


Sorry for the noise.

Cheers,
STEFAN

Re: Staying -current with cvsup or cvsync

2014-12-02 Thread Jungle Boogie

Dear Stuart,

From: Stuart Henderson s...@spacehopper.org
Sent:  Tue, 2 Dec 2014 10:40:22 + (UTC)
To: misc@openbsd.org
Subject: Re: Staying -current with cvsup or cvsync

On 2014-11-28, Jungle Boogie jungleboog...@gmail.com wrote:

Hello All,

For the last several updates I've applied to my system, I've used plain CVS:
cvs -q up -Pd

This is pretty slow for some reason, but I understand that's just how CVS works.

I just timed an update of /usr/ports on my laptop at 63 seconds. That's fetching
from a good anoncvs server, with /usr/ports on SSD and mounted like this

/dev/sd1j on /usr/ports type ffs (local, noatime, nodev, nosuid, softdep)

63 seconds is quite impressive! I've got a pata drive with only:
(local,  nodev)

How often do you fetch/rebuild?

I plan on making a low power router (not really looking at the APU devices 
anymore) and in that, I'll use SSD or msata.

Does this mean cvssup is no longer used?

Correct, the server side was written in Modula-3 which on OpenBSD has only
ever been ported to i386 (most anoncvs servers are now running amd64) and
it was not widely used, so wasn't worth the maintenance headache and extra
exposure on servers.

Well the book I referenced is from 2003, when i386 was common and 3.1  3.2 
were out so it's not surprising that technological advancements have been made. ;)

Then I came across cvsync: http://www.openbsd.org/cvsync.html

Is cvsync preferred now?

CVSup was able to either mirror the full repository, or make a checkout.
The method you were looking at for CVSup was just for making a checkout.
(This was quite widely used by FreeBSD in the past, but in OpenBSD the main
method of users fetching the tree was from anoncvs mirrors).

cvsync is only used for mirroring the full repo. Useful if connectivity
between you and an anoncvs mirror isn't very fast, or if you want to hack
offline and still be able to make diffs etc. Unlike CVSup it cannot do
a direct checkout.

I used to run a local cvsync mirror at home. But then the anoncvs server
I used had some upgrades and got much faster so I now just fetch directly
from there, unless I am going to be travelling and want an up-to-date
local copy of the tree on my laptop.

Now that I understand what cvsync is, I don't think it would have saved me any 
time with the updates as the longest time seems like my HDD searching for 
data, not the actual transmit.

--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread Chris Cappuccio

li...@ggp2.com [li...@ggp2.com] wrote:
 On Tue, Dec 02, 2014 at 07:51:19AM -0800, Chris Cappuccio wrote:
  Stan Gammons [sg063...@gmail.com] wrote:
  Call me crazy, but when OpenBSD takes over control of the Realtek chips,
  isn't it OpenBSD's responsibility to program them properly, not the BIOS?
 
 Wouldn't this generally be controlled by the firmware?

Which firmware?

missing packages for SPARC

2014-12-02 Thread Riccardo Mottola


Hi,

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


Is this a problem? or is it deliberate? Sebastian, I know you used to 
stress your SPARCs :)


Thank you,
Riccardo

Re: Time keeping problem

2014-12-02 Thread Michał Koc

On Mon, Dec 01, 2014 at 17:33, MichaÅ Koc wrote:
 Hi All,

 I've got a OpenBSD installation on Microsoft Hyper-V, and there is a
 strange issue related to time.
 Actually the clock seems to be running fine, but all of the sleep
 operations expire 2 times too fast.
 cpu0 at mainbus0: apid 0 (boot processor)
 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
 cpu0: apic clock running at 105MHz
 The clock that determines how long a second is the apic clock, which
 we attempt to measure at boot time. However, sometimes the reading is
 done wrong which usually results in a multple of the actual frequency.
 Actually, it usually results in clocks running at 1/2 or 1/3 speed,
 not double speed. But it's the same problem. Your apic clock is
 apparently really running at 200MHz.

 There was a fix made to the code quite some time ago which resolved
 the issue on real hardware. I haven't seen it since. But Hyper-V is
 obviously different.

 There is no fix or change you can make to change the frequency once
 determined, but maybe if Hyper-V has some setting for optimized clock
 ticks or whatever, you can fiddle with it.



Hi Ted,

thank You for a quick response.
Unfortunately I'm not in position to do any changes in the settings.

But I've set this value manually in lapic_gettick, and the machine seems 
to be running fine for now.

I know that's not a best possible solution :)

Best regards
-- 
MichaÅ Koc

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread Stan Gammons


On 12/02/14 09:51, Chris Cappuccio wrote:

Stan Gammons [sg063...@gmail.com] wrote:

The APU1C works fine for a home network.  The only 2 things I dislike are
the CPU temperature and the link LED's are off when the Ethernet ports are
linked at 1 gig. I've complained about the link LED issue on the PC Engines
support forum, but I guess there's no desire to fix it. Oh well.


Call me crazy, but when OpenBSD takes over control of the Realtek chips,
isn't it OpenBSD's responsibility to program them properly, not the BIOS?



Well, using any version of OpenBSD 5.5 and newer the LEDs work right 
with this NIC.


re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E-VL 
(0x2c80), msi, address 90:2b:34:af:eb:1a

rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 5

With this NIC, which is the one in the APU, the LEDs don't work right.

re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E 
(0x2c00), msi, address 00:0d:b9:33:75:88

rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4

So, the question is why don't the LEDs work right on the NIC in the 
APU?  The NIC in the APU is very similar to the one that the LEDs do 
work right on.


I'm pretty sure the FreeBSD Realtek driver is the same as the OpenBSD 
one, although I haven't tried FreeBSD on an APU.  Or have I tried Linux 
on one.  I guess I could try both on the APU to see if there's any 
difference.



Stan

Squid configuration

2014-12-02 Thread sven falempin

Hello,

I am more or less forced to test Squid.
OpenBSD test.my.domain 5.6 GENERIC.MP#333 amd64

I have two problems:


WARNING! Your cache is running out of filedescriptors


And probably have to read more about ICAP

suspending ICAP service for too many failures



My question is about the fds,
i tried to add

squid:\
:openfiles-cur=4096:\
:tc=daemon:

into login.conf and did not forget to 'push' it

# cap_mkdb /etc/login.conf
# echo $?
0

It looks like it has no effect. Is this the way to go ? have I to change a
limit somewhere else ?

Best regards,
Sven

pftop on konsole

Hi there!

I noticed s.th. strange when running pftop on 'konsole' (KDE4 on
current-amd64):

On the console  I started fluxbox via 'startx' I read the following message:
konsole(11345) OpenBSDProcessInfo::readCurrentDir: sysctl() call \
failed with code 1

This is repeated as long as pftop is running. I guess this specifically
relates to KDE4 as running pftop e.g. in a xterm does not lead to this
messages. Or am I simply lacking some setting?

Anybody with an idea? More details needed?

TIA.

Cheers,
STEFAN


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

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread Darren Tucker

On Fri, Nov 28, 2014 at 6:32 PM, Blaise Hizded bla...@ovh.fr wrote:

 I run the previous generation ALIX 2D13 with OpenBSD 5.6 on it for a
 home firewall with 10MB WAN broadband and 100MB between computers.
 All is fine: low temperature, low consumption, same speed as with a
 basic 100MBB switch.


I spent some time tuning the vr(4) driver on ALIX a while back[1], and in
my experience the throughput maxes out at around 85 Mbit/s of TCP (ie
iperf) traffic through it.  I don't know what the limiting factor is, but
it's not CPU.  My guess is it's the checksum offload hardware in the chips,
in which case doing those in software would be faster at the cost of using
more CPU, but I never tested this theory.

[1] http://undeadly.org/cgi?action=articlesid=20130201054156

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Re: Packet Filter router i368 vs 64bit

2014-12-02 Thread Josh Grosse

On Wed, Dec 03, 2014 at 10:54:14AM +1100, Darren Tucker wrote:
 On Fri, Nov 28, 2014 at 6:32 PM, Blaise Hizded bla...@ovh.fr wrote:
 
  I run the previous generation ALIX 2D13 with OpenBSD 5.6 on it for a
  home firewall with 10MB WAN broadband and 100MB between computers.
  All is fine: low temperature, low consumption, same speed as with a
  basic 100MBB switch.
 
 
 I spent some time tuning the vr(4) driver on ALIX a while back[1], and in
 my experience the throughput maxes out at around 85 Mbit/s of TCP (ie
 iperf) traffic through it.  I don't know what the limiting factor is, but
 it's not CPU.  My guess is it's the checksum offload hardware in the chips,
 in which case doing those in software would be faster at the cost of using
 more CPU, but I never tested this theory.
 
 [1] http://undeadly.org/cgi?action=articlesid=20130201054156

On my Alix 2d13s I have seen peaks of about 230 Mbps as reported by nfsen, 
which is in line with Darren's observed results.  They've been a good fit on 
100 Mbps Ethernet segments.

Re: -current hangs during boot from xhci controller on MacbookAir6,1

2014-12-02 Thread Scott Bonds

I compiled a custom kernel with the options you specified. When I do a
normal boot (xhci mode) using the custom kernel, instead of a hang I get
a panic. The last lines on the screen before the panic instructions are:

scscibus3 at softraid0: 256 targets
panic: root device (4c16713a536188bf) not found
stopped at  Debugger+0x9:   leave

The keyboard does not respond after the panic.

Booting the custom kernel after putting the laptop into ehci mode I'm
able to boot successfully and get a dmesg, though perhaps not the one
you need, since its no longer in xhci mode. :( Here it is:

OpenBSD 5.6-stable (SCOTT.MP) #0: Tue Dec  2 16:55:45 PST 2014
root@foo.localdomain:/usr/src/sys/arch/amd64/compile/SCOTT.MP
RTC BIOS diagnostic error 
ffclock_battery,ROM_cksum,config_unit,memory_size,fixed_disk,invalid_time
real mem = 8511332352 (8117MB)
avail mem = 8275972096 (7892MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (42 entries)
bios0: vendor Apple Inc. version MBA61.88Z.0099.B16.1408291503 date 08/29/2014
bios0: Apple Inc. MacBookAir6,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT MCFG DMAR
acpi0: wakeup devices P0P2(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S3) 
ARPT(S4) RP05(S3) RP06(S3) SPIT(S3) XHC1(S3) ADP1(S3) LID0(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.21 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM
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 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.01 MHz
cpu2: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 1600.01 MHz
cpu3: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-155
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 5 (RP05)
acpiprt6 at acpi0: bus 4 (RP06)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpibat0 at acpi0: BAT0 model 3545797981023400290 type 3545797981528607052 
oem 3545797981528608836
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD01
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 2301, 2300, 2200, 2100, 2000, 1900, 
1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800, 759 MHz
memory map conflict 0xe00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xffe1/0x3
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 4G Host rev 0x09
vga1 at pci0 dev 2 function 0 Intel HD Graphics 5000 rev 0x09
intagp at vga1 not configured

Re: Squid configuration

2014-12-02 Thread Einfach Jemand

Hi,

Am 02.12.2014 22:46, schrieb sven falempin:
 Hello,
 
 I am more or less forced to test Squid.
 OpenBSD test.my.domain 5.6 GENERIC.MP#333 amd64
 
 I have two problems:
 
 
 WARNING! Your cache is running out of filedescriptors

 
 And probably have to read more about ICAP
 
 suspending ICAP service for too many failures

 
 
 My question is about the fds,
 i tried to add
 
 squid:\
 :openfiles-cur=4096:\
 :tc=daemon:
 
 into login.conf and did not forget to 'push' it
 
 # cap_mkdb /etc/login.conf
 # echo $?
 0

Hmm, I checked on one of my boxen and there /etc/passwd has

_squid
^! Note the underline.

as account for this package, so you probably want

_squid:\
:openfiles-cur=4096:\
:tc=daemon:

in /etc/login.conf

 It looks like it has no effect. Is this the way to go ? have I to change a
 limit somewhere else ?
 
 Best regards,
 Sven
 

HTH
rru

Re: Squid configuration

2014-12-02 Thread Libertas

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/02/2014 08:49 PM, Einfach Jemand wrote:
 Hmm, I checked on one of my boxen and there /etc/passwd has
 
 _squid ^! Note the underline.
 
 as account for this package, so you probably want
 
 _squid:\

I'm pretty sure it's supposed to be 'squid', as the daemon name is
supposed to be used. The example given in 5.6's default
/etc/login.conf uses 'bgpd', despite the fact that bgpd runs as the
user '_bgpd'.

Sven, make sure the syntax is identical to that of the bgpd example.
It'd probably be easiest just to duplicate it and replace what you
need to. Things like using spaces rather than tabs can easily cause
silent errors.
iQIcBAEBCAAGBQJUfm9dAAoJELxHvGCsI27Nv2wP/j71JWZX1sHkYmIZeIm9hRrD
YwZwazYILx/Bu4U3JDQLGWYebeu+d3cr05hnd/v3Z+FvXqb3TIwNTG+UL0QgHIOK
PGPTXzvih2uJ9RKXG5VUTvtNSqzl6a9+trs4B82A45tEu5uHjYo6YX53a0K+QJBH
uGqys8g5ggHzixqOETccZIIKBxUAq5esyU6UIXQiykvt/3X+ikYNJeH2QDf0Tov/
sYAzQObCuw2CvdYJajK6iftl6rJt+Zpz7hIMVbr/mTi/1ldH+l68IoBSYw1n7EnT
Vq9jxVD+6oY25CIc48Tcb9UcJwsRcywc20F2+rRKvYaZjaUzPNtkCZ8TKFaDaEHe
M9cwqhp+ckxYxzs4BhxqtWNKprOQJ3W3tphGc8pdh+SSdXHdy67mZun2GYN5qWfu
WrqrMRKXE+GlXgtnvOAsUcJ7FUN7S052R0K6+/off96RK+/HMpFsXIgWxKGohO5V
nFUu6g+/gMOye1svmJDmg5jUr+DjqnpqPEadHN4yxAFaKXu05lbG7X2XwJFe4N2P
kCJN8M4PzLxxgL5XlQoRLQ4A5FrxU29h4ST2b24ZbrDNLTncrsEUo/fs5A9YC0xl
jbjiLSUsg6ZixrF+4jnBrdinUIwjekW61es5mnoRhuG0qN2+YZrwjkhaiUTflENL
elmLg8e6dF3O9jEZxImi
=07gk
-END PGP SIGNATURE-

Re: Squid configuration

2014-12-02 Thread Steve Shockley


On 12/2/2014 4:46 PM, sven falempin wrote:


WARNING! Your cache is running out of filedescriptors




I have Squid on 5.4 amd64, which may or may not be the same.


And probably have to read more about ICAP

suspending ICAP service for too many failures




Do you need ICAP?  I think it's primarily for web filtering or virus/DLP 
scans.




My question is about the fds,
i tried to add

squid:\
 :openfiles-cur=4096:\
 :tc=daemon:

into login.conf


Is there a reason you chose a different config than suggested in the 
port README?


squid:\
:datasize=1500M:\
:openfiles=4096:\
:tc=daemon:

Does setting openfiles-cur also increase openfiles-max if it's not 
specified?  Based on http://marc.info/?l=openbsd-miscm=140698839413081, 
it appears not.

Re: Squid configuration

2014-12-02 Thread Steve Shockley


On 12/2/2014 8:49 PM, Einfach Jemand wrote:


Hmm, I checked on one of my boxen and there /etc/passwd has

_squid
^! Note the underline.

as account for this package, so you probably want


According to the package README:

When started by rc.d(8) (i.e. via pkg_scripts in rc.conf.local or from
${RCDIR}/squid start) the appropriately-named login class is used
automatically.

So, the underline shouldn't be necessary.

Re: Squid configuration

2014-12-02 Thread Einfach Jemand

Am 03.12.2014 03:55, schrieb Steve Shockley:
 On 12/2/2014 8:49 PM, Einfach Jemand wrote:
 
 Hmm, I checked on one of my boxen and there /etc/passwd has

 _squid
 ^! Note the underline.

 as account for this package, so you probably want
 
 According to the package README:
 
 When started by rc.d(8) (i.e. via pkg_scripts in rc.conf.local or from
 ${RCDIR}/squid start) the appropriately-named login class is used
 automatically.
 
 So, the underline shouldn't be necessary.

Yes, I have rechecked and that is correct, no underline/underscore needed.

Directing someone looking for a solution into the wrong direction is no
good, please accept my apologies.

Bye,
rru

Re: PF rules loading bug on OpenBSD 5.6

2014-12-02 Thread Cosmo Wu

Could anyone run into these problems? thanks!

On 14.11.2014 14:50,
Cosmo Wu wrote:
 Hi Misc ,
 
 
 There is a no-syntax-error pf config
file ( such a pf.conf.test ) ,
 
 but another queue named differently
is created on the same interface.
 
 and it parsed correctly using
command  pfctl -nf /etc/pf.conf.test
 
 when I loaded it from the
command  pfctl -f /etc/pf.conf.test 
 
 it grumbled:
 
 pfctl:
DIOCXCOMMIT: Invalid argument
 
 
 so I corrected the pf config file
, even a simple line  pass  in it .
 
 It also grumble  pfctl:
DIOCXCOMMIT: Invalid argument  ,
 
 the config file was loaded when
using  pfctl -sr  which won't
 prompt the warning,
 
 but it
prompted the same warning when using command  pfctl -s queue
 -v -v 
,
 
 and it won't show any queue info any more.
 
 It can't get
right when using  pfctl -Fa; pfctl -d  to reload.
 
 I have to
reboot the OpenBSD .
 
 So how to fix these problems? thanks for
reading!

-- 

Best Regards,

Cosmo Wu

Re: Upgrade guide 5.5 to 5.6: sysmerge options


On 02.12.2014 17:45, Stefan Wollny wrote:

Am 02.12.2014 17:15 schrieb Otto Moerbeek:

On Tue, Dec 02, 2014 at 05:04:39PM +0100, Stefan Wollny wrote:


Am 02.12.2014 16:46 schrieb Otto Moerbeek:
On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:

Hi there, reading the upgrade-guide 5.5 to 5.6
on http://www.openbsd.org/faq/upgrade56.html I came across an 
issue with
sysmerge options: The guide advises to run sysmerge like 
so:sysmerge -s

${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
*tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there 
and

runsysmerge
-s etc56.tgz -x xetc56.tgz What I get is the following
comment:/usr/sbin/sysmerge[612]:
-s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me

(http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
sysmerge
[-bdp] Question:Is my system outdated or should the FAQ get a 
review?

Cheers,STEFAN

Looks like you are running a current sysmerge. Likely you did not
upgrade to 5.6-release, but 5.6-current, using a snapshot.

-Otto
Hi Otto,
thanks for the quick reply.
Yes - your assumption is correct, I run 5.6-current. Nevertheless: 
What
would the correct usage of sysmerge be as the online-version of 
'man(8)

sysmerge' does not know about the options '-s' and '-x'?
Best,
STEFAN

Run it without arguments,

-Otto


Thanks - this is how I usually do it but got confused by the upgrade
guide. There haven't been any change-notices by sysmerge lately so I
thought I have done s.th. wrong.


Upgrade guide is meant for upgrade from release/stable to next 
relase/stable http://www.openbsd.org/faq/upgrade56.html
As you upgraded to current from previous release/stable you need to put 
in work this one as well http://www.openbsd.org/faq/current.html





I just noticed that the online-version of 'man(8) sysmerge' refers to
OpenBSD-current - guess this added to my confusion.



But seems like in current.html is already note about sysmerge change 
missing (not sure how often it's updated and how much history is kept)
You can see details eg. here 
http://marc.info/?l=openbsd-cvsm=140924782007306w=2


http://www.openbsd.org/cgi-bin/man.cgi points by default to current as 
you can see so you will get this:


http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge

but you can switch to last release and you get this:

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-5.6/man8/sysmerge.8?query=sysmergemanpath=OpenBSD-5.6


Sorry for the noise.

Cheers,
STEFAN

Re: Upgrade guide 5.5 to 5.6: sysmerge options

On Wed, Dec 03, 2014 at 07:54:00AM +0100, bodie wrote:

On 02.12.2014 17:45, Stefan Wollny wrote:
Am 02.12.2014 17:15 schrieb Otto Moerbeek:
On Tue, Dec 02, 2014 at 05:04:39PM +0100, Stefan Wollny wrote:

Am 02.12.2014 16:46 schrieb Otto Moerbeek:
On Tue, Dec 02, 2014 at 04:39:11PM +0100, Stefan Wollny wrote:

Hi there, reading the upgrade-guide 5.5 to 5.6
on http://www.openbsd.org/faq/upgrade56.html I came across an issue
with
sysmerge options: The guide advises to run sysmerge like so:sysmerge
-s
${RELEASEPATH}/etc56.tgz -x ${RELEASEPATH}/xetc56.tgz I have the
*tgz-files in the folder ~/Downloads/amd64/. I have cd'ed there and
runsysmerge
-s etc56.tgz -x xetc56.tgz What I get is the following
comment:/usr/sbin/sysmerge[612]:
-s: unknown optionusage: sysmerge [-bdp] man sysmerge tells me

(http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge)SYNOPSIS
sysmerge
[-bdp] Question:Is my system outdated or should the FAQ get a
review?
Cheers,STEFAN

Looks like you are running a current sysmerge. Likely you did not
upgrade to 5.6-release, but 5.6-current, using a snapshot.

-Otto
Hi Otto,
thanks for the quick reply.
Yes - your assumption is correct, I run 5.6-current. Nevertheless:
What
would the correct usage of sysmerge be as the online-version of
'man(8)
sysmerge' does not know about the options '-s' and '-x'?
Best,
STEFAN
Run it without arguments,

-Otto

Thanks - this is how I usually do it but got confused by the upgrade
guide. There haven't been any change-notices by sysmerge lately so I
thought I have done s.th. wrong.

Upgrade guide is meant for upgrade from release/stable to next relase/stable
http://www.openbsd.org/faq/upgrade56.html
As you upgraded to current from previous release/stable you need to put in
work this one as well http://www.openbsd.org/faq/current.html

I just noticed that the online-version of 'man(8) sysmerge' refers to
OpenBSD-current - guess this added to my confusion.

But seems like in current.html is already note about sysmerge change missing
(not sure how often it's updated and how much history is kept)
You can see details eg. here
http://marc.info/?l=openbsd-cvsm=140924782007306w=2

http://www.openbsd.org/cgi-bin/man.cgi points by default to current as you
can see so you will get this:

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/sysmerge.8?query=sysmerge

but you can switch to last release and you get this:

http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-5.6/man8/sysmerge.8?query=sysmergemanpath=OpenBSD-5.6

Sorry for the noise.

Cheers,
STEFAN

Current.html does not described *every* change. It was originally
meant as guide to cross bumps you might encounter building ths system.

The man pages for current en 5.6 properly reflect the change. I think
we can expect people following current to read the man pages when they
see a tool returning usage. Relatively speaking (especially compared
to other projects) a lot of time is spent on man pages. They are worth
a read.

-Otto

Re: pftop on konsole


On 02.12.2014 22:54, Stefan Wollny wrote:

Hi there!

I noticed s.th. strange when running pftop on 'konsole' (KDE4 on
current-amd64):

On the console  I started fluxbox via 'startx' I read the following 
message:

konsole(11345) OpenBSDProcessInfo::readCurrentDir: sysctl() call \
failed with code 1

This is repeated as long as pftop is running. I guess this 
specifically
relates to KDE4 as running pftop e.g. in a xterm does not lead to 
this

messages. Or am I simply lacking some setting?

Anybody with an idea? More details needed?



Hi,

here I'm not sure at all as I'm not a programmer so hopefully someone 
will provide more insight, but looking here 
https://projects.kde.org/projects/kde/applications/konsole/repository/revisions/master/entry/src/ProcessInfo.cpp 
on line 844 which relates to your error message it tries to get info 
about KERN_PROC_CWD and aPID where aPID is not defined at all in 'man 3 
sysctl' and KERN_PROC_CWD is mentioned there, but as 'not applicable' 
[based on paragraph in man page preceding that table I would say that 
this parameter is not used/available in OpenBSD]. Because of that sysctl 
is not able to get needed info and result in that fail code.



Or I may be totally out of course :-) Anyway best bet is to contact 
directly porter/maintainer of KDE? openbsd-...@googlegroups.com or 
ports@ list here in OpenBSD project.





TIA.

Cheers,
STEFAN


OpenBSD 5.6-current (GENERIC.MP) #633: Mon Dec  1 06:54:44 MST 2014

dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

real mem = 3203203072 (3054MB)
avail mem = 3114151936 (2969MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version 79ETC9WW (2.09 ) date 12/22/2006
bios0: LENOVO 2007VG2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4)
EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) 
USB7(S3)

HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.65 MHz
cpu0:

FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.33 MHz
cpu1:

FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 92P1139 serial  2887 type LION oem
Panasonic
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03
ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility X1300 
M52-64

rev 0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: 
msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using 
Analog

Devices AD1981HD
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 Intel 82573L rev 0x00: msi, address
00:15:58:81:15:fb
ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: msi
pci3 at ppb2 bus 3
wpi0 at pci3 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02:
msi, MoW2, address 00:19:d2:85:6f:4d
ppb3 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: msi
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02:

Re: pftop on konsole


On 03.12.2014 08:11, bodie wrote:

On 02.12.2014 22:54, Stefan Wollny wrote:

Hi there!

I noticed s.th. strange when running pftop on 'konsole' (KDE4 on
current-amd64):

On the console  I started fluxbox via 'startx' I read the following 
message:

konsole(11345) OpenBSDProcessInfo::readCurrentDir: sysctl() call \
failed with code 1

This is repeated as long as pftop is running. I guess this 
specifically
relates to KDE4 as running pftop e.g. in a xterm does not lead to 
this

messages. Or am I simply lacking some setting?

Anybody with an idea? More details needed?



Hi,

here I'm not sure at all as I'm not a programmer so hopefully someone
will provide more insight, but looking here

https://projects.kde.org/projects/kde/applications/konsole/repository/revisions/master/entry/src/ProcessInfo.cpp
on line 844 which relates to your error message it tries to get info
about KERN_PROC_CWD and aPID where aPID is not defined at all in 'man
3 sysctl' and KERN_PROC_CWD is mentioned there, but as 'not
applicable' [based on paragraph in man page preceding that table I
would say that this parameter is not used/available in OpenBSD].
Because of that sysctl is not able to get needed info and result in
that fail code.



of course that I misread something aPid is mentioned and defined on 
start of ProcessInfo.cpp and is simply PID of process so supposed to be 
available already at time of line 844. Anyway you can try to use 
ktrace/kdump to see if it's really getting all needed parameters and 
what are they.





Or I may be totally out of course :-) Anyway best bet is to contact
directly porter/maintainer of KDE? openbsd-...@googlegroups.com or
ports@ list here in OpenBSD project.




TIA.

Cheers,
STEFAN


OpenBSD 5.6-current (GENERIC.MP) #633: Mon Dec  1 06:54:44 MST 2014

dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

real mem = 3203203072 (3054MB)
avail mem = 3114151936 (2969MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version 79ETC9WW (2.09 ) date 12/22/2006
bios0: LENOVO 2007VG2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT
SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4)
EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) 
USB7(S3)

HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.65 MHz
cpu0:

FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.33 MHz
cpu1:

FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 92P1139 serial  2887 type LION oem
Panasonic
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: GDCK not docked (0)
cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 
MHz

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03
ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility X1300 
M52-64

rev 0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: 
msi
azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using 
Analog

Devices AD1981HD
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 Intel 82573L rev 0x00: msi, address
00:15:58:81:15:fb
ppb2

Re: Packet Filter router i368 vs 64bit