Re: [DNG] why is polkit needed?
On Fri, 06 Mar 2020 15:25:55 -0700 tekHedd wrote: > On Fri, Mar 6, 2020, at 12:51 PM, Hendrik Boom wrote: > > On Thu, Mar 05, 2020 at 02:09:37PM +0100, Didier Kryn wrote: > > > Le 03/03/2020 à 23:37, tekHedd a écrit : > > > > > > > > So, I would consider rewriting polkit and dbus from scratch. > > > > > > > > Also, who has time to rewrite polkit and dbus from scratch? > > > > What are the actual requirements for a dbus-like system? > > Requirements that would allow a completely different design? > > Exactly. Are there even requirements supporting the current design? > Were there ever requirements at all? We can easily see what it does, > but it's really hard to determine what it *needs* to do. > > Bad sign: You know you've chosen poorly the moment you are > simultaneously offering a) broadcast messaging and b) guaranteed > delivery. > > A google search for d-bus requirements turns up, well, documentation > of its current architecture. No requirements. Also contains this > choice quote: > > "The usage of D-Bus is steadily expanding beyond the initial scope of > desktop environments to cover an increasing amount of system > services. For instance, NetworkManager network daemon, BlueZ > bluetooth stack and Pulseaudio sound server use D-Bus to provide part > or all of its services. systemd uses the D-Bus wire protocol for > communication between systemctl and systemd, and is also promoting > traditional system daemons to D-Bus services, such as logind.[25] > Another heavy user of D-Bus is Polkit, whose policy authority daemon > is implemented as a service connected to the system bus.[26]" > > So... all of the usual suspects. What is absent here? That's right, > no *other* programs are listed besides the usual suspects. So who > really uses it? > > Nothing I can find suggests that dbus is used for anything essential, > besides possibly polkit. And there's nothing suggesting that polkit > needs to be implemented via dbus. Therefore, you could eliminate dbus > entirely and rethink polkit's implementation without undue impact, > assuming you are ditching systemd and friends of course. > > (I realize I'm skirting "devil's advocate" territory here...) > > t > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng The ONLY thing I am using DBUS for on my systems is for notifications. Be it have something blip in the top right of my monitor when I get an email, or gmusicplayer changes a song. psi-plus (XMPP client) is able to read MPRISv2 over dbus to update my presence information with the song i'm currently listening to. Other than that that is the only thing dbus is useful for that I can see. But I am sure there is a more elegant way to handle desktop notifications. but to me clear i'm talking purely about dbus, not polkit -- _ < You love peace. > - \ \ /\ /\ //\\_//\\ \_ _// / / * * \/^^^] \_\O/_/[ ] / \_[ / \ \_ / / [ [ / \/ _/ _[ [ \ /_/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] why is polkit needed?
Quoting tekHedd (tekh...@byteheaven.net): > Cool software doesn't really happen without the ability for apps to > communicate and read/write the state of the system and communicate > with other user level components. If so, so what? This doesn't in any way suggest need for a new extra system authentication layer. By default, all software running under the user's EUID can intercommunicate as peers. So, given that, and taking as true for the sake of discussion your assertion above, what would polkit or a workalike add, given that apps can already do what you said is desirable? I don't know, man. Perhaps we're somehow failing to communicate, on that point. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
Quoting Rainer Weikusat via Dng (dng@lists.dyne.org): > But this is not the case. There's nothing which stops users from running > their own, fully capable resolver locally[*] (or somewhere on a local > network) and thus, not make a comprehensive browsing history available > to any third party. Reminder, I maintain a bestiary of all 'DNS Server (and Related) Software for Linux' by category, here: http://linuxmafia.com/faq/Network_Other/dns-servers.html Candidate (maintained) open source recursive resolvers for Linux are: o bind9 (has baggage; see page) o Deadwood o dnscache (from djbdns), if patched to modern standards o PowerDNS Recursor o Unbound For various reasons out of scope here, I would generally recommend Unbound. (I'm sure Deadwood is really good and competitive, but am unsure of its packaging status. Disclaimer: Sam Trenholme, author of Deadwood and MaraDNS, is a friend of mine.) > [*] Except systemd-resolvd, of course, at that's (reportedly) a stub > resolver to replace another stub resolver :->. Correct. -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when we're such cool people out with whom to hang?" r...@linuxmafia.com-- @laureneoneal (Lauren O'Neal) McQ! (4x80) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Installer images for armel, armhf and ppc64 need testing
On 3/6/20 6:30 PM, fsmithred wrote:
> On 3/2/20 7:54 PM, fsmithred wrote:
>> We built beowulf installer images for armel, armhf and ppc64el. If you
>> have appropriate hardware, please test and report.
>>
>> armel (no mini.iso for these. I hope you know what to do.)
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armel/current/images/
>>
>> kirkwood/netboot/marvell/{dreamplug,guruplug,sheevaplug,sheevaplug-esata}
>> kirkwood/netboot/seagate/dockstar
>> orion/netboot/buffalo
>>
>> armhf
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/netboot/mini.iso
>>
>> ppc64el
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-ppc64el/current/images/netboot/mini.iso
>>
>> Thanks,
>> fsmithred
>>
>
>
> I installed from the ppc64el mini.iso in qemu today. That one works.
> Anyone else?
>
> fsr
>
arm64 has been added:
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-arm64/current/images/
fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] why is polkit needed?
Le 06/03/2020 à 20:51, Hendrik Boom a écrit : What are the actual requirements for a dbus-like system? Requirements that would allow a completely different design? There must have been requirements. At the time KDE had its own middleware called DCOP and Gnome had or was developping its own. I guess they both had requirements and they devised a superset. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
