https://lists.dyne.org/lurker/message/2 … 81.en.html

Hi fsmithred,

nothing has changed in the repo: there was just a mistake in the numbering of the latest version of debootstrap in ascii. It should have been named +devuan2.1 while it has suffix -devuan2.1 (notice the difference between "-" and "+"), As such, version "-devuan2.1" is lower than any of the other versions, hence it is never considered for installation. Also, "~" sorts before anything else :-)

HTH

KatolaZ

Hi gop,

Beowulf has not been released. If you are familiar with the Debian way of dealing with releases, Beowulf is more or less equivalent to a Debian/testing. Hence, there are no official installation images for it yet. There is only a stripped-down testing minimal iso that can be used to perform a netinst. It is available at:

  https://pkgmaster.devuan.org/devuan/dis … t/mini.iso

If you want to upgrade an existing ascii to beowulf, you can use as a reference the guide provided at:

  https://devuan.org/os/documentation/dev … e-to-ascii

noting that you are not upgrading from jessie to ascii, rather from ascii to beowulf. If you spot any bug in beowulf, please report it.

HTH

KatolaZ

Hi,

why do you need the git repo of the kernel at all? if you just want to compile the kernel yourself, use one of the tarballs available at www.kernel.org You should get the git repo only if you want to contribute to kernel development. If you are determined to have a repo anyway, you should try a shallow clone, but that's not particularly easy in a repo as large as that...

HTH

KatolaZ

Hi,

Devuan has its own devuan-sdk:

  https://git.devuan.org/sdk

which is a tool to create different kinds of Devuan-based images. In your case, you can create a live image by using live-sdk. It comes with two pre-defined "blends" (desktop-live and minimal-live). It's an easy and extremely customisable way of getting your own live Devuan derivative.

HTH

KatolaZ

In general, you should only use third-party repos only if you trust them. And I would not trust a third-party repo which says it is providing php7 and then also contains a replacement for openssl. Please be careful with this stuff, and use it at your own risk. You would probably be better off upgrading to ascii, if you desperately need php7. Or compile it by yourself.

My2Cents

KatolaZ

This is not the case any more. Just have a look on the interweb, as I did before recently buyng a new SSD. I was skeptical about them as well, but as I found out I was totally wrong.

The average write before starting to reallocating sectors seems to never fall below 300TB for SSDs produced in the last 3 years. Some of them can go up to 2.4 PB before the first sectors get reallocated. This means that you can fully write 1TB disk between 300 and 2400 times before it starts to physically wear out. In many cases, this will amount to several lustres (if you write 50GB of data every day, you will need 6000 days to write 300TB, which is slightly more than 16 years). The expected fraction of SDDs having one write failure during the first three years of their lifespan is 0.3%, or 3 over 1000. I know this might look big, but for classical HDDs this percentage is normally much higher (around 3-5%), and HDDs have 50% probability of failing after 6 years.

In conclusion, there is no scientific argument supporting the myth that SSDs fail more often than HDDs, rather the opposite.

Then, if you ask me whether the extra speed provided by the SSD was worth the 120GBP it costed, I would say "probably not entirely, at least in my case". I mostly use lightweight applications, and my laptop has uptimes of several months, which means that almost everything I need is always availalbe either in RAM or in the buffer cache or in the disk cache, and loads pretty fast. There is a noticeable improvement in boot times and start times of heavy applications, but again, those are mostly outside my use case. YMMV.

So the main reason why I actually decided to buy an SSD was basically its expected durability :-)

Please feel free to move this post elsewhere, if it looks OT.

My2Cents

KatolaZ

-- edited "2.4 TB" -> "2.4 PB"

It's most probably elogind-related, and it's stuff needed for session management. If you ```apt-get remove --purge elogind```, the folder will disappear (but you will not be able to automount any USB drive as a user, reboot/suspend as a user, and similar stuff). elogind is an alternative to systemd-logind which replaces systemd code (and removes most of the unnecessary stuff).

HTH

KatolaZ

You need matching kernel headers for wireguard-dkms to work.

HND

KatolaZ

I confirm that nothing has changed: bugs should be filed at bugs.devuan.org, using reportbug. That's the only way to actually keep track of all the outstanding bugs. You are still free to report on DNG, or on this forum, but don't be surprised if the report goes "forgotten". The way to report bugs in Devuan is by using `reportbug`, as explained in the first post of this thread.

HTH

KatolaZ

Dear Dutch_Master,

with the risk of re-stating the obvious: Devuan (as Debian) is not a rolling release. Devuan ASCII is the stable branch of Devuan. Once a release becomes "stable" it will not receive updates any more, except for security issues, which will go anyway in <codename>-security, and simple issues related to the Debian packaging itself, which will go under <codename>-updates. This means that the versions of packages are freezed at the time the release went out (actually, a few months before that happens). There is a place for higher versions of some packages in Debian/Devuan, and that place is "<codename>-backports". This is a suite of the repo that offers newer versions of some packages to a stable release, guaranteeing that they will work without requiring anything that is not already available in the "main" suite and/or in the "<codename>-backports" suite itself.

Since youtube-dl is a script that keeps changing over and over again, and does not have many dependencies, the best options for a single user are probably to either 1) use the "source" version, and update it every once in a while,  or 2) install the deb from Ceres, and pin it down appropriately.

The third option would be to have youtube-dl included in Devuan's ascii-backports. But that needs somebody who is willing to maintain it for backports, i.e., to update it and make sure that it works properly in ASCII. There is no point in getting upset if you are suggested/requested to maintain a package you need, as there is no point in asking somebody else to do that on your behalf :-) Devuan is mainly a community effort, and the people currently working on Devuan development have no time to handle backports. Nevertheless, literally anybody is welcome to join such development effort, so this situation can change in the future if people interested in having such and such package backported to stable actually step up and do some work for that to happen.

HTH

KatolaZ