Re: How to verify linux-next

On Mon, 02 Oct 2017 10:11:34 +0200, Kamil Konieczny said: > What about /usr/bin/ssh as init replacement ? Well, if you are OK with your system panicking right away. :) (Hint - the init process needs to be something that can run as a daemon). If you use /usr/sbin/sshd, that has a *slightly*

Re: How to verify linux-next

On Mon, 02 Oct 2017 10:11:34 +0200, Kamil Konieczny said: > What about /usr/bin/ssh as init replacement ? Well, if you are OK with your system panicking right away. :) (Hint - the init process needs to be something that can run as a daemon). If you use /usr/sbin/sshd, that has a *slightly*

Re: How to verify linux-next

On 29.09.2017 17:45, valdis.kletni...@vt.edu wrote: > On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said: > >> 1) If you have pointers on how to setup ssh/net connection on QEMU >> with busybox, do let me know. > > Busybox doesn't do that as far as I know, as it's intended as a single-user >

Re: How to verify linux-next

On 29.09.2017 17:45, valdis.kletni...@vt.edu wrote: > On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said: > >> 1) If you have pointers on how to setup ssh/net connection on QEMU >> with busybox, do let me know. > > Busybox doesn't do that as far as I know, as it's intended as a single-user >

Re: How to verify linux-next

On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith wrote: > On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: >> On 10/01/17 09:44, Damian Tometzki wrote: >> >> > i resolved the issue with: >> > sudo /etc/init.d/apparmor stop >> >> or boot with: apparmor=0 > > or systemctl mask

Re: How to verify linux-next

On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith wrote: > On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: >> On 10/01/17 09:44, Damian Tometzki wrote: >> >> > i resolved the issue with: >> > sudo /etc/init.d/apparmor stop >> >> or boot with: apparmor=0 > > or systemctl mask apparmor Ok,

Re: How to verify linux-next

On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: > On 10/01/17 09:44, Damian Tometzki wrote: > > > i resolved the issue with: > > sudo /etc/init.d/apparmor stop > > or boot with: apparmor=0 or systemctl mask apparmor

Re: How to verify linux-next

On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: > On 10/01/17 09:44, Damian Tometzki wrote: > > > i resolved the issue with: > > sudo /etc/init.d/apparmor stop > > or boot with: apparmor=0 or systemctl mask apparmor

Re: How to verify linux-next

On 10/01/17 09:44, Damian Tometzki wrote: > > Am Sonntag, den 01.10.2017, 21:58 +0530 schrieb Pintu Kumar: >> On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o >> wrote: >>> >>> On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: I need to submit a patch to

Re: How to verify linux-next

On 10/01/17 09:44, Damian Tometzki wrote: > > Am Sonntag, den 01.10.2017, 21:58 +0530 schrieb Pintu Kumar: >> On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o >> wrote: >>> >>> On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: I need to submit a patch to mainline which should

Re: How to verify linux-next

On Sun, Oct 01, 2017 at 09:58:37PM +0530, Pintu Kumar wrote: > Ok thank you so much for your reply. > Now I am able to boot with v4.14-rc2. But now I am facing another problem. > Now, I am not able to connect to internet from virtual box. > When I switch back to the default 4.10 the internet works

Re: How to verify linux-next

On Sun, Oct 01, 2017 at 09:58:37PM +0530, Pintu Kumar wrote: > Ok thank you so much for your reply. > Now I am able to boot with v4.14-rc2. But now I am facing another problem. > Now, I am not able to connect to internet from virtual box. > When I switch back to the default 4.10 the internet works

Re: How to verify linux-next

Am Sonntag, den 01.10.2017, 21:58 +0530 schrieb Pintu Kumar: > On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o > wrote: > > > > On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > > > > > > I need to submit a patch to mainline which should be verified > > > against >

Re: How to verify linux-next

Am Sonntag, den 01.10.2017, 21:58 +0530 schrieb Pintu Kumar: > On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o > wrote: > > > > On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > > > > > > I need to submit a patch to mainline which should be verified > > > against > > > linux-next

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o wrote: > On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: >> I need to submit a patch to mainline which should be verified against >> linux-next tree with latest API. > > If you want to verify a patch that you intend to

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o wrote: > On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: >> I need to submit a patch to mainline which should be verified against >> linux-next tree with latest API. > > If you want to verify a patch that you intend to submit upstream,

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > I need to submit a patch to mainline which should be verified against > linux-next tree with latest API. If you want to verify a patch that you intend to submit upstream, my suggestion is to *not* use linux-next, but rather use the

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > I need to submit a patch to mainline which should be verified against > linux-next tree with latest API. If you want to verify a patch that you intend to submit upstream, my suggestion is to *not* use linux-next, but rather use the

Re: How to verify linux-next

Thanks Mr. Tso for your reply. Please find my reply inline. On Sat, Sep 30, 2017 at 3:20 AM, Theodore Ts'o wrote: > On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: >> BTW, I am more interested in my another query about QEMU arm. >> This will be much quicker and easy

Re: How to verify linux-next

Thanks Mr. Tso for your reply. Please find my reply inline. On Sat, Sep 30, 2017 at 3:20 AM, Theodore Ts'o wrote: > On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: >> BTW, I am more interested in my another query about QEMU arm. >> This will be much quicker and easy for me. >> But

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: > BTW, I am more interested in my another query about QEMU arm. > This will be much quicker and easy for me. > But the problem is I wanted to use multiple ssh shell on qemu. > Also I needed a pre-built rootfs image for qemu-arm,

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: > BTW, I am more interested in my another query about QEMU arm. > This will be much quicker and easy for me. > But the problem is I wanted to use multiple ssh shell on qemu. > Also I needed a pre-built rootfs image for qemu-arm,

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar wrote: > On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki > wrote: >> Hello, >> >> Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 >> >> Host: Windows 10 >> Guest: Ubuntu 16.04 >>

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar wrote: > On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki > wrote: >> Hello, >> >> Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 >> >> Host: Windows 10 >> Guest: Ubuntu 16.04 >> >> Best regards >> Damian >> >> >> Am Freitag,

Re: How to verify linux-next

On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said: > 1) If you have pointers on how to setup ssh/net connection on QEMU > with busybox, do let me know. Busybox doesn't do that as far as I know, as it's intended as a single-user /sbin/init replacement. You'll need a full-featured userspace

Re: How to verify linux-next

On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said: > 1) If you have pointers on how to setup ssh/net connection on QEMU > with busybox, do let me know. Busybox doesn't do that as far as I know, as it's intended as a single-user /sbin/init replacement. You'll need a full-featured userspace

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki wrote: > Hello, > > Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 > > Host: Windows 10 > Guest: Ubuntu 16.04 > > Best regards > Damian > > > Am Freitag, den 29.09.2017, 08:41 -0400 schrieb >

Re: How to verify linux-next

On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki wrote: > Hello, > > Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 > > Host: Windows 10 > Guest: Ubuntu 16.04 > > Best regards > Damian > > > Am Freitag, den 29.09.2017, 08:41 -0400 schrieb > valdis.kletni...@vt.edu: >> On

Re: How to verify linux-next

Hello, i can tell you ubuntu 16.04 works under virtualbox 5.1.28 with the current linux-next kernel My maschine: Host: Windows 10 Guest: Ubuntu 16.04 Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I

Re: How to verify linux-next

Hello, i can tell you ubuntu 16.04 works under virtualbox 5.1.28 with the current linux-next kernel My maschine: Host: Windows 10 Guest: Ubuntu 16.04 Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I

Re: How to verify linux-next

Hello, Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 Host: Windows 10 Guest: Ubuntu 16.04 Best regards Damian Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general

Re: How to verify linux-next

Hello, Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 Host: Windows 10 Guest: Ubuntu 16.04 Best regards Damian Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletni...@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general

Re: How to verify linux-next

On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > I have a general question. > How do we normally verify linux-next tree? The same exact way you "verify" any other Linux kernel, for whatever definition of "verify" you plan to use. > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the

Re: How to verify linux-next

On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > I have a general question. > How do we normally verify linux-next tree? The same exact way you "verify" any other Linux kernel, for whatever definition of "verify" you plan to use. > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the

Re: How to verify linux-next

Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next

Re: How to verify linux-next

Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next

Re: How to verify linux-next

** Re sending ** Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot

Re: How to verify linux-next

** Re sending ** Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot

How to verify linux-next

Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next

How to verify linux-next

Hi, I have a general question. How do we normally verify linux-next tree? I wanted to work on linux-next but I am facing some issues. I could able to build linux-next for both x86 and arm, but I could not verify it on any machine. Currently I don't have a real Linux PC to boot with linux-next