On Fri, 09 Aug 2019 at 12:17:13 -0400, Marvin Renich wrote:
> My point is that Debian as a distribution is used in a wide variety of
> use cases, from locked-down server to single-user desktop to multi-user
> application server (what used to be called time sharing).
If you're executing arbitrary c
Simon Richter writes:
> What I'm not happy with is that we have effectively incorporated systemd
> unit files as an interface into Debian Policy without *explicitly* doing
> so, and that this interface remains "defined by upstream".
> If that is what we want, then we should update Debian Policy.
Marvin Renich writes:
> I don't get this at all. Has there ever been a routine, best-practice
> of having a machine that frequently changed its IP address to prevent
> operators of other machines on the net from "fingerprinting"? (I'm not
> talking about intentional use of an onion router.)
Ye
Hi,
On Fri, Aug 09, 2019 at 02:54:55PM +0100, Simon McVittie wrote:
> To a large extent, the design of units and service files *is* systemd.
This is a large part of the systemd criticism as well: the refusal to
commit to an API because it would hinder future development, while at the
same time p
* Simon McVittie [190808 18:37]:
> On Thu, 08 Aug 2019 at 15:20:28 -0400, Marvin Renich wrote:
> > The man page for machine-id says:
> >
> > This ID uniquely identifies the host. It should be considered
> > "confidential", and must not be exposed in untrusted environments, in
> > particular
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, Aug 8, 2019 at 9:39 PM Aurelien Jarno wrote:
> We are at a point were we should probably look for a real solution
> instead of relying on tricks.
*sigh* i _have_ been pointing out for several years now that thi
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Aug 9, 2019 at 1:49 PM Ivo De Decker wrote:
>
> Hi Aurelien,
>
> On 8/8/19 10:38 PM, Aurelien Jarno wrote:
>
> > 32-bit processes are able to address at maximum 4GB of memory (2^32),
> > and often less (2 or 3GB)
Hi,
On 8/9/19 4:41 PM, Karsten Merker wrote:
On Fri, Aug 09, 2019 at 02:31:47PM +0200, Ivo De Decker wrote:
Some random notes (these are just my preliminary thoughts, not a new release
team policy):
[...]
- We are talking about having both native 32-bit and 64-bit packages in
the same envi
On 09.08.19 12:06, Ansgar wrote:
>
> Having sysvinit might make things a bit easier for Hurd/kFreeBSD, but
> it's not an absolute requirement for such a port to exist.
>
> Ansgar
>
Thanks Ansgar, this is the user deep in me - i like things to easy as
possible. More verbose: I will apply all patch
On 09.08.19 15:51, Tomas Pospisek wrote:
>
> FWIW (I mean it, this is just anecdotical evidence): I have been
> recently upgrading a lot of containers and host and I have been unable
> to make lxc guest with systemd inits even start.
>
> Also, I have been having problems with ssh sessions taking
On 2019-08-09 07:00:41 +0200 (+0200), Vincent Bernat wrote:
> ❦ 8 août 2019 21:47 +02, Simon Richter :
>
> >> inetd performance is very low because it needs to spawn one instance for
> >> each connection. systemd socket activation has absolutely 0 overhead
> >> except on the first connection (wh
Package: wnpp
Severity: wishlist
Owner: Andrew Lee (李健秋)
* Package name: gnome-shell-xrdesktop
Version : 0.12.1
Upstream Author : Lubosz Sarnecki lubosz.sarne...@collabora.com
* URL : https://gitlab.freedesktop.org/xrdesktop/gnome-shell
* License : Expat
Prog
On Fri, 09 Aug 2019 at 14:31:47 +0200, Ivo De Decker wrote:
> On 8/8/19 10:38 PM, Aurelien Jarno wrote:
> > This is still a kind of cross-compiler
>
> As you noted, our current policy doesn't allow that.
...
> The resulting (32-bit) binaries still need to run natively in the build
> environment.
A
On Fri, 09 Aug 2019 at 17:12:17 +0800, Benda Xu wrote:
> Simon Richter writes:
> > For that to happen, we'd have to define .service files as an API
> > though, which would feature-freeze them, and I'm not sure the systemd
> > people would be happy about that.
>
> Thank you for sharing your though
Am 07.08.19 um 19:00 schrieb Marc Haber:
> On Wed, 7 Aug 2019 14:44:01 +0100, Ian Jackson
> wrote:
>> Marc Haber writes ("Re: do packages depend on lexical order or
>> {daily,weekly,monthly} cron jobs?"):
>>> We have already thrown sysvinit away.
>>
>> No, we have not.
>
> We have given up on so
Hi Aurelien,
On 8/8/19 10:38 PM, Aurelien Jarno wrote:
32-bit processes are able to address at maximum 4GB of memory (2^32),
and often less (2 or 3GB) due to architectural or kernel limitations.
[...]
Thanks for bringing this up.
1) Build a 64-bit compiler targeting the 32-bit correspondin
Ian Jackson - 09.08.19, 11:27:31 CEST:
> Ondřej Surý writes ("Re: Please stop hating on sysvinit"):
> > On 9 Aug 2019, at 09:22, Martin Steigerwald
> > wrote:
> > > Actually as a user of my services I do not even notice any
> > > difference, so for me it is: What is actually the point of
> > > st
Package: wnpp
Severity: wishlist
Owner: Josua Mayer
* Package name: stratis-cli
Version : 1.0.4
Upstream Author : RedHat, Inc.
* URL : https://stratis-storage.github.io/
* License : Apache 2.0
Programming Lang: Python 3
Description : cli interface to s
Alf Gaida writes:
> We need sysvinit for some non-linux things
No: Hurd existed for a long time without using sysvinit/sysv-rc. I
think sysvinit was only ported to Hurd in 2013 or 2014 (I didn't search
much, but found a Summer of Code application from 2013 for this).
Having sysvinit might make t
On dv., ag. 09 2019, Vincent Bernat wrote:
❦ 9 août 2019 09:22 +02, Martin Steigerwald
:
Reality seems different. Almost nothing was using inetd (tftpd
is the
I note that you wrote "seems". But still:
As if there would just be *one* reality. Actually there is. But
I never
saw any human
Ondřej Surý writes ("Re: Please stop hating on sysvinit"):
> On 9 Aug 2019, at 09:22, Martin Steigerwald wrote:
> > Actually as a user of my services I do not even notice any difference, so
> > for me it is: What is actually the point of starting them on demand?
>
> Unprivileged access to port <
Dear Simon,
Simon Richter writes:
> The sanest thing we could do in Debian is to teach start-stop-daemon
> to parse systemd .service files and pull its command line arguments
> from there, so we could use service definitions as init scripts with a
> #! line.
>
> For that to happen, we'd have to
On 9 Aug 2019, at 09:22, Martin Steigerwald wrote:
>
> Actually as a user of my services I do not even notice any difference, so
> for me it is: What is actually the point of starting them on demand?
Unprivileged access to port < 1024. The socket-activated services can start
as user since the
On Fri, 09 Aug 2019 at 02:04:25 +0200, Adam Borowski wrote:
> But... if this ID must not be exposed on the network, why does it need to be
> unique?
At the risk of stating the obvious, that defeats the object of having a
unique ID: anything that stores per-machine state/configuration keyed
by the
On 8/7/19 4:14 AM, Marc Haber wrote:
Imo, there should be a possibility in a systemd timer to switch on the
"old" output-to-e-mail behavior. This is probably something that
systemd upstream would never implement, so we'd end up with a wrapper
that is called by the systemd timer unit.
You can s
❦ 9 août 2019 09:22 +02, Martin Steigerwald :
>> Reality seems different. Almost nothing was using inetd (tftpd is the
>
> I note that you wrote "seems". But still:
>
> As if there would just be *one* reality. Actually there is. But I never
> saw any human being being able to express it in word
Vincent Bernat - 09.08.19, 07:00:41 CEST:
> ❦ 8 août 2019 21:47 +02, Simon Richter :
> >> inetd performance is very low because it needs to spawn one
> >> instance for each connection. systemd socket activation has
> >> absolutely 0 overhead except on the first connection (where
> >> systemd need
27 matches
Mail list logo
