On Mon, 2024-12-16 at 21:21 +0300, Michael Tokarev wrote:
> It turns out the reason for this is a myth, which we believed to for
> 25 years - a myth that "On FreeBSD, chroot is painless, but on Linux,
> chroot never works and is only suitable for the ones who want pain".
> Actually, it looks like,
On Wed, 2024-12-18 at 10:38 +, Jonathan Dowland wrote:
> I would also like to see this. Perhaps it's because the maintainers
> don't want to close the door to alternative init systems, by making
> their package depend on systemd features?
Adding a couple of lines to the systemd unit should n
On Wed, 2024-12-11 at 09:11 +0100, Marc Haber wrote:
> That's easy, just choose a user name for YOU that YOU can type on YOUR
> keyboard. Why would anybody chose a username that is impossible to use
> in their own locale?
I don't see much problems with single-user machines, especially security
rel
On Thu, 2024-12-19 at 07:08 -0600, rhys wrote:
>
> What group of idiots came up with a system where instead of having all of the
> configs in maximum of two places (/etc | ~/.config) have now spread them out
> across five completely separate directory trees?
The group is called "The Linux User
On Thu, 2024-12-19 at 11:04 +0300, Michael Tokarev wrote:
> I would advise against this simplistic view on security and "hardening" -
> it often makes false sense of security instead of real security.
Yes I agree, also blindly applied "hardening" settings can cause the
program not function correct
On Fri, 2024-12-20 at 09:55 +0100, Samuel Thibault wrote:
> But isn't it what we already have? If I don't modify the example in /etc
> and only add files to .d/, I'm getting upgrades without questions.
> And if I modify the example in /etc, I'm getting the question. That way
> I can decide per-pack
On Fri, 2024-12-20 at 12:01 +0100, Ansgar 🙀 wrote:
> With empty-/etc, you would (ideally) only have explicit local
> configuration in /etc which makes it much, much easier to see what the
> local admin changed to diagnose problems, prepare upgrades and so on.
> This is practically impossible now.
On Sat, 2025-01-25 at 15:34 +, Richard Lewis wrote:
> downloading and running a script from a random website seems a rather
> unhelpful approach and maybe not the best idea to suggest debian
> supports this?
Does this even work with Debian?
The script
https://github.com/CrypticVerse/linux-o
On Tue, 2025-01-28 at 10:42 +0100, IOhannes m zmölnig (Debian GNU|Linux)
wrote:
> i cannot.
> using 'unzip' in a debian:stable docker container works nicely
No problems with stable or trixie unzip.
@Frederic-Emmanuel, did you check that your copy of the file is not
corrupted?
$ md5sum fiji-linu
Andrey Rakhmatullin writes:
Unfortunately, while proposing is cheap, actually *doing* this
is somewhat harder. So unless you, and a suitable number of
other people, are ready to work on this, this won't happen.
A more realistic goal might be to increase the number of packages
in the backpo
"Andrea Pappacoda" writes:
As you can see, the Content-Type header has no Format parameter.
Yeah, (decoded) lines end with ' ' (ASCII space), but with no
Format parameter set to Flowed, they have no special meaning.
I stand corrected; I mistakenly interpreted f=f there. It seems
expectat
Andrey Rakhmatullin writes:
> This (as a mild but easy to get example of pre-formatted text):
>
>> For sake of argument:- If this re-wrapping is purely client side and
>> happens after PGP verification, incoming mail could still show as
>> verified (but it may look slightly different)- I could to
Soren Stoutner writes:
All of the subsequent emails I have sent as part of this
discussion have been wrapped at 80 characters inline with the
current mailing list code of conduct.
If I'm not mistaken, your emails (at least this one I am replying
to) utilize Format=Flowed (in the text/pain
13 matches
Mail list logo
