Go ahead and test them
some would support 4GB Ram, some maybe 8GB Ram( ShorTie,C0rnelius, MetaYan? )
tux

As far as I know, the images support all versions of the RPi4 and if setup, can also USB boot.
As for the kernel, the builder supports 4.19LTS, 5.4LTS and branches as high as 5.7.y. (currently)
There is also a mainline branch, for those who wanna test kernels without the foundation patch set applied.
I've yet to include Devuan in that branch, but that shouldn't stop anyone from using it to compile a kernel and installing it in Devuan.

To those interested in the RPI support topic: Feel free to start a new thread.

The subject about RPi4 can be seen here
There are experimental Images available by:
MetaYan
ShorTie
and by C0rnelius

So 3 different images for rpi4

I believe all the 3 images are based in RaspBerry PI foundation kernels, so they are updated( by the RPi standards, because last stable mainline kernel is now 5.7 )..

Go ahead and test them
some would support 4GB Ram, some maybe 8GB Ram( ShorTie,C0rnelius, MetaYan? )

Debian started to do some RPi development, and they have some images( like Yeti stated above ), but none for RPi4, iirc..

Edit: What they start to have is a continuous integration system based in ARM Server class hardware..
https://www.debian.org/News/2020/20200616

Best Regards,
tux

The sed "s/__LINUX_IMAGE__/... lines patch in the kernel deb's name into a copy of the config template and the kernels are in the standard Debian repos for those arches.

If Debian has a repo for that, I am sure Devuan could follow the same approach to build images for the RPI.

Ahh ...
Petit dètail.

I understand.

I've not seen anything like that.

Where does the Raspbian kernel come from?
How do the Ubuntu people do it?
Surely they are both Debian based.

Indeed ...
But like you say, no generic kernel.  8^7

Of course, I agree 100%, it is a false sense of security.
I was trying to make a point.

Thanks for your input.

A.

Given this situation, I don't see any sound way for providing any sound RPI support in Devuan. Just two ideas:

(1) Imho, the best approach would be to build some kind of "Respuan" that includes all the RPI-specific stuff but uses Devuan instead of Debian. Not sure if anyone tried this already?
(2) As an alternative, you could package a kernel for the RPI boards and then build installation images which use this kernel. However, keep ind mind that one of the great benefits of Debian's "universal OS" approach is having one generic kernel per architecture that works for all supported devices...

Nevertheless, shipping images with a kernel that is not packaged and receives no security updates whatsoever is probably not the best way to convince people about the benefits of Devuan's core philosophy - at least if you ask me.

From where I stand ie: not a coder or developer, just a 65+ advanced (?) user, what you say makes a lot of sense.

But I also believe that it makes sense to take into account that for Devuan, which has a hard time as things stand, things won't get easier if it has no access to or ignores SBC hardware such as RPis of which over 35 million have been sold.

These inexpensive SBP are the entry point to IT for a great many people who maybe cannot afford something else, just want to play and see what it is like or just need an inexpensive solution to a small and simple problem.

And if you leave it all to Raspbian, you will have lost a lot of potential users many of which may eventually become IT staff or pros ie: just the people Devuan needs to survive in the future.

I'm afraid that spawning dozens of derivatives will not be enough.

The Devuan project is not just a distribution, it also represents a core philosophy (Unix) or an ideology if you will.
Exactly the opposite of what mainstream MS software represents today. 

It urgently needs to develop a strategy to occupy the RPi field or get permanently pushed out of it.

Just another point of view and as always, YMMV.

Cheers,

A.

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

Interestingly, this worked like a charm - without setting up any netboot server or alike! Now I just wonder what the difference between the netboot and netinst ISO actually is.

Regarding the RPI side-topic: As long as the packaged Devuan kernel is not working for the RPI, I don't see much value in providing such images. This sort of images with a "hardcoded" kernels are definitely not what you want to run on a production system connected to any non-trustworthy network. The result of such images is that some users that are not aware of this issue, develop a false sense about security of such systems and run them in production with no kernel updates forever.

I thought so.

I tried (just to test it) but it did not do anything because of the system lacking the proper entries in /etc/apt/sources.list.
Maybe when Beowulf reaches old-stable.

I understand.
But I don't want the mainline version, just the last stable one.

Thanks a lot for taking the time to explain this.

Best,

A.

Hello:
There's only one (have I missed something?) image for RPi3 and it is from 2 years ago.
Would it be the same as an image of the last/latest Devuan ascii 2.1 old-stable?

Hello Altoid,
yep for rpi 3B+ its the only arm64 image, but you can dist-upgrade it to beowulf..
besides one of the problems of RPi sbc's is that they are not mainlined.. and because of that, they are always behind..

Which means even if you are with the latest version, you are always behind( and still not mainline.. )
For example, kernels >= 5.6 are a nice to have thing( since they have wireguard vpn kernel driver mainlined.. ).

You can't have that on RPi,
because the experimental version for RPi is now kernel 5.4( so you are always behind, weather you want it or not..   ), in contrast with other sbc's were you can have the latest kernels..

An example,
The Lime2 from Olimex which is a 5.7.0 Kernel( wireguard enabled.. ).
We are talking about a dual core Cortex-A7, which can now be seen as a old board, but because it has mainline kernels, you are always updated..

While my WS ascii installaton gets me this ...

groucho@devuan:~$ apt list --installed | grep -i linux-image
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
linux-image-4.9.0-12-amd64/oldstable-security,now 4.9.210-1+deb9u1 amd64 [installed,automatic]
linux-image-amd64/oldstable,now 4.9+80+deb9u10 amd64 [installed]
groucho@devuan:~$ 

... my RPi installation (image) gets me this:

pi@rpidevuan:~$ apt list --installed | grep -i linux-image
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
pi@rpidevuan:~$ 

Please explain as I'm not getting the point.

Thnaks,

A.

yeti wrote:

... official RPi images never got kernel updates.

No idea ...
Is there/would there be a reason for that?

Search the kernel image in the list of installed packages.

No idea ...
Is there/would there be a reason for that?

As I noted previously, there's only one image for the RPi3 and it is 12 major revisions behind.

A.