update-rc.d: error: unable to read /etc/init.d/clamav-freshclam

[Mario Marietto]

-> Nevertheless, in many cases modern iPads work as well, or at least
almost as well, for a wide range of professional applications as desktop
PCs do, while tablet computers based on Linux (Android and anything else)
fail miserably, despite equally excellent hardware.

If the OS works great but it is closed source,I don't care. I don't want a
closed source product.

---> In the regard of packages Arch Linux has got a similar approach as
FreeBSD. It provides package repositories and a FreeBSD port-like build
system. In most cases software from upstream isn't even split by the
provided packages. Building by the port-like system, in a clean chroot is
straight forward. The documentation of Arch Linux is also similar to the
documentation of FreeBSD.

Some years ago I tried arch linux. And not,it hasn't given me the same
satisfaction as FreeBSD. Hard to say why,I should reinstall it to better
evaluate it,but I don't want to. Instead I could try MakuluLinux.

---> The problem with systemd is that it's not just an init system.
However,even with systemd a user can still use e.g. a fstab instead of
countless confusing systemd units. OTHO even without systemd, some distros
do not use systemd, there are still insanely split configurations.

Here you clearly see the divisions of the tasks as bad. But mature users
like to have more customization and not a monolithic block that does
several tasks.

On Mon, Jan 15, 2024 at 6:09 PM Ralf Mardorf via ubuntu-users <
ubuntu-users at lists.ubuntu.com> wrote:

> On Mon, 2024-01-15 at 15:11 +0100, Mario Marietto wrote:
> > From my personal perspective a closed OSes even if they are certified
> > as POSIX os,they aren't POSIX os.
>
> Hi,
>
> nevertheless, in many cases modern iPads work as well, or at least
> almost as well, for a wide range of professional applications as desktop
> PCs do, while tablet computers based on Linux (Android and anything
> else) fail miserably, despite equally excellent hardware.
>
> Proper quality management and real standards always make a big
> difference, even if they are never perfect and there are some mistakes
> and they do not protect against a malicious corporate philosophy and
> human error.
>
> Windows doesn't seem to be doing too badly in this area either. I have
> heard of professional applications for desktop PCs that can also run on
> a Windows tablet.
>
> > Why not mimic the FreeBSD packaging and port systems ? I still use
> > Linux today but less than some years ago because I've found FreeBSD
> > that's a lot intriguing. The main reason is to escape from the
> > dependencies nightmare. I'm not sure if there is a Linux distro that
> > uses the same techniques as FreeBSD for installing tools. Anyway I'm
> > very satisfied by that system.
>
> In the regard of packages Arch Linux has got a similar approach as
> FreeBSD. It provides package repositories and a FreeBSD port alike build
> system. In most cases software from upstream isn't even split by the
> provided packages. Building by the port alike system, in a clean chroot
> is straight forward. The documentation of Arch Linux is also similar to
> the documentation of FreeBSD.
>
> >> I hope that the next upgrade doesn't install a package named
> >> systemd-registry or systemd-kernel.
> > That's another critical point. A lot of Linux users don't like
> > systemd. Probably because it is perceived as heavy and complicated to
> > manage. Even here,FreeBSD uses rc.d that's old but good enough and
> > versatile. Sometimes the old techniques are better than the newer
> > ones.
>
> The problem with systemd is, that it's not just an init system. However,
> even with systemd a user can still use e.g. a fstab instead of countless
> confusing systemd units. OTHO even without systemd, some ditros do not
> use systemd, there are still insanely split configurations.
>
> If for example an admin maintains a lean and clean
> /etc/security/limits.conf, the admin needs to take a look at
> /etc/security/limits.d/ each time a new package gets installed, each
> time after installing upgrades. And it's not only
> /etc/security/limits.d/, there are countless drop-in directories. I'm
> not aware of any admin, power-user, expert who wasn't already bitten by
> a drop-in directory issue.
>
> Regards,
> Ralf
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


-- 
Mario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20240115/b66b1333/attachment.html>