assigning ipv6 addresses to interfaces

2016-01-30 Thread LÉVAI Dániel
Hi! My ISP recently enabled ipv6 on their network, and started sending router advertisements (offering a /64 prefix) on their pppoe end. So now I have an autoconf'd v6 address on my pppoe0 device (yay!), and I wish to set my in-home devices a v6 address each. The router that has the pppoe device

Re: xz: (stdin): Cannot allocate memory

2016-01-30 Thread Lampshade
I figured out that my default is: ulimit -d 1572864 echo "1572864/1024" | bc 1536 Value, which lets me compress using this setting is between 1682864 and 1672864 kilobytes. I have also discovered command line option for xz --memlimit= Now my command looks that: cat archive.tar | xz -zf

Re: xz: (stdin): Cannot allocate memory

2016-01-30 Thread Lampshade
This xz command worked in past so I think something must have been changed in past. Indeed, this command worked when I had 4G of DDR3@1333Mhz RAM. Now I have 6GB DDR3 on the same laptop so I have even more. I will look at ulimit -d this evening. I didn't changed them manually, so they must have

xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command

2016-01-30 Thread Lô Baret
Hello, I recently installed OpenBSD 5.8 amd64 for the first time (default install options all the way) on my laptop (Thinkpad X200s) and everything went well until I tried to startx another window manager than the default fvwm. startx launches fvwm correctly but whenever I try with another window

Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command

2016-01-30 Thread Peter N. M. Hansteen
On 01/30/16 17:48, Lô Baret wrote: Hello, I recently installed OpenBSD 5.8 amd64 for the first time (default install options all the way) on my laptop (Thinkpad X200s) and everything went well until I tried to startx another window manager than the default fvwm. startx launches fvwm correctly

Re: xauth: (argv):1: bad display name "BadSystemDetected.my.domain:0" in "remove" command

2016-01-30 Thread Lô Baret
Thanks for the answer, i've already looked for solutions in the mailing list archive and on numerous forums. Now I can successfully launch i3 or awesome with startx /usr/local/bin/mywm but there is still the same xauth error: bad display name. $DISPLAY command returns nothing 2016-01-30 18:09

Re: "Available disks are: none" on Sony Vaio SVZ13115GGXI

2016-01-30 Thread Christian Weisgerber
On 2016-01-30, Paul de Weerd wrote: > { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_AHCI, > NULL, ahci_intel_attach }, > + { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801HBM_RAID, > + NULL, ahci_intel_attach }, So

Re: xz: (stdin): Cannot allocate memory

2016-01-30 Thread Brian Conway
Have you read the xz man page, specifically on memory requirements? 9-extreme is probably not what you want - it's fairly insane/placebo. Full dmesg with memory information is needed beyond that. Brian Conway On Jan 30, 2016 7:18 AM, "Lampshade" wrote: > Hello > I have

Re: xz: (stdin): Cannot allocate memory

2016-01-30 Thread Christian Weisgerber
Lampshade: > I have following error: > cat archive.tar | xz -zf --format=xz -9e --threads=2 - > archive.tar.xz > xz: (stdin): Cannot allocate memory You are using the most extreme compression setting, which requires about 674 MB per thread according to the xz(1) man page. This causes you to

Re: "Available disks are: none" on Sony Vaio SVZ13115GGXI

2016-01-30 Thread Paul de Weerd
On Sat, Jan 30, 2016 at 12:04:10PM +1100, Jonathan Gray wrote: | They are the same, the string in pcidevs was wrong. I just commited | a change to fix it. Ah, right. Thanks Jonathan! Ben, you may still try that patch then. Index: ahci_pci.c

Re: I have a program I wish to submit for the base

2016-01-30 Thread lists
Fri, 29 Jan 2016 16:35:12 -0600 Luke Small > I have secure architectures with openbsd. Looks like public learning from a viewer's point, thanks for sharing your work so far. This is the right thing to show progress and ask reviews. Please try to very carefully listen what

xz: (stdin): Cannot allocate memory

2016-01-30 Thread Lampshade
Hello I have this OS with packages as of yesterday (Jan 29): kern.version=OpenBSD 5.9-beta (GENERIC.MP) #1865: Thu Jan 28 20:18:15 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP and also tested on with packages around Jan 17: kern.version=OpenBSD 5.9-beta

Re: Trying to newfs an old 128 compactflash

2016-01-30 Thread Edgar Pettijohn
On 01/30/16 18:15, Monah Baki wrote: Hi all, Trying to newfs an old 128MB flashcard on my OpenBSD 5.7, so I can install OpenBSd on it to run on a Soekris. # dmesg | grep sd0 sd0 at scsibus5 targ 1 lun 0: SCSI4 0/direct removable serial.0bda0309201209010309 sd0:

Re: assigning ipv6 addresses to interfaces

2016-01-30 Thread Stuart Henderson
On 2016-01-30, LÉVAI Dániel wrote: > Hi! > > My ISP recently enabled ipv6 on their network, and started sending > router advertisements (offering a /64 prefix) on their pppoe end. So now > I have an autoconf'd v6 address on my pppoe0 device (yay!), and I wish > to set my in-home

Lanp equivalent web server working on OpenBSD no Apache

2016-01-30 Thread bruce
I've been working on this for several weeks now. Results with instructions can be seen here: http://tonyevil.zapto.org/serendipity/ Any feedback welcome. httpd is too new for this to be well documented, so here is my small contribution.

Re: xz: (stdin): Cannot allocate memory

2016-01-30 Thread Christian Weisgerber
On 2016-01-30, Lampshade wrote: > xz: Adjusted the number of threads from 2 to 1 to not exceed the memory > usage limit of 1600 MiB > > 1600 is clearly larger than 674*2=1348 A closer reading of the man page reveals that memory consumption is even higher in multi-threaded

Re: Trying to newfs an old 128 compactflash

2016-01-30 Thread Monah Baki
# newfs /dev/rsd0a /dev/rsd0a: 123.0MB in 251840 sectors of 512 bytes 4 cylinder groups of 30.74MB, 3935 blocks, 7872 inodes each newfs: wtfs: write error on block 16: Input/output error Same error. I never seen this error before and I've used newfs before. On Sat, Jan 30, 2016 at 8:10 PM, Edgar

Trying to newfs an old 128 compactflash

2016-01-30 Thread Monah Baki
Hi all, Trying to newfs an old 128MB flashcard on my OpenBSD 5.7, so I can install OpenBSd on it to run on a Soekris. # dmesg | grep sd0 sd0 at scsibus5 targ 1 lun 0: SCSI4 0/direct removable serial.0bda0309201209010309 sd0: 123MB, 512 bytes/sector, 251904 sectors #

style

2016-01-30 Thread Chris Bennett
I found a couple of small things a little unclear in style manual page. For example: int lflag int *rflag int sflag int from_remote char**blist int *blist_size int blist_addrs char***boof or with spaces int lflag int *rflag int sflag int from_remote char

Re: 5.8 IKEv2 with OSX 10.11.3

2016-01-30 Thread Dot Yet
Forgot to mention that I know the problem is here: ca_x509_subjectaltname: FQDN/server.obsd57.com ca_x509_subjectaltname_cmp: FQDN/server.obsd57.com mismatched ca_validate_cert: /C=CA/ST=Ontario/L=Toronto/O=stark/OU=ITOPS/CN=client-number-1/emailAddress= ad...@obsd57.com invalid subjectAltName

Re: style

2016-01-30 Thread Michael McConville
Chris Bennett wrote: > Should it be done like this? > > int lflag > int*rflag > int sflag > int from_remote > char **blist > int*blist_size > int blist_addrs > char ***boof Close, but you only use spaces there. They usually start with tabs and then align with spaces,

Re: style

2016-01-30 Thread Michael McConville
Chris Bennett wrote: > > This has the downside that if you add another level of indentation, you > > either have to break the alignment or change every line. > > No, that's definitely not OK at all. I sure wouldn't want to review > diff's with code changes and full of style changes also. > > >

5.8 IKEv2 with OSX 10.11.3

2016-01-30 Thread Dot Yet
Hello, I am trying to setup IKEv2 roadwarrior based VPN. I've the client functional in Windows 7 using the native client. I am trying to get the same functional on OSX, but facing problems. The authentication is being done using certificates. I used ikectl to generate, CA, server's certificate

Re: style

2016-01-30 Thread Chris Bennett
On Sat, Jan 30, 2016 at 09:03:26PM -0500, Michael McConville wrote: > Chris Bennett wrote: > > Should it be done like this? > > > > int lflag > > int*rflag > > int sflag > > int from_remote > > char **blist > > int*blist_size > > int blist_addrs > > char ***boof > >