Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Linda]

First, Julien, your suggestion worked like a charm.
So here's what's happened tonight.  I tried to build the tools directory 
of my git repository.  Although I used the sudo command in my virtual 
ubuntu, I got a permission denied error  126 on xen_foreign.

Second, I tried to follow the protocol for submitting my patches.  I 
changed libxl_utils.c and libxl_utils.h, in my repository, add and 
commit them.  Unfortunately, I didn't include my signature (next page of 
instructions I was following), and couldn't figure how to get back in to 
add them.

Finally, I tried git send-email (took a bit to find I had to install 
it).  Now it doesn't like the format of my send-email:
  to the devlopers list above and cc'ing Julien and Wei, followed by:
1.  following this with the files (even with --no-format-patch), error 
was "no subject line"
2.  (different attempt) the repository "master"  error complained about 
the format patch

SO   if anyone is up at an ungodly hour and can explain any of these 
errors to me (I'm in Colorado - so it's 7:30 here), especially with a 
fix, I'd be grateful.  Otherwise, Julien, Wei, I'll start at about 7am 
my time, maybe a little earlier.

Thanks.

Linda Jacobson

On 4/1/2015 2:57 PM, Julien Grall wrote:
>
>
> On 01/04/2015 18:46, Linda wrote:
>> I'll try it.  That's the
>>
>> libvncserver-dev libsdl-dev libjpeg62-dev
>>
>> Should I keep the libsdl-dev?
>>
>>    In the meantime, I'm following the git protocol for patches. I
>> successfully cloned xen.git.  The next statement in the directions - I
>> can't tell if it's one statement on many lines, or many statements.  It
>> starts out git branch -a
>> When I type this alone, I get "Not a git repository"  When I type in the
>> many lines as a single command I get the error message:
>> origin/master no such file or directory
>
> You have to type the command "git branch -a"  in the git repository 
> (i.e the directory xen.git).
>
>
>>
>> This comes from the line remotes/origin/HEAD->origin
>>
>> ?????
>
> This is normal. The line starting by '$' is a command. Everything else 
> is an example output of the execution of the command.
>
> Obviously, you have to drop the '$' when typing copying the command.
>
> To go further, '$' means a command to execute with your current user 
> and '#' a command to execute with root privileges (i.e adding sudo 
> before).
>
> This is usually a standard on Linux/BSD shell documentation.
>
> Although, there is some place within this wiki page where the command 
> doesn't have '$'/'#' (see [1]). So you to judge yourself if the line 
> looks like a command or not :).
>
> Regards,
>
> [1] 
> http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Git_send-email
>
>

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Konrad Rzeszutek Wilk]

On Wed, Apr 01, 2015 at 07:36:49PM -0600, Linda wrote:
> First, Julien, your suggestion worked like a charm.
> So here's what's happened tonight.  I tried to build the tools directory of
> my git repository.  Although I used the sudo command in my virtual ubuntu, I
> got a permission denied error  126 on xen_foreign.

One way to help with that is if you do:

make 1>&2 2>log

And attach the log.
> 
> Second, I tried to follow the protocol for submitting my patches.  I changed
> libxl_utils.c and libxl_utils.h, in my repository, add and commit them.
> Unfortunately, I didn't include my signature (next page of instructions I
> was following), and couldn't figure how to get back in to add them.

git commit --amend

Or if you want to do more of them:

git rebase -i origin/staging

(and in the editor change 'pick' to 'r').

> 
> Finally, I tried git send-email (took a bit to find I had to install it).
> Now it doesn't like the format of my send-email:

Again, please copy-n-paste the command line you had.

>  to the devlopers list above and cc'ing Julien and Wei, followed by:
> 1.  following this with the files (even with --no-format-patch), error was
> "no subject line"
> 2.  (different attempt) the repository "master"  error complained about the
> format patch

Not sure I understand that. Is that for 'git send-email' or 'git
format-patch'?
> 
> SO   if anyone is up at an ungodly hour and can explain any of these errors
> to me (I'm in Colorado - so it's 7:30 here), especially with a fix, I'd be
> grateful.  Otherwise, Julien, Wei, I'll start at about 7am my time, maybe a
> little earlier.

The previous OPW had an article about using git and how to do it with
kernel patches. It is exactly the same flow - except different email
address.

Anyhow, what I end up doing is:

1). git format-patch --subject-prefix "PATCH RFC" origin/staging..

(which generates 0001-, 0002-, etc files - for two patches).

2). git send-email --to xen-devel@xenproject.org --to someotheremail.org
--compose --subject "[PATCH RFC] Patches to fix XYZ." 000*.patch

And in the editor do a little writeup of what the patches have.
At the end of this, I attach the output from:

git diff --stat origin/staging..

git shortlog origin/staging..

which gives a nice diff output and what the patches are.

And then send it off.
> 
> Thanks.
> 
> Linda Jacobson
> 
> On 4/1/2015 2:57 PM, Julien Grall wrote:
> >
> >
> >On 01/04/2015 18:46, Linda wrote:
> >>I'll try it.  That's the
> >>
> >>libvncserver-dev libsdl-dev libjpeg62-dev
> >>
> >>Should I keep the libsdl-dev?
> >>
> >>   In the meantime, I'm following the git protocol for patches. I
> >>successfully cloned xen.git.  The next statement in the directions - I
> >>can't tell if it's one statement on many lines, or many statements.  It
> >>starts out git branch -a
> >>When I type this alone, I get "Not a git repository"  When I type in the
> >>many lines as a single command I get the error message:
> >>origin/master no such file or directory
> >
> >You have to type the command "git branch -a"  in the git repository (i.e
> >the directory xen.git).
> >
> >
> >>
> >>This comes from the line remotes/origin/HEAD->origin
> >>
> >>?????
> >
> >This is normal. The line starting by '$' is a command. Everything else is
> >an example output of the execution of the command.
> >
> >Obviously, you have to drop the '$' when typing copying the command.
> >
> >To go further, '$' means a command to execute with your current user and
> >'#' a command to execute with root privileges (i.e adding sudo before).
> >
> >This is usually a standard on Linux/BSD shell documentation.
> >
> >Although, there is some place within this wiki page where the command
> >doesn't have '$'/'#' (see [1]). So you to judge yourself if the line looks
> >like a command or not :).
> >
> >Regards,
> >
> >[1] http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Git_send-email
> >
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Linda]

Thanks Konrad.

I came close to doing your suggestions on git, and got it, sort of, to 
work.  I will follow your instructions exactly for updates.

There were also, some problems with the way the smtp server needed to be 
set up (compounded by typos of course), which are all fixed.

As far as your answer to my build problems, I'm not sure what this will do:

One way to help with that is if you do:

make 1>&2 2>log

And attach the log.

I am semi-new to the linux world - is this to allow someone else to help 
me?  What does the make command above do?

Thanks, again.

Linda

On 4/2/2015 12:59 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 01, 2015 at 07:36:49PM -0600, Linda wrote:
>> First, Julien, your suggestion worked like a charm.
>> So here's what's happened tonight.  I tried to build the tools directory of
>> my git repository.  Although I used the sudo command in my virtual ubuntu, I
>> got a permission denied error  126 on xen_foreign.
> One way to help with that is if you do:
>
> make 1>&2 2>log
>
> And attach the log.
>> Second, I tried to follow the protocol for submitting my patches.  I changed
>> libxl_utils.c and libxl_utils.h, in my repository, add and commit them.
>> Unfortunately, I didn't include my signature (next page of instructions I
>> was following), and couldn't figure how to get back in to add them.
> git commit --amend
>
> Or if you want to do more of them:
>
> git rebase -i origin/staging
>
> (and in the editor change 'pick' to 'r').
>
>> Finally, I tried git send-email (took a bit to find I had to install it).
>> Now it doesn't like the format of my send-email:
> Again, please copy-n-paste the command line you had.
>
>>   to the devlopers list above and cc'ing Julien and Wei, followed by:
>> 1.  following this with the files (even with --no-format-patch), error was
>> "no subject line"
>> 2.  (different attempt) the repository "master"  error complained about the
>> format patch
> Not sure I understand that. Is that for 'git send-email' or 'git
> format-patch'?
>> SO   if anyone is up at an ungodly hour and can explain any of these errors
>> to me (I'm in Colorado - so it's 7:30 here), especially with a fix, I'd be
>> grateful.  Otherwise, Julien, Wei, I'll start at about 7am my time, maybe a
>> little earlier.
> The previous OPW had an article about using git and how to do it with
> kernel patches. It is exactly the same flow - except different email
> address.
>
> Anyhow, what I end up doing is:
>
> 1). git format-patch --subject-prefix "PATCH RFC" origin/staging..
>
> (which generates 0001-, 0002-, etc files - for two patches).
>
> 2). git send-email --to xen-devel@xenproject.org --to someotheremail.org
> --compose --subject "[PATCH RFC] Patches to fix XYZ." 000*.patch
>
> And in the editor do a little writeup of what the patches have.
> At the end of this, I attach the output from:
>
> git diff --stat origin/staging..
>
> git shortlog origin/staging..
>
> which gives a nice diff output and what the patches are.
>
> And then send it off.
>> Thanks.
>>
>> Linda Jacobson
>>
>> On 4/1/2015 2:57 PM, Julien Grall wrote:
>>>
>>> On 01/04/2015 18:46, Linda wrote:
>>>> I'll try it.  That's the
>>>>
>>>> libvncserver-dev libsdl-dev libjpeg62-dev
>>>>
>>>> Should I keep the libsdl-dev?
>>>>
>>>>    In the meantime, I'm following the git protocol for patches. I
>>>> successfully cloned xen.git.  The next statement in the directions - I
>>>> can't tell if it's one statement on many lines, or many statements.  It
>>>> starts out git branch -a
>>>> When I type this alone, I get "Not a git repository"  When I type in the
>>>> many lines as a single command I get the error message:
>>>> origin/master no such file or directory
>>> You have to type the command "git branch -a"  in the git repository (i.e
>>> the directory xen.git).
>>>
>>>
>>>> This comes from the line remotes/origin/HEAD->origin
>>>>
>>>> ?????
>>> This is normal. The line starting by '$' is a command. Everything else is
>>> an example output of the execution of the command.
>>>
>>> Obviously, you have to drop the '$' when typing copying the command.
>>>
>>> To go further, '$' means a command to execute with your current user and
>>> '#' a command to execute with root privileges (i.e adding sudo before).
>>>
>>> This is usually a standard on Linux/BSD shell documentation.
>>>
>>> Although, there is some place within this wiki page where the command
>>> doesn't have '$'/'#' (see [1]). So you to judge yourself if the line looks
>>> like a command or not :).
>>>
>>> Regards,
>>>
>>> [1] http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Git_send-email
>>>
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Konrad Rzeszutek Wilk]

On Thu, Apr 02, 2015 at 01:16:36PM -0600, Linda wrote:
> Thanks Konrad.
> 
> I came close to doing your suggestions on git, and got it, sort of, to work.
> I will follow your instructions exactly for updates.

Heh. The git manual is also a very good resource.
> 
> There were also, some problems with the way the smtp server needed to be set
> up (compounded by typos of course), which are all fixed.
> 
> As far as your answer to my build problems, I'm not sure what this will do:
> 
> One way to help with that is if you do:
> 
> make 1>&2 2>log
> 
> And attach the log.
> 
> I am semi-new to the linux world - is this to allow someone else to help me?

Correct.
> What does the make command above do?

Build.
> 
> Thanks, again.
> 
> Linda
> 
> On 4/2/2015 12:59 PM, Konrad Rzeszutek Wilk wrote:
> >On Wed, Apr 01, 2015 at 07:36:49PM -0600, Linda wrote:
> >>First, Julien, your suggestion worked like a charm.
> >>So here's what's happened tonight.  I tried to build the tools directory of
> >>my git repository.  Although I used the sudo command in my virtual ubuntu, I
> >>got a permission denied error  126 on xen_foreign.
> >One way to help with that is if you do:
> >
> >make 1>&2 2>log
> >
> >And attach the log.
> >>Second, I tried to follow the protocol for submitting my patches.  I changed
> >>libxl_utils.c and libxl_utils.h, in my repository, add and commit them.
> >>Unfortunately, I didn't include my signature (next page of instructions I
> >>was following), and couldn't figure how to get back in to add them.
> >git commit --amend
> >
> >Or if you want to do more of them:
> >
> >git rebase -i origin/staging
> >
> >(and in the editor change 'pick' to 'r').
> >
> >>Finally, I tried git send-email (took a bit to find I had to install it).
> >>Now it doesn't like the format of my send-email:
> >Again, please copy-n-paste the command line you had.
> >
> >>  to the devlopers list above and cc'ing Julien and Wei, followed by:
> >>1.  following this with the files (even with --no-format-patch), error was
> >>"no subject line"
> >>2.  (different attempt) the repository "master"  error complained about the
> >>format patch
> >Not sure I understand that. Is that for 'git send-email' or 'git
> >format-patch'?
> >>SO   if anyone is up at an ungodly hour and can explain any of these errors
> >>to me (I'm in Colorado - so it's 7:30 here), especially with a fix, I'd be
> >>grateful.  Otherwise, Julien, Wei, I'll start at about 7am my time, maybe a
> >>little earlier.
> >The previous OPW had an article about using git and how to do it with
> >kernel patches. It is exactly the same flow - except different email
> >address.
> >
> >Anyhow, what I end up doing is:
> >
> >1). git format-patch --subject-prefix "PATCH RFC" origin/staging..
> >
> >(which generates 0001-, 0002-, etc files - for two patches).
> >
> >2). git send-email --to xen-devel@xenproject.org --to someotheremail.org
> >--compose --subject "[PATCH RFC] Patches to fix XYZ." 000*.patch
> >
> >And in the editor do a little writeup of what the patches have.
> >At the end of this, I attach the output from:
> >
> >git diff --stat origin/staging..
> >
> >git shortlog origin/staging..
> >
> >which gives a nice diff output and what the patches are.
> >
> >And then send it off.
> >>Thanks.
> >>
> >>Linda Jacobson
> >>
> >>On 4/1/2015 2:57 PM, Julien Grall wrote:
> >>>
> >>>On 01/04/2015 18:46, Linda wrote:
> >>>>I'll try it.  That's the
> >>>>
> >>>>libvncserver-dev libsdl-dev libjpeg62-dev
> >>>>
> >>>>Should I keep the libsdl-dev?
> >>>>
> >>>>   In the meantime, I'm following the git protocol for patches. I
> >>>>successfully cloned xen.git.  The next statement in the directions - I
> >>>>can't tell if it's one statement on many lines, or many statements.  It
> >>>>starts out git branch -a
> >>>>When I type this alone, I get "Not a git repository"  When I type in the
> >>>>many lines as a single command I get the error message:
> >>>>origin/master no such file or directory
> >>>You have to type the command "git branch -a"  in the git repository (i.e
> >>>the directory xen.git).
> >>>
> >>>
> >>>>This comes from the line remotes/origin/HEAD->origin
> >>>>
> >>>>?????
> >>>This is normal. The line starting by '$' is a command. Everything else is
> >>>an example output of the execution of the command.
> >>>
> >>>Obviously, you have to drop the '$' when typing copying the command.
> >>>
> >>>To go further, '$' means a command to execute with your current user and
> >>>'#' a command to execute with root privileges (i.e adding sudo before).
> >>>
> >>>This is usually a standard on Linux/BSD shell documentation.
> >>>
> >>>Although, there is some place within this wiki page where the command
> >>>doesn't have '$'/'#' (see [1]). So you to judge yourself if the line looks
> >>>like a command or not :).
> >>>
> >>>Regards,
> >>>
> >>>[1] http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Git_send-email
> >>>
> >>>
> >>
> >>_______________________________________________
> >>Xen-devel mailing list
> >>Xen-devel@lists.xen.org
> >>http://lists.xen.org/xen-devel
> 

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Linda Jacobson]

[-- Attachment #1: Type: text/html, Size: 80 bytes --]

[-- Attachment #2: log --]
[-- Type: application/octet-stream, Size: 234 bytes --]

/bin/sh: 1: ./checker: Permission denied
make[4]: *** [check-headers] Error 126
make[3]: *** [xen-foreign] Error 2
make[2]: *** [subdir-install-include] Error 2
make[1]: *** [subdirs-install] Error 2
make: *** [install-tools] Error 2

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: implementing a classic Xen front/back pv driver pair to provide a transport for 9P FS Protocol

[Linda Jacobson]

[-- Attachment #1: Type: text/html, Size: 4753 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel