FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 01-10-2012, 10:33 PM
Ben Hutchings
 
Default

On Tue, Jan 10, 2012 at 11:46:10PM +0100, Marcus Osdoba wrote:
> Am 10.01.2012 02:42, schrieb Ben Hutchings:
> >We need to make a decision soon on whether we will use Linux 3.2 for
> >wheezy or wait for a later release. Whichever one we choose, we need to
> >make sure someone (possibly one of us) maintains a longterm branch for
> >it. I am strongly disinclined to choose a version that puts us on our
> >own, and therefore I would prefer to use Linux 3.2 along with Ubuntu.
> >
> Hi, I'm just a user, but using 3.2 along with Ubuntu LTS looks more
> than reasonable to me.
> Unfortunatly, upstream maintains only 3.0. Is there any longterm
> version beyond 3.0 in sight, which might be an adequate alternative
> for Wheezy? If not, the sum of Debian/UbuntuLTS installations should
> have a critical mass to justify the maintenance of a 3.2-DEBline on
> their own without offcial "support" from upstream.
[...]

There is no restriction that only Greg K-H can maintain longterm
series; in fact he will be handing over 2.6.32 shortly. And
'upstream' isn't an exclusive club; many kernel team members in
both distributions are upstream developers too.

Whatever mainline version we start with, I will try to make sure that
there is a longterm series based on it. If necessary, I will
volunteer to do that myself, but I would rather find some other mug
to do it!

Ben.

--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120110233304.GV20752@decadent.org.uk">http://lists.debian.org/20120110233304.GV20752@decadent.org.uk
 
Old 01-11-2012, 08:07 AM
Arch Website Notification
 
Default

=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 4 fully signed off packages
* 31 packages missing signoffs
* 5 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)



== Incomplete signoffs for [community] (29 total) ==

* dsniff-2.4b1-21 (i686)
0/2 signoffs
* exim-4.77-2 (i686)
0/2 signoffs
* expac-0.07-1 (i686)
0/2 signoffs
* fcron-3.0.6-5 (i686)
0/2 signoffs
* libgda3-3.1.5-11 (i686)
0/2 signoffs
* librcc-0.2.6-5 (i686)
0/2 signoffs
* ndiswrapper-1.57-3 (i686)
0/2 signoffs
* packagekit-0.6.19-5 (i686)
0/2 signoffs
* perl-berkeleydb-0.50-2 (i686)
0/2 signoffs
* pkgtools-23-3 (i686)
0/2 signoffs
* poedit-1.4.6.1-6 (i686)
0/2 signoffs
* python-bsddb-5.2.0-3 (i686)
0/2 signoffs
* tomoyo-tools-2.5.0.20111025-1 (i686)
0/2 signoffs
* vdrift-2011.10.22-3 (i686)
0/2 signoffs
* virtualbox-modules-4.1.8-2 (i686)
0/2 signoffs
* xemacs-21.5.31-4 (i686)
0/2 signoffs
* dsniff-2.4b1-21 (x86_64)
0/2 signoffs
* exim-4.77-2 (x86_64)
0/2 signoffs
* fcron-3.0.6-5 (x86_64)
0/2 signoffs
* libgda3-3.1.5-11 (x86_64)
0/2 signoffs
* librcc-0.2.6-5 (x86_64)
0/2 signoffs
* ndiswrapper-1.57-3 (x86_64)
0/2 signoffs
* packagekit-0.6.19-5 (x86_64)
0/2 signoffs
* perl-berkeleydb-0.50-2 (x86_64)
0/2 signoffs
* poedit-1.4.6.1-6 (x86_64)
0/2 signoffs
* python-bsddb-5.2.0-3 (x86_64)
0/2 signoffs
* tomoyo-tools-2.5.0.20111025-1 (x86_64)
0/2 signoffs
* vdrift-2011.10.22-3 (x86_64)
0/2 signoffs
* xemacs-21.5.31-4 (x86_64)
0/2 signoffs

== Incomplete signoffs for [unknown] (2 total) ==

* percona-server-5.5.18_rel23.0-1 (i686)
0/2 signoffs
* percona-server-5.5.18_rel23.0-1 (x86_64)
1/2 signoffs


== Completed signoffs (4 total) ==

* pacman-contrib-4.0.1-1 (any)
* expac-0.07-1 (x86_64)
* pkgtools-23-3 (x86_64)
* virtualbox-modules-4.1.8-2 (x86_64)


== All packages in [community-testing] for more than 14 days (5 total) ==

* expac-0.07-1 (i686), since 2011-10-13
* expac-0.07-1 (x86_64), since 2011-10-13
* pacman-contrib-4.0.1-1 (any), since 2011-11-25
* percona-server-5.5.18_rel23.0-1 (i686), since 2011-12-23
* percona-server-5.5.18_rel23.0-1 (x86_64), since 2011-12-23


== Top five in signoffs in last 24 hours ==

1. tomegun - 11 signoffs
2. dan - 4 signoffs
 
Old 01-11-2012, 08:07 AM
Arch Website Notification
 
Default

=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 2 new packages in last 24 hours
* 2 known bad packages
* 0 packages not accepting signoffs
* 13 fully signed off packages
* 69 packages missing signoffs
* 3 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)


== New packages in [testing] in last 24 hours (2 total) ==

* btrfs-progs-0.19.20120110-1 (i686)
* btrfs-progs-0.19.20120110-1 (x86_64)


== Incomplete signoffs for [core] (12 total) ==

* iproute2-3.2.0-1 (i686)
1/2 signoffs
* kernel26-lts-2.6.32.53-1 (i686)
0/2 signoffs
* libsasl-2.1.23-9 (i686)
0/2 signoffs
* openldap-2.4.28-2 (i686)
0/2 signoffs
* perl-5.14.2-6 (i686)
1/2 signoffs
* db-5.3.15-1 (x86_64)
1/2 signoffs
* iproute2-3.2.0-1 (x86_64)
1/2 signoffs
* kernel26-lts-2.6.32.53-1 (x86_64)
0/2 signoffs
* libsasl-2.1.23-9 (x86_64)
0/2 signoffs
* openldap-2.4.28-2 (x86_64)
0/2 signoffs
* pam-1.1.5-2 (x86_64)
1/2 signoffs
* perl-5.14.2-6 (x86_64)
0/2 signoffs

== Incomplete signoffs for [extra] (55 total) ==

* apr-util-1.3.12-5 (i686)
0/2 signoffs
* bogofilter-1.2.2-4 (i686)
0/2 signoffs
* claws-mail-3.8.0-2 (i686)
0/2 signoffs
* claws-mail-extra-plugins-3.8.0-2 (i686)
1/2 signoffs
* cmake-2.8.7-2 (i686)
0/2 signoffs
* cyrus-sasl-2.1.23-9 (i686)
0/2 signoffs
* evolution-data-server-3.2.3-2 (i686)
0/2 signoffs
* evolution-exchange-3.2.1-2 (i686)
0/2 signoffs
* evolution-groupwise-3.2.1-2 (i686)
0/2 signoffs
* fcpci-31107-66 (i686)
0/2 signoffs
* fcpcmcia-31107-62 (i686)
0/2 signoffs
* gvfs-1.10.1-2 (i686)
0/2 signoffs
* hplip-3.11.12-1 (i686)
0/2 signoffs
* hydrogen-0.9.5-2 (i686)
0/2 signoffs
* java7-openjdk-7.b147_2.0-5 (i686)
1/2 signoffs
* kdeutils-4.7.4-2 (i686)
0/2 signoffs
* kmod-3-5 (i686)
0/2 signoffs
* libetpan-1.0-4 (i686)
0/2 signoffs
* libreoffice-3.4.4-5 (i686)
0/2 signoffs
* lirc-1:0.9.0-10 (i686)
0/2 signoffs
* moc-20110528-5 (i686)
0/2 signoffs
* nvidia-290.10-2 (i686)
0/2 signoffs
* php-5.3.8-7 (i686)
0/2 signoffs
* postfix-2.8.7-2 (i686)
0/2 signoffs
* redland-1:1.0.15-3 (i686)
0/2 signoffs
* ruby-1.9.3_p0-3 (i686)
0/2 signoffs
* subversion-1.7.2-2 (i686)
0/2 signoffs
* totem-plparser-2.32.6-2 (i686)
0/2 signoffs
* apr-util-1.3.12-5 (x86_64)
0/2 signoffs
* bogofilter-1.2.2-4 (x86_64)
0/2 signoffs
* claws-mail-3.8.0-2 (x86_64)
0/2 signoffs
* claws-mail-extra-plugins-3.8.0-2 (x86_64)
1/2 signoffs
* cmake-2.8.7-2 (x86_64)
1/2 signoffs
* cyrus-sasl-2.1.23-9 (x86_64)
0/2 signoffs
* evolution-data-server-3.2.3-2 (x86_64)
0/2 signoffs
* evolution-exchange-3.2.1-2 (x86_64)
0/2 signoffs
* evolution-groupwise-3.2.1-2 (x86_64)
0/2 signoffs
* fcpci-31107-66 (x86_64)
0/2 signoffs
* fcpcmcia-31107-62 (x86_64)
0/2 signoffs
* gvfs-1.10.1-2 (x86_64)
1/2 signoffs
* hplip-3.11.12-1 (x86_64)
1/2 signoffs
* hydrogen-0.9.5-2 (x86_64)
0/2 signoffs
* java7-openjdk-7.b147_2.0-5 (x86_64)
1/2 signoffs
* kdeutils-4.7.4-2 (x86_64)
1/2 signoffs
* kmod-3-5 (x86_64)
1/2 signoffs
* libetpan-1.0-4 (x86_64)
0/2 signoffs
* libreoffice-3.4.4-5 (x86_64)
0/2 signoffs
* lirc-1:0.9.0-10 (x86_64)
0/2 signoffs
* moc-20110528-5 (x86_64)
0/2 signoffs
* php-5.3.8-7 (x86_64)
0/2 signoffs
* postfix-2.8.7-2 (x86_64)
0/2 signoffs
* redland-1:1.0.15-3 (x86_64)
0/2 signoffs
* ruby-1.9.3_p0-3 (x86_64)
0/2 signoffs
* subversion-1.7.2-2 (x86_64)
0/2 signoffs
* totem-plparser-2.32.6-2 (x86_64)
0/2 signoffs

== Incomplete signoffs for [unknown] (2 total) ==

* btrfs-progs-0.19.20120110-1 (i686)
0/2 signoffs
* btrfs-progs-0.19.20120110-1 (x86_64)
0/2 signoffs


== Completed signoffs (13 total) ==

* mkinitcpio-0.8.1-1 (any)
* coreutils-8.15-1 (i686)
* db-5.3.15-1 (i686)
* linux-3.2-2 (i686)
* pacman-4.0.1-3 (i686)
* pam-1.1.5-2 (i686)
* coreutils-8.15-1 (x86_64)
* linux-3.2-2 (x86_64)
* pacman-4.0.1-3 (x86_64)
* namcap-3.2.1-1 (any)
* pyalpm-0.5.3-1 (i686)
* nvidia-290.10-2 (x86_64)
* pyalpm-0.5.3-1 (x86_64)


== All packages in [testing] for more than 14 days (3 total) ==

* pyalpm-0.5.3-1 (i686), since 2011-10-15
* pyalpm-0.5.3-1 (x86_64), since 2011-10-15
* namcap-3.2.1-1 (any), since 2011-10-20


== Top five in signoffs in last 24 hours ==

1. tomegun - 11 signoffs
2. dan - 4 signoffs
 
Old 01-11-2012, 08:36 AM
Stefan Bader
 
Default

On 09.01.2012 11:20, Serge Hallyn wrote:
> Hi Stefan,
>
> One of our goals for 12.04 is to have an unmodified precise image
> boot in lxc. We will need this patch in the kernel in order to
> be able to do that.
>
> It's gone through quite a few feedback cycles and has Oleg's
> ack.
>
> This email has a testcase.
>
> thanks,
> -serge
>
> ----- Forwarded message from Daniel Lezcano <daniel.lezcano@free.fr> -----
>
> Date: Thu, 5 Jan 2012 10:06:49 +0100
> From: Daniel Lezcano <daniel.lezcano@free.fr>
> To: akpm@linux-foundation.org
> Cc: serge.hallyn@canonical.com, oleg@redhat.com, containers@lists.linux-foundation.org, gkurz@fr.ibm.com,
> linux-kernel@vger.kernel.org, mtk.manpages@gmail.com
> Subject: [PATCH 0/1][V5] Handle reboot in a child pid namespace
>
>
> ChangeLog:
> ==========
>
> * V5
> - make static inline function for reboot_pid_ns to return 0 when
> CONFIG_PID_NS is off and do the pid_namespace pointer comparison
> inside the function. That makes the compiler to remove this portion
> of code when CONFIG_PID_NS is not enabled.
>
> * V4
> - store the signal number the child pid namespace init should
> exit from. It is simpler, cleaner, and does not add more encoding
> bits to the exit code of the process.
>
> * V3
> - removed lock and serialization of pid_ns_reboot
>
> * V2
> - added a lock for the pid namespace to prevent racy call
> to the 'reboot' syscall
> - Moved 'reboot' command assigned in zap_pid_ns_processes
> instead of wait_task_zombie
> - added tasklist lock around force_sig
> - added do_exit in pid_ns_reboot
> - used task_active_pid_ns instead of declaring a new variable in sys_reboot
> - moved code up before POWER_OFF changed to HALT in sys_reboot
>
>
> Test case:
> ==========
>
> #include <alloca.h>
> #include <stdio.h>
> #include <sched.h>
> #include <unistd.h>
> #include <signal.h>
> #include <sys/reboot.h>
> #include <sys/types.h>
> #include <sys/wait.h>
>
> #include <linux/reboot.h>
>
> static int do_reboot(void *arg)
> {
> int *cmd = arg;
>
> if (reboot(*cmd))
> printf("failed to reboot(%d): %m
", *cmd);
> }
>
> int test_reboot(int cmd, int sig)
> {
> long stack_size = 4096;
> void *stack = alloca(stack_size) + stack_size;
> int status;
> pid_t ret;
>
> ret = clone(do_reboot, stack, CLONE_NEWPID | SIGCHLD, &cmd);
> if (ret < 0) {
> printf("failed to clone: %m
");
> return -1;
> }
>
> if (wait(&status) < 0) {
> printf("unexpected wait error: %m
");
> return -1;
> }
>
> if (!WIFSIGNALED(status)) {
> printf("child process exited but was not signaled
");
> return -1;
> }
>
> if (WTERMSIG(status) != sig) {
> printf("signal termination is not the one expected
");
> return -1;
> }
>
> return 0;
> }
>
> int main(int argc, char *argv[])
> {
> int status;
>
> status = test_reboot(LINUX_REBOOT_CMD_RESTART, SIGHUP);
> if (status < 0)
> return 1;
> printf("reboot(LINUX_REBOOT_CMD_RESTART) succeed
");
>
> status = test_reboot(LINUX_REBOOT_CMD_RESTART2, SIGHUP);
> if (status < 0)
> return 1;
> printf("reboot(LINUX_REBOOT_CMD_RESTART2) succeed
");
>
> status = test_reboot(LINUX_REBOOT_CMD_HALT, SIGINT);
> if (status < 0)
> return 1;
> printf("reboot(LINUX_REBOOT_CMD_HALT) succeed
");
>
> status = test_reboot(LINUX_REBOOT_CMD_POWER_OFF, SIGINT);
> if (status < 0)
> return 1;
> printf("reboot(LINUX_REBOOT_CMD_POWERR_OFF) succeed
");
>
> status = test_reboot(LINUX_REBOOT_CMD_CAD_ON, -1);
> if (status >= 0) {
> printf("reboot(LINUX_REBOOT_CMD_CAD_ON) should have failed
");
> return 1;
> }
> printf("reboot(LINUX_REBOOT_CMD_CAD_ON) has failed as expected
");
>
> return 0;
> }
>
> Daniel Lezcano (1):
> Add reboot_pid_ns to handle the reboot syscall
>
> include/linux/pid_namespace.h | 8 +++++++-
> kernel/pid_namespace.c | 33 +++++++++++++++++++++++++++++++++
> kernel/sys.c | 3 +++
> 3 files changed, 43 insertions(+), 1 deletions(-)
>

Looking at the patch, I do not think it will cause any issues for normal use, so
I do not see a reason to not take it. We still have a bit of time, though. And
if there is a chance that it will land in 3.3 then it will be even better
because its then rather a cherry-pick. And we should have a bug report on
launchpad for this to track the thing.

-Stefan

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 01-11-2012, 09:20 AM
Serge Hallyn
 
Default

Quoting Stefan Bader (stefan.bader@canonical.com):
> On 09.01.2012 11:20, Serge Hallyn wrote:
> > Hi Stefan,
> >
> > One of our goals for 12.04 is to have an unmodified precise image
> > boot in lxc. We will need this patch in the kernel in order to
> > be able to do that.
> >
> > It's gone through quite a few feedback cycles and has Oleg's
> > ack.
> >
> > This email has a testcase.
> >
> > thanks,
> > -serge
> >
> > ----- Forwarded message from Daniel Lezcano <daniel.lezcano@free.fr> -----
> >
> > Date: Thu, 5 Jan 2012 10:06:49 +0100
> > From: Daniel Lezcano <daniel.lezcano@free.fr>
> > To: akpm@linux-foundation.org
> > Cc: serge.hallyn@canonical.com, oleg@redhat.com, containers@lists.linux-foundation.org, gkurz@fr.ibm.com,
> > linux-kernel@vger.kernel.org, mtk.manpages@gmail.com
> > Subject: [PATCH 0/1][V5] Handle reboot in a child pid namespace
> >
> >
> > ChangeLog:
> > ==========
> >
> > * V5
> > - make static inline function for reboot_pid_ns to return 0 when
> > CONFIG_PID_NS is off and do the pid_namespace pointer comparison
> > inside the function. That makes the compiler to remove this portion
> > of code when CONFIG_PID_NS is not enabled.
> >
> > * V4
> > - store the signal number the child pid namespace init should
> > exit from. It is simpler, cleaner, and does not add more encoding
> > bits to the exit code of the process.
> >
> > * V3
> > - removed lock and serialization of pid_ns_reboot
> >
> > * V2
> > - added a lock for the pid namespace to prevent racy call
> > to the 'reboot' syscall
> > - Moved 'reboot' command assigned in zap_pid_ns_processes
> > instead of wait_task_zombie
> > - added tasklist lock around force_sig
> > - added do_exit in pid_ns_reboot
> > - used task_active_pid_ns instead of declaring a new variable in sys_reboot
> > - moved code up before POWER_OFF changed to HALT in sys_reboot
> >
> >
> > Test case:
> > ==========
> >
> > #include <alloca.h>
> > #include <stdio.h>
> > #include <sched.h>
> > #include <unistd.h>
> > #include <signal.h>
> > #include <sys/reboot.h>
> > #include <sys/types.h>
> > #include <sys/wait.h>
> >
> > #include <linux/reboot.h>
> >
> > static int do_reboot(void *arg)
> > {
> > int *cmd = arg;
> >
> > if (reboot(*cmd))
> > printf("failed to reboot(%d): %m
", *cmd);
> > }
> >
> > int test_reboot(int cmd, int sig)
> > {
> > long stack_size = 4096;
> > void *stack = alloca(stack_size) + stack_size;
> > int status;
> > pid_t ret;
> >
> > ret = clone(do_reboot, stack, CLONE_NEWPID | SIGCHLD, &cmd);
> > if (ret < 0) {
> > printf("failed to clone: %m
");
> > return -1;
> > }
> >
> > if (wait(&status) < 0) {
> > printf("unexpected wait error: %m
");
> > return -1;
> > }
> >
> > if (!WIFSIGNALED(status)) {
> > printf("child process exited but was not signaled
");
> > return -1;
> > }
> >
> > if (WTERMSIG(status) != sig) {
> > printf("signal termination is not the one expected
");
> > return -1;
> > }
> >
> > return 0;
> > }
> >
> > int main(int argc, char *argv[])
> > {
> > int status;
> >
> > status = test_reboot(LINUX_REBOOT_CMD_RESTART, SIGHUP);
> > if (status < 0)
> > return 1;
> > printf("reboot(LINUX_REBOOT_CMD_RESTART) succeed
");
> >
> > status = test_reboot(LINUX_REBOOT_CMD_RESTART2, SIGHUP);
> > if (status < 0)
> > return 1;
> > printf("reboot(LINUX_REBOOT_CMD_RESTART2) succeed
");
> >
> > status = test_reboot(LINUX_REBOOT_CMD_HALT, SIGINT);
> > if (status < 0)
> > return 1;
> > printf("reboot(LINUX_REBOOT_CMD_HALT) succeed
");
> >
> > status = test_reboot(LINUX_REBOOT_CMD_POWER_OFF, SIGINT);
> > if (status < 0)
> > return 1;
> > printf("reboot(LINUX_REBOOT_CMD_POWERR_OFF) succeed
");
> >
> > status = test_reboot(LINUX_REBOOT_CMD_CAD_ON, -1);
> > if (status >= 0) {
> > printf("reboot(LINUX_REBOOT_CMD_CAD_ON) should have failed
");
> > return 1;
> > }
> > printf("reboot(LINUX_REBOOT_CMD_CAD_ON) has failed as expected
");
> >
> > return 0;
> > }
> >
> > Daniel Lezcano (1):
> > Add reboot_pid_ns to handle the reboot syscall
> >
> > include/linux/pid_namespace.h | 8 +++++++-
> > kernel/pid_namespace.c | 33 +++++++++++++++++++++++++++++++++
> > kernel/sys.c | 3 +++
> > 3 files changed, 43 insertions(+), 1 deletions(-)
> >
>
> Looking at the patch, I do not think it will cause any issues for normal use, so
> I do not see a reason to not take it. We still have a bit of time, though. And
> if there is a chance that it will land in 3.3 then it will be even better
> because its then rather a cherry-pick. And we should have a bug report on
> launchpad for this to track the thing.

I've opened https://bugs.launchpad.net/ubuntu/+source/linux/+bug/914676

thanks,
-serge

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 01-11-2012, 05:12 PM
Giles Coochey
 
Default

On 11/01/2012 17:36, Giles Coochey wrote:

On 11/01/2012 10:33, Benjamin Hackl wrote:


$ cat /etc/postfix/main.cf
myorigin=yourdomain.com
relayhost=your.smarthost.com
smtp_sasl_auth_enable=yes
## you probably want to limit how postfix authenticates
# smtp_sasl_security_options=noanonymous
# smtp_sasl_mechanism_filter=login
smtp_sasl_password_maps=hash:/etc/postfix/relay_password
## if something doesn't work and you need detailed(!!) logs
#debug_peer_list=your.smarthost.com
#debug_peer_level=3
smtp_use_tls=yes
#inet_interfaces = loopback-only
#local_transport = error: disabled
unknown_local_recipient_reject_code = 450




I was missing:

smtp_sasl_mechanism_filter <postconf.5.html#smtp_sasl_mechanism_filter>
= !gssapi


Something about GSSAPI auth meant it was tried first, failed, and failed
permanently.


Disabling that, and it works.

--
Best Regards,

Giles Coochey
NetSecSpec Ltd
UK Mobile: +44 7983 877 438
Business Email: giles.coochey@netsecspec.co.uk
Email/MSN/Live Messenger: giles@coochey.net
Skype: gilescoochey

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 01-11-2012, 08:00 PM
Carlos Alberto Lopez Perez
 
Default

On 10/01/12 02:42, Ben Hutchings wrote:
> We need to make a decision soon on whether we will use Linux 3.2 for
> wheezy or wait for a later release. Whichever one we choose, we need to
> make sure someone (possibly one of us) maintains a longterm branch for
> it. I am strongly disinclined to choose a version that puts us on our
> own, and therefore I would prefer to use Linux 3.2 along with Ubuntu.
>
> Ben.
>
> -------- Forwarded Message --------
> From: Greg KH <greg@kroah.com>
> To: linux-kernel@vger.kernel.org
> Cc: stable@vger.kernel.org
> Subject: Latest kernel stable/longterm status
> Date: Mon, 9 Jan 2012 16:37:05 -0800
>
> As 3.2 is now out, here's a note as to the current status of the
> different stable/longterm kernel trees.
>
> First off, please everyone remember to mark any patch that you want to
> have applied to the stable kernel trees with a simple:
> Cc: stable <stable@vger.kernel.org>
> marking in the Signed-off-by: area. Once the patch hits Linus's tree, I
> will automatically be notified of it and it will be applied if possible.
> If it does not applied, you will be notified of that.
>
> Note that the address is stable@vger.kernel.org, not the older address
> that used to be used before October of 2011.
>
> At this time, all stable and longterm kernel trees are being maintained
> in one big git tree, located at:
> git.kernel.org:/pub/scm/linux/kernel/git/stable/linux-stable.git
> There are different branches for every different major kernel version.
>
> Here's the different active kernel versions that I am maintaining at the moment:
>
> 3.2.y - this will be maintained until 3.3 comes out

The Ubuntu guys would maintain 3.2 up to 2017 [1]

> 3.1.y - there will be only one, maybe two, more releases of this tree
> 3.0.y - this is the new "longterm" kernel release, it will be
> maintained for 2 years at the minimum by me.

This means that 3.0.y would be maintained by Greg until 2014 and Debian
probably would have to support Wheezy more long than that, because when
Wheezy-next becomes stable (2014+) we will have to support wheezy
(old-stable) for one year more at least. So in the end the support for
Wheezy will end probably in [2015-2016]


Meanwhile 3.2 will be maintained until 2017 by the Ubuntu folks (they
support LTS releases up to 5 years)


> 2.6.32.y - this is the previous "longterm" kernel release. It is
> approaching it's end-of-life, and I think I only have
> another month or so doing releases of this. After I am
> finished with it, it might be picked up by someone else, but
> I'm not going to promise anything.
>

Actually 2.6.32.y will be maintained by Ubuntu until 2015 [1] since they
need to keep with it up to that date. (2.6.32 was the kernel for Ubuntu
10.04 LTS)



> All other longterm kernels are being maintained in various forms
> (usually quite sporadically, if at all), by other people, and I can not
> speak for their lifetime at all, that is up to those individuals.
>
> If anyone has any questions about any of this, please let me know.
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>


So my humble opinion, as user, is that 3.2 seems the best choice. Also,
it is a newer kernel than 3.0, and this generally means more features
and better support for newer devices.


Regards!


[1] https://lkml.org/lkml/2012/1/10/73
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
Carlos Alberto Lopez Perez http://neutrino.es
Igalia - Free Software Engineering http://www.igalia.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
 
Old 01-11-2012, 08:15 PM
Julien Cristau
 
Default

On Wed, Jan 11, 2012 at 22:00:47 +0100, Carlos Alberto Lopez Perez wrote:

> So my humble opinion, as user, is that 3.2 seems the best choice. Also,
> it is a newer kernel than 3.0, and this generally means more features
> and better support for newer devices.
>
3.0 was never an option AIUI. The choice is essentially between 3.2,
3.3 or 3.4.

Cheers,
Julien
 
Old 01-12-2012, 08:07 AM
Arch Website Notification
 
Default

=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 4 fully signed off packages
* 11 packages missing signoffs
* 3 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)



== Incomplete signoffs for [community] (11 total) ==

* expac-0.07-1 (i686)
0/2 signoffs
* ndiswrapper-1.57-3 (i686)
0/2 signoffs
* packagekit-0.6.19-5 (i686)
0/2 signoffs
* pkgtools-23-3 (i686)
0/2 signoffs
* tomoyo-tools-2.5.0.20111025-1 (i686)
0/2 signoffs
* vdrift-2011.10.22-3 (i686)
0/2 signoffs
* virtualbox-modules-4.1.8-2 (i686)
0/2 signoffs
* ndiswrapper-1.57-3 (x86_64)
0/2 signoffs
* packagekit-0.6.19-5 (x86_64)
0/2 signoffs
* tomoyo-tools-2.5.0.20111025-1 (x86_64)
0/2 signoffs
* vdrift-2011.10.22-3 (x86_64)
0/2 signoffs


== Completed signoffs (4 total) ==

* pacman-contrib-4.0.1-1 (any)
* expac-0.07-1 (x86_64)
* pkgtools-23-3 (x86_64)
* virtualbox-modules-4.1.8-2 (x86_64)


== All packages in [community-testing] for more than 14 days (3 total) ==

* expac-0.07-1 (i686), since 2011-10-13
* expac-0.07-1 (x86_64), since 2011-10-13
* pacman-contrib-4.0.1-1 (any), since 2011-11-25


== Top five in signoffs in last 24 hours ==

1. ibiru - 7 signoffs
2. thomas - 6 signoffs
3. stativ - 2 signoffs
4. tomegun - 1 signoffs
5. pierre - 1 signoffs
 
Old 01-12-2012, 08:07 AM
Arch Website Notification
 
Default

=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 2 new packages in last 24 hours
* 4 known bad packages
* 2 packages not accepting signoffs
* 10 fully signed off packages
* 28 packages missing signoffs
* 3 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)


== New packages in [testing] in last 24 hours (2 total) ==

* systemd-38-1 (i686)
* systemd-38-1 (x86_64)


== Incomplete signoffs for [core] (2 total) ==

* kernel26-lts-2.6.32.53-1 (i686)
1/2 signoffs
* kernel26-lts-2.6.32.53-1 (x86_64)
0/2 signoffs

== Incomplete signoffs for [extra] (24 total) ==

* claws-mail-extra-plugins-3.8.0-2 (i686)
1/2 signoffs
* cmake-2.8.7-2 (i686)
0/2 signoffs
* fcpci-31107-66 (i686)
0/2 signoffs
* fcpcmcia-31107-62 (i686)
0/2 signoffs
* gvfs-1.10.1-2 (i686)
0/2 signoffs
* hplip-3.11.12-1 (i686)
0/2 signoffs
* hydrogen-0.9.5-2 (i686)
0/2 signoffs
* java7-openjdk-7.b147_2.0-5 (i686)
1/2 signoffs
* kdeutils-4.7.4-2 (i686)
0/2 signoffs
* kmod-3-5 (i686)
0/2 signoffs
* lirc-1:0.9.0-10 (i686)
0/2 signoffs
* nvidia-290.10-2 (i686)
0/2 signoffs
* totem-plparser-2.32.6-2 (i686)
0/2 signoffs
* claws-mail-extra-plugins-3.8.0-2 (x86_64)
1/2 signoffs
* cmake-2.8.7-2 (x86_64)
1/2 signoffs
* fcpci-31107-66 (x86_64)
0/2 signoffs
* fcpcmcia-31107-62 (x86_64)
0/2 signoffs
* gvfs-1.10.1-2 (x86_64)
1/2 signoffs
* hplip-3.11.12-1 (x86_64)
1/2 signoffs
* hydrogen-0.9.5-2 (x86_64)
0/2 signoffs
* java7-openjdk-7.b147_2.0-5 (x86_64)
1/2 signoffs
* kdeutils-4.7.4-2 (x86_64)
1/2 signoffs
* lirc-1:0.9.0-10 (x86_64)
0/2 signoffs
* totem-plparser-2.32.6-2 (x86_64)
0/2 signoffs

== Incomplete signoffs for [unknown] (2 total) ==

* btrfs-progs-0.19.20120110-1 (i686)
0/2 signoffs
* btrfs-progs-0.19.20120110-1 (x86_64)
1/2 signoffs


== Completed signoffs (10 total) ==

* mkinitcpio-0.8.1-1 (any)
* coreutils-8.15-1 (i686)
* pacman-4.0.1-3 (i686)
* coreutils-8.15-1 (x86_64)
* pacman-4.0.1-3 (x86_64)
* namcap-3.2.1-1 (any)
* pyalpm-0.5.3-1 (i686)
* kmod-3-5 (x86_64)
* nvidia-290.10-2 (x86_64)
* pyalpm-0.5.3-1 (x86_64)


== All packages in [testing] for more than 14 days (3 total) ==

* pyalpm-0.5.3-1 (i686), since 2011-10-15
* pyalpm-0.5.3-1 (x86_64), since 2011-10-15
* namcap-3.2.1-1 (any), since 2011-10-20


== Top five in signoffs in last 24 hours ==

1. ibiru - 7 signoffs
2. thomas - 6 signoffs
3. stativ - 2 signoffs
4. tomegun - 1 signoffs
5. pierre - 1 signoffs


Thu Jan 12 11:30:01 2012
Return-path: <bounce-debian-user=tom=linux-archive.org@lists.debian.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Thu, 12 Jan 2012 11:08:22 +0200
Received: from liszt.debian.org ([82.195.75.100]:33266)
by s2.java-tips.org with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <bounce-debian-user=tom=linux-archive.org@lists.debian.org>)
id 1RlGdx-0007Nx-V9
for tom@linux-archive.org; Thu, 12 Jan 2012 11:08:22 +0200
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with QMQP
id CB0E9AC945B; Thu, 12 Jan 2012 09:08:34 +0000 (UTC)
Old-Return-Path: <debian-user@list-post.mks-mail.de>
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on liszt.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-10.9 required=4.0 tests=FOURLA,LDOSUBSCRIBER,
LDO_WHITELIST autolearn� version=3.2.5
X-Original-To: lists-debian-user@liszt.debian.org
Delivered-To: lists-debian-user@liszt.debian.org
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with ESMTP id 84080AC9264
for <lists-debian-user@liszt.debian.org>; Thu, 12 Jan 2012 09:08:25 +0000 (UTC)
X-Virus-Scanned: at lists.debian.org with policy bank en-ht
X-Amavis-Spam-Status: No, score=-6.9 tagged_above=-10000 required=5.3
tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5] autolearn=ham
Received: from liszt.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id 7WMSgpNpELo6 for <lists-debian-user@liszt.debian.org>;
Thu, 12 Jan 2012 09:08:00 +0000 (UTC)
X-policyd-weight: using cached result; rate: -6.1
Received: from mail2.ddt-consult.de (mail2.ddt-consult.de [88.198.36.7])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by liszt.debian.org (Postfix) with ESMTPS id 55C6A6C967A
for <debian-user@lists.debian.org>; Thu, 12 Jan 2012 09:08:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by mail2.ddt-consult.de (Postfix) with ESMTP id AE01F4004FB
for <debian-user@lists.debian.org>; Thu, 12 Jan 2012 10:07:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d list-post.mks-mail.de; h=content-transfer-encoding:content-type
:content-type:in-reply-to:references:subject:subject
:mime-version:user-agent:reply-to:from:from:date:date:message-id
:received:received; s=lpm; t26359225; bh=ZEPUSWm9fcjHN7BsZyGm
yhM2JhKA7qTYsWde1tr1Hsc=; b�qMD62yd23cQ0lbBnN6EuJ6bCurSWed+tRd
idhHQJchxAaWXjqk7n8hFvd3vXKo0IKIl/tvo62OEYV4/GTzQxuVpwr4QVwsUT/w
vnCaCQBLqplplsOj7fAA/4FvmvFA/dzAuWgekmCCXKRTUo4SM3GePlpxRwEHeDAk
W3I9HicX-Virus-Scanned: Debian amavisd-new at mail
Received: from mail2.ddt-consult.de ([127.0.0.1])
by localhost (mail2.ddt-consult.de [127.0.0.1]) (amavisd-new, port 20024)
with LMTP id ShVKgUqjhV8r for <debian-user@lists.debian.org>;
Thu, 12 Jan 2012 10:07:05 +0100 (CET)
Received: from legolas.home.ddt.intern (p5DC37859.dip.t-dialin.net [93.195.120.89])
(Authenticated sender: mks@list-post.mks-mail.de)
by mail2.ddt-consult.de (Postfix) with ESMTPSA id E09D8400258
for <debian-user@lists.debian.org>; Thu, 12 Jan 2012 10:06:59 +0100 (CET)
Message-ID: <4F0EA2B0.3060009@list-post.mks-mail.de>
Date: Thu, 12 Jan 2012 10:06:56 +0100
From: =?ISO-8859-1?Q?Markus_Sch�ber? <debian-user@list-post.mks-mail.de>
Reply-To: debian-user@lists.debian.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: debian-user@lists.debian.org
Subject: Re: smtp/postfix/sasl/openssh headaches
References: <20120111175157.GA27352@deathstar.hsd1.ct.comcast. net> <4F0DDF71.5060308@list-post.mks-mail.de> <20120111214133.GB10561@deathstar.hsd1.ct.comcast. net>
In-Reply-To: <20120111214133.GB10561@deathstar.hsd1.ct.comcast. net>
Content-Type: text/plain; charset=ISO-8859-1
X-Rc-Virus: 2007-09-13_01
X-Rc-Spam: 2008-11-04_01
Resent-Message-ID: <nTPprtLAu7M.A.jgD.SMqDPB@liszt>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/621264
X-Loop: debian-user@lists.debian.org
List-Id: <debian-user.lists.debian.org>
List-Post: <mailto:debian-user@lists.debian.org>
List-Help: <mailto:debian-user-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-user-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
Resent-Date: Thu, 12 Jan 2012 09:08:34 +0000 (UTC)
Content-Transfer-Encoding: quoted-printable

11.01.2012 22:41, Tony Baldwin:

> On Wed, Jan 11, 2012 at 08:13:53PM +0100, Markus Sch�ber wrote:

>> Stop and/or uninstall sendmail (or whatever this process might belong to).
>
>
> I think I just addressed that.

Obviously not.

> I do not have sendmail installed.

Then stop/uninstall the software that listens on port 25 and thus
prevents postfix of doing so.

> $ sudo aptitude remove sendmail
> NUCLEAR LAUNCH CODE:
> No packages will be installed, upgraded, or removed.
> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B of archives. After unpacking 0 B will be used.
>
> My understanding is that postfix has something with the same name.

Yes, it's the command line interface to the mail system and it's called
"sendmail" because of sendmail compatibility. But postfix' sendmail
binary never listens on any network socket. The postfix process that
does is called "master".

Is your mail server going to be accessible from an untrusted network/the
internet?

--
Regards
mks


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/4F0EA2B0.3060009@list-post.mks-mail.de
 

Thread Tools




All times are GMT. The time now is 04:41 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org