From: Tomasz Rola <rtomek@ceti.pl>
To: coff@tuhs.org
Subject: [COFF] Re: Systemd Creator Lands At Microsoft
Date: Sat, 9 Jul 2022 10:35:53 +0200 [thread overview]
Message-ID: <20220709083552.GC28363@tau1.ceti.pl> (raw)
In-Reply-To: <YsjfXjpe951GJVft@zombi.ugr.es>
On Sat, Jul 09, 2022 at 03:52:30AM +0200, Angel M Alganza wrote:
> Hello, Tomasz,
>
[...]
> Devuan GNU+Linux is a fork of Debian without systemd that allows
> users to reclaim control over their system by avoiding
> unnecessary entanglements and ensuring Init Freedom.
Thank you. I have Devuan on a (very short) list. Right now I am
testing a systemd based Debian derivative, to see what I will be
missing. Testing takes time etc. I am not very impressed, so
far. During last months, nothing I would like to have so much that I
would go with systemd. It just behaves predictably, which is a lot,
but not really lot. After all, it is still a Linux.
However, performance seems to be worse. I have a really old (like,
decade) desktop with really antique Debian (pre-systemd) and it seems
to behave faster than a newish (bought from second hand) laptop with
integrated CPU/GPU and Parrot installed on it. The clocks - I always
downclock as a rule. So old Debian is clocked @800MHz and Parrot
@1100MHz. Hence Parrot really could do a bit more, but nope. Feels
sluggish, but I might be making this up. After all, I do not like the
whole idea of systemd and stuff. Well, a small difference - Debian
runs on four cores, and Parrot cannot. On four cores it overheats and
shuts down whenever I try to use it - be it computing control sums or
compiling. In order to be any usable at all I have to boot it with
maxcpus=1. This probably tells more about quality of laptop than
Parrot. But I will see more when I install something else on it.
--
Regards,
Tomasz Rola
--
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** **
** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
next prev parent reply other threads:[~2022-07-09 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:40 [COFF] " Tomasz Rola
2022-07-08 10:26 ` [COFF] " Michael Cardell Widerkrantz
2022-07-09 0:29 ` Tomasz Rola
2022-07-09 1:52 ` Angel M Alganza
2022-07-09 8:35 ` Tomasz Rola [this message]
2022-07-09 8:59 ` Angel M Alganza
2022-07-10 21:39 ` Chris Hanson
2022-07-11 14:11 ` Steffen Nurpmeso
2022-07-11 21:04 ` Michael Cardell Widerkrantz
2022-07-11 23:01 ` Dave Horsfall
2022-07-12 7:58 ` [COFF] Re: Alpine, was: " Michael Kjörling
2022-07-12 15:34 ` Adam Thornton
2022-07-12 22:02 ` Steffen Nurpmeso
2022-07-12 23:34 ` Dave Horsfall
2022-07-13 7:36 ` [COFF] Re: Alpine Michael Kjörling
2022-07-12 15:56 ` [COFF] Re: Systemd Creator Lands At Microsoft Michael Cardell Widerkrantz
2022-07-12 19:48 ` Lars Brinkhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220709083552.GC28363@tau1.ceti.pl \
--to=rtomek@ceti.pl \
--cc=coff@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).