On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote:
> I would like to know if there is indeed a way to toggle between gdb
> and ddb while debugging a remote kernel. I am already at the gdb (or
> rather kgdb) prompt. From here how do I switch to local ddb on the
> debugged
On Tue, Apr 19, 2016 at 10:17 PM, Conrad Meyer wrote:
> On Tue, Apr 19, 2016 at 9:35 AM, Aijaz Baig wrote:
>> On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote:
>>> On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig
On Tue, Apr 19, 2016 at 9:35 AM, Aijaz Baig wrote:
> On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote:
>> On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote:
>>> I would like to know if there is indeed a way to toggle between gdb
On Tue, Apr 19, 2016 at 9:08 PM, Conrad Meyer wrote:
> On Tue, Apr 19, 2016 at 5:49 AM, Aijaz Baig wrote:
>> I would like to know if there is indeed a way to toggle between gdb
>> and ddb while debugging a remote kernel. I am already at the gdb (or
>>
On 19/04/2016 8:49 PM, Aijaz Baig wrote:
Hello
I think the title says it all!! :)
I would like to know if there is indeed a way to toggle between gdb
and ddb while debugging a remote kernel. I am already at the gdb (or
rather kgdb) prompt. From here how do I switch to local ddb on the
debugged
Hello
I think the title says it all!! :)
I would like to know if there is indeed a way to toggle between gdb
and ddb while debugging a remote kernel. I am already at the gdb (or
rather kgdb) prompt. From here how do I switch to local ddb on the
debugged machine??
My kernel configuration file
On 19.04.2016 17:39, Melissa Jenkins wrote:
> Will do - it behaves the same even without PXE.
>
> I believe the issue is that kern.proc.pathname does not exist on any of my
> systems
Have you tried running "sysctl -d kern.proc.pathname" ?
___
On 0419T0906, Melissa Jenkins wrote:
> I've been trying to get reboot -r to work but get an error that
> kern.proc.pathname is undefined. It then drops to single user mode.
>
> Interestingly I've checked the value of kern.proc.pathname and it appears to
> be undefined on all the OS boxes we
Will do - it behaves the same even without PXE.
I believe the issue is that kern.proc.pathname does not exist on any of my
systems
Mel
> On 19 Apr 2016, at 11:19, Eugene Grosbein wrote:
>
> CCing Edward Tomasz Napierala, "Root Remount" project contact.
>
> On 19.04.2016
CCing Edward Tomasz Napierala, "Root Remount" project contact.
On 19.04.2016 16:42, Melissa Jenkins wrote:
> My apologies:
>
> [root@test:~]# sysctl -A kern.proc.pathname
> [root@test:~]# kenv vfs.root.mountfrom
> nfs:nfsserver:/bootenv/10.3
> [root@test:~]# kenv
My apologies:
[root@test:~]# sysctl -A kern.proc.pathname
[root@test:~]# kenv vfs.root.mountfrom
nfs:nfsserver:/bootenv/10.3
[root@test:~]# kenv vfs.root.mountfrom=zfs:test/root_role
vfs.root.mountfrom="zfs:test/root_role"
[root@test:~]# reboot -r
[root@test:~]#
Apr 19 09:35:28 test
On 19.04.2016 15:06, Melissa Jenkins wrote:
> I've been trying to get reboot -r to work but get an error that
> kern.proc.pathname is undefined. It then drops to single user mode.
>
> Interestingly I've checked the value of kern.proc.pathname and it appears to
> be undefined on all the OS
I've been trying to get reboot -r to work but get an error that
kern.proc.pathname is undefined. It then drops to single user mode.
Interestingly I've checked the value of kern.proc.pathname and it appears to be
undefined on all the OS boxes we have from 9.3 up to current. In fact the
13 matches
Mail list logo