DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
IMHO it's still a fraud (asking donations for re-building 10 or less completely free Debian packages sounds unethical to me).
They've mostly changed udisks2 and added policykit again.
This works on any normal installation as well (though I would personally never recommend it).
It's far from being fraud. Many companies looking to get donations are doing so to raise minimal capital for basic needs like webservers and a dotcom namespace. Devuan has many donations of software going on but they need money/cash to get servers up and running. I'm less worried about the developers, if any. The cause is noble and is geared towards software sanity in UNIX, not just GNU/Linux if you read the mission statement.
It's far from being fraud. Many companies looking to get donations are doing so to raise minimal capital for basic needs like webservers and a dotcom namespace. Devuan has many donations of software going on but they need money/cash to get servers up and running. I'm less worried about the developers, if any. The cause is noble and is geared towards software sanity in UNIX, not just GNU/Linux if you read the mission statement.
You're missing my entire point.
I could have done this in few seconds (building packages is easy in debian).
Thing is, who the bleep are those "Elite" people and why do they need donations for something that easy?
They claim the need for extra logistics/hardware.
That's pure nonsense.
Debian is open to accept all their packages (no extra server/whatever costs needed).
I honestly doubt if any of them even understands what they're doing (their ... code ... er ... very few changes aren't that exiting).
PS: For a distribution as big as debian, trust does matter.
jens, I encourage you to take a look at https://git.devuan.org/ sometime . Devuan is a long-term project, and as such the VUA have been putting most of their efforts towards building the infrastructure necessary to keep it going, and towards writing replacements for systemd-encumbered programs. Here are some links you might like:
* loginkit: A backwards-compatible systemd-free logind replacement.
* amprolla: An APT mirroring system that lets us transparently overlay Devuan's packages on top of Debian's mirrors.
* jenkins-debian-glue: Glue code that ties the GitLab repositories to the Jenkins build servers, so we can queue packages to be built and pushed to the repository.
* devuan-sdk: An SDK that aims to make it easy for Devuan developers to import code from Debian or git into Devuan's GitLab, and build packages, and toast ISOs.
* vdev: A device manager to replace udev and some aspects of logind (disclaimer: I'm the author, AMA).
* Devuan Puppy Linux: The Community Edition of Puppy now supports building from Devuan.
This is on top of:
* the ~100 packages we're maintaining patches for to remove dependencies on systemd
* the Jenkins build servers we've got set up
* the GitLab server, mailing lists, and IRC channels
* the APT repository
Also, although I've been asked not to share links publicly (but they're in the mailing list archives if you're interested), we also have nightly QEMU images we use for testing, as well as a discourse forum in the works.
Please don't let the low Web profile fool you . Most of us prefer mailing lists, IRC, and git, so that's where most of the action happens. You can find our mailing list archives here, and the development IRC logs here.
Are you sure that is the correct link? It points to a Git repository created two months ago with no commits since then, except an initial commit containing a dead link.
@veerain: One of the motivations for logind is to filter access to device files on a per-process basis. An unprivileged program can ask logind for a file descriptor for a device file, and logind will either open it on its behalf or reject the request, subject to some admin-given policy. The approach taken by vdev is to offer not only a hotplug daemon (vdevd) to replace udev, but also an optional userspace device filesystem (vdevfs) to sit on top of /dev and selectively hide or alter the visible properties of device nodes based on which process is asking (this is possible since FUSE exposes the task ID of the calling thread, which can then be resolved to the calling program in /proc). This would let you do the same sorts of things as logind (e.g. filter device access by seat, by session, by container, etc.), but without needing to modify the client programs to do so. I have a design document here that goes into more detail: http://judecnelson.blogspot.com/2015...cing-vdev.html.
Thanks, that works. So, I have looked around a bit, especially at the Devuan Project Documentation, and at this point I find it rather funny, but not really serious. Since you are a Devuan developer I can ask directly, I see this in said documentation:
Quote:
and to avoid any lock-in in the most important parts of the systems by avoiding things that are trying to hijack the GNU part of the system, like systemd is doing right now in many distros and also in our lovely debian.
and this
Quote:
preserving users and sysadmins to be forced to abandon the GNU, KISS and UNIX philosophy and losing control,
and I have to ask, which part of systemd do you perceive is taking away something from GNU and which part of GNU is taken away?
I also have a question about the Devuan Constitution, especially article 2.2:
Quote:
2.2 protect freedom of choice of users and developers
An universal OS must protect freedom of choice, trying to provide all the alternatives to adapt to any use case, from a common home user to a developer and/or a sysadmin, and avoiding to force minoritarian users to work in the way the majority follow, as any minority has usually good reasons for doing thing in different way.
I don't quite get how you can claim that you want to provide freedom of choice and at the same time dismiss the inclusion of systemd, by now the most used init system (and more) in your repositories, maybe you can explain that a bit.
Sidenote: When I saw this
Quote:
We consider ourselves the real debian history continuity path, and the actual debian like a fork from us, or a derivate from devuan with bloatware added.
My first thought was that this would be the first time I know off that the derivative (Debian, is there a specific reason that you write it lowercase?) provides the repositories for the the main distro and not the other way around.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.