Re: installer amd64 'Get/Verify bsd' -> 'Illegal instruction' - shuttle ds47d

2016-01-28 Thread Marcus MERIGHI
sisnk...@gmail.com (Stefan Kempf), 2016.01.28 (Thu) 20:57 (CET): > Marcus MERIGHI wrote: > > sisnk...@gmail.com (Stefan Kempf), 2016.01.28 (Thu) 06:48 (CET): > > > Stuart Henderson wrote: > > > > On 2016/01/27 20:10, Stefan Kempf wrote: > > > > > So what I suspect to happen is that: > > > > > - us

Re: installer amd64 'Get/Verify bsd' -> 'Illegal instruction' - shuttle ds47d

2016-01-28 Thread Stefan Kempf
Marcus MERIGHI wrote: > sisnk...@gmail.com (Stefan Kempf), 2016.01.28 (Thu) 06:48 (CET): > > Stuart Henderson wrote: > > > On 2016/01/27 20:10, Stefan Kempf wrote: > > > > So what I suspect to happen is that: > > > > - userland does a syscall > > > > - something goes wrong in the kernel, causing i

Re: Wrong documentation of chmod(2) wrt. S_ISVTX on non-directories

2016-01-28 Thread Benjamin Baier
On Thu, 28 Jan 2016 08:22:16 + Jason McIntyre wrote: > On Wed, Jan 27, 2016 at 08:24:09PM +0100, f...@fuz.su wrote: > > The manual page chmod(2) states about the chmod() system call: > > > > If mode ISVTX (the sticky bit) is set on a file, it is ignored. > > > > However, attempting to s

[no subject]

2016-01-28 Thread herminio . hernandezjr
>Synopsis: >Category: >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC) #1170: Sun Aug 16 02:26:00 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC Architecture: OpenBSD.amd64

Re: doas(1) throws a syntax error on a valid doas.conf

2016-01-28 Thread bian
I did, but must have made some mistake when doing so. Trying now it works as expected. Embarrassing. I'll be more careful. Thanks /birger On 2016-01-28 16:38, Nicholas Marriott wrote: Did you try this? permit keepenv { PKG_PATH ENV PS1 SSH_AUTH_SOCK } "as" permit "as" as root cmd /sbin/halt

Re: doas(1) throws a syntax error on a valid doas.conf

2016-01-28 Thread Nicholas Marriott
Did you try this? permit keepenv { PKG_PATH ENV PS1 SSH_AUTH_SOCK } "as" permit "as" as root cmd /sbin/halt On Thu, Jan 28, 2016 at 03:55:12PM +0100, bian wrote: > doas(1) throws a syntax error on what should be a valid doas.conf. There are > two users on this system -- as and aas. The examples

Re: doas(1) throws a syntax error on a valid doas.conf

2016-01-28 Thread Bryan Steele
On Thu, Jan 28, 2016 at 03:55:12PM +0100, bian wrote: > doas(1) throws a syntax error on what should be a valid doas.conf. There are > two users on this system -- as and aas. The examples below shows two valid > doas.conf with the respective output after running the command as the logged > in user.

doas(1) throws a syntax error on a valid doas.conf

2016-01-28 Thread bian
doas(1) throws a syntax error on what should be a valid doas.conf. There are two users on this system -- as and aas. The examples below shows two valid doas.conf with the respective output after running the command as the logged in user. The documentation doesn't indicate how to get around the

Re: cannot connect to mirrors

2016-01-28 Thread Herminio Hernandez, Jr.
Yup the issue was in my pf rules. I created a table and forgot to mention it in the corresponding rule. Once I did and reloaded pf.conf I was good to go. I should have caught that. Thanks On Thu, Jan 28, 2016 at 2:37 AM, Stuart Henderson wrote: > On 2016/01/27 22:27, Herminio Hernandez, Jr. wro

Re: cannot connect to mirrors

2016-01-28 Thread Stuart Henderson
On 2016/01/27 22:27, Herminio Hernandez, Jr. wrote: > I cannot install packages using pkg_add as root. I am getting a no > route to host error. However I can ping the mirror so I know I have ip > connectivity. I tried using curl to get a package from the mirror and > that failed as well. Below are

Re: installer amd64 'Get/Verify bsd' -> 'Illegal instruction' - shuttle ds47d

2016-01-28 Thread Marcus MERIGHI
sisnk...@gmail.com (Stefan Kempf), 2016.01.28 (Thu) 06:48 (CET): > Stuart Henderson wrote: > > On 2016/01/27 20:10, Stefan Kempf wrote: > > > So what I suspect to happen is that: > > > - userland does a syscall > > > - something goes wrong in the kernel, causing it to call > > > sigexit(SIGILL),

Re: Wrong documentation of chmod(2) wrt. S_ISVTX on non-directories

2016-01-28 Thread Jason McIntyre
On Wed, Jan 27, 2016 at 08:24:09PM +0100, f...@fuz.su wrote: > The manual page chmod(2) states about the chmod() system call: > > If mode ISVTX (the sticky bit) is set on a file, it is ignored. > > However, attempting to set S_ISVTX on a plain file, the system call > fails with EFTYPE unless