From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [patch 0/17] UML updates, which must be merged before 2.6.9
Date: Fri, 15 Oct 2004 00:44:47 +0200 [thread overview]
Message-ID: <200410150044.47234.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200410130040.i9D0eA3P004443@ccure.user-mode-linux.org>
On Wednesday 13 October 2004 02:40, Jeff Dike wrote:
> Thanks for pushing these. I was about to, but you saved me the trouble.
Ok, thanks - however, I've just added (you'll see it in your mailbox) the "ln
vmlinux linux" fix for the Single Linking Step, which I missed in the first
merge. I have seen mention of it in your diary, which sadly I don't read
frequently (I'll try to do this).
But it would be better to contact me directly (in this case, I just re-added
again the archhelp, mentioning the deprecation of this target).
I also just built a vanilla -rc4-bk2 kernel and it worked like a charm. Andrew
sent to Linux all the patches, and it appears all them were taken inside the
BK snapshot.
This page is very nice:
http://linux.bkbits.net:8080/linux-2.5
As a side note: for now, to avoid breaking people scripts, ubd=sync and/or
CONFIG_BLK_DEV_UBD_SYNC are still synonims (like people are used to threat
them), and are also like replacing ubd0= with ubd0s= for all devices (like
people used to think).
This way, the only think people will notice is more speed. Since you are
always worried about people needing to change their boot scripts, this meets
perfectly your criteria.
You had not agreed on this, but you can fix it later if you want - actually,
you did not answer to my last email about this subject, in which I said what
I say above (it happens frequently).
> BTW, I really like what you did with the build. It is far better than it
> was before you started working on it.
About other work - could you drop the outdated SKAS patches from the official
page? Updating two sites is slow, and waiting for you to pull the changes
from CVS makes the CVS actually unusable (plus you must do the fucking
"SF.net download dance", which I experienced too!).
A pointer to my archive directory would be fine, I guess.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-14 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:05 [uml-devel] [patch 0/17] UML updates, which must be merged before 2.6.9 BlaisorBlade
[not found] ` <200410130040.i9D0eA3P004443@ccure.user-mode-linux.org>
2004-10-14 22:44 ` BlaisorBlade [this message]
2004-10-18 21:16 ` [uml-devel] " Jeff Dike
2004-10-18 22:20 ` BlaisorBlade
2004-10-22 1:32 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410150044.47234.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox