> On Dec 17, 2017, at 4:48 PM, Warner Losh wrote:
>
> Sorry to top post. The problem did turn out to be securelevel. We found
> this by doing
>
> dtrace -n 'fbt::securelevel_gt:return {print(args[1];)}'
>
> Though you could also replace securelevel_gt with passopen to see it was in
> passopen t
Sorry to top post. The problem did turn out to be securelevel. We found
this by doing
dtrace -n 'fbt::securelevel_gt:return {print(args[1];)}'
Though you could also replace securelevel_gt with passopen to see it was in
passopen too...
Warner
On Sun, Dec 17, 2017 at 2:08 PM, Dan Langille wrote:
> On Dec 17, 2017, at 4:04 PM, Warner Losh wrote:
>
> What's the permissions of /dev/xpt0 in the jail? If it's not there I know
> at least camcontrol won't work. I've not used mtx, so I can't say if it's
> affected too or not.
I have tried both with and without xpt0. When I tried, it was:
# ls
What's the permissions of /dev/xpt0 in the jail? If it's not there I know
at least camcontrol won't work. I've not used mtx, so I can't say if it's
affected too or not.
However, looking at the truss output:
openat(AT_FDCWD,"/dev/pass7",O_RDWR|O_EXCL,00) ERR#1 'Operation not
permitted'
suggests so
On Sun, Dec 17, 2017 at 03:49:15PM -0500, Dan Langille wrote:
> > On Dec 17, 2017, at 3:37 PM, Konstantin Belousov
> > wrote:
> > Does it work to access the pass device from host using host' /dev ?
>
> Yes, it does. see "This command on the host" at
> https://lists.freebsd.org/pipermail/freebsd
> On Dec 17, 2017, at 3:37 PM, Konstantin Belousov wrote:
>
> On Sun, Dec 17, 2017 at 02:52:12PM -0500, Dan Langille wrote:
>> Hello,
>>
>> What suggestions do you have for where I should look next? I'm happy to
>> start installing various builds of FreeBSD in order to track down which
>> comm
> On Dec 17, 2017, at 3:37 PM, Bjoern A. Zeeb
> wrote:
>
> On 17 Dec 2017, at 19:52, Dan Langille wrote:
>
>> Hello,
>>
>> What suggestions do you have for where I should look next? I'm happy to
>> start installing various builds of FreeBSD in order to track down which
>> commit caused this.
On 17 Dec 2017, at 19:52, Dan Langille wrote:
Hello,
What suggestions do you have for where I should look next? I'm happy
to start installing various builds of FreeBSD in order to track down
which commit caused this.
I'm trying to access a tape library from within a jail running on a
FreeB
On Sun, Dec 17, 2017 at 02:52:12PM -0500, Dan Langille wrote:
> Hello,
>
> What suggestions do you have for where I should look next? I'm happy to start
> installing various builds of FreeBSD in order to track down which commit
> caused this.
>
> I'm trying to access a tape library from within
Hello,
What suggestions do you have for where I should look next? I'm happy to start
installing various builds of FreeBSD in order to track down which commit caused
this.
I'm trying to access a tape library from within a jail running on a FreeBSD
11.1 host. sa(4) devices are working (e.g. I c
10 matches
Mail list logo