Hi!
I'm wondering why CONFIG_CC_STACKPROTECTOR is disabled on openSUSE.
Debian and Fedora seem to enabled it per default.
What's the deal?
--
Thanks,
//richard
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org
Hello,
I have a doubt in the correct procedure for compiling the operating
system kernel in OpenSUSE.
I have sought help in forums, but nobody could help me, so I'm turning to you.
I hope you can understand me, my English is not very good.
I'm using version 12.1 of the "OpenSUSE" with kernel "1.3.10-1.16-default."
After downloading the kernel source code and all the build
dependencies via "YAST", run the following commands as "root":
cd /usr/src/linux-3.1.10-1.16/;
make clean;
make mrproper;
cp /boot/config-3.1.10-1.16-default ./.config;
make menuconfig;
At this stage I would not change any configuration of the kernel, just
select the file ".config" and choose a name for the kernel that will
be compiled. After these procedures, I save and start the build
process via the command:
make dep;
make rpm;
After waiting for the build is done, I checked the package ".rpm"
generated has a size of 317 MB, and the repository of the "OpenSUSE",
the size of this file is approximately 37 MB.
After installing the kernel compiled, I noticed no difference in the
number of generated binary files, only in their size.
So, I wonder, because the kernel is compiled much mair than the kernel
provided by the repository "OpenSUSE"?, And I'm using the same
configuration.
And what is the correct way to compile the kernel in OpenSUSE?. So I
can generate a size compatible with the repository.
Thank you for the information,
João
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org
Hi,
The patch below removes some optional parts from the config that makes it
build again with the 3.6.rc3.
I'm currently burn-in testing this kernel, so far it looks good.
Please apply.
Thanks,
Dirk
Hi all,
As part of one of the Linux kernel Summit discussions today, it was
brought up that after a kernel is released (for example 3.5), it's a bit
too late to be doing testing to see how well it is working out. The .0
release is usually a bit rough, and it takes until the .1 or .2 release
to get most major issues out of the way.
So, the kernel developers would like to get a wider range of testing,
and one thing proposed would be to have rolling distros switch their
kernel over a bit earlier to the new release than they had been doing.
Specifically, around the -rc5 point in time would be great. That way,
any reported regressions could be fixed sooner and get into the final .0
release for everyone to use.
Now this does place a bit of a larger burden on the users of those
distros to be diligent in reporting problems, and the distro engineers
to report the issues upstream as well, but it sounds like a reasonable
thing to try out.
So, for the next kernel release, I'm thinking of switching the kernel in
Tumbleweed over to 3.6 at the -rc5 timeframe. Does anyone strongly
object to this happening?
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org
* Achim Gratz <Stromeko(a)nexgo.de> [08-28-12 13:33]:
> Greg KH writes:
> > So, the kernel developers would like to get a wider range of testing,
> > and one thing proposed would be to have rolling distros switch their
> > kernel over a bit earlier to the new release than they had been doing.
> > Specifically, around the -rc5 point in time would be great. That way,
> > any reported regressions could be fixed sooner and get into the final .0
> > release for everyone to use.
>
> While I understand the idea, I am one of those Tumbleweed users that do
> not have a dedicated test machine or even test partition so I'd really
> have to think about sticking with Tumbleweed if this became the new
> policy. I usually have the three latest kernels installed, so I can go
> back if one of the updates makes problems, but there are times where I
> wouldn't want to bear this added risk. Besides, the way Tumbleweed was
> advertised in the past does not really fit to what it would become with
> that change. I'd suggest putting the not-quite released kernel stuff
> into a different or add-on repo so that everyone can opt in or out by
> activating the correct repo.
>
this appears a *reasonable* approach, with wide publication
--
(paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2http://en.opensuse.org openSUSE Community Member
Registered Linux User #207535 @ http://linuxcounter.net
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org