Hi,
On Wed, Jan 23, 2013 at 05:12:59AM +0600, Andrey Rahmatullin wrote:
> On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > This blogpost is months old but it makes some interesting reflections:
> > http://www.pappp.net/?p=969
> https://plus.google.com/u/0/11554768395172769
I demand that Adam Borowski may or may not have written...
[snip]
> No, it's something in the middle. Those who dislike systemd say it
> exaggerates systemd's claimed benefits, while Joss considers it an attack
> as well. Let's no go there for now.
>
> What makes this article worth reading is t
Russ Allbery wrote:
> Adam Borowski writes:
>
> > There are two ways to design a system:
> > * a monolithic well-integrated system, granting features and efficiency at
> > the cost of portability and hackability
> > * the traditional Unix way, with a stress on replaceable tools that do only
> >
On 2013-01-23 20:45:49 -0800, Russ Allbery wrote:
> Adam Borowski writes:
>
> > There are two ways to design a system:
> > * a monolithic well-integrated system, granting features and efficiency at
> > the cost of portability and hackability
> > * the traditional Unix way, with a stress on repl
Le mercredi 23 janvier 2013 à 21:03 +0100, Florian Weimer a écrit :
> Unfortunately, a lot of this doesn't apply to the polkit version in
> experimental, which replaces .plka files with Javascript (which
> sort-of enforces that only system administrators can configure polkit,
> and not other packa
Chow Loong Jin writes:
> * But if it ever fails due to a bug within it, $DEITY help you, because
> you're going to have to go through everything mentioned in your first
> point here (save the issues with getting patches accepted)
Sometimes, debugging can be easier in monoli
Adam Borowski writes:
> Putting it another way:
> * the monolithic design has a huge freeness problem. To do anything not on
> a rigid list of features you need to learn the intricaties of a large
> complex system, and you can be certain that even if you manage to do so,
> your patches wi
On 24/01/2013 13:09, Adam Borowski wrote:
> [...]
> * the monolithic design has a huge freeness problem. To do anything not on
> a rigid list of features you need to learn the intricaties of a large
> complex system, and you can be certain that even if you manage to do so,
> your patches wil
On Wed, Jan 23, 2013 at 08:45:49PM -0800, Russ Allbery wrote:
> Adam Borowski writes:
>
> > There are two ways to design a system:
> > * a monolithic well-integrated system, granting features and efficiency at
> > the cost of portability and hackability
> > * the traditional Unix way, with a st
Adam Borowski writes:
> There are two ways to design a system:
> * a monolithic well-integrated system, granting features and efficiency at
> the cost of portability and hackability
> * the traditional Unix way, with a stress on replaceable tools that do only
> one thing, granting freedom to
On Wed, Jan 23, 2013 at 08:16:40PM +0100, Philipp Kern wrote:
> On Tue, Jan 22, 2013 at 02:57:58PM +0100, Svante Signell wrote:
> > On Tue, 2013-01-22 at 14:41 +0100, Adam Borowski wrote:
> > > On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > > > This blogpost is months old
* Jon Dowland:
> On Wed, Jan 23, 2013 at 10:46:33AM +0100, Josselin Mouette wrote:
>> You might find this useful:
>> http://np237.livejournal.com/33449.html
>>
>> I made this presentation in the hope to make such things easier to
>> understand for the sysadmin.
>
> Just for the record I found it
On Tue, Jan 22, 2013 at 02:57:58PM +0100, Svante Signell wrote:
> On Tue, 2013-01-22 at 14:41 +0100, Adam Borowski wrote:
> > On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > > This blogpost is months old but it makes some interesting reflections:
> > > http://www.pappp.net/
On Wed, Jan 23, 2013 at 10:46:33AM +0100, Josselin Mouette wrote:
> You might find this useful:
> http://np237.livejournal.com/33449.html
>
> I made this presentation in the hope to make such things easier to
> understand for the sysadmin.
Just for the record I found it a good read, and mentally
Josselin Mouette writes:
> You might find this useful:
> http://np237.livejournal.com/33449.html
>
> I made this presentation in the hope to make such things easier to
> understand for the sysadmin.
I read that back then when you originally posted it and I still think
it's one of the most useful
Le mardi 22 janvier 2013 à 16:32 -0500, Theodore Ts'o a écrit :
> One of the big things which is incredibly frustrating with the D-Bus
> interfaces is that they aren't documented; and if they are documented,
> it's not obvious where.
I can only agree completely. It is very frustrating for some pl
On 01/22/2013 09:05 AM, Josselin Mouette wrote:
Le mardi 22 janvier 2013 à 14:57 +0100, Svante Signell a écrit :
Worthwhile to read, definitely.
Yet full of misinformation, like the idea that using D-Bus makes a service
less scriptable (while the reality is a complete opposite), or that
conf
On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> Hello,
>
> This blogpost is months old but it makes some interesting reflections:
>
> http://www.pappp.net/?p=969
https://plus.google.com/u/0/115547683951727699051/posts/74r518xVUNH
--
WBR, wRAR
signature.asc
Description:
On Tue, Jan 22, 2013 at 03:05:58PM +0100, Josselin Mouette wrote:
> Yet full of misinformation, like the idea that using D-Bus makes a
> service less scriptable (while the reality is a complete opposite), or
> that configuration files are less human-readable than shell scripts.
My biggest complain
On Tue, Jan 22, 2013 at 3:05 PM, Josselin Mouette wrote:
> Le mardi 22 janvier 2013 à 14:57 +0100, Svante Signell a écrit :
> > Worthwhile to read, definitely.
>
> Yet full of misinformation, like the idea that using D-Bus makes a
> service less scriptable (while the reality is a complete opposit
Josselin Mouette writes:
> Yet full of misinformation, like the idea that using D-Bus makes a
> service less scriptable (while the reality is a complete opposite)
I was bit puzzled by this part too but I guess the author meant mostly
shell scripts here. If one uses e.g. python then dbus is often
On Tue, Jan 22, 2013 at 03:05:58PM +0100, Josselin Mouette wrote:
> Le mardi 22 janvier 2013 à 14:57 +0100, Svante Signell a écrit :
> > Worthwhile to read, definitely.
>
> Yet full of misinformation, like the idea that using D-Bus makes a
> service less scriptable (while the reality is a complet
Le mardi 22 janvier 2013 à 14:57 +0100, Svante Signell a écrit :
> Worthwhile to read, definitely.
Yet full of misinformation, like the idea that using D-Bus makes a
service less scriptable (while the reality is a complete opposite), or
that configuration files are less human-readable than shell
On Tue, 2013-01-22 at 14:41 +0100, Adam Borowski wrote:
> On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > Hello,
> >
> > This blogpost is months old but it makes some interesting reflections:
> >
> > http://www.pappp.net/?p=969
>
> It appears to be the most insightful th
On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> Hello,
>
> This blogpost is months old but it makes some interesting reflections:
>
> http://www.pappp.net/?p=969
It appears to be the most insightful thing about systemd vs the rest of the
world I've ever read. READ IT, FOL
Hello,
This blogpost is months old but it makes some interesting reflections:
http://www.pappp.net/?p=969
I wonder what's Debian position in regards to FLOS* vs Unix philosophy. Is
there one, at all? (I can't remember reading one, my apologies if this was
discussed and I have not noticed)
* FLO
26 matches
Mail list logo
