l2tp client

I’ve just started a job where I will be working from home a bunch, so I would like to configure my home router as an ipsec/l2tp client and to push the routes from my work network to all computers on my home network. i.e. a site-to-site VPN. I have found a bunch of documentation for configuring

6.2 starts nsd before slaacd binds ipv6 address

Hello all - I don't feel this warrants a bug report, but nevertheless feel that this behavior is inconsistent with the way dhclient works. I have a vultr server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd from kernel code in 6.1 is what has broken my nsd config (it fails to sta

Re: gtar: ambiguous package

On 2017-10-09, "Todd C. Miller" wrote: >> a 0: >> 1: gtar-1.28p1 >> 2: gtar-1.28p1-static > > Packages with the -static suffix are statically linked and do not > depend on shared libraries. This means that the binary is not > affected by changes in the shared libraries, wh

Re: Tar and bzip2 maximum compression

Hi Philippe, Philippe Meunier wrote on Mon, Oct 09, 2017 at 08:03:12AM -0400: > leo_...@volny.cz wrote: >> % tar cvvf - > On a related note, it would be nice if tar(1)'s man page indicated that the > -v option can be specified more than once to get extra information. Until > seeing this discuss

Re: gtar: ambiguous package

We still ship a few packages with a static flavor, for the paranoid who wants a version that will work even if they manage to fuck up most of everything else on their system. I'll admit I find fewer and fewer valid use cases to these, as opposed to rebooting on bsd.rd and fixing things another way

Re: gtar: ambiguous package

On Mon, 09 Oct 2017 17:24:53 +0200, Max Power wrote: > Hi guys, and wishes for the new release, Thank You Theo. > > Installing gtar ask me: > Ambiguos: choose package for gtar > a 0: > 1: gtar-1.28p1 > 2: gtar-1.28p1-static > Your choice: > > Ok, but differece between 'nor

gtar: ambiguous package

Hi guys, and wishes for the new release, Thank You Theo. Installing gtar ask me: Ambiguos: choose package for gtar a 0: 1: gtar-1.28p1 2: gtar-1.28p1-static Your choice: Ok, but differece between 'normal' and 'static'...? Thanks.

Re: Is there git-flow-completion for ksh?

> If you love bash and its features, then it is better to use bash than to > try that ksh will be like bash :-/ I hate when BASH completion hides files for me based on context, eg. tar -tvf /dir/dir/file_without_good_suffix won't work. j.

Re: pkg_add ignores -m

On Mon, Oct 09, 2017 at 11:53:31AM +, Luke Small wrote: > Using the -m flag it still gets warnings from pulseaudio and redis that I > didn't use the -m flag The warning about not using `-m' actually comes from useradd. It is just telling you that useradd will not create a new home directory fo

Re: Tar and bzip2 maximum compression

leo_...@volny.cz wrote: >% tar cvvf - On a related note, it would be nice if tar(1)'s man page indicated that the -v option can be specified more than once to get extra information. Until seeing this discussion thread I had never realized this was possible. Philippe

pkg_add ignores -m

Using the -m flag it still gets warnings from pulseaudio and redis that I didn't use the -m flag

Re: Is there git-flow-completion for ksh?

On Mon, Oct 09, 2017 at 05:33:17PM +0800, Nan Xiao wrote: > Hi misc@, > > I know there is git-flow-completion for bash. For default ksh on OpenBSD, > is there any out-of-box git-flow-completion? I try to google, but can't > find it. If you know the completition for bash then you can build a simil

Re: tar: file is too long for ustar

I think the limit is 8GB, actually. On Mon, Oct 9, 2017 at 1:43 PM, Marc Peters wrote: > On Mon, Oct 09, 2017 at 10:23:08AM +, Max Power wrote: >> Hi guys. >> OpenBSD never ceases to amaze me...!! >> >> Solved the problem about maximum compression with bzip2 by tar, there's >> another... >>

Re: tar: file is too long for ustar

On Mon, Oct 09, 2017 at 10:23:08AM +, Max Power wrote: > Hi guys. > OpenBSD never ceases to amaze me...!! > > Solved the problem about maximum compression with bzip2 by tar, there's > another... > while tar run [tar cvvf - directory | bzip2 -9 -v > directory.tbz2], at a > certain point, retu

tar: file is too long for ustar

Hi guys. OpenBSD never ceases to amaze me...!! Solved the problem about maximum compression with bzip2 by tar, there's another... while tar run [tar cvvf - directory | bzip2 -9 -v > directory.tbz2], at a certain point, return: tar: file is too long for ustar The file that creates the proble

Re: Is there git-flow-completion for ksh?

Hi, Nan Xiao wrote on Mon, Oct 09, 2017 at 05:33:17PM +0800: > I know there is git-flow-completion for bash. > For default ksh on OpenBSD, is there any out-of-box > git-flow-completion? Hell no. No plugins in the shell, please. You want a shell that you can trust, right? If you want an environ

Is there git-flow-completion for ksh?

Hi misc@, I know there is git-flow-completion for bash. For default ksh on OpenBSD, is there any out-of-box git-flow-completion? I try to google, but can't find it. Thanks very much in advance! Best Regards Nan Xiao

Solved: Tar and bzip2 maximum compression

Thank You leo_...@volny.cz!

RE: Tar and bzip2 maximum compression

Hi, > Hi guys, > How can I get the maximum compression from bzip2 by tar? > > I try this but not work [although with linux it works]: > tar cvv file_to_compress | pbzip2 -9 -v > compressed.tbz2 > return--> tar: Failed open to write on /dev/rst0: Device not configured > I believe the ancient defau

RE: Tar and bzip2 maximum compression

I wrote: > > I believe the ancient default for tar(1) is to try to open the 0th > st(1) device in raw mode, that's what you're seeting. Try: grah... that's st(4), of course. --schaafuit.

Tar and bzip2 maximum compression

Hi guys, How can I get the maximum compression from bzip2 by tar? I try this but not work [although with linux it works]: tar cvv file_to_compress | pbzip2 -9 -v > compressed.tbz2 return--> tar: Failed open to write on /dev/rst0: Device not configured Can anyone give me some tips? Thanks.