Guillaume,
Don't see why not, sounds like the right place for it? I rebuilt a 6
kernel some while back for work that had MP-TCP and F-RTO in it along with
some twiddling of initRTO as well, those other two are in mainstream now
and the MP-TCP patch must have been fairly simple if I managed to work it
in. Shout if you need any help, I've got some doco somewhere.
> Message: 19
> Date: Sun, 15 Jun 2014 13:54:29 +0200
> From: Guillaume Derval <guillaume.derval(a)student.uclouvain.…
[View More]be>
> Subject: [CentOS-devel] Multipath-TCP in the centosplus kernel?
> To: centos-devel(a)centos.org
> Message-ID:
> <A8BF2232-7620-433F-82D0-C74FBEE5597B(a)student.uclouvain.be>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello everyone,
>
> I am thinking about building custom kernels for CentOS-7 with a support
> for Multipath-TCP (http://multipath-tcp.org/), and I am wondering if a
> such heavy modification should have its place in the centosplus kernel?
>
> Modified kernel sources are available at
> https://github.com/multipath-tcp/mptcp and equivalent patches are there:
> http://multipath-tcp.org/patches/.
>
> Best regards,
> Guillaume Derval.
>
--
Regards,
Phil
[View Less]
Hello everyone,
I am thinking about building custom kernels for CentOS-7 with a support for Multipath-TCP (http://multipath-tcp.org/), and I am wondering if a such heavy modification should have its place in the centosplus kernel?
Modified kernel sources are available at https://github.com/multipath-tcp/mptcp and equivalent patches are there: http://multipath-tcp.org/patches/.
Best regards,
Guillaume Derval.
hi,
So we now have RHEL media, RHEL optionals and RHEL Extras. Optionals and
media seems to tie in as before, however Extras has its own policy +
lifeterm etc.
Thoughts on what we might do with those rpms ? I'd have though that
putting them in CentOS-Extras would line up nicely. Content that is
available out of the blocks to anyone with a CentOS install, but not
themselves included in the distro.
thoughts ?
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh…
[View More]GnuPG Key : http://www.karan.org/publickey.asc
[View Less]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/15/2014 08:00 AM, centos-devel-request(a)centos.org wrote:
> Message: 8 Date: Sat, 14 Jun 2014 16:22:33 +0100 From: Karanbir
> Singh <mail-lists(a)karan.org> Subject: Re: [CentOS-devel] CentOS 7
> Public QA Release Beginner's Question To: centos-devel(a)centos.org
> Message-ID: <539C68B9.1080703(a)karan.org> Content-Type: text/plain;
> charset=ISO-8859-1 On 06/14/2014 01:28 PM, Bob Lightfoot wrote:
>>> …
[View More]Looks like a great lot of work, so thanks for the effort. As
>>> a Fedora Testor I am puzzled somewhat though. Is there
>>> available reading material and such as how I would go about
>>> using these rpm with a qemu/kvm for testing without having the
>>> installer available yet? Obviously I can test the install media
>>> when it exists just like I do for Fedora, but using these trees
>>> of rpms is a new skill I am hoping to add. Don't want to bog
>>> anyone down with explaining it in detail, as I don't mind
>>> reading and teaching myself, just need pointed where to look.
> we also spend quite a bit of time looking at and working with the
> rpms themselves to make sure they built ok, carry the right
> metadata, and then work on the branding stuff - ideally that, and
> migration paths from 6 to 7 are what we'd be expecting people to be
> consuming and testing here.
>
> - KB
KB - you mention migration paths from 6 to 7 and branding stuff. Are
you envisioning a test like taking an up to date c6 installation and
the yum installing c7 rpms and looking for hiccups and issues? I'm
not quite sure I understand what is meant by migration when as yet
there is no C7 installer or install tree.
Sincerely,
Bob Lightfoot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTndCiAAoJEKqgpLIhfz3XyvcH/0RPkamdyK9zJgARJxWE2ZQa
svvEwdDz41DtYSMlPfHp/FxU8pX/c4abIjebqFhnUlcfSmVR2jUAIdGzpwsN6Twm
uq4ypJz5UYFPcQx3bJQu1xYKSDJ2EzgI3oBLXYK67ZB4rLFZuPc3lJMt1wG2e4Ut
5sfCMi/T5hmtTS6QQBUkSK105IpA2/krC8s/v77ys3QGmcjjS00QPy2ME3DjoD4O
HBwsQAHgmMQicT3RAL1SImfjIInt+Bq7fcdHJpl1UxGFZb2MEAaj137KYIM5Emsh
Yijlj4b1l9y2A2QEEfKLQK57acGDOEBtK25oovSZWIxT3oQpZ52bFRBFeNVH4EI=
=Hcps
-----END PGP SIGNATURE-----
[View Less]
From: Pat Riehecky <riehecky(a)fnal.gov>
I was looking for some automated tooling to determine what SRPMS can be
generated by a given git repo. Since none was out there, I've tossed
this together.
Pat Riehecky (3):
Minor updates to some doc, nothing of real interest
Added script to show srpms contained within a given repo
Added switches for setting branch to check, alas I've no idea how to
do this
return_disttag.sh | 3 +-
show_possible_srpms.sh | 121 ++++++++++++++…
[View More]++++++++++++++++++++++++++++++++++
2 files changed, 123 insertions(+), 1 deletions(-)
create mode 100755 show_possible_srpms.sh
[View Less]
hi,
Just wondering if anyone has had a stab at an rpm-ostree build + atomic
host from the content hosted in centos7qa tree's.
Will need to find docker, but that can come from EPEL7 ( or for now,
step1, just an atomic host might be a good start ).
- KB
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi,
There still seems to be some level of ambiguity as to how we are doing
the change requests, rebuild requests and change requests so I wanted to
get a short summary on the list and we can pickup details where needed.
For anything that anyone sees that needs a change : file an issue report
at bugs.centos.org; this is most important. Then see if you can also
propose a patch.
In order to propose a patch you need to run through a few steps( in this
example assuming we want to patch httpd ):
$…
[View More] git clone https://git.centos.org/git/centos-git-common.git
$ git clone https://git.centos.org/git/rpms/httpd.git
$ cd httpd
$ git branch -a
$ git checkout c7
$ bash ../centos-git-common/get_sources.sh
$ git rev-parse HEAD > `whoami`.start-point
$ bash ../centos-git-common/rpm-tree-prep.sh
At this point you should be good to make changes to SPECS/ SOURCES/ and
BUILD/package-name ( note that the rpm-tree-prep.sh script will setup a
__orig dir for you to build patches against.
once you have the content ready, git commit the changes, in multiple
commits, to have a complete, but as small as possible, change in one
commit. Eg. if you are fixing 5 things, ideally end up with 5 commits.
Also, if you are adding content, to replace something else that is going
away, make sure you have the delete and addition in the same commit. Eg.
replacing xulrunner-redhat-prefs.js with xulrunner-centos-prefs.js - add
the git rm and git add into the same commit.
Once you are happy with the state of play, go back to the root of the
git repo, and :
$ git format-patch $(cat `whoami`.start-point)
this will leave behind files, one per commit that you made, in the
format : NNNN-<commit summary>.patch : these are the files you need to
attach to bugs.centos.org; these files contain your user metadata as
well, and can then be applied as is. So you get credit for the changes,
and we are able to replay exactly the change you had in mind.
NOTES:
CentOS patches added to the SPEC file should be named :
<packagename>-CentOS-<change being made>.patch
When added to the spec file, its a good practise to skip a few hundred
spots on the patch list. Eg. if the spec has no patches, then start the
CentOS patches at Patch1000 onward. If the spec already has patches,
then skip a large number. This is just so we dont have ( or are less
likely to have ) Patch number conflict with upstream changes in the life
of CentOS-7
lets get patching, todays build is definitely on.
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
[View Less]
Hi,
as I'm messing around with upstream's installer, I see that it crashes
on my Intelli:
https://drive.google.com/file/d/0B6Xv-IAqdukmd3luaE5EODYwY2c/edit?usp=shari…
The machine is in perfect condition, Fedora 20 (Heisenbug) runs like a
charm.
However, I don't even find detailed information on whether RHEL7
supports this hardware or not.
Cheers,
Timo
Right now within the centos-logos package, we have:
Anaconda:
- Theme from Tuomas
- banners from Alain
Backgrounds:
- Backgrounds from Tuomas
- Backgrounds from Alain
- Backgrounds from Marcus
At some point tomorrow KB will have the updated centos-logos package
imported into git, so we'll all have a common base to work from. Until
then, the src.rpm for the working package can be found at
http://buildlogs.centos.org/c7.00.04/centos-logos/20140613160840/70.0.4-1.e…
I'd like to see if …
[View More]we can align the blues used in Tuomas's anaconda
theme and the blues used in Alain's anaconda banners so that the
installer has a more unified feel to it. I'll leave it to the two of you
to figure out how best to address that.
I'd also like to get everyone's opinions on the 'default' desktop
background. They're all quite good, including a rotating set that will
vary throughout the day.
Marcus, I'm reasonably certain I gave your two background submissions
terrible names. Please tell me if you'd like them corrected to something
a bit more appropriate.
If anyone has other suggestions for the look and feel of the distro as
it applies to the -logos package, now is the time to provide both voice
and/or changes.
Patches sound be submitted either to the mailing list, or attached to a
ticket at bugs.centos.org
--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
[View Less]