Re: [DNG] snapd in Devuan? Dependency on systemd...
On 2020-12-02 01:09, Bernard Rosset via Dng wrote: > Certbot has removed support of certbot-auto for Debian-based systems Sorry, I feel contrarian today (and many other days too). So there: http://michael.orlitzky.com/articles/lets_not_encrypt.xhtml -- Ian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] snapd in Devuan? Dependency on systemd...
On Tue, Dec 1, 2020 at 6:09 PM Bernard Rosset via Dng wrote: > > Certbot has removed support of certbot-auto for Debian-based systems > (cf. > https://github.com/certbot/certbot/blob/adacc4ab6dc63b024b17f0ec5adeb1adc9f93300/certbot-auto#L802). > > Official instructions for Debian > (https://certbot.eff.org/lets-encrypt/debianbuster-other) tell to use > the snapd package (https://packages.debian.org/buster/snapd)... which > depends on systemd and has not been rebuilt separately for Devuan yet. > > Is there any plan to do so? > I know making the list of repackaged packages grow is troublesome for > maintenance future-wise... > Greetings I would suggest that you stay as far as you can form snapd! I spent about 8 months working on/with it and in the end was totally frustrated. After you install snapd - - - - -well canonical will upgrade anything AND everything on its schedule. You CANNOT change that! The longest file in the forum is individuals asking for an off switch for updates. You can push it to about 60 days with some serious tap dancing. I tried ALL the options giving to stop the triggered updates - - - my machine responded by shutting down. So I didn't get the updates but the machine would shut itself off when it was time for upgrades. Then I tried to remove the shebang! I tried using $rm -r and still had 'crap' hanging around. Got real frustrated with that. Left the mess for about a year and then when I tried to restart the machine I couldn't get a complete reboot (even using secure boot for repair). So I was forced to replace the complete system - - - - a right royal pita. The idea is good (lxd) but snapd - - - - that's toxic! HTH ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] snapd in Devuan? Dependency on systemd...
> On 2 Dec 2020, at 11:09, Bernard Rosset via Dng wrote: > > Certbot has removed support of certbot-auto for Debian-based systems (cf. > https://github.com/certbot/certbot/blob/adacc4ab6dc63b024b17f0ec5adeb1adc9f93300/certbot-auto#L802). > > Official instructions for Debian > (https://certbot.eff.org/lets-encrypt/debianbuster-other) tell to use the > snapd package (https://packages.debian.org/buster/snapd)... which depends on > systemd and has not been rebuilt separately for Devuan yet. > > Is there any plan to do so? > I know making the list of repackaged packages grow is troublesome for > maintenance future-wise... > > Cheers, > Bernard (Beer) Rosset > https://rosset.net Have you tried just installing certbot via apt directly? It’s available in the repositories. There are instructions on their website for Devuan Beowulf at https://certbot.eff.org/lets-encrypt/devuanbeowulf-other___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] snapd in Devuan? Dependency on systemd...
Certbot has removed support of certbot-auto for Debian-based systems (cf. https://github.com/certbot/certbot/blob/adacc4ab6dc63b024b17f0ec5adeb1adc9f93300/certbot-auto#L802). Official instructions for Debian (https://certbot.eff.org/lets-encrypt/debianbuster-other) tell to use the snapd package (https://packages.debian.org/buster/snapd)... which depends on systemd and has not been rebuilt separately for Devuan yet. Is there any plan to do so? I know making the list of repackaged packages grow is troublesome for maintenance future-wise... Cheers, Bernard (Beer) Rosset https://rosset.net/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba/NAS box problem
On 12/1/20 10:03 AM, Rowland penny via Dng wrote: On 01/12/2020 16:25, Fred wrote: Hello, I have a DNS321 NAS box on my local network and samba/cifs to access it. When I upgraded from Debian Jessie to i386 Beowulf the DNS321 was no longer accessible by samba. fred@ragnok:~$ mount /mnt/dns321 Password for fred@//192.168.42.32/Volume_1: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) This is the /etc/fstab entry: //192.168.42.32/Volume_1 /mnt/dns321 cifs rw,user 0 0 The dsn321 is accessible with ftp. The mount.cifs manual pages had lots of interesting options but I didn't see any clue about what might be the problem. Where would one look up error(112) to find out what it means? Best regards, Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng This undoubtedly down to SMBv1 (or rather the lack of it), try adding 'vers=1.0' to the cifs options in /etc/fstab Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Hi Rowland, That fixed it. Thanks for the help! Best regards, Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba/NAS box problem
On Tue, 1 Dec 2020 17:03:19 + Rowland penny via Dng wrote: > On 01/12/2020 16:25, Fred wrote: > > Hello, > > > > I have a DNS321 NAS box on my local network and samba/cifs to > > access it. When I upgraded from Debian Jessie to i386 Beowulf the > > DNS321 was no longer accessible by samba. > > > > fred@ragnok:~$ mount /mnt/dns321 > > Password for fred@//192.168.42.32/Volume_1: > > mount error(112): Host is down > > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) > > > > This is the /etc/fstab entry: > > //192.168.42.32/Volume_1 /mnt/dns321 cifs rw,user 0 0 > > > > The dsn321 is accessible with ftp. > > The mount.cifs manual pages had lots of interesting options but I > > didn't see any clue about what might be the problem. > > > > Where would one look up error(112) to find out what it means? > > Best regards, > > Fred > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > This undoubtedly down to SMBv1 (or rather the lack of it), try adding > 'vers=1.0' to the cifs options in /etc/fstab You can 'nmap --script smb-protocols ' for a list of supported versions. libre Grüße, Florian ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba/NAS box problem
On 01/12/2020 16:25, Fred wrote: Hello, I have a DNS321 NAS box on my local network and samba/cifs to access it. When I upgraded from Debian Jessie to i386 Beowulf the DNS321 was no longer accessible by samba. fred@ragnok:~$ mount /mnt/dns321 Password for fred@//192.168.42.32/Volume_1: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) This is the /etc/fstab entry: //192.168.42.32/Volume_1 /mnt/dns321 cifs rw,user 0 0 The dsn321 is accessible with ftp. The mount.cifs manual pages had lots of interesting options but I didn't see any clue about what might be the problem. Where would one look up error(112) to find out what it means? Best regards, Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng This undoubtedly down to SMBv1 (or rather the lack of it), try adding 'vers=1.0' to the cifs options in /etc/fstab Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] samba/NAS box problem
Hello, I have a DNS321 NAS box on my local network and samba/cifs to access it. When I upgraded from Debian Jessie to i386 Beowulf the DNS321 was no longer accessible by samba. fred@ragnok:~$ mount /mnt/dns321 Password for fred@//192.168.42.32/Volume_1: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) This is the /etc/fstab entry: //192.168.42.32/Volume_1 /mnt/dns321 cifs rw,user 0 0 The dsn321 is accessible with ftp. The mount.cifs manual pages had lots of interesting options but I didn't see any clue about what might be the problem. Where would one look up error(112) to find out what it means? Best regards, Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What I learned at Distrowatch
On Tue, Dec 01, 2020 at 03:33:41PM +0100, Antony Stone wrote: > What, specifically, gets installed as part of Devuan which you don't want to > see there? As an exercise, try doing a minimal install via debootstrap, which is arguably the easiest way to tailor an install. I've thus far not managed to get an install through without elogind creeping in, even if I explicitly mark it as something to ignore. The Devuan live media I use for installs runs elogind. It sort of reminds me of the Agent Smith virus speech from The Matrix. > libsystemd0 is a stub library which contains none of the objectionable > code or "features" which people who don't want systemd are trying to keep > away from. Unix libraries bundle related functionality together so that you can link just that which you need. Can you explain how libsystemd0 fits into this model? I'm unclear on what set of related functions it provides. -- Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What I learned at Distrowatch
On Tuesday 01 December 2020 at 15:16:57, Mason Loring Bliss wrote: > This brings us to the other thing worthy of note. Try sometime to install > Devuan (not Debian, Devuan) without systemd and you'll be in for a rude > shock. It's installed by default, and it's a massive pain to eradicate it. Please give more detail about what you mean in this context by "systemd". What, specifically, gets installed as part of Devuan which you don't want to see there? > Does this bother you? It bothers me. If it's impossible to install *Devuan* > without systemd, that's problematic. (To forestall the inevitable pedantry, > elogind is systemd. It's a major component of it. And libelogind0 maps > directly to libsystemd0. A rose by any other name...) libsystemd0 is a stub library which contains none of the objectionable code or "features" which people who don't want systemd are trying to keep away from. Regards, Antony. -- The difference between theory and practice is that in theory there is no difference, whereas in practice there is. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What I learned at Distrowatch
On Mon, Nov 30, 2020 at 05:34:48PM -0500, Steve Litt wrote: > The fact that Redhat is #64 tells me not that many people are buying > their stupid support, Lest we get too excited, let me note two things: https://distrowatch.com/dwres.php?resource=faq#phr This says, What is this "Page Hit Ranking"? It is a light-hearted way of looking at popularity of distribution. Since each distribution has its own page, we thought it would be fun to track the number of visitors viewing individual distribution pages. The Page Hit Ranking (PHR) figure represents hits per day by unique visitors; as determined by the visitor's IP address. So, you need to ask yourself if the people buying Red Hat support contracts are visiting DistroWatch daily. I'd argue that, having made their choice, they probably aren't weighing the merits of deploying MX Linux to their datacenters. > And given Redhat's, Freedesktop's and Poettering's rhetoric about how > completely systemd has taken over, #64 is unexpectedly low This brings us to the other thing worthy of note. Try sometime to install Devuan (not Debian, Devuan) without systemd and you'll be in for a rude shock. It's installed by default, and it's a massive pain to eradicate it. Does this bother you? It bothers me. If it's impossible to install *Devuan* without systemd, that's problematic. (To forestall the inevitable pedantry, elogind is systemd. It's a major component of it. And libelogind0 maps directly to libsystemd0. A rose by any other name...) -- Mason Loring Bliss (( If I have not seen as far as others, it is because ma...@blisses.org )) giants were standing on my shoulders. - Hal Abelson signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] cups in ceres: Correction
On Tue, 1 Dec 2020 13:35:48 + fraser kendall wrote: Correction: > Workaround from > https://askubuntu.com/questions/1069702/dpkg-error-processing-package-install-info > > #mv /var/lib/dpkg/info/install-info.postinst > /var/lib/dpkg/info/install-info.postinst.bad > #mv /var/lib/dpkg/info/install-info.postrm > /var/lib/dpkg/info/install-info.postrm.bad > #mv /var/lib/dpkg/info/install-info.prerm > /var/lib/dpkg/info/install-info.prerm.bad > #dpkg -r printer-driver-cups-pdf > Should be: #mv /var/lib/dpkg/info/printer-driver-cups-pdf.postinst /var/lib/dpkg/info/printer-driver-cups-pdf.postinst.bad #mv /var/lib/dpkg/info/printer-driver-cups-pdf.postrm /var/lib/dpkg/info/printer-driver-cups-pdf.postrm.bad #mv /var/lib/dpkg/info/printer-driver-cups-pdf.prerm /var/lib/dpkg/info/printer-driver-cups-pdf.prerm.bad #dpkg -r printer-driver-cups-pdf Sorry for that. f ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] cups in ceres
On Tue, 1 Dec 2020 03:23:11 +0100 Arnt Karlsen wrote: > On Mon, 30 Nov 2020 11:39:37 +, Le wrote in message > <20201130113937.6da5d2fa@cruncher>: > > > Hello, > > > > I'm getting a circular problem upgrading cups in ceres. I've been > > tackling this for a week or so. I need two root terminals open: > > one to apt-get and the other to top + kill apt-get and dpkg. > > ..snip PITA details > Given up trying to find an answer. Not due to apparmor. Workaround from https://askubuntu.com/questions/1069702/dpkg-error-processing-package-install-info #mv /var/lib/dpkg/info/install-info.postinst /var/lib/dpkg/info/install-info.postinst.bad #mv /var/lib/dpkg/info/install-info.postrm /var/lib/dpkg/info/install-info.postrm.bad #mv /var/lib/dpkg/info/install-info.prerm /var/lib/dpkg/info/install-info.prerm.bad #dpkg -r printer-driver-cups-pdf seems to restore apt-get functionality. Posting for the record. Best fraser ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What I learned at Distrowatch
never learned anything at DW by looking statistics.. some guides and reviews were helpful... On 12/1/20 12:34 AM, Steve Litt wrote: fact that Redhat is #64 certainly not a fact. this is just a number without value. just a "Page Hit Rank"... if i was to guess, i'd say "serious corporate executives who use RH" (haha), don't visit DW so often as linux enthusiasts/hobbyists/distro testers (= community). fact is that DW seems to be on the init-freedom side, and that's a good thing... --- btw, MX linux comes with systemd (disabled), by default. 2c. d. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
