Hi,
I am working on CentOS 6.5 which has 2.6.32-431 kernel.
I have a problem with my driver and I need to enable Kernel-Memory
leak in the kernel for which I will have to recompile the kernel.
I get the kernel source tree from the the source rpm for my running
kernel from below link-
http://vault.centos.org/6.5/updates/Source/SPackages/kernel-2.6.32-431.11.2…
and I try to build the kernel according to the below link on CentOS Wiki -
http://www.centos.org/docs/rhel-sag-en-3/s1-custom-kernel-modularized.html
according to which it tells me , after make menuconfig( and
customizing my configuration), I need to follow the following steps-
1. make bzImage
2. make modules
3. make modules_install
4. make install
but I get errors in the first step only-(make bzImage)
Kindly suggest me as to what I am doing wrong.
Regards,
Saket SInha
Forwarding this here - we'd like to get some CentOS storage SIG packaging done.
Free lunch and happy hour drinks will be served on-site.
-JM
----- Forwarded Message -----
From: "John Mark Walker" <johnmark(a)gluster.org>
To: "Gluster Devel" <gluster-devel(a)nongnu.org>
Sent: Monday, March 24, 2014 12:01:37 PM
Greetings,
Red Hat Storage is sponsoring Data Liberate: a Storage Hackathon and Mixer in San Francisco on Sunday, April 13. Would be great to get general participation from people in the area, as well as some hacking on big data, cloud and virtualization management integration.
RSVP at http://dataliberate.eventbrite.com/
If you're interested in sponsoring, contact me off-list.
Description:
Hack all day, stay for the prizes and party!
Modern cloud workloads demand storage services that are easily consumable and available to a variety of platforms. We need to liberate our data from the shackles of the big, dumb (proprietary) storage box and move it into the 21st century. So come one, come all storage, cloud and big data developers and devops practitioners. The Data Liberate Hackathon will be a chance for developers in disparate worlds to link their applications, infrastructure and other code with storage services.
And did I mention fabulous prizes? And drinks?
_______________________________________________
Gluster-devel mailing list
Gluster-devel(a)nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
@eduardo
Yes you are right. You are not crazy dreamer ! A midrange UTM and uper
should support this features and another...
The technical topic will open later, for now we are talking about general
subjects !
Are goal is CentOS Security SIG ! A version of CentOS that provide features
for network security and my topics to discuss are:
- Do we need this SIG in CentOS ecosystem?
- Is it any parallel project in CentOS right now?
- Is CentOS a suitable base to provide and create this project?
- and anything you think...
:-)
On Mar 22, 2014 3:15 AM, "Eduardo Kaftanski" <ekaftan(a)gmail.com> wrote:
Can I elaborate a bit on what I would like this SIG to provide?
-An integrated web console for object oriented (objects being servers,
pc-workstations and people) network access manager. This
console would get installed in a centralized server (maybe a
small VM on whatever virtualization system you have)
-A small dedicated CentOS server that you can install over comodity
hardware. This would be an 'almost zero config' server. You only need
to specify the IP for the admin interface and the IP for the central
admin-server
-This small servers can act as firewalls, mail proxys, antiviruses,
web proxies, DNS, etc.
-Small network? One small VM for the adminserver + one box doing
firewall, proxy, mx, snort, etc.
-Growing up? install a second box. Select proxy off for box 1 on the admin
console, select proxy on on the second box. Select 'transparent on'. Select
antivirus on. Click apply. Box one is no longer your proxy but transparently
redirects proxy traffic to box two, now your proxy.
yes, I am a crazy dreamer, but its like Asterisk... if you want a very small
cheap PBX you can buy a Panasonic for US$500. You need Asterisk when you
want the strange and crazy features.
you dont install a CentOS firewall for a tiny network. A small WRT box
works better
is more stable and its way cheaper. You need a CentOS box when you are doing
strange things, like balancinh, HA, multiview DNS, multiple ISP links,
openvpn servers,
ipsec, etc..
Ah... at least down here customers place MUCH more weight on the ability to
selectively block access to their own people than protecting from
outside attacks
and 90% of the configurations I make have no external access at all. All
they
care is to be able to allow and block youtube and facebook with a mouse
click.
On Fri, Mar 21, 2014 at 6:36 PM, Shafiee Roozbeh
<roozbeh.shafiee(a)gmail.com> wrote:
> @Manuel
> Our goal is not IPtables rule generator ! We are talking about a version
of
> CentOS that provide unified threat management which will be install on a
> device or server. On this machine except iptables we need proxy and
caching
> service like squid and some tools else.
> Firewalling is one of our goal...
> :-)
>
> On Mar 22, 2014 1:51 AM, "Manuel Wolfshant" <wolfy(a)nobugconsulting.ro>
> wrote:
>>
>>
>>
>> On 21 martie 2014 22:50:39 EET, Shafiee Roozbeh
>> <roozbeh.shafiee(a)gmail.com> wrote:
>> >@Christoph
>> >Yes, I worked with this tool sometimes ago but I think that a web GUI
>> >is
>> >better for an administrator and our project because:
>> >
>> >- An administrator maybe doesn't access to a Linux desktop to work
>> >with
>> >fwbuilder but with his/her tablet or smartphone or even a Microsoft
>> >Windows
>> >OS can work with web GUI
>> >
>> If you can expose a web interface, you can expose ssh /VNC/VPN whatever
to
>> a machine where fwbuilder can run. Google Play provides apps for all of
>> those and then some more
>>
>> >- Designing and development of web GUI with HTML/CSS is faster and
>> >easier
>> >that using a framework like Qt or GTK
>> >
>> >- The world is going to web !
>> And fwbuilder can run on your management workstation and push the rules
to
>> ANY server. Including the web server that you mentioned :)
>>
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-devel
>
--
Eduardo Kaftanski
eduardo(a)kdi.cl
ekaftan(a)gmail.com
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
Actually I mean HA
my idea about this SIG is create HA Cluster spin of centos with
installation media that has cli interface or web interface to perform and
configure centos for HA usage.
HA Cluster spin of centos with ISO installation media is my goal !
--
Roozbeh Shafiee
Linux/BSD System Administrator and Python Developer
RoozbehShafiee.Com
Hi
Something that keeps coming up is how far can we minimalise an Instance
/ Image / Installer before we cant call it CentOS anymore. In the past,
what we have generally stuck with is:
- CentOS Shipped kernel
- Initscripts
- functional yum
- functional openssh-server
- atleast all of @base
however, in some cases, openssh-server might not be needed, and
initscripts has a fairly long dep tree, similarly making yum work needs
a few things. Can we get away with losing yum as an example and
replacing it with a script that says 'need yum? I can download and
install it for you' and have it hit mirror.centos.org for static yum and
yum dep urls ?
similarly, should nobase and nocore be acceptable ?
the aim being to setup a base image, that is under 150mb to download and
deploy.
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
I've volunteered to help maintain official CentOS Docker (
https://www.docker.io/) images, and Karanbir suggested I email the list to
"thrash out what we need at the infra end to achieve these images."
Currently, there are 'centos' images available in the top-level Docker
registry namespace, but these are maintained by dotcloud. I think we can
do better. :)
As I see it, there are two ways we can do this:
1. Use ami-creator (https://github.com/katzj/ami-creator), or something
derived from it, to build Docker images from a kickstart file. This is how
CentOS AMIs are currently built.
Pros: Consistent with how AMIs are usually built; Kickstart is a known
entity.
Cons: ami-creator won't actually work for us as-is; requires a full
kickstart config.
2. Use the mkimage-yum.sh script from Docker (
https://github.com/dotcloud/docker/blob/master/contrib/mkimage-yum.sh),
customized as necessary to produce a minimal base image.
Pros: Consistent with how Docker images are usually built; we can
contribute changes to mkimage-yum.sh upstream to help other Yum-based
distros; only requires a yum config.
Cons: Requires changing a shell script to make changes to the base image,
not just a Kickstart.
Unfortunately, Docker Trusted Build (
http://blog.docker.io/2013/11/introducing-trusted-builds/) can't be used
for base images, AFAICT.
In either case, we'll need a git repo to hold the code and configs used to
build the images. If we follow the example of the official CentOS AMIs (
http://wiki.centos.org/Cloud/AWS), it should be sufficient to provide a
reasonably up-to-date base image ("latest" or "nightly" or similar), and a
few recent dot releases. Of course, once CentOS 7 is released we'll need
to do that for both 6 and 7, but that shouldn't be difficult if we do this
right.
Thoughts on process and/or infrastructure?
--
Chris St. Pierre
Do you use TencentQQ?
------------------ Original ------------------
From: "centos-devel-request";<centos-devel-request(a)centos.org>;
Date: Mon, Mar 17, 2014 08:00 PM
To: "centos-devel"<centos-devel(a)centos.org>;
Subject: CentOS-devel Digest, Vol 109, Issue 16
Send CentOS-devel mailing list submissions to
centos-devel(a)centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-devel
or, via email, send a message with subject or body 'help' to
centos-devel-request(a)centos.org
You can reach the person managing the list at
centos-devel-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-devel digest..."
Today's Topics:
1. CentOS Docker images (Chris St. Pierre)
----------------------------------------------------------------------
Message: 1
Date: Sun, 16 Mar 2014 15:30:04 -0400
From: "Chris St. Pierre" <chris.a.st.pierre(a)gmail.com>
Subject: [CentOS-devel] CentOS Docker images
To: centos-devel(a)centos.org
Message-ID:
<CAGwiO7ZcLRbD=_ZyxecK716NOU3VJ7i69K6vf3zfPmn-_D8-Tw(a)mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I've volunteered to help maintain official CentOS Docker (
https://www.docker.io/) images, and Karanbir suggested I email the list to
"thrash out what we need at the infra end to achieve these images."
Currently, there are 'centos' images available in the top-level Docker
registry namespace, but these are maintained by dotcloud. I think we can
do better. :)
As I see it, there are two ways we can do this:
1. Use ami-creator (https://github.com/katzj/ami-creator), or something
derived from it, to build Docker images from a kickstart file. This is how
CentOS AMIs are currently built.
Pros: Consistent with how AMIs are usually built; Kickstart is a known
entity.
Cons: ami-creator won't actually work for us as-is; requires a full
kickstart config.
2. Use the mkimage-yum.sh script from Docker (
https://github.com/dotcloud/docker/blob/master/contrib/mkimage-yum.sh),
customized as necessary to produce a minimal base image.
Pros: Consistent with how Docker images are usually built; we can
contribute changes to mkimage-yum.sh upstream to help other Yum-based
distros; only requires a yum config.
Cons: Requires changing a shell script to make changes to the base image,
not just a Kickstart.
Unfortunately, Docker Trusted Build (
http://blog.docker.io/2013/11/introducing-trusted-builds/) can't be used
for base images, AFAICT.
In either case, we'll need a git repo to hold the code and configs used to
build the images. If we follow the example of the official CentOS AMIs (
http://wiki.centos.org/Cloud/AWS), it should be sufficient to provide a
reasonably up-to-date base image ("latest" or "nightly" or similar), and a
few recent dot releases. Of course, once CentOS 7 is released we'll need
to do that for both 6 and 7, but that shouldn't be difficult if we do this
right.
Thoughts on process and/or infrastructure?
--
Chris St. Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-devel/attachments/20140316/e56a5ee…
------------------------------
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
End of CentOS-devel Digest, Vol 109, Issue 16
*********************************************
.
Hi,
Does anyone, with beta version of CentOS 7 installed, could describe
the installer artwork requirements? I've downloaded the
http://ftp.redhat.com/redhat/rhel/beta/7/source/SRPMS/redhat-logos-69.1.9-1…
file and didn't find any image for anaconda but the
syslinux-splash.png file inside it. Is this the only image shown in
the CentOS 7 installation process or there is any other image shown in
the process. Any idea of related source packages to take a look in?
Best Regards,
al.