Hello List,
i am new to Centos and did my first install on a server. I got it working that also looks inzo the epel repositorie.
Now i want to install DRBD. But yum search drbd returns me only a package i dont need.
Do i have to enable the epel-test repo to get itß But test sounds not stable for me and we switched to centos for stability.
anyone here can help me or give me any hints on drbd on centos 6?
Do i have to compile by hand?
marko
Do i have to compile by hand?
Yeah, but generate rpm's for final installation, its trivial. http://www.drbd.org/users-guide-emb/s-build-rpm.html
Thanks Joseph,
my thought ideas behind was, i like to maintenance systems via package manager. Each thing you install by hand brake this. But it sounds okay for me.
Thank you.
marko (from rainy Hamburg)
Am 11.10.2011 12:22, schrieb Joseph L. Casale:
Do i have to compile by hand?
Yeah, but generate rpm's for final installation, its trivial. http://www.drbd.org/users-guide-emb/s-build-rpm.html
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
centos-bounces@centos.org schrieb am 11.10.2011 12:27:57:
Marko Weber weber@zackbummfertig.de Gesendet von: centos-bounces@centos.org
11.10.2011 12:28
Bitte antworten an CentOS mailing list centos@centos.org
An
CentOS mailing list centos@centos.org
Kopie
Thema
Re: [CentOS] Centos 6.0 , DRBD
Thanks Joseph,
my thought ideas behind was, i like to maintenance systems via package manager. Each thing you install by hand brake this. But it sounds okay for me.
Thank you.
marko (from rainy Hamburg)
Am 11.10.2011 12:22, schrieb Joseph L. Casale:
Do i have to compile by hand?
Yeah, but generate rpm's for final installation, its trivial. http://www.drbd.org/users-guide-emb/s-build-rpm.html
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi Marko,
you can use drbd from elrepo.repo (http://elrepo.org/tiki/drbd83-utils), so you can manage this rpms from your package-manager like yum
Gruß Andreas Reschke ________________________________________________________________ Unix/Linux-Administration Andreas.Reschke@behrgroup.com
Vreme: 10/11/2011 07:47 PM, Joseph L. Casale piše:
Each thing you install by hand brake this.
Did you actually read my post and the link? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think he did, but he would like an package done by someone who knows what he is doing. Bear in mind that RHEL kernel is not stock kernel, there are number of back-ported patches in it. It is safer to use a package with applied RHEL specific patches (if necessary) done by people working with RHEL kernel regularly. I for one would never try to build kernel module my self. I would at least ask for experts opinion on my spec/package work.
I think he did, but he would like an package done by someone who knows what he is doing. Bear in mind that RHEL kernel is not stock kernel, there are number of back-ported patches in it. It is safer to use a package with applied RHEL specific patches (if necessary) done by people working with RHEL kernel regularly. I for one would never try to build kernel module my self. I would at least ask for experts opinion on my spec/package work.
Wow, you didn't read it either... You build it against _your_ kernel. Its like two commands...
Vreme: 10/12/2011 12:09 AM, Joseph L. Casale piše:
I think he did, but he would like an package done by someone who knows what he is doing. Bear in mind that RHEL kernel is not stock kernel, there are number of back-ported patches in it. It is safer to use a package with applied RHEL specific patches (if necessary) done by people working with RHEL kernel regularly. I for one would never try to build kernel module my self. I would at least ask for experts opinion on my spec/package work.
Wow, you didn't read it either... You build it against _your_ kernel. Its like two commands...
I do not have to read it (although I understood you the first time). My production server is not going to be a ginipig for developers. And I, so far, rebuilt over 100 packages including newer Qt for C6.
There is a repo (ELRepo) run by knowledgeable kernel developers/packagers, with 10 times more knowledge about kernels then me. And their package was build from most stable version, taking RHEL kernel oddities into account, and already tested. Why would I (or anyone else) "invent hot water"??
Getting out from the slippery bath tub is one "command" to my brain, but I managed to almost cut my palm in two when porcelain sink I was leaning onto (I almost never did that before, and never again) broke to peaces. If I had passed out (and I almost did), I would not be here now. Crude analogy, but very real for me, my thumb lost normal sensitivity for ever, as a reminder.
So for me, there is no more easy getting out of the tub, and no easy kernel module builds for production use. Not to mention the need to follow module development for patches and rebuilding newer versions, etc...
I do not have to read it (although I understood you the first time). My production server is not going to be a ginipig for developers.
So if I understand you correctly:
If you build and rpm from the current stable release of a package provided to you by the people whom know this package best (its makers), utilizing their automated method that they would need to know for certain works, then install this rpm in a packaged managed system, your system becomes a ginipig for these devels?
Now if someone else takes this same source and builds it, and you install it, you're better off?
Uhm, whatever floats your boat:)
Hi,
On 10/11/2011 06:23 PM, Ljubomir Ljubojevic wrote:
I do not have to read it (although I understood you the first time). My
its strange then you feel compelled to comment on something without making an effort to even see what the other person is talking about.
production server is not going to be a ginipig for developers. And I, so far, rebuilt over 100 packages including newer Qt for C6.
people with the idea of a 'production' setup usually also understand the idea of 'devel' and 'testing'. People who dont have an idea of 'production' dont need to care about or are already isolated from needing to care about 'devel' and 'testing', isnt it ?
Just saying.
- KB
Vreme: 10/12/2011 07:10 AM, Karanbir Singh piše:
Hi,
On 10/11/2011 06:23 PM, Ljubomir Ljubojevic wrote:
I do not have to read it (although I understood you the first time). My
its strange then you feel compelled to comment on something without making an effort to even see what the other person is talking about.
production server is not going to be a ginipig for developers. And I, so far, rebuilt over 100 packages including newer Qt for C6.
people with the idea of a 'production' setup usually also understand the idea of 'devel' and 'testing'. People who dont have an idea of 'production' dont need to care about or are already isolated from needing to care about 'devel' and 'testing', isnt it ?
Just saying.
- KB
Joseph's post was:
Yeah, but generate rpm's for final installation, its trivial. http://www.drbd.org/users-guide-emb/s-build-rpm.html
End of the link says Build Rpm. So, install building tools and environment, and kernel-devel on the production system (5 years ago I was thought that it is not wise to do so), and compile it against your kernel. And there is already built and tested "kmod-" module from ELRepo.
Just so I can answer you (all), I visited that web page and read following: "Note that any kernel upgrade will require you to generate a new drbd-km package to match the new kernel."
So, my assumption that kernel upgrade without rebuilding the module would brake his production server was correct.
I used to use madwifi-kmdl kernel modules for my Atheros wireless radio card, and each time I upgraded kernel I had to upgrade/install new module also. Very tiresome.
Then I studied kmdl vs kmod packages and learned that kmod packages do not need any recompilation after kernel upgrade. They use "weak-update" model (essentially symlinks) as long as new kernel has same ABI as previous ones. Install process of new kernel checks kernel modules of currently installed kernels and symlinks them, avoiding need for building them or installing new packages (hoping they are already available). I was delighted when I saw that ELRepo developers use kmod model, no more messing with kernel modules.
That is why I suggested using ELRepo kernel module package instead of self-built one. Only reason I can see in building your own module is to use those other packages (like drbd-heartbeat).
I hope this finally clears up what I tried to say:
1. Joseph's link clearly stated it was for self building the rpm(s) so I did not need to visit the link to know what is on the page.
2. Developers of kernel module packages rarely use kmod approach in fear people will mess it up (like installing vanila kernel on CentOS sistem and still calling it CentOS,...). Ubuntu and Arch users especially have this problem, so it is safer to build for each new kernel.
3. Kernel module re-packagers from ELRepo have luxury of safely offering kmod packages for EL kernels, and I believe this is safest and best approach.
Hi Ljubomir,
i am completely confused now. With elrepo u dont mean "epel.repo" or? How do i enable this "elrepo" in Centos?
marko
Am 12.10.2011 12:16, schrieb Ljubomir Ljubojevic:
Vreme: 10/12/2011 07:10 AM, Karanbir Singh piše:
Hi,
On 10/11/2011 06:23 PM, Ljubomir Ljubojevic wrote:
I do not have to read it (although I understood you the first time). My
its strange then you feel compelled to comment on something without making an effort to even see what the other person is talking about.
production server is not going to be a ginipig for developers. And I, so far, rebuilt over 100 packages including newer Qt for C6.
people with the idea of a 'production' setup usually also understand the idea of 'devel' and 'testing'. People who dont have an idea of 'production' dont need to care about or are already isolated from needing to care about 'devel' and 'testing', isnt it ?
Just saying.
- KB
Joseph's post was:
Yeah, but generate rpm's for final installation, its trivial. http://www.drbd.org/users-guide-emb/s-build-rpm.html
End of the link says Build Rpm. So, install building tools and environment, and kernel-devel on the production system (5 years ago I was thought that it is not wise to do so), and compile it against your kernel. And there is already built and tested "kmod-" module from ELRepo.
Just so I can answer you (all), I visited that web page and read following: "Note that any kernel upgrade will require you to generate a new drbd-km package to match the new kernel."
So, my assumption that kernel upgrade without rebuilding the module would brake his production server was correct.
I used to use madwifi-kmdl kernel modules for my Atheros wireless radio card, and each time I upgraded kernel I had to upgrade/install new module also. Very tiresome.
Then I studied kmdl vs kmod packages and learned that kmod packages do not need any recompilation after kernel upgrade. They use "weak-update" model (essentially symlinks) as long as new kernel has same ABI as previous ones. Install process of new kernel checks kernel modules of currently installed kernels and symlinks them, avoiding need for building them or installing new packages (hoping they are already available). I was delighted when I saw that ELRepo developers use kmod model, no more messing with kernel modules.
That is why I suggested using ELRepo kernel module package instead of self-built one. Only reason I can see in building your own module is to use those other packages (like drbd-heartbeat).
I hope this finally clears up what I tried to say:
- Joseph's link clearly stated it was for self building the rpm(s)
so I did not need to visit the link to know what is on the page.
- Developers of kernel module packages rarely use kmod approach in
fear people will mess it up (like installing vanila kernel on CentOS sistem and still calling it CentOS,...). Ubuntu and Arch users especially have this problem, so it is safer to build for each new kernel.
- Kernel module re-packagers from ELRepo have luxury of safely
offering kmod packages for EL kernels, and I believe this is safest and best approach.
--
Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS, Mikrotik and CentOS/RHEL/Linux consultant _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
From: Marko Weber weber@zackbummfertig.de
i am completely confused now. With elrepo u dont mean "epel.repo" or? How do i enable this "elrepo" in Centos?
Google 'elrepo' and it is the first answer...
JD
Marko Weber wrote:
i am completely confused now. With elrepo u dont mean "epel.repo" or? How do i enable this "elrepo" in Centos?
On Oct 11, 2011, at 4:02 PM, Ljubomir Ljubojevic office@plnet.rs wrote:
Bear in mind that RHEL kernel is not stock kernel, there are number of back-ported patches in it. It is safer to use a package with applied RHEL specific patches (if necessary) done by people working with RHEL kernel regularly.
Starting in CentOS 6 one cannot see the patches that are applied to the kernel by upstream as they are slip streamed into the kernel source tree.
Therefore one should test, test, test, test...
BTW Building the RPM directly from DRBD sources is fully supported by Linbit. Installing an RPM compiled by a third party, not so much.
-Ross
Hello Joesph,
i am a gentoo child. So, do i have to download latest drbd source package, then untar , and do this =
{ If you are about to build RPMs for both the DRBD userspace utilities and the kernel module, use: }
$ ./configure --enable-spec --with-km $ make tgz $ cp drbd*.tar.gz `rpm -E _sourcedir` $ rpmbuild -bb drbd.spec $ rpmbuild -bb drbd-kernel.spec
This would be right way for me?
And waht do i have to do on updates=? Same Procedure?
Am 11.10.2011 19:47, schrieb Joseph L. Casale:
Each thing you install by hand brake this.
Did you actually read my post and the link? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Am 11.10.2011 11:27, schrieb Marko Weber:
Do i have to enable the epel-test repo to get itß But test sounds not stable for me and we switched to centos for stability.
anyone here can help me or give me any hints on drbd on centos 6?
Do i have to compile by hand?
No, use elrepo, do not compile and build a rpm by yourself. This was already done be elrepo.
Look here how to enable it: http://wiki.centos.org/AdditionalResources/Repositories
Rainer
-
Andreas Reschke -
John Doe -
Joseph L. Casale -
Karanbir Singh -
Ljubomir Ljubojevic -
Marko Weber -
Nicolas Thierry-Mieg -
Rainer Traut -
Ross Walker