On Thu, Apr 03, 2014 at 11:58:17AM +0200, Tollef Fog Heen wrote:
> [...]
> Am I understanding you correctly that you don't think there are any
> situations where compiling out features from the kernel can lead to pid1
> not working would be acceptable?
For the record, there's CONFIG_BINFMT_SCRIPT,
On Thu, 03 Apr 2014, Stephen Allen wrote:
> Like the OP - I didn't like Gnome-Shell at first, but after giving it a
> month I really started enjoying it. It's also mature and being worked on
> extensively. Not something one can say about Xfce4 at this point.
>
> I think you're probably the excepti
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 570 (new: 5)
Total number of packages offered up for adoption: 135 (new: 1)
Total number of packages request
Hi!
I am the maintainer of the raccon/ipsec-tools packages and I want to
review their relevance in modern Debian.
Systemd package support is the thing that pushed me over the edge about
this. There are no systemd unit files at all for ipsec-tools/racoon
that I know of. Please advise me otherwise
On Fri, Apr 04, 2014 at 08:18:41AM +1100, Dmitry Smirnov wrote:
> On Thu, 3 Apr 2014 14:16:15 Undefined User wrote:
> > The problem is that right now Debian project is changing its default
> > desktop environment, and I think that this is not a good move. Of course,
> > it all depends on where the
On Thu, 3 Apr 2014 14:16:15 Undefined User wrote:
> The problem is that right now Debian project is changing its default
> desktop environment, and I think that this is not a good move. Of course,
> it all depends on where the project is aiming at, specially on which users.
> But, for normal users,
previously on this list Steve Langasek contributed:
> The avalanche has already started; it is too late for the pebbles to vote.
Winston Churchill said "It is never too late" a few times and I think
some of his quotes are quite fitting.
"A lie gets halfway around the world before the truth has a
previously on this list Matthias Urlichs contributed:
> > I don't believe I have said that. «die» is not the same as «crash».
>
> If you're talking about PID1, the end result is the same.
It is not because one is a foreseen issue and the other indicates a
lack of polish on PID1!
--
previously on this list The Wanderer contributed:
> I was explicitly referring to the point in the future when maintainers
> do stop providing traditional init scripts. This likely won't happen
> that fast, no, but I do think it's likely that it will happen - whether
> days after the jessie releas
previously on this list Jan Gloser contributed:
Kev, the systemd design document says it all about the lack of design
with statements showing a clear lack of understanding. I would be
ashamed to call it a design document.
> I would also like to ask something the people who dislike systemd (as the
previously on this list Russ Allbery contributed:
> > I guess you missed all the exploits in JAVA over the years and
> > especially last year where it was banned for long periods from all
> > browsers. To the point that the pressure is building on web hosts to
> > drop JAVA KVM clients completely.
previously on this list Bas Wijnen contributed:
> On Tue, Apr 01, 2014 at 10:49:15PM +0100, Kevin Chadwick wrote:
> > > I think at Debian we all agree that it would be a good
> > > thing if everything would be encrypted, so this is a very bad outcome.
> >
> > I beg to differ I'm afraid. SSL shou
Package: wnpp
Severity: wishlist
Owner: Miguel Landaeta
* Package name: ruby-scrypt
Version : 1.2.1
Upstream Author : Patrick Hogan
* URL : https://github.com/pbhogan/scrypt
* License : BSD
Programming Lang: Ruby
Description : Ruby gem with native C ex
Hello,
I'm a Debian user for almost 8 years now and I've always supported the OS
on the internet, trying to bring more people to it.
The problem is that right now Debian project is changing its default
desktop environment, and I think that this is not a good move. Of course,
it all depends on whe
On Thu, Apr 03, 2014 at 06:23:36PM +0200, Marc Haber wrote:
> >> I'd say the opposite way. Could you please explain in which case you
> >> find it acceptable to *just crash*, and render the system completely
> >> unusable, and possibly even not recoverable?
> >
> >1. If the kernel is configured wit
On Thu, Apr 03, 2014 at 10:26:22AM +0100, Neil McGovern wrote:
> On Thu, Apr 03, 2014 at 11:12:12AM +0900, Norbert Preining wrote:
> > Is this the upstream Debian wants to base its "life" on?
> According to the technical committee, and the lack of support for the
> GR, the answer is yes.
The GR t
On Thu, 03 Apr 2014 16:39:29 +0100, Ben Hutchings
wrote:
>On Thu, 2014-04-03 at 19:55 +0800, Thomas Goirand wrote:
>> On 04/03/2014 05:58 PM, Tollef Fog Heen wrote:
>> > Am I understanding you correctly that you don't think there are any
>> > situations where compiling out features from the kernel
On Thu, 2014-04-03 at 19:55 +0800, Thomas Goirand wrote:
> On 04/03/2014 05:58 PM, Tollef Fog Heen wrote:
> > Am I understanding you correctly that you don't think there are any
> > situations where compiling out features from the kernel can lead to pid1
> > not working would be acceptable?
>
> I'
Hi,
Tollef Fog Heen:
> I don't believe I have said that. «die» is not the same as «crash».
If you're talking about PID1, the end result is the same.
--
-- Matthias Urlichs
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Nahar P
* Package name: libip2location
Version : 6.0.2
Upstream Author : Liew
* URL : https://www.ip2location.com/downloads/c/
* License : GPL
Programming Lang: C
Description : C library to query geolocation and
]] Thomas Goirand
> On 04/03/2014 05:58 PM, Tollef Fog Heen wrote:
> > Am I understanding you correctly that you don't think there are any
> > situations where compiling out features from the kernel can lead to pid1
> > not working would be acceptable?
>
> I'd say the opposite way. Could you ple
]] Bjørn Mork
> Tollef Fog Heen writes:
> > ]] Norbert Preining
> >
> >> > systemd needs cgroups, that's pretty well established. Arguably, it
> >> > should die with a clearer message.
> >>
> >> No, NO NOO
> >>
> >> *IT*SHOULD*NOT*DIE*!!! It is in PID 1. Please digest th
On Tue, Apr 01 2014, Andrew M.A. Cater wrote:
> On Tue, Apr 01, 2014 at 05:39:04PM +0200, The deity team wrote:
>>
>> Who would have guessed that 16 years ago? Do you remember what you did
>> on the first April in 1998? What is the first thing you thought while
>> reading this mail? And most impo
On 04/03/2014 05:58 PM, Tollef Fog Heen wrote:
> Am I understanding you correctly that you don't think there are any
> situations where compiling out features from the kernel can lead to pid1
> not working would be acceptable?
I'd say the opposite way. Could you please explain in which case you
fi
Tollef Fog Heen writes:
> ]] Norbert Preining
>
>> > systemd needs cgroups, that's pretty well established. Arguably, it
>> > should die with a clearer message.
>>
>> No, NO NOO
>>
>> *IT*SHOULD*NOT*DIE*!!! It is in PID 1. Please digest that.
>
> Am I understanding you cor
On Thu, Apr 03, 2014 at 06:33:42PM +0900, Norbert Preining wrote:
> Hi Tollef,
>
> On Thu, 03 Apr 2014, Tollef Fog Heen wrote:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=76935
> >
> > That's being moved to systemd.debug instead of overloading debug.
>
> Good news. And please make Kay e
Hi Norbert et al.,
> * systemd maintainers (Lennart Poettering) does not care for
> segfaults in his code, even if it happens in pid 1.
> https://bugs.freedesktop.org/show_bug.cgi?id=74589
to me his response does not read as if he didn't care. Systemd on
systems without cgroups has never
]] Norbert Preining
> Hi Tollef,
>
> On Thu, 03 Apr 2014, Tollef Fog Heen wrote:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=76935
> >
> > That's being moved to systemd.debug instead of overloading debug.
>
> Good news. And please make Kay excuse for his rudeness and ifgnorance.
Why
Hi,
On Thu, Apr 03, 2014 at 10:41:45AM +0200, Matthias Urlichs wrote:
> Norbert Preining:
> > * several kernel maintainer propose (not completely serious, but
> > it shows the general opinion), to add
> > + BUG_ON(!strcmp(current->comm, "systemd"));
>
> URLs please.
IIRC that's from
Hi,
On Thu, Apr 03, 2014 at 05:41:21AM -0007, Cameron Norman wrote:
> This really is not something suitable for debian-devel, unless you
> are actually proposing a GR to re-choose the init system, which you
> do not seem to be doing.
GRs are also off-topic on -devel.
Michael
--
To UNSUBSCRIB
On Thu, Apr 03, 2014 at 10:41:45AM +0200, Matthias Urlichs wrote:
> Hi,
> [...]
> > * several kernel maintainer propose (not completely serious, but
> > it shows the general opinion), to add
> > + BUG_ON(!strcmp(current->comm, "systemd"));
>
> URLs please.
http://marc.info/?l=linux-ke
Hi,
On Thu, 03 Apr 2014, Matthias Urlichs wrote:
> > https://bugs.freedesktop.org/show_bug.cgi?id=76935
> >
> It's not "an obvious bug", it's primarily an issue of interpreting whether
> a generic boot parameter like "debug" is intended for just the kernel, or
> the whole system.
>
> Linux h
Hi Tollef,
On Thu, 03 Apr 2014, Tollef Fog Heen wrote:
> > https://bugs.freedesktop.org/show_bug.cgi?id=76935
>
> That's being moved to systemd.debug instead of overloading debug.
Good news. And please make Kay excuse for his rudeness and ifgnorance.
Thanks for letting us know.
But why is th
On Thu, Apr 03, 2014 at 11:12:12AM +0900, Norbert Preining wrote:
> Is this the upstream Debian wants to base its "life" on?
>
According to the technical committee, and the lack of support for the
GR, the answer is yes.
If you don't like this answer, please put effort into doing the work to
prov
]] Norbert Preining
> Hi
>
> recent discussions on lkml really made me rethink the systemd
> position.
>
> How is it possible that:
> * systemd maintainers (Kay Sievers) considers an obvious bug in
> his code that locks out users something not in need to be cared
> for?
> https://bugs
Hi,
Norbert Preining:
> How is it possible that:
> * systemd maintainers (Kay Sievers) considers an obvious bug in
> his code that locks out users something not in need to be cared
> for?
> https://bugs.freedesktop.org/show_bug.cgi?id=76935
>
It's not "an obvious bug", it's primarily an
36 matches
Mail list logo
